Page created: April 30, 2021
The wallet needed an ecosystem.
Designing the 5-Card Brick was the device problem. CanDo was the deployment problem — how you get the wallet actually used by real people at real merchants, issued by real banks, recognized by real governments. A device sitting in a drawer is not a wallet. A wallet only works when every party in a transaction recognizes it.
The Problem CanDo Was Solving
By 2009, the mobile wallet concept was a decade old. The smartphone era had arrived. The technical building blocks — NFC, the Secure Element, BLE, biometric authentication — were either here or imminent. What was missing was not hardware. What was missing was the business architecture that aligned four sets of interests that had never agreed on anything: cardholders, issuers, merchants, and the network connecting them.
The payments industry’s four-party model is elegant in theory. In practice, every party protects its position. Issuers protect their customer relationship. Merchants protect their margin. Networks protect their interchange. Cardholders just want it to work. CanDo was designed to give each party what they actually needed — without requiring any of them to surrender what they would not surrender.
The Architecture
CanDo introduced several design principles that were years ahead of their deployment.
The transaction moves to the background. The friction in payment is not the payment — it is the ritual around the payment. Get out your card. Wait for the terminal. Tap or insert. Wait for approval. Put the card back. CanDo relocated all of that to the background. Walk in, be recognized, select, leave. The transaction completes without ceremony.
The credential is anchored to a Genesis block. Each participant in the CanDo ecosystem was issued a Genesis block — a self-sovereign identity anchor that could not be counterfeited, transferred, or revoked without the holder’s participation. This was not a central registry. It was a distributed trust architecture before blockchain was a common vocabulary.
The BLE pendant as a merchant touchpoint. The merchant-side hardware was a low-energy Bluetooth beacon — a pendant-scale device deployable at any location without payment terminal infrastructure. The wallet talked to the pendant. The pendant talked to the network. The cardholder’s phone never left their pocket.
Loyalty and payment unified. CanDo treated loyalty and payment as the same event, not two separate systems bolted together. Every transaction simultaneously completed a payment and updated a loyalty record. The merchant saw one interaction. The cardholder felt one experience.
What It Predicted
CanDo was prototyped in 2009–2010. The following arrived later:
- Apple Pay’s background transaction model (2014)
- BLE-based merchant beacons for proximity payments (2015–2018)
- Self-sovereign identity frameworks gaining standards traction (2019–present)
- Unified loyalty-payment wallets as the norm in super-apps (2020–present)
The sequence is not coincidence. These are convergent solutions to the same problem. CanDo was an early proof that the problem was solvable — and a demonstration of the architecture that would eventually solve it.
A Conversation About CanDo
Designing the wallet was only half the problem. The other half was building the ecosystem that could issue into it, transact through it, and anchor identity at scale. The identity layer that makes all of this work is explored on the Identity page. The prior art record connecting My Wallet to CanDo is on the My Wallet page.