Verify callback signatures before trusting event fields
The adapter currently reads order IDs before validating callbacks.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Webhook security
Estimated field mix
- Security70%
- Integrations30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional software vendor changes payment providers. Its application must tolerate unknown outcomes, signed callbacks, refunds, and inconsistent settlement reports.
Setup prerequisites
- Create a local payment-provider double and synthetic orders; use test-only signatures and execute no financial transactions.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Verify raw bytes with the configured test key.
- Enforce timestamp tolerance and key identity.
- Reject malformed or unsigned bodies before processing.
Implementation constraints
- Never log signing secrets or full callback bodies.
Verification to include
- Accept a valid signed fixture.
- Reject modified bytes and an expired timestamp.
Deliverables
- Callback verification boundary.
Rollout and recovery
Reject unverifiable callbacks; retain safe failure counts.
Value of the work
For the engineer: Practice idempotent integrations, state reconciliation, and provider migration.
For the team: Provide a reviewable adapter design that protects order consistency and recovery.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.