Solidgate’s sandbox testing capabilities, which encompass successful transactions, failures, fraud detection, and error modeling, are valuable for identifying potential issues and ensuring system stability.

By testing various payment methods such as card payments, Google Pay, Apple Pay, and PayPal, you can ensure interoperability and security, and prepare your integration for real-world scenarios.


Payment outcomes

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

  • Webhook keys, which start with the prefix wh_pk_ / wh_sk_ , allow for receiving simulated webhook notifications.
  • API keys, starting with api_pk_ / api_sk_ , are used to make API requests within the sandbox.

Test scenarios are available to simulate processing , success , and failed outcomes, which are crucial for assessing your system’s readiness and reliability across varied payment conditions.

CARD NUMBER 4067429974719265 TEST CARD
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
Card number varies depending on the payment scenario like success or decline.

Success

Success CARD NUMBER 4067429974719265 SUCCESS
auth success
settle success
recurring success
void success
refund success
Testing includes scenarios such as auth + settle , with certain limitations on timing and transaction status. Recurring success CARD NUMBER 4532456618142692 RECURRING
recurring success
An example of the recurring token card_token , which you can receive via the check order status API / updated card order Webhook notification after payment.

Declined

Auth CARD NUMBER 4553815318053315 AUTH FAILED
auth failed
settle success
recurring success
void success
refund success
This scenario tests placing a temporary hold on funds, ensuring they are available for final transaction confirmation. Steps include creating an order processing, attempting authorization, and verifying if it fails auth_failed. Settle CARD NUMBER 5361074849060618 SETTLE FAILED
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. Void CARD NUMBER 5361074849060618 VOID FAILED
auth success
settle failed
void failed
refund success
The customer 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. Recurring CARD NUMBER 4123212486997559 RECURRING FAILED
auth success
settle success
recurring failed
void success
refund success
Testing recurring payments involves executing an auth to receive a token used for a recurring operation. For recurring auth payments, perform the initial payment through auth , receive a token upon successful authorization, and use this token for a recurring payment with another authorization step. The recurring transaction transitions to the fail status, indicating the recurring setup failure, while the order transitions to the declined status. Refund CARD NUMBER 4476284533825961 REFUND FAILED
auth success
settle success
recurring 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.

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
0.01 CARD NUMBER 4510108818406882 ERROR 0.01 error : {code: 0.01 , message: "General decline"} 0.02 CARD NUMBER 4532003312475364 ERROR 0.02 error : {code: 0.02 , message: "Order expired"} 0.03 CARD NUMBER 4929213352238223 ERROR 0.03 error : {code: 0.03 , message: "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
2.06 CARD NUMBER 5299389115628964 ERROR 2.06 error : {code: 2.06 , message: "Invalid CVV2 code"} 2.08 CARD NUMBER 4539146503757117 ERROR 2.08 error : {code: 2.08 , message: "Invalid card number"} 2.09 CARD NUMBER 4945960509912296 ERROR 2.09 error : {code: 2.09 , message: "Invalid expiration date"} 2.10 CARD NUMBER 4857027008185133 ERROR 2.10 error : {code: 2.10 , message: "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
3.01 CARD NUMBER 5462413335551193 ERROR 3.01 error : {code: 3.01 , message: "Card is blocked"} 3.02 CARD NUMBERS 5151948477715326 4890838637940261 recurring ERROR 3.02 error : {code: 3.02 , message: "Insufficient funds"} 3.03 CARD NUMBER 4485664001324176 ERROR 3.03 error : {code: 3.03 , message: "Payment amount limit excess"} 3.04 CARD NUMBERS 5361250317309261 2490161849593101 recurring ERROR 3.04 error : {code: 3.04 , message: "Transaction is declined by issuer"} 3.05 CARD NUMBER 4916242642369774 ERROR 3.05 error : {code: 3.05 , message: "Call your bank"} 3.06 CARD NUMBER 5261820900437819 ERROR 3.06 error : {code: 3.06 , message: "Debit card not supported"} 3.07 CARD NUMBERS 4347225319309917 5134431550984251 recurring ERROR 3.07 error : {code: 3.07 , message: "Card brand is not supported"} 3.08 CARD NUMBER 4907428874384745 ERROR 3.08 error : {code: 3.08 , message: "Do not honor"} 3.10 CARD NUMBERS 4283184051091165 4423511615594071 recurring ERROR 3.10 error : {code: 3.10 , message: "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
4.02 CARD NUMBER 4983102885450335 ERROR 4.02 error : {code: 4.02 , message: "Stolen card"} 4.05 CARD NUMBER 4075752033922822 ERROR 4.05 error : {code: 4.05 , message: "PSP antifraud"} 4.07 CARD NUMBER 6011491463366455 ERROR 4.07 error : {code: 4.07 , message: "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
5.01 CARD NUMBER 5539974195624197 ERROR 5.01 error : {code: 5.01 , message: "3D secure verification failed"} 5.02 CARD NUMBER 4485589319980072 ERROR 5.02 error : {code: 5.02 , message: "Invalid card token"} 7.01 CARD NUMBER 5241981397484014 ERROR 7.01 error : {code: 7.01 , message: "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
5.03 CARD NUMBER 5414915934193648 ERROR 5.03 error : {code: 5.03 , message: "Application error"} 5.08 CARD NUMBER 5199914302370491 ERROR 5.08 error : {code: 5.08 , message: "Invalid transaction"} 6.02 CARD NUMBER 4935964870334207 ERROR 6.02 error : {code: 6.02 , message: "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.

4.04 CARD NUMBER 4222192107639022 ERROR 4.04 error : {code: 4.04 , message: "Lost card"}
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.

5.04 CARD NUMBER 5394262465415346 ERROR 5.04 error : {code: 5.04 , message: "Merchant is not configured correctly"}

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.

3DS CARD NUMBER 497592770594980 3DS
auth success
recurring success

Cards brands

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

VISA CARD NUMBER 4532456618142692 VISA
auth success
settle success
recurring success
void success
refund success
Testing this particular card brand is essential for ensuring smooth and secure transactions for customers, ultimately enhancing customer satisfaction and trust in the payment system. Mastercard CARD NUMBER 5329777445319300 MASTERCARD
auth success
settle success
recurring 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. Maestro CARD NUMBER 6763428189229070 MAESTRO
auth success
settle success
recurring success
void success
refund success
Ensuring Maestro card compatibility enhances global transaction reliability, essential for expanding market presence and strengthening consumer trust. JCB CARD NUMBER 3527602488193781 JCB
auth success
settle success
recurring success
void success
refund success
Testing JCB cards is essential for seamless global transactions, enhancing customer trust, and expanding market accessibility, ensuring broad compatibility and reliability. Discover CARD NUMBER 6011218207927015 DISCOVER
auth success
settle success
recurring success
void success
refund success
Assessing Discover card transactions ensures broad acceptance and seamless payment experiences, reinforcing confidence in payment infrastructure. UnionPay CARD NUMBER 6229261954246138 UNIONPAY
auth success
settle success
recurring success
void success
refund success
Testing UnionPay cards is vital for ensuring global financial inclusivity and transactional efficacy, fostering wider acceptance and customer convenience. Amex CARD NUMBER 371495481347626 AMEX
auth success
settle success
recurring 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. Diners CARD NUMBER 36527094796869 DINERS
auth success
settle success
recurring success
void success
refund success
Ensuring seamless transaction processing for Diners Club cards is essential to delivering exceptional service experiences and maintaining a loyal, high-value customer base.

Estimated and incremental auth

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

Success CARD NUMBER 4067429974719265 SUCCESS
auth estimated success
auth incremental success
Recurring success CARD NUMBER 4532456618142692 RECURRING
auth estimated success
auth incremental success
Error CARD NUMBER 4553815318053315 AUTH FAILED
auth estimated failed
auth incremental failed
CARD NUMBER 5140308911473822 INCREMENTAL FAILED
auth estimated success
auth incremental failed
3DS CARD NUMBER 497592770594980 3DS
auth estimated success

Mastercard CARD NUMBER 5329777445319300 MASTERCARD
auth estimated success
auth incremental success
Amex CARD NUMBER 371495481347626 AMEX
auth estimated success
auth incremental success
Diners CARD NUMBER 36527094796869 DINERS
auth estimated success
auth incremental success

Apple Pay or Google Pay

Sandbox provides a secure environment for simulating the integration of Google Pay and Apple Pay, without any risk to real bank accounts or transactions.

Before beginning tests, please contact us to discuss configuration needs. Keep in mind that Google Pay and Apple Pay digital wallets require real cards, and test cards do not work.

For the initial one-time payment, using an amount that is not listed below results in a standard approval. This ensures that all subsequent recurring payments using the same token are automatically approved. However, to trigger specific recurring or recurring auth payment outcomes, the initial transaction must use predefined amount values, which should be specified in cents. For example, an amount of 100 represents 1.00. Use the following values:

Using an amount different from the values listed above for the initial transaction ensures that subsequent recurring payments are always approved. This demonstrates the flexibility of the system in handling different transaction types.

Success AMOUNT 100 SUCCESS success without 3DS AMOUNT 666 SUCCESS success with 3DS AMOUNT 555 SUCCESS success with frictionless 3DS Error AMOUNT 1 ERROR 0.01 error : {code: 0.01 , message: "General decline"} AMOUNT 301 ERROR 3.01 error : {code: 3.01 , message: "Card is blocked"} AMOUNT 302 ERROR 3.02 error : {code: 3.02 , message: "Insufficient funds"} AMOUNT 3020 ERROR 3.02 error : {code: 3.02 , message: "Insufficient funds"} with frictionless 3DS AMOUNT 304 ERROR 3.04 error : {code: 3.04 , message: "Transaction is declined by issuer"} AMOUNT 308 ERROR 3.08 error : {code: 3.08 , message: "Do not honor"} AMOUNT 3080 ERROR 3.08 error : {code: 3.08 , message: "Do not honor"} with 3DS AMOUNT 310 ERROR 3.10 error : {code: 3.10 , message: "Suspected fraud"} AMOUNT 403 ERROR 4.03 error : {code: 4.03 , message: "Restricted card"} Processing AMOUNT 549 PROCESSING processing AMOUNT 649 PROCESSING processing with 3DS AMOUNT 749 PROCESSING processing with frictionless 3DS

PayPal

PayPal testing allows you to simulate failed transactions using a sandbox environment, which is useful for ensuring that your system correctly handles various scenarios, including negative flows.

Technical declines generated in the sandbox environment do not appear in PayPal's administrative dashboards.
  • Before you begin testing, ensure that your development environment is set up correctly.
  • To perform testing, contact us to request access to the PayPal sandbox account.

To test failed payments, set the API request with currency to USD and an amount, which should be specified in cents (for example, an amount of 302 means 3.02), to trigger errors.

Init payment AMOUNT 302 ERROR 3.02 error : {code: 3.02 , message: "Insufficient funds"} AMOUNT 305 ERROR 3.05 error : {code: 3.05 , message: "Call your bank"} AMOUNT 308 ERROR 3.08 error : {code: 3.08 , message: "Do not honor"} Recurring AMOUNT 301 ERROR 3.01 error : {code: 3.01 , message: "Card is blocked"} AMOUNT 302 ERROR 3.02 error : {code: 3.02 , message: "Insufficient funds"} AMOUNT 305 ERROR 3.05 error : {code: 3.05 , message: "Call your bank"} AMOUNT 308 ERROR 3.08 error : {code: 3.08 , message: "Do not honor"} AMOUNT 502 ERROR 5.02 error : {code: 5.02 , message: "Invalid card token"} AMOUNT 512 ERROR 5.12 error : {code: 5.12 , message: "Account is blocked"}

Alternative payments

Use APM sandbox scenarios to validate your integration behavior for method-specific input fields and expected outcomes.


Bizum

Bizum sandbox uses amount-based outcomes to simulate payment scenarios. Use the init payment API required fields with specific:

  • amount to match the success or error flow
  • customer_phone +34700000000
Success AMOUNT 400 SUCCESS success Amount should be less than 500. Error AMOUNT 700 ERROR 1.01 declined : {code: 1.01 , message: "Authentication failed"} Amount should be between 500 and 1000. AMOUNT 1200 ERROR 5.03 declined : {code: 5.03 , message: "Application error"} Amount should be between 1000 and 1500. AMOUNT 1600 ERROR 3.05 declined : {code: 3.05 , message: "Call your bank"} Amount should be greater than 1500.

Blik

Blik uses a 6-digit code to trigger specific outcomes. Use the init payment API required fields with specific:

  • amount to match the error flow
  • payment_type_data blik_code
Success BLIK CODE 777987 DIRECT success BLIK CODE 777123 REDIRECT success Error BLIK CODE 960111 PAYMENT DECLINED declined AMOUNT 31200 BLIK CODE 777567 TIMEOUT PAYMENT EXPIRED declined AMOUNT 12000 INSUFFICIENT FUNDS declined

Boleto

Boleto requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data brazil_cpf

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success CPF 52274278288 SUCCESS success Error CPF 213 630 678 26 INVALID CPF FORMAT declined Contains spaces CPF 052.161.533-0 INVALID CPF FORMAT declined Too short

Efecty

Effecty requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data colombia_cc

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success Cedula de Ciudadania 42141221 SUCCESS success

Mercado Pago

Mercado Pago requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data brazil_cpf

After a successful request:

  • follow pay_form return_url in the response to complete the payment flow
  • use your sandbox shopper credentials to complete the flow:
Success CPF 42141221 SUCCESS success

OXXO

OXXO requires a country-specific document field in payment_type_data. Use the test init payment API required fields with specific:

  • payment_type_data mexico_curp

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success CURP GAMS871004HNERRM56 SUCCESS success

Pix

Pix (SmartPix and PIX QR) requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data brazil_cpf
Success CPF 52274278288 SUCCESS success Error CPF 01063207185 ERROR 6.01 declined : {code: 6.01 , message: "Unknown decline code"} Validation error Missing customer first_name or last_name Missing billing_address country

Przelewy24

Przelewy24 is a Polish online bank transfer method supporting multiple banks, including BLIK as a sub-method. Use the init payment API to initiate a payment.

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success Select any bank on the sandbox page and approve the payment. SUCCESS success AMOUNT 1002 PENDING pending Error Validation currency not supported Currency other than PLN

PSE

PSE requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data colombia_cc

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success Cedula de Ciudadania 42141221 SUCCESS success

Sencillito

Sencillito requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data chile_ci

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success CI number (identity card) 5633554V SUCCESS success

Servipag

Servipag requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data chile_ci

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success CI number (identity card) 5633554V SUCCESS success

Webpay

Webpay requires a country-specific document field. Use the init payment API required fields with specific:

  • payment_type_data chile_ci

After a successful request, follow pay_form return_url in the response to complete the payment flow.

Success CI number (identity card) 5633554 SUCCESS success