CMA9 Transaction IDs
Transaction IDs are conditional in the OBIE Read/Write Specification v3.x. There are 4 options for how an ASPSP can treat this field in the API response:
- ASPSPs provide a Unique, Immutable TransactionID from their core system
- ASPSPs generate a Unique TransactionID from a set of Immutable fields
- ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier
- ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one
Each of the CMA9 have been asked to confirm which of these 4 methods they will support, and this is listed below...
ASPSP | Brand / Products confirmed | Option Supported | Live Date |
|---|---|---|---|
| AIB | N/A | 4 (longer term commitment to option 1) | N/A |
| Barclays | All | 3 (longer term commitment to option 1) | Mar-19 |
| BoI | |||
| Danske | PCA/BCA (other products from June 2019) | 1 | Already live - Release 1 |
| HSBC | This applies to PCAs and BCAs and to posted and pending payments, but not to future dated / scheduled payments. This approach applies consistently to all 4 brands: HSBC personal, HSBC business, first direct, M&S Bank. This applies to HSBC's 3.1.1 stack onwards. | 2 | Sep-19 |
| LBG | PCA & BCA (Cards to be considered for future development, but not planned for 2019) | 1 | September 2019 (R4) |
| NBS | Current Accounts & Cards | 1 | Mar-19 |
| RBS | Not confirmed | 4 (working on alternative options) | Not confirmed |
| Santander | All products | 1 | Sep-19 |
© Open Banking Limited 2019 | https://www.openbanking.org.uk/open-licence | https://www.openbanking.org.uk