[ARCHIVE] ID Permanence fields

Archived 2023.01.11. Content moved to Guidance on ID permanence

Question

We have identified the following fields which are subject to the ID Permanence requirements for arbitrariness, uniqueness and immutability across sessions and consents. Can you confirm this is correct?

• Get Accounts (Response Field: accountId)
• Get Bulk Balances (Response Field: accountId)
• Get Balances for Specific Accounts (Input Parameter: accountIds, Response Field: accountId)
• Get Account Balance (Input Parameter: accountId, Response Field: accountId)
• Get Account Detail (Input Parameter: accountId, Response Field: accountId)
• Get Transaction Account (Input Parameter: accountId. Response Field: accountId, transactionId)
• Get Transaction Detail (Input Parameter: acccountId, Response Field: accountId, transactionId)
• Get Direct Debits for Account (Input parameter: accountId, Response Field: accountId)
• Get Bulk Direct Debits (Response Field: accountId)
• Get Direct Debits for Specific Account (Input parameter: accountIds, Response Field: accountId)
• Get Scheduled Payments for Accounts (Input parameter: accountId, Response Field: scheduledPayementId, accountId)
• Get Scheduled Payments Bulk (Response Field: scheduledPaymentId, accountId)
• Get Scheduled Payment for Specific Accounts (Input parameter: accountIds, Response Field: scheduledPaymentId, accountId)
• Get Payees (Response Field: payeeId)
• Get Payee Detail (Input parameter: payeeId, Response Field: payeeId)

Answer

The Data Standards Body (DSB) confirms that the IDs listed (accountId, transactionId, scheduledPayementId and payeeId) are all subject to the ID Permanence rules.

The DSB also confirms that the endpoints listed use the listed IDs.

The DSB cannot confirm that this list is exhaustive.

See:

• CDS ID Permanence