Account Identifier

Overview

Account identifier is a broader term than account address. It describes the value a system uses to distinguish an account, but it does not require that the value be directly usable as a blockchain destination. In a blockchain protocol, the identifier may be an address, a public-key-derived value, an account index, or a structured key. In an application, it may instead be an internal customer ID or database record key.

This distinction matters because several identifiers can refer to the same real-world user or operational account. A merchant platform might store a customer ID, a payment account ID, one or more blockchain addresses, and an external order reference. These values serve different purposes and should not be substituted for one another.

A reliable system defines the scope of each identifier: whether it is globally unique, unique only inside one platform, reusable, case-sensitive, public, or safe to expose. It should also avoid using mutable data, such as an email address, as the permanent primary identifier for critical records. In payment operations, clear identifier design supports reconciliation, reporting, access control, and accurate linking between off-chain orders and on-chain transactions.

Identifier design has direct consequences for security and reconciliation. A good identifier is stable, unique within its defined scope, and resistant to accidental reuse. For example, an internal account ID can remain constant even when a user rotates a wallet address, while an order ID can connect several payment attempts to one purchase.

Systems should also separate public identifiers from sensitive credentials. An identifier can be safe to expose in URLs or logs, while a secret token or private key cannot. When data moves between platforms, developers should document whether the identifier is globally unique, case-sensitive, mutable, or meaningful only inside one provider. This prevents duplicate records, broken links, and mistaken ownership assumptions.