Technical Guide GPP Fndt Message Usage For Feeder Interface Single Transaction Handoff

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

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.

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 1

Version Control

Version

Date

Summary of Changes

1.0

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 2 
Table of Contents 
1 INTRODUCTION .......................................................................................................................... 3 
1.1 Overview ............................................................................................................................... 3 
1.2 About This Guide .................................................................................................................. 3 
1.3 Background ........................................................................................................................... 3 
1.4 Scope .................................................................................................................................... 3 
1.5 References ............................................................................................................................ 3 
2 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 3

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 4

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

Pmnt

<Pmnt> quotes 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 5

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 6

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

Description

Format

Mapped From/Into GPP Table

and Field

FndtMsg

1

+

[1..1]

Fndt Message

Header

2

+

[1..1]

Header

contextName

3

+

[0..1]

Context Name

Generic field to add information

regarding the specific usage.

Note: Specifically for the usage

for Feeder request, the value can

be Feeder

Text {1,n}

Feeder system to populate with Feeder

Not mapped into GPP. Just used for

usage identification.

contextLocalName

3

+

[0..1]

Context Local

Name

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

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).

Credentials

3

+

[0..1]

Credentials

Credentials when required

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 7

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

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

Text {1,50}

Feeder system to populate with User

Role

Not mapped into GPP. May be used for

authentication and filtering.

D_SKIP_PERSIST_O

N_ERROR

3

+

[0..1]

Skip Persist

On Error

Indicator

An indication whether to store the

transaction details when an error

or errors were found

[1,0] {1, 1}

Feeder system to populate with 01

Not mapped into GPP. Just used for

processing.

Workflow

3

+

[0..1]

Workflow

Defined for mass processing. The

valid values are Template, File or

Swift

Text {1,50}

Expected to be left empty in Request.

P_MID

3

+

[0..1]

GPP Message

Identifier

The Internal GPP message

Identifier

Text {1,16}

Expected to be left empty in Request.

Will be populated by GPP on response

deliveryTimestamp

3

+

[0..1]

Deliver

Timestamp

The Timestamp when the request

was created

ISO Date

Time

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 8

Tag

L

0

1

2

3

4

5

6

7

8

9

10

Presence

Element

Description

Format

Mapped From/Into GPP Table

and Field

P_INIT_SRC_ID

+

[0..1]

Initiating

source system

ID

The ID of the source system

initiating the request/response

Text {1,50}

Feeder system to populate with name of

the Feeder system

Not mapped into GPP. May be used for

authentication.

Msg

2

+

[1..1]

Message

Pmnt

3

+

[0..1]

Payment

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

+

[1..1]

Extension

ProcessingPersistentI

nfo*

4

+

[1..1]

ProcessingPer

sistentInfo

Transaction derived attributes

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.

Mapped into MINF.P_TX_ID

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}

Product Code

The Product Code for the

transaction. Used for

categorization.

Note: If provided, should be

populated with a value that fits a

Product entry configured in GPP

Text {1,10}

Mapped into MINF.P_PRODUCT_CD

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 9

Tag

L

0

1

2

3

4

5

6

7

8

9

10

Presence

Element

Description

Format

Mapped From/Into GPP Table

and Field

P_RVS_SELL

5

+

[0..1]

Reverse Sell

Indicator

Set to 1 if transaction is reverse

sell (fixed debit amount). If not set

to 1 or not present credit amount

is fixed

[1,0] {1,1}

Mapped into MINF.P_RVS_SELL

CreditSide*

5

+

[0..1]

Credit Side

Persistent Info

Information on the Credit side.

P_CDT_AMT

6

+

[0..1]

Credit Amount

fractionDigits

4

totalDigits 19

Mapped into MINF.P_CDT_AMT

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}

Mapped into MINF.P_CDT_CUST_CD

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]

Credit

Account Office

The office of the credit account

[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

Account Office

The office of the credit fee

account, if provided

[A-Z,0-9] {3,3}

Mapped into

MINF.P_CDT_FEE_ACCT_OFFICE

DebitSide*

5

+

[0..1]

Debit Side

Persistent Info

Information on the Debit side.

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 10

Tag

L

0

1

2

3

4

5

6

7

8

9

10

Presence

Element

Description

Format

Mapped From/Into GPP Table

and Field

P_DBT_AMT

6

+

[0..1]

Debit Amount

fractionDigits

4

totalDigits 19

Mapped into MINF.P_DBT_AMT

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}

Mapped into MINF.P_DBT_CUST_CD

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

Account Office

The office of the debit fee

account, if provided

[A-Z,0-9] {3, 3}

Mapped into

MINF.P_DBT_FEE_ACCT_OFFICE

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 11

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 <ProcessingPersistentInfo> and <Monitors> 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 12

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 13

2.1.2.1 Detailed Structure When Using Minimal Scope + MOP Information Option

These additional tags are included in the <ProcessingPersistentInfo> and <Monitors> 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

Description

Format

Mapped From/Into GPP Table and

Field

FndtMsg

1

+

[1..1]

Fndt Message

…

Msg

2

+

[1..1]

Message

Pmnt

3

+

[0..1]

Payment

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

+

[1..1]

Extension

…

ProcessingPersistentI

nfo*

4

+

[1..1]

ProcessingPersi

stentInfo

Transaction derived attributes

relevant to the transaction

information

…

CreditSide*

5

+

[0..1]

Credit Side

Persistent Info

Information on the Credit side.

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

P_CDT_MOP

6

+

[0..1]

Credit MOP

The suggested or instructed

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

(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

Text {1,20}

Mapped into MINF.P_CDT_MOP

…

DebitSide*

5

+

[0..1]

Debit Side

Persistent Info

Information on the Debit side.

P_DBT_MOP

6

+

[0..1]

Debit MOP

The suggested or instructed

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

(under the

Text {1,20}

Mapped into MINF.P_DBT_MOP

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | 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).

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

+

[0..1]

Monitors

Monitor flags that can provide

additional information used in

processing

UserMonitor

5

+

[0..1]

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)

MU_SET_CDT_MOP

6

+

[0..1]

Credit MOP

Selected

Manually

Monitor

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

Text {1,1}

Mapped into MU_SET_CDT_MOP and

the relevant character within the

MINF. USER_STATE_MONITOR

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 16

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

A monitor that indicates to GPP

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

Text {1,1}

Mapped into MU_SET_DBT_MOP and

the relevant character within the

MINF. USER_STATE_MONITOR

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 17

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 <MsgFees> 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 18

2.1.3.1 Detailed Structure When Using Minimal Scope + Fees Information Option

These additional tags are included in the <MsgFees> 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

e

Element

Description

Format

Mapped From/Into GPP Table

and Field

FndtMsg

1

+

[1..1]

Fndt Message

…

Msg

2

+

[1..1]

Message

Pmnt

3

+

[0..1]

Payment

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

+

[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

For each occurrence of

M_MSG_FEES_LINE a Msg_Fees

entry will be created in GPP for the

message

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 19

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

F_MSG_FEES_MAN

UAL_FEE

6

+

[1..1]

Indicates a fee manually selected

by a user or from an external

system (CDB).

Note: When fees reported via this

request always populate with 2

(CDB)

[2,1,0] {1, 1}

Mapped into

MSG_FEES.MANUAL_FEE

F_MSG_FEES_DED

UCT_FROM

6

+

[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).

 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).

Text {1,1}

Mapped into

MSG_FEES.DEDUCT_FROM

F_MSG_FEES_FEE_

ACC_AMOUNT

6

+

[0..1]

Amount (in fee account currency)

that are debited from fee account.

Relevant only for scenarios a fee

account is involved

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.FEE_ACC_AMOUNT

F_MSG_FEES_FEE_

AMOUNT

6

+

[1..1]

Fee amount (in fee currency)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.FEE_AMOUNT

F_MSG_FEES_FEE_

AMT_IN_PMT_CCY

6

+

[0..1]

Fee amount in transaction or

instruction currency.

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.FEE_AMOUNT_IN_PMT_

CCY

F_MSG_FEES_FEE_

APPLY

6

+

[1..1]

Indicates when fees are applied.

One of the following: NOW,

LATER, WAIVE.

Text {1,10}

Mapped into MSG_FEES.APPLY

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 20

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

F_MSG_FEES_FEE_

BASE_AMOUNT

6

+

[0..1]

Fee amount in office base

currency.

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.FEE_BASE_AMOUNT

F_MSG_FEES_FEE_

CURRENCY

6

+

[1..1]

Currency in which the fee is

defined

[A-Z] {3, 3}

Mapped into

MSG_FEES.FEE_CURRENCY

F_MSG_FEES_FEE_

PNL_ACC_CUR

6

+

[0..1]

Fee Profit and Loss (PNL)

account currency.

Note: If not provided will be first

derived from the Fee Type Profile

configured in GPP and then

mapped as if received

[A-Z] {3, 3}

Mapped into

MSG_FEES.FEE_PNL_ACCOUNT_CU

RRENCY

F_MSG_FEES_FEE_

PNL_ACC_NO

6

+

[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

Text {1,34}

Mapped into

MSG_FEES.FEE_PNL_ACC_NO

F_MSG_FEES_PNL_

ACC_OFFICE

6

+

[0..1]

Office of the fee Profit and Loss

(PNL) account

Note: If not provided it is first

derived from the Fee Type Profile

configured in GPP and then

mapped as if received

[A-Z,0-9] {3, 3}

Mapped into

MSG_FEES.FEE_PNL_ACC_OFFICE

F_MSG_FEES_FEE_

PNL_AMOUNT

6

+

[0..1]

Fee amount (in Profit and Loss

account currency) credited to the

account.

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.FEE_PNL_AMOUNT

TAX_AMOUNT

6

+

[0..1]

Tax Amount

The tax amount (in fee currency)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_AMOUNT

F_MSG_FEES_TAX_

ACC_AMOUNT

6

+

[0..1]

Tax Account

Amount

The tax amount in the currency of

the account from which the tax is

deducted.

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_ACC_AMOUNT

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 21

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

F_TAX_BASE_AMOU

NT

6

+

[0..1]

Tax Base

Amount

The tax amount (in base

currency)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_BASE_AMOUNT

F_MSG_FEES_TAX_

PNL_ACCT

6

+

[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_

PNL_ACCT_CCY

6

+

[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_

PNL_ACCT_OFFICE

6

+

[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

OUNT

6

+

[0..1]

Tax on Tax

Amount

The tax on tax amount (in

transaction currency)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_ON_TAX_AMOUNT

F_TAX_ON_TAX_AC

C_AMOUNT

6

+

[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)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_ON_TAX_ACC_AMO

UNT

F_TAX_ON_TAX_PN

L_AMOUNT

6

+

[0..1]

Tax on Tax P&L

Amount

The tax on tax amount (in P&L

account currency)

fractionDigits

4

totalDigits 19

Mapped into

MSG_FEES.TAX_ON_TAX_PNL_AMO

UNT

F_MSG_FEES_FEE_

TYPE_UID

6

+

[1..1]

The Fee Type UID for the Fee in

this entry.

Note: Should be populated with a

value that fits a Fee Type entry

configured in GPP, in the

following structure:

Office + ^ + Fee type

name

Text {1,100}

Mapped into

MSG_FEES.FEE_TYPE_UID

F_MSG_FEES_PAYI

NG_PARTY

6

+

[1..1]

Indicates the party that its fee

arrangement defines the fee

amount and application. It is not

Text {1,2}

Mapped into

MSG_FEES.PAYING_PARTY

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 22

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

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 23

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 <MsgRates> 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 24

2.1.4.1 Detailed Structure When Using Minimal Scope + Rates Information Option

These additional tags are included in the <MsgRates> 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

e

Element

Description

Format

Mapped From/Into GPP Table

and Field

FndtMsg

1

+

[1..1]

Fndt Message

…

Msg

2

+

[1..1]

Message

Pmnt

3

+

[0..1]

Payment

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

+

[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.

For each occurrence of M_FC_LINE a

MessageRates entry will be created in

GPP for the message

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 25

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

F_FC_CONTRACT

6

+

[1..1]

The reference of the forward

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.

Text {1,30}

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

totalDigits 19

Mapped into MESSAGERATES.RATE

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

totalDigits 16

Mapped into

MESSAGERATES.SPREAD

F_FC_SPREAD_UNI

TS

6

+

[0..1]

Indicates whether the value of the

SPREAD is points or percentage.

Possible values: PCT or PTS

Expected to be populated if

F_FC_SPREAD is provided.

[A-Z] {3, 3}

Mapped into

MESSAGERATES.SPREAD_UNITS

F_FC_CONVERSIO

N_TYPE

6

+

[1..1]

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

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 26

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

 DR - debit side conversion for

Credit Transfers

 CR - Credit side conversion

for Direct Debits

F_FC_FORWARD_C

ONTRACT

6

+

[1..1]

Flag indicting the type of

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

[0-9] {1, 2}

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

EAD

6

+

[1..1]

Indicates if spread was entered

manually by user.

Feeder system to populate

always with 0 (not manually

entered).

[1,0] {1, 1}

Mapped into

MESSAGERATES.MANUAL_SPREAD

F_FC_LATEST_DAT

E

6

+

[0..1]

Latest Date

The expiration date of the

Contract.

ISO Date

Mapped into

MESSAGERATES.LATEST_DATE

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 27

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

Expected to be populated if

F_FC_FORWARD_CONTRACT

= 0. As it is required for

validation.

F_FC_TARGET_RAT

E

6

+

[0..1]

Target Rate

The target or limit rate that is

used for the Trigger Payment

functionality

(F_FC_FORWARD_CONTRACT

=3)

fractionDigits

11

totalDigits 19

Mapped into

MESSAGERATES.TARGET_RATE

…

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 28

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 <BalanceCheckInf> 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 29

2.1.5.1 Detailed Structure When Using Minimal Scope + Account Balance and Earmark Reference Information Option

These additional tags are included in the <BalanceCheckInf> 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

e

Element

Description

Format

Mapped From/Into GPP Table

and Field

FndtMsg

1

+

[1..1]

Fndt Message

…

Msg

2

+

[1..1]

Message

Pmnt

3

+

[0..1]

Payment

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

+

[1..1]

Extension

…

BalanceCheckInf

4

+

[0..1]

Balance Check

Information

M_BI_INFO_LINE

5

+

[0..n]

BI information

Line

F_BI_INFO_DEBIT_

TYPE

6

+

[0..1]

Debit Type

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

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 30

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

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}

Not used by GPP. Just for proper

quote

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

T

6

+

[0..1]

Amount

The amount on which balance

check is requested

fractionDigits

3

totalDigits 18

F_BI_INFO_VALUE_

DATE

6

+

[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

in <F_BI_INFO_ACCNO>,

returned from the Balance

Inquiry interface (if returned)

Text {1,50}

 If <F_BI_INFO_DEBIT_TYPE> =

MAIN - Map to logical field

P_BI_DBT_ACC_BALANCE

 If <F_BI_INFO_DEBIT_TYPE> = 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)

Text {1,50}

 If <F_BI_INFO_DEBIT_TYPE> =

MAIN - Map to logical field

P_BI_MAIN_ERAMARK_REF

 If <F_BI_INFO_DEBIT_TYPE> = FEE

- Map to logical field

P_BI_FEE_ERAMARK_REF

…

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 31

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 32

 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 33

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 <ContexName> and <contexLocalName>, 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

Description

Format

Mapped From/

Into GPP Table and Field

FndtMsg

1

+

[1..1]

Fndt (Funds

Transfer) Message

Header

2

+

[1..1]

Header

contextName

3

+

[0..1]

Context Name

Generic field to add

information regarding the

specific usage.

Text {1,n}

Populate with value in

<ContexName> in the request

contextLocalName

3

+

[0..1]

Context Local

Name

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

Text {1,n}

If required, populate with specific

local context string

credentials

3

+

[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

UserID

4

+

[0..1]

User ID

Text {1,8}

N/A

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | 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

Role

4

+

[0..1]

User ID

Text {1,50}

N/A

D_SKIP_PERSIST_ON

_ERROR

3

+

[0..1]

Skip Persist On

Error Indicator

An indication whether to

store the transaction details

when an error or errors were

found

[1,0] {1,1}

Not required in the response. Can

be omitted

Workflow

3

+

[0..1]

Workflow

Defined for mass

processing. The valid values

are Template, File or Swift

Text {1,50}

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.

For more information, see

pain.002.

A pain.002 payload generated by

GPP as per the Advising Type

Selection and the interface selected

Extn*

3

+

[1..1]

Extension

ProcessingPersistentInf

o*

4

+

[1..1]

ProcessingPersiste

ntInfo

Transaction derived

attributes relevant to the

transaction information

P_TX_ID

5

+

[1..1]

Transaction Id

A unique transaction

reference. This tag will be

included in responses and

advises enabling Feeder

system to match by it.

GPP will populate with

MINF.P_TX_ID

P_MSG_STS

5

+

[1..1]

Message Status

Status of the transaction

Mapping from GPP status

 Debit Failed –

POSTREST, NSF,

POSTEX

Text {1,25}

GPP populates with

Minf.P_STATUS of the original

initiating message

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 35

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.

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.

GPP populated from the

MINF.XML_MSG of the original

initiating transaction

ResponseDetails

2

+

[1..1]

Response Details

returnCode

3

+

[1..1]

Return Code

The return code to indicate

success (1) or failure (0) of

account lookup

[0-9] {1, 5}

description

3

+

[0..1]

Description

The description of the return

code. Relevant only for a

failure (0) <returnCode>

Text {1,250}

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 36

Tag

L

0

1

2

3

4

5

6

7

8

9

10

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

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

[0-9] {1, 5}

description

5

+

[0..1]

Description

The description of the return

code – relevant only for a

failure (0) <returnCode>

Text {1,250}

dataArray

3

+

[0..n]

Data Array

List of additional information

entries, if required

data

4

+

[0..1]

Data

Additional information entry

Text {1,250}

2.2.1.1 pain.002

Note: Level is provided in relative term to the Pmnt tag in the Fndt message.

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

Document

0

+

[1..1]

Document

specify in Attribute

xmlns="Urn.iso:std:iso:20022:tech:

xsd:pain.002.001.03"

1

+

[1..1]

GrpHdr

2

+

[1..1]

Group Header

MsgId

3

+

[1..1]

Message

Identification

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

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 37

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

time format) at which the

message was created.

ISO Date

Time

Generated by GPP

NbOfTxs

3

+

[1..1]

No of Transactions

Number of individual

transactions contained in the

message.

Text[0-9]{1,15}

This interface will be used for

single transaction handoff. So

value will be 1

InitgPty

3

+

[1..1]

Initiating Party

Initiating Party Details

Mapped from details within original

message

Nm

4

+

[1..1]

Initiating party

Name

Name of Initiating party

Text{1.. 40}

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

institution

Text{1..16}

DbtrAgt

3

+

[0..1]

Debtor Agent

Financial institution servicing

an account for the debtor

Mapped from details within original

message

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 | Page 38

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

MmbId

6

+

[1..1]

Member

Identification

Nm

5

+

[0..1]

Debtor agent Name

The name of the Debtor

Agent

CdtrAgt

3

+

[0..1]

Creditor Agent

Financial institution servicing

an account for the creditor

Mapped from details within original

message

FinInstnId

4

+

[1..1]

Financial Institution

Identification

BIC

5

+

[0..1]

Creditor agent BIC

The BIC of the Creditor

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.

MmbId

6

+

[1..1]

Member

Identification

Nm

5

+

[0..1]

Creditor agent

Name

The name of the Creditor

Agent

OrgnlGrpInfAndSts

2

+

[1..1]

Original Group

Information And

Status

Original group information

concerning the group of

transactions, to which the

status report message refers

to.

OrgnlMsgId

3

+

[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}

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

OrgnlMsgNmId

3

+

[1..1]

Original Message

Name Identification

Specifies the original

message name identifier to

which the message refers

e.g.

Text {1,35}

GPP to echo back the message

name of the original initiating

message

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 39

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

pain.001.001.03.

pain.008.001.03.

OrgnlCreDtTm

3

+

[0..1]

Original Creation

Date Time

Date and time at which the

original message was

created.

ISODateTime

GPP to echo back the CreDtTm of

the original initiating message.

OrgnlNbOfTxs

3

+

[0..1]

Original Number Of

Transactions

Number of individual

transactions contained in the

original message.

Text {1,15}

GPP to echo back the NbOfTxs of

the original initiating message.

OrgnlCtrlSum

3

+

[0..1]

Original Control

Sum

Total of all individual

amounts included in the

original message,

irrespective of currencies

fractionDigits:

17

TotalDigits: 18

GPP to echo back the CtrlSum of

the original initiating message.

OrgnlPmtInfAndSts

2

+

[0..n]

Original Payment

Information And

Status

OrgnlPmtInfId

3

+

[1..1]

Original Payment

Information

Identification

TxInfAndSts

3

+

[0..n]

Transaction

Information and

Status

StsId

4

+

[0..1]

Status Identification

Unique identification, as

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.

Text {1,35}

GPP to populate with the original

MID of the original initiating

message.

OrgnlInstrId

4

+

[0..1]

Original Instruction

Identification

Unique identification, as

assigned by the original

instructing party for the

original instructed party, to

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 | Page 40

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

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

Text {1,35}

GPP to echo back the EndToEndId

(or field 21 in SWIFT) of the

original initiating message.

TxSts

4

+

[0..1]

Transaction Status

Specifies the status of a

transaction, in a coded form.

Text {1,4}

(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

+

[0..n]

Status Reason

Information

Set of elements used to

provide detailed information

on the status reason

Rsn

5

+

[0..1]

Reason

Specifies the reason for the

status report.

Cd

6

+

{Or [1..1]

Proprietary

Reason for the status, in a

proprietary form

Text {1,35}

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.

Prtry

6

+

Or} [1..1]

Proprietary

Reason for the status, in a

proprietary form

Text {1,35}

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.

AddtlInf

5

+

[0..n]

Additional

information

Additional information about

the reason

Text {1,105}

Each occurrence populated with

the relevant error text

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 41

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

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

+

[0..1]

OriginalTransaction

Reference

Set of key elements used to

identify the original

transaction that is being

referred to

IntrBkSttlmAmt and

Ccy

5

+

[0..1]

Interbank

Settlement Amount

Amount of money moved

between the instructing

agent and the instructed

agent

fractionDigits:

5

minInclusive:

0

totalDigits: 18,

[A-Z]{3,3}

GPP to echo back the settlement

amount and currency of the

original initiating message.

IntrBkSttlmDt

5

+

[0..1]

Interbank

Settlement Date

Date on which the amount of

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.

ISO Date

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.

Text {1,3}

(Enum)

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 | Page 42

Tag

L

0

1

2

3

4

5

6

7

Presence

Element

Description

Format

Mapped From/

Into GPP Table and Field

CdtrAcct

5

+

[0..1]

Creditor Account

Creditor account details

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 43

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 (<pmnt>) information that is stored in an XML structure in

the XML_MSG

OX_

Original XML

Copy of the originally received XML transaction (<pmnt>)

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 44

Prefix

Meaning

Explanation

agent BIC was provided or not. Relevant only for originally

received attributes.

P_

Process

GPP extension field for transaction data that cannot be placed

in the ISO standard format. Commonly used attributes: P_MID,

P_OFFICE, etc.

F_

GPP derived transaction

attribute

Derived attribute that are taken from the static data profile that

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 PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 45

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 46

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

<Pmnt> section) is the P_TX_ID reference (within ProcessingPersistentInfo extension).

This is an example with ISO pain.001 message for Credit transfer.

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 47

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 48

</Pmnt>

<Extn>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

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.

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Cdtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 49

</Othr>

</Id>

</CdtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</CdtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</DbtrAgt>

<Dbtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

</DrctDbtTxInf>

</PmtInf>

</CstmrDrctDbtInitn>

</Document>

</Pmnt>

<Extn>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

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).

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 50

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 51

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<P_OFFICE>US1</P_OFFICE>

<P_TX_ID>1234567890</P_TX_ID>

<P_CDT_MOP>FED</P_CDT_MOP>

</CreditSide>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

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).

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 52

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<P_OFFICE>US1</P_OFFICE>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 53

<P_TX_ID>1234567890</P_TX_ID>

<P_CDT_MOP>FED</P_CDT_MOP>

</CreditSide>

</ProcessingPersistentInfo>

<MU_SET_CDT_MOP>F</MU_SET_CDT_MOP>

</UserMonitor >

</Monitors>

</Extn>

</Msg>

</FndtMsg>

Feeder with

instructed MOP.xml

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 54

C.4 Outgoing Single Credit Transfer Handoff with Fees

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 55

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_MSG_FEES_LINE>

<F_MSG_FEES_MANUAL_FEE>2</F_MSG_FEES_MANUAL_FEE>

<F_MSG_FEES_DEDUCT_FROM>P</F_MSG_FEES_DEDUCT_FROM>

<F_MSG_FEES_FEE_AMOUNT>5</F_MSG_FEES_FEE_AMOUNT>

<F_MSG_FEES_FEE_APPLY>NOW</F_MSG_FEES_FEE_APPLY>

<F_MSG_FEES_FEE_CURRENCY>USD</F_MSG_FEES_FEE_CURRENCY>

<F_MSG_FEES_FEE_TYPE_UID>US1^FEDFEE</F_MSG_FEES_FEE_TYPE_UID>

<F_MSG_FEES_PAYING_PARTY>DR</F_MSG_FEES_PAYING_PARTY>

</M_MSG_FEES_LINE>

</MsgFees>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

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.

<?xml version=”1.0” encoding=”UTF-8”?>

<contextName>Feeder</contextName>

</credentials>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 56

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns=”urn:iso:std:iso:20022:tech:xsd:pain.001.001.03”

xmlns:n1=”http://www.w3.org/2001/XMLSchema-instance”>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Nm>ANOTHER BANK CUST</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 57

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<P_TX_ID>1234567890</P_TX_ID>

<P_DBT_ACCT_NB>22222222</P_DBT_ACCT_NB>

<P_DBT_ACCT_CCY>USD</P_DBT_ACCT_CCY>

<P_DBT_ACCT_OFFICE>XX1</P_DBT_ACCT_OFFICE>

</DebitSide>

</ProcessingPersistentInfo>

<M_DBT_CUST_PROFILE>

<F_DBT_CUST_CUST_CATEGORY>YYY</F_DBT_CUST_CUST_CATEGORY>

<F_DBT_CUST_CUST_NAME>South Pacific</F_DBT_CUST_CUST_NAME>

<F_DBT_CUST_PROFESSION>ZZZZ</F_DBT_CUST_PROFESSION>

<F_DBT_CUST_SWIFT_ID>BISFAEA1</F_DBT_CUST_SWIFT_ID>

<F_DBT_CUST_ABA>211122232</F_DBT_CUST_ABA>

<F_DBT_CUST_ALIAS>2111</F_DBT_CUST_ALIAS>

<F_DBT_CUST_BASE_NO>XXXYYYMMMTTT</F_DBT_CUST_BASE_NO>

<F_DBT_CUST_FEE_ACCOUNT_NO>2244667788</F_DBT_CUST_FEE_ACCOUNT_NO>

<F_DBT_CUST_FEE_ACCOUNT_CCY>USD</F_DBT_CUST_FEE_ACCOUNT_CCY>

<F_DBT_CUST_FEE_ACCOUNT_OFFICE>XX1</F_DBT_CUST_FEE_ACCOUNT_OFFICE>

<F_DBT_CUST_COUNTRYCODE>AE</F_DBT_CUST_COUNTRYCODE>

<F_DBT_CUST_CITY>RAS AL KHAIMAH</F_DBT_CUST_CITY>

<F_DBT_CUST_ADDRESS1>Business Center 04, Floor 6</F_DBT_CUST_ADDRESS1>

<F_DBT_CUST_ADDRESS2>Business Park, 610a, Free Trade

Zon</F_DBT_CUST_ADDRESS2>

</M_DBT_CUST_PROFILE>

<M_DBT_ACCOUNT>

<F_DBT_ACCT_ASSET>1</F_DBT_ACCT_ASSET>

<F_DBT_ACCT_BOOKNG_ENT>xxx</F_DBT_ACCT_BOOKNG_ENT>

<F_DBT_ACCT_ACC_TYPE>VOS</F_DBT_ACCT_ACC_TYPE>

<F_DBT_ACCT_IS_RESIDENT>1</F_DBT_ACCT_IS_RESIDENT>

</M_DBT_ACCOUNT>

<M_CONTACT_INFO>

<M_CONTACT_LINE>

<F_CONTACT_OF>DR_ACC</F_CONTACT_OF >

<F_CONTACT_NAME>Jack Wilson</F_CONTACT_NAME>

<F_CONTACT_DESCRIPTION>Relationship Manager</F_CONTACT_DESCRIPTION>

<F_CONTACT_PHONE>97254222334456</F_CONTACT_PHONE>

<F_CONTACT_FAX>97254222334111</F_CONTACT_FAX>

<F_CONTACT_EMAIL>jack.wilson@katota.com</F_CONTACT_EMAIL>

<F_CONTACT_ADDRESS1>Business Center 04, Floor 6</F_CONTACT_ADDRESS1>

<F_CONTACT_ADDRESS2>Business Park, 610a, Free Trade

Zon</F_CONTACT_ADDRESS2>

<F_CONTACT_ADDRESS3> RAS AL KHAIMAH, AE</F_CONTACT_ADDRESS3>

</M_CONTACT_LINE>

<M_CONTACT_LINE>

<F_CONTACT_OF>DR_ACC</F_CONTACT_OF >

<F_CONTACT_NAME>Laora Adams</F_CONTACT_NAME>

<F_CONTACT_DESCRIPTION>Head Relationship

Manager</F_CONTACT_DESCRIPTION>

<F_CONTACT_PHONE>97254222334666</F_CONTACT_PHONE>

<F_CONTACT_FAX>97254222334111</F_CONTACT_FAX>

<F_CONTACT_EMAIL>laora.adams@katota.com</F_CONTACT_EMAIL>

<F_CONTACT_ADDRESS1>Business Center 04, Floor 6</F_CONTACT_ADDRESS1>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 58

<F_CONTACT_ADDRESS2>Business Park, 610a, Free Trade

Zon</F_CONTACT_ADDRESS2>

<F_CONTACT_ADDRESS3> RAS AL KHAIMAH, AE</F_CONTACT_ADDRESS3>

</M_CONTACT_LINE>

</M_CONTACT_INFO>

</ReferenceData>

</Extn>

</Msg>

</FndtMsg>

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).

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 59

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAGB2LXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_FC_LINE>

<F_FC_CONTRACT>0000123</F_FC_CONTRACT>

<F_FC_AMOUNT>875</F_FC_AMOUNT>

<F_FC_RATE>1.25</F_FC_RATE>

<F_FC_CURRENCY1>GBP</F_FC_CURRENCY1>

<F_FC_CURRENCY2>USD</F_FC_CURRENCY2>

<F_FC_SPREAD>0.02</F_FC_SPREAD>

<F_FC_SPREAD_UNITS>PTS</F_FC_SPREAD_UNITS>

<F_FC_CONVERSION_TYPE>DR</F_FC_CONVERSION_TYPE>

<F_FC_FORWARD_CONTRACT>0</F_FC_FORWARD_CONTRACT>

<F_FC_CUSTOMER_ID>140506000S</F_FC_CUSTOMER_ID>

<F_FC_LATEST_DATE>2010-05-04</F_FC_LATEST_DATE>

</M_FC_LINE>

<M_FC_LINE>

<F_FC_CONTRACT>0000124</F_FC_CONTRACT>

<F_FC_AMOUNT>1500</F_FC_AMOUNT>

<F_FC_RATE>1.3</F_FC_RATE>

<F_FC_CURRENCY1>GBP</F_FC_CURRENCY1>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 60

<F_FC_CURRENCY2>USD</F_FC_CURRENCY2>

<F_FC_SPREAD>0.02</F_FC_SPREAD>

<F_FC_SPREAD_UNITS>PTS</F_FC_SPREAD_UNITS>

<F_FC_CONVERSION_TYPE>DR</F_FC_CONVERSION_TYPE>

<F_FC_FORWARD_CONTRACT>0</F_FC_FORWARD_CONTRACT>

<F_FC_CUSTOMER_ID>140506000S</F_FC_CUSTOMER_ID>

<F_FC_LATEST_DATE>2010-05-04</F_FC_LATEST_DATE>

</M_FC_LINE>

</MsgRates>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

Feeder with

Forward Contract Rates.xml

C.7 Outgoing Single Credit Transfer Handoff with Counter Rate and

Spread

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 61

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAGB2LXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_FC_LINE>

<F_FC_CONTRACT>0000124</F_FC_CONTRACT>

<F_FC_AMOUNT>1500</F_FC_AMOUNT>

<F_FC_RATE>1.3</F_FC_RATE>

<F_FC_CURRENCY1>GBP</F_FC_CURRENCY1>

<F_FC_CURRENCY2>USD</F_FC_CURRENCY2>

<F_FC_SPREAD>0.02</F_FC_SPREAD>

<F_FC_SPREAD_UNITS>PTS</F_FC_SPREAD_UNITS>

<F_FC_CONVERSION_TYPE>DR</F_FC_CONVERSION_TYPE>

<F_FC_FORWARD_CONTRACT>3</F_FC_FORWARD_CONTRACT>

<F_FC_CUSTOMER_ID>140506000S</F_FC_CUSTOMER_ID>

<F_FC_LATEST_DATE>2010-05-04</F_FC_LATEST_DATE>

</M_FC_LINE>

</MsgRates>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 62

</Extn>

</Msg>

</FndtMsg>

Feeder with

Counter Spread and Rate.xml

C.8 Outgoing Single Credit Transfer Handoff with Trigger Payment

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 63

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAGB2LXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_FC_LINE>

<F_FC_CONTRACT>0000124</F_FC_CONTRACT>

<F_FC_AMOUNT>1500</F_FC_AMOUNT>

<F_FC_CURRENCY1>GBP</F_FC_CURRENCY1>

<F_FC_CURRENCY2>USD</F_FC_CURRENCY2>

<F_FC_SPREAD>0.02</F_FC_SPREAD>

<F_FC_SPREAD_UNITS>PTS</F_FC_SPREAD_UNITS>

<F_FC_CONVERSION_TYPE>DR</F_FC_CONVERSION_TYPE>

<F_FC_FORWARD_CONTRACT>3</F_FC_FORWARD_CONTRACT>

<F_FC_CUSTOMER_ID>140506000S</F_FC_CUSTOMER_ID>

<F_FC_LATEST_DATE>2010-05-04</F_FC_LATEST_DATE>

<F_FC_TARGET_RATE>1.3</F_FC_TARGET_RATE>

</M_FC_LINE>

</MsgRates>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

Feeder with Trigger

Payment.xml

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 64

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.

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 65

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_MSG_FEES_LINE>

<F_MSG_FEES_MANUAL_FEE>2</F_MSG_FEES_MANUAL_FEE>

<F_MSG_FEES_DEDUCT_FROM>P</F_MSG_FEES_DEDUCT_FROM>

<F_MSG_FEES_FEE_AMOUNT>1</F_MSG_FEES_FEE_AMOUNT>

<F_MSG_FEES_FEE_APPLY>NOW</F_MSG_FEES_FEE_APPLY>

<F_MSG_FEES_FEE_CURRENCY>USD</F_MSG_FEES_FEE_CURRENCY>

<F_MSG_FEES_FEE_TYPE_UID>US1^FEDFEE</F_MSG_FEES_FEE_TYPE_UID>

<F_MSG_FEES_PAYING_PARTY>DR</F_MSG_FEES_PAYING_PARTY>

</M_MSG_FEES_LINE>

</MsgFees>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

<M_BI_INFO_LINE>

<F_BI_INFO_DEBIT_TYPE>MAIN</F_BI_INFO_DEBIT_TYPE>

<F_BI_INFO_ACCNO>22222222</F_BI_INFO_ACCNO>

<F_BI_INFO_ACC_CURRENCY>USD</F_BI_INFO_ACC_CURRENCY>

<F_BI_INFO_ACC_OFFICE>XXX</F_BI_INFO_ACC_OFFICE>

<F_BI_INFO_ACC_TRANS_CD>TRN_DR</F_BI_INFO_ACC_TRANS_CD>

<F_BI_INFO_BOOKING_ENT>MINDOL-SYS</F_BI_INFO_BOOKING_ENT>

<F_BI_INFO_AMOUNT>700.0</F_BI_INFO_AMOUNT>

<F_BI_INFO_VALUE_DATE>2009-05-04+02:00</F_BI_INFO_VALUE_DATE>

<F_BI_INFO_BALANCE>160999.34</F_BI_INFO_BALANCE>

<F_BI_INFO_EARMARK_REF>3394777746</F_BI_INFO_EARMARK_REF>

</M_BI_INFO_LINE>

<M_BI_INFO_LINE>

<F_BI_INFO_DEBIT_TYPE>FEE</F_BI_INFO_DEBIT_TYPE>

<F_BI_INFO_ACCNO>26026</F_BI_INFO_ACCNO>

<F_BI_INFO_CURRENCY>GBP</F_BI_INFO_CURRENCY>

<F_BI_INFO_ACC_OFFICE>XXX</F_BI_INFO_ACC_OFFICE>

<F_BI_INFO_ACC_TRANS_CD>TRN_FDR</F_BI_INFO_ACC_TRANS_CD>

<F_BI_INFO_BOOKING_ENT>MINDOL-SYS</F_BI_INFO_BOOKING_ENT>

<F_BI_INFO_AMOUNT>1.0</F_BI_INFO_AMOUNT>

<F_BI_INFO_VALUE_DATE>2009-05-04+02:00</F_BI_INFO_VALUE_DATE>

<F_BI_INFO_BALANCE>160.66</F_BI_INFO_BALANCE>

<F_BI_INFO_EARMARK_REF>3394777747</F_BI_INFO_EARMARK_REF>

</M_BI_INFO_LINE>

</BalanceCheckInf>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 66

</Extn>

</Msg>

</FndtMsg>

Feeder with

Balance earmark inf (including Fees).xml

This example shows Feeder with fees reported but earmark included is only for the principal amount.

<?xml version="1.0" encoding="UTF-8"?>

<contextName>Feeder</contextName>

</credentials>

<P_INIT_SRC_ID>FEED_SYS</P_INIT_SRC_ID>

</Header>

<Msg>

<Pmnt>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"

xmlns:n1="http://www.w3.org/2001/XMLSchema-instance">

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</InitgPty>

</GrpHdr>

<BtchBookg>false</BtchBookg>

<Dbtr>

<Nm>South Pacific</Nm>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<BIC>BRASUS3MXXX</BIC>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 67

</FinInstnId>

</DbtrAgt>

<PmtId>

</PmtId>

<Amt>

</Amt>

<BIC>BOFAUS3NXXX</BIC>

</FinInstnId>

</CdtrAgt>

<Cdtr>

<Id>

<OrgId>

<Othr>

</Othr>

</OrgId>

</Id>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</CdtTrfTxInf>

</PmtInf>

</CstmrCdtTrfInitn>

</Document>

</Pmnt>

<Extn>

<M_MSG_FEES_LINE>

<F_MSG_FEES_MANUAL_FEE>2</F_MSG_FEES_MANUAL_FEE>

<F_MSG_FEES_DEDUCT_FROM>P</F_MSG_FEES_DEDUCT_FROM>

<F_MSG_FEES_FEE_AMOUNT>1</F_MSG_FEES_FEE_AMOUNT>

<F_MSG_FEES_FEE_APPLY>NOW</F_MSG_FEES_FEE_APPLY>

<F_MSG_FEES_FEE_CURRENCY>USD</F_MSG_FEES_FEE_CURRENCY>

<F_MSG_FEES_FEE_TYPE_UID>US1^FEDFEE</F_MSG_FEES_FEE_TYPE_UID>

<F_MSG_FEES_PAYING_PARTY>DR</F_MSG_FEES_PAYING_PARTY>

</M_MSG_FEES_LINE>

</MsgFees>

<P_TX_ID>1234567890</P_TX_ID>

</ProcessingPersistentInfo>

<M_BI_INFO_LINE>

<F_BI_INFO_DEBIT_TYPE>MAIN</F_BI_INFO_DEBIT_TYPE>

<F_BI_INFO_ACCNO>22222222</F_BI_INFO_ACCNO>

<F_BI_INFO_ACC_CURRENCY>USD</F_BI_INFO_ACC_CURRENCY>

<F_BI_INFO_ACC_OFFICE>XXX</F_BI_INFO_ACC_OFFICE>

<F_BI_INFO_ACC_TRANS_CD>TRN_DR</F_BI_INFO_ACC_TRANS_CD>

<F_BI_INFO_BOOKING_ENT>MINDOL-SYS</F_BI_INFO_BOOKING_ENT>

<F_BI_INFO_AMOUNT>700.0</F_BI_INFO_AMOUNT>

<F_BI_INFO_VALUE_DATE>2009-05-04+02:00</F_BI_INFO_VALUE_DATE>

<F_BI_INFO_BALANCE>160999.34</F_BI_INFO_BALANCE>

<F_BI_INFO_EARMARK_REF>3394777746</F_BI_INFO_EARMARK_REF>

</M_BI_INFO_LINE>

</BalanceCheckInf>

</Extn>

</Msg>

</FndtMsg>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 68

Feeder with

Balance earmark inf (no eramark on Fees).xml

C. 10 Successful Outgoing Single Transaction Handoff Response –

Minimal Scope

<?xml version="1.0" encoding="UTF-8"?>

<P_MID>159R2344307I2862</P_MID>

</Header>

<Msg>

<Pmnt>

</GrpHdr>

<OrgnlMsgId>FUNDT11</OrgnlMsgId>

</OrgnlGrpInfAndSts>

<OrgnlInstrId>TESTWW1FF1</OrgnlInstrId>

<Amt>

</Amt>

<Dbtr>

<Nm>FIGUEIRELS</Nm>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<Cdtr>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</OrgnlTxRef>

</TxInfAndSts>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 69

</OrgnlPmtInfAndSts>

</CstmrPmtStsRpt>

</Document>

</Pmnt>

<Extn>

<P_MSG_STS>COMPLETE</P_MSG_STS>

<P_TX_ID>15092300002S</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</OrigMsg>

</FndtMsg>

Succesfull Feeder

Acknowledgment - minimal scope.XML

C. 11 Successful Outgoing Single Transaction Handoff Response –

Extended Scope

<?xml version="1.0" encoding="UTF-8"?>

<P_MID>159R2344307I2862</P_MID>

</Header>

<Msg>

<Pmnt>

</GrpHdr>

<OrgnlMsgId>FUNDT11</OrgnlMsgId>

</OrgnlGrpInfAndSts>

<OrgnlInstrId>TESTWW1FF1</OrgnlInstrId>

<Amt>

</Amt>

<Dbtr>

<Nm>FIGUEIRELS</Nm>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 70

</DbtrAcct>

<Cdtr>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</OrgnlTxRef>

</TxInfAndSts>

</OrgnlPmtInfAndSts>

</CstmrPmtStsRpt>

</Document>

</Pmnt>

<Extn>

<P_CDT_ACCT_CCY>GBP</P_CDT_ACCT_CCY>

<P_CDT_ACCT_NB>26815573499</P_CDT_ACCT_NB>

<P_CDT_ACCT_OFFICE>LDS</P_CDT_ACCT_OFFICE>

<P_CDT_AMT>23.0</P_CDT_AMT>

<P_CDT_CROSS_CONV/>

<P_CDT_CUST_CD>BDBTEST1LN1</P_CDT_CUST_CD>

<P_CDT_MOP>BOOK</P_CDT_MOP>

<P_CDT_TX_CD>001</P_CDT_TX_CD>

<P_CDT_VD>2015-09-24</P_CDT_VD>

</CreditSide>

<P_DBT_ACCT_CCY>GBP</P_DBT_ACCT_CCY>

<P_DBT_ACCT_NB>8000000180</P_DBT_ACCT_NB>

<P_DBT_ACCT_OFFICE>LDS</P_DBT_ACCT_OFFICE>

<P_DBT_AMT>23.0</P_DBT_AMT>

<P_DBT_CUST_CD>AMITTest4645</P_DBT_CUST_CD>

<P_DBT_MOP>BOOK</P_DBT_MOP>

<P_DBT_TX_CD>100</P_DBT_TX_CD>

<P_DBT_VD>2015-09-24</P_DBT_VD>

</DebitSide>

<P_BASE_AMT>23.0</P_BASE_AMT>

<P_BASE_CCY>GBP</P_BASE_CCY>

<P_BA_CD>GBP</P_BA_CD>

<P_DEPARTMENT>LNP</P_DEPARTMENT>

<P_DESTINATION_DEPARTMENT>LNP</P_DESTINATION_DEPARTMENT>

<P_DESTINATION_OFFICE>LDS</P_DESTINATION_OFFICE>

<P_DISPLAY_MSG_TYPE>PACS008</P_DISPLAY_MSG_TYPE>

<P_FC_INFO_IND>M</P_FC_INFO_IND>

<P_IS_HISTORY>0</P_IS_HISTORY>

<P_MSG_CLASS>PAY</P_MSG_CLASS>

<P_MSG_STS>COMPLETE</P_MSG_STS>

<P_MSG_TYPE>Pain_002</P_MSG_TYPE>

<P_OFFICE>LDS</P_OFFICE>

<P_ORIG_MSG_TYPE>Pacs_008</P_ORIG_MSG_TYPE>

<P_ORIG_STTLM_AMT>23.00</P_ORIG_STTLM_AMT>

<P_ORIG_STTLM_CCY>GBP</P_ORIG_STTLM_CCY>

<P_ORIG_STTLM_DT>2015-09-24</P_ORIG_STTLM_DT>

<P_PMNT_SRC>FDR_GCP</P_PMNT_SRC>

<P_PROC_DT>2015-09-24</P_PROC_DT>

<P_PRODUCT_CD>LNGBP</P_PRODUCT_CD>

<P_RELEASE_DT>2015-09-24</P_RELEASE_DT>

<P_TIME_STAMP>2015-09-27 02:34:43.424</P_TIME_STAMP>

<P_TX_ID>15092300002S</P_TX_ID>

</ProcessingPersistentInfo>

<D_DIRECT_RECEIVER_INDEX>X</D_DIRECT_RECEIVER_INDEX>

</ProcessingTransientInfo>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 71

<MU_COMPLIANCE_FORCE_STS>X</MU_COMPLIANCE_FORCE_STS>

<MU_FORCE_STANDARD_VD>X</MU_FORCE_STANDARD_VD>

<MU_HANDLE_71G_GAP>X</MU_HANDLE_71G_GAP>

<MU_MISSED_CUTOFF>X</MU_MISSED_CUTOFF>

<MU_NSF_FORCE_STS>X</MU_NSF_FORCE_STS>

<MU_PARTY_LIMIT_FORCE_STS>X</MU_PARTY_LIMIT_FORCE_STS>

<MU_PI_FORCE_STS>X</MU_PI_FORCE_STS>

<MU_REQ_FOR_CHARGES_FORCE_STS>X</MU_REQ_FOR_CHARGES_FORCE_STS>

<MU_SET_CDT_MOP>X</MU_SET_CDT_MOP>

<MU_SPECIAL_INST_STS>X</MU_SPECIAL_INST_STS>

<MU_STOP_FLAGS_OVERRIDE_STS>X</MU_STOP_FLAGS_OVERRIDE_STS>

</UserMonitors>

<MF_AF_MATCH_STS>N</MF_AF_MATCH_STS>

<MF_AF_PROCESS_STS>X</MF_AF_PROCESS_STS>

<MF_CANCEL_MATCH_STS>X</MF_CANCEL_MATCH_STS>

<MF_CANCEL_REQUEST_VALID_STS>X</MF_CANCEL_REQUEST_VALID_STS>

<MF_CDT_STOP_FLAGS_STS>N</MF_CDT_STOP_FLAGS_STS>

<MF_COMPLIANCE_VALIDATION_STS>B</MF_COMPLIANCE_VALIDATION_STS>

<MF_CRD_FEES_POSTING_STS>B</MF_CRD_FEES_POSTING_STS>

<MF_CREDIT_POSTING_STS>B</MF_CREDIT_POSTING_STS>

<MF_CREDIT_R_POSTING_STS>X</MF_CREDIT_R_POSTING_STS>

<MF_DBT_FEES_POSTING_STS>B</MF_DBT_FEES_POSTING_STS>

<MF_DBT_STOP_FLAGS_STS>N</MF_DBT_STOP_FLAGS_STS>

<MF_DEBIT_POSTING_STS>B</MF_DEBIT_POSTING_STS>

<MF_DEBIT_R_POSTING_STS>X</MF_DEBIT_R_POSTING_STS>

<MF_DIRECT_COVER_GENERATED>X</MF_DIRECT_COVER_GENERATED>

<MF_FEE_PROC_STS>P</MF_FEE_PROC_STS>

<MF_GENERATED_ANSWER_MESSAGE>X</MF_GENERATED_ANSWER_MESSAGE>

<MF_GENERATED_CANCEL_REQUEST>X</MF_GENERATED_CANCEL_REQUEST>

<MF_GENERATE_REQ_CHARGES>X</MF_GENERATE_REQ_CHARGES>

<MF_INITIAL_CREATE>X</MF_INITIAL_CREATE>

<MF_LC_MATCH_STS>X</MF_LC_MATCH_STS>

<MF_LC_PROCESS_STS>X</MF_LC_PROCESS_STS>

<MF_MOP_SELECTION_STS>S</MF_MOP_SELECTION_STS>

<MF_NUM_OF_191>X</MF_NUM_OF_191>

<MF_NUM_OF_210>X</MF_NUM_OF_210>

<MF_N_MESSAGES_MATCH_STS>X</MF_N_MESSAGES_MATCH_STS>

<MF_OPIOSN_MATCH_STS>X</MF_OPIOSN_MATCH_STS>

<MF_OUT_REQ_FOR_CHRG_MATCH_STS>X</MF_OUT_REQ_FOR_CHRG_MATCH_STS>

<MF_PDM>X</MF_PDM>

<MF_PISN_MATCH_STS>X</MF_PISN_MATCH_STS>

<MF_PISN_PROCESS_STS>X</MF_PISN_PROCESS_STS>

<MF_PNL_POSTING_STS>X</MF_PNL_POSTING_STS>

<MF_POSTING_STS>X</MF_POSTING_STS>

<MF_REQ_FOR_CHARGES_MATCH_STS>X</MF_REQ_FOR_CHARGES_MATCH_STS>

<MF_REQ_FOR_CHARGES_VALID_STS>X</MF_REQ_FOR_CHARGES_VALID_STS>

<MF_SC_MATCH_STS>N</MF_SC_MATCH_STS>

<MF_SC_PROCESS_STS>X</MF_SC_PROCESS_STS>

<MF_SPECIAL_INST_STS>X</MF_SPECIAL_INST_STS>

<MF_TIME_HOLD>X</MF_TIME_HOLD>

</ServiceMonitors>

</Monitors>

<M_DBT_CUST_PROFILE>

<F_DBT_CUST_ADDRESS1>151 MAIN ST</F_DBT_CUST_ADDRESS1>

<F_DBT_CUST_CITY>STOCKTON</F_DBT_CUST_CITY>

<F_DBT_CUST_COUNTRYCODE>US</F_DBT_CUST_COUNTRYCODE>

<F_DBT_CUST_CUST_CATEGORY>GCP</F_DBT_CUST_CUST_CATEGORY>

<F_DBT_CUST_CUST_CODE>AMITTest4645</F_DBT_CUST_CUST_CODE>

<F_DBT_CUST_CUST_TYPE>CU</F_DBT_CUST_CUST_TYPE>

<F_DBT_CUST_DEPARTMENT>LNP</F_DBT_CUST_DEPARTMENT>

<F_DBT_CUST_PROFESSION>TRNS</F_DBT_CUST_PROFESSION>

<F_DBT_CUST_STATE>CA</F_DBT_CUST_STATE>

<F_DBT_CUST_ZIP>95105</F_DBT_CUST_ZIP>

</M_DBT_CUST_PROFILE>

<M_CDT_CUST_PROFILE>

<F_CDT_CUST_COUNTRYCODE>GB</F_CDT_CUST_COUNTRYCODE>

<F_CDT_CUST_CUST_NAME>BDB LONDON</F_CDT_CUST_CUST_NAME>

<F_CDT_CUST_SWIFT_ID>BRASGB1LXXX</F_CDT_CUST_SWIFT_ID>

</M_CDT_CUST_PROFILE>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 72

<M_STTLM_CCY_PROFILE>

<F_INSTR_CCY_DRAFT>false</F_INSTR_CCY_DRAFT>

<F_INSTR_CCY_EURO>OUT</F_INSTR_CCY_EURO>

</M_STTLM_CCY_PROFILE>

<M_DBT_MOP_PROFILE>

<F_MOP_ALLOW_NAC_MSG>false</F_MOP_ALLOW_NAC_MSG>

<F_MOP_CHK_DRAFT_CURRENCY>false</F_MOP_CHK_DRAFT_CURRENCY>

<F_MOP_MOPDOWN>false</F_MOP_MOPDOWN>

<F_MOP_NM>BOOK</F_MOP_NM>

<F_MOP_SENDOUTMSG>false</F_MOP_SENDOUTMSG>

<F_MOP_SEND_REC_IDCODE>SA</F_MOP_SEND_REC_IDCODE>

<F_MOP_SETTLEMENT_ACC>1</F_MOP_SETTLEMENT_ACC>

<F_MOP_SETT_ACC_EXISTS>false</F_MOP_SETT_ACC_EXISTS>

<F_MOP_SPLIT_OVER_MAX>false</F_MOP_SPLIT_OVER_MAX>

</M_DBT_MOP_PROFILE>

<M_CDT_MOP_PROFILE>

<F_CDT_MOP_ALLOW_NAC_MSG>false</F_CDT_MOP_ALLOW_NAC_MSG>

<F_CDT_MOP_CHK_DRAFT_CCY>false</F_CDT_MOP_CHK_DRAFT_CCY>

<F_CDT_MOP_DOWN>false</F_CDT_MOP_DOWN>

<F_CDT_MOP_NM>BOOK</F_CDT_MOP_NM>

<F_CDT_MOP_SENDOUTMSG>false</F_CDT_MOP_SENDOUTMSG>

<F_CDT_MOP_SEND_REC_IDCODE>SA</F_CDT_MOP_SEND_REC_IDCODE>

<F_CDT_MOP_SETTLEMENT_ACC>1</F_CDT_MOP_SETTLEMENT_ACC>

<F_CDT_MOP_SETT_ACC_EXISTS>false</F_CDT_MOP_SETT_ACC_EXISTS>

<F_CDT_MOP_SNDR_BIC>BRASGB2LXXX</F_CDT_MOP_SNDR_BIC>

<F_CDT_MOP_SPLIT_OVER_MAX>false</F_CDT_MOP_SPLIT_OVER_MAX>

</M_CDT_MOP_PROFILE>

<M_DBT_ACCOUNT>

<F_DBT_ACCT_ACC_TYPE>NOS</F_DBT_ACCT_ACC_TYPE>

<F_DBT_ACCT_IS_RESIDENT/>

<F_DBT_ACCT_STOPFLAGCR/>

<F_DBT_ACCT_STOPFLAGDR/>

</M_DBT_ACCOUNT>

<M_CDT_ACCOUNT>

<F_CDT_ACCT_ACC_TYPE>NOS</F_CDT_ACCT_ACC_TYPE>

<F_CDT_ACCT_IS_RESIDENT/>

<F_CDT_ACCT_STOPFLAGCR/>

<F_CDT_ACCT_STOPFLAGDR/>

</M_CDT_ACCOUNT>

</ReferenceData>

</Extn>

</Msg>

</OrigMsg>

</FndtMsg>

Succesfull Feeder

Acknowledgment - extended scope.XML

C. 12 Failed Outgoing Single Transaction Handoff Response –

Minimal Scope

<?xml version="1.0" encoding="UTF-8"?>

<P_MID>159R2344307I2862</P_MID>

</Header>

<Msg>

<Pmnt>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 73

</GrpHdr>

<OrgnlMsgId>FUNDT11</OrgnlMsgId>

</OrgnlGrpInfAndSts>

<OrgnlInstrId>TESTWW1FF1</OrgnlInstrId>

<Rsn>

</Rsn>

<AddtlInf>Account Number could not be retrieved since Account 80000001890

defined in payment was not found for the</AddtlInf>

</StsRsnInf>

<Amt>

</Amt>

<Dbtr>

<Nm>FIGUEIRELS</Nm>

</Dbtr>

<Id>

<Othr>

</Othr>

</Id>

</DbtrAcct>

<Cdtr>

</Cdtr>

<Id>

<Othr>

</Othr>

</Id>

</CdtrAcct>

</OrgnlTxRef>

</TxInfAndSts>

</OrgnlPmtInfAndSts>

</CstmrPmtStsRpt>

</Document>

</Pmnt>

<Extn>

<P_MSG_STS>P</P_MSG_STS>

<P_TX_ID>15092300002S</P_TX_ID>

</ProcessingPersistentInfo>

</Extn>

</Msg>

</FndtMsg>

GPP PAYplus | Fndt Message Usage for Feeder Interface - Single Transaction Handoff | Page 74

Failed Feeder

Acknowledgment - minimal scope.XML

Technical Guide GPP Fndt Message Usage For Feeder Interface Single Transaction Handoff

Navigation menu

Versions of this User Manual:

Views

Navigation