What to check
Use the order-reference or idempotency mechanism specified by the API documentation and retain results. After a timeout, query the original order.
Common pitfalls
Do not generate a new business reference for every retry and charge again, or undo a completed provider result merely because the client timed out.
The next step
Keep an uncertain result pending reconciliation and use queries and callbacks to establish a definite final state before proceeding.
Before taking action
- Confirm the merchant, currency and product requirements before selecting an available card.
- Check card status, the balance timestamp and the original order; distinguish pending from completed.
- Retain a redacted error and avoid duplicate submissions while an outcome remains uncertain.
Keep useful evidence
Record the event time and time zone, order reference, current state and redacted message. Separate completed steps from unresolved outcomes. Do not publish a full card number, security code, password or verification code. Keep support discussions tied to the specific order.