Get Transaction Detail X2P1.01 mandatory fields

Question

In the BankingTransactionDetail response to Get Transaction Detail, if the optional field extensionUType is set tox2p101Payload, is the mandatory field service required to be set toX2P1.01?

If extensionUType is not set to x2p101Payload, is the mandatory field service still required?

If a transaction type is NPP (New Payments Platform) then should the the isDetailAvailable be set to TRUE?

In any other case should isDetailAvailable be set to FALSE, and no extendedData block returned?

Answer

A transaction can have extended data only if it was executed using the X2P1.01 overlay service. If an extended payload for X2P1.01 (Osko) is unavailable, there is no response to the transaction detail API, the isDetailAvailable field is set to FALSE and a 404 status response is returned if extended data is requested.

If an extended payload for X2P1.01 (Osko) is available, the fields are set as follows:

• isDetailAvailable = TRUE
• service = X2P1.01
• extensionUType = x2p101Payload
• x2p101Payload contains payload details.

Transaction detail could be extended to describe other payment schemes in the same manner as X2P1.01. The DSB would welcome a change request to that effect if the community saw benefit.

See:

• CDS Get Transaction Detail
• CDS BankingTransactionDetail
• Creating a Change Request