Repository navigation
Description
In plain terms
To approve a spending grant on a phone today, a developer has to mint a custom payment card with a script in this repo, import it into the wallet by hand, and run a patched wallet build. A spending grant is the limit a person approves once so their agent can buy while they are away.
The goal: a developer, or an agent acting for one, installs the official Multipaz Wallet, adds the Payment card the official Multipaz issuer offers, and approves a grant. No custom card, no script, no patched build. The custom card can stay as a test fixture; it should stop being the path we send people down.
Plan (decided 2026-11-11)
- The card: the official issuer's SD-JWT Payment card,
payment_sca_sd_jwt(urn:emvco:dpc:card:1) fromhttps://issuer.multipaz.org. Not a custom card, and not the mdoc card: the grant signing page stays on one format. - Which side changes for the claim mismatch: the gate. It accepts a claim the official card carries.
- The wallet: a build from the draft pull request Support AP2 spending mandates delegated over OpenID4VP. openwallet-foundation/multipaz#2178 for testing, then a release once that merges.
- Who does what: the gate change and the docs are this repo's work; the wallet's
delegatesupport is the Multipaz work.
The work, one issue each:
- The grant signing page asks for a field the official Multipaz Payment card doesn't have #465 — the grant signing page accepts the official card's claim
- Record a phone run: approve a spending grant with the official Multipaz Payment card #466 — a recorded phone run that ends with the grant
authorized - Docs send developers to a custom payment card instead of the official Multipaz one #467 — the docs describe the official path; the custom card becomes a test fixture
Reproduce via
The UI, on the hosted dev store.
Steps to reproduce
- On an Android phone, install the released Multipaz Wallet.
- Add the "Payment card" from the official issuer's OpenID4VCI server at https://issuer.multipaz.org (credential configuration
payment_sca_sd_jwt). - In claude.ai, with the "Utopia Marketplace Dev" connector (
https://credentagent.ai/marketplace-dev/mcp), ask for a $300 spending grant for the Cascade Court Sneakers. - Open the approve link, press "Sign with your wallet", and scan the QR code with the phone.
What happens
The phone shows "Your info wasn't found — There is no info available to share with another device". The grant stays pending.
Seen on 2026-11-11 against build dev.ea12b21 with the custom mdoc demo card in the wallet. Steps 1–2 with the official SD-JWT card have not been run on a phone yet; the mismatch below is read from the source on both sides and predicts the same message.
What should happen instead
The wallet offers the official Payment card, shows what the grant allows, and signs. The grant becomes authorized.
Version or commit
credentagent main at ea12b21 · Multipaz main at the commit of 2026-11-11.
Details
What the signing page asks the wallet for (decoded from the live request at /credentagent/grants/:id/sign/request; built in packages/credentagent-gate/src/ceremony/intent-sign/dcql.ts and request.ts):
{ "id": "dpc_credential", "format": "dc+sd-jwt",
"meta": { "vct_values": ["urn:emvco:dpc:card:1", "com.emvco.dpc"] },
"claims": [{ "path": ["payment_instrument_id"] }] }plus two transaction_data entries of type delegate (AP2's signed permission), over openid4vp-v1-signed.
What the official issuer offers (https://issuer.multipaz.org/issuer/.well-known/openid-credential-issuer):
| Configuration | Format | Type | Claims (Multipaz main) |
|---|---|---|---|
payment_sca_sd_jwt |
dc+sd-jwt |
urn:emvco:dpc:card:1 |
credential_id, network, last_four |
payment_sca_mdoc |
mso_mdoc |
org.multipaz.payment.sca.1 |
issuer_name, payment_instrument_id, masked_account_reference, holder_name, issue_date, expiry_date |
The gaps
- Claim mismatch on the grant signing page. The type matches, but the page asks for
payment_instrument_id, which the official SD-JWT card does not carry. On Android a request for a claim the card lacks matches nothing.verify.tsalso requires that claim to be disclosed (security invariant 5: an explicit positive claim, not "a token was present"). delegatein a released wallet. Issue Show the "no released wallet can sign yet" caveat where people meet phone signing #413 records that no released wallet signs AP2'sdelegaterequest (Add the AP2delegatetransaction type openwallet-foundation/multipaz#2011 was closed without merging), so signing needs a patched build.- Issuer certificate chain.
dcql.tsnotes that without anx5cchain on the issuer JWT the wallet exports the card to Android's matcher with no claims. The official issuer signs with a certified key (CredentialFactory.getSigningKey()), so this is probably fine. It needs one check on a device. - Docs and tooling point at the custom card.
tools/demo-pki/mint/mint-dpc-sdjwt.mjs, its README, anddocs/guides/testing-on-device.md.
The checkout payment page is not affected: it asks for the mdoc card, and the official payment_sca_mdoc carries the same six claims it requests.
Still to settle
- Whether the gate should check the card's issuer against a trusted list here, or leave that to the issuer-trust work (issue Check a wallet credential against the issuer's certificate and a trusted root, with tests that prove forgeries are refused #392). The trust wording on the page must keep matching what is checked.
Acceptance criteria
- AC1 With a released Multipaz Wallet and the Payment card from
issuer.multipaz.org, signing a grant oncredentagent.ai/marketplace-devends with the grantauthorized. Recorded on a real phone. - AC2 No step uses a card minted from this repo or a patched wallet build.
- AC3 The signing page still refuses a presentation that does not disclose the required claim, and one from a card of another type. The tests fail if either check is removed.
- AC4
docs/guides/testing-on-device.mdand the gate README describe the official path in three steps or fewer: install the wallet, add the card, approve. - AC5 The caveat issue Show the "no released wallet can sign yet" caveat where people meet phone signing #413 asks for is updated or removed to match what a released wallet can do.
- AC6 The custom card tooling is labelled as a test fixture, or removed.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- StatusShow more project fieldsIn progress
Activity
dzuluaga commentedon Nov 12, 2026
@TheBlackBit some context on why this is coming to you now.
We ran into this during a conference demo: approving a spending grant on the phone ended with "Your info wasn't found". The custom payment card (minted from this repo and imported into the wallet by hand) was a stopgap to get phone signing working at all. That was a fine call at the time. But it is still the only path, and anyone who doesn't have that card hits the same wall, including us on stage.
I'd like us to fix this properly and stop carrying the stopgap. The target is what a developer or an agent would do without help: install the Multipaz Wallet, add the Payment card from the official issuer, approve.
I've assigned you the two issues that need your wallet build:
authorized.#467 (the docs) stays unassigned until the phone run passes. The custom card can stay as a test fixture.
If the plan at the top of this issue looks wrong to you, say so here before starting.