SDD payment and mandate Copy section link Copied!

The Single Euro Payments Area (SEPA) Direct Debit is a standardised payment method for bank-to bank transactions within the European Union.

AgoraPay supports:

• Both one-off and recurring SEPA payments
• B2B customers (professionals only). In this case, a copy of the SDD mandate must be transmitted by the payer to its bank when the signature or certification occurs, in order for the bank to register the mandate's characteristics. It's important to remind this to the payers to avoid payment rejections.
• B2C customers (individuals or professionals). In this case, the payer has 8 weeks to reject the payment after the payment has occurred.

The main steps for a SDD payment transaction include

1. The buyer validates his cart on the marketplace
2. The buyer selects SDD as a payment method on the marketplace website
3. The SDD e-mandate is subject to signature validation beyond a pre established threshold. Pin will be sent by sms.
4. Agorapay redirect the buyer to the Marketplace
5. The Marketplace displays the SDD mandat confirmation
6. Pre notification e-mail is sent to the buyer

Please note : in case of Recurring SDD payment, except for the first SDD payment, Mandate Reference (RUM) is directly transmitted via the API Payment. No path.

Please note, the SDD Business to Business (SDD BtoB) and Business to Customer (SDD BtoC) workflow are the same.
But few differencies must be underlined :

For a BtoB SDD

• Debtor must be a business
• Mandate signature is required only beyond pre established threshold.
• Mandate registration by Debtor bank is required
• Mandate is undisputable

For a BtoC SDD

• Debtor can be a consumer or a business
• Mandate signature is required only beyond pre established threshold
• Mandate is disputable

The SDD mandate is delivered in PDF format, base-64 encoded.

There is two separate ways to retrieve a mandate:

1. On the transaction identifier when its status is 'COMPLETED' or 'REFUSED'
2. On the unique mandate reference (RUM/UMR), without condition on the SDD transaction(s) associated to this reference

If your request is successful, you will receive a getMandate response, containing the following information:

Here is a successful response example:

If the request is not successful, you will receive a response error with no SDD mandate.

It is possible to receive unpaid before or after the payment effective date.
This leads to 2 distinct behaviors:

1. Collection of an unpaid amount before the compensation (after payment effective date) leads to the cancellation of the direct debit.
   An operation before the effective date is in status 'W'. The reception of the unpaid amount will result to an operation update to status 'C ' and a webhook being sent.
2. Collection of an unpaid after compensation (after payment effective date) possible up to 13 months in the event of a contestation by the debitor. The operation after the payment effective date is in status 'E'. The collection of the unpaid will lead to the creation of a new UNPAID type operation with status W and the sending of a webhook.

This webhook has the following specificity:

• The operationType = 9 (for unpaid type)
• The transactionId respects the following nomenclature: UNPAID-XXXXX where XXXXX corresponds to the transaction which caused the unpaid
• The operationMasterId corresponds to the transaction that suffered the chargeback.
• Once the unpaid funds have been cleared, the status of the UNPAID type transaction will change to E and a webhook will be issued.