Level 2 cannot be executed yet, and this screen does not simulate it.
Authorising a transaction is a different ceremony, not the same one relabelled: the holder has to see the amount, sign it — so that the signature covers what they read — and type four digits that can only have arrived through the voice of whoever is calling them. Sending the level 1 ceremony under this name would teach everybody to authorise transfers by swiping, which is exactly what the two ceremonies exist to prevent.
In the meantime, to confirm that whoever is on the phone is the holder, use level 1. It authorises no transaction and it says so: that is what separates this ceremony from a permission.
Show technical detail · what is missing and where
- Wallet
- OID4VP transaction_data in the KB-JWT, and refusing to sign if it does not match what was painted. It is the only new cryptography work in the plan.
- te-api · the four digits
- It already mints them in createWakeup, but they do not come out: they are needed in the response of POST /v1/b2b/wakeups — so this CRM can show them — and in GET /v1/requests/pending — so the wallet can ask for them —, and POST /v1/requests/:id/outcome has to check them and kill the challenge on the first failure.
- te-api · the transaction
- The wake-up carries no amount and no recipient. Without them there is nothing to summarise inside the transaction_data.