Testing
Get started
Sign In
Testing
Simulate payments to test your integration before launching in production

To test your Solidgate integration, use your sandbox channel with specific keys:

  • Guide
    Learn to authenticate API requests and fix validation errors effectively.
    Webhook keys
    , which start with the prefix wh_pk_/wh_sk_ , allow for receiving simulated webhook notifications.
  • Guide
    Learn to authenticate API requests and fix validation errors effectively.
    API keys
    , starting with api_pk_/api_sk_ , are used to make API requests within our sandbox.

Test scenarios are available to simulate processing , success , and failure , which are crucial for assessing your system’s readiness and reliability across varied payment conditions. Use the following test credentials to test:

Card number The specific numbers to use vary depending on the scenario described below. 4067429974719265
Expiry date Any future date within the next 50 years is valid. 12/34
CVV/CVC Use any 3-digit code (or 4-digit for AMEX). 123
Cardholder Use any placeholder values. Name Surname

Success orders

Card number Operation Result
4067429974719265 charge success
recurring success
auth success
settle success
void success
refund success
Testing includes scenarios for a Guide
This process involves the merchant obtaining authorization to hold a Customer’s funds, Solidgate communicating with the acquirer to process the transaction, and the merchant settling the transaction.
2-step charge
( auth + settle ), with certain limitations on timing and transaction status.
Card number Operation Result
4532456618142692 charge success
recurring success
An example of the recurring token card_token , which you can receive via the check order status API / order status Webhook notification after payment.

Declined orders

Card number Operation Result
5251033622437578 charge failed
recurring success
auth failed
settle success
void success
refund success
The user attempts a direct payment, skipping pre-approval or authorization, leading to an immediate fund transfer. Test steps include creating an order in processing status, trying a payment, and checking if the order moves to declined status with a fail transaction.
Card number Operation Result
4553815318053315 charge success
recurring success
auth failed
settle success
void success
refund success
This scenario tests placing a temporary hold on funds, ensuring they're available for final transaction confirmation. Steps include creating an order processing, attempting authorization, and verifying if it fails auth_failed.
Card number Operation Result
5361074849060618 charge success
recurring success
auth success
settle failed
void failed
refund success
This scenario involves a merchant attempting to finalize a transaction by capturing previously authorized funds, transferring the amount from the customer's to the merchant's account. Steps include successful authorization auth_ok, settlement attempt, and verifying if the transaction settles or fails.
Card number Operation Result
5361074849060618 charge success
recurring success
auth success
settle failed
void failed
refund success
The user initiates an authorization to temporarily hold a specific amount on their card, ensuring funds are available but not immediately transferred. This allows for final confirmation before transaction completion. Testing involves creating an order in the processing status, attempting authorization, and checking if the order transitions to the auth_failed status, indicating a failed authorization attempt.
Card number Operation Result
4916400491851 charge success
recurring failed
auth success
settle success
void success
refund success
Establishing a recurring payment involves setting up a schedule for automatically charging the card at specified intervals for ongoing services or subscriptions. Test steps include executing an initial auth payment and successfully obtaining a token upon authorization. This token is then used for a recurring payment operation, with the transaction initially in the created status. The process is verified by ensuring the recurring transaction transitions to the fail status, indicating the recurring setup's failure, while the order transitions to the declined status if successful.
Card number Operation Result
4916400491851 charge success
recurring failed
auth success
settle success
void success
refund success
The user initiates a process for a recurring payment that starts with an authorization step. This ensures the merchant can verify the card and secure funds before setting up automatic charges at specified intervals for ongoing services or subscriptions. The testing process includes executing an initial payment through auth/charge, obtaining a token upon successful authorization, then using this token for a recurring payment with an additional authorization step, and finally verifying the outcome of the recurring-auth transaction.
Card number Operation Result
4476284533825961 charge success
recurring success
auth success
settle success
void success
refund failed
This scenario tests the refund process, intended to reverse a previously successful charge and return funds to the customer. The procedure involves confirming a successful payment settle_ok, initiating a refund, and validating the outcome. Successful refunds should transition the status to refunded, while failures maintain the original settle_ok status.

Card brand test

This section provides a list of test cards that can be used to verify the payment system.

Card number Operation Result
4532456618142692 charge success
recurring success
auth success
settle success
void success
refund success
Testing this particular card brand is essential for ensuring smooth and secure transactions for our customers, ultimately enhancing customer satisfaction and trust in our payment system.
Card number Operation Result
5329777445319300 charge success
recurring success
auth success
settle success
void success
refund success
Testing this particular card brand is crucial for ensuring compatibility and reliability in transactions, key to maintaining customer trust and minimizing transaction declines.
Card number Operation Result
6763428189229070 charge success
recurring success
auth success
settle success
void success
refund success
Ensuring Maestro card compatibility enhances global transaction reliability, essential for expanding market presence and strengthening consumer trust.
Card number Operation Result
3527602488193781 charge success
recurring success
auth success
settle success
void success
refund success
Testing JCB cards is essential for seamless global transactions, enhancing user trust, and expanding market accessibility, ensuring broad compatibility and reliability.
Card number Operation Result
6011218207927015 charge success
recurring success
auth success
settle success
void success
refund success
Assessing Discover card transactions ensures broad acceptance and seamless payment experiences, reinforcing confidence in payment infrastructure.
Card number Operation Result
6229261954246138 charge success
recurring success
auth success
settle success
void success
refund success
Testing UnionPay cards is vital for ensuring global financial inclusivity and transactional efficacy, fostering wider acceptance and customer convenience.
Card number Operation Result
371495481347626 charge success
recurring success
auth success
settle success
void success
refund success
Testing American Express cards is essential for guaranteeing high-end transaction security and enhancing premium service offerings, vital for customer satisfaction and retention.
Card number Operation Result
36527094796869 charge success
recurring success
auth success
settle success
void success
refund success
Ensuring the Diners Club card's seamless transaction processing is key to providing exclusive service experiences, crucial for retaining a discerning customer base.

Apple Pay or Google Pay

Our sandbox provides a secure environment for simulating the integration of Guide
Enable Google Pay button to give your customers more payment options.
Google Pay
and Guide
Optimize your payment form with Apple Pay integration, providing a secure and efficient checkout for Apple device users.
Apple Pay
, ensuring no risk to actual bank accounts or transactions.

Before beginning tests, please consult with your account manager regarding configuration needs. Note that Google Pay and Apple Pay digital wallets require the use of real cards; test cards will not work.

For initial one-time payment, using any amount not detailed below will result in standard approval, ensuring all subsequent recurring payments on that token are automatically approved. However, to initiate specific recurring or recurring auth payment outcomes, the first transaction (auth/sale) must utilize predefined amount values:

  • 100 for Guide
    3D Secure enhances online payment security by verifying cardholder identity, reducing fraud, and shifting liability from merchants to card issuers.
    no 3DS
    success
  • 666 for Guide
    Challenge flow in 3D Secure 2 requires cardholder interaction for authentication, triggered by high-risk scenarios or regulatory mandates.
    challenge
    success
  • 555 for Guide
    Frictionless flow in 3D Secure 2 authenticates transactions silently, requiring no input from the cardholder for low-risk payments.
    frictionless
    success

Employing an amount other than these specified values for the initial transaction ensures that subsequent recurring payments are invariably approved, demonstrating the system’s flexibility in handling various transaction types.

Amount

Result

100

success without 3DS

666

success with 3DS

555

success with frictionless 3DS

1

error : {code: 0.01, message: “ Guide
The general group of declines. The card issuing bank did not complete the transaction successfully.
General decline
“}

301

error : {code: 3.01, message: “ Guide
The card issuer bank blocked the card for payments.
Card is blocked
“}

302

error : {code: 3.02, message: “ Guide
The user’s card balance has insufficient funds.
Insufficient funds
“}

3020

error : {code: 3.02, message: “ Guide
The user’s card balance has insufficient funds.
Insufficient funds
“} with frictionless 3DS

304

error : {code: 3.04, message: “ 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.
Transaction is declined by issuer
”}

308

error : {code: 3.08, message: “ Guide
The card has been declined for an unknown reason.
Do not honor
”}

3080

error : {code: 3.08, message: “ Guide
The card has been declined for an unknown reason.
Do not honor
”} with 3DS

310

error : {code: 3.10, message: “ Guide
The issuing bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, etc.
Suspected Fraud
”}

403

error : {code: 4.03, message: “ Guide
The card is restricted, possibly due to being reported lost or stolen, or because of a restriction at the BIN or cardholder level preventing usage in certain countries, such as those subject to OFAC or embargo restrictions.
Restricted card
”}

Amount

Result

549

processing

649

processing with 3DS

749

processing with frictionless 3DS


Errors

To simulate payments that the issuer rejects for various reasons, use the test cards in this section. This can be useful to test the error-handling logic of your integration.


General decline

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

  • 0.01 Guide
    The general group of declines. The card issuing bank did not complete the transaction successfully.
    General decline
  • 0.02 Guide
    The user could not finalize the payment during the given timeframe, which resulted in order expiration.
    Order expired
  • 0.03 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.
    Illegal operation

Card number

Result

4929360879023

error : {code: 0.01, message: “ Guide
The general group of declines. The card issuing bank did not complete the transaction successfully.
General decline
”}

Card number

Result

4532003312475364

error : {code: 0.02, message: “ Guide
The user could not finalize the payment during the given timeframe, which resulted in order expiration.
Order expired
”}

Card number

Result

4929213352238223

error : {code: 0.03, message: “ 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.
Illegal operation
”}


Validation errors

These errors indicate that correcting the input data can typically resolve invalid transaction data.

Card number

Result

5299389115628964

error : {code: 2.06, message: “ 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.
Invalid CVV2 code
”}

Card number

Result

4539146503757117

error : {code: 2.08, message: “ Guide
The user entered an incorrect card number.
Invalid card number
”}

Card number

Result

4945960509912296

error : {code: 2.09, message: “ Guide
Card is expired.
Invalid Expiration Date
”}

Card number

Result

4857027008185133

error : {code: 2.10, message: “ Guide
3DS URL was not displayed to the cardholder during 3D Secure authentication attempts.
Invalid 3DS Flow on the Merchant Side
”}


Transaction declines

Transaction declines arise from factors like card limits, insufficient funds, or fraud concerns, often necessitating bank contact or alternative payment methods.

  • 3.01 Guide
    The card issuer bank blocked the card for payments.
    Card is blocked
  • 3.02 Guide
    The user’s card balance has insufficient funds.
    Insufficient funds
  • 3.03 Guide
    Card payment/credit limit was reached.
    Payment amount limit excess
  • 3.04 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.
    Transaction is declined by issuer
  • 3.05 Guide
    Contact card issuer for clarifications.
    Call your bank
  • 3.06 Guide
    The card has been declined for an unknown reason.
    Debit card not supported
  • 3.07 Guide
    The card has been declined for an unknown reason.
    Card brand is not supported
  • 3.08 Guide
    The card has been declined for an unknown reason.
    Do not honor
  • 3.10 Guide
    The issuing bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, etc.
    Suspected Fraud

Card number

Result

5462413335551193

error : {code: 3.01, message: “ Guide
The card issuer bank blocked the card for payments.
Card is blocked
”}

Card number

Result

5151948477715326

error : {code: 3.02, message: “ Guide
The user’s card balance has insufficient funds.
Insufficient funds
”}

Card number

Result

4485664001324176

error : {code: 3.03, message: “ Guide
Card payment/credit limit was reached.
Payment amount limit excess
”}

Card number

Result

5361250317309261

error : {code: 3.04, message: “ 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.
Transaction is declined by issuer
”}

Card number

Result

4916242642369774

error : {code: 3.05, message: “ Guide
Contact card issuer for clarifications.
Call your bank
”}

Card number

Result

5261820900437819

error : {code: 3.06, message: “ Guide
The card has been declined for an unknown reason.
Debit card not supported
”}

Card number

Result

5134431550984251

error : {code: 3.07, message: “ Guide
The card has been declined for an unknown reason.
Card brand is not supported
”} for recurrent transactions only

Card number

Result

4907428874384745

error : {code: 3.08, message: “ Guide
The card has been declined for an unknown reason.
Do not honor
”}

Card number

Result

4283184051091165

error : {code: 3.10, message: “ Guide
The issuing bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, etc.
Suspected Fraud
”}


Fraud and anti-fraud

These errors indicate transactions flagged for potential fraud due to blacklisted cards, stolen cards, or triggered antifraud rules, requiring merchants to display a general decline and conduct further investigation or recommend customers to try again.

  • 4.02 Guide
    The card in use is stolen, all transactions are restricted.
    Stolen card
  • 4.05 Guide
    The acquiring bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, etc.
    PSP antifraud
  • 4.07 Guide
    An antifraud rule was triggered.
    Trusted antifraud system

Card number

Result

4983102885450335

error : {code: 4.02, message: “ Guide
The card in use is stolen, all transactions are restricted.
Stolen card
”}

Card number

Result

4075752033922822

error : {code: 4.05, message: “ Guide
The acquiring bank blocked the transaction due to possible fraud. The card was not in use for a long time, unusual activity, etc.
PSP antifraud
”}

Card number

Result

6011491463366455

error : {code: 4.07, message: “ Guide
An antifraud rule was triggered.
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.

Card number

Result

5539974195624197

error : {code: 5.01, message: “ Guide
Understand why the payment is declined and how you can resolve it.
3D secure verification failed
”}

Card number

Result

4485589319980072

error : {code: 5.02, message: “ Guide
We received an invalid/nonexistent card token.
Invalid Card Token
”}

Card number

Result

5241981397484014

error : {code: 7.01, message: “ Guide
An error occurred and the token was not found.
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.

Card number

Result

5414915934193648

error : {code: 5.03, message: “ Guide
Processing error.
Application Error
”}

Card number

Result

5199914302370491

error : {code: 5.08, message: “ Guide
Processing error. The transaction is not authorized due to technical issues.
Invalid transaction
”}

Card number

Result

4935964870334207

error : {code: 6.02, message: “ Guide
A connection is poor or interrupted.
Connection error
”}


Card blocked or restricted

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

Card number

Result

4222192107639022

error : {code: 4.04, message: " Guide
The card in use is lost, all transactions are restricted.
Lost card
”}


Merchant configuration or activation errors

These errors are related to merchant configuration and API communication issues; resolution steps include contacting Solidgate support or ensuring proper API method usage.

Card number

Result

5394262465415346

error : {code: 5.04, message: “ Guide
Processing error.
Merchant is not configured correctly
”}