Accessing Your Gateway's Test Environment

If Use Gateway Test Environment is selected in your payment gateway configuration, Zuora will direct payment transactions to the Worldline Global Collect Legacy staging environment.

If Use Gateway Test Environment is not selected (disabled), Zuora will direct payment transactions to the Worldline Global Collect Legacy production environment.

Test Credit Cards and Testing Scenarios

Please contact your Worldline Global Collect Legacy implementation manager or Worldline Global Collect Legacy Support for specific test credit card numbers and testing scenarios. General support information can be viewed on the Worldline Global Collect Legacy 24/7 Shopper Support web page, including phone numbers by region and email contact information.

Integration Testing

Zuora has been certified with Worldline Global Collect Legacy as an integration partner and maintains the integration on an ongoing basis, thoroughly testing the integration with every new release. The Worldline Global Collect Legacy integration documentation is helpful if you are integrating Worldline Global Collect Legacy directly with your website, however, you do not need to perform any integration or certification testing to submit transactions to Worldline Global Collect Legacy 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. Integration guides and all necessary documentation are provided to you by your Worldline Global Collect Legacy implementation team (as described below).

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.

Transaction Testing

The following information explains how to test Worldline Global Collect Legacy transactions:

Credit Card Transactions:

• PM Creation: This can be tested by making an auth call.

• Sale: The Sale can be tested by making a sale call.

• Void: The void can be done before the transaction goes for settlement. If you want to do a void on sale, you can call it immediately after the sale call is made.

• Refund: In case of credit cards, it takes one business day for a sale transaction to be settled. If you do a sale call today, then you can test the refund of the transaction on the next business day or once the transaction is settled. You can use the inquiry call to identify whether the transaction is settled or is still in the process of settling.

• Inquiry: This can be tested by making an inquiry call.

Direct Debit Transactions:

• PM creation: This can be tested by making a auth call. In case of direct debit, the auth call is used for validation of the bank account information. This is done by Worldline Global Collect Legacy against their database.

• Sale: This can be tested by making a sale call.

• Void: Similar to credit card transaction, the void can be done only before the transaction goes for settlement.

• Refund: In case of direct debit, the settlement happens from one to five business days, depending on which country direct debit you are testing for. For the UK and France, it takes four to five business days to settle on their test environment. For all other countries, it can take up to two business days to settle. Similar to credit card, you can make an inquiry call to see whether the transaction is settled. If it has settled, then you can make a refund call.

• Inquiry: This can be tested by making an inquiry call.

Troubleshooting Gateway Errors

There are several ways to obtain information about gateway errors:

• Look up the transaction by the transaction ID number (in the Zuora payment detail page, this is the Reference ID and Secondary Reference ID numbers) in your Worldline Global Collect Legacy payment console to see if more information is provided; often you will see more than just the response (reasons) code and response message in Zuora.

• If you need further assistance with a specific error, please contact Worldline Global Collect Legacy support. General support information can be viewed on the Worldline Global Collect Legacy 24/7 Shopper Support web page, including phone numbers by region and email contact information.

Make sure you are not re-trying an invalid card too many times

We recommend that you check the payment in Zuora to see how many times the same payment method has been retried for payment and failed. If there have been several retries, check the error messages from the beginning with the first failure and the more recent failures to determine if the error message is the same. If a merchant tries to process a payment against the same credit card too many times despite receiving errors, this could trigger warnings to the card issuing bank. The card issuing bank may place an alert on the account and not allow any further transactions from the merchant using that payment method. When a merchant has been flagged, the error received on the payment may be not state the reason why, instead it might be a generic error decline error. In this case, the merchant (Zuora customer) should work with Worldline Global Collect Legacy to see if they can identify the problem with the payment method. If the processor does not know, then the merchant and/or the card holder can try calling their card issuing bank to look into the issue.

Transaction Error 410110

As discussed above under Prerequisites, it is very important for your account to be configured properly to accept the two-step Sale call. If it is not configured correctly, your transactions may error with Worldline Global Collect Legacy code "410110." This error code may contain a message that can vary, but here is an example of the message: "410110 -- REQUEST 35649 UNKNOWN ORDER OR NOT PENDING."

Working with your Worldline Global Collect Legacy implementation team

Worldline Global Collect Legacy provides merchants with an implementation manager during the first 90 days of the implementation to help with the complex process of implementing and working with direct debits. Processing direct debit transactions may require management of mandates (some countries require mandates and some do not) and thus we recommend working very closely with your implementation manager to understand how direct debits work and how mandates are obtained, processed, and maintained. Your implementation manager should also review how reporting and payment reconciliation is handled, as well as provide you all the necessary documentation to get you started with using Worldline Global Collect Legacy such as:

• Business Guide for Direct Debit

• WebCollect Reporting Guide

• Documentation Containing Test Credit Card Numbers and Test Scenarios