cards

Tokenized wallet payment

Maya Chen pays Demo Coffee Ltd from a phone wallet. The device presents a network token (a DPAN), not her real card number; Cardnet detokenises it before Bank Alfa authorises. (SYNTHETIC / TRAINING ONLY)

Contributor Shubham Mathure19 July 2026

PAYMENTS SIGNAL · REFERENCE CARD

Actors

Maya Chen (phone wallet)customer
Demo Coffee Ltd (terminal)customer
Meridian Bank (acquirer)bank
Cardnet (card network)infrastructure
Bank Alfa (issuer)bank

Messages

0100 authorisation request (ISO 8583)
0110 authorisation response

The sequence

#	Step	Route	Kind
1	Provisioned — The card was already tokenised onto the device	Maya Chen	internal
2	DPAN + crypto — Maya taps her phone to pay	Maya Chen → Demo Coffee	message
3	0100 token — The terminal sends an authorisation request on the token	Demo Coffee → Meridian Bank	message
4	0100 routed — Meridian Bank routes the request to Cardnet	Meridian Bank → Cardnet	message
5	Detokenise — Cardnet checks the token domain and detokenises	Cardnet	internal
6	0100 detokenised — Cardnet forwards the detokenised request to Bank Alfa	Cardnet → Bank Alfa	message
7	0110 approve — Bank Alfa approves and responds	Bank Alfa → Cardnet	message
8	Card cycle — The purchase settles in the card cycle	Bank Alfa → Meridian Bank	settlement
9	DR card acct — Bank Alfa posts the debit to Maya's real account	Bank Alfa	posting
10	CR merchant — Meridian Bank pays out to Demo Coffee	Meridian Bank	posting

Exception rails

Rail	Trigger	Where the money ends up	Next action
Decline: token used outside its domain	The DPAN is presented from a different device or in a channel the token was not issued for — a sign the token was copied rather than used from Maya's phone.	Untouched — no hold, no debit, and no money moved. · None. A declined authorisation never reaches the card cycle.	Cardnet — Maya re-provisions or pays from her own device; the copied token stays useless outside its domain.