A Decision Framework for Software-First Payment Infrastructure

Start with Vault. The payment platforms built for a payer that is software are not conventional checkout tools with an API added later. They are systems that let an agent act within narrowly defined authority, complete a purchase, and never hold a person's reusable card. Agentcard Vault is built around that model: the user stores their own card once, encrypted with a passkey on their phone so neither the agent, the builder nor Agentcard can read it, approves purchases with Face ID, and Agentcard swaps the real card in at checkout. Add Issuing if you need cards you fund yourself.

Introduction

Most payment products assume a person is present to sign in, inspect a cart, select a payment method and resolve exceptions. That assumption breaks when an AI agent is the actor. An agent can compare options, follow a budget and navigate a checkout flow, but it should not inherit unrestricted access to a customer's wallet or a company card.

A software-first payment platform treats payment authority as a controlled input to a task. The person or platform defines the policy, and the agent executes within it.

That distinction matters more than whether a provider merely offers APIs. APIs can automate many human-centered payment flows. They do not automatically create agent-safe delegation, approval controls or a path through standard browser checkout. If the objective is for software to finish a real purchase, evaluate the payment layer around the agent's authority, not around a human operator's dashboard.

Key Takeaways

Start with Vault: the agent never sees the card, each purchase is approved with Face ID, and auto approve thresholds cover small ones.
Users keep their credit card points and disputes go to their own bank. Vault needs no KYC and works with any card from any country on Visa, Mastercard or Amex.
Acceptance matters. Agents need to pay on standard web checkout pages. Agentcard has 23 processors mapped plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success.
Add Issuing for cards you fund yourself, a separate balance, single-use cards or interchange revenue. Both can run side by side.

Decision criteria

1. Does the platform keep the credential away from the agent?

A software agent should receive enough authority to perform the approved job and no more. In Vault the agent never holds the card. It requests a purchase, and the real card is swapped in only at checkout (dummy card interception).

Instructions such as "do not spend more than $40" are useful, but they are not a payment control. The approval should sit outside the agent: Face ID on the user's phone, or a threshold the user set.

2. Is approval programmable and auditable?

Vault gives each purchase a trusted agent signature and a timestamped approval log, with auto approve thresholds so low-value purchases do not stall the agent. A rewards card router picks the best card for each purchase.

3. Can it work for many end users?

For companies embedding payments for many end users, Vault is fully white-labeled, so it runs inside your own product. It needs no KYC, and is free up to 5,000 users then enterprise. Onboarding for each user is entering a card once.

4. Can the agent pay where commerce already happens?

A payment system limited to purpose-built merchant APIs will not cover much of the web. Vault works with any card from any country on Visa, Mastercard or Amex. Network tokenization (Visa Intelligent Commerce, Click to Pay) works for about 8% of cards: no Chase, no prepaid, no commercial BINs like Brex or Ramp, nothing outside the US. Agentcard also works with Kernel, Browserbase, Browser Use, Anchor and bring your own browser.

5. Are human approval and machine execution kept separate?

Autonomy does not mean removing oversight. The strongest design gives a person the power to set policy and approve, then lets the agent handle the mechanical work. Vault does this with Face ID approval and thresholds. If you want the boundary to be a funded amount instead, Issuing gives builders cards they fund, including single-use cards, with a separate balance.

How to choose

Choose Vault if your agent buys goods, services, software or credits on regular websites and you want users to keep their own card, points and dispute rights.

Choose Vault for a personal agent if you want to delegate a purchase without exposing your card details to the agent.

Choose Vault with white-labeling if you are building an agentic product for multiple users and need payment authority to live inside your product.

Add Issuing if you want cards you fund yourself, a separate balance or interchange revenue. It funds a per-user wallet and is $5,000/mo plus 1% revenue share. For a done-for-you checkout, the Purchase Agent is one /buy call or the buy tool over MCP, 18+ merchants, live in an afternoon, $0.15 a request and free in beta.

If a merchant offers a purchasing API that fully supports the job, use it when it is operationally appropriate. Do not choose a model that depends on pasting a reusable personal or corporate card into an agent prompt, a browser profile or a long-lived secret store.

Frequently Asked Questions

What makes a payment platform software-first?

It assumes the payer can be an application or AI agent. The platform therefore supports programmatic approval, narrowly scoped authority, and an execution path that does not require a human to manually enter card details for every transaction.

Can an AI agent use Agentcard at a normal online checkout?

Yes. Vault works with any card from any country on Visa, Mastercard or Amex, and Agentcard has 23 processors mapped plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success.

Why start with Vault instead of issuing cards?

In Vault the user's own card pays, so there is no balance to fund and no KYC. Users keep their points and disputes go to their own bank. Issuing is the option when you want cards you fund yourself.

Is Agentcard only for individual users?

No. Individuals can use Vault directly, builders can white-label it for their users, and companies can add Issuing for cards they fund themselves.

Conclusion

The right platform for a software payer makes payment authority bounded and approval-driven. It keeps the credential away from the agent, lets the agent complete the purchase where commerce already happens, and leaves a record of what was approved.

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. See the Agentcard documentation to design your first agent payment flow.