Confirm available mechanisms
Check whether the provider documents polling, webhook notifications, or both. Do not assume webhook support exists because another panel offers it. Read how notifications identify an order and whether the documentation describes authentication or retry behavior.
Treat updates as evidence
Preserve the update source and timestamp. If events can arrive late or more than once, avoid creating new purchases or double-counting charges from repeated messages. Use the documented order state to reconcile discrepancies rather than relying on arrival order alone.
Keep a recovery path
A notification mechanism does not remove the need to investigate missing or inconsistent updates. Where supported, a periodic status lookup can reconcile outstanding records. Choose intervals and request volume within the provider's documented limits.
Decision checklist
| Decision | What to check |
|---|---|
| Support | Actually documented method |
| Identity | Order reference in update |
| Recovery | Reconciliation after missed events |
Worked example
A hypothetical integration receives the same completed notification twice. It should update the existing order record consistently, not record two completed purchases. The notification describes a state change; it is not a second authorization to order.
Example figures explain the decision; they are not current prices or promised results.