Vantiv is a full services payment provider offering payment processing and payment gateway services. Zuora pre-integrates with both the Vantiv payment gateway and processor, as well as their Automatic Account Updater.
Go to Vantive/Zuora Sign up for more information about Vantiv.
Vantiv was previously called Litle & Co.
Contact Zuora Global Support to enable this gateway in your tenant.
Confirm with Vantiv support whether your Merchant ID is enabled for the Vantiv test environment and whether your Merchant ID is linked with Zuora's Vantiv Submitter ID for the test environment. Vantiv gateway does not permit access to its test environment using your production Merchant ID, so you must obtain a test Merchant ID for testing purposes.
When your request is sent to the Vantiv Gateway via Zuora, the request is sent with the Zuora's Submitter ID in all environments. Your Merchant IDs can vary per your gateway settings for the production and testing environments.
If you plan to process both credit card and ACH transactions, we recommend that you configure two separate instances of the Vantiv Gateway within Zuora. The first configuration with verification turned on can process credit cards, and the second configuration with verification turned off can process ACH transactions. This setup avoids issues caused by eCheck verification on ACH transactions.
Once the gateway is enabled for your tenant, configure your gateway by going to Z-Payments Settings > Setup Payment Gateway page. When selecting a Gateway Type, choose Vantiv.
There are some common fields you must complete for every gateway configuration. We recommend reviewing our Setup Payment Gateway documentation for information on these common fields:
If enabled, Zuora will decline Credit Card transactions for certain AVS response codes returned by the gateway, even if the gateway has approved the transaction. Default is disabled.
If enabled, Zuora will decline Credit Card transactions for certain CVV response codes returned by the gateway, even if the gateway has approved the transaction. Default is disabled.
|AVS Response Codes||Description|
|10||5-Digit zip matches, address does not match|
|11||9-Digit zip matches, address does not match|
|12||Zip does not match, address matches|
|13||Postal code does not match, address matches|
|20||Neither zip nor address match|
|40||Address failed Vantiv edit checks|
|CVV Response Codes||Description|
In addition to the common fields, every gateway has unique requirements and information (such as credentials) that you must provide to configure the gateway in Zuora.Zuora.
Click and select the Merchant ID number for the gateway configuration. The Merchant ID number should be the same one you provided to Zuora Global Support to enable in your tenant, and the ID(s) will appear as a picklist in the gateway configuration page. If you have more than one Merchant ID number, you can set up Zuora Global Support to enable in your tenant, and the ID(s) will appear as a picklist in the gateway configuration page. If you have more than one Merchant ID number, you can set up multiple gateway configurations for each Merchant ID number.
If the Use Gateway Test Environment option is selected, click and select the test environment type in the Test Environment Type field. The Pre Live and Post Live environments are available.
Pre Live environment
The Pre Live test environment is the platform used for all merchant testing. You should use this environment if you are a newly on-boarding Vantiv merchant or if you are an existing Vantiv merchant seeking to incorporate additional features or functionalities.
Post Live environment
The Post Live testing environment is intended for merchants that are already fully certified and submitting transactions to the Vantiv Production platform, but wish to perform regression or other tests to confirm the operational readiness of modifications to their own systems.
If you accept credit card 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 Vantiv. For recurring payments, this option may result in reduced fees and greater acceptance with your merchant bank. Check with Vantiv to verify that this is available and appropriate for your account.
The Commerce Indicator identifies the source channel of the transaction request (i.e., the environment that the cardholder used to provide the payment card details to the merchant) and the type of transaction being processed. Select one of the following values from the list:
Perform the following steps to ensure that first and recurring transactions are setup properly:
We recommend testing your selected payment gateway using both your payment gateway's test and production (live) environments. Once you have completed testing in the gateway's test environment, it is recommended that you perform a test in your live production environment with a real credit card. If there are any differences in the configuration of your testing and production accounts, testing in production ensures your production merchant account is set up properly and can successfully connect to the production environment.
If Use Gateway Test Environment is selected in your payment gateway configuration, Zuora will direct payment transactions to the Vantiv testing environment that you chose in the Test Environment Type field in the Credentials section.
You will be accessing a test environment linked to Zuora's Submitter ID.
If Use Gateway Test Environment is not selected, Zuora will direct payment transactions to the Vantiv production environment.
Test credit card numbers and testing scenarios can be found in the Vantiv XML Reference Guide. Please work with your Vantiv implementation analyst to retrieve all necessary information for testing. Contact Vantiv Support for the latest version of the Vantiv XML Reference Guide. This guide provides specific credit card account numbers and data to include in your testing to generate specific gateway responses.
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.
There are several ways to obtain information about gateway errors:
For credit card and ACH transactions, we recommend configuring two separate instances of the Vantiv Gateway within Zuora. Use the first configuration (with verification turned on) for processing credit cards. Use the second configuration (with verification turned off) for ACH transactions. This setup avoids issues caused by eCheck verification on ACH transactions
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 Vantiv Support 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.