IG Test SimpleTestRequest
- 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
<svnig date="Thu Sep 13 16:05:36 GMT+01:00 2012" revision="" repository="Test" last="" conversion="none" source="SplReq_Intro.txt">
Introduction
This message is the simplest of all test messages -- and currently, the only one. It is designed to allow any party to test its SEPAmail communication, without generating any undue traffic.
This message may be sent by anyone to anyone, in a nominal missive. It must be accepted by any SEPAmail member, and an acknowledgement missive must of course be sent. The answer to this message is a Test SimpleTestReport message.
This message must be signed and crypted as any other SEPAmail message. </svnig>
<svnig date="Thu Sep 13 16:05:36 GMT+01:00 2012" revision="" repository="Test" last="" conversion="none" source="SplReq_Body.txt">
Message Body
This message is strictly non-ISO. It can hold two kinds of contents, text or binary, or possibly both.
In the body of the message, only the Id is mandatory. All elements will be sent back unchanged by the report.
</svnig>
<svnig date="Thu Sep 13 16:05:36 GMT+01:00 2012" revision="" repository="Test" last="" conversion="tab" source="SplReq_Body.tab">
| Ref | Mult | Message Element | SEPAmail requirement |
|---|---|---|---|
| A | [1..1] | + SimpleTestRequest | Base element |
| A1 | [1..1] | ++ TestId | Unique identifier for current test. |
| A2 | [0..1] | ++ Text | Textual part |
| A3 | [0..1] | ++ Data | Binary part, base64 coded |
</svnig>