Integrate e-mandates

An e-mandate is a SEPA Direct Debit mandate that your customer signs online. Before the customer signs, Fintecture checks that they own the bank account to be debited. Fintecture then generates the signed mandate as a PDF and keeps you informed of its status.

E-mandates follow the SEPA CORE scheme and are always in EUR.

How it works

1. Your backend creates the e-mandate with the customer's details. The e-mandate starts in draft and comes with a link for the customer (links.next).
2. You redirect the customer to that link, or ask Fintecture to email it to them.
3. The customer proves they own the account to debit, either by connecting to their bank or by making a bank transfer.
4. The customer reviews the mandate and signs it.
5. The e-mandate becomes active. The customer receives the signed mandate PDF by email, you receive a webhook, and the customer is redirected to your redirect_uri.

What your customer sees

The customer first lands on the invitation page, which shows your name and the two steps.

They select their bank and connect to it. No payment is made at this stage.

Back on Fintecture, they review the mandate (its unique reference, your creditor identifier, the account to debit and the beneficiary), tick the consent box and validate.

Verification methods

Both methods are offered by default, bank connection first. You can restrict or reorder them when you create the e-mandate.

Before you start

1. Create a Fintecture account and register a client application with the e-mandates scope.
2. Make sure your application has a beneficiary. Its name and address are printed on the mandate as the creditor.
3. Have your SEPA creditor identifier (ICS) at hand. Your bank issues it, and it is printed on every mandate.
4. Configure a webhook for the emandates.status.* events. This is optional but recommended.

Integration steps

1. Request an E-Mandate access token.
2. Create an e-mandate and send your customer to links.next.
3. Follow its status through webhooks, or by reading the e-mandate.
4. Cancel, revoke or restart it when needed.

Every attribute and status is described in E-Mandate object.

📘

Production requests are signed

In production, every e-mandate call also needs an HTTP Signature on top of the Bearer token. Signing is optional in sandbox.

Test in sandbox

1. Create an e-mandate on https://api.sandbox.fintecture.com with a redirect_uri you control.
2. Open links.next in a browser.
3. Select Demo Bank and authorise account sharing. Sandbox banks return static test accounts.
4. Tick the consent box and click Validate mandate.
5. You are redirected to your redirect_uri with status=active, and your webhook receives emandates.status.active.