Skip to content

Approve a spending grant with the official Multipaz Wallet and its Payment card, with no custom card #464

Open
3 of 3 issues completed

Description

@dzuluaga

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) from https://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 delegate support is the Multipaz work.

The work, one issue each:

Reproduce via

The UI, on the hosted dev store.

Steps to reproduce

  1. On an Android phone, install the released Multipaz Wallet.
  2. Add the "Payment card" from the official issuer's OpenID4VCI server at https://issuer.multipaz.org (credential configuration payment_sca_sd_jwt).
  3. 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.
  4. 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

  1. 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.ts also requires that claim to be disclosed (security invariant 5: an explicit positive claim, not "a token was present").
  2. delegate in 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's delegate request (Add the AP2 delegate transaction type openwallet-foundation/multipaz#2011 was closed without merging), so signing needs a patched build.
  3. Issuer certificate chain. dcql.ts notes that without an x5c chain 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.
  4. Docs and tooling point at the custom card. tools/demo-pki/mint/mint-dpc-sdjwt.mjs, its README, and docs/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

Acceptance criteria

  • AC1 With a released Multipaz Wallet and the Payment card from issuer.multipaz.org, signing a grant on credentagent.ai/marketplace-dev ends with the grant authorized. 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.md and 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.

Activity

  1. dzuluaga commented on Nov 12, 2026

    @dzuluaga
    ContributorAuthor

    @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:

    1. The grant signing page asks for a field the official Multipaz Payment card doesn't have #465 — the grant signing page accepts a claim the official SD-JWT Payment card carries. The open point is how to ask for "either claim" so Android's matcher accepts it; you can try that against your build from Support AP2 spending mandates delegated over OpenID4VP. openwallet-foundation/multipaz#2178.
    2. Record a phone run: approve a spending grant with the official Multipaz Payment card #466 — a recorded phone run with the official card that ends with the grant 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.

  2. moved this from Backlog to Ready in CredentAgenton Nov 12, 2026
  3. moved this from Ready to In progress in CredentAgenton Nov 13, 2026
  4. moved this from In progress to In review in CredentAgenton Nov 13, 2026
  5. moved this from In review to In progress in CredentAgenton Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dxDeveloper experienceenhancementNew feature or requestepicTracking epic

Type

No type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions