Technical Guide GPP Fndt Message Usage For Feeder Interface Single Transaction Handoff
User Manual: Pdf
Open the PDF directly: View PDF 
.
Page Count: 76
| Download | |
| Open PDF In Browser | View PDF |
GPP PAYplus Fndt Message Usage for Feeder Interface - Single Transaction Handoff Technical Guide Product Version: 4.6.8 Catalog ID: GPP4.6-00-T16-01-201801 Copyright © 2009-2018 Finastra International Limited, or a member of the Finastra group of companies (“Finastra”). All Rights Reserved. Confidential - Limited Distribution to Authorized Persons Only, pursuant to the terms of the license agreement by which you were granted a license from Finastra for the applicable software or services and this documentation. Republication or redistribution, in whole or in part, of the content of this documentation or any other materials made available by Finastra is prohibited without the prior written consent of Finastra. The software and documentation are protected as unpublished work and constitute a trade secret of Finastra International Limited, or a member of the Finastra group of companies, Head Office: One Kingdom Street, Paddington, London W2 6BL, United Kingdom. Disclaimer Finastra does not guarantee that any information contained herein is and will remain accurate or that use of the information will ensure correct and faultless operation of the relevant software, services or equipment. This document contains information proprietary to Finastra. Finastra does not undertake mathematical research but only applies mathematical models recognized within the financial industry. Finastra does not guarantee the intrinsic theoretical validity of the calculation models used. Finastra, its agents, and employees shall not be held liable to or through any user for any loss or damage whatsoever resulting from reliance on the information contained herein or related thereto. The information contained in this document and the general guidance of Finastra staff does not take the place of qualified compliance personnel or legal counsel within your institution. FINASTRA CANNOT RENDER LEGAL, ACCOUNTING OR OTHER PROFESSIONAL SERVICES TO YOUR INSTITUTION. THE INFORMATION CONTAINED HEREIN IS GENERAL IN NATURE AND DOES NOT CONSTITUTE LEGAL ADVICE OR A LEGAL OPINION. CONSULT YOUR LEGAL COUNSEL FOR LEGAL ADVICE SPECIFIC TO YOUR SITUATION OR CIRCUMSTANCES OR TO ANSWER ANY LEGAL QUESTIONS. This document is not intended as a substitute for formal education in the regulatory requirements of banking, banking operations, lending, lending operations, or other topics generally applicable to financial institutions. Your financial institution is solely responsible for configuring and using the software or services in a way that meets policies, practices, and laws applicable to your institution, including, without limitation: (1) options and selections made on prompts; (2) entries in the software program; (3) program setup; and (4) documents produced by the software or services. It is the obligation of the customer to ensure that responsible decisions are taken when using Finastra products. Information in this document is subject to change without notice and does not represent a commitment on the part of Finastra. Feedback Do you have comments about our guides and online help? Please address any comments and questions to your local Finastra representative. Need more information? Read more about our products at http://www.finastra.com or contact your local Finastra office at http://www.finastra.com/contact. Version Control Version Date 1.0 Summary of Changes Document created 2.0 June 2016 Updated with some rephrasing and marking of subtrees that the order of their child elements is not mandatory 3.0 August 2016 Updated with fix in format definition of Office tags 4.0 December 2016 Updated with an additional note explaining the usage of the Credentials element in the Header structure GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 1 Table of Contents 1 INTRODUCTION .......................................................................................................................... 3 1.1 1.2 1.3 1.4 1.5 2 Overview ............................................................................................................................... 3 About This Guide .................................................................................................................. 3 Background ........................................................................................................................... 3 Scope .................................................................................................................................... 3 References ............................................................................................................................ 3 INTERFACE STRUCTURES ....................................................................................................... 4 2.1 Feeder Transaction Handoff Request ................................................................................... 4 2.1.1 Minimal Scope ................................................................................................................... 4 2.1.2 Minimal Scope + MOP Information Option ...................................................................... 11 2.1.3 Minimal Scope + Fees Information Option ...................................................................... 17 2.1.4 Minimal Scope + Rates Information Option..................................................................... 23 2.1.5 Minimal Scope + Account Balance and Earmark Reference Information Option ........... 28 2.2 Feeder Transaction handoff Response (Acknowledgement) ............................................. 31 2.2.1 Detailed Structure When Using Minimal Scope .............................................................. 33 2.2.2 Options for More Detailed Scope .................................................................................... 43 3 USAGE ....................................................................................................................................... 43 APPENDIX A: GLOSSARY OF TERMS .............................................................................................. 43 APPENDIX B: CONVENTIONS (INCLUDING FORMAT AND PRESENCE) ...................................... 45 APPENDIX C: SCENARIOS AND EXAMPLES FOR FEEDER HANDOFF ........................................ 46 C.1 Simple Minimal Handoff .............................................................................................................. 46 C.2 Outgoing Single Credit Transfer Handoff with Suggested MOP ................................................ 49 C.3 Outgoing Single Credit Transfer Handoff with Instructed MOP .................................................. 51 C.4 Outgoing Single Credit Transfer Handoff with Fees ................................................................... 54 C.5 Outgoing Single Credit Transfer Handoff with Account, Customer and Contact Information..... 55 C.6 Outgoing Single Credit Transfer Handoff with Forward Contract Rates ..................................... 58 C.7 Outgoing Single Credit Transfer Handoff with Counter Rate and Spread .................................. 60 C.8 Outgoing Single Credit Transfer Handoff with Trigger Payment ................................................ 62 C.9 Outgoing Single Credit Transfer Handoff with Earmark Reference ............................................ 64 C. 10 Successful Outgoing Single Transaction Handoff Response – Minimal Scope ...................... 68 C. 11 Successful Outgoing Single Transaction Handoff Response – Extended Scope ................... 69 C. 12 Failed Outgoing Single Transaction Handoff Response – Minimal Scope .............................. 72 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 2 1 Introduction Note: This document has not yet been certified for GPP V4.6; therefore, there may be inaccuracies in this document that may require amendments in the future. For more information, please contact your Finastra Project Manager. 1.1 Overview This guide describes Global PAYplus (GPP)’s standard usage of the Fndt (FuNDs Transfer) message for the Feeder interface for single transaction handoff from a Feeder system to Global PAYplus (GPP). This interface is an XML interface based on the GPP Fndt (FuNDs Transfer) message format. It includes the interface structure and related processing of the Feeder Transaction Handoff interface Request and Response: Transaction handoff request (from Feeder system to GPP) Transaction handoff response (acknowledgement) (from GPP to Feeder system) GPP standard transaction handoff is invoked by the Feeder system when placing a relevant message on a dedicated MQueue (or when calling a web service), in many cases via a message mediation layer. GPP automatically consumes the message, validates its structure, parses it and directs it to the relevant message processing flow. GPP generates a response for the message the first time the message is stored in the GPP database (DB). The response serves as an acknowledgement (or status report) to the Feeder system. The response contains feeder transaction reference to allow matching, and provides information on the status of the message. The response is also in an Fndt (FuNDs Transfer) message structure with a pain.002 payload. The processing, manual handling and configuration required around the different options for information provided in the Feeder Request, are detailed in the Feeder interface section in the GPP Business Guide System Integration - Single Payment document. 1.2 About This Guide Information is provided for Global PAYplus (GPP) clients implementing a Feeder Transaction Handoff interface, using the GPP Fndt (FuNDs Transfer) Message Format as the base for initiating transaction processing and acknowledgment for providing processing state information. 1.3 Background A standard interface was defined to streamline the process of handoff between bank or financial institution Feeder system/s and GPP. In addition to providing additional fields for GPP processing, this structure supports the use of ISO 20022 or SWIFT messages embedded in the structure. When the message is received as a SWIFT message it is included within the Fndt Message within the specific wrapping XML structure, with the original transaction text in one tag and a structured list of additional attributes as additional and separate tags and trees. 1.4 Scope The guide covers only the structure and mapping aspects. The rest of the functionality is described in the sections related to the Feeder interface in the GPP Business Guide System Integration - Single Payment. 1.5 References For information about the GPP Fndt (FuNDs Transfer) Message structure, see GPP Technical Guide Fndt Message Format document. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 3 For more information about the logic and functionality around this interface, see GPP Business Guide System Integration – Single Payments document. 2 Interface Structures For the formatting and conventions in the interface detailed structure tables, the following should be taken into consideration: The shading in the detailed tables in this chapter marks tags, which represent subtree parents, for example, tags in level 1, 2, where leaf tags in level 3 exist under the level 1 and 2. Each level has a different shade, with the first (1) being the darkest shade and gradually getting lighter through the levels. For conventions, including the explanation of the values in the Presence and Format within the detailed structure tables, see Appendix B: Conventions (Including Format and Presence). For examples of the different scenarios, see Appendix C: Scenarios and Examples for Feeder Handoff. 2.1 Feeder Transaction Handoff Request 2.1.1 Minimal Scope The following sections from the full Fndt Message structure are the Product minimal scope to be included when the structure is used as a Feeder Transaction handoff Request (additional sections can be configured to be included, if required): Notes: As GPP is the receiver of the Feeder request, the generic interfaces mechanism of the EventID tag in the Header section (for distinguishing between a resent request and a new one) is not applied for this interface, and this tag is not required. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ‘all’ and not ‘sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmntquotes the transaction. When used for Feeder interface, it is an ISO based pain, or a SWIFT message. For more information, see GPP Technical Guide Fndt Message. Extn* Processing PersistentI nfo* GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 4 Level 1 Level 2 Level 3 Level 4 Level 5 Description Debit Side Persistent Info* Credit Side Persistent Info* UserDefine dFields User Defined Fields aka Custom Fields. System level and client/financial institution-defined message fields, if relevant. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 5 2.1.1.1 Detailed Structure When Using Minimal Scope Notes: As GPP is the receiver of the Feeder request, the generic interfaces mechanism of the EventID tag in the Header section (for distinguishing between a resent request and a new one) is not applied for this interface, and this tag is not required. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ‘all’ and not ‘sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element FndtMsg 1 [1..1] Fndt Message Header 2 contextName 3 + + + Description Format Mapped From/Into GPP Table and Field [1..1] Header [0..1] Context Name Generic field to add information regarding the specific usage. Text {1,n} Feeder system to populate with Feeder Not mapped into GPP. Just used for usage identification. Note: Specifically for the usage for Feeder request, the value can be Feeder contextLocalName Credentials 3 3 + + [0..1] [0..1] Context Local Name Credentials Generic optional field to add regarding the specific usage, but using the financial institution system terminology naming, in case such exist and is required for the identification on the financial institution side Credentials when required Text {1,n} Feeder system to populate, if required – with specific local context string. Mapped into X_CONTEXT_LCL_NM and used to be quoted back in the response (into same tag). Note: The usage of this section, if populated, is allowing to filter results passed in the Fndt Message structure, based on the credentials (permissions) of the quoted GPP User – for example filtering out details of transactions belonging to an Office the quoted user doesn’t have permissions for. This section is mainly used when Fndt Message structure is used within SOA GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 6 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element Description Format Mapped From/Into GPP Table and Field services, but can also be applied, if filtering is required, when using it in interface structures. If left empty – no filtering occurs In the context of Feeder feeding GPP – has meaning and business rational if needing to hide inner information for a user viewing the Request itself, maybe based on Office. UserID 4 + [0..1] User ID User ID Text {1,8} Feeder system to populate with User Id Not mapped into GPP. May be used for authentication and filtering. Role 4 + [0..1] User ID User ID Text {1,50} Feeder system to populate with User Role Not mapped into GPP. May be used for authentication and filtering. Skip Persist On Error Indicator An indication whether to store the [1,0] {1, 1} transaction details when an error or errors were found Feeder system to populate with 01 [0..1] Workflow Defined for mass processing. The Text {1,50} valid values are Template, File or Swift Expected to be left empty in Request. + [0..1] GPP Message The Internal GPP message Identifier Identifier + [0..1] Deliver Timestamp D_SKIP_PERSIST_O 3 N_ERROR + Workflow 3 + P_MID 3 deliveryTimestamp 3 [0..1] Text {1,16} The Timestamp when the request ISO Date was created Time Not mapped into GPP. Just used for processing. Expected to be left empty in Request. Will be populated by GPP on response Feeder system to populate with Office Date Time Not mapped into GPP. 1 Do not skip the saving of the message when there is an error invoking the Account Lookup request GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 7 Tag L 0 1 2 3 4 5 6 7 8 9 10 P_INIT_SRC_ID + Msg 2 Pmnt 3 + + Presence Element [0..1] Initiating The ID of the source system source system initiating the request/response ID [1..1] Message [0..1] Payment Description Format Mapped From/Into GPP Table and Field Text {1,50} Feeder system to populate with name of the Feeder system Not mapped into GPP. May be used for authentication. ISO or SWIFT message text that is stored in an XML structure in the XML_MSG The message is parsed per generic GPP parsing and a MINF entry is created for it. The entire transaction text is mapped to MINF.XML_MSG Extn* 3 ProcessingPersistentI 4 nfo* + + [1..1] Extension [1..1] ProcessingPer Transaction derived attributes sistentInfo relevant to the transaction information Note: Only the P_TX_ID is a must for a proper reconciliation. The rest are optional and should be populated only if required P_TX_ID 5 + [1..1] A unique transaction reference. This tag will be included in responses and advises enabling Feeder system to match by it. P_OFFICE 5 + {0..1} The office of the transaction. If left empty, GPP derives the Office per its Office derivation logic [A-Z,0-9] {3,3} P_PRODUCT_CD 5 + {0..1} The Product Code for the transaction. Used for categorization. Text {1,10} Product Code Mapped into MINF.P_TX_ID Mapped into MINF.P_PRODUCT_CD Note: If provided, should be populated with a value that fits a Product entry configured in GPP GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 8 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element Description P_RVS_SELL 5 CreditSide* 5 P_CDT_AMT 6 + [0..1] Reverse Sell Indicator Set to 1 if transaction is reverse [1,0] {1,1} sell (fixed debit amount). If not set to 1 or not present credit amount is fixed + [0..1] Credit Side Information on the Credit side. Persistent Info [0..1] Credit Amount + Format fractionDigits 4 Mapped From/Into GPP Table and Field Mapped into MINF.P_RVS_SELL Mapped into MINF.P_CDT_AMT totalDigits 19 P_CDT_CUST_CD 6 + [0..1] Credit Customer Code Applicable for outgoing debit transfer, or outgoing book credit transfer in case the creditor is also a GCP customer Text {1,34} P_CDT_ACCT_NB 6 + [0..1] Credit Account Number The credit account number to be validated Text {1,34} P_CDT_ACCT_CCY 6 + [0..1] Credit Account Currency The currency of the credit account [A-Z] {3,3} P_CDT_ACCT_OFFI CE 6 + [0..1] The office of the credit account Credit Account Office [A-Z,0-9] {3, 3} P_CDT_FEE_ACCT_ NB 6 + [0..1] Credit Fee Account Number The credit fee account number, if different than the credit account, to use for credit fees Text {1,34} Mapped into MINF.P_CDT_FEE_ACCT_NB P_CDT_FEE_ACCT_ CCY 6 + [0..1] Credit Fee Account Currency The currency of the credit fee account, if provided A-Z,0-1] {3, 3} Mapped into MINF.P_CDT_FEE_ACCT_CCY P_CDT_FEE_ACCT_ OFFCIE 6 + [0..1] Credit Fee The office of the credit fee Account Office account, if provided [A-Z,0-9] {3,3} Mapped into MINF.P_CDT_FEE_ACCT_OFFICE DebitSide* 5 [0..1] Debit Side Information on the Debit side. Persistent Info + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Mapped into MINF.P_CDT_CUST_CD Page 9 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element P_DBT_AMT 6 [0..1] Debit Amount + Description Format Mapped From/Into GPP Table and Field fractionDigits 4 Mapped into MINF.P_DBT_AMT totalDigits 19 P_DBT_CUST_CD 6 + [0..1] Debit Customer Code Applicable for outgoing credit transfer, or outgoing book debit transfer in case the debtor is also a financial institution customer Text {1,34} P_DBT_ACCT_NB 6 + [0..1] Debit Account Number The debit account number Text {1,34} P_DBT_ACCT_CCY 6 + [0..1] Debit Account Currency The currency of the debit account [A-Z] {3,3} P_DBT_ACCT_OFFI CE 6 + [0..1] Debit Account Office The office of the debit account [A-Z,0-9] {3, 3} P_DBT_FEE_ACCT_ NB 6 + [0..1] Debit Fee Account Number The debit fee account number, if different than the debit account, to use for debit fees Text {1,34} Mapped into MINF.P_DBT_FEE_ACCT_NB P_DBT_FEE_ACCT_ CCY 6 + [0..1] Debit Fee Account Currency The currency of the debit fee account, if provided [A-Z] {3,3} Mapped into MINF.P_DBT_FEE_ACCT_CCY P_DBT_FEE_ACCT_ OFFICE 6 + [0..1] Debit Fee The office of the debit fee Account Office account, if provided GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Mapped into MINF.P_DBT_CUST_CD [A-Z,0-9] {3, 3} Mapped into MINF.P_DBT_FEE_ACCT_OFFICE Page 10 2.1.1.2 Payment Document Payload (Pmnt tag) The Feeder system can provide any of the following transaction payloads: Pain.001 - For credit transfer - For Single transaction (which is the scope of this guide) › GrpHdr/NbOfTxs will always be 1 › PmtInf section will always be of 1 occurrence Pain.008 - For collection (debit transfer) - For Single transaction (which is the scope of this guide) › GrpHdr/NbOfTxs will always be 1 › PmtInf section will always be of 1 occurrence SWIFT MT103 SWIFT MT101 with single transaction 2.1.2 Minimal Scope + MOP Information Option When the financial institution system reports the MOP to be used for sending the specific transaction out, the following additional tags can be included in the request. These additional tags are included in the and extensions with the MOP information. Notes: Only the additional extension (on top of the extension specified in the previous section) is included in the following table. The main tree tags are also included, to show the path where the additional extension should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmnt Pmnt quotes the transaction. When used for Feeder interface it is an ISO based pain, or a SWIFT message embedded within the GPP proprietary XML structure. For more information, see GPP Technical Guide Fndt Message. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 11 Level 1 Level 2 Level 3 Level 4 Level 5 Description Extn* … ProcessingPer sistentInfo* Debit Side Persistent Info Credit Side Persistent Info … Monitors* Monitors. User/Services/Interface tracking monitors. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 12 2.1.2.1 Detailed Structure When Using Minimal Scope + MOP Information Option These additional tags are included in the and extensions with the MOP information. Notes: Only additional tags (on top of the tags specified in the previous section) are included in the following table. The main tree tags are also included, to show the path where the additional tags should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc e Element FndtMsg 1 [1..1] Fndt Message [1..1] Message + Description Format Mapped From/Into GPP Table and Field … Msg 2 + Pmnt 3 + [0..1] Payment Extn* 3 + [1..1] Extension [1..1] ProcessingPersi Transaction derived attributes stentInfo relevant to the transaction information [0..1] Credit Side Persistent Info ISO or SWIFT message text that is stored in an XML structure in the XML_MSG The message is parsed per generic GPP parsing and a MINF entry is created for it. The entire transaction text is mapped to MINF.XML_MSG … ProcessingPersistentI 4 nfo* + … CreditSide* 5 + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Information on the Credit side. Page 13 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc e Element Description P_CDT_MOP 6 [0..1] Credit MOP The suggested or instructed Text {1,20} MOP for outgoing credit transfer. Relevant only for a credit transfer Payload. If provided as instructed, where GPP needs to use it as is and only perform MOP validation, needs to be provided also with the MU_SET_CDT_MOP=F + Format Mapped From/Into GPP Table and Field Mapped into MINF.P_CDT_MOP (under the extension). If provided as suggested (MU_SET_CDT_MOP is not provided), MOP selection rules can be defined with conditions on the P_CDT_MOP to influence the final selection of the MOP Note: If provided, it should be populated with a value that fits a MOP entry configured in GPP … DebitSide* 5 P_DBT_MOP 6 + + [0..1] Debit Side Persistent Info Information on the Debit side. [0..1] Debit MOP The suggested or instructed Text {1,20} MOP for outgoing debit transfer. Relevant only for a direct debit Payload. If provided as instructed, where GPP needs to use it as is and only perform MOP validation, needs to be provided also with the MU_SET_DBT_MOP=F Mapped into MINF.P_DBT_MOP (under the GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 14 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc e Element Description Format Mapped From/Into GPP Table and Field Text {1,1} Mapped into MU_SET_CDT_MOP and the relevant character within the MINF. USER_STATE_MONITOR extension). If provided as suggested (MU_SET_DBT_MOP is not provided), MOP selection rules can be defined with conditions on the P_DBT_MOP to influence the final selection of the MOP Note: If provided, it should be populated with a value that fits a MOP entry configured in GPP … Monitors* 4 UserMonitor 5 MU_SET_CDT_MOP 6 + [0..1] + Monitors [0..1] + [0..1] Monitor flags that can provide additional information used in processing Monitor flags that record user actions. Usually within GPP UI. When included in Feeder Interface, it can be used to emulate a user action and cause GPP to behave the same as if the user has performed the action within the GPP UI (usually used to force user selection and skip the generic system logic for specific derived attributes) Credit MOP Selected Manually Monitor GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | A monitor that indicates to GPP that a user has selected the Credit MOP, and hence this MOP has to be the MOP used when sending the Credit Transfer out. Needs to be provided, set to F, along with P_CDT_MOP (under the Page 15 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc e Element Description Format Mapped From/Into GPP Table and Field extension) when the provided MOP is an instructed MOP (as opposed to suggested). Relevant to Credit Transfers MU_SET_DBT_MOP 6 + [0..1] Debit MOP Selected Manually Monitor GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | A monitor that indicates to GPP Text {1,1} that a user has selected the Debit MOP, and hence this MOP has to be the MOP used when sending the Direct Debit out. Needs to be provided, set to F, along with P_CDT_MOP (under the extension) when the provided MOP is an instructed MOP (as opposed to suggested). Relevant to Direct Debits Mapped into MU_SET_DBT_MOP and the relevant character within the MINF. USER_STATE_MONITOR Page 16 2.1.3 Minimal Scope + Fees Information Option When the financial institution system reports fees to be charged for the specific account/customer, and it is required that GPP includes these fees in the posting for the applicable transaction, the following additional tags can be included in the request. These additional tags are included in the extension with the fee information. Notes: Only the additional extension (on top of the extension specified in the previous section) is included in the following table. The main tree tags are also included, to show the path where the additional extension should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmnt Pmnt quotes the transaction. When used for Feeder interface it is an ISO based pain, or a SWIFT message embedded within the GPP proprietary XML structure. For more information, see GPP Technical Guide Fndt Message document. Extn* … MsgFees Message Fees. Multiple transaction fee details. … GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 17 2.1.3.1 Detailed Structure When Using Minimal Scope + Fees Information Option These additional tags are included in the extension with the fee information. Notes: Only additional tags (on top of the tags specified in the previous section) are included in the following table. The main tree tags are also included, to show the path where the additional tags should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e FndtMsg 1 [1..1] Fndt Message [1..1] Message + Description Format Mapped From/Into GPP Table and Field … Msg 2 + Pmnt 3 + [0..1] Payment Extn* 3 + [1..1] Extension MsgFees* 4 [0..1] Message Fees Information The information on the fee/s applied for the transaction M_MSG_FEES_LINE 5 {0..n} MsgFeeLine Message fees records + + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | ISO or SWIFT message text that is stored in an XML structure in the XML_MSG The message is parsed per generic GPP parsing and a MINF entry is created for it. The entire transaction text is mapped to MINF.XML_MSG For each occurrence of M_MSG_FEES_LINE a Msg_Fees entry will be created in GPP for the message Page 18 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description F_MSG_FEES_MAN UAL_FEE 6 [1..1] Indicates a fee manually selected [2,1,0] {1, 1} by a user or from an external system (CDB). + Format Mapped From/Into GPP Table and Field Mapped into MSG_FEES.MANUAL_FEE Note: When fees reported via this request always populate with 2 (CDB) F_MSG_FEES_DED UCT_FROM 6 + [1..1] Text {1,1} Indicates whether it is the transaction or account from which the fee is deducted. One of the following: A = Account. Fees should be deducted from an account (either a separate fee account or principal account). Mapped into MSG_FEES.DEDUCT_FROM P = Payment. Fees should be deducted from the transaction amount to be charged to the customer on the next financial institution (BEN fees in case of credit transfer). F_MSG_FEES_FEE_ 6 ACC_AMOUNT F_MSG_FEES_FEE_ 6 AMOUNT + + [0..1] [1..1] Amount (in fee account currency) fractionDigits that are debited from fee account. 4 Relevant only for scenarios a fee account is involved totalDigits 19 Fee amount (in fee currency) fractionDigits 4 Mapped into MSG_FEES.FEE_ACC_AMOUNT Mapped into MSG_FEES.FEE_AMOUNT totalDigits 19 F_MSG_FEES_FEE_ 6 AMT_IN_PMT_CCY F_MSG_FEES_FEE_ 6 APPLY + + [0..1] [1..1] GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Fee amount in transaction or instruction currency. Indicates when fees are applied. One of the following: NOW, LATER, WAIVE. fractionDigits 4 totalDigits 19 Mapped into MSG_FEES.FEE_AMOUNT_IN_PMT_ CCY Text {1,10} Mapped into MSG_FEES.APPLY Page 19 Tag L 0 1 2 3 4 5 6 7 8 9 10 F_MSG_FEES_FEE_ 6 BASE_AMOUNT + Presenc Element e Description Format Mapped From/Into GPP Table and Field [0..1] Fee amount in office base currency. fractionDigits 4 Mapped into MSG_FEES.FEE_BASE_AMOUNT totalDigits 19 F_MSG_FEES_FEE_ 6 CURRENCY + [1..1] Currency in which the fee is defined [A-Z] {3, 3} Mapped into MSG_FEES.FEE_CURRENCY F_MSG_FEES_FEE_ 6 PNL_ACC_CUR + [0..1] Fee Profit and Loss (PNL) account currency. [A-Z] {3, 3} Mapped into MSG_FEES.FEE_PNL_ACCOUNT_CU RRENCY Text {1,34} Mapped into MSG_FEES.FEE_PNL_ACC_NO Note: If not provided will be first derived from the Fee Type Profile configured in GPP and then mapped as if received F_MSG_FEES_FEE_ 6 PNL_ACC_NO + [0..1] Fee Profit and Loss (PNL) account number. Note: If not provided it is first derived from the Fee Type Profile configured in GPP and then mapped as if received F_MSG_FEES_PNL_ 6 ACC_OFFICE + [0..1] Office of the fee Profit and Loss (PNL) account [A-Z,0-9] {3, 3} Mapped into MSG_FEES.FEE_PNL_ACC_OFFICE Note: If not provided it is first derived from the Fee Type Profile configured in GPP and then mapped as if received F_MSG_FEES_FEE_ 6 PNL_AMOUNT TAX_AMOUNT 6 + + [0..1] [0..1] Tax Amount Fee amount (in Profit and Loss account currency) credited to the account. fractionDigits 4 The tax amount (in fee currency) fractionDigits 4 Mapped into MSG_FEES.FEE_PNL_AMOUNT totalDigits 19 Mapped into MSG_FEES.TAX_AMOUNT totalDigits 19 F_MSG_FEES_TAX_ 6 ACC_AMOUNT + [0..1] Tax Account Amount GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | The tax amount in the currency of fractionDigits the account from which the tax is 4 deducted. totalDigits 19 Mapped into MSG_FEES.TAX_ACC_AMOUNT Page 20 Tag L 0 1 2 3 4 5 6 7 8 9 10 F_TAX_BASE_AMOU 6 NT + Presenc Element e Description Format Mapped From/Into GPP Table and Field [0..1] The tax amount (in base currency) fractionDigits 4 Mapped into MSG_FEES.TAX_BASE_AMOUNT Tax Base Amount totalDigits 19 F_MSG_FEES_TAX_ 6 PNL_ACCT + [0..1] Tax P&L Account Number The tax Profit and Loss account number Text {1,34} Mapped into MSG_FEES.TAX_PNL_ACCT F_MSG_FEES_TAX_ 6 PNL_ACCT_CCY + [0..1] Tax P&L Account Currency Currency of the tax Profit and Loss account [A-Z] {3, 3} Mapped into MSG_FEES.TAX_PNL_ACCT_CCY F_MSG_FEES_TAX_ 6 PNL_ACCT_OFFICE + [0..1] Tax P&L Account Office Office of the tax Profit and Loss account [A-Z,0-9] {3, 3} Mapped into MSG_FEES.TAX_PNL_ACCT_OFFICE F_TAX_ON_TAX_AM 6 OUNT + [0..1] Tax on Tax Amount The tax on tax amount (in transaction currency) fractionDigits 4 Mapped into MSG_FEES.TAX_ON_TAX_AMOUNT totalDigits 19 F_TAX_ON_TAX_AC C_AMOUNT F_TAX_ON_TAX_PN L_AMOUNT 6 6 + + [0..1] [0..1] Tax on Tax Account Amount The tax on tax amount (in the currency of the account from which the tax on tax is deducted) Tax on Tax P&L The tax on tax amount (in P&L Amount account currency) fractionDigits 4 totalDigits 19 fractionDigits 4 totalDigits 19 F_MSG_FEES_FEE_ 6 TYPE_UID + [1..1] The Fee Type UID for the Fee in this entry. Mapped into MSG_FEES.TAX_ON_TAX_ACC_AMO UNT Mapped into MSG_FEES.TAX_ON_TAX_PNL_AMO UNT Text {1,100} Mapped into MSG_FEES.FEE_TYPE_UID Text {1,2} Mapped into MSG_FEES.PAYING_PARTY Note: Should be populated with a value that fits a Fee Type entry configured in GPP, in the following structure: Office + ^ + Fee type name F_MSG_FEES_PAYI NG_PARTY 6 + [1..1] GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Indicates the party that its fee arrangement defines the fee amount and application. It is not Page 21 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description Format Mapped From/Into GPP Table and Field necessarily the party that pays the fee. One of the following: DR - Debit party CR - Credit party AF - Agent fee GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 22 2.1.4 Minimal Scope + Rates Information Option When the financial institution system reports rates or the spread to be used for the specific transaction, the following additional tags can be included in the request. These additional tags are included in the extension with the fee information. Notes: Only the additional extension (on top of the extension specified in the previous section) is included in the following table. The main tree tags are also included, to show the path where the additional extension should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmnt Pmnt quotes the transaction. When used for Feeder interface it is an ISO based pain, or a SWIFT message embedded within the GPP proprietary XML structure. For more information, see GPP Technical Guide Fndt Message. Extn* … MsgRates Message Rates. Multiple transaction exchange rate details. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 23 2.1.4.1 Detailed Structure When Using Minimal Scope + Rates Information Option These additional tags are included in the extension with the fee information. Notes: Only additional tags (on top of the tags specified in the previous section) are included in the following table. The main tree tags are also included, to show the path where the additional tags should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e FndtMsg 1 [1..1] Fndt Message [1..1] Message + Description Format Mapped From/Into GPP Table and Field … Msg 2 + Pmnt 3 + [0..1] Payment Extn* 3 + [1..1] Extension MsgRates 4 {0..1} MsgRates Message Rates (for Forward Contract, Counter Rate and spread and for Trigger Payment), Multiple transaction exchange rate details. M_FC_LINE 5 {0..n} Forward contract line Forward contract line record. + + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | ISO or SWIFT message text that is stored in an XML structure in the XML_MSG The message is parsed per generic GPP parsing and a MINF entry is created for it. The entire transaction text is mapped to MINF.XML_MSG For each occurrence of M_FC_LINE a MessageRates entry will be created in GPP for the message Page 24 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description Format Mapped From/Into GPP Table and Field F_FC_CONTRACT 6 + [1..1] The reference of the forward Text {1,30} contract, is either Forward contract or Dealer reference. Expected to be populated if F_FC_FORWARD_CONTRACT is 0 or 1. As it is required for contract/dealer validation. Mapped into MESSAGERATES.CONTRACT F_FC_AMOUNT 6 + [1..1] The calculated amount using the specific rate. fractionDigits 4 totalDigits 19 Mapped into MESSAGERATES.AMOUNT F_FC_RATE 6 + [1..1] The exchange rate for the currency conversion. fractionDigits 11 Mapped into MESSAGERATES.RATE totalDigits 19 F_FC_CURRENCY1 6 + [1..1] From currency. [A-Z] {3, 3} Mapped into MESSAGERATES.CCY1 F_FC_CURRENCY2 6 + [1..1] To currency. [A-Z] {3, 3} Mapped into MESSAGERATES.CCY2 F_FC_SPREAD 6 + [0..1] Holds the spread given for the provided rate, or for GPP rates in cases these are used. The spread is the difference between the low rate and the high rate, i.e., the margin which stands for the profit of the financial institution. fractionDigits 8 Mapped into MESSAGERATES.SPREAD F_FC_SPREAD_UNI TS 6 + [0..1] totalDigits 16 Indicates whether the value of the [A-Z] {3, 3} SPREAD is points or percentage. Mapped into MESSAGERATES.SPREAD_UNITS Possible values: PCT or PTS Expected to be populated if F_FC_SPREAD is provided. F_FC_CONVERSIO N_TYPE 6 + [1..1] GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Indicate if the given information is on the debit side or credit side (In Feeder handoff – always the customer’s side). Possible values: [A-Z] {2, 2} Mapped into MESSAGERATES.CONVERSION_TY PE Page 25 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description Format Mapped From/Into GPP Table and Field DR - debit side conversion for Credit Transfers CR - Credit side conversion for Direct Debits F_FC_FORWARD_C 6 ONTRACT + [1..1] Flag indicting the type of [0-9] {1, 2} contract. Possible values: 0 - Forward contract. When an FX contract is quoted and its rate is used. 1 - Dealer rate. When a dealer rate is used. 2 - Residual amount. When a rate is quoted to be used for the residual amount of the transaction, after Contract amount/s were used. 3 - Counter Rate and Spread Contract. When short term rate quoted to be used for STP processing, and spread to be used in non-STP scenario orTrigger Payment. When a limit rate that instructs the system to only process the transaction if and when the calculated rate is favorable to the limit (Target) rate Mapped into MESSAGERATES.FORWARD_CONT RACT F_FC_CUSTOMER_I D 6 + [1..1] The ID of the customer for which the message rates apply. Text {1,34} Mapped into MESSAGERATES.CUSTOMER_ID F_FC_MANUAL_SPR 6 EAD + [1..1] Indicates if spread was entered manually by user. [1,0] {1, 1} Mapped into MESSAGERATES.MANUAL_SPREAD ISO Date Mapped into MESSAGERATES.LATEST_DATE Feeder system to populate always with 0 (not manually entered). F_FC_LATEST_DAT E 6 + [0..1] Latest Date GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | The expiration date of the Contract. Page 26 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description Format Mapped From/Into GPP Table and Field fractionDigits 11 Mapped into MESSAGERATES.TARGET_RATE Expected to be populated if F_FC_FORWARD_CONTRACT = 0. As it is required for validation. F_FC_TARGET_RAT 6 E + [0..1] Target Rate The target or limit rate that is used for the Trigger Payment functionality (F_FC_FORWARD_CONTRACT =3) totalDigits 19 … GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 27 2.1.5 Minimal Scope + Account Balance and Earmark Reference Information Option When the financial institution system reports account balance and earmark reference for the specific message, and it is required that GPP will include the earmark reference/s in the posting for the applicable transaction, the following additional tags can be included in the request. These additional tags are included in the extension with the above information. Notes: Only the additional extension (on top of the extension specified in the previous section) is included in the following table. The main tree tags are also included, to show the path where the additional extension should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmnt Pmnt quotes the transaction. When used for Feeder interface it is an ISO based pain, or a SWIFT message embedded within the GPP proprietary XML structure. For more information, see GPP Technical Guide Fndt Message. Extn* … BalanceCheckI nf Balance Check Information. Up to 2 balance check details GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 28 2.1.5.1 Detailed Structure When Using Minimal Scope + Account Balance and Earmark Reference Information Option These additional tags are included in the extension with the above information. Notes: Only additional tags (on top of the tags specified in the previous section) are included in the following table. The main tree tags are also included, to show the path where the additional tags should be added in the structure. These tags are marked with grey font. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is the XSD definition of the list of elements is ’all’ and not ’sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e FndtMsg 1 [1..1] Fndt Message [1..1] Message + Description Format Mapped From/Into GPP Table and Field … Msg 2 + Pmnt 3 + [0..1] Payment Extn* 3 + [1..1] Extension [0..1] Balance Check Information [0..n] BI information Line [0..1] Debit Type ISO or SWIFT message text that is stored in an XML structure in the XML_MSG The message is parsed per generic GPP parsing and a MINF entry is created for it. The entire transaction text is mapped to MINF.XML_MSG … BalanceCheckInf 4 M_BI_INFO_LINE 5 F_BI_INFO_DEBIT_ TYPE 6 + + + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | The type of the amount on which balance check is requested - either MAIN or FEE Text {1, 10} GPP will map the earmark reference and balance to appropriate logical Page 29 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presenc Element e Description Format Mapped From/Into GPP Table and Field fields (FEE or MAIN) based on the value in this tag F_BI_INFO_ACCNO 6 + [0..1] Account Number The account number to be validated Text {1,34} F_BI_INFO_ACC_C URRENCY 6 + [0..1] Account Currency The currency of the account [A-Z] {3, 3} F_BI_INFO_ACC_O FFICE 6 + [0..1] Account Office The office of the account [A-Z,0-9] {3, 3} F_BI_INFO_AMOUN 6 T + [0..1] Amount The amount on which balance check is requested fractionDigits 3 totalDigits 18 F_BI_INFO_VALUE_ 6 DATE + [0..1] Value Date Value date for which the balance was checked ISO Date F_BI_INFO_BALAN CE 6 + [0..1] Balance Balance per the account quoted Text {1,50} in , returned from the Balance Inquiry interface (if returned) If = MAIN - Map to logical field P_BI_DBT_ACC_BALANCE If = FEE - Map to logical field P_BI_FEE_ACC_BALANCE F_BI_INFO_EARMA RK_REF 6 + [0..1] Earmark Reference Earmark reference returned from the Balance Inquiry interface (if returned) If = MAIN - Map to logical field P_BI_MAIN_ERAMARK_REF If = FEE - Map to logical field P_BI_FEE_ERAMARK_REF Text {1,50} Not used by GPP. Just for proper quote … GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 30 2.2 Feeder Transaction handoff Response (Acknowledgement) The following sections from the full Fndt Message structure are the Product minimal scope to be included when the structure is used as a Feeder Transaction handoff Response (additional sections can be configured to be included, if required). Notes: As GPP is the receiver of the Feeder request, the generic interfaces mechanism of the EventID tag in the Header section (for distinguishing between a resent request and a new one) is not applied for this interface, and this tag is not required. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is, the XSD definition of the list of elements is ‘all’ and not ‘sequence.’ Level 1 Level 2 Level 3 Level 4 Level 5 Description FndtMsg Header General identifying attributes Msg Transaction message and extension Pmnt Pmnt quotes the transaction payload of a pain.002. Note: Due to the industry move to XML, even by SWIFT, the acknowledgment response is always using the ISO pain.002, even if the original message payload text was a SWIFT message. For more information, see GPP Technical Guide Fndt Message document. Extn* Processin gPersiste ntInfo* Processing Persistent Info. Transaction derived attributes relevant to the transaction information OrigMsg The message that was sent out from GPP as a result of this Feeder transaction handoff (for example, pain.008.001.02, pacs.003.03 or SWIFT MT103 message embedded within the GPP proprietary XML structure) as text. This is populated only if Response Details indicate a successful handoff receipt, and only if outgoing message was created by the time this response is sent back. This can be used to show the customer the outcome of its transaction initiation. Response Details Applicable for Interface Responses Possible errors that may be encountered by GPP when processing a Feeder transaction handoff request: GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 31 Technical errors: - Request not valid – failing Fndt message XSD - Transaction payload is not valid – failing transaction parsing - Possible Duplicate Functional errors while processing the transaction, for example: - Source account/initiating party could not be identified - Transaction failed cutoff GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 32 2.2.1 Detailed Structure When Using Minimal Scope Notes: GPP supports a functional and technical handshake functionalities with the initiating system. The functional, and more generic, method is the generic usage of and , quoting their value/s from the request + the P_TX_ID. This functionality is described in the table. There are additional technical methods that allow echo back of the sending system identifier in a custom property of the MQ header (the value of this identifier was captured from the handoff request as transport property) or using the MQ correlation Id in the MQ envelope. When a sub-tree tag is marked with [*] - the elements underneath it can appear in any order. That is, the XSD definition of the list of elements is ‘all’ and not ‘sequence.’ For the conventions of the Presence and Format columns in this table, see Appendix B: Conventions (Including Format and Presence). Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element FndtMsg 1 [1..1] Fndt (Funds Transfer) Message Header 2 [1..1] Header contextName 3 + [0..1] contextLocalName 3 + credentials 3 + UserID 4 + + + Description Format Mapped From/ Into GPP Table and Field Context Name Generic field to add information regarding the specific usage. Text {1,n} Populate with value in in the request [0..1] Context Local Name Generic optional field to add Text {1,n} regarding the specific usage, but using the financial institution system terminology naming, in case such exist and is required for the identification on the financial institution side If required, populate with specific local context string [0..1] Credentials Credentials when required Not required in the response as is going back to channel and GPP credentials are not relevant there. Can be omitted [0..1] User ID User ID GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Text {1,8} N/A Page 33 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element Description Format Mapped From/ Into GPP Table and Field Role 4 [0..1] User ID User ID Text {1,50} N/A D_SKIP_PERSIST_ON _ERROR 3 + [0..1] Skip Persist On Error Indicator An indication whether to [1,0] {1,1} store the transaction details when an error or errors were found Not required in the response. Can be omitted Workflow 3 + [0..1] Workflow Defined for mass Text {1,50} processing. The valid values are Template, File or Swift Populate with - TBD P_MID 3 + [0..1] GPP Message Identifier The Internal GPP message Identifier Text {1,16} GPP will populate with MINF.P_MID deliveryTimestamp 3 + [0..1] Deliver Timestamp The Timestamp when the request was created ISO Date Time Populate with Office Date Time Msg 2 [1..1] Message Pmnt 3 [0..1] Payment + + + pain.002 payload. A pain.002 payload generated by GPP as per the Advising Type Selection and the interface selected For more information, see pain.002. Extn* 3 ProcessingPersistentInf o* 4 P_TX_ID 5 P_MSG_STS 5 + [1..1] Extension [1..1] ProcessingPersiste Transaction derived ntInfo attributes relevant to the transaction information + [1..1] Transaction Id A unique transaction reference. This tag will be included in responses and advises enabling Feeder system to match by it. + [1..1] Message Status Status of the transaction + Mapping from GPP status Debit Failed – POSTREST, NSF, POSTEX GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | GPP will populate with MINF.P_TX_ID Text {1,25} GPP populates with Minf.P_STATUS of the original initiating message Page 34 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element Description Format Mapped From/ Into GPP Table and Field Failed for any other reason - REPAIR Warehoused in GPP SCHEDULED Sent to clearing WAIT_ACK / WAIT_CONFIRMATION Liquidation success – COMPLETED Liquidation Failed – NAK, REJECTED, RETURNED OrigMsg 2 + Original Message The message that was sent out from GPP as a result of this Feeder transaction handoff (for example, pain.008.001.02, pacs.003.03 or SWIFT MT103) as text. GPP populated from the MINF.XML_MSG of the original initiating transaction This is populated only if Response Details indicate a successful handoff receipt, and only if outgoing message was created by the time this response is sent back. This can be used to show the customer the outcome of its payment initiation. ResponseDetails 2 returnCode 3 description 3 + [1..1] Response Details + [1..1] Return Code The return code to indicate success (1) or failure (0) of account lookup + [0..1] Description The description of the return Text {1,250} code. Relevant only for a failure (0) GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | [0-9] {1, 5} Page 35 Tag L 0 1 2 3 4 5 6 7 8 9 10 Presence Element Description errorsList 3 [0..n] Error List List of errors for this response error 4 [1..1] Error code 5 + [1..1] Code The return code to indicate success (1) or failure (0) of account lookup description 5 + [0..1] Description The description of the return Text {1,250} code – relevant only for a failure (0) dataArray 3 [0..n] Data Array List of additional information entries, if required data 4 [0..1] Data Additional information entry Text {1,250} Description Format 2.2.1.1 + + + + Format Mapped From/ Into GPP Table and Field [0-9] {1, 5} pain.002 Note: Level is provided in relative term to the Pmnt tag in the Fndt message. Tag L 0 Document 0 + 1 GrpHdr 2 MsgId 3 1 2 3 + 4 5 6 7 Presence Element [1..1] Document Mapped From/ Into GPP Table and Field specify in Attribute xmlns="Urn.iso:std:iso:20022:tech: xsd:pain.002.001.03" [1..1] + + [1..1] Group Header [1..1] Message Identification GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to Text{1,16} Message Id is internally generated by GPP application Page 36 Tag L 0 1 2 3 4 5 6 7 Presence Element Description Format Mapped From/ Into GPP Table and Field unambiguously identify the message. CreDtTm 3 + [1..1] Request Date Time The date and time (ISO date ISO Date Time time format) at which the message was created. NbOfTxs 3 + [1..1] No of Transactions Text[0-9]{1,15} This interface will be used for Number of individual transactions contained in the single transaction handoff. So message. value will be 1 InitgPty 3 + [1..1] Initiating Party Initiating Party Details Nm 4 + [1..1] Initiating party Name Name of Initiating party Id 4 + [1..1] Identification OrgId 5 [1..1] Organization Identification Othr 6 [1..1] Other Id 7 [1..1] Identification Identification assigned by an Text{1..16} institution DbtrAgt 3 [0..1] Debtor Agent Financial institution servicing an account for the debtor FinInstnId 4 [1..1] Financial Institution Identification BIC 5 + [0..1] Debtor agent BIC The BIC of the Debtor Agent Text{4!a2!a2!c [3!c]} ClrSysMmbId 5 + [0..1] Clearing System Member Identification Information used to identify a member within a clearing system + + + + + GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Generated by GPP Mapped from details within original message Text{1.. 40} Mapped from details within original message Page 37 Tag L MmbId 6 Nm 5 CdtrAgt 3 FinInstnId 4 BIC 5 ClrSysMmbId 5 MmbId 6 Nm 5 OrgnlGrpInfAndSts 2 OrgnlMsgId 3 OrgnlMsgNmId 3 0 1 2 3 4 5 6 Presence Element [1..1] Member Identification [0..1] Debtor agent Name The name of the Debtor Agent [0..1] Creditor Agent [1..1] Financial Institution Identification + [0..1] Creditor agent BIC The BIC of the Creditor Agent + [0..1] Clearing System Member Identification Information used to identify a member within a clearing system. [1..1] Member Identification [0..1] Creditor agent Name The name of the Creditor Agent [1..1] Original Group Information And Status Original group information concerning the group of transactions, to which the status report message refers to. [1..1] Original Message Identification Point to point reference assigned by the original instructing party to unambiguously identify the original group of individual transactions. Text {1,35} Original Message Specifies the original Name Identification message name identifier to which the message refers e.g. Text {1,35} + + + + + + + + + 7 [1..1] GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Description Format Financial institution servicing an account for the creditor Mapped From/ Into GPP Table and Field Mapped from details within original message Text{4!a2!a2!c [3!c]} The point to point reference quoted in the original message – MsgId tag if original message was either pain.001 or pain.008 Message reference from the header of the MT101 GPP to echo back the message name of the original initiating message Page 38 Tag L 0 1 2 3 4 5 6 7 Presence Element Description Format Mapped From/ Into GPP Table and Field ISODateTime GPP to echo back the CreDtTm of the original initiating message. pain.001.001.03. pain.008.001.03. OrgnlCreDtTm 3 + [0..1] Original Creation Date Time OrgnlNbOfTxs 3 + [0..1] Original Number Of Number of individual Text {1,15} Transactions transactions contained in the original message. GPP to echo back the NbOfTxs of the original initiating message. OrgnlCtrlSum 3 + [0..1] Original Control Sum GPP to echo back the CtrlSum of the original initiating message. OrgnlPmtInfAndSts 2 OrgnlPmtInfId 3 TxInfAndSts 3 StsId 4 OrgnlInstrId 4 + Date and time at which the original message was created. Total of all individual amounts included in the original message, irrespective of currencies fractionDigits: 17 TotalDigits: 18 [0..n] Original Payment Information And Status + [1..1] Original Payment Information Identification + [0..n] Transaction Information and Status + [0..1] Status Identification Unique identification, as Text {1,35} assigned by GPP to unambiguously identify the reported status. Usage: The instructing party is the party sending the status message and not the party that sent the original instruction that is being reported on. GPP to populate with the original MID of the original initiating message. + [0..1] Original Instruction Identification Text {1,35} GPP to echo back the InstrId (or field 20 in SWIFT) of the original initiating message. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Unique identification, as assigned by the original instructing party for the original instructed party, to Page 39 Tag L 0 1 2 3 4 5 6 7 Presence Element Description Format Mapped From/ Into GPP Table and Field Text {1,35} GPP to echo back the EndToEndId (or field 21 in SWIFT) of the original initiating message. unambiguously identify the original instruction OrgnlEndToEndId 4 + [0..1] Original End To End Identification Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction TxSts 4 + [0..1] Transaction Status Specifies the status of a Text {1,4} transaction, in a coded form. (Enum) Element: Status Acceptable Statuses: RJCT (Unsuccessful) ACTC (Successful) ACSP (Accepted) PDNG (Pending) This is status from GPP that is returned to the channels. StsRsnInf 4 Rsn 5 Cd 6 Prtry AddtlInf + + + 6 5 + + [0..n] Status Reason Information Set of elements used to provide detailed information on the status reason [0..1] Reason Specifies the reason for the status report. {Or [1..1] Proprietary Reason for the status, in a proprietary form Text {1,35} Reason for the status, in a proprietary form Text {1,35} Additional information about the reason Text {1,105} Or} [1..1] [0..n] Proprietary Additional information GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Element: Reason Code Reason Code according to GPP standard. It has values where the source of the reason code is generated and the original code itself. Element: Reason Code Reason Code according to GPP standard. It has values where the source of the reason code is generated and the original code itself. Each occurrence populated with the relevant error text Page 40 Tag L 0 1 2 3 4 5 6 7 Presence Element Description Format Mapped From/ Into GPP Table and Field fractionDigits: 5 GPP to echo back the settlement amount and currency of the original initiating message. This field stores the error text, e.g. “Length of STP field Account No value is less then defined minimum length: [7]”, etc. OrgnlTxRef 4 IntrBkSttlmAmt and Ccy 5 + + [0..1] OriginalTransaction Set of key elements used to Reference identify the original transaction that is being referred to [0..1] Interbank Settlement Amount Amount of money moved between the instructing agent and the instructed agent minInclusive: 0 totalDigits: 18, [A-Z]{3,3} IntrBkSttlmDt 5 + [0..1] Interbank Settlement Date Date on which the amount of ISO Date money ceases to be available to the agent that owes it and when the amount of money becomes available to the agent to which it is due. GPP to echo back the settlement date of the original initiating message. PmtMtd 5 + [0..1] PaymentMethod Specifies the transfer method that was used by the instructing agent to transfer the funds to the creditor. GPP populates with Transaction Code of the original initiating message. Dbtr 5 + [0..1] Debtor Debtor details DbtrAcct 5 + [0..1] Debtor Account Debtor account details DbtrAgt 5 + [0..1] Debtor Agent Debtor agent details CdtrAgt 5 + [0..1] Creditor Agent Creditor agent details Cdtr 5 + [0..1] Creditor Creditor details GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Text {1,3} (Enum) Page 41 Tag L CdtrAcct 5 0 1 2 3 4 5 + 6 7 Presence Element Description [0..1] Creditor Account Creditor account details GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Format Mapped From/ Into GPP Table and Field Page 42 2.2.2 Options for More Detailed Scope In addition to the minimal scope defined above, configuration can be done to include additional information as per financial institution requirements. This additional information may include: Additional information under the ProcessingPersistentInfo extension, on top of just the status and the P_TX_ID which are the minimal information. This information can include: - Details on the credit and debit side accounts, customers, amounts, MOP - Details on the original message, for example, message type, settlement date and amount, source Additional extensions with more information to shed more light on the processing of the original message. Such as: - The Monitors extension – including the state of various monitors. - The ReferenceData extension – that can include additional information on the debit and credit customers, accounts and MOPs. 3 Usage For more information on logic related to STP processing, usage of the information provided in the Feeder interface, related manual handling and related configuration see Feeder Interface section in the GPP Business Guide System Integration - Single Payment document. Appendix A: Glossary of Terms This table lists the terms used in this document. Term Description Fndt Message The FuNDs Transfer message structure is a GPP specific XML structure that is comprising of the full set of information as received, enriched, computed or manually updated per message. This structure is used as part of the standard interfaces for interacting with financial institution systems. ISO International Organization for Standards The prefix convention for naming transaction attribute fields is described in this table: Prefix Meaning Explanation T_ Tree Place holder in the tree view that hold the relevant associated information. For example: T_PARTIES holds all of the transaction parties X_ XML ISO ( ) information that is stored in an XML structure in the XML_MSG OX_ Original XML Copy of the originally received XML transaction ( ) information that is stored in an XML structure in ORIG_XML_MSG OC_ Original Copy of XML field Prefix used if there is more than one way to receive specific data. Example: OX_CDTR_AGT_BIC_1OR or OX_CDTR_AGT_BIC_2AND. GPP copies the data into OC_CDTR_AGT_BIC to facilitate determining whether creditor GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 43 Prefix Meaning Explanation agent BIC was provided or not. Relevant only for originally received attributes. P_ Process F_ GPP derived transaction Derived attribute that are taken from the static data profile that attribute is associated with transaction details. For example, after P_CDT_MOP is determined, the related credit MOP profile attributes are set in these fields. Examples: F_CDT_MOP_NM is the credit MOP name derived from the credit MOP value. F_MOP_NM is associated with the debit MOP. D_ Derived Derived attributes that are calculated ‘on the fly’ while the GPP service is calculating the information. Derived fields are not stored in the transaction after processing is completed, or stopped for manual handling or wait. Therefore, they usually cannot be used as a condition in business rules. MU MF MI User Monitor Flow (service) monitor Interface monitor Monitors are divided into three categories: User monitors that track the user action over the UI such as forcing a transaction out of the insufficient funds queue Workflow monitors – internal monitors in the code that track the payment processing flow Interface monitors that monitor interface interactions These P_ field attributes hold the monitor statuses strings for every transaction. P_USER_STATE_MONITOR - for User Monitors – MU_ prefix for specific user action monitors within the P_USER_STATE_MONITOR string P_SERVICE_STATE_MONITOR - for Flow Monitors – MF_ prefix for specific flow monitors within the P_SERVICE_STATE_MONITOR string P_INTERFACE_STATE_MONITOR - for Interface Monitors – MI_ prefix for specific interface interaction monitors within the P_INTERFACE_STATE_MONITOR string The location of each monitor in the string field is defined by LOGICAL_FIELDS.LOCATION. The first location is 0 (zero). Example of a monitor string P_ field value: XXXXXXXXXXXXXXXXXXXT. The following SQL can be used to check the full list of monitors as per their monitor string P_ field and their location: select lf.obj_ref_data_id, lf.location, lf.* from logical_fields lf where lf.obj_ref_data_id like '%MONITOR' order by 1,2 GPP extension field for transaction data that cannot be placed in the ISO standard format. Commonly used attributes: P_MID, P_OFFICE, etc. GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 44 Appendix B: Conventions (Including Format and Presence) This table details naming conventions (including explanation of the values in the format and presence) used in the interface structures in this document. Term Meaning Tag name in Bold Indicate Aggregates ISO Date Time Date Time formats defined as ISO Date Time will conform to ISO8601. Representation: ISO Date Time with milliseconds: YYYY-MM-DD [T] {0,1} HH:MM:SS.mmm [Z,-,+] {1,1} HH:MM {0,1} ISO Date Time without milliseconds: YYYY-MM-DD [T] {0,1} HH:MM:SS [Z,-,+] {1,1} HH:MM {0,1} Where: YYYY is the year MM is the month (01 - 12) DD is the day (01 - 31) T is a literal separator between the date and time portions (optional) HH is the hour in 24 hour time MM is the minutes SS is the seconds mmm is the milliseconds Z is the time zone designator: Z for when time is in UTC time, OR +HH:MM; OR or -HH:MM ISO Date Date formats defined as ISO Date Time will conform to ISO8601. Representation: YYYY-MM-DD Where: YYYY is the year, MM is the month (01 - 12) DD is the day (01 - 31) ISO Decimal Values Decimal values defined as ISO Decimal Values will use the ISO format definition using fractionDigits and totalDigits Where: totalDigits defines the total number of digits in the number (on both sides of the decimal point) fractionDigits defines the number of digits to the right of the decimal point (the fraction) SWIFT Date Date formats defined as SWIFT Date will conform to SWIFT representation: YYMMDD Where: YY is the year MM is the month (01 - 12) DD is the day (01 - 31) GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 45 Term Meaning SWIFT Decimal Values Decimal values defined as SWIFT Decimal Values will use the SWIFT representation of digits and a comma acting as the decimal separator between the fraction and the full number Presence (Cardinality) 0..1 means Optional 1..1 means Required 0..n means Optional and may have multiple occurrences (limited to specified n) 1..n means required and may have multiple occurrences (limited to specified n) String format [character set] {min length, max length] [A-Z] means only upper letter characters [a-z] means only lower letter characters [0-9] means only digits [A-Za-z] means upper and lower letter characters Text means all characters {1,6} means a string at least one character long and no longer than 6 characters Appendix C: Scenarios and Examples for Feeder Handoff The below are examples of various scenarios of Feeder Handoff using the various optional functionality supported by the system. These can be used as guidelines for usage of this interface and the following GPP processing. C.1 Simple Minimal Handoff In this scenario the only added information on top of the transaction message text itself (within the section) is the P_TX_ID reference (within ProcessingPersistentInfo extension). This is an example with ISO pain.001 message for Credit transfer. Simple Feeder with only Pmnt and ref.xml This is an example with ISO pain.008 message for Direct Debit (Drawdown) without Mandate reference details. Feeder ABCD SYS_USER SYS_ROLE FEED_SYS GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 47 CTv422-001 2008-06-25T06:19:06 1 700 South Pacific GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 46140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 700 CRED BOFAUS3NXXX NON BDB CUST 14050600NB 8552503 1234567890 Simple Feeder with only Pmnt and ref - Direct Debit.xml C.2 Outgoing Single Credit Transfer Handoff with Suggested MOP This is an example with suggested MOP as local clearing (FED). Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2014-06-25T06:19:06 1 700 South Pacific 140506000S 2100000009 DD false 2014-06-25 South Pacific 140506000S 333333333 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 48USD BRASUS3MXXX ADv41045 DDv4230 700 BOFAUS3NXXX NON BDB CUST 14050600NB 8552503 1234567890 Feeder with suggested MOP.xml C.3 Outgoing Single Credit Transfer Handoff with Instructed MOP This is an example with instructed MOP as local clearing (FED). Feeder ABCD GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 49SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 700 CRED BOFAUS3NXXX NON BANK CUST GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 50 14050600NB 8552503 US1 1234567890 FED Feeder with instructed MOP.xml GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 53 C.4 Outgoing Single Credit Transfer Handoff with Fees Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 51TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 700 CRED BOFAUS3NXXX NON BANK CUST 14050600NB 8552503 US1 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 521234567890 FED F Feeder with Fees.xml C.5 Outgoing Single Credit Transfer Handoff with Account, Customer and Contact Information Debtor is a financial institution customer, and customer, account and contact details are not managed in GPP. Feeder system can provide customer, account and contact details as part of this handoff, instead of another invocation for Account Lookup. Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 700 CRED GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 54 BOFAUS3NXXX NON BANK CUST 14050600NB 8552503 2 P 5 NOW USD US1^FEDFEE DR 1234567890 Feeder with cust account and contact inf.xml C.6 Outgoing Single Credit Transfer Handoff with Forward Contract Rates The first 875 will converted using the first contract (and rate) and the rest will be converted using the second contract (and rate). Feeder ABCD GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 55 SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 700 CRED BRASUS3MXXX ANOTHER BANK CUST GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 56 140506000F 8552502 USD 1234567890 22222222 USD XX1 YYY South Pacific ZZZZ BISFAEA1 211122232 2111 XXXYYYMMMTTT 2244667788 USD XX1 AE RAS AL KHAIMAH Business Center 04, Floor 6 Business Park, 610a, Free Trade Zon 1 xxx VOS 1 DR_ACC Jack Wilson Relationship Manager 97254222334456 97254222334111 jack.wilson@katota.com Business Center 04, Floor 6 Business Park, 610a, Free Trade Zon RAS AL KHAIMAH, AE DR_ACC Laora Adams Head Relationship Manager 97254222334666 97254222334111 laora.adams@katota.com Business Center 04, Floor 6 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 57Business Park, 610a, Free Trade Zon RAS AL KHAIMAH, AE Feeder with Forward Contract Rates.xml C.7 Outgoing Single Credit Transfer Handoff with Counter Rate and Spread Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 58 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 7000 CRED BOFAGB2LXXX NON BDB CUST GB 14050600GB 8552504 0000123 875 1.25 GBP USD 0.02 PTS DR 0 140506000S 2010-05-04 0000124 1500 1.3 GBP GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 59USD 0.02 PTS DR 0 140506000S 2010-05-04 1234567890 Feeder with Counter Spread and Rate.xml C.8 Outgoing Single Credit Transfer Handoff with Trigger Payment Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 60 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 7000 CRED BOFAGB2LXXX NON BDB CUST GB 14050600GB 8552504 0000124 1500 1.3 GBP USD 0.02 PTS DR 3 140506000S 2010-05-04 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 61 1234567890 Feeder with Trigger Payment.xml GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 63 C.9 Outgoing Single Credit Transfer Handoff with Earmark Reference This example shows Feeder with fees reported and also an earmark for the fess included. Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 62ADv41-04 CTv4228 7000 CRED BOFAGB2LXXX NON BDB CUST GB 14050600GB 8552504 0000124 1500 GBP USD 0.02 PTS DR 3 140506000S 2010-05-04 1.3 1234567890 Feeder with Balance earmark inf (including Fees).xml This example shows Feeder with fees reported but earmark included is only for the principal amount. Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX ADv41-04 CTv4228 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 64 700 CRED BOFAUS3NXXX NON BDB CUST 14050600NB 8552503 2 P 1 NOW USD US1^FEDFEE DR 1234567890 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 65 MAIN 22222222 USD XXX TRN_DR MINDOL-SYS 700.0 2009-05-04+02:00 160999.34 3394777746 FEE 26026 GBP XXX TRN_FDR MINDOL-SYS 1.0 2009-05-04+02:00 160.66 3394777747 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 67 Feeder with Balance earmark inf (no eramark on Fees).xml C. 10 Successful Outgoing Single Transaction Handoff Response – Minimal Scope Feeder ABCD SYS_USER SYS_ROLE FEED_SYS CTv422-001 2008-06-25T06:19:06 1 700 South Pacific 140506000S TRF false 2009-05-04 South Pacific 140506000S 22222222 USD BRASUS3MXXX GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 66ADv41-04 CTv4228 700 CRED BOFAUS3NXXX NON BDB CUST 14050600NB 8552503 2 P 1 NOW USD US1^FEDFEE DR 1234567890 MAIN 22222222 USD XXX TRN_DR MINDOL-SYS 700.0 2009-05-04+02:00 160999.34 3394777746 Succesfull Feeder Acknowledgment - minimal scope.XML C. 11 Successful Outgoing Single Transaction Handoff Response – Extended Scope 159R2344307I2862 159R2344307I2862 2015-09-27T02:41:13 FUNDT11 Pain.001 15092300002S GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 68 159R2344307I2862 TESTWW1FF1 TEST45331FF1 ACTC 2015-09-27T07:41:13 23.00000 23.00000 2015-09-24 TRF FIGUEIRELS 8000000180 GBP HSBC HONG KONG 26815573499 USD COMPLETE 15092300002S Succesfull Feeder Acknowledgment - extended scope.XML C. 12 Failed Outgoing Single Transaction Handoff Response – Minimal Scope 159R2344307I2862 159R2344307I2862 2015-09-27T02:41:13 FUNDT11 Pain.001 15092300002S 159R2344307I2862 TESTWW1FF1 TEST45331FF1 ACTC 2015-09-27T07:41:13 23.00000 23.00000 2015-09-24 TRF FIGUEIRELS GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 69 8000000180 GBP HSBC HONG KONG 26815573499 USD GBP 26815573499 LDS 23.0 BDBTEST1LN1 BOOK 001 2015-09-24 GBP 8000000180 LDS 23.0 AMITTest4645 BOOK 100 2015-09-24 23.0 GBP GBP LNP LNP LDS PACS008 M 0 PAY COMPLETE Pain_002 LDS Pacs_008 23.00 GBP 2015-09-24 FDR_GCP 2015-09-24 LNGBP 2015-09-24 2015-09-27 02:34:43.424 15092300002S X GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 70 X X X X X X X X X X X N X X X N B B B X B N B X X P X X X X X X S X X X X X X X X X X X X N X X X 151 MAIN ST STOCKTON US GCP AMITTest4645 CU LNP TRNS CA 95105 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 71 GB BDB LONDON BRASGB1LXXX false OUT false false false BOOK false SA 1 false false false false false BOOK false SA 1 false BRASGB2LXXX false NOS NOS GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 73 Failed Feeder Acknowledgment - minimal scope.XML GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 74 159R2344307I2862 159R2344307I2862 GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 722015-09-27T02:41:13 FUNDT11 Pain.001 15092300002S 159R2344307I2862 TESTWW1FF1 TEST45331FF1 RJCT FF01 Account Number could not be retrieved since Account 80000001890 defined in payment was not found for the 2015-09-27T07:41:13 23.00000 23.00000 2015-09-24 TRF FIGUEIRELS 8000000180 GBP HSBC HONG KONG 26815573499 USD P 15092300002S
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Language : en-US Tagged PDF : Yes XMP Toolkit : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26 Format : application/pdf Creator : Finastra Description : Fndt Message Usage for Feeder Interface - Single Transaction Handoff Title : Technical Guide Create Date : 2018:01:08 16:09:34+02:00 Creator Tool : Microsoft® Word 2016 Modify Date : 2018:01:08 16:09:45+02:00 Metadata Date : 2018:01:08 16:09:45+02:00 Producer : Microsoft® Word 2016 Document ID : uuid:cbd44862-05c4-44e9-8d84-b91c095ebff4 Instance ID : uuid:7508a260-f587-49f8-a003-60f016e668c9 Page Mode : UseOutlines Page Count : 76 Author : Finastra Keywords : Global, PAYplus Subject : Fndt Message Usage for Feeder Interface - Single Transaction HandoffEXIF Metadata provided by EXIF.tools