For wallets
Be the wallet that works, or get routed around.
When an AI agent goes to pay, it reaches for the wallet that can approve in-flow and hand back proof the human meant it. Stay inside the transaction with an embedded, passkey-signed payment mandate, or watch agents route to a rail that can.
{"mandate": {"amount": "129.00","currency": "USD","merchant": "shop.example","scope": "single-use"},"human": {"passkey": "approved","aal": "AAL2"},"result": "signed_mandate"}
Why agent-ready wallets win the transaction
As AI agents start to transact on behalf of people, they route payments to the wallet that can approve in the moment and return proof of intent. A wallet that forces a redirect, can't sign a mandate, or can't prove the human meant it gets routed around. LoginID lets your wallet run the approval ceremony inside the agent surface with a single passkey gesture at NIST AAL2, return a non-repudiable signed mandate, and keep a clear delegation and liability chain, so you stay the rail agents reach for.
The agent picks the wallet that works. Make sure that's you.
Stay in the transaction
Run the approval ceremony inside the agent surface. No redirect to a browser, no broken context. The user approves with one passkey gesture and the agent keeps going.
Be agent-ready, not routed around
Agents default to the rail that can return a signed mandate on the spot. Wallets that can't approve in-flow get skipped. Being agent-ready is how you stay the chosen payment method.
Signed mandate as proof of intent
Every payment carries a cryptographically signed, user-approved mandate, proof the human meant it. Exactly what was authorized, when, and for how much.
A clear delegation and liability chain
A signed delegation chain ties the agent to the human and the wallet, so disputes resolve against proof instead of guesswork.
Strong authentication built in
Phishing-resistant SCA satisfies PSD2 and NIST AAL2, with no password to steal or OTP to intercept.
One integration, every agent
Speak the mandate protocol once and become spendable across the agent ecosystem, without rebuilding your checkout for each new platform.
How a wallet stays in the agent's path.
- 01
Agent requests a payment
The agent presents the purchase to your wallet with the merchant, amount, and scope, then looks for a wallet that can approve in-flow.
- 02
Human approves with a passkey
The user confirms in-surface with a single tap at AAL2, with no redirect, no password, and no dropped flow.
- 03
Wallet returns a signed mandate
You hand back a single-use, scoped, non-repudiable mandate the merchant and network can trust, and the agent reaches for you again next time.
Frequently asked questions
- What does it mean for a wallet to be 'agent-ready'?
- An agent-ready wallet can approve a payment inside the agent surface and return a signed, user-approved mandate without forcing a redirect. Agents route to wallets that can do this in-flow; wallets that can't get skipped for one that can.
- How does a wallet stay in the transaction without a redirect?
- LoginID runs the approval ceremony inside the agent surface. The user confirms the merchant and amount with one 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 a signed payment mandate?
- A signed payment mandate is a cryptographically signed, user-approved record of exactly what the human authorized: the merchant, amount, and scope, at AAL2. It is non-repudiable proof of intent, 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.
Stay the wallet agents reach for.
Approve in-flow and return a signed mandate with a single integration: proof of intent and a clear liability chain, so agents route to you, not around you.