Prerequisites

Enable the CyberSource payment gateway integration for your tenant. See Enable payment gateway integrations for your tenant for instructions.

Test your configuration

For basic guidance on how to test payment gateway integrations within a sandbox environment, see Test payment gateway integration .

Access your gateway test environment

Some payment gateways provide separate credentials for merchants to access their testing environment, some gateways use the same credentials for testing as for the production (live) environment but direct test transactions to a different URL, and other gateways do a little of both. CyberSource uses the same credentials for test and live transactions, however, you have to make sure your account is in test mode for testing and live mode for production.

Initial CyberSource Account is in Test Mode

When your company signs up with CyberSource, your account is initially set up in test mode only and enabled for live mode shortly after.

Access Test or Live Mode from the CyberSource Business Center

View CyberSource support documentation to understand the difference between test and live modes .

You should perform all testing in Test mode before going to Live Mode. After you have gone live, you can still access the testing environment from your Business Center at: https://ebctest.cybersource.com . From the Business Center, you can view all your transactions.

Access Test or Live Mode from Zuora

When configuring the CyberSource payment gateway in Zuora, you can indicate whether you would like to use the CyberSource test environment or the CyberSource (Live) environment.

• If you select Use Gateway Test Environment , Zuora will direct payment transactions to your CyberSource account in test mode.

• If you do not select Use Gateway Test Environment , Zuora will direct payment transactions to your CyberSource account in live mode.

Test credit cards and testing scenarios

See the following documentation for test payment methods and general testing information:

• Testing Guide

• Testing CyberSource ACH service transactions

General testing information

Integration testing

Performance and volume testing

In general, gateway testing environments are intended to give merchants the opportunity to test their gateway and integrations to their gateway, in order to work out any bugs before going to the production environment. Some gateway test environments are shared amongst multiple merchants, and other gateways provide unique testing environments for each merchant. Additionally, gateway test environments (also referred to as certification or sandbox environments) do not have the same high availability or performance capability as production environments. As such, they are not intended for load testing. Merchants performing high volumes of load testing that puts a stress on a shared test environment may receive a warning from the gateway or have their access to the testing environment suspended.

Upgrade to P12 Authentication

Upgrading to P12 Authentication requires you to replace username and password-based authentication from your SOAP toolkit integration and transition to certificate-based authentication.

To upgrade to a compliant P12 certificate, you must populate the Cybersource Transaction Security Key and Cybersource Transaction Security Key Password in each active gateway instance in Zuora. See Configuration fields .

To retrieve the values of the Cybersource Transaction Security Key and Cybersource Transaction Security Key Password fields, see Create a .p12 File .

Related information

Overview of CyberSource payment gateway integration