Accessing your gateway's test environment

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

• If Use Gateway Test Environment is selected, Zuora will direct payment transactions to the following test environment which is a test simulator at https://pilot-payflowpro.paypal.com (This URL is the API entry point for a test environment dedicated to PayFlow)

• If Use Gateway Test Environment is not selected (disabled), Zuora will direct payment transactions to the following production environment: https://payflowpro.paypal.com (API entry point).

  Note: Your credentials will be the same for both test and production environments, which both requires Payflow credentials. Zuora ensures your payment transactions are routed to the right environment based on whether the Use Gateway Test Environment is selected. The UI entry point for https://pilot-payflowpro.paypal.com and https://payflowpro.paypal.com is at https://manager.paypal.com .

Test credit cards and testing scenarios

When testing transactions through the Zuora integration of Payflow Pro, Website Payments Pro Payflow Edition, and Website Payments Pro integrations, you should refer to the following developer's guides for more information:

• Payflow Pro Developer's Guide (see Chapter on "Credit Card Testing")

• Payflow Gateway Developer Guide (see Chapter on "Testing Transactions")

The integration uses the https://pilot-payflowpro.paypal.com simulator for testing, thus we refer you to the instructions in the Payflow guides. The developer's guides include information on generating payment errors based on the transaction amount used for testing. If you use a different credit card number for testing that is not listed in the developer's guide, it may also fail the transaction.

Test credit cards and test scenarios will depend on the Sandbox ssed

If you are using the https://pilot-payflowpro.paypal.com (Payflow Sandbox) for testing, you should follow the instructions in the Payflow Pro Developer's Guide . The Payflow Sandbox uses specific credit card numbers and generating transaction results and responses are handled differerently than with the PayPal Sandbox Sandbox.

By default, any merchant testing transactions via Zuora will be using the https://pilot-payflowpro.paypal.com test simulator.

If you are using the https://www.sandbox.paypal.com (PayPal Sandbox) account for testing through Zuora, you should following the steps in the Sandbox User Guide for adding a credit card account.

The PayPal Sandbox does not have a list of specific credit cards to use, however, these are your options:

• You can follow the instructions to add a credit card account to a test account.

• You can generate credit card numbers in sandbox.paypal.com.

• You can use a live card in your www.sandbox.com account for testing. This transaction will not go to a live environment it will only be sent to the Sandbox test environment.

Negative testing

For the Payflow Sandbox, to generate test transactions with specific decline errors, you would:

• Use a test credit card # provided in the Payflow Pro Developer's Guide (see Chapter on "Credit Card Testing"). The use of any other test credit card number will generate a decline.

• Create a payment transaction in Zuora with the appropriate payment amount to generate the result code you want to see. For example, the Payflow guide states that a payment transaction amount of $0-$1000 will generate Result = 0 (Approved). For transaction amounts of $1000-2000, certain amounts in this range will garner an error/declined Result.To generate a specific error, take the amount of $1000 and increase an amount matching the error code you want to produce (for example, transaction amount $1013 will generate an error of 13-Referral). A transaction amount greater than $2000 will generate a result of 12-Declined.

For the PayPal Sandbox, to generate test transactions with specific decline errors, you would:

• Generate a test credit card number per the instructions in the PayPal Sandbox User Guide .

• Create a payment transaction in Zuora using a payment amount matching the error code for the result you wish to generate (see PayPal API Error Codes for a list of errors). Here are some sample payment amounts you can test: 1. Amt = 107.52 Error: 12 -- Declined: 10752-Please use a different payment card. 2. Amt = 150.50 Error: 12 -- Declined: 15005-This transaction cannot be processed. 3. Amt = 107.55 Error: 6 -- Invalid or unsupported currency code: 10755-This transaction cannot be processed due to an unsupported currency.

• The errors you choose to test, have to:

  • Be valid errors for credit cards if you are testing a credit card payment method versus testing PayPal payment method.

  • Be a valid error for the transaction type you are testing, for example: PayPal API () DoAuthorization = Payment Method Authorization and PayPal API () DoCapture = Sale, Payment

Viewing test transactions in UI

Test transactions sent to the Payflow Sandbox can be viewed in the UI by logging into manager.paypal.com . If your PayPal sandbox account linked to Payflow, then you can view your transactions in https://www.sandbox.paypal.com .

General testing information

Integration testing

Zuora has been certified with PayPal as an integration partner and maintains the integration on an ongoing basis, thoroughly testing the integration with every new release. The PayPal integration documentation is helpful if you are integrating PayPal directly with your website (for example, to support the creation of Billing Agreement IDs), then you may need to refer to the integration guides. However, you do not need to perform any integration or certification testing to submit transactions to PayPal via the Zuora application. The intended audience for the integration guides are technical integrators, however, these documents can be helpful to non-technical integrators who can refer to it for information on testing and troubleshooting gateway errors (as described in the following section).

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.