This page explains how to get started testing your integration. It lists the payment methods currently supported in our test environment and their flow type. For testing standard payment methods, such as credit cards, you'll find data you can use to test against success and error scenarios. You'll also find information on how to test redirect and receiver type payment methods.

Getting started

Always use your test API keys when testing. That way you never interact directly with the payments services. This ensures that the test data you enter does not create an actual charge or result in the transfer of funds.

When conducting testing in the Digital River API, use your confidential (secret) test API key. To create payment sources in DigitalRiver.js, use your public test API key.

The testing approach you use depends on whether the payment method has a flow type of standard, redirect, or receiver. If you don't know the type of the payment method you'd like to test, you can find it here.

Supported payment methods with flow type

The Digital River API supports a wide-range of payment methods. However, not all of these methods are currently supported in our testing environment. The following table indicates whether each payment method is supported or in progress.

The table also indicates the flow type. The three types (standard, redirect, and receiver) are tested using different approaches.

Testing standard payment methods

The payment methods with a standard flow type that Digital River currently supports in our testing environment are Credit Cards and Google Pay.

Credit cards

Before accepting live payments, you can use the card numbers in this section to test against success and error scenarios. These numbers are only valid in our testing environment. They do not create a real charge or result in a transfer of funds.

To conduct the testing, create a source in DigitalRiver.js, and use the appropriate data to set the parameters of the creditCard hash table.

Success scenarios

To test a successful payment, use the following basic credit card numbers. The expiration date must be at least one day in the future. With the exception of Visa, the security code can be any random three or four digit number.

You can also test how your integration handles different 3D Secure 2 authentication scenarios. To test your 3D Secure 2 integrations, use the the following test data.

When prompted for 3D Secure 2 text challenges, use these credentials:

Error scenarios

Use these test card numbers to test against specific error scenarios. For all the cards listed, the expiration date must be at least one day in the future and the security code can be any random three digit number.

Testing redirect payment methods

The following are the payment methods with a redirect flow type that Digital River currently supports in our testing environment: PayPal, Direct Debit, Klarna, and Alipay.

Success scenarios

For redirect payment sources, use the create source method in DigitalRiver.js to provide success scenario test data. Once you've done this, you should receive a Source in a pending_redirect state.

You'll then be directed to our generic authorization page that contains accept and reject options. Follow the redirect and select one of the following options:

Error scenarios

For redirect sources, first select one of the following payment methods. Then identify the error scenario you would like to test against. Finally, when creating a source using DigitalRiver.js, set the lastName parameter in the Owner object to the value that you expect to trigger the scenario.

Testing receiver payment methods

Wire Transfer is currently the only payment method with a receiver flow type that Digital River supports in our testing environment.

Success scenarios

For receiver type payment methods, use the create source method in DigitalRiver.js to provide success scenario test data. Once you've done this, you should receive a Source in a pending_funds state. The Source may then be used to complete your Checkout or Order.

Error scenarios

From the following table, first identify the error scenario you would like to test against. Then when creating a source using DigitalRiver.js, set the lastName parameter in the Owner object to the value that you expect to trigger the scenario.