IG Secure EnrollAdvise

SEPAmail – Norme 1206
Cette page fait partie de la version 1206 de la norme. Sauf indication contraire, elle a été validée par les instances concernées et s'impose à tous les adhérents SEPAmail. ATTENTION ! La version 1606 de la norme est disponible, vérifiez si cette page est toujours valable.

These implementation rules shall be applied in accordance with ISO20022 and SEPA own implementation rules. Thus, unless explicitly specified, data contained within a field or XML structure of a SEPAmail message must comply with the constraints related to the equivalent field or XML structure in ISO20022 or SEPA messages.
for an explanation of the color coding used in the tables below, see this page
for general rules applying to all fields, see this page
for business rules directing these IG, see this page

Introduction

This document describes the contents of the Sepamail message used to advise all actors of the enrollment of a new member, either bank or creditor.

The full name of this message is sepamail_message_secure_EnrollAdvise.

This message can only be generated and sent by an organization receiving an EnrollRequest message, whether this message has been sent by a bank joining the Sepamail system, or by an individual or corporation wishing to use its services.

The EnrollAdvise message has two aims :

transmitting the certificate(s) for the new member to existing members, after all due verification has been made on them. This allows all other members to accept these certificates without any further checks, if they wish. Typically, this message would be transmitted by the scheme manager. Similarly, this message can be used to advise other members of the removal or deactivation of some certificates.
notifying all members that a new party has enrolled. This allows all other members, in the case of a BIC, to send delayed messages with this BIC as recipient.

This message is not based upon any existing ISO schema, since no such message exists in their model. Thus, it only includes a non-ISO part, described here. </svnig>

Root element

To facilitate upgrades, an indirection level has been inserted at the root of this element.

The root element is fixed, but it can be of different types. Currently, only the sepamail_message_secure_enroll_advise_001 type is available. </svnig>

Mult	Message Element	Sepamail requirement
[1..1]	EnrollAdvise

</svnig>

EnrollAdvise body

This part of the message describes the identification of the person/corporation having just enrolled, and the associated certificate(s).

</svnig>

Ref	Mult	Message Element	Sepamail requirement
A1	[1..1]	++ CreDtTm	Creation date and time, ISO format
A2	[1..1]	++ Sndr	Mandatory : identification of sender
A3	[1..1]	++ SndrBIC	Mandatory : BIC of sender
A4	[1..1]	++ CdtrQxCard	Mandatory, description of new Creditor (or party)
A4.1	[1..1]	+++ PartyName	Mandatory, text-only identifier of party. This should be the legal identifier (registered name, for instance)
A4.9	[0..1]	+++ DisplayName	Party name, as will be displayed
A4.2	[1..1]	+++ RIS2D	Mandatory
A4.3	[0..1]	+++ Test	should be set to “true” if this is a testing-only party
A4.4	[1..1]	+++ QXBAN	Mandatory, standard IBAN2007 format, QXBAN recommended.
A4.5	[0..1]	+++ ICQX
A4.6	[0..n]	+++ Services	Describes Sepamail applications supported by party. Possible values are "GEMME", "RUBIS" and "JADE
A4.7	{Or	+++ DbtrElements	Debtor-specific elements, currently none.
A4.8	Or}	+++ CdtrElements	Creditor-specific elements
A4.8.1	[0..1]	++++ Logo
A4.8.2	[0..1]	++++ Thumbnail
A4.8.3	[0..n]	++++ customerHelp	Elements describing where the customer reference8 may be found by the debtors
A4.8.3.1	[1..1]	+++++ identifierName	Mandatory, used to differentiate identifiers
A4.8.3.2	[1..n]	+++++ helpText	Textual parts
A4.8.3.3	[0..n]	+++++ helpImage	Illustrations, if necessary
A5	[1..n]	++ CommunicationElement	Mandatory. One such element must be present for each certificate the sender wishes to communicate to the receivers. Normally, all certificates submitted by the member should be sent to all other members.
A5.1	[1..1]	+++ CertifId	Mandatory. This identifier must be present but is not used in the current flow of messages.
A5.2	[1..1]	+++ Allow	Mandatory. This boolean indicates whether the certificates is being added to the Sepamail system (true), or removed from the system (false). Although it is possible, in the same message, to remove some certificates and add some other ones, this practice is discouraged.
A5.3	[1..1]	+++ SignKey	Mandatory. Contains the signing certificate.
A5.3.1	[0..1]	++++ KeyName	Mandatory. Indicates the element upon which the certificate is based. For inter-bank enrollment, this should be a mail address. For other cases, other identifiers are possible.
A5.3.2	[0..1]	++++ KeyValue
A5.3.3	[0..1]	++++ RetrievalMethod
A5.3.4	[0..1]	++++ X509Data	Mandatory, with all available sub-elements filled in.
A5.3.5	[0..1]	++++ PGPData
A5.3.6	[0..1]	++++ SPKIData
A5.3.8	[0..1]	++++ Other
A5.4	[1..1]	+++ CryptKey	Mandatory. Contains the ciphering certificate.
A5.4.1	[0..1]	++++ KeyName	Mandatory. Indicates the element upon which the certificate is based. For inter-bank enrollment, this should be a mail address. For other cases, other identifiers are possible.
A5.4.2	[0..1]	++++ KeyValue
A5.4.3	[0..1]	++++ RetrievalMethod
A5.4.4	[0..1]	++++ X509Data	Mandatory, with all available sub-elements filled in.
A5.4.5	[0..1]	++++ PGPData
A5.4.6	[0..1]	++++ SPKIData
A5.4.7	[0..1]	++++ MgmtData
A5.4.8	[0..1]	++++ Other
A5.5	[1..n]	+++ Family	Mandatory. Designates the message ecosystem(s) for which the certificate will be used. Possible values are test, secure, direct.debit and payment.activation

</svnig>

IG Secure EnrollAdvise

Introduction

Root element

EnrollAdvise body

Navigation menu

Search