Say what changes hands
Use approved currency, scope, timing, terms, and customer information before payment begins.
Commerce route
Keep the customer promise attached to the payment state.
Card, bank, mobile-money, or other provider routes are project decisions to verify—not assumptions. Whatever route is approved, the system must keep price, consent, confirmation, fulfilment, support, and reconciliation connected.
Create one traceable attempt
Protect against double submission and attach the provider reference to the internal record.
Handle delay and interruption
Do not equate a missing browser response with failure; reconcile provider callbacks safely.
Trigger only from accepted truth
Connect confirmation to the approved order state and tell the customer what happens next.
Support and reconcile
Give staff evidence for refund, dispute, fee, settlement, and end-of-day review.
Provider gate
Integration documentation is not permission to operate.
Before development, the business owner confirms the merchant account, country and currency support, settlement, identity requirements, prohibited uses, fees, and operational responsibilities directly with the provider.
- Test: duplicate, delayed, abandoned, declined, and refunded cases.
- Explain: clear customer status without exposing provider internals.
- Separate: technical events from tax and accounting conclusions.
- Reconcile: compare provider truth with the internal order record.
- Escalate: name who handles disputes and unsupported states.
Bring the approved route