Testing Card Payments
Overview
Stitch's test client simulates deterministic card payment outcomes based on the exact transaction amount. Use the amounts below to verify how your integration handles successful, failed, and delayed payments before going live.
All examples use ZAR (R).
Test scenarios
| Amount | Status | Reason | Notes |
|---|---|---|---|
R1.01 | TransactionFailure | insufficientFunds | The payment is declined because the card has insufficient funds. |
R2.02 | TransactionFailure | exceedsCardWithdrawalLimit | The payment is declined because it exceeds the card's withdrawal limit. |
R3.03 | TransactionFailure | downstreamProviderError | The payment is declined because of a downstream provider error. |
R4.04 | TransactionFailure | authorizationFailed | The payment authorization fails. |
R5.05 | TransactionPending → TransactionSuccess | unknownExternalState while pending | The payment initially has an unknown external state and resolves successfully after approximately 10 seconds. |
| Any other amount | TransactionSuccess | - | The payment is captured successfully. |
note
The test scenarios require the exact amounts shown. For example, R1.01 returns insufficientFunds, while R10.01 follows the default success behavior.