Worldpay Payment Gateway

Disable Capture Delay

It is very important that you disable capture delay in Worldpay, as Zuora issues a separate capture call after the authorization occurs. Log in to the Merchant Interface for the desired environment, and locate the setting Capture delay (days). Set this to -off to disable capture delay.

$0 Authorization Support

As is common with payment gateways, Worldpay can check that customer's credit card is valid by issuing an authorization for an amount of money. Worldpay provides you with the option to enable $0 authorization, so that authorizations can be issued without leaving a trace on the customer's card history. To enable this optional feature please contact Worldpay Support.

Whether or not requests for $0 amounts are authorized depends on the specific bank and currency the customer uses. Although many financial institutions accept small authorization amounts (for example, $0.01 or $0), there are a number of banks that do not. These banks will reject cards that may or may not be valid simply due to the size of the authorization amount. This will affect cards entered in the Zuora Payments UI as well as through the API. In these cases, you should increase the default authorization amount.

Risk Screening

Worldpay authorization supports Address Verification Service (AVS), and Card Verification Value / Card Verification Code (CVV2, CVC). These provide a mechanism for checking the authenticity of a transaction by comparing information entered by the shopper during the payment process, with details held by the card issuer. You can also configure whether to receive the AVS/CVC result code or message in the authorization response. If enabled, Zuora will record the value returned without interpretation.

Worldpay offers two fraud screening products; Risk Management Module (RMM) and Risk Guardian (RG). Both of these allow you to configure the mapping from the risk check results to the authorization result. If you choose to use either of these products, you must configure the settings in the Merchant Interface for both live and test environments.

Define Shop Name and Shop URL

Worldpay allows you to set values for ‘Shop name’ and ‘Shop Url’ (which define the name of your business and URL of your website). To do this, visit the Merchant Interface for the live or test environment and set the values in your profile, or contact Worldpay Support to request that they do this on your behalf.

Discover Card Support

Worldpay supports payments by Discover card, but this is disabled by default. If you would like to issue payments with Discover cards in Zuora, please contact Worldpay Support to enable this feature.

Single Euro Payment Area (SEPA) Direct Debit Payments 

By default, the Worldpay SEPA integration supports direct debit payments for these countries: Austria, Belgium, France, Germany, Ireland, Italy, Netherlands and Spain. SEPA trade schemes vary between countries and there is a settlement delay of 1 to 5 business days.

The following fields are required by Worldpay for saving a SEPA payment in Zuora:

• Select SEPA from the Bank Transfer Type drop-down 
• Valid Bank Transfer Account Number and Name.

e-Mandates

e-Mandates are online agreements between the shopper/consumer and Worldpay. It is the obligation of the merchant to create your own SEPA Direct Debit e-Mandate and present the e-Mandate to the shopper using this payment method. The following e-mandate fields need to be sent to Worldpay:

• Shopper email address
• Merchant name
• Mandate ID or reference information
• Account holder's name
• Mandate type (one-time, recurring, etc.)
• IBAN

Tokenization 

The payment method used for tokenization is the Credit Card Reference Transactions (CCRef) payment method. Zuora uses the shopper token and not the merchant token. The following are supported by the Credit Card Reference payment method:

• Credit token
• Verify a token - The Token ID and Second Token ID fields in Zuora are required by Worldpay in order to verify a token.
• Capture a payment using a token
• Refund payment

Common Fields for Configuration

There are some common fields you must complete for every gateway configuration. We recommend reviewing Setting Up Payment Gateways for information on these fields: 

• Name: Choose a name that identifies this payment gateway. We recommend using a name that helps your users identify the gateway.
• Use Gateway Test Environment: Select this check box if you want Billing to use the payment gateway's test service URL. This allows you to test payment transactions while you are setting up your Billing.
• Cards Accepted: Worldpay accepts the following cards: Visa, MasterCard, American Express, Discover, Diner's and JCB.
• Default Authorization Amount: Enter the minimum default amount used to process a payment. If the verify credit card checkboxes are selected, this amount will be used to validate the payment method by first authorizing the amount and then voiding the authorization when the amount is greater than zero.. 
• Verify new payment method (optional): When you select either or both of the Verify new payment method and Verify updated payment method check boxes, Zuora Payments (within the Zuora Application and Zuora API) submits key information to the payment gateway to authorize all payment methods for authenticity and fraud prevention. For more information see Verifying the Credit Card Gateway Options.
• Verify updated payment method (optional): See text above.

In addition to the common fields, every gateway has unique requirements and information (such as credentials and certain rules) that you must provide to configure the gateway in Zuora. 

Worldpay Credentials

Your credentials should be obtained from Worldpay and configured in Zuora. 

Worldpay Rules

The following fields are specific to the Worldpay 1.4 payment gateway:

• Enable gateway reconciliation (optional): Select this check box if you want to enable Gateway Reconciliation in this gateway instance.
• Admin code (optional): The Admin Code assigned to your merchant account by Worldpay.
• Merchant Acronym (optional): The Merchant Acronym assigned to your merchant account by Worldpay.

See Configuring Worldpay Gateway Reconciliation for more information.

Accessing Your Gateway's 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. Worldpay uses the same Merchant ID for test and live transactions, but a different XML password for each.

General Testing Information

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).

Integration Notes

Functional Mapping between Zuora and Worldpay

This section describes the functional mapping between the Zuora API and the Worldpay API.

Credit Card Field Mappings

This section describes the object and field mappings between Zuora and Worldpay for Credit Card Payment Method creation and Payment creation.