Pending and Posted Transactions

Matching Pending and Posting Transactions

If the Data Holder wishes to match the pending and posted transaction, it is perfectly acceptable to allow for this kind of linkage using the transaction ID. However, it is not a requirement to make this linkage.

Pending and Posted Transaction duplication

There is no requirement from the Consumer Data Standards to correlate pending and posted transactions, in order to avoid duplicate transactions. This has been deliberately excluded from the standards as a requirement due to feedback from the banking community.

Pending Transactions on Accounts

Regarding the phasing of the transaction end points, the phasing guidance is applicable to accounts.  Once an account is in scope there is no phasing of transaction types.  All transactions lodged against an account are in scope once the account is in scope.  The transaction APIs should present the same list as can be seen by the customer in their internet banking experience.

Marking of specific transaction types as pending is at the discretion of the Data Holder.

POSTED transaction data changes

Data may change for the same POSTED transaction retrieved a day apart. DSB recommends that any data shared through CDR match what is provided to the consumer through other channels.