An e-mandate is a digital authorization for one or more direct debit payments.
What is direct debit?
Within the EU, consumers and companies can agree to pay for goods or services using direct debit. This means that you as a customer (the debtor) allow, via e-mandate, that someone (the creditor) can take money from your bank account. Direct debit has been standardized in the EU to enable cross-border use, and is therefore called “SEPA direct debit” (SDD) in the EU. The e-mandate is managed by the creditor (the party receiving the money).
About SEPA direct debit (SDD)
SDD is described in the:
- SDD Core Rulebook (https://www.europeanpaymentscouncil.eu/what-we-do/sepa-direct-debit/sepa-direct-debit-core-rulebook) and the
- SDD B2B Rulebook (https://www.europeanpaymentscouncil.eu/what-we-do/sepa-direct-debit/sepa-direct-debit-b2b-rulebook).
The following table explains the key differences between the two SEPA Direct Debit schemes: Core and B2B.
|SDD CORE||SDD B2B|
|General description||A mandate for the standard SEPA Direct Debit. This can be issued by consumers and businesses.||The business-to-business SEPA Direct Debit. This is for direct debits between businesses.|
|Bank participation||Mandatory||Optional, so not all banks have to support this method.|
|Submission timing (of payment transactions)||1 day prior to collection||1 day prior to collection + faster response from the bank in case of a failure (3 days after collection)|
About SEPA e-mandate
The e-mandate is standardized in the EU by the European Payments Council. Information about the standard can be found at https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/guidelines-appearance-mandates-sepa-direct-debit-schemes.
Electronic payment mandates may be issued without a physical signature on paper.
End-user (debtor) experience
- Creditors can invite their customers (debtors) via a link.
- The debtor is able to react to invitations and accepts the mandate using a bank-accepted binding method.
- The debtor can cancel and modify contracts or mandates.
- Signicat/ Twikey informs creditors/suppliers of the acceptance or rejection of the mandate.
- The mandate can be managed by the creditor via a mandate dashboard.
Creditor management portal
Twikey delivers a management portal for each individual creditor. In the management portal, a creditor can:
- Create and send e-mandates to debtors
- Monitor e-mandate statuses
- Cancel, resume and reschedule (recurring) direct debits
- Check the direct debit collection statuses (optional)
- Configure “templates”, which define
- the end-user UX
- which methods can be used to sign an e-mandate
- which creditor bank account should be used to receive the funds
- one-time or recurring payment
- the redirect URL
Creating an e-mandate URL
The following is the basic URL for triggering an e-mandate signing session in our pre-production environment:
Please note the query string &prefilled.ct=1482 at the end of the URL. This represents the Contract Template number and is the only mandatory field in the call.
You can follow the same approach of adding &prefilled.<ATTRIBUTE-KEY>=<ATTRIBUTE-VALUE> for other attributes. These attributes will then be asked for in the mandate form presented to the end-user:
|Contract Template ID||Number (*)|
|l||The language choice to be pre-selected on the registration screen||String (en/nl/fr/de/it/es/pt)|
|The email to be pre-filled on the registration screen||String|
|lastname||The last name of the person to be pre-filled on the registration screen||String|
|firstname||The first name of the person to be pre-filled on the registration screen||String|
|address||The address (street + number) of the debtor||String|
|city||The city to be pre-filled on the registration screen||String|
|zip||The zip to be pre-filled on the registration screen||String|
|country||The country to be pre-filled on the registration screen||String (Iso2)|
|mobile||The mobile phone number to be pre-filled on the registration screen (optional)||String|
|mandateNumber||Mandate ID overruling the automatically generated number by Twikey. Needs to be unique.||String (Uppercase)|
|contractNumber||The contract number which can override the one defined in the template||String|
|iban||The IBAN account number to be pre-filled in the contract||String|
|bic||The BIC number to be pre-filled in the contract (if known)||String|
|amount||Amount to add to the mandate once the debtor has signed the mandate||Double|
|token||A parameter that can be returned in the exit URL (see below) to avoid invalid sessions||String|
|attributename||If attributes are defined, the name of the attribute||String|
|plan||name of a plan in order to add a (custom) plan to the mandate||String|
|Parameters if the debtor is a company (B2B mandate)|
|company||enable ‘I act on behalf of a company’ on the registration screen. By default, the checkbox value is false.||Boolean|
|companyName||the company name (of the customer) to be pre-filled on the registration screen||String|
|vatno||the enterprise number (of the customer) to be pre-filled on the registration screen||String|
|form||Legal form of the company (depending on country). If the form given in the URL is not known, Twikey will interpret it as “other” value.
• BE : nvsa, bvbasprl, vzwasbl, cvsc
• NL : nv, bvba, cv, cvoa, vof
• FR : sa, sarl, sc, snc, eurl
• LU : sa, sarl, senc, soparfi
• DE : ag, gmbh, gbr, kg, ev, kgaa, ohg
• IT : spa, srl, sa, sapa, sas, snc
• UK : plc, ltd
After an e-mandate is signed, a SAML 1.1 response is returned to the creditor, containing the fields specified in the URL, adding the template-specific fields. The mandate information is also available in the Creditor Management Portal. In the pre-production environment, the response is available in OIDC and SAML2.0 as well.
Creating a mandate contract template (CT) with Twikey
For every type of mandate, Twikey allows the creditor to create a template which contains more information, such as B2B, creditor ID, one-off, contract reference and description. This must be manually configured in the creditor GUI. Twikey provides a unique ID per contract template (CT).
- Go to https://www.beta.twikey.com/r/admin#/c/contracts.
- Click on Settings ->Templates.
- In the top right corner, press “New”.
- Fill out the form with the already known “default” data.
- “Type” combobox will determine the type of scheme to be used: CORE or B2B.
- Make sure to specify the exit URL. This will be the URL the end-user is redirected to after finishing the mandate process.
- You will be presented with a popup similar to the following:
A sample flow
1. Redirect the user to the mandate signing URL, e.g. https://eu01.preprod.signicat.com/std/method/signicat/?id=twikey::&target=https%3A%2F%2Feu01.preprod.signicat.com%2Fjames%2Fresponse&prefilled.ct=1482. The user will see a field where he/she needs to upload his/her details to sign the mandate:
2. After filling out the form, the user is asked for consent:
3. The user needs to select a signing method to sign the mandate:
4. In the bank simulation screen, choose the “Success (w/o delay)” scenario:
5. The SAML response is received: