Skip to content

Record a phone run: approve a spending grant with the official Multipaz Payment card #466

Closed

Description

@dzuluaga

In plain terms

Nobody has yet approved a spending grant on a real phone using the Payment card from the official Multipaz issuer. Everything about that path is read from source code. This issue is the phone run that proves it, and records what the wallet showed.

Part of #464 (approve a spending grant with the official Multipaz Wallet and its Payment card). Needs the gate change in the sibling issue merged first, because the hosted dev store deploys from main.

Reproduce via

The UI.

Steps to run

  1. Build and install the Multipaz wallet from the draft pull request Support AP2 spending mandates delegated over OpenID4VP. openwallet-foundation/multipaz#2178 (branch feat/ap2-delegate-transaction-utopia), with the delegate transaction type registered. A released wallet does not sign that request yet.
  2. In the wallet, add the "Payment card" (payment_sca_sd_jwt) from https://issuer.multipaz.org.
  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", scan the QR code with the phone, and approve in the wallet.
  5. Ask the agent for the grant's status.

What happens today

Not run. With the custom mdoc demo card in the wallet, step 4 ended with "Your info wasn't found" on 2026-11-11 (build dev.ea12b21).

What should happen

The wallet offers the official Payment card, shows what the grant allows, and signs. The grant reads authorized.

Version or commit

credentagent main after the gate change · Multipaz at the head of pull request 2178.


What to record

  • The wallet build (commit) and the phone model and Android version.
  • A screenshot or recording of the wallet's consent screen and of the signed grant page.
  • Whether the card matched on the first try. If the phone says "Your info wasn't found", capture which of these it was: the claim (the sibling gate issue), the issuer certificate chain on the card (dcql.ts notes a card without x5c never matches), or the delegate type not being registered.
  • Whether the wallet showed the verifier as trusted or unknown.

Acceptance criteria

  • AC1 A recorded run ending with the grant authorized, using only the official issuer's card.
  • AC2 No card minted from this repo was imported.
  • AC3 Any failure found on the way is filed as its own issue, here or in Multipaz.

Activity

  1. moved this from Backlog to Ready in CredentAgenton Nov 12, 2026
  2. TheBlackBit commented on Nov 13, 2026

    @TheBlackBit
    Collaborator

    Local run: approved with the official Multipaz Payment card

    Approved a spending grant on a phone with the official SD-JWT Payment card. This was against a local server running PR #468 (via a tunnel), not the hosted dev store, so AC1 stays open until #468 is merged and I repeat it there.

    Video: https://drive.google.com/file/d/130D9wt-dy1PJCfkNJ_utoVcanhWimYOh/view?usp=share_link

    Setup

    • Phone: Samsung SM-S928B, Android 17
    • Wallet: org.multipaz.wallet.android.dev 2026.W46.0-pr-48-176-git-55db8c2-dirty (multipaz-wallet PR 48, on multipaz PR 2178)
    • Card: payment_sca_sd_jwt from https://issuer.multipaz.org. No card minted from this repo.

    What I saw

    • The card matched on the first try.
    • The consent prompt showed the "Spending permission" block and shared only Credential ID.
    • Verifier shown as unknown ("unverified requester"). I did not import a VICAL or RICAL.
    • The grant page read "Authorized", device-signed: $200 per purchase, court-sneakers, $300 total.

    One thing to know
    The issuer lists two cards both named "Payment card": payment_sca_mdoc and payment_sca_sd_jwt. My first attempt failed ("Your info wasn't found") because I had added the mdoc one. A grant needs the SD-JWT one. This goes in the docs (#467).

    Still open

  3. moved this from Ready to In review in CredentAgenton Nov 13, 2026
  4. moved this from In review to In progress in CredentAgenton Nov 13, 2026
  5. moved this from In progress to Ready in CredentAgenton Nov 17, 2026
  6. moved this from Ready to In progress in CredentAgenton Nov 17, 2026
  7. TheBlackBit commented on Nov 18, 2026

    @TheBlackBit
    Collaborator

    Ran it on the hosted dev store (deployed from main at 4a3a863) with the "Utopia Marketplace Dev" connector in Claude, and the grant ended authorized.

    Run: Multipaz Wallet development build, with the SD-JWT "Payment card" from issuer.multipaz.org. Asked for a $300 grant for the Cascade Court Sneakers (max $200 per purchase), opened the approve link in a desktop browser, pressed "Sign with your wallet", scanned the QR code with the phone, and approved in the wallet.

    What happened:

    • Card matched on the first try; the wallet offered the Payment card and shared "Credential ID".
    • Consent screen: $200 per purchase, $300 total, at Utopia, for court-sneakers, until 18 November 2027.
    • Verifier shown as unknown ("The website requesting this data is unknown"). Expected: the request is signed with a self-signed reader certificate (the default), and the wallet has no reader trust list (RICAL) that lists it.
    • The page ended with "Authorized — your agent may now spend within these limits", trust level device-signed. Not issuer-verified.

    Recording: https://youtu.be/D5lfELSPDgA

    Phone and wallet build: Samsung SM-S928B, Android 17. Wallet 2026.W46.0-pr-48-176-git-55db8c2-dirty (built from multipaz-wallet pull request 48, on Multipaz pull request 2178; the build had uncommitted local changes).

    Not covered: the minted test card on a phone.

  8. TheBlackBit commented on Nov 18, 2026

    @TheBlackBit
    Collaborator

    The one failure found on the way is filed as #471: the grant cards are cut off in the claude.ai mobile chat. All three acceptance criteria are now met, so closing.

  9. moved this from In progress to Done in CredentAgenton Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions