Creating a SEPA direct debit mandate

Estimated reading: 4 minutes

After registering the customer’s bank account bankAccount and linking it to their “Customer” profile, you can create a SEPA mandate “mandate” and collect your customer’s electronic signature using a one-time password (OTP) sent via text message.

Prerequisite: You must retrieve the creditorBankAccountId from your CentralPay Merchant Profile that corresponds to your ICS. You can find it in your Merchant Portal by using a profile with Admin privileges: Administration My Merchant Profile Bank accounts

Locate the row containing your ICS in the “IBAN” column, then copy the associated UUID.

1. Creating and signing a new SEPA mandate

1.1. Create a SEPA direct debit:

  • Create a “Mandate”
    • Enter your “creditorBankAccountId”
    • Enter your customer’s “CustomerId”
    • Enter your Unique Mandate Reference (RUM)
    • Specify the type of payment you want to create in the “paymentType” property
    • Enter your customer’s phone number in the “debtorPhone” property
    • Enter your customer’s email address in the “debtorEmail” property
    • Specify your customer’s bank account by entering their “bankAccountId” in the “debtorBankAccountId” property.

  • Once the SEPA direct debit has been set up:
    • Un “mandateId” sera généré
    • The mandate status will be PENDING
    • A 6-digit code (OTP) will be sent to your customer via text message (valid for 15 minutes). You can have the OTP resent.

1.2. Sign a SEPA direct debit authorization:

  • Sign the “Mandate”
    • Collect the 6-digit code from your customer and enter it in the “otp” property
    • Enter the “mandateId” generated when the mandate was created
    • Enter your client’s IP address in the “endUserIp” property
    • The mandate status will then change to “ACTIVE,” and the SEPA mandate in PDF format will be emailed to the customer.

1.3. Flowchart for bank account registration and power of attorney creation

2. Declaration of an existing mandate (migration)

When migrating payment orders that were previously created with another payment service provider, you can disable the SMS OTP signature feature and the option to send SEPA payment orders via email. If this applies to you, please contact our team for more details about this process.

Requirements:

  • Direct debits must have been set up using your SEPA Creditor Identifier (ICS)
  • Power of attorney documents must have been created using your current legal entity
  • The payment orders must have been duly signed and accepted by your debtors
  • Accounts must still be active (less than 36 months since the last transaction)

3. Modifying an existing SEPA mandate

3.1. Possible changes that do not require a new mandate

Certain information may be updated without requiring the signing of a new SEPA direct debit mandate, provided that the debtor is properly notified:

  • Change in the creditor’s name (change in the legal structure of the entity making the deduction)
  • Change to the SEPA Creditor Identifier (ICS)
  • Change to the Unique Mandate Reference (RUM)
  • Change of account or IBAN for the payer within the same bank
  • Change of account/IBAN of the payer following a change of bank

Related endpoints:

  • Edit a Debit Account IBAN
    POST /bankAccount/{bankAccountId}
    Allows you to update the IBAN of a debit account linked to an existing SEPA mandate.
  • Modifying a RUM
    This operation is not possible via the CentralPay APIs. Modifying a RUM requires creating a new mandate (migration).
  • Change the Creditor’s Name
    If there is a change in the legal structure responsible for processing direct debits, a new CentralPay Merchant Profile (Merchant) must be created. Existing mandates will then need to be re-registered under this new profile through a migration process.

3.2. Changes that require a new mandate

The following changes require the creation of a new SEPA direct debit mandate, as they involve a new authorization from the payer:

  • Change of the debtor’s name
  • Change in the date of signing the mandate
  • Change in mandate type: transition from SDD Core to SDD B2B
    Note: This use case is not available in CentralPay services
  • Change in the sampling frequency: from one-time to recurring

3.3. Notification of changes

Notifications of changes must be submitted:

  • From the creditor to the debtor, for any changes initiated by the creditor (ICS, RUM, IBAN, etc.)
  • By the debtor to the creditor, with submission of supporting documentation (e.g., bank account information or identification) for changes to the IBAN or personal information
Creating a SEPA direct debit mandate - PreviousBank account statementNext - Creating a SEPA direct debit mandateDirect Debit transaction
CONTENU