Agents are the customer.
Not the humans who build them. Every design decision — from claim codes to the SSE stream to non-custodial payments — starts by asking "what does a program need that a dashboard user doesn't?".
Cards402 was started because there was no way for an LLM agent to buy something on the open internet without a human holding its hand. Not without pasting a card number into a chat. Not without a human approving every transaction. Not without giving up custody. We're fixing that — carefully, one primitive at a time.
The web assumed a human was always there, at the other end of a checkout form, tapping a 3-D Secure OTP out of an iPhone. AI agents broke that assumption a year ago. The industry responded with either “wrap it in a shared corporate card” or “let the agent ask the human”. Neither scales.
Cards402 is the middle answer. A stablecoin payment in, a real card out, and a non-custodial architecture so no single party — not us, not a custodian, not a compromised operator — can divert agent funds in flight. Boring, correct, and mostly invisible. That's the job.
Not the humans who build them. Every design decision — from claim codes to the SSE stream to non-custodial payments — starts by asking "what does a program need that a dashboard user doesn't?".
Cards402 does one job: turn a Stellar payment into a Visa card. We will not bolt on a rewards programme, a fiat on-ramp, or a chat widget. Depth over breadth, forever.
Every non-obvious decision ends up in a design doc, and every design doc eventually shows up on the docs site. If the only person who understands a subsystem is the person who wrote it, we failed.
Cards at face value. No dark patterns. No free-trial auto-renewal traps. No "we'll get back to you in 5–7 business days" when the real answer is next quarter. We tell you what happened and when.
First live orders fulfilled end-to-end. ~33s from payment confirmation to PAN delivery.
Agents now pay the receiver contract directly. Claude Desktop integration via the Cards402 MCP server.
Expand beyond the initial reward-card supplier so agents can pick the best card for each use case.
European IBAN accounts for agents that need a non-card rail. Transparent on-chain reporting of Cards402 treasury flow.