Knowledge Center

Knowledge Center > Billing and Payments > Payment Gateways > Supported Payment Gateways > Ingenico ePayments > Direct Debit for Ingenico ePayments > Implementing Direct Debit with Ingenico ePayments

Implementing Direct Debit with Ingenico ePayments

Although direct debit is treated like any other electronic payment method in Zuora, there are additional steps that you need to perform to implement this payment method. During your integration, contact your Ingenico ePayments integration manager for assistance.Your Ingenico ePayments integration manager will provide you with required documentation for your implementation.

Implementation Process

The implementation process consists of the following steps: 

  1. Collect  payment method information (direct debit account data) and mandates (signed approval, if required by the country) from customers.
  2. Submit payment transaction requests from Zuora to Ingenico ePayments to the customer's bank to debit the customer's account on a recurring basis.  
  3. Send notifications to the customer to notify them in advance that a payment will be debited from their account.
  4. Ongoing management of mandates to keep them current, payment reconciliation, and handling payments which fail to settle and charge backs (reflecting them in Zuora)

Direct Debit Processing

From Zuora’s perspective, processing direct debit payments works like any other electronic payment method, such as credit cards:

  1. Payment information is securely stored in Zuora.
  2. When it is time to collect payment, Zuora connects to the gateway electronically to verify credit cards, process sale transactions, void sale transactions, or process refunds.
  3. Successful payments are captured and funds are deposited in the merchant’s account.
  4. The payment record is recorded in Zuora and in the payment gateway (Ingenico ePayments). 
  5. If a payment attempt is denied by the bank, a failed payment is recorded in Zuora and in Ingenico ePayments, and the invoice remains unpaid. The payment may be reattempted by the merchant at a later time either by creating a payment manually or through a payment run. 
Last modified
15:04, 19 Jan 2016

Tags

Classifications

(not set)