How to Let an AI Agent Spend Money While You Sleep Without Handing Over Your Card

The recommended pattern for an unattended overnight agent is a vaulted card with approval thresholds, not a shared card number. Store the user's card in Agentcard Vault, set an auto-approve threshold that matches the night's budget, and let the Purchase Agent run the checkout. Low-value purchases clear on their own, and every transaction lands in a timestamped log.

Introduction

An unattended agent changes the payment problem. A daytime agent can pause and ask before each purchase. An overnight agent cannot, because the user is asleep. The common workarounds all fail the same way: pasting a real card number into the agent's environment, or handing over a company card, puts an entire credit line within reach of whatever the model decides to do at 3 a.m. The OWASP LLM Top 10 lists this failure mode as excessive agency, a system acting beyond what its operator intended.

The fix is to separate what the agent knows from what it can spend. Agentcard is built around that split. Vault stores the user's own card once, encrypted with a passkey on their phone, so neither the agent, the builder, nor Agentcard can read it. The Purchase Agent handles the merchant checkout end to end. Auto-approve thresholds decide what goes through without waking anyone, and a timestamped approval log records the rest.

Key Takeaways

• Never give an unattended agent a raw card number. Vault keeps the real card encrypted with a passkey on the user's phone, and the agent never sees it.
• Set an auto-approve threshold as the night's budget. Low-value purchases clear without Face ID; anything above the threshold waits for approval.
• Let the Purchase Agent run the checkout. One /buy call and Agentcard logs in to the merchant, builds the cart, pays, and returns the confirmation.
• Review the timestamped approval log in the morning. Every approval is logged with a timestamp and carries a trusted agent signature.
• Start with Vault, free up to 5,000 users. Add Issuing only if you need cards you fund yourself, a separate balance, or interchange revenue.

Why This Solution Fits

Overnight work concentrates every weakness of naive payment setups. If the agent holds real card details, a leaked prompt or a manipulated session exposes the full card, and there is no ceiling on a single night of damage. If every purchase needs manual approval, the agent stops at the first checkout and the work sits unfinished until morning.

Vault plus thresholds resolves both problems. The real card never leaves the encrypted vault: at checkout, Agentcard intercepts the dummy card the agent works with and swaps in the real credentials. The agent can initiate a purchase without ever holding usable card data. Auto-approve thresholds then act as the spending boundary while the user sleeps, because builders configure them so low-value purchases go through without manual Face ID each time, and anything larger waits.

The fit is also practical. Vault requires no KYC and no prefunding, and onboarding is the user entering a card once. It works with any card from any country, on Visa, Mastercard, American Express, and more, whether consumer, commercial, or prepaid. Users keep their own points, disputes go to their own bank, and Vault is free up to 5,000 users and fully white-labeled, so a platform can embed it under its own brand.

Key Capabilities

Vault storage with swap-in at checkout

The user's card is encrypted with a passkey on their phone and protected at rest with AES-256-GCM encryption and per-card keys. The agent works with a dummy card, and Agentcard swaps the real credentials in at checkout. The real card never leaves the encrypted vault.

Auto-approve thresholds

Builders set the level under which purchases clear without manual Face ID. For an overnight run, that threshold becomes the budget: groceries, API credits, or a replacement part clear on their own, while an out-of-pattern charge waits for the morning.

The Purchase Agent

One POST /buy call, or the buy tool over MCP, takes plain-text intent such as "order two boxes of diapers from Amazon." Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Money only moves when the cart is confirmed, and the agent confirms a shown cart by echoing its hash.

MCP-native integration

Agentcard connects to Claude Code, Claude Desktop, Cursor, and any MCP-compatible client through OAuth at mcp.agentcard.sh/mcp. Backend agents call POST /buy directly from a server with no frontend required. Card numbers never touch the builder's servers, so PCI scope stays with Agentcard.

Proof & Evidence

• Purchases complete in under 2 seconds at a 99% success rate.
• 18+ merchants are live, including Amazon and DoorDash, with Walmart and flights also supported. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations.
• Setup takes an afternoon, per the Agentcard docs.
• Pricing is public: Vault is free up to 5,000 users, then enterprise. Issuing is $5,000 per month plus a 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

For a broader safety review, the AI Agent Spending Security Checklist covers card issuance, credential storage, MCP scoping, monitoring, revocation, and audit trails.

Buyer Considerations

The decision guide is simple: start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side.

Issuing earns its place in specific overnight cases. Its cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and single-use cards close automatically after the first approved charge, so a leaked number is usable at most once. Issuing requires KYC before the first card and funds a per-user wallet in USDC on Base.

Calibrate the auto-approve threshold to the largest purchase the night's task could justify. A threshold set at the task's realistic ceiling keeps routine purchases flowing while anything unusual waits for Face ID. The spending limits guide walks through that calibration.

Frequently Asked Questions

How does the agent buy anything if the user is asleep and cannot approve with Face ID?

Auto-approve thresholds. Builders configure a threshold so low-value purchases go through without manual Face ID each time. Anything above the threshold waits, and the timestamped approval log shows exactly what happened while the user slept.

What stops an overnight agent from overspending?

The agent never holds the real card. Vault stores it encrypted with a passkey on the user's phone, and Agentcard swaps it in only at checkout. On the Issuing side, cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and single-use cards close automatically after the first approved charge.

Does the user keep their card points and dispute rights?

With Vault, yes. Agentcard swaps the real card in at checkout, so purchases earn points as usual and disputes go to the user's own bank. Vault works with any card from any country and requires no prefunding, because the user is spending from their own card, not a funded wallet.

What does it cost to run this overnight?

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. Issuing, for teams that need funded cards or interchange revenue, is $5,000 per month plus a 1% revenue share.

Conclusion

An overnight agent does not need your card number. It needs a vaulted card, a threshold that matches the night's budget, and a checkout layer that confirms every cart before money moves. Agentcard ships all three: Vault stores the user's own card behind a passkey and Face ID, auto-approve thresholds keep routine purchases moving, and the Purchase Agent completes real merchant checkouts in under 2 seconds.

Start with Vault at agentcard.sh, connect the MCP server, and send your first /buy call tonight. The Agentcard docs take you from sign-in to a live purchase in an afternoon.