Skip to main content

Overview of Verifi Global payment gateway


Overview of Verifi Global payment gateway

Supported features

The following table provides a quick reference for the supported features. For details about each feature, see the later sections in this article.

Supported payment methods

Credit Card/Prepaid Card/Gift Card, Debit Card, ACH

Support 3D Secure 2.0 No
Support Delayed Capture Yes
Support Level 2 and Level 3 card data No
Support stored credential transactions No
Support Gateway Options fields Yes
Verifi production endpoint used for Zuora gateway integration service
Support Gateway Reconciliation No
Support Payment Method Updater No

Supported payment methods

  • Credit Card/Prepaid Card/Gift Card, including:
    • Visa
    • MasterCard
    • American Express
    • Discover
  • Debit Cards
  • ACH

Support for Delayed Capture

The Delayed Capture feature allows you to authorize the availability of funds for a transaction but delay the capture of funds until a later time. For how to use the Delayed Capture feature, see Payment Authorization in Zuora API Reference. 

Sale vs Authorize and Capture (Delayed Capture) Verifi API Calls

Sale transactions are immediately flagged for settlement, as is standard for most gateways. All payments in Zuora are submitted as a Sale transaction. 

If you have a use case where you need to authorize a payment amount prior to capturing the payment, you will need the delayed capture functionality. For example, your company sells goods online but ships the product at a later time. You want to authorize a payment amount at the time of the order, and when the goods are shipped you capture the payment. 

Delayed capture is supported in this integration by passing the transaction data using the Verifi auth and capture API calls. An authorization is typically active for 3-7 days from the authorization date (however this can vary by different card issuing banks), and the payment can be captured as long as the authorization is active. Upon capture, the payment transaction is flagged for settlement and for most credit card transactions, settlement can be almost immediate.

Delayed Capture: Single Capture

The integration allows you to capture a payment amount equal to or less than the authorized amount. The authorization can only be captured once (this is a single capture). Therefore, you cannot capture part of an authorization amount now, then capture the remaining at a later time. If you have a use case that requires capturing partial payment upfront and capturing the remaining payment amount at a later time, you should create two separate authorizations and two separate captures.

Order ID

The integration uses the PaymentMethodId as the Order Id in the payment method verify() from which a payment method gets created. For a Payment transaction, the PaymentId is used as the Order Id in the sale() when the payment is created. Zuora does not pass an Order ID for Refund transactions to the payment gateway. To clarify, PaymentMethodID is not used in the void, auth, or capture API calls. 

Support for Gateway Options fields

You can submit additional information to the Verifi gateway by using Gateway Options fields through Zuora API operations. All Gateway Options fields are string fields.

Merchant Defined Fields

Zuora supports all of Verifi's Merchant Defined Fields (MDFs) from MDF1 through MDF20, allowing up to twenty MDFs to be passed per payment method authorization, payment, or refund transaction. MDF Fields are used to provide Verifi with important information about your business that Verifi will use when processing the transaction. Verifi may use this information for advanced transaction analysis, to trigger rules and filtering, as well as dynamically routing transactions. Information passed in these MDF fields should be accurate as the information is especially critical to mitigating and remediating fraud and risk.

MDFs are only supported via the Zuora API, with exception of MDF3 which can be configured when setting up your Verifi payment gateway using the field for "Product" (under Credentials). In the Zuora API, these MDFs are represented like this: Merchant Defined Field 1 is merchant_defined_field_1. If you would like to pass in different data for one of the MDFs in which Zuora passes default information (these are MDF1, MDF 2, MDF3, MDF6, MDF9, MDF18), you can do so utilizing gateway options.

The table below contains 3 columns: 

  • Verifi MDF Field Name: This is the name of the field in the Verifi gateway. In the API these fields are represented like this: Merchant Defined Field 1 is merchant_defined_field_1. 
  • Verifi Description: Listed are common data points to give you an idea as to the type of data commonly passed in these fields. You may not use all these fields or pass the exact data, as you would only pass the information and MDFs applicable to your business. 
  • Zuora Data Passed in MDF Field: Zuora will pass information in these fields by default with every payment and refund transactions (including create/update payment method, payment, create refund). Any of the Zuora data passed can be overriden using Zuora's gateway options, allowing you to customize the data passed in any of the 20 Verifi MDF fields.

Verifi MDF Field Name

Verifi Description

Zuora Data Passed In MDF Field

Merchant Defined Field 1

Customer ID

Customer Account Number

Merchant Defined Field 2

Level of Continuity Indicator Account Age

Total Number of Processed Payments for the Payment Method

Merchant Defined Field 3

Product Group/Brand

Text from the Product Field on the Gateway Configuration

Merchant Defined Field 4

Product ID, SKU(s)


Merchant Defined Field 5

Sales Center ID, URL


Merchant Defined Field 6

Sales Center Agent ID

Customer Account Sales Rep Name

Merchant Defined Field 7

Affiliate ID


Merchant Defined Field 8

Campaign ID


Merchant Defined Field 9

Retry Count
(Recurring Payments)

Number of Consecutive Failed Payments for the Payment Method

Merchant Defined Field 10

Shipping Method


Merchant Defined Field 11

Order Channel


Merchant Defined Field 12

Verify Indicator


Merchant Defined Field 13

Refund Indicator


Merchant Defined Field 14

Product Position


Merchant Defined Field 15

Acquisition Cost


Merchant Defined Field 16

Review Indicator


Merchant Defined Field 17



Merchant Defined Field 18

Device Profiling Session ID

Device Session Profiling ID from the Payment Method

Merchant Defined Field 19

Card Product Indicator Code


Merchant Defined Field 20

Verifi Processed


Enable additional gateway services using Gateway Options

You can use Zuora's gateway options to enable additional services provided by Verifi such as:

Gateway options allow you to pass in custom information with your transactions (any value can be passed) and Verifi can use the data to enable or trigger additional gateway services.  For example, gateway options can be used to pass in information such as IP Address or Device Session ID. 

As previously mentioned, you can use gateway options to overwrite the data which Zuora passes over by default in the Merchant Defined Fields (MDF), specifically MDF1, MDF 2, MDF 3, MDF6, MF9, MDF18. 

To enable additional services provided by Verifi, you will need to be signed up for the service through Verifi and the service must be enabled for your Verifi merchant account. Please direct inquiries regarding Verifi's gateway features associated fees to use such features to your Verifi account manager. 

Additional gateway information

Settlement Cut Off Time

Payment gateways have a cut off time by which payment transactions have to be received by the gateway if you want the payment(s) to be submitted for settlement that same day. Some gateways, such as Verifi, alllow you to customize this cutoff time. 

  • Daily Cutoff Time = 00:00 GMT (midnight) but is customizable. 
  • Extended Void Period = 00:00 - 02:00 GMT
    Verifi provides an extended Void Period to allow void transactions to be submitted which may cancel a payment that is pending settlement. 

Soft Descriptors

Merchant soft descriptors are supported with the integration, allowing you to submit any information you want about the purchase. This soft descriptor appears on your customer's credit card statement and helps identify what the charge is for. Examples of soft descriptors are your product name, company name, store locations. Using soft descriptors helps prevent chargebacks that occur when a customer does not recognize a charge on their credit card and mistakes it for fraud. 

The Zuora API fields for soft descriptors map to the Verifi API fields as follows:

Zuora API Field Name Zuora API Object Verifi API Name Field Type Field Size