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.

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.

Related information

Set up and configure a Verifi Global payment gateway instance