Customer Documentation Request for Information Message (camt.026 & camt.028)

Transcription

1 Customer Documentation Request for ormation Message (camt.026 & camt.028) Version 2.2 April 2018

2 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT"). ANY USE OR REPRODUCTION OF THE DOCUMENT CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. This Agreement is an agreement between Recipient and The Clearing House Payments Company, L.L.C. ( Payco ). Capitalized terms used but not defined in this Agreement shall have the meanings given to such terms in the Real-Time Payments Operating Rules or Real-Time Payments Participation Rules released by Payco from time to time (collectively, the Rules ) which are available for download at Payco s website, For purposes of this Agreement, Recipient means the person who receives this Document from Payco or, if the person who receives this Document from Payco is the representative of a juristic person, that juristic person. Subject to the terms of this Agreement, Payco hereby grants Recipient a worldwide, nonassignable, non-sublicensable, non-transferable, non-exclusive, royalty-free copyright license to reproduce this Document and prepare derivative works of this Document that are products and services that integrate with the Real-Time Payments service provided by Payco ( Works ) and publicly display, publicly perform, distribute and sublicense the Works (the License ). As a condition to exercising the rights and licenses granted hereunder, Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Works, it is Recipient's responsibility to acquire that license before distributing the Works. The Document is the property of Payco and Payco retains all right, title, and interest in and to the proprietary rights expressed in this document and the information contained therein. Recipient shall not disclose the Document to any third party and no rights in the Document are granted other than those specifically authorized by the License. Any reproduction of the Document must reproduce this Agreement, including partial copies. The Document must be returned to Payco or the Works and Document must be destroyed immediately, upon Payco s request. In the event of such a request, Recipient will provide a certification if it is a natural person, or a certification of a senior officer or executive if it is a representative of a juristic person, that all copies of the Document and Works have been destroyed or returned to Payco as required. If you are a Participant, you acknowledge and agree that this agreement and the licenses granted hereunder are subject to your Participant Agreement and the Rules, and you agree that nothing herein shall relieve you of your obligation to comply with the foregoing. In the event of a conflict between this Agreement and the Participant Agreement or the Rules, the Participant Agreement or the Rules, as applicable, shall control. EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON The Clearing House Payments Company L.L.C. 2

3 INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Recipient is solely responsible for determining the appropriateness of using the Document and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. Recipient shall, at its sole cost and expense, indemnify and hold Payco and its affiliates harmless from and against any and all damages arising out of or related to Recipient s use and reproduction of the document and works. PAYCO SHALL HAVE NO LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR REPRODUCTION OF THE DOCUMENT OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER BY RECIPIENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. If Recipient institutes patent litigation against Payco or any affiliate of Payco (including a crossclaim or counterclaim in a lawsuit) alleging infringement of Recipient's patent(s), then the License of this Agreement shall terminate as of the date such litigation is filed. All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use of the Document and Works as soon as reasonably practicable. However, Recipient's obligations under this Agreement shall continue and survive. This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. Each party waives its rights to a jury trial in any resulting litigation The Clearing House Payments Company L.L.C. 3

4 CHANGES VERSION 2.0 TO VERSION 2.1 Request for ormation Message Version 2.2 Section Change Comments 2.1 Alignment with ISO specification for camt Element Missing Or Incorrect ormation Note: The AMLReq field showed in the array is not used within RTP and is not present in either the Message Old Structure: Structure Description or Detail Message Field Descriptions. New Structure: Added Occurrence ormation overview This section was added to clarify the meaning of Occurrence within the Message Structure Description and Detail Message Field Descriptions. 1.6 Expanded Date Validation to include both Date and Participant Identification Validation Occurrence column updated to reflect RTP-specific usage rather than ISO general requirements. (These changes are also reflected in the Detail Message Field Descriptions for fields noted.) Validation was added to ensure that the participant ID included within the unique identifier for the message belongs to the sender of the message. The following fields were updated from [0..1] to [1..1]: M/O/C column updated to reflect RTP product usage. The following fields were updated as noted: - 4.6: O field changed to C Assignment Identification (Index 1.1) format extended to 35 characters (originally defined as 31 characters). Product Usage updated to reflect that Assignment Identification is used for duplicate checking by the system. Additionally, a Rule is noted to show that the first 20 characters of Assignment ID are validated structurally. If the structure is not as defined, RTP will reject with an Administration Advice message with Reason Code 650. V2.0 format description: Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (9 digit Routing and Transit Number) Pos Message generation source ("B" if generated by a TCH FI) Pos Alphabetic serial identifier (2 alphabetic characters) Pos Message serial number ( The Clearing House Payments Company L.L.C. 4

5 The example was updated to reflect the format change. numeric characters) Assigner Agent / Member Identification (Index 1.53) was updated to include a note regarding validation of the Member ID Original Message Identification (Index 3.16) updated to include a note regarding system validation Updated examples of Original Message Identification (Index 3.16), Original Instruction Identification (Index 3.2), and Original Transaction Identification (Index 3.22) to reflect the expected format of these identifiers Occurrence column updated to reflect RTP-specific usage rather than ISO general requirements. (These changes are also reflected in the Detail Message Field Descriptions for fields noted.) V2.1 format description: Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (11 digit Participant ID) Pos Message generation source ("B" if generated by a TCH FI) Pos Alphabetic serial identifier (3 alphabetic characters) Pos Message serial number (11 numeric characters) Note: The system validates that the participant indicated in the Assignment ID (positions 10-20) owns the Routing and Transit Number contained within this field. Note: The system does not validate the information within this field. None. The following fields were updated from [0..1] to [1..1]: M/O/C column updated to reflect RTP product usage. The following fields were updated as noted: : M field changed to C (Note, this field is required when Rmt is present, which is required when information related to the Request for ormation cannot be provided. The field may optionally be used to return information related to the original Request for ormation that cannot be provided in other fields included within the camt.028 message Assignment Identification (Index 1.1) format extended to 35 characters (originally defined as 31 characters). Product Usage updated to reflect that Assignment Identification is used for duplicate checking by the system. V2.0 format description: Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (9 digit Routing and Transit Number) 2018 The Clearing House Payments Company L.L.C. 5

6 Additionally, a Rule is noted to show that the first 20 characters of Assignment ID are validated structurally. If the structure is not as defined, RTP will reject with an Administration Advice message with Reason Code 650. The example was updated to reflect the format change Assigner Agent / Member Identification (Index 1.53) was updated to include a note regarding validation of the Member ID The note within Case ID (Index 2.1) was updated to clarify that the field references the original Request for ormation message Examples within Detail Message Field Descriptions were updated or added for the fields noted Product Usage of Original Transaction Identification (Index 3.22) was updated for clarity Updated the table labels for End-to-End Identification (Index 4.2) and Transaction Identification (Index 4.4) as needed Updated the product usage of the Remittance ormation (index 4.745) field for clarity. Pos Message generation source ("B" if generated by a TCH FI) Pos Alphabetic serial identifier (2 alphabetic characters) Pos Message serial number (10 numeric characters) V2.1 format description: Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (11 digit Participant ID) Pos Message generation source ("B" if generated by a TCH FI) Pos Alphabetic serial identifier (3 alphabetic characters) Pos Message serial number (11 numeric characters) Note: The system validates that the participant indicated in the Assignment ID (positions 10-20) owns the Routing and Transit Number contained within this field. Previously, the note stated that the field identified the original message None Error in table formatting identified from version 2.0. This is a conditional field which must be used if the Debtor cannot provide the requested information. The field may optionally be used to provide additional information regarding the orginal Credit Transfer message that could not be provided in the fields above The Clearing House Payments Company L.L.C. 6

7 CHANGES VERSION 2.1 TO VERSION 2.2 Section Change Comments Request for ormation Message Version Removed section 1.6 Validation Validation rules are generally captured within Detailed Message Field Descriptions Removed reference to The Clearing House Message Status Report Version Updated Reason Codes within Assigner Agent Member ID (Index 1.53): - Removed reason code RC04 - Indicated that if the Assigner Agent Member ID does not exist in RTP, the system will reject the message with an admi.002 (reason 650) Provided a generic reference to the Message Status Report specification, where additional information can be found. None Added Rule and Reason Code. Creation Date Time must be within one calendar day of the system s date/time or the message will be rejected with a pacs.002 and reason code DT Updated note in Original Transaction Identification to provide reference to the Payment ormation Identification from the pain Removed reference to The Clearing House Message Status Report Version Updated Product Usage of Assignment Id (Index 1.1) for clarity Updated Reason Codes within Assigner Agent Member ID (Index 1.53): - Removed reason code RC03 - Indicated that if the Assigner Agent Member ID does not exist in RTP, the system will reject the message with an admi.002 (reason 650) Updated Occurrence of Original Instruction ID (Index 3.20) from [0..1] to [1..1]. Previously, this note referred to the Payment ormation Identification as Payment Identification. This change is for clarification only. Provided a generic reference to the Message Status Report specification, where additional information can be found. The Assignment ID uniquely identifies the camt.028 message. None. While the Detailed Message Field Description previously indicated that this field was optional, the Message Structure in section indicated that the field was required The Clearing House Payments Company L.L.C. 7

8 CONTENTS Changes Version 2.0 to Version CHANGES VERSION 2.1 TO VERSION Contents INTRODUCTION Document Purpose Scope Acronyms Message Format Description and Overall Message Structure Occurrence ormation Date / Time Format Message Structure Request for ormation and Response to Request for ormation Request for ormation camt Scope Message Structure Description Detail Message Field Description Response to Request for ormation camt Scope Message Structure Description Detail Message Field Description The Clearing House Payments Company L.L.C. 8

9 1 INTRODUCTION 1.1 Document Purpose 1.2 Scope This document defines the standard product message formats used within RTP, a real-time payment system from The Clearing House, for sending and receiving a Request for ormation message (camt.026) and the associated Response to Request for ormation (camt.028) message, between RTP and Participants using the System. Participants should use this document as a reference as they develop their messaging systems to send and receive Real-Time messages in ISO format. This document covers the following: The message structure of the camt.026 and the camt.028 message used in RTP The required data types and usage rules of the data fields in the messages This document does not include message flows for the camt.026 and camt Acronyms Acronym BAH ET ISO TPSP UNIFI XML Description Business Application Header Eastern Time International Standards Organization Third Party Service Provider Universal Financial Industry Message scheme Extensible Mark-up Language 2018 The Clearing House Payments Company L.L.C. 9

10 1.4 Message Format Description and Overall Message Structure Request for ormation Message Version 2.2 ormation about the message format and the overall message structure are provided in the document The Clearing House Business Application Header chapters: 2 Message Format Description 3 Overall Message Structure Occurrence ormation The Message Structure Description and Detail Message Field Description Sections include an Occurrence definition that indicates how each field is to be used within RTP. These occurrence notations have two element. The first character is a binary indicator to show whether a field is mandatory (1) or optional (0). The second character indicates how many occurrences of the field are allowed within RTP usage. This starts at 1 occurrence and can extend to an unlimited number n. Notation Description [1..1] Is a mandatory single field with one occurrence [0..1] Is an optional field with one occurrence [0..n] Is an optional field with unlimited occurrences Please note that RTP product usage of each field is consistent with, but not always equal to, ISO defined occurrence. For example, ISO may define a field as optional with one occurrence [0..1], but such field may be defined as required with one occurrence [1..1] within RTP. Further, if a field is a mandatory sub-element of an optional field, the occurrence represents the nature of the sub-element should the optional field be present. For example, while Date and Place of Birth (Index within the Credit Transfer (pacs.008) message) is an optional field, if it is present, Birth Date, City of Birth, and Country of Birth must also be present. Therefore, these fields are represented as being mandatory with a single occurrence ([1..1]) even though they may not be present in every Credit Transfer message. Index XML Tag Element Name Occurr. Length M/O/C DtAndPlcOfBirth Date And Place Of Birth [0..1] C BirthDt Birth Date [1..1] 10 C CityOfBirth City Of Birth [1..1] 35 C CtryOfBirth Country Of Birth [1..1] 2 C 1 M mandatory / O optional / C - conditional 2018 The Clearing House Payments Company L.L.C. 10

11 1.5 Date / Time Format All message processing dates are required to be set to Eastern Time (Easter Standard Time or Eastern Daylight Time, as applicable according to the Energy Policy Act of 2005) by the message sender. This includes the following fields: Creation Date Time Interbank Settlement Date (set by RTP) Date field within the Business Reference field Date field within the Message Identification field Date field within the Instruction Identification field Date field within the Transaction Identification field 2018 The Clearing House Payments Company L.L.C. 11

12 2 MESSAGE STRUCTURE REQUEST FOR INFORMATION AND RESPONSE TO REQUEST FOR INFORMATION 2.1 Request for ormation camt Scope The Request for ormation (camt.026) message is sent by the Creditor Customer to the Debtor Customer through their FIs. The message is used by the Creditor Customer to initiate a request for additional information from the Debtor Customer. This will likely be done when the Creditor needs additional information in order to apply a payment. Upon receipt of the Request for ormation (camt.026), the Debtor FI must send a Message Status Report (pacs.002) confirming that the Request for ormation (camt.026) was processed or indicating that the Request for ormation (camt.026) could not be processed with the appropriate rejection code (e.g. AC03). For detailed information on Message Status Report (pacs.002) please see the Message Status Report specification Message Structure Description Index XML Tag Element Name Occurr. Length M/O/C UblToApply Unable To Apply V05 [1..1] M 1.0 Assignment [1..1] M 1.1 Id Identification [1..1] 35 M 1.2 Assgnr Assigner [1..1] M 1.46 Agt Agent [1..1] M 1.47 FinInstnId Financial Institution Identification [1..1] M 1.49 ClrSysMmbId Clearing System Member Identification [1..1] M 1.53 MmbId Member Identification [1..1] 9 M 1.86 Assgne Assignee [1..1] M Agt Agent [1..1] M FinInstnId Financial Institution Identification [1..1] M ClrSysMmbId Clearing System Member Identification [1..1] M MmbId Member Identification [1..1] 9 M CreDtTm Creation Date Time [1..1] 19 M 2.0 Case Case [1..1] M 2.1 Id Identification [1..1] 35 M 2.2 Cretr Creator [1..1] M 2.3 Pty Party [1..1] M 2.4 Nm Name [1..1] 140 M 3.0 Undrlyg Underlying [1..1] M 3.14 IntrBk Interbank [1..1] M 3.15 OrgnlGrp Original Group ormation [1..1] M 3.16 OrgnlMsgId Original Message Identification [1..1] 35 M 3.17 OrgnlMsgNmId Original Message Name Identification [1..1] 35 M 3.18 OrgnlCreDtTm Original Creation Date Time [1..1] 19 M 2018 The Clearing House Payments Company L.L.C. 12

13 Index XML Tag Element Name Occurr. Length M/O/C 3.20 OrgnlInstrId Original Instruction Identification [1..1] 35 M 3.21 OrgnlEndToEndId Original End To End Identification [0..1] 35 O 3.22 OrgnlTxId Original Transaction Identification [1..1] 35 M 3.23 OrgnlIntrBkSttlmAmt Original Interbank Settlement Amount [1..1] 18 M 3.24 Ccy Currency [required] 3 M 3.25 OrgnlIntrBkSttlmDt Original Interbank Settlement Date [1..1] 10 M 4.0 Justfn Justification [1..1] M 4.2 MssngOrIncrrct Missing Or Incorrect ormation [1..1] M 4.4 Mssng Missing ormation [0..10] C 4.5 Cd Code [1..1] 4 M 4.6 AddtlMssng Additional Missing ormation [0..1] 140 C 4.7 Incrrct Incorrect ormation [0..10] C 4.8 Cd Code [1..1] 4 M 4.9 AddtlIncrrct Additional Incorrect ormation [0..1] 140 C Detail Message Field Description The following section provides the detailed information of each element used in the Request for ormation message for RTP. In some cases, a single field has two different meanings: the ISO Definition, and the RTP Product Usage. these instances, the first definition is based on the ISO specification provided by the ISO RMG group. The second definition is the definition The Clearing House developed for the product usage of this element within the RTP implementation. The second definition is only provided where the RTP product usage is different from the ISO group specification, or where more detailed information of the usage of this field is required. For the ISO Definition and further detail on the message itself please refer to the official ISO website ( Unable to Apply V05 Assignment Identifies the assignment of an investigation case from an assigner to an assignee. Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver. Index: 1.0 <> 2018 The Clearing House Payments Company L.L.C. 13

14 Identification +Id Product Usage: Uniquely identifies the case assignment. Assigned by Creditor FI to uniquely identify the message. The uniqueness of a Request for ormation is determined by the Assignment Identification and is based on the format below. RTP will use the Assignment ID to perform a check for a duplicate transaction within the duplicate checking period and as a reference to the payment instruction in other non-payment messages (i.e. Response to Request for ormation). Index: 1.1 <Id> Format: Format: MYYYYMMDDbbbbbbbbbbbBAAAnnnnnnnnnnn Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (11 digit Participant ID) Pos Message generation source ("B" if generated by a TCH FI) Pos Alphabetic serial identifier (3 alphabetic characters) Pos Message serial number (11 numeric characters) Rules: The first 20 characters of Assignment Identification (positions 01-20) are validated for structural alignment in accordance with the format specification. Reason Codes: Business validations for the Assignment Identification include: Embedded date (positions 02-09) must be within 1 calendar day of the system date. Embedded Participant ID (positions 10-20) must be owned by the Instructing Agent. Reject with Message Status Report (pacs.002) if: Assignment Identification matches a previously completed transaction (DUPL); Embedded date is not within 1 calendar day of the system date (DT04) Participant ID is not owned by the Instructing Agent (DS0H) If structural validation fails, reject with reason code 650 in Administration Advice message (admi.002). <Id>M BRFIA <Id/> Assigner +Assgnr Produt Usage: Party who assigns the case. Usage: This is also the sender of the message. Creditor FI requesting further information from the Debtor FI The Clearing House Payments Company L.L.C. 14

15 Index: 1.2 <Assgnr> Agent +Assgnr ++Agt Identification of a financial institution. Index: 1.46 <Agt> Financial Institution Identification +Assgnr ++Agt +++FinInstnId Index: 1.47 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. <FinInstnId> Clearing System Member Identification +Assgnr ++Agt +++FinInstnId ++++ClrSysMmbId Index: 1.49 ormation used to identify a member within a clearing system. <ClrSysMmbId> Member Identification +Assgnr ++Agt +++FinInstnId ++++ClrSysMmbId +++++MmbId Product Usage: Index: 1.53 Identification of a member of a clearing system. The 9 digit Routing and Transit Number of the FI initiating the Request for ormation message (Creditor FI). <MmbId> Format: Rules: Reason Codes: 9 digit Routing and Transit Number Member Identification must be a valid 9 digit Routing and Transit Number. Reject with Message Status Report (pacs.002) if: 2018 The Clearing House Payments Company L.L.C. 15

16 Note: Sender is not authorized to send this specific message (reason code 'AG03') agent is signed off (reason code 9934 ) agent is suspended (reason code 9946 ) the sender of the message is not authorized to submit messages on behalf of this agent (reason code DS0H ) Reject with admi.002 (reason 650) if Routing and Transit number does not exist in RTP. The system validates that the participant indicated in the Assignment ID (positions 10-20) owns the Routing and Transit Number contained within this field. <MmbId> </MmbId> Assignee +Assgne Party to which the case is assigned. Usage: This is also the receiver of the message. Product Usage: Index: 1.86 Debtor FI to whom the Request for ormation message from the Creditor FI has been sent. <Assgne> Agent +Assgne ++Agt Identification of a financial institution. Index: <Agt> Financial Institution Identification +Assgne ++Agt +++FinInstnId Index: Unique and unambiguous identification of a financial institution, as assigned under an internationally recognized or proprietary identification scheme. <FinInstnId> 2018 The Clearing House Payments Company L.L.C. 16

17 Clearing System Member Identification +Assgne ++Agt +++FinInstnId ++++ClrSysMmbId Index: Request for ormation Message Version 2.2 ormation used to identify a member within a clearing system. <ClrSysMmbId> Member Identification +Assgne ++Agt +++FinInstnId ++++ClrSysMmbId +++++MmbId Product Usage: Index: Identification of a member of a clearing system. The 9 digit Routing and Transit Number of the FI receiving the Request for ormation message (Debtor FI). <MmbId> Format Rules: Reason Codes: 9 digit Routing and Transit Number Member Identification must be a valid 9 digit Routing and Transit Number Reject with Message Status Report (pacs.002) if: Routing and Transit number is not supported in RTP (reason code 'RC03') Routing and Transit number is not authorized to receive this business message (reason code 'AG03') Agent is signed-off (reason code '9910') Agent is suspended (reason code '9947') Receiver connection is not available (reason code 9912 ) <MmbId> </MmbId> Creation Date Time +CreDtTm Product Usage: Date and time at which the assignment was created. The date and time the assignment was created. Index: <CreDtTm> Format Rule: YYYY-MM-DDThh:mm:ss Creation Date Time must be within one calendar day of the system s date/time The Clearing House Payments Company L.L.C. 17

18 Reason Code: Note: Reject with code DT04 in pacs.002 for failing business validation. The date is required to be set to Eastern Time (ET). <CreDtTm> T10:09:33</CreDtTm> Case Case Identifies the investigation case. Index: 2.0 <Case> Identification Case +Id Product Usage: Index: 2.1 Uniquely identifies the case. The Identification for the Case uses the same Identification that was used for the Assignment. <Id> Format Note: This must be equal to the Assignment ID. Format specification see element Assignment/Id. <Id>M BRFIA </Id> Creator Case +Cretr Product Usage: Index: 2.2 Party that created the investigation case. Identity of the original Creditor associated with the Request for ormation message. <Cretr> Rule: Note: Only element Party / Name is allowed. This is a mandatory ISO field that will not be used by RTP The Clearing House Payments Company L.L.C. 18

19 Party Case +Cretr ++Pty Product Usage: Index: 2.3 Identification of a person or an organization. This field is used to identify the Creditor that initiated the Request for ormation message. <Pty> Name Case +Cretr ++Pty +++Nm Product Usage: Index: 2.4 Name by which a party is known and which is usually used to identify that party. Official name of the Creditor Customer as associated with the Creditor FI account that initiates the Request for ormation message. <Nm> <Nm>Creator Name</Nm> Underlying Undrlyg References the payment instruction or statement entry that a party is unable to execute or unable to reconcile. Product Usage: Index: 3.0 ormation about the underlying transaction for which this Request for ormation is created. Only the Interbank element is being used. <Undrlyg> Interbank Undrlyg +IntrBk Product Usage: Index: 3.14 Set of elements used to reference the details of the original interbank payment transaction. This element identifies the original pacs.008 and is provided either by the Creditor or the Creditor Agent (Creditor FI or TPSP of the Creditor FI) of the Request for ormation <IntrBk> 2018 The Clearing House Payments Company L.L.C. 19

20 Original Group ormation Undrlyg +IntrBk ++OrgnlGrp Index: 3.15 Request for ormation Message Version 2.2 Set of elements used to provide information on the original messsage. <OrgnlGrp> Original Message Identification Undrlyg +IntrBk ++OrgnlGrp +++OrgnlMsgId Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. Product Usage: Index: 3.16 Message identification from the original Credit Transfer (pacs.008) message that is being referenced. <OrgnlMsgId> <OrgnlMsgId>M BFFF </OrgnlMsgId> Original Message Name Identification Undrlyg +IntrBk ++OrgnlGrp +++OrgnlMsgNmId Product Usage: Index: 3.17 Specifies the original message name identifier to which the message refers. Specifies the type of the original message, to which this Request for ormation message is being used. <OrgnlMsgNmId> Rules: Reason Codes: Codes Expected value is pacs (for credit transfer) Reject with code '650' in Administration Advice message (admi.002) if Original Message Name Identification is not valid. <OrgnlMsgNmId>pacs </OrgnlMsgNmId> Name / Description pacs Credit Transfer Original Creation Date Time Undrlyg +IntrBk ++OrgnlGrp +++OrgnlCreDtTm Produt Usage: Date and time at which the original message was created. This date is referring to the original Credit Transfer (pacs.008) message The Clearing House Payments Company L.L.C. 20

21 Index: 3.18 <OrgnlCreDtTm> Format: Reason Codes: Note: YYYY-MM-DDThh:mm:ss Reject with code '650' in Administration Advice message (admi.002) if not a valid date. The date is required to be set to Eastern Time (ET). <OrgnlCreDtTm> T10:05:00</OrgnlCreDtTm> Original Instruction Identification Undrlyg +IntrBk ++OrgnlInstrId Unique identification, as assigned by the original instructing party for the original instructed party, to unambiguously identify the original instruction. Product Usage: Index: 3.20 The Instruction Identification of the Credit Transfer (pacs.008) message for which this Request for ormation message is being sent. <OrgnlInstrId> Note: This is the Identification from the pacs.008 assigned by the Debtor FI to uniquely identify a single payment instruction within a pacs.008 throughout its existence within the system. <OrgnlInstrId> BFFFF </OrgnlInstrId> Original End To End Identification Undrlyg +IntrBk ++OrgnlEndToEndId Product Usage: Index: 3.21 Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction. The End To End ID from the pacs.008 instruction for which this message is being sent. <OrgnlEndToEndId> <OrgnlEndToEndId>E2E-Ref001</OrgnlEndToEndId> 2018 The Clearing House Payments Company L.L.C. 21

22 Original Transaction Identification Undrlyg +IntrBk ++OrgnlTxId Product Usage: Index: 3.22 Request for ormation Message Version 2.2 Unique identification, as assigned by the original first instructing agent, to unambiguously identify the transaction. The unique identifier, assigned by the first instructing agent to unambiguously identify the transaction that is passed on unchanged throughout the entire interbank chain. This is the transaction identifier assigned by the original Debtor FI for the pacs.008 transaction and is a mandatory field. <OrgnlTxId> Note: If the Credit Transfer (pacs.008) message is based on a Request for Payment (pain.013) the original Payment ormation Identification from the pain.013 must be populated in this field. <OrgnlTxId> BIIAA </OrgnlTxId> Original Interbank Settlement Amount Undrlyg +IntrBk ++OrgnlIntrBkSttlmAmt Product Usage: Index: 3.23 Amount of money, as provided in the original transaction, to be moved between the instructing agent and the instructed agent. The total amount that the Debtor FI was obligated to pay the Creditor FI upon the Creditor FI s acceptance of the payment instructed by the original Credit Transfer (pacs.008) message. <OrgnlIntrBkSttlmAmt> Reason Codes: Note: Attribute: ISO Definition Reject due to structural validation failure with code '650' in Administration Advice message (admi.002) if: The value of the payment amount is less than or equal to zero The value of the payment is greater than supported by the ISO definition for the maximum number of digits (total 18 digit) The currency code is not valid (i.e. not USD) The number of decimal digits is greater than the specified number of digits as defined by the ISO4217 definition RTP is only supporting USD and the maximum decimal digits allowed are two. <OrgnlIntrBkSttlmAmt>520.15</OrgnlIntrBkSttlmAmt> Currency A code allocated to a currency by a Maintenance Agency under 2018 The Clearing House Payments Company L.L.C. 22

23 Index: 3.24 Rules: an international identification scheme, as described in the latest edition of the international standard ISO 4217 "Codes for the representation of currencies and funds". <Ccy> Currency must be a currency that is supported by RTP (US Dollar). Reason Codes: Reject with code '650' in Administration Advice (admi.001) message if the currency code is not supported by RTP. USD Original Interbank Settlement Date Undrlyg Date, as provided in the original transaction, on which the amount +IntrBk of money ceases to be available to the agent that owes it and when ++OrgnlIntrBkSttlmDt the amount of money becomes available to the agent to which it is due. Product Usage: The original Reconciliation Window of the Credit Transfer (pacs.008) message. Index: 3.25 <OrgnlIntrBkSttlmDt> <OrgnlIntrBkSttlmDt> </OrgnlIntrBkSttlmDt> Justification Justfn Explains the reason why the case creator is unable to apply the instruction Product Usage: To identify whether the requested information in the underlying transaction is missing or incorrect information, this element is used. Index: 4.0 <Justfn> Missing Or Incorrect ormation Justfn +MssngOrIncrrct Set of elements used to indicate which information is missing or incorrect. Index: 4.2 <MssngOrIncrrct> 2018 The Clearing House Payments Company L.L.C. 23

24 Note: If the Request for ormation message is being used to obtain information that was missing from the original message, then the element Missingormation is used. If the Request for ormation message is being used to obtain information that was incorrect in the original message, then the element Incorrectormation is used. For both elements there is the option to provide up to 140 characters of additional detailed information. Missing ormation Justfn +MssngOrIncrrct ++Mssng Indicates the missing information. Index: 4.4 <Mssng> Occurrences: [0..10] Code Justfn +MssngOrIncrrct ++Mssng +++Cd Indicates whether or not all available information on the underlying payment instruction is requested. Index: 4.5 <Cd> Codes MS01 NARR <Cd>MS01</Cd> Name / Description MissingRemittanceormation Remittance ormation is missing. Narrativeormation Narrative ormation, Additional Missing ormation must be present. Additional Missing ormation Justfn +MssngOrIncrrct ++AddtlMssng Provides additional information regarding the missing information. Product Usage: This field is mandatory with the code NARR and being used to provide additional information. Index: The Clearing House Payments Company L.L.C. 24

25 <AddtlMssng> <AddtlMssng>Unstructured ormation</addtlmssng> Incorrect ormation Justfn +MssngOrIncrrct ++Incrrct Indicates, in a coded form, the incorrect information. Index: 4.7 <Incrrct> Occurrences: [0..10] Note: Not all of the codes will be used. The final list will be provided at a later stage Code Justfn +MssngOrIncrrct ++Incrrct +++Cd Indicates whether or not all available information on the underlying payment instruction is requested. Index: 4.8 <Cd> Codes IN01 IN06 IN15 IN38 IN39 MM20 MM21 NARR <Cd>IN01</Cd> Name / Description IncorrectRelatedReference Related transaction reference is incorrect. IncorrectInterbankSettlementAmount Interbank settlement amount is incorrect (former IncorrectSettledAmount). IncorrectRemittanceormation Remittanceormation is incorrect. IncorrectDebtorAddress Debtor's address is incorrect. IncorrectCreditorAddress Creditor's address is incorrect. MismatchCreditorNameAccount Name and account of creditor are not matching. MismatchDebtorNameAccount Name and account of debtor are not matching. Narrativeormation Narrative ormation, Additional Missing ormation must be present The Clearing House Payments Company L.L.C. 25

26 Additional Incorrect ormation Justfn +MssngOrIncrrct ++AddtlIncrrct Product Usage: Provides additional information regarding the incorrect information. This field is mandatory with the code NARR and being used to provide additional information. Index: 4.9 <AddtlIncrrct> <AddtlIncrrct>Unstructured ormation</addtlincrrct> 2018 The Clearing House Payments Company L.L.C. 26

27 2.2 Response to Request for ormation camt Request for ormation Message Version Scope The Response to the Request for ormation (camt.028) message is sent by the Debtor Customer to the Creditor Customer. The message is used by the Debtor Customer to provide the requested additional information in the form of an amendment to the original Request for ormation (camt.026) in the camt.028 message. This is based on the Request for ormation message and the original Credit Transfer (pacs.008) message. Upon receipt of the Response to Request for ormation (camt.028), the Creditor FI must send a Message Status Report (pacs.002) confirming that the Response to Request for ormation (camt.028) was processed or indicating that the Response to Request for ormation (camt.028) could not be processed with the appropriate rejection code (e.g. AC04). For detailed information on Message Status Report (pacs.002) please see Message Status Report specification. Note: If the Debtor Customer cannot provide additional information, the Response to Request for ormation can indicate such in the text field Remittance ormation / Unstructured beginning with /RJCT/ Message Structure Description Index XML Tag Element Name Occurr. Length M/O/C AddtlPmt Additional Payment ormation V06 [1..1] M 1.0 Assignment [1..1] M 1.1 Id Identification [1..1] 35 M 1.2 Assgnr Assigner [1..1] M 1.46 Agt Agent [1..1] M 1.47 FinInstnId Financial Institution Identification [1..1] M 1.49 ClrSysMmbId Clearing System Member Identification [1..1] M 1.53 MmbId Member Identification [1..1] 9 M 1.86 Assgne Assignee [1..1] M Agt Agent [1..1] M FinInstnId Financial Institution Identification [1..1] M ClrSysMmbId Clearing System Member Identification [1..1] M MmbId Member Identification [1..1] 9 M CreDtTm Creation Date Time [1..1] 19 M 2.0 Case Case [1..1] M 2.1 Id Identification [1..1] 35 M 2.2 Cretr Creator [1..1] M 2.3 Pty Party [1..1] M 2.4 Nm Name [1..1] 140 M 3.0 Undrlyg Underlying [1..1] M 3.14 IntrBk Interbank [1..1] M 3.15 OrgnlGrp Original Group ormation [1..1] M 3.16 OrgnlMsgId Original Message Identification [1..1] 35 M 3.17 OrgnlMsgNmId Original Message Name Identification [1..1] 35 M 3.20 OrgnlInstrId Original Instruction Identification [1..1] 35 M 2018 The Clearing House Payments Company L.L.C. 27

28 Index XML Tag Element Name Occurr. Length M/O/C 3.21 OrgnlEndToEndId Original End To End Identification [0..1] 35 O 3.22 OrgnlTxId Original Transaction Identification [1..1] 35 M 3.23 OrgnlIntrBkSttlmAmt Original Interbank Settlement Amount [1..1] 18 M 3.24 Ccy Currency [1..1] 3 M 3.25 OrgnlIntrBkSttlmDt Original Interbank Settlement Date [1..1] 10 M 4.0 ormation [1..1] M 4.1 InstrId Instruction Identification [0..1] 35 O 4.2 EndToEndId End To End Identification [0..1] 35 O 4.3 TxId Transaction Identification [0..1] 35 O 4.73 Dbtr Debtor [0..1] O 4.74 Nm Name [0..1] 140 O 4.75 PstlAdr Postal Address [0..1] O 4.79 StrtNm Street Name [0..1] 70 O 4.80 BldgNb Building Number [0..1] 16 O 4.81 PstCd Post Code [0..1] 16 O 4.82 TwnNm Town Name [0..1] 35 O 4.84 Ctry Country [0..1] 2 O 4.86 Id Identification [0..1] O 4.95 PrvtId Private Identification [1..1] O 4.96 DtAndPlcOfBirth Date And Place Of Birth [1..1] O 4.97 BirthDt Birth Date [1..1] 10 O 4.99 CityOfBirth City Of Birth [1..1] 35 O CtryOfBirth Country Of Birth [1..1] 2 O Cdtr Creditor [0..1] O Nm Name [0..1] 140 O PstlAdr Postal Address [0..1] O StrtNm Street Name [0..1] 70 O BldgNb Building Number [0..1] 16 O PstCd Post Code [0..1] 16 O TwnNm Town Name [0..1] 35 O Ctry Country [0..1] 2 O Id Identification [0..1] O PrvtId Private Identification [1..1] O DtAndPlcOfBirth Date And Place Of Birth [1..1] O BirthDt Birth Date [1..1] 10 O CityOfBirth City Of Birth [1..1] 35 O CtryOfBirth Country Of Birth [1..1] 2 O Rmt Remittance ormation [0..1] C Ustrd Unstructured [1..1] 140 C Detail Message Field Description The following section provides the detailed information of each element used in the Response to a Request for ormation message within RTP. In some cases, a single field has two different meanings: the ISO Definition, and the RTP Product Usage. In these instances, the first definition is based on the ISO specification provided by the ISO RMG group. The second definition is the definition The Clearing House developed for the product usage of this element within the 2018 The Clearing House Payments Company L.L.C. 28

29 RTP implementation. The second definition is only provided where the RTP product usage is different from the ISO group specification, or where more detailed information of the usage of this field is required. For the ISO Definition and further detail on the message itself, please refer to the official ISO website ( Additional Payment ormation V06 Assignment Identifies the assignment of an investigation case from an assigner to an assignee. Index: 1.0 Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver. <> Identification +Id Uniquely identifies the case assignment. Product Usage: Assigned by Debtor FI to uniquely identify the Response to Request for ormation message. The uniqueness of a Response to Request for ormation is determined by the Assignment Identification and is based on the format below. RTP will use the Assignment ID to perform a check for a duplicate transaction within the duplicate checking period. Index: 1.1 <Id> Index: [1..1] Format: Expected Format: MYYYYMMDDbbbbbbbbbbbXAAAnnnnnnnnnnn Pos Prefix "M" Pos File creation date in format YYYYMMDD Pos FI Identifier (11 digit Participant ID) Pos Message generation source ("B" generated by a TCH FI) Pos Alphabetic serial identifier (3 alphabetic characters) Pos Message serial number (11 numeric characters) Rules: The first 20 characters of Message Identification (positions 01-20) are validated for structural alignment in accordance with the format specification. Business validations for the Assignment Identification include: Embedded date (positions 02-09) must be within 1 calendar day 2018 The Clearing House Payments Company L.L.C. 29

30 of the system date. Embedded Participant ID (positions 10-20) must be owned by the Instructing Agent. Reason Codes: Reject with Message Status Report (pacs.002) if: Assignment Identification matches a previously completed transaction (DUPL); Embedded date is not within 1 calendar day of the system date (DT04) Participant ID is not owned by the Instructing Agent (DS0H) If structural validation fails, reject with reason code 650 in Administration Advice message (admi.002). <Id>M BRFIA </Id> Assigner +Assgnr Party who assigns the case. Usage: This is also the sender of the message. Product Usage: Debtor FI that originally received the Request for ormation message (same FI as provided in Assignee of the original Request for ormation (camt.026) message). Index: 1.2 <Assgnr> Agent +Assgnr ++Agt Identification of a financial institution. Index: 1.46 <Agt> Financial Institution Identification +Assgnr ++Agt +++FinInstnId Unique and unambiguous identification of a financial institution, as assigned under an internationally recognized or proprietary identification scheme. Index: 1.47 <FinInstnId> 2018 The Clearing House Payments Company L.L.C. 30

31 Clearing System Member Identification +Assgnr ++Agt +++FinInstnId ++++ClrSysMmbId ormation used to identify a member within a clearing system. Index: 1.49 <ClrSysMmbId> Member Identification +Assgnr ++Agt +++FinInstnId ++++ClrSysMmbId +++++MmbId Identification of a member of a clearing system. Product Usage: The 9 digit Routing and Transit Number of the Original Assignee (Debtor FI) of the Request for ormation message. Index: 1.53 <MmbId> Format: Rules: 9 digit Routing and Transit Number Member Identification must be a valid 9 digit Routing and Transit Number. Reason Codes: Reject with Message Status Report (pacs.002) if: Sender is not authorised to send this business message (reason code 'AG03') Agent is signed-off (reason code '9934') Agent is suspended (reason code '9946') The sender of the message is not authorized to submit messages on behalf of this agent (reason code 'DS0H') Reject with admi.002 (reason 650) if Routing and Transit number does not exist in RTP. Note: The system validates that the participant indicated in the Assignment ID (positions 10-20) owns the Routing and Transit Number contained within this field. <MmbId> </MmbId> Assignee +Assgne Party to which the case is assigned. Usage: This is also the receiver of the message. Product Usage: Creditor FI that originated the Request for ormation message (same FI as provided in Assigner of the Request for ormation (camt.026) message). Index: The Clearing House Payments Company L.L.C. 31

32 <Assgne> Agent +Assgne ++Agt Identification of a financial institution. Index: <Agt> Financial Institution Identification +Assgne ++Agt +++FinInstnId Unique and unambiguous identification of a financial institution, as assigned under an internationally recognized or proprietary identification scheme. Index: <FinInstnId> Clearing System Identification +Assgne ++Agt +++FinInstnId ++++ClrSysMmbId ormation used to identify a member within a clearing system. Index: <ClrSysMmbId> Member Identification +Assgne ++Agt +++FinInstnId ++++ClrSysMmbId +++++MmbId Identification of a member of a clearing system. Index: Occurrences: The 9 digit Routing and Transit Number of the Original Assigner (Creditor FI) of the Request for ormation message. <MmbId> [1..1] Format: Rules: 9 digit Routing and Transit Number Member Identification must be a valid 9 digit Routing and Transit 2018 The Clearing House Payments Company L.L.C. 32

33 Number. Reason Codes: Reject with Message Status Report (pacs.002) if: Routing and Transit number is not supported in RTP (reason code 'RC04') Receiver is not authorised to receive this business message (reason code 'AG03') Agent is signed-off (reason code '9910') Agent is suspended (reason code '9947') Receiver connection is not available (reason code 9912 ) <MmbId> </MmbId> Creation Date Time +CreDtTm Date and time at which the assignment was created. Index: The date and time the assignment of the camt.028 was created. Occurrences: <CreDtTm> [1..1] Format: Note: YYYY-MM-DDThh:mm:ss The date is required to be set to Eastern Time (ET). <CreDtTm> T10:09:33</CreDtTm> Case Case Identifies the investigation case. Index: 2.0 <Case> Identification Case +Id Uniquely identifies the case. Product Usage: The Identification from the original Case ID used in the Request for ormation Message (Equals the Assignment ID of the original camt.026 message). Index: 2.1 <Id> 2018 The Clearing House Payments Company L.L.C. 33