[ARCHIVE] HTTP status for transactionId unavailable

Archived 2022.11.20. Content moved to error scenarios and responses.

Question

In our application, some historical transactions may be removed, or replaced with a new record and new transactionId. 

Is this scenario classified as a data correction, where we need to notify the consumer of the amendment to a transaction listing that was shared earlier, in line with privacy safeguard 11?

Should we respond with HTTP status 402 or a 404 error to a request for the unavailable transactionId?

Answer

transactionIds are unevenly implemented and can change across the lifecycle of various transaction. For this reason the description of the transactionId indicates that it does not need to be provided if there are good technical reasons for the omission. See BankingTransaction, transactionId.

Changes of this type are not considered as data correction, as the data has changed through the normal lifecycle of the data and not through correction of an error.

The correct HTTP status response is 422, as the transactionId is valid and has been previously shared but is no longer available.

HTTP status 404 indicates the transactionId was never valid and is unknown.

See:

• CDS BankingTransaction, transactionId
• CDS Error codes, 404
• CDS Error codes, 422
• CDR Rules, Main section, division 7.2, subdivision 7.2.4, 7.10 Rule relating to privacy safeguard 11 - quality of CDR data