Overview of Verifi Global payment gateway

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.

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.

Enable additional gateway services using Gateway Options

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

• Chargeback Representment
• Card Holder Dispute Resolution Network
• Decline Salvage
• Data Analytics
• Payer Authentication (Verified by Visa and Mastercard SecureCode)

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. 

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: