Published test cards
Tests using production data must be authorized and coordinated with the acquirer.
Scenarios to cover
After each test, confirm
purchaseOperationNumber, purchaseAmount, authorizationResult, errorCode, errorMessage, and the returned signature.
Signature generation pattern
authorizationResult, and then the key. Compare both hashes securely before processing the result.
Move to production
- Integrations approved the test cases.
- The final HTTPS response URL was registered.
- Integration endpoint, credentials, and keys were replaced.
- Signature validation and idempotency remain enabled.
- A final transaction was coordinated with the acquirer.

