Map provider payment states to explicit order transitions
Two provider status names are currently treated as equivalent even though only one confirms collection.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State modeling
Estimated field mix
- Integrations60%
- Backend40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List provider states and allowed transitions.
- Represent pending and unknown separately.
- Reject impossible terminal reversals.
Implementation constraints
- Keep provider status distinct from local order status.
Verification to include
- Map successful and pending examples.
- Reject an unsupported state without marking an order paid.
Deliverables
- State mapping contract.
Rollout and recovery
Review mapping before accepting callbacks.
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.