Set up and configure a Verifi Global payment gateway instance
Learn how to set up and configure a Verifi Global payment gateway instance, including prerequisites, configuration fields, and testing procedures.
Set up and configure a Verifi Global payment gateway instance by using the information in this article, including prerequisites, configuration procedure, descriptions of the configuration fields, and reference for testing the payment gateway.
Prerequisites
Enable the Verifi Global payment gateway integration for your tenant. See Enable payment gateway integrations for your tenant for instructions.
Configuration fields
Common configuration fields
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:
-
Name
-
Use Gateway Test Environment
-
Cards Accepted
-
Default Authorization Amount
-
Verify new payment method (optional)
-
Verify updated payment method (optional)
Default Authorization Amount
The Verifi gateway accepts only a $0.00 authorization amount, which Verifi will use to perform card validation. For $0.00 authorizations the Verifi
validate()
is used to process a non-financial transaction against the credit card. This type of authorization will still return a response for both Address Verification Service (AVS) and Card Verification Value (CVV) Code. Verifi's API documentation states "some processing networks may return an invalid authorization code and this value should be ignored."
Since Zuora's payment gateway configuration allows you to define any authorization amount you want, we will use the Verifi
auth()
if you configure the default authorization amount to be greater than $0.00. The
auth()
does process a financial transaction against the credit card, but this transaction is immediately reversed using the
void().
Credentials
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. For Verifi, you must enter a username, password, and product.
User Name
This is the username assigned to you (the merchant) by Verifi. It is a numeric 50 digit value that identifies you in the Verifi gateway.
Password
This is the password for the username.
Product
Zuora will default the product to "Subscription" but this field can be modified. The text in this field is passed into Verifi's Merchant Defined Field 3 (MDF3). See Overview of Verifi Global payment gateway for more information.
Test the configuration
Troubleshoot 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 Verifi gateway virtual terminal to see if more information is provided; often you will see more than just the response (reasons) code and response message in Zuora.
-
Review Verifi's API Documentation for transaction response codes and descriptions.
-
For additional assistance or to obtain the Verifi API Documentation, you can contact the Verifi support team .
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 re-tried 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 not state the reason why, instead it might be a generic error decline error. In this case, the merchant (Zuora customer) should work with Verifi and/or your payment 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 cardholder can try calling their card issuing bank to look into the issue.
Duplicate Transaction Decline Error
If you receive an "Error Processing Transaction.300 Duplicate Transaction REFID: 326976199" it may be caused by a duplicate check by Verifi. The Verifi gateway checks for duplicates when orders are submitted within 20 minutes of each other and the same payment method, same dollar amount for the transaction, and same order ID are used for the transaction (see below for more information on order ID) are used for the transaction.
Related information
Overview of Verifi Global payment gateway