commit f5f05a3edd2010a6a3ffdc1a609ea28f5c00f416
parent fab77323629eae1b92e9dc2f18b7a5f687925273
Author: Antoine A <>
Date: Thu, 20 Feb 2025 15:02:28 +0100
DD58 fix layout
Diffstat:
1 file changed, 1 insertion(+), 0 deletions(-)
diff --git a/design-documents/058-ebics-tx-unique-id.rst b/design-documents/058-ebics-tx-unique-id.rst
@@ -10,6 +10,7 @@ Problem
=======
ISO20022 provides three many transaction identifier:
+
* *AcctSvcrRef (AccountServicerReference)*: unique reference, as assigned by the account servicing institution, to unambiguously identify the instruction. The format is ambiguous and is only unique within the account servicing institution database. This identifier can be present a the entry level and/or at the transaction level (a single entry can be a batch of transaction), this make this identifier sometimes a bit ambiguous.
* *UETR (unique end-to-end transaction reference)*: universally unique identifier to provide an end-to-end reference of a payment transaction. This is the perfect unique ID, it's a UUID v4 that is shared with all participant of the transfer.
* *TxId (TransactionIdentification)*: unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. The format is ambiguous and only unique for a “pre-agreed period”, whatever that means, but it is shared all participant of the transfer.
