Treat the payment callback as one event in a longer business transaction. The system must still decide what was paid, what record changed, whether an invoice exists and who owns any unresolved mismatch.
1. Establish one correlation chain
Define the identifier that connects checkout, order, account, payment request, provider event, invoice and reconciliation record. Do not depend on a phone number or amount as the only match key.
2. Make processing idempotent
The same provider message can arrive more than once. Reprocessing must not create a second payment application, order transition or tax invoice.
3. Separate payment from allocation
Money received and money correctly allocated are different states. Preserve both so operations can resolve unmatched or partially matched funds without altering the original evidence.
4. Design the tax failure path
If payment succeeds and invoice creation fails, create a visible exception. Record the cause, retry policy, responsible owner and evidence of eventual resolution.
5. Reconcile independently
Use an independent comparison process—not only real-time callbacks—to identify missing, duplicated, reversed or inconsistent records.
Core takeaway
A successful API response is not the same as an auditable commercial transaction.
Next step
Use the checklist in a discovery session with operations, finance, compliance and the technical team. Record disagreements as risks before they become production exceptions.