- 18 Sep 2024
- 9 Minutes to read
- Print
- DarkLight
Getting payment details (pacs.008)
- Updated on 18 Sep 2024
- 9 Minutes to read
- Print
- DarkLight
This tutorial describes how you can get payment details with the Payments Hub API.
For this tutorial, consider a scenario where a customer wants to see the ID of each transaction for a payment they have previously made. The Payments Hub API can be used to retrieve these details. The tutorial describes how you can retrieve the payment details using the ISO pacs.008 message.
Note
The instructions in this tutorial apply to the sandbox environment.
Prerequisites
Before obtaining the access token, make sure you have a public-private key pair that you can use to sign JWT Bearer tokens.
Click here to email your public key, along with the kid and iss claim values you will use in your JWT Bearer tokens.
Note
The public key must be created with RSA and sent in PEM format, without password encryption, and must have a length of at least 2048 bits. If these criteria are not met, the token will be rejected.
If you don't have a public-private key pair yet, you can use a predefined JWT Bearer token in the sandbox with no need to create or sign your own tokens for authentication:
eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6InByb1BheW1lbnRzSHViU2IifQ.eyJzdWIiOiJxTWtaOTBxb0hBTjVJbkE2V2xNYVZBaE41dDhBQWVPeCIsImlzcyI6IlNhbnRhbmRlciIsImlhdCI6MTcxMDg0MjgwNCwibmJmIjoxNzEwODQyODA0LCJleHAiOjE3NDIzNzg4MDQsImp0aSI6ImM3YWY0Yzg0LTRkYzQtNDM2Mi05OTA2LWM5ZTg5N2YyNzUzOCJ9.LOaGmVUnQ6I0HYUQWA1y2vUhREaJrAasAxDlqAnxKbEYGmjP6AKeIViLdkBVVPTUWRETxmnlU6fBQRYU0BN8NEJ9dd_uJ20uiPGWp1ieTFvee27LbqqqS-4AbwD_oJluBUzb77cx4P_1o35gFskcFjbzdl5ert4xJvpbXNOQYa0C7f4YQ6wMLjCGkbdhimwRxeOEGVdYiRoVEizkPpNgUZi_H3o58gATIJ4rSSWqLmKvy9aBlK_YAT947klkJI-ej22KU8qgLCInBbBGdoW9gjg8Zpmizs7Xc7eAvNm7QRiAzd1NT6dgX3hAYDJz2m2dnZYS6zE_UPWOi5cbAyQggw
1. Authenticate to get an access token
The Payments Hub API endpoints are protected with OAUTH 2.0 JWT Bearer grant. To use the API, you must create a JWT Bearer token and use it to get an access token:
To create a JWT Bearer token, see the Appendix in Authentication guide. For a predefined token that you can use in the sandbox for testing purposes, see the Prerequisites in Authentication guide.
For detailed instructions on how to get the access token, see Authentication guide.
2. Retrieve the payment details
This section describes how to retrieve the payment details via a pacs.008 HTTP request to the Payments Hub API. To send this request, you need to provide the Payments Hub ID. This section also illustrates a successful response.
Request
Create and send a request using the following operation:
GET https://sandbox.api.pagonxt.com/payments/pacs008/v08/{paymentsHubId}
Headers
The request must contain the headers shown in the following table.
Table: Retrieve payment details – Required request headers.
Header name | Description | Required/Optional | Values |
---|---|---|---|
Authorization | Authorization security header | Required | Bearer <Access token> |
X-Client-Id | Client ID | Required | <Client ID> |
Accept | Format of the response body | Required | application/json |
Parameters
The request must contain the path parameter shown in the following table.
Table: Retrieve payment details – Request parameters.
Parameter type | Parameter name | Description | Data format | Required/Optional |
---|---|---|---|---|
Path | paymentsHubId | Payments Hub ID related to the payment whose details you want to retrieve. This is the value you received when you originally submitted the payment. | String | Required |
Request example
The following example illustrates the request using raw HTTP code:
GET /payments/pacs008/v08/YOUR_PAYMENTS_HUB_ID HTTP/1.1
Host: sandbox.api.pagonxt.com
Content-Type: application/json
Authorization: Bearer YOUR_ACCESS_TOKEN
X-Client-Id: YOUR_CLIENT_ID
Response
If the request is valid, you receive an HTTP 200 OK response, which means that the payment details were successfully retrieved. For further details of HTTP response codes and instructions on how to handle errors, see HTTP codes and request error handling .
In addition to the response code, the response body returns the fitoFICstmrCdtTrf JSON object, which contains a pacs.008 ISO message. This message contains different elements depending on which payment scheme was used in the original transaction.
Response body
The following table shows the response body elements that are relevant for the current use case for the Faster Payments (FP) payment scheme. For details on all the response body elements for all supported payment schemes, see the Message field definition for pacs.008 .
Extract the value of the cdtTrfTxInf.pmtId.txId key to see the transaction IDs for the payment.
Table: Retrieve payment details – Relevant response body elements.
Element | Description | Data type |
---|---|---|
grpHdr.msgId | Message ID, which uniquely identifies each request that was sent. This ID is used internally for idempotency of the API. | String |
grpHdr.creDtTm | Date and time of the payment submission request | String |
grpHdr.nbOfTxs | Number of transactions within the message. Value: 1 | String |
grpHdr.ttlIntrBkSttlmAmt | Data structure containing the payment currency and the amount for the total interbank settlement. The currency is GBP and the amount is a positive value. If these fields are used, the amount is equal to the sum of all the transactions in the message. | Object |
grpHdr.sttlmInf.sttlmMtd | Settlement method. Value: CLRG | String |
cdtTrfTxInf.pmtId.endToEndId | End-to-end ID, which can be used to track the transaction between payment systems. If the ID is not available, the value is NOT PROVIDED. | String |
cdtTrfTxInf.pmtId.txId | Transaction ID, which uniquely identifies each transaction within the message | String |
cdtTrfTxInf.pmtTpInf.svcLvl.prtry | Payment scheme type. Value: FP | String |
cdtTrfTxInf.pmtTpInf.lclInstrm.prtry | Faster Payments Scheme (FPS) processing code | String |
cdtTrfTxInf.pmtTpInf.ctgyPurp.prtry | Payment channel | String |
cdtTrfTxInf.intrBkSttlmAmt | Data structure containing the payment currency and the amount that was transferred. The currency is GBP and the amount is a positive value. | Object |
cdtTrfTxInf.chrgBr | Charge bearer type. The possible values are:
| String |
cdtTrfTxInf ► .intrmyAgt1 ► .intrmyAgt1Acct | Data structures containing the details for the intermediary agent and the agent's account. These structures are required if you use multiple agencies and agency accounts for debiting. | Object |
cdtTrfTxInf ► .dbtr ► .dbtrAcct ► .dbtrAgt | Data structures containing the details for the debtor, the debtor’s account, and the debtor agent | Object |
cdtTrfTxInf ► .cdtrAgt ► .cdtr ► .cdtrAcct | Data structures containing the details for the creditor agent, the creditor, and the creditor’s account | Object |
cdtTrfTxInf.rmtInf | Data structure containing remittance details | Object |
Example response body for the FP payment scheme:
{
"fitoFICstmrCdtTrf": {
"grpHdr": {
"msgId": "MsgId-44458394999944",
"creDtTm": "2022-02-03T11:08:19.664+01:00",
"nbOfTxs": "1",
"sttlmInf": {
"sttlmMtd": "CLRG"
}
},
"cdtTrfTxInf": [
{
"pmtId": {
"endToEndId": "e2eId-1587641040",
"txId": "111112"
},
"pmtTpInf": {
"svcLvl": [
{
"prtry": "FP"
}
],
"lclInstrm": {
"prtry": "SIP"
}
},
"intrBkSttlmAmt": {
"value": 10.04,
"ccy": "GBP"
},
"chrgBr": "SHAR",
"dbtr": {
"nm": "Steve",
"pstlAdr": {
"twnNm": "miltonKeynes",
"ctry": "GB",
"adrLine": [
"Somewhere in MK"
]
}
},
"dbtrAcct": {
"id": {
"othr": {
"id": "12345678"
}
}
},
"dbtrAgt": {
"finInstnId": {
"bicfi": "ABBYGB20",
"clrSysMmbId": {
"mmbId": "090401"
},
"pstlAdr": {
"twnNm": "miltonKeynes",
"ctry": "GB",
"adrLine": [
"Somewhere in MK"
]
}
}
},
"cdtrAgt": {
"finInstnId": {
"bicfi": "ABBYGB3E",
"clrSysMmbId": {
"mmbId": "090401"
},
"pstlAdr": {
"twnNm": "miltonKeynes",
"ctry": "GB",
"adrLine": [
"Somewhere in MK"
]
}
}
},
"cdtr": {
"nm": "Creditor",
"pstlAdr": {
"twnNm": "miltonKeynes",
"ctry": "GB",
"adrLine": [
"Somewhere in MK"
]
}
},
"cdtrAcct": {
"id": {
"iban": "GB91BARC09023134945865"
}
},
"rmtInf": {
"strd": [
{
"cdtrRefInf": {
"ref": "validref123"
}
}
]
}
}
]
}
}