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
Troubleshooting Gateway Errors
For failed payments processed using the Worldpay payment gateway, Zuora Payments will provide the gateway
Response Reason Code (for example, 203) and Response Reason text (for example, general decline of the card).
To obtain more information on gateway errors, look up the transaction ID number (called Reference ID in the Zuora
payment detail page) in the Worldpay Merchant Interface or Worldpay Merchant Test Interface to see if more information
is provided; often you will see more than just the response code and response message in Zuora.
If you require additional information, you can log a case in the Worldpay Support Center. All Worldpay merchants have
access to online support, and depending on your support package with Worldpay, you may also have access to phone
support. Please work with your Worldpay contacts to understand your options for contacting Worldpay Support. Be sure
to have your reason code as well as your Transaction ID (in Zuora Payments this is the Reference ID) for the failed
payment. This Transaction ID is an alphanumeric number (for example, CLEF4CGE8AB8).
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 mechant has been flagged, the error received on the payment may be
not state the reason why, instead it might be a generic decline error. In this case, the merchant (Zuora customer) should
work with their merchant acquirer/processor 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.
https://knowledgecenter.zuora.com/Billing/Billing_and_Payments/M_Payment_Gateways/Supported_Payment_Gateways/Wo…
Updated: Tue, 28 Dec 2021 13:23:23 GMT
Powered by
7
