+ All Categories
Home > Documents > Integration Guidelines: A2A Instant Payments

Integration Guidelines: A2A Instant Payments

Date post: 18-Nov-2021
Category:
Upload: others
View: 8 times
Download: 0 times
Share this document with a friend
14
Transcript
Page 1: Integration Guidelines: A2A Instant Payments
Page 2: Integration Guidelines: A2A Instant Payments

Integration Guidelines: A2A Instant Payments

ForғProduct managers and program developers of WalletsClub full participants

1: Send or receive money

Standard procedure

Messageғpacs.008

ISO 20022 Messaging Specifications

Scope

The FinancialInstitutionToFinancialInstitutionCustomerCreditTransfer message is sent by the debtor agent to the creditor

agent, directly or through other agents and/or a payment clearing and settlement system. It is used to move funds from a

debtor account to a creditor.

Usage

The FIToFICustomerCreditTransfer message is exchanged between agents and can contain one or more customer credit

transfer instructions.

The FIToFICustomerCreditTransfer message does not allow for grouping: a CreditTransferTransactionInformation block

must be present for each credit transfer transaction.

The FIToFICustomerCreditTransfer message can be used in different ways:

If the instructing agent and the instructed agent wish to use their direct account relationship in the currency of the

transfer then the message contains both the funds for the customer transfer(s) as well as the payment details;

If the instructing agent and the instructed agent have no direct account relationship in the currency of the transfer, or

do not wish to use their account relationship, then other (reimbursement) agents will be involved to cover for the

customer transfer(s). The FIToFICustomerCreditTransfer contains only the payment details and the instructing agent

Page 3: Integration Guidelines: A2A Instant Payments

must cover the customer transfer by sending a FinancialInstitutionCreditTransfer to a reimbursement agent. This

payment method is called the Cover method;

If more than two financial institutions are involved in the payment chain and if the FIToFICustomerCreditTransfer is

sent from one financial institution to the next financial institution in the payment chain, then the payment method is

called the Serial method.

The FIToFICustomerCreditTransfer message can be used in domestic and cross-border scenarios.

Outline

The FIToFICustomerCreditTransferV09 MessageDefinition is composed of 3 MessageBuildingBlocks:

A. GroupHeader

Set of characteristics shared by all individual transactions included in the message.

B. CreditTransferTransactionInformation

Set of elements providing information specific to the individual credit transfer(s).

C. SupplementaryData

Additional information that cannot be captured in the structured elements and/or any other specific block.

Example

{

"AppHdr": {

"BizMsgIdr": "B20210527YSJLHKHHXXXBPSP81298868970",

"CreDt": "2021-05-27T10:55:45",

"Fr": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

}

},

"MsgDefIdr": "pacs.008.001.09",

"To": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WCSMHKHKXXX"

}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Page 4: Integration Guidelines: A2A Instant Payments

}

}

}

},

"Document": {

"FIToFICstmrCdtTrf": {

"CdtTrfTxInf": {

"Cdtr": {

"Nm": "Shen Jun"

},

"CdtrAcct": {

"Id": {

"Othr": {

"Id": "[email protected]"

}

}

},

"CdtrAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "GCSHPHMMXXX"

}

}

},

"ChrgBr": "SLEV",

"Dbtr": {

"Nm": "Cai You Meng"

},

"DbtrAcct": {

"Id": {

"Othr": {

"Id": "[email protected]"

}

}

},

"DbtrAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

},

"InstdAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "GCSHPHMMXXX"

}

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

Page 5: Integration Guidelines: A2A Instant Payments

}

},

"InstgAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

},

"IntrBkSttlmAmt": {

"Amount": "1245.74",

"Ccy": "PHP"

},

"PmtId": {

"EndToEndId": "20210527YSJLHKHHXXXBWPSP62258652831",

"InstrId": "20210527YSJLHKHHXXXBWPSP62258652831",

"TxId": "20210527YSJLHKHHXXXBWPSP62258652831"

},

"PmtTpInf": {

"LclInstrm": {

"Prtry": "BUSINESS"

},

"SvcLvl": {

"Cd": "SDVA"

}

},

"RgltryRptg": [

{

"DbtCdtRptgInd": "CRED",

"Authrty": {

"Nm": "WWbnI",

"Ctry": "HKG"

},

"Dtls": [

{

"Tp": "NZEF",

"Dt":"2021-05-27",

"Ctry":"HKG",

"Cd":"WHUQX",

"Amt":"1245.74",

"Inf": [

"yokel-gaw-oxygas-psha-peppin-buyer-vined"

]

}

]

}

]

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

10

010

110

210

310

410

510

610

710

810

911

011

111

211

311

Page 6: Integration Guidelines: A2A Instant Payments

Messageғpacs.002

ISO 20022 Messaging Specifications

Scope

The FIToFIPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is

used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to

report on a pending instruction.

Usage

The FIToFIPaymentStatusReport message is exchanged between agents to provide status information about instructions

previously sent. Its usage will always be governed by a bilateral agreement between the agents.

The FIToFIPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance)

of a credit transfer instruction, a direct debit instruction, as well as other intraagent instructions (for example

FIToFIPaymentCancellationRequest).

The FIToFIPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of

references and a set of elements from the original instruction.

},

"GrpHdr": {

"CreDtTm": "2021-05-27 10:55:45",

"IntrBkSttlmDt": "2021-05-27",

"MsgId": "M20210527YSJLHKHHXXXBPSP17221563853",

"NbOfTxs": 1,

"SttlmInf": {

"ClrSys": {

"Cd": "WNET"

},

"SttlmMtd": "CLRG"

},

"TtlIntrBkSttlmAmt": {

"Amount": "1245.74",

"Ccy": "PHP"

}

}

}

}

}

411

511

611

711

811

912

012

112

212

312

412

512

612

712

812

913

013

113

213

313

413

513

Page 7: Integration Guidelines: A2A Instant Payments

The FIToFIPaymentStatusReport message can be used in domestic and cross-border scenarios.

The FIToFIPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both

sides of the transactions must be informed of the status of the transaction (for example either the beneficiary is credited,

or the transaction is rejected).

Outline

The FIToFIPaymentStatusReportV11 MessageDefinition is composed of 4 MessageBuildingBlocks:

A. GroupHeader

Set of characteristics shared by all individual transactions included in the status report message.

B. OriginalGroupInformationAndStatus

Original group information concerning the group of transactions, to which the status report message refers to.

C. TransactionInformationAndStatus

Information concerning the original transactions, to which the status report message refers.

D. SupplementaryData

Additional information that cannot be captured in the structured elements and/or any other specific block.

Example

NOTE: This is a POSITIVE feedback message (pacs.002) from Participant #2. Transaction has been accepted by

Participant #2.

{

"AppHdr": {

"BizMsgIdr": "B20210527WXJJPHMMXXXBPSP78918650741",

"CreDt": "2021-05-27T12:20:55",

"Fr": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WXJJPHMMXXX"

}

}

}

},

"MsgDefIdr": "pacs.002.001.11",

"To": {

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Page 8: Integration Guidelines: A2A Instant Payments

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WCSMHKHKXXX"

}

}

}

}

},

"Document": {

"FIToFIPmtStsRpt": {

"GrpHdr": {

"CreDtTm": "2021-05-27 12:20:55",

"MsgId": "M20210527WXJJPHMMXXXBPSP98156093890"

},

"OrgnlGrpInfAndSts": {

"OrgnlCreDtTm": "2021-05-27 12:20:55",

"OrgnlMsgId": "M20210527WCSMHKHKXXXHNET14615209834",

"OrgnlMsgNmId": "pacs.008.001.09",

"OrgnlNbOfTxs": 1

},

"TxInfAndSts": {

"AccptncDtTm": "2021-05-27 12:20:55",

"InstdAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

},

"InstgAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WXJJPHMMXXX"

}

}

},

"OrgnlInstrId": "20210527YSJLHKHHXXXBWPSP65698172762",

"TxSts": "RCVD"

}

}

}

}

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

Page 9: Integration Guidelines: A2A Instant Payments

Messageғadmi.002

ISO 20022 Messaging Specifications

Scope

The MessageReject message is sent by a central system to notify the rejection of a previously received message.

Usage

The message provides specific information about the rejection reason.

Outline

The MessageRejectV01 MessageDefinition is composed of 2 MessageBuildingBlocks:

A. RelatedReference

Refers to the identification of the message previously received and for which the rejection is notified.

B. Reason

General information about the reason of the message rejection.

Example

NOTE: This is a NEGATIVE feedback message (pacs.002) from Participant #2. Transaction has been Declined by

Participant #2.

{

"AppHdr": {

"BizMsgIdr": "B20210517WCSMHKHKXXXPSP95392645792",

"MsgDefIdr": "camt.003.001.07",

"CreDt": "2021-02-05",

"Fr": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WXJJPHMMXXX"

}

}

}

},

"To": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

Page 10: Integration Guidelines: A2A Instant Payments

2: Refund

Standard procedure

"MmbId": "WCSMHKHKXXX"

}

}

}

}

},

"Document": {

"MsgRjct": {

"RltdRef": {

"Ref": "B20210527ALPYHKHHXXXBPSP81298868970"

},

"Rsn": {

"RjctgPtyRsn": "690",

"AddtlData": "eyJhbGciOiJFUzU........."

}

}

}

}

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

Page 11: Integration Guidelines: A2A Instant Payments

Messageғpacs.008

ISO 20022 Messaging Specifications

Scope

Same as above.

Usage

Same as above.

Example

NOTE: The refund request message (pacs.008) MUST involve the original message information (see RmtInf section)

{

"AppHdr": {

"BizMsgIdr": "B20210329GCSHPHMMXXXBPSP27673869487",

"CreDt": "2021-03-29T14:57:32",

"Fr": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "GCSHPHMMXXX"

}

}

}

},

"MsgDefIdr": "pacs.008.001.09",

"To": {

"FIId": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "WCSMHKHKXXX"

}

}

}

}

},

"Document": {

"FIToFICstmrCdtTrf": {

"CdtTrfTxInf": {

"Cdtr": {

"Nm": "Cai You Meng"

},

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

Page 12: Integration Guidelines: A2A Instant Payments

"CdtrAcct": {

"Id": {

"Othr": {

"Id": "[email protected]"

}

}

},

"CdtrAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

},

"ChrgBr": "SLEV",

"Dbtr": {

"Nm": "Shen Jun"

},

"DbtrAcct": {

"Id": {

"Othr": {

"Id": "[email protected]"

}

}

},

"DbtrAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "GCSHPHMMXXX"

}

}

},

"InstdAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "YSJLHKHHXXX"

}

}

},

"InstgAgt": {

"FinInstnId": {

"ClrSysMmbId": {

"MmbId": "GCSHPHMMXXX"

}

}

},

"IntrBkSttlmAmt": {

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

Page 13: Integration Guidelines: A2A Instant Payments

"Amount": "626.00",

"Ccy": "PHP"

},

"PmtId": {

"EndToEndId": "20210329GCSHPHMMXXXBWPSP62568915598",

"InstrId": "20210329GCSHPHMMXXXBWPSP62568915598",

"TxId": "20210329GCSHPHMMXXXBWPSP62568915598"

},

"PmtTpInf": {

"LclInstrm": {

"Prtry": "BUSINESS"

},

"SvcLvl": {

"Cd": "SDVA"

}

},

"RmtInf": {

"Strd": {

"RfrdDocInf": {

"Nb": "20210329YSJLHKHHXXXBWPSP21364964358",

"RltdDt": "2021-03-29"

}

},

"Ustrd": "this is a refund"

},

"RgltryRptg": [

{

"DbtCdtRptgInd": "CRED",

"Authrty": {

"Nm": "WWbnI",

"Ctry": "HKG"

},

"Dtls": [

{

"Tp": "NZEF",

"Dt":"2021-03-29",

"Ctry":"PHP",

"Cd":"WHUQX",

"Amt":"626.00",

"Inf": [

"fremp-blind-prod-juv-tuf-zof-mom-brak"

]

}

]

}

]

},

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

10

010

110

210

310

410

510

610

710

810

911

011

111

211

311

411

511

611

711

811

912

012

112

212

312

Page 14: Integration Guidelines: A2A Instant Payments

"GrpHdr": {

"CreDtTm": "2021-03-29 14:57:32",

"IntrBkSttlmDt": "2021-03-29",

"MsgId": "M20210329GCSHPHMMXXXBPSP51298638899",

"NbOfTxs": 1,

"SttlmInf": {

"ClrSys": {

"Cd": "WNET"

},

"SttlmMtd": "CLRG"

},

"TtlIntrBkSttlmAmt": {

"Amount": "626.00",

"Ccy": "PHP"

}

}

}

}

}

412

512

612

712

812

913

013

113

213

313

413

513

613

713

813

914

014

114

214


Recommended