Card payments

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.

• Guide
  The general group of declines. The card-issuing bank did not complete the transaction successfully. 0.01 General decline
• Guide
  The customer could not finalize the payment during the given timeframe, which resulted in order expiration. 0.02 Order expired
• Guide
  In some cases, the card issuer can block a transaction for law violation reasons. It can be due to a cardholder or due to a sanctioned country. 0.03 Illegal operation

Validation errors

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

• Guide
  The CVV code is the three-digit code on the back of a Mastercard or Visa, or the four-digit code on the front of an American Express. 2.06 Invalid CVV2 code
• Guide
  This decline indicates that the entered card number is not correct and the customer’s account cannot be found. 2.08 Invalid card number
• Guide
  This error occurs when the entered or stored card expiration date is invalid or has already passed. 2.09 Invalid expiration date
• Guide
  3DS URL was not displayed to the cardholder during 3D Secure authentication attempts. 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.

• Guide
  The card issuer bank blocked the card for payments. 3.01 Card is blocked
• Guide
  The customer’s card balance has insufficient funds. 3.02 Insufficient funds
• Guide
  The transaction was declined because the card payment or credit limit was exceeded. 3.03 Payment amount limit excess
• Guide
  The transaction has been declined by the card issuer. Reasons for decline can vary, including limits on online payments, daily payment amounts, or daily transaction counts. 3.04 Transaction is declined by issuer
• Guide
  The card issuer has blocked the transaction for reasons that need to be clarified. 3.05 Call your bank
• Guide
  The transaction was declined because debit cards are not supported. 3.06 Debit card not supported
• Guide
  The transaction was declined because the card’s brand is not supported. 3.07 Card brand is not supported
• Guide
  A general decline response indicating that the card issuer has rejected the transaction without providing a specific reason code. 3.08 Do not honor
• Guide
  The issuing bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, and other reasons. 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.

• Guide
  The card in use is stolen, all transactions are restricted. 4.02 Stolen card
• Guide
  The acquiring bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, and other reasons. 4.05 PSP antifraud
• Guide
  The transaction was declined after triggering an antifraud rule. 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.

• Guide
  Use the payment error code reference to identify decline reasons, understand issuer responses, and decide on retry or resolution steps. 5.01 3D secure verification failed
• Guide
  Receive this error when you received an invalid/nonexistent card token. 5.02 Invalid card token
• Guide
  This error indicates that the card token is missing or inaccessible. 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.

• Guide
  An error occurred during transaction processing due to technical issues on the server side. 5.03 Application error
• Guide
  Processing error. The transaction is not authorized due to technical issues. 5.08 Invalid transaction
• Guide
  There is a connection issue, possibly due to poor or interrupted connectivity. 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 Guide
Challenge flow in 3D Secure requires cardholder interaction for authentication, triggered by high-risk scenarios or regulatory mandates. 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 Guide
Submit estimated authorizations and request incremental amount increases for variable-total transactions like travel and hospitality. estimated incremental authorization flows to ensure your integration handles authorization types correctly.

Reloadable prepaid indicator

The sandbox cards used for validating is_reloadable under Guide
Follow card payment orders through each processing stage with clear status definitions, available actions, and real-time event tracking. reloadable prepaid indicator.