Testing

Simulate payments to test your integration before launching in production

To test your integration with Solidgate, use our sandbox environment and the corresponding webhook keys and API.

Guide
Learn to authenticate API requests and fix validation errors effectively. Webhook keys have the prefix wh_pk_/wh_sk_
Guide
Learn to authenticate API requests and fix validation errors effectively. API keys have the prefix api_pk_/api_sk_

We provide test cards and parameters to simulate various payment scenarios, including successful or failures results.

By payment result

Solidgate for card payments allows merchants to securely integrate with a payment gateway to process and manage card transactions.

Success

Test Data	Result
card_number: 4067429974719265 card_exp_month: 12 card_exp_year: 2029 card_cvv: 945	charge: success recurring: success auth: success settle: success void: success refund: success
Note: Testing can include scenarios for a 2-step charge ( auto + settle ), with certain limitations on timing and transaction status.

card_number: 4067429974719265
card_exp_month: 12
card_exp_year: 2029
card_cvv: 945

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Note: Testing can include scenarios for a 2-step charge ( auto + settle ), with certain limitations on timing and transaction status.

Recurring success

Test Data	Result
card_number: 4532456618142692 card_exp_month: 03 card_exp_year: 2029 card_cvv: 967 card_token: card4532456618142692 card_bin: USA zip_code: 99801	charge: success recurring: success
Note: An example of the card_token (recurring token), which you can receive via the check order status API / order status Webhook notification after a successful / declined payment.

card_number: 4532456618142692
card_exp_month: 03
card_exp_year: 2029
card_cvv: 967
card_token: card4532456618142692
card_bin: USA
zip_code: 99801

charge: success

recurring: success

Note: An example of the card_token (recurring token), which you can receive via the check order status API / order status Webhook notification after a successful / declined payment.

Failed

Charge

Test Data	Result
card_number: 5251033622437578 card_exp_month: 09 card_exp_year: 2029 card_cvv: 847	charge: failed
The user tries to complete a payment directly, bypassing any pre-approval or authorization steps. This means the funds are transferred immediately without holding or reserving them first. Test logic: Create an order in the processing status. Attempt to execute a payment. Validate if the order transitions to the declined status (transaction pay in status fail ).

card_number: 5251033622437578
card_exp_month: 09
card_exp_year: 2029
card_cvv: 847

charge: failed

The user tries to complete a payment directly, bypassing any pre-approval or authorization steps. This means the funds are transferred immediately without holding or reserving them first.

Test logic:

Create an order in the processing status.
Attempt to execute a payment.
Validate if the order transitions to the declined status (transaction pay in status fail ).

Auth

Test Data	Result
card_number: 4553815318053315 card_exp_month: 06 card_exp_year: 2029 card_cvv: 809	charge: success auth: failed
The user tries to place a temporary hold on a specific amount of funds on their card. This authorization ensures the amount is available but not immediately transferred, allowing for final confirmation before completing the transaction. Test logic: Create an order in the processing status. Attempt to execute an authorization. Validate if the order transitions to the auth_failed status (transaction auth in status fail ).

card_number: 4553815318053315
card_exp_month: 06
card_exp_year: 2029
card_cvv: 809

charge: success

auth: failed

The user tries to place a temporary hold on a specific amount of funds on their card. This authorization ensures the amount is available but not immediately transferred, allowing for final confirmation before completing the transaction.

Test logic:

Create an order in the processing status.
Attempt to execute an authorization.
Validate if the order transitions to the auth_failed status (transaction auth in status fail ).

Settle

Test Data	Result
card_number: 4115399877827485 card_exp_month: 02 card_exp_year: 2029 card_cvv: 327	charge: success auth: success settle: failed
The merchant seeks to finalize the transaction by capturing the funds that were previously put on hold during the authorization process. This completes the payment and transfers the authorized amount from the customer's account to the merchant's account. Test logic: Make successful authorization request, placing the order in status auth_ok (transaction auth in status success ). Attempt to execute a settlement (settle transaction is in status created ). Validate if the settle transaction transitions to the fail status. Order in status auth_ok ; otherwise, it should transition to settle_ok .

card_number: 4115399877827485
card_exp_month: 02
card_exp_year: 2029
card_cvv: 327

charge: success

auth: success

settle: failed

The merchant seeks to finalize the transaction by capturing the funds that were previously put on hold during the authorization process. This completes the payment and transfers the authorized amount from the customer's account to the merchant's account.

Test logic:

Make successful authorization request, placing the order in status auth_ok (transaction auth in status success ).
Attempt to execute a settlement (settle transaction is in status created ).
Validate if the settle transaction transitions to the fail status. Order in status auth_ok ; otherwise, it should transition to settle_ok .

Void

Test Data	Result
card_number: 5361074849060618 card_exp_month: 01 card_exp_year: 2029 card_cvv: 111	charge: success auth: success settle: failed void: failed
The merchant initiates a void transaction to cancel the funds that were previously authorized, effectively releasing the hold on the customer's account without completing the charge. Test logic: Create an order in the auth_ok status (transaction auth in status success ). Execute a void operation on the authorized funds (void transaction is initially in the created status). Validate if the void transaction transitions to the fail status. If it does, confirm the order remains in auth_ok status; otherwise, it should transition to void_ok .

card_number: 5361074849060618
card_exp_month: 01
card_exp_year: 2029
card_cvv: 111

charge: success

auth: success

settle: failed

void: failed

The merchant initiates a void transaction to cancel the funds that were previously authorized, effectively releasing the hold on the customer's account without completing the charge.

Test logic:

Create an order in the auth_ok status (transaction auth in status success ).
Execute a void operation on the authorized funds (void transaction is initially in the created status).
Validate if the void transaction transitions to the fail status. If it does, confirm the order remains in auth_ok status; otherwise, it should transition to void_ok .

Recurring

Test Data	Result
card_number: 4916400491851 card_exp_month: 09 card_exp_year: 2029 card_cvv: 492 card_token: card4916400491851 card_bin: USA zip_code: 99801	charge: success recurring: failed
The user initiates a process to establish a recurring payment schedule, allowing the merchant to automatically charge their card at specified intervals for ongoing services or subscriptions. Test logic: Execute the first payment using auth and successfully authorize it; upon successful authorization, obtain a token (order in auth_ok status, and transaction auth in success status). Use the token to execute a recurring payment operation (order transitions to the processing status, and the recurring transaction is initially in the created status). Validate if the recurring transaction transitions to the fail status; otherwise, the order transitions to the declined status.

card_number: 4916400491851
card_exp_month: 09
card_exp_year: 2029
card_cvv: 492
card_token: card4916400491851
card_bin: USA
zip_code: 99801

charge: success

recurring: failed

The user initiates a process to establish a recurring payment schedule, allowing the merchant to automatically charge their card at specified intervals for ongoing services or subscriptions.

Test logic:

Execute the first payment using auth and successfully authorize it; upon successful authorization, obtain a token (order in auth_ok status, and transaction auth in success status).
Use the token to execute a recurring payment operation (order transitions to the processing status, and the recurring transaction is initially in the created status).
Validate if the recurring transaction transitions to the fail status; otherwise, the order transitions to the declined status.

Recurring Auth

Test Data	Result
card_number: 4916400491851 card_exp_month: 09 card_exp_year: 2029 card_cvv: 492 card_token: card4916400491851 card_bin: USA zip_code: 99801	charge: success recurring: failed
The user initiates a process for recurring payment that starts with an authorization step. This allows the merchant to verify the user's card and secure funds before automatically charging the card at specified intervals for ongoing services or subscriptions. Test logic: Execute the first payment using auth/charge and successfully authorize it; upon successful authorization, obtain a token (order in auth_ok status, and transaction auth in success status). Use the token to execute a recurring payment with an additional authorization step (type auth ) (order transitions to the processing status, and the recurring-auth transaction is initially in the created status). Validate if the recurring-auth transaction transitions to the fail status; otherwise the order transitions to the auth_failed status.

card_number: 4916400491851
card_exp_month: 09
card_exp_year: 2029
card_cvv: 492
card_token: card4916400491851
card_bin: USA
zip_code: 99801

charge: success

recurring: failed

The user initiates a process for recurring payment that starts with an authorization step. This allows the merchant to verify the user's card and secure funds before automatically charging the card at specified intervals for ongoing services or subscriptions.

Test logic:

Execute the first payment using auth/charge and successfully authorize it; upon successful authorization, obtain a token (order in auth_ok status, and transaction auth in success status).
Use the token to execute a recurring payment with an additional authorization step (type auth ) (order transitions to the processing status, and the recurring-auth transaction is initially in the created status).
Validate if the recurring-auth transaction transitions to the fail status; otherwise the order transitions to the auth_failed status.

Refund

Test Data	Result
card_number: 4476284533825961 card_exp_month: 12 card_exp_year: 2030 card_cvv: 725	charge: success refund: failed
The merchant initiates a refund procedure after confirming a successful payment transaction. This involves reversing the earlier charge and returning the funds to the customer's card or account. Test logic: Create an order and successfully process a payment (order should be in the settle_ok status, and both the auth and settle transactions should be in the success status). Initiate a refund operation (refund transaction starts in the created status). Validate if the refund transaction transitions to the fail status. If it does, confirm that the order remains in the settle_ok status; otherwise, it should transition to refunded .

card_number: 4476284533825961
card_exp_month: 12
card_exp_year: 2030
card_cvv: 725

charge: success

refund: failed

The merchant initiates a refund procedure after confirming a successful payment transaction. This involves reversing the earlier charge and returning the funds to the customer's card or account.

Test logic:

Create an order and successfully process a payment (order should be in the settle_ok status, and both the auth and settle transactions should be in the success status).
Initiate a refund operation (refund transaction starts in the created status).
Validate if the refund transaction transitions to the fail status. If it does, confirm that the order remains in the settle_ok status; otherwise, it should transition to refunded .

By card brand

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

VISA

Test Data	Result
card_number: 4532456618142692 card_exp_month: 03 card_exp_year: 2029 card_cvv: 967	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 4532456618142692
card_exp_month: 03
card_exp_year: 2029
card_cvv: 967

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

MasterCard

Test Data	Result
card_number: 5329777445319300 card_exp_month: 12 card_exp_year: 2029 card_cvv: 312	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 5329777445319300
card_exp_month: 12
card_exp_year: 2029
card_cvv: 312

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Maestro

Test Data	Result
card_number: 6763428189229070 card_exp_month: 11 card_exp_year: 2029 card_cvv: 111	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 6763428189229070
card_exp_month: 11
card_exp_year: 2029
card_cvv: 111

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

JCB

Test Data	Result
card_number: 3527602488193781 card_exp_month: 06 card_exp_year: 2029 card_cvv: 268	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 3527602488193781
card_exp_month: 06
card_exp_year: 2029
card_cvv: 268

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Discover

Test Data	Result
card_number: 6011218207927015 card_exp_month: 06 card_exp_year: 2029 card_cvv: 567	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 6011218207927015
card_exp_month: 06
card_exp_year: 2029
card_cvv: 567

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Amex

Test Data	Result
card_number: 371495481347626 card_exp_month: 11 card_exp_year: 2030 card_cvv: 4831	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 371495481347626
card_exp_month: 11
card_exp_year: 2030
card_cvv: 4831

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Diners

Test Data	Result
card_number: 36527094796869 card_exp_month: 12 card_exp_year: 2030 card_cvv: 546	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 36527094796869
card_exp_month: 12
card_exp_year: 2030
card_cvv: 546

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

UnionPay

Test Data	Result
card_number: 6229261954246138 card_exp_month: 04 card_exp_year: 2029 card_cvv: 324	charge: success recurring: success auth: success settle: success void: success refund: success

card_number: 6229261954246138
card_exp_month: 04
card_exp_year: 2029
card_cvv: 324

charge: success

recurring: success

auth: success

settle: success

void: success

refund: success

Card 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.

Card blocked or restricted

Data or card verification issues

Connection or processing issues

Merchant configuration or activation errors

General decline

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

General decline

Test Data	Result
card_number: 4929360879023 card_exp_month: 07 card_exp_year: 2029 card_cvv: 519 card_bin: UNITED KINGDOM zip_code: 99801	error: {code: 0.01, message: “ Guide The general group of declines. The card issuing bank did not complete the transaction successfully. General decline ”}

Order expired

Test Data	Result
card_number: 4532003312475364 card_exp_month: 05 card_exp_year: 2029 card_cvv: 957 card_bin: SPAIN	error: {code: 0.02, message: “ Guide The user could not finalize the payment during the given timeframe, which resulted in order expiration. Order expired ”}

Illegal operation

Test Data	Result
card_number: 4929213352238223 card_exp_month: 06 card_exp_year: 2029 card_cvv: 204 card_bin: UNITED KINGDOM	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 invalid transaction data can typically be resolved by correcting the input data.

Invalid CVV2 code

Test Data	Result
card_number: 5262030475142781 card_exp_month: 10 card_exp_year: 2027 card_cvv: 912	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 ”}

Invalid card number

Test Data	Result
card_number: 4539146503757117 card_exp_month: 02 card_exp_year: 2029 card_cvv: 661 card_cvv: PHILIPPINES	error: {code: 2.08, message: “ Guide The user entered an incorrect card number. Invalid card number ”}

Invalid expiration date

Test Data	Result
card_number: 4945960509912296 card_exp_month: 01 card_exp_year: 2029 card_cvv: 420 card_bin: USA zip_code: 99801	error: {code: 2.09, message: “ Guide Card is expired. Invalid Expiration Date ”}

Invalid 3DS flow on the merchant side

Test Data	Result
card_number: 4857027008185133 card_exp_month: 09 card_exp_year: 2029 card_cvv: 478 card_cvv: GERMANY	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.

Card is blocked

Test Data	Result
card_number: 5462413335551193 card_exp_month: 07 card_exp_year: 2029 card_cvv: 369 card_bin: USA zip_code: 99801	error: {code: 3.01, message: “ Guide The card issuer bank blocked the card for payments. Card is blocked ”}

Insufficient funds

Test Data	Result
card_number: 5151948477715326 card_exp_month: 10 card_exp_year: 2029 card_cvv: 100 card_bin: USA zip_code: 99801	error: {code: 3.02, message: “ Guide The user’s card balance has insufficient funds. Insufficient funds ”}

Payment amount limit excess

Test Data	Result
card_number: 4485664001324176 card_exp_month: 08 card_exp_year: 2029 card_cvv: 383 card_bin: USA zip_code: 99801	error: {code: 3.03, message: “ Guide Card payment/credit limit was reached. Payment amount limit excess ”}

The transaction is declined by issuer

Test Data	Result
card_number: 5361250317309261 card_exp_month: 09 card_exp_year: 2029 card_cvv: 629 card_bin: REPUBLIC OF KOREA	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 ”}

Call your bank

Test Data	Result
card_number: 4916242642369774 card_exp_month: 04 card_exp_year: 2029 card_cvv: 595 card_bin: UNITED KINGDOM	error: {code: 3.05, message: “ Guide Contact card issuer for clarifications. Call your bank ”}

Debit card not supported

Test Data	Result
card_number: 5261820900437819 card_exp_month: 01 card_exp_year: 2029 card_cvv: 272 card_bin: USA zip_code: 99801	error: {code: 3.06, message: “ Guide The card has been declined for an unknown reason. Debit card not supported ”}

Card brand is not supported

Test Data	Result
card_number: 5134431550984251 card_exp_month: 05 card_exp_year: 2029 card_cvv: 584 card_bin: USA zip_code: 99801	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: 5134431550984251
card_exp_month: 05
card_exp_year: 2029
card_cvv: 584
card_bin: USA
zip_code: 99801

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

For recurrent transactions only.

Do not honor

Test Data	Result
card_number: 4907428874384745 card_exp_month: 10 card_exp_year: 2029 card_cvv: 123 card_bin: GERMANY	error: {code: 3.08, message: “ Guide The card has been declined for an unknown reason. Do not honor ”}

Suspected fraud

Test Data	Result
card_number: 4283184051091165 card_exp_month: 08 card_exp_year: 2028 card_cvv: 058 card_bin: AUSTRALIA	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.

Stolen card

Test Data	Result
card_number: 4983102885450335 card_exp_month: 01 card_exp_year: 2029 card_cvv: 111 card_bin: FRANCE	error: {code: 4.02, message: “ Guide The card in use is stolen, all transactions are restricted. Stolen card ”}

PSP antifraud

Test Data	Result
card_number: 4075752033922822 card_exp_month: 01 card_exp_year: 2029 card_cvv: 312	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 ”}

Trusted antifraud system

Test Data	Result
card_number: 6011491463366455 card_exp_month: 12 card_exp_year: 2029 card_cvv: 361	error: {code: 4.07, message: “ Guide An antifraud rule was triggered. Trusted antifraud system ”}

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.

Lost card

Test Data	Result
card_number: 4222192107639022 card_exp_month: 08 card_exp_year: 2029 card_cvv: 759 card_bin: GERMANY	error: {code: 4.04, message: " Guide The card in use is lost, all transactions are restricted. Lost card ”}

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.

3D secure verification failed

Test data	Result
card_number: 5539974195624197 card_exp_month: 07 card_exp_year: 2029 card_cvv: 472 card_bin: SPAIN	error: {code: 5.01, message: “ Guide Understand why the payment is declined and how you can resolve it. 3D secure verification failed ”}

Invalid card token

Test Data	Result
card_number: 4485589319980072 card_exp_month: 11 card_exp_year: 2029 card_cvv: 351	error: {code: 5.02, message: “ Guide We received an invalid/nonexistent card token. Invalid Card Token ”}

Card token not found

Test Data	Result
card_number: 5241981397484014 card_exp_month: 04 card_exp_year: 2029 card_cvv: 233	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.

Application error

Test Data	Result
card_number: 5414915934193648 card_exp_month: 07 card_exp_year: 2029 card_cvv: 986	error: {code: 5.03, message: “ Guide Processing error. Application Error ”}

Invalid transaction

Test data	Result
card_number: 5199914302370491 card_exp_month: 01 card_exp_year: 2029 card_cvv: 820 card_bin: USA zip_code: 99801	error: {code: 5.08, message: “ Guide Processing error. The transaction is not authorized due to technical issues. Invalid transaction ”}

Connection error

Test data	Result
card_number: 4935964870334207 card_exp_month: 04 card_exp_year: 2029 card_cvv: 336	error: {code: 6.02, message: “ Guide A connection is poor or interrupted. Connection error ”}

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.

Merchant is not configured correctly

Test Data	Result
card_number: 5394262465415346 card_exp_month: 02 card_exp_year: 2029 card_cvv: 937	error: {code: 5.04, message: “ Guide Processing error. Merchant is not configured correctly ”}

Related articles FAQ

Tickets management