Payment State Discipline
Handle initiated, pending, completed, failed and exception states without ambiguity.
A structured merchant integration for payment initiation, status handling, callbacks and reconciliation across local payment routes.
DOT standardizes the merchant-facing flow where possible while preserving the market-specific behavior required by each local method.
Send order, amount, currency and customer context.
Redirect or display the relevant market payment experience.
Process callbacks, redirects and state transitions reliably.
Match transaction outcome, payment state and settlement records.
{
"merchantReference": "ORD-10452",
"amount": 39.99,
"currency": "USD",
"country": "EG",
"customer": {
"id": "C-2451",
"email": "[email protected]"
},
"returnUrl": "https://merchant.example/return",
"callbackUrl": "https://merchant.example/callback"
}Handle initiated, pending, completed, failed and exception states without ambiguity.
Protect payment creation and callback processing from duplicate execution.
Validate source, signature and event integrity before changing merchant order state.
Design merchant references and reporting logic for finance and operations from day one.
| Phase | Merchant objective | DOT support | Exit criterion |
|---|---|---|---|
| Discovery | Define the payment route | Scope methods, states, callbacks and dependencies | Approved integration brief |
| Build | Implement merchant flow | API guidance, sandbox path and technical support | Working end-to-end transaction |
| UAT | Prove business outcomes | Scenario validation, exception testing and acceptance | Go-live approval |
| Launch | Operate with confidence | Status monitoring and escalation support | Stable live route |
Start with the target market, payment method and desired checkout experience.