Buckaroo Support - EN

Explanation mandate

A different word for Digital Direct Debit Authorisation is eMandate or e-Mandate. This is a new way to issue a direct debit authorisation online via your bank.

Difference B2C/Core and B2B direct debit authorisations

As yet, the direct electronic manner of issuing authorisations is supported only in the Netherlands by the banks themselves. If the Merchant states in the eMandates dashboard (issued by his main bank) that the integraton will take place via Buckaroo, a very fast integration is possible. There are two available types of Digital direct debit authorisations:

 

  • The B2C, also called Core: these authorisations can be used by consumers for private accounts as well as by businesses for business accounts. This explains why there are two names for the same product.

    Note: if the Core is used for a business authorisation, reversal of payment is possible up to 56 days.

  • The B2B: these authorisations can only be used on a business account.

    Note: if the B2B is used for a business authorisation, reversal of payment is not possible.

Note with regard to status: When a Merchant decides to apply for a B2C eMandate on a business account, the pending status of the result can run up to a maximum of one week. So if the status for a B2C eMandate is pending for over 30 minutes, it is almost definitely an eMandate request on a business account, which requires more than one signature.

 

Mandaat Service Provider - MSP

Buckaroo is an accredited party appointed by Currence in the list of Mandate Service Providers. As a Mandate Service Provider, Buckaroo is able to generate eMandates. These eMandates serve as a substitute for the wet signature which up until now was the only legal way of authorisation. The Stichting Derde Gelden of Buckaroo can process these eMandates for all Merchants who process the authorisations via Buckaroo Collecting. It is also possible to let the issuing of the authorisations be handled in a processing manner (on your own link).  In that case, Buckaroo will take care of the connection with the banks to generate the eMandates on the subscription that the Merchant has for this purpose at the bank. The direct debits then also have to be executed via the account held in the name of the Merchant. The adjacent figure shows which information is necessary for these two eMandates methods.

 

Pay With Emandate

PayWithEmandate is an additional service for SEPA Direct Debit processing developed by Buckaroo. The Merchant does not have to save privacy-sensitive payment data, such as BIC, IBAN and the name of the account holder. The service can be managed by means of tokenization. This also makes it easy to let Buckaroo perform updates of the payment data (IBAN switching service) without disrupting the future SEPA Direct Debit payent requests: requesting a modification of the existing eMandate will suffice. Based on the mandate reference, Buckaroo manages the latest version of those payment data in its secured databases. The direct debit data from the successful eMandate are added automatically to the message that is sent to the bank. This working method applies to both processing and collecting SEPA Direct Debits.

 

 

Validity of e-mandate link

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

Type of e-mandate link request Vallid until Opmerking
Without bank identifier undefined Hosted page of Buckaroo will be used
With bank identifier 15 minutes Debtor will be redirected to own bank environment

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

Genarating an e-Mandate

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

  • Name of the accountholder of the IBAN
  • IBAN number
  • BIC belonging to the IBAN
  • Mandaat date
  • Digital Signature / e-Mandaat number
Flow generating an e-Mandate
Choice of the bank at Buckaroo

It is possible to offer an e-mandate at Buckaroo without the choice of the 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 authorization. The URL has an unlimited validity and can therefore be added to an email sent by the Merchant. It can also be prepared in a "my" environment. The pre-registered data is shown on the page pointed to by the URL:

  • Applicant: Name of the website key
  • Service : e-mandates
  • Authorization reference: Mandaat reference
  • Description: Description of the e-mandate
  • Direct debit type: Continuous / One-off
  • Reference: Number associated with mandate
  • Customer number: Debtor number

In the following cases, the use of the Buckaroo intermediate page is a good addition:

  • When sending an email asking to confirm an authorization
  • For the confirmation of a direct debit e-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 has an unlimited validity. This enables the Merchant to share this URL with the debtor by e-mail or another digital medium. The link can only be used once to come to a valid e-Mandate. If the first attempt fails, a new link needs to be provided.

Withdrawing en e-Mandate B2B

For a B2B e-Mandate it is possible to withdraw an e-Mandate. The banks offer a separate message flow for this. This message can be sent to the various banks via Buckaroo. In this case, it is sufficient to state the mandate reference as an identifier and the fact that it must be withdrawn. The reason for the option to withdraw from a B2B e-Mandate is because cancellation is not possible on a Debtor initiative. The funds that are collected with a SEPA Direct Debit with an e-Mandate can only be reclaimed through legal proceedings.

Withdraw an e-Mandate B2C / Core

It is not possible to withdraw a B2C e-Mandate. As an alternative, the banks offer a blocking list. This list is part of the consumer's banking environment and can block an individual mandate as well as a complete collector. This means that a mandate previously provided with an e-Mandate can still end up in a reject (cancellation) on the initiative of the bank. The reason that the withdrawal of an e-Mandate is not supported by the banks is related to the right to cancel within 8 weeks. Even after an e-Mandate has been issued, it remains possible for consumers to reverse the funds.

e-Mandate number versus Mandaat reference

Various terms are used interchangeably within the SEPA Direct Debit product. Therefore below an explanation and a drawing:

Mandate Reference

  • A mandate reference is a unique number generated by the Merchant for Sepa DirectDebit contract, this is also applicable when using e-Mandates
  • Is passed on to the bank together with a mandate date (date of authorization)
  • Verplicht voor alle machtigingen met elektronische en natte handtekening

    Mandatory for all mandates as well as electronic and traditional signatures

e-Mandate number

  • Unique number generated by the Bank as a reference to the electronic consent
  • Can optionally be given to direct debit
  • An notification of a not authorized SEPA Direct Debit (in dutch : MOI) is not possible with B2B and B2C
  • Authorization can only be issued on available accounts within the online banking environment
  • Reversal within the 56 days after a SEPA Direct Debit is also not possible with B2B