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.

Card payments

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 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:

Success orders

Declined orders

Card brand test

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

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.

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 customer 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

Validation errors

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

• 2.06 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
• 2.08 Guide
  This decline indicates that the entered card number is not correct and the customer’s account cannot be found. Invalid card number
• 2.09 Guide
  This error occurs when the entered or stored card expiration date is invalid or has already passed. Invalid expiration date
• 2.10 Guide
  3DS URL was not displayed to the cardholder during 3D Secure authentication attempts. Invalid 3DS flow on the 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 Guide
  The card issuer bank blocked the card for payments. Card is blocked
• 3.02 Guide
  The customer’s card balance has insufficient funds. Insufficient funds
• 3.03 Guide
  The transaction was declined because the card payment or credit limit was exceeded. 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
  The card issuer has blocked the transaction for reasons that need to be clarified. Call your bank
• 3.06 Guide
  The transaction was declined because debit cards are not supported. Debit card not supported
• 3.07 Guide
  The transaction was declined because the card’s brand is not supported. Card brand is not supported
• 3.08 Guide
  A general decline response indicating that the card issuer has rejected the transaction without providing a specific reason code. 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, and other reasons. 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 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, and other reasons. PSP antifraud
• 4.07 Guide
  The transaction was declined after triggering an antifraud rule. 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 Guide
  Understand why the payment is declined and how you can resolve it. 3D secure verification failed
• 5.02 Guide
  Receive this error when you received an invalid/nonexistent card token. Invalid card token
• 7.01 Guide
  This error indicates that the card token is missing or inaccessible. 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 Guide
  An error occurred during transaction processing due to technical issues on the server side. Application error
• 5.08 Guide
  Processing error. The transaction is not authorized due to technical issues. Invalid transaction
• 6.02 Guide
  There is a connection issue, possibly due to poor or interrupted connectivity. 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. The resolution steps include contacting the Solidgate support or ensuring proper API method usage.

Apple Pay or Google Pay

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 customers. Apple Pay, ensuring no risk to actual bank accounts or transactions.

For the initial one-time payment, using any amount not detailed below result in a standard approval, ensuring all subsequent recurring payments on that token are automatically approved. However, to initiate a specific recurring or recurring auth payment outcomes, the initial transaction must have predefined amount values, which should be specified in cents, for example, amount 100 means 1:

• 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

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

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.

• Before you begin testing, ensure that your development environment is set up correctly.
• To perform testing, request access to the PayPal sandbox account from your account manager.

To test failed payments, set the API request with currency to USD and a specific amount, which should be specified in cents like amount 302 means 3.02, to trigger errors.