Who can use this feature?
PayBox is available globally. You don't need a MoonPay account — PayBox is a standalone product with its own onboarding.
Overview
AI agents are powerful — but handing one your raw card number or wallet key is asking for trouble. PayBox fixes that by separating your credentials from the agents that use them.
Think of it as 1Password meets Stripe Link, built for agentic workflows. Store credentials in PayBox once, create scoped agent clients with explicit permissions, and let PayBox enforce your rules. For cards and wallets, agents never see the underlying credential — they receive derived, limited-use outputs like one-time virtual cards or transaction signatures. For secrets, you decide what's released and when.
Important: Money never moves through PayBox infrastructure. PayBox is a control plane — it gates who can authorize a payment and under what conditions. Funds move directly from your funding source to the merchant or recipient.
Key benefits
No raw card or wallet exposure — agents receive scoped tokens, signatures, or one-time virtual cards, never your actual card number or wallet key
You stay in control — set approval rules per agent client, including spend limits, allowed merchants, and whether each operation needs your sign-off
Full audit trail — every request, approval, denial, and timeout is logged so you can see exactly what your agents did and when
One vault for everything — wallets, payment cards, and secrets, all under a single policy layer
What PayBox stores
PayBox can hold several types of sensitive material on your behalf.
Wallets — on-chain wallets managed via MPC infrastructure; PayBox signs transactions without ever returning your private key to an agent
Secrets — API keys, passwords, identity documents (KYC), and any other named credentials you choose to provision to trusted agent clients
Payment cards — credit cards tokenized so raw card data never touches PayBox servers (Coming in a future release)
Important: Secrets are returned as raw credentials to agent clients you've granted access to, based on the rules you set. Only store a secret in PayBox if you're comfortable with that secret being shared with your agents.
How approval works
Approval is a first-class part of every agent interaction, not an afterthought. You choose an approval mode for each agent client when you set it up.
Approval modes
Always approve — every operation pauses for your explicit sign-off before PayBox executes it
Approve above limit — small, pre-scoped operations run automatically; anything larger or outside the defined scope requires approval
Autonomous within policy — the agent acts without per-operation approval, but only inside a tightly defined grant you've configured
Tip: For a deeper look at how agent connections work — including grants, client keys, and what agents can and can't do — see how agent connections work in PayBox.
How an approval request flows
Your agent sends an operation to PayBox
PayBox authenticates the agent's client key
PayBox checks the agent's grants and limits against the request
If allowed automatically, PayBox executes it and logs the event
If approval is required, PayBox creates a pending approval and returns pending_approval to the agent
You receive a push notification on mobile or web
You review the request details and approve or deny with passkey or biometric step-up
If approved, PayBox executes exactly the approved operation — no changes allowed
PayBox logs an audit event and returns the result to the agent
Note: If the agent changes the amount, merchant, destination, contract, function, or secret name after submitting a request, it must start a new approval request. Approvals are bound to the exact operation as submitted.
What you'll see on an approval screen
Every approval request shows you the full context before you decide:
Requesting agent client
Credential being accessed
Merchant, domain, or destination address
Amount and currency (for payment operations)
Chain, contract, function, and value (for wallet operations)
Secret name and whether raw secret access is being requested
Expiration time of the request
What agents receive (credential outputs)
What PayBox returns depends on the credential type.
Payment operations — a scoped payment token or one-time virtual card, restricted by merchant, amount, currency, expiration, and use count
Wallet operations — a signature, signed message, or transaction hash; private keys, seed phrases, and MPC shares are never returned
Secret access — the secret itself, returned to the agent based on your grant rules; for high-risk secrets, you can require your approval before release
Tip: You can always export your own wallet private key or any of your raw secrets back to yourself from the PayBox dashboard. Exports go to you only, never to an agent.
Reviewing your agent activity
PayBox keeps an append-only audit log of every request, decision, and credential issued. You can review your full activity from the PayBox dashboard, and audit events are also sent to you by email so you always have a record of what your agents did.
Revoking agent access
You can revoke an agent client's access at any time. Removing a client's grant immediately prevents it from making further requests. For a full lock on all agent access at once, use the kill switch in your PayBox account settings.
Tip: Review your active agent clients and their grants periodically, especially after completing a project or workflow where an agent no longer needs credential access.
Important: If you think your PayBox has been compromised, use the kill switch immediately and contact our support team. They can freeze your PayBox account while you investigate and re-secure things.
FAQs
Does PayBox move my money?
Does PayBox move my money?
No. PayBox is a control plane for credentials, not a payment processor or custodian. It authorizes and gates operations, then issues scoped credentials to the agent. Actual fund movement happens directly between your funding source and the merchant or recipient.
Can an agent see my raw card number or wallet private key?
Can an agent see my raw card number or wallet private key?
No. Agents receive scoped tokens, signatures, or transaction hashes. Raw cards and private keys are never returned to agents.
What about my secrets — can an agent see those?
What about my secrets — can an agent see those?
Yes, secrets work differently from cards and wallets. When you store a secret in PayBox, it's returned as-is to the agent clients you've granted access to, based on the rules you set. Only store secrets you're comfortable sharing with those agents. You can require approval before any secret is released.
How do I dispute a transaction made by an agent?
How do I dispute a transaction made by an agent?
For card transactions, contact your card provider — they handle disputes the same way they would for any other charge on your card. For wallet transactions, the same rules apply as any non-custodial wallet: on-chain transactions can't be reversed once broadcast, so use approval modes and spend limits to protect yourself.
What if I think my PayBox has been compromised?
What if I think my PayBox has been compromised?
Use the kill switch in your account settings to immediately revoke all agent access. Then contact our support team — they can freeze your PayBox account while you investigate and re-secure things.
Tip: See the PayBox FAQs for more answers, including questions about approval modes, audit logs, geographic availability, and account recovery.