What is device-tokenised payment?¶
A device-tokenised payment uses a substitute identifier issued for a wallet or endpoint instead of exposing the underlying card number. That token can distinguish a payment route even when several devices use the same card account.
Provisioning creates the relationship¶
The issuer, network or wallet provider maps the token to the card and provisioning event. Different phones or watches can receive different tokens, and a token may later be suspended, deleted or reactivated.
The transaction record can contain the token, wallet, merchant, authentication result and reference. It does not necessarily contain the physical card number or identify the human operator.
Resolve the token before attributing use¶
Preserve the token exactly and obtain its mapping, lifecycle and provisioning verification. Compare the transaction time with endpoint evidence, wallet notifications, location and other context.
Deletion from the visible wallet need not remove provider history. Report token, endpoint, wallet, card account and user separately, with any mapping limitation stated.
The point to remember
A device token identifies a provisioned payment relationship; provider mapping and contextual evidence are still needed to establish the card and user.