What to check
Check the environment address, credential environment, partnership review and production product permissions separately. Document successful and failed responses using test data.
Common pitfalls
Do not present test cards or simulated balances as spendable assets, or place credentials in public frontend code.
The next step
Before production use, complete the documented approval and acceptance process, including callbacks, exception handling and reconciliation responsibilities.
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.