Skip to main content

Supported Configuration Fields By Gateway


Supported Configuration Fields By Gateway

Because each gateway has different requirements, the setup page for each of these payment gateways varies. Contact your payment gateway to obtain the information required to configure the gateway in Zuora.

List of available fields

The following fields are available for the, Chase Orbital, CyberSource, and Ingenico ePayments payment gateways.

Standard fields

All payment gateways configurations in Zuora use the following fields:

  • Name
  • Use Gateway Test Environment
  • Credit Cards Accepted
  • Default Authorization Amount
  • Verify new payment method (optional)
  • Verify updated payment method (optional) fields

The gateway uses the following fields:

  • API Login ID
  • Transaction Key

Chase fields

The Chase Orbital gateway uses the following fields:

  • Industry Type
  • BIN
  • Merchant ID

CyberSource fields

The CyberSource gateway uses the following fields:

  • Merchant ID
  • Private Key
    The private key is a security file that must be downloaded within your CyberSource Business Center. To download the security (.p12) file from the Business Center, go to the Account Management tab and select the Transaction Security Keys option. Next follow the instructions on the Transaction Security Keys page in order to generate your security keys for the simple order API. 
  • Use Export Compliance (optional)
    CyberSource offers a variety of verification and compliance services, one of which is called Export Compliance. Export Compliance helps online merchants maintain compliance with the U.S. Government export regulations. Visit CyberSource's website to read about the features of Export Compliance. If you have signed up for CyberSource's Export Compliance verification services, you should select the "Use Export Compliance" field in the gateway configuration. By doing this, Zuora will submit an API call (through CyberSource) to verify whether the end customer (credit card holder) is on a black list of countries or person with whom the merchant should not accept orders from. If the export compliance verification fails, the payment method verification also fails which may result in the order not being accepted (for example, the subscribe call will fail). 

Ingenico ePayments Collect fields

The Ingenico ePayments gateway uses the following fields:

  • Merchant ID
  • Soft Descriptor

Merchant e-Solutions fields

The Merchant e-Solutions gateway uses the following fields:

  • Profile ID
  • Profile Key
  • IP Address
  • Moto eCommerce Indicator

Moneris fields

The Moneris gateway uses the following fields:

  • Store ID
  • API Token
  • eFraud
  • Crypt

PayPal Payflow Pro fields

If you are using the PayPal Payflow Pro product, the credentials to configure the gateway in Zuora will be the same as your login credentials for PayPal Manager. If you are using the PayPal Website Payments Pro product, you should request Payflow Pro API credentials and configure those credentials in Zuora.

The PayPal Payflow Pro gateway uses the following fields:

  • Partner
    The partner is typically PayPal, but may also be Verisign depending on your specific PayPal account set up. 
  • Merchant ID
    If you are using the Payflow Pro product, enter your Merchant ID. If you are using Website Payments Pro product, enter your Vendor information here.
  • User ID
    User ID may also be referred to by PayPal as User and may be the same as your merchant login. 
  • Password
  • Support Recurring
    If you accept credit card reference transaction payment methods, you may consider enabling the Support Recurring option. If Support Recurring is selected, Zuora will mark such payments as recurring when submitting the sale payment transactions to PayPal. For recurring payments, additional security checks for previously authorized transactions may be disabled by PayPal, allowing for reduced fees and greater acceptance with your merchant bank. Please check with PayPal to verify that this is available and appropriate for your account.

SoftBank fields

The SoftBank Payment Service gateway uses the following fields:

  • Merchant ID
  • Service ID
  • Hashkey
  • Basic Authorization Id
  • Basic Authorization Password

Stripe v2 fields

See Stripe Payment Gateway for details.

Vantiv fields

The Vantiv gateway (formerly called Litle) uses the following fields:

  • Merchant ID
  • User Name/ID
  • Password

Verifi fields

The Verifi gateway uses the following fields:

  • User Name/ID
  • Password
  • Product

WorldPay fields

This feature is in Limited Availability. We are actively soliciting feedback from a small set of early adopters before releasing as generally available.

The WorldPay gateway uses the following fields:

  • Merchant code
  • User Name
  • XML Password