For wallets
Be the rail agents reach for.
Carry a signed, user-approved payment mandate inside the agent surface, with no redirect to break the flow. Prove intent, keep a clear delegation and liability chain, and become the default way agents pay.
{"mandate": {"amount": "129.00","currency": "USD","merchant": "shop.example","scope": "single-use"},"human": {"passkey": "approved","aal": "AAL2"},"result": "signed_mandate"}
Why wallets need agent-ready payment authorization
As AI agents start to transact on behalf of people, the wallet that can sign a user-approved payment mandate inside the agent surface, without a redirect that breaks the flow, becomes the default rail agents reach for. LoginID lets your wallet run the approval ceremony in-context with a single passkey gesture at NIST AAL2, return a non-repudiable signed mandate, and keep a clear delegation and liability chain for every agent-initiated payment.
Stay in the flow. Prove the intent. Keep the liability clear.
Embedded ceremony, no redirect
Run the approval inside the agent surface. No bounce to a browser, no broken context. The user approves with a passkey and the agent continues.
Non-repudiable proof of intent
Every payment carries a cryptographically signed, user-approved mandate. You can prove exactly what the human authorized, when, and for how much.
Clear delegation and liability
A signed delegation chain ties the agent to the human and the wallet. Disputes resolve against proof, not guesswork.
Built-in strong authentication
Phishing-resistant SCA satisfies PSD2 and NIST AAL2 without a password to steal or an OTP to intercept.
How a wallet signs for an agent.
- 01
Agent requests a payment
The agent presents the purchase to your wallet with the merchant, amount, and scope.
- 02
Human approves with a passkey
The user confirms in-surface with a single tap at AAL2, with no redirect and no password.
- 03
Wallet returns a signed mandate
You hand back a single-use, scoped, non-repudiable mandate the merchant and network can trust.
Frequently asked questions
- How does a wallet authorize an agent payment without a redirect?
- LoginID runs the approval ceremony inside the agent surface. The user confirms the merchant and amount with a single passkey gesture at AAL2, and the wallet returns a signed, single-use mandate, with no bounce to a browser and no broken context.
- What is proof of intent for an agent payment?
- Proof of intent is a cryptographically signed, user-approved mandate that records exactly what the human authorized, when, and for how much. It is non-repudiable, so disputes resolve against proof rather than guesswork.
- How is liability handled when an agent pays from a wallet?
- A signed delegation chain ties the agent to the human and the wallet. That clear chain of accountability is what lets networks and merchants trust the payment and resolve disputes cleanly.
- Does this satisfy PSD2 SCA?
- Yes. The approval delivers phishing-resistant Strong Customer Authentication that satisfies PSD2 and NIST AAL2, with no password to steal or OTP to intercept.
Become the wallet agents reach for.
Sign user-approved mandates inside the agent surface with a single integration: proof of intent and a clear liability chain, in days not quarters.