Accounts for API Testing

The test accounts listed below can be used to test API functionality in the sandbox environment. The sandbox is an entirely separate environment from the production environment.

Related information: Tender Types, Bin Ranges.

Credit Card Authorization

The following card numbers may be used to trigger specific credit card authorization responses:

Approved Response

Declined Response

AVS/CSC Response

Processor Timeout Response

Private Label Credit Card Authorization

The following card numbers may be used to trigger specific private label credit card authorization responses:

Approved Response

Declined Response

Processor Timeout Response

Validate Card

The following card numbers may be used to trigger specific validate card responses:

Valid Response

Invalid Response

Timeout Response

Terms and Conditions

The following card numbers may be used to trigger specific terms and conditions responses:

Success Response

Fail Response

Timeout Response

Gift Card Balance Inquiry

A gift card is a prepaid payment that is issued with a set amount, which eventually gets exhausted.
The test cards below are fixed amount gift cards and will never have a zero balance unless stated otherwise.

Success Response

Fail Response

Timeout Response

PayPal

A Custom Sandbox Account is required for testing. Merchants should create a Personal (buyer account) Custom Sandbox Account to ensure testing is done correctly. Please note that Radial does not support mock test data for PayPal.

PayPal provides rejection trigger codes that can be used during sandbox testing to simulate failures. To test these scenarios, enter the appropriate trigger code in the “First Name” or “Name on Card” field when adding a card. Please visit the official PayPal documentation: Card Testing and scroll to the "Simulate card error scenarios" section to view the full list of available rejection trigger codes and their corresponding simulated error responses.

PayPal Sandbox Testing Steps:

1. Initiate a Test Transaction: Begin by placing an order using the PayPal payment method within your sandbox environment.

2. Log In to Your Sandbox PayPal Account When redirected to the PayPal login page, sign in using your Personal (buyer account) Custom Sandbox Account credentials.

3. Add a New Card: On the "Review Order" page, click "Add Card" to enter new payment details.

4. Enter Rejection Trigger: In the “First Name” or “Name on Card” field, enter one of the rejection trigger codes provided in the PayPal documentation (e.g., CCREJECT-REFUSED). This will simulate a specific error response during testing.

Please refer to the official PayPal documentation: Card Testing and navigate to the "Simulate card error scenarios" section to view the full list of available rejection trigger codes and their corresponding simulated error responses.

Note: These codes are case-sensitive and must be entered exactly as shown to work correctly.

5. Complete Card Details: Fill in the remaining required card details. You can generate random test card number, expiration date, and CVV code using this link Card Testing (navigate to "Credit card generator" section).

6. Save the Card: Click "Save" to add the card information to your PayPal account.

7. Place the Order: Complete the transaction by placing the order using the saved card.

Note: Radial will return a standard failure response during the authorization creation. No additional error details will be provided, regardless of which rejection trigger code is used.

Google Pay

Webstore PAN_ONLY Testing

• Add your email to access test suite cards by following these instructions.

• This will enable non-tokenized test cards access for web testing, .

• Some of the tests cards may still get routed as standard 4111 visa card.

InApp CRYPTOGRAM_3DS testing

• Remove your email from test suite access.

• This will enable the users to add other cards to their GooglePay profile.

• Add tokenized test cards for in-app device based testing only.

• Any other cards added may still get routed as standard 4111 visa card.

Note: The actual cards may not be used when routing to card authorizer, instead DPAN (Device Pan) may be generated. This card number is different than the actual card. This card may not work for e2e testing and may still get declined in the test environment. Share your failed order number details to DL-PTF Services <PTFServices@radial.com> with copy to Radial account manager. They will identify associated DPAN and set that as a mock for you to continue the testing. Please further note that same card, when added to a different device, may generate a different DPAN, and you would have to work with Radial to set the mock again.

Apple Pay

Apple provides a list of current test cards that you can use for ApplePay testing.

Note: The actual cards may not be used when routing to card authorizer, instead DPAN (Device Pan) may be generated. This card number is different than the actual card. This card may not work for e2e testing and may still get declined in the test environment. Share your failed order number details to DL-PTF Services <PTFServices@radial.com> with copy to Radial account manager. They will identify associated DPAN and set that as a mock for you to continue the testing. Please further note that same card, when added to a different device, may generate a different DPAN, and you would have to work with Radial to set the mock again.

Klarna JavaScript Integration

For testing, the sample data for different regions are listed by Klarna on this web page: Klarna Test Sample Data.

Ajax Tokenization and 3DS

There are test cards for testing Radial's JavaScript APIs for Ajax tokenization and 3DS. For details, see Testing JavaScript API Integration.