2. eMandates Solution Overview - Betaalvereniging-Nederland/emandates-libraries-dotnet GitHub Wiki

A brief description of eMandates and the underlying iDx protocol.

Basic Product Description

eMandates is a service for issuing, amending and cancelling online mandates for SEPA Direct Debits. The eMandate information is exchanged between Creditor, Routing Service and Validation Service using iDx as a messaging standard. The eMandates solution uses the ISO XML 20022 standard eMandate messages to convey eMandate specific data. The generic information-container in the iDx protocol is filled with the ISO messages.

eMandates uses four different ISO messages for specific purposes:

  • Pain.009 for new eMandate requests
  • Pain.010 for amendment requests to existing eMandates
  • Pain.011 for cancellation requests of existing eMandates (B2B eMandates only)
  • Pain.012 for the acceptance report containing the actual eMandate

eMandates uses the three iDx protocols:

  • Directory protocol: this protocol is run between the Creditor and Routing Service only. Its purpose is to retrieve the list of Validation Services that participate in eMandates;
  • Transaction protocol: this is run between the Creditor, Routing Service and Validation Service to initiate the issuing, amendment or cancellation of an eMandate;
  • Status protocol: this is run between the Creditor, Routing Service and Validation Service to retrieve the status of an eMandate from the Validation Service, after a transaction protocol has been run. If an eMandate has been approved by the Debtor and no errors have occurred in the transaction, the response from the Validation Service in the status protocol contains the signed eMandate.

eMandates Creditor Libraries Overview

The eMandates Creditor Libraries are a set of software libraries created to facilitate the integration of Creditors with Creditor Banks for supporting eMandate payment methods based on the iDx standards. The libraries are responsible for validating and authenticating incoming messages against its XML schema and the Creditor Bank’s certificate. The libraries save Creditors the need to implement all functionality described in the eMandates product and iDx standards.

The eMandates Creditor Libraries expose the following operations:

  • Retrieve the list of the Debtor Banks accepting eMandates;
  • Issuing an eMandate;
  • Amending an existing eMandate;
  • Cancelling an existing eMandate (for B2B only);
  • Retrieve Issuing/Amending/Cancelling eMandate Transaction status.

Glossary

The following terms are used in this document, related to the eMandates service:

  • The Creditor: the owner of a web application in which eMandates is a payment method (also called a Merchant).
  • The Creditor Bank: the bank with which the Creditor has a contract for the eMandates solution, sometimes also referred to as the Acquirer.
  • The Debtor: the customer who wants to issue a new eMandate, amend an existing eMandate or cancel an existing eMandate.
  • The Debtor Bank: the bank that communicates on behalf of the Debtor, sometimes referred to as the Issuer.
  • Routing Service: the technical role that handles the acquiring side of the transaction.
  • Validation Service: the technical role that handles the issuing side of the transaction.