Outils personnels

The standard

De documentation SEPAmail.

Cette page est une traduction de la page La norme et la traduction est complétée à 100 % et à jour.

Modèle:TOC:standard

General principles of the standard

Introduction : numbering

Each version of the standard is identified by a 4 digits number, with the format YYMM. The version 1206 is then dated in June 2012 for instance. The steering committee decides the frequency and the content of successive versions.

The version 1206 of the standard changed many items compared to the previous version, 1202. As a summary, we may even consider that this version changed everything.

On the other hand, the future versions of the standard will not necessarily have the same impact. They may content themselves to limited evolutions of some messages or ecosystems, even to let them completely unchanged – just adding for instance one or several new applications.

The version numbers of all messages may then be different from the standard version number itself: if these messages have not changed since the previous version of the standard, they will keep the same version number. We can consider that the version number of the standard is the maximum numbers of the messages and the missives included.

Scope

The diagram below shows a representation of the scope of the SEPAmailmessagerie bancaire sécurisée. standards specifications:

le périmètre des spécifications

Within a banking SEPAmailmessagerie bancaire sécurisée. member, there are 4 types of main functional components:

  • SMARTinterface SEPAmail entre deux adhérents au réseau SEPAmail (SepaMail Acknowledgment, Routing and Transfer) which receives and sends missives in the SEPAmailmessagerie bancaire sécurisée. members network (interbank cooperative space)
  • the business components related to payment:
    • RUBISRèglement Universel Bancaire Immédiat & SEPA (application SEPAmail), related to payment request, managing RUBISRèglement Universel Bancaire Immédiat & SEPA (application SEPAmail) messages (linked to the payment.activation ecosystem)
    • GEMMEGlobal European Mandate Management & Exchange (Application SEPAmail), related to money order signature, managing GEMMEGlobal European Mandate Management & Exchange (Application SEPAmail) messages (linked to the direct.debit ecosystem)
  • one security business component:
    • SAPPHIRESecurity, Authentication, Privacy, Public Key Infrastructure, Highly Innovative, Interoperable, Reliable & Exchange, related to authentication and to authentication components exchange, managing SAPPHIRESecurity, Authentication, Privacy, Public Key Infrastructure, Highly Innovative, Interoperable, Reliable & Exchange message (linked to the ecosystem secure)
  • SMILEinterface SEPAmail entre une banque et ses clients which receives and sends missives in the bank customers network (intrabank competitive space)


The documents of the standard are:

  • the XML diagrams and their implementation directives
  • the comments requests (SMIRKacronyme SEPAmail SepaMail Internal Request for Komment, équivalent d'un RFC pour SEPAmail. in blue)
  • business rules (in green)
    • RUBISRèglement Universel Bancaire Immédiat & SEPA (application SEPAmail)
    • GEMMEGlobal European Mandate Management & Exchange (Application SEPAmail)
  • Functional and technical specifications
    • API SMARTinterface SEPAmail entre deux adhérents au réseau SEPAmail (SepaMail Acknowledgment, Routing and Transfer) (file and web-service)
    • exchange protocols
    • XML validation
    • companies and applicationune application SEPAmail est liée à un service bancaire proposé. Elle peut se définir comme une séquence de messages utilisant le dispositif technique SEPAmail providers guide
Autres langues :English 100% • ‎Français 100%