How it works

The agent proposes. Alyte disposes.

One request path, three server-side checks a purchase must clear, and money that never touches us. Here is exactly how it works.

The three enforcement layers

Each layer owns one refusal, for one reason.

1
Authed, gateway

Is this a known agent, in scope? Enforced with JWT, tenant scoping, and a know-your-agent allowlist.

2
Merchant, reserve

Within the mandate cap and scope, is the seat actually free? Atomic, oversell-proof holds, plus a price lock.

3
PSP, confirm

Does the card authorize? Ambiguous outcomes halt the transaction; there is never a silent double-charge.

The purchase flow

Discover, quote, reserve, confirm, settle to the merchant.

discover quote reserve confirm settle to merchant
Alyte never holds funds at any step. The money moves merchant to the merchant's own PSP to the cardholder; Alyte moves only instructions and tokens, and invoices its fee separately.
Safe by construction

The rigor that makes the claims true.

Mandate enforced server side

A prompt-injected agent still cannot exceed its cap, scope, or the locked price.

Oversell impossible

One atomic database operation claims inventory. Proven at 250 agents versus 100 seats: exactly 100 sold.

Money handled with paranoia

Integer-exact amounts, idempotent charges, an ambiguous PSP halt, and a durable append-only audit log.

Unlicensed by design

We orchestrate. Your PSP settles.

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.

The three faces

Deep dive: how each face works.

A. Agent issuance & BYOA

Alyte issues and governs a scoped mandate-bound agent, or accepts a bring-your-own-agent over authenticated MCP. Built and demoable today.

B. Persona, passkeys, Click to Payroadmap

A vaulted identity and payment instrument that travels across surfaces, authenticated with passkeys.

C. Merchant readiness, AI-ready catalogsroadmap

Structuring a merchant's catalogue and content so agents can find and transact with them.

Neutral vs captured

Every on-ramp today is captured. Alyte is not.

PlayerWhat it isWhere Alyte differs
Visa Intelligent Commerce ConnectNetwork 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 / VermilionClean horizontal PSP orchestration, never holds funds.Complementary: it routes across PSPs, Alyte adds the agentic, mandate and identity layer on top.

See the gauntlet run against a real on-sale.

Book a demo See it live →