What identifiers should be included in a provider request?¶

Include exact identifiers that locate the account, event and time range, while marking uncertainty and avoiding ambiguous names or screenshots as the sole locator.

Match identifiers to the record sought¶

Account fields can include customer or user ID, contacts, handle and merchant ID. Transaction fields include internal reference, order or request ID, amount, currency, status, counterparties, time and zone. Banking and card routes may need masked details, routing data, descriptor, authorisation and processor references.

For cryptocurrency include exchange account, network, asset and contract, complete addresses and hash, memo or tag. Access requests need defined endpoints, sessions, authentication and changes.

Preserve exact form and provenance¶

Do not shorten, repunctuate or substitute display names for internal IDs. Separate providers and accounts, define which timestamp is known and record the source of every identifier.