Help Center

Use sandbox test cards to trigger approvals, declines, 3DS challenges, and later operations. Click a card number to copy it.

Payment outcomes

Success

Declined

Errors

Use the test cards to simulate payments that the issuer rejects for various reasons. This can be useful for testing the error-handling logic of your integration.

Payment operations are handled asynchronously. The final result, including any decline, is delivered later through a webhook notification or via the check order status endpoint.

When testing decline scenarios with test cards, the decline code and final order status appear only in those asynchronous updates.

General decline

These errors reflect declined transactions from bank refusals, order time-outs, compliance issues, or authentication failures.

• 0.01 General decline
• 0.02 Order expired
• 0.03 Illegal operation

Validation errors

These errors indicate invalid transaction data that can typically be resolved by correcting the input.

• 2.06 Invalid CVV2 code
• 2.08 Invalid card number
• 2.09 Invalid expiration date
• 2.10 Invalid 3DS flow on merchant side

Transaction declines

Transaction refusal may be caused by factors such as card limits, insufficient balance, or suspected fraud, which often requires contacting the bank or using alternative payment methods.

• 3.01 Card is blocked
• 3.02 Insufficient funds
• 3.03 Payment amount limit excess
• 3.04 Transaction is declined by issuer
• 3.05 Call your bank
• 3.06 Debit card not supported
• 3.07 Card brand is not supported
• 3.08 Do not honor
• 3.10 Suspected fraud

Fraud and anti-fraud

These errors indicate that a transaction was flagged for potential fraud, often involving blocklisted or stolen cards or triggered antifraud rules. Merchants should display a general decline message and either investigate further or advise the customer to try again.

• 4.02 Stolen card
• 4.05 PSP antifraud
• 4.07 Trusted antifraud system

Data or card verification

These errors relate to address mismatches, failed 3D verification, and issues with card tokens, requiring merchants to verify customer information, check for fraud, and consult support as needed.

• 5.01 3D secure verification failed
• 5.02 Invalid card token
• 7.01 Card token not found

Connection or processing issues

These errors relate to transaction issues and connection errors. Solutions include retrying, using a different card, or contacting the bank.

• 5.03 Application error
• 5.08 Invalid transaction
• 6.02 Connection error

Card blocked or restricted

These errors refer to transactions blocked due to lost or restricted cards, requiring merchants to offer alternative payment options and check for potential fraud.

Merchant configuration or activation errors

These errors are related to merchant configuration and API communication issues. To resolve them, you can contact us for assistance but first ensure proper API method usage.

3D Secure authentication

Test the 3DS flow where the cardholder must complete additional authentication steps. This scenario simulates the full 3D Secure authentication process with cardholder verification.

Cards brands

Use a list of test cards to verify the payment system.

Estimated and incremental auth

Test estimated incremental authorization flows to ensure your integration handles authorization types correctly.

Reloadable prepaid indicator

The sandbox cards used for validating is_reloadable under reloadable prepaid indicator.