In addition to the transactionId
provided by most banks, GoCardless now generates a unique ID for each transaction. The data point is called internalTransactionId
and is returned on the GET/api/v2/accounts/{id}/transactions/
endpoint.
These IDs are unique within the scope of one bank account (based on GoCardless account_id
), meaning that they are not globally unique across the many bank accounts you might be accessing via GoCardless.
Note the difference between transactionId
, which is provided by most (but not all) banks and can vary wildly between institutions, and internalTransactionId
, which is consistent across all of GoCardless Open Banking coverage:
{
"transactionId": "2022102000494539-1", <--- Bank-generated original ID
"bookingDate": "2022-10-20",
"valueDate": "2022-10-20",
"transactionAmount": {
"amount": "-5.50",
"currency": "EUR"
},
"remittanceInformationUnstructured": "bla bla (222095) Kafejnica Sala-VEF 2 LV-1039 Riga",
"bankTransactionCode": "PMNT",
"internalTransactionId": "d8f93e27c3fd639e111f95fd49647fc7" <-- GoCardless-generated ID
},
Be aware that internalTransactionId
is generated only for booked transactions and not for the pending ones.
If you need unique identifiers across all connected accounts please use: account_id+internalTransactionId
This feature is implemented for all banks across our coverage.
Comments
0 comments
Please sign in to leave a comment.