Buckaroo Support - EN

Explanation mandate

Another word for Digital eMandate is eMandate or e-mandate. This is the new way to issue a direct debit authorization online via your bank. The English term is eMandate also written as e-Mandate.

The distinction between B2C / Core and B2B direct debit mandates

For the time being, the direct electronic way of issuing mandates is only supported by the banks themselves within the Netherlands. When the merchant notes in the e-Mandates dashboard (indicated by their house bank) that the integration takes place via Buckaroo, a swift integration is possible. There are two types of Digital Direct Debit mandates available:

  • The B2C which is also called Core : these authorizations can be used by consumers on private accounts as well as by companies on a company account. That also explains the two names for the same product.

    Note: If the Core is used for a corporate mandate, a cancellation of up to 56 days is possible.

  • De B2B : These authorizations can only be used on a business account.


    -1- If the B2B is used for a company authorization, a reversal is not possible.

    -2- There may be a second signatory, who must give permission in their own banking environment.

Note about the term : When a Merchant decides to apply for a B2C e-Mandate on a business account, the pending status of the result can take up to 1 week. A B2C e-Mandate that is pending for more than 30 minutes is almost certainly an e-Mandate request on a business account, which requires more than one signature.

Note on the second signer : When a B2B e-Mandate is issued, it is possible that a second signer is required to ratify the agreement. This second signature must be given within one week in your own business banking environment. The first signer therefore does it in real time and the second is invited for this via the bank portal.

Mandate Service Provider - MSP

Buckaroo is an accredited party appointed by Currence in the list of Mandate Service Providers. As a Mandate Service Provider, Buckaroo can generate the e-Mandates. These e-Mandates serve as a replacement for the wet signature, which was the only legally valid way of authorizing until its introduction. Buckaroo's Third-Party Money Foundation can process these e-Mandates for all Merchants that handle the collecting mandates via Buckaroo. It is also possible to have the authorizations issued in a processing manner (on your own connection). In that case, Buckaroo provides the connection to the banks to generate the e-Mandates on the subscription that the Merchant has with the bank for this purpose. The direct debits must therefore be made via the account in the name of the Merchant. On the right is the image that describes which data applies to these two methods for e-Mandates.


Pay With Emandate

The PayWithEmandate is an additional service specially developed by Buckaroo for SEPA Direct Debit processing. The Merchant does not have to store the privacy-sensitive payment information, such as BIC, IBAN and name of the account holder. This service can be controlled by means of tokenization. This also makes it easy to have Buckaroo perform updates of the payment data (IBAN transfer service) without disrupting future SEPA Direct Debit payment requests: requesting a change to the existing e-Mandate is sufficient. Buckaroo manages the latest version of the payment data in its secured databases based on the mandate reference. The collection data from the successful e-Mandate is automatically added to the message to the bank. This method applies to both processing and collecting SEPA Direct Debits.


Validity e-mandate link

When an e-mandate is requested from Buckaroo, a redirect link is returned. This link has different expifagion times:

Type aanvraag e-mandate link Houdbaarheid Note
No bank selection Unlimited Hosted page from Buckaroo is used
With bank selection 15 minutes Consumer is redirected to their bank environment

Note: For the B2B e-mandate, the second signature must be provided in the bank package of the house bank. It can take up to 1 week before a complete e-mandate is completed.

Creating an e-Mandate

When applying for an e-Mandate, a mandate reference can be provided. If this is not provided, Buckaroo generates it itself. The data obtained during a successful e-Mandate interaction is stored by Buckaroo in the record of the mandate reference.

  • Name of the account
  • IBAN number
  • BIC corresponding with the IBAN
  • Mandate date
  • Digital Signature / e-Mandate number
Flow of creating an e-Mandate
Bank selection by Buckaroo

It is possible to offer an e-mandate at Buckaroo without choosing a bank. The response that comes back is a URL to a page where the bank choice can be made by the person who wants to issue the digital direct debit mandate. The URL has an unlimited expiration time and can therefore be added to an email sent by the Merchant. It can also be set up in a mining environment. The pre-registered data is shown on the page behind the URL:

  • Requester : Name of websitekey
  • Service : e-mandates
  • Authorization Attribute : Mandate Reference
  • Description : Description mandate
  • Collection type : Continuous / One-off
  • Reference : Number associated with mandate
  • Customer number : Debtor number

The use of the Buckaroo intermediate page is a good addition in the following cases:

  • When sending an email asking to confirm an authorization
  • For the confirmation of a direct debit mandate after a telephone conversation with a customer
  • When it is not possible to request the bank list in the Merchant environment

The URL link can be used indefinitely. This makes it possible for the Merchant to share it with the authorization provider by e-mail or another medium. The link can only be used once to arrive at a valid Mandate. When the first attempt fails, a new link is necessary. This is equivalent to the functionality if the bank is included with the request.

Revoke e-Mandate B2B

It is possible for a B2B e-Mandate to revoke an e-Mandate. The banks offer a separate message flow for this. This message can be sent to the various banks via Buckaroo. It suffices to mention the mandate reference as an identifier and the fact that it must be revoked. The reason for the option to withdraw from a B2B e-Mandate is because it is not possible to cancel. The money collected with a SEPA Direct Debit with an e-Mandate can only be reclaimed through legal proceedings.

Revoke e-Mandate B2C / Core

Withdrawing a B2C e-Mandate is not possible. As an alternative, the banks offer a block list for this. This list is part of the consumer's banking environment and can block an individual mandate as well as a complete payee. This means that an authorization previously provided with an e-Mandate can still end in a reject (reversal) at the initiative of the bank. The reason that the withdrawal of an e-Mandate is not supported by the banks is related to the cancellation right within 8 weeks. It remains possible for consumers to cancel the funds, even after issuing an e-Mandate.

e-Mandate number versus Mandate reference

Within the SEPA Direct Debit product, different terms are used interchangeably. Therefore, below an explanation and a drawing:

Mandate Reference / Mandate Reference

  • A mandate reference is a unique number generated by the Merchant per authorization with reference to the authorization issued, also when using e-Mandate
  • Is passed on to the bank together with a mandate date (date of issue of authorization)
  • Mandatory for all electronic and wet signature authorizations

e-Mandate / e-Mandate number

  • Unique number generated by the Bank as reference to the electronic consent
  • Can be optionally included in direct debit
  • A Notification of Incorrect Direct Debit (MOI) is not possible with B2B and B2C
  • Authorization is only possible on available accounts within the online banking environment
  • A reversal is also not possible with B2B
B2B paper mandates handling
  • Parties: When issuing a B2B mandate, there are two parties: the debtor's bank and the debtor's merchant. The first provides money and the second a service. The merchant exercises an authorization after a service has been provided on the IBAN of the debtor's bank.
  • Record: The merchant records the details of the mandate agreement with the debtor. The debtor signs this agreement and thereby allows the merchant to perform a B2B authorization on the specified IBAN. The debtor's bank must also be notified by the debtor of the arrangement between him and the Merchant. This is done by also sharing the signed agreement with your own bank.
  • Result: When both parties are aware of the agreement, the mandate will be successful and the bank will report this via the bank statement in the form of a successful mandate. Without this double authorization, the authorization will not succeed.
  • Advice: Handling the described paper flow is intensive and is not supported by Buckaroo. Buckaroo advises the B2B e-mandate functionality.

Below is a schematic representation of the paper mandate processing.