Standards:IG Jade CreditTransferReply

Cette page est à l'état de discussion.

Elle n'a donc aucune valeur normative, et pourrait même disparaître du périmètre de SEPAmail.

Si vous voulez contribuer, utilisez la page de discussion SVP. Consultez également les autres pages en discussion.

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 reply to a “Credit Transfer Advise” message.

The full name of this message is sepamail_message_credit.activation_CreditTransferReply.

This message must be generated on behalf of the creditor, and sent by itself or by its bank. It MUST NOT be emitted if the incoming message didn't require a reply.

This message is based upon ISO 20022 pain.001 message. For adaptability reasons, it also includes non-ISO parts. All message parts are described in this document.

Message Root

Mult	Message Element	SEPAmail requirement
[1..1]	+ CreditTransferReply

Internal abstraction level

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

Mult	Message Element	SEPAmail requirement
[1..1]	sepamail_message_credit_activation_credit_transfer_reply_001	First version of the structure

ISO and Non-ISO parts

Ref	Mult	Message Element	SEPAmail requirement
A	[1..1]	++ Transfer	some version of the pain.001 message
B	[1..1]	++ Complement	Non-ISO part, described further in this document.
C	[0..1]	++ Signature	Digital signature of the message by the creditor. MUST be present if a signature was requested by initiating party. is_present($(self)) <=> CreditAdvise:B5.1 == "signature"

ISO Part : Transfer

The whole contents of this part MUST be copied directly from the matching part of the “Credit Transfer Advise” message, with no modification whatsoever.

Please see the incoming message page for more information.

A == CreditAdvise:A

Non-ISO Part : Complement

This part of the message adds information used by the SEPAmail/JADE system, to provide users with richer functionalities.

If the original message required an agreement, this part must indicate whether or not the agreement was accepted.

In any case, it can also carry a free-form message from the beneficiary to the original sender.

Ref	Mult	Message Element	SEPAmail requirement
B1	[1..1]	+ Status	Code describing the status of the request. Usage rule: allowed values are "accepted" (accepted by recipient), "rejected" (rejected by recipient), "unknown" (QXBAN does not match an account able to receive transfers) and "unavailable" (the service as described is not provided by the bank).
B2	[1..1]	+ Agrmt	Describes whether the recipient accepted or declined the proposed agreement. All fields except the last one (B1.3) MUST match those of the incoming message.
B2.1	[1..1]	++ Type	Type of agreement required (and provided). $(self) == CreditAdvise:B5.1
B2.2	[1..1]	++ Description	Formal sentence which the recipient accepted or declined. $(self) == CreditAdvise:B5.2
B2.3	[0..*]	++ DocRef	Reference to one or several of the incoming documents. every B2.3 satisfies some CreditAdvise:B5 satisfies B2.3 == CreditAdvise:B5.3
B2.4	[0..1]	++ Accepted	Mandatory: true if the recipient accepted the sentence, false if he declined it.
B3	[0..1]	+ IBAN	recipient's IBAN, if a QXBAN was provided in the incoming message and the payment was accepted. is_present($self) <=> ((CreditAdvise:Creditor:IBAN ~ "^QX") and (B2.4 == "accepted"))
B4	[0..1]	+ Comment	Any text the recipient wishes to communicate to the initiator.

</svnig>