One request path, three server-side checks a purchase must clear, and money that never touches us. Here is exactly how it works.
Is this a known agent, in scope? Enforced with JWT, tenant scoping, and a know-your-agent allowlist.
Within the mandate cap and scope, is the seat actually free? Atomic, oversell-proof holds, plus a price lock.
Does the card authorize? Ambiguous outcomes halt the transaction; there is never a silent double-charge.
A prompt-injected agent still cannot exceed its cap, scope, or the locked price.
One atomic database operation claims inventory. Proven at 250 agents versus 100 seats: exactly 100 sold.
Integer-exact amounts, idempotent charges, an ambiguous PSP halt, and a durable append-only audit log.
Money moves merchant to the merchant's own PSP to the cardholder. Alyte moves only instructions and tokens, never funds, and invoices its fee separately from any transaction. This is an architecture choice, not a workaround, and it is why Alyte is never a money transmitter under this design.
Alyte issues and governs a scoped mandate-bound agent, or accepts a bring-your-own-agent over authenticated MCP. Built and demoable today.
A vaulted identity and payment instrument that travels across surfaces, authenticated with passkeys.
Structuring a merchant's catalogue and content so agents can find and transact with them.
| Player | What it is | Where Alyte differs |
|---|---|---|
| Visa Intelligent Commerce Connect | Network on-ramp, near-zero price to drive rail volume. | A merchant on ICC is inside Visa. Alyte is network-neutral and settles to the merchant's own PSP. |
| PSP compatibility layers (e.g. Nuvei) | First-party in-agent payments for that PSP's own merchants. | A merchant on one PSP is captured by it. Alyte is cross-PSP-neutral and unconflicted. |
| Soma / Vermilion | Clean horizontal PSP orchestration, never holds funds. | Complementary: it routes across PSPs, Alyte adds the agentic, mandate and identity layer on top. |