REST API Direct Debit

Direct Debit is a widely used payment method that enables merchants to collect funds directly from a customer's bank account. It is a pull-based payment method where the merchant initiates the debit after obtaining authorization from the customer. This method is particularly favored for recurring payments such as subscriptions, utility bills, or installment payments, thanks to its reliability and lower transaction costs. NEXI supports Direct Debit payments both through its native offering and via multiple provider partnerships including EVO Payments, Intercard and PPRO.

Get started

To start accepting Direct Debit payments, onboarding with NEXI is required. During the onboarding process, merchants must provide:

• Creditor ID – A unique identifier used to authorize SEPA Direct Debits.

• Bank account details – The merchant's account details where funds will be settled.

Contact NEXI Helpdesk with the above details to activate the Direct Debit payment method for your merchant profile. Specify your preferred processing route if opting for a provider (EVO Payments, Intercard or PPRO).

Integration options

Direct debit is supported via all three integration types:

Hosted Payment Page

Integrate via Hosted Payment Page by submitting a payment request through Create checkout session

Hosted forms

Use the Hosted forms integration by calling Create payment with:

"paymentMethods": {
  "type": "DIRECTDEBIT",
  "integrationType": "HOSTED"
}

Direct integration

For merchants requiring full control over the checkout UI, integrate using Direct integration via Create payment:

"paymentMethods": {
  "type": "DIRECTDEBIT",
  "integrationType": "DIRECT",
  "directDebit": {
    "iban": "DE89370400440532013000",
    "accountHolder": "Max Mustermann"
  }
}

Mandate types

When processing Direct Debit payments, it is important to distinguish between the two types of mandates: one-off mandates and recurring mandates.

One-off mandates

A payment request that does not include any data in the credentialOnFile object is treated as a one-off mandate. These mandates are valid only for the specific payment for which they are created and are expired immediately after use. They cannot be reused for any future transactions.

Recurring mandates

Mandates created with a recurring intent (by providing data in the credentialOnFile object) are reusable. These mandates allow merchants to initiate future debits without needing to obtain new consent from the customer for each transaction. They support:

• Unscheduled CIT (Customer-Initiated Transactions) for one-click payments.

• Unscheduled MIT & Recurring Payments for ad-hoc debits & subscriptions.

For more information, refer to the Payment with recurring mandates.

Reverse payment

A Direct Debit transaction can be reversed before it is settled, releasing the funds back to the customer’s account.

To reverse a transaction, use the Reverse payment endpoint by specifying the payId of the original transaction.

Capture payment

If a Direct Debit transaction is initiated with captureMethod.type=MANUAL, you must explicitly capture the transaction after authorization.

Call the Capture payment endpoint with the associated payId.

Refund payment

Refunds can be issued for successfully settled Direct Debit transactions using either a referenced or unreferenced flow.

Refund with reference

Use the Refund payment endpoint with the payId of the original payment to initiate a refund.

Refund without reference

If needed, you can also issue a standalone refund using Refund external payment. Contact NEXI Support to activate this functionality.