For merchants

Close the sales your fans abandon, and survive the on-sale.

High-intent fans click and never check out. On-sales risk overselling. Agents get blocked as bots. Alyte closes the purchase safely, inside the agent, and makes oversell impossible.

The pains, named

Four problems, one layer.

Abandoned high-intent demand

About 70% of carts are abandoned (Baymard Institute). In ticketing, high-intent fans drop before checkout, and the agent nudges while Alyte owns the close.

On-sale oversell

Thousands of agents hit finite inventory at once. Oversell is pinned at 0 by construction, proven at 250 reservers versus 100 seats: exactly 100.

Agent-blocking

In a bot-hostile world, a known, scoped agent is exactly what gets safely let in.

Invisibility

Be on the agent's shortlist with AI-ready catalogs, not absent when it decides.

roadmap
What you keep

Your PSP. Your funds. Your checkout.

Alyte settles to your own account and never holds money. Your success-fee is invoiced, never taken from funds in transit. You only pay when a ticket is actually issued.

How you go live

Set yourself up in the console. No engineering lift.

Everything below is self-service in your merchant console today. It is an admin surface you operate, not a system to integrate against. available now

1
Connect your own PSP real

Register your PSP rails (Stripe today, Adyen and local acquirers on the way) and enter each account's credentials once. Alyte stores only an opaque credential reference, never the secret itself, and resolves it to a live key only at charge time. Every charge settles merchant to your own PSP account, exactly as your checkout does today; Alyte is never a payee and never on the money line.

You can link more than one PSP and set how they're ordered, cheapest processing fee first, for example, so routing follows your economics.

console → link PSP → store credential_ref (never the secret) → resolve at charge
2
Build your catalog real

Create your merchant, events and ticket tiers; set price, tax, and availability per tier. This is the live, mutable inventory the agent shops against, and it's what makes oversell impossible: a reservation is one atomic database step (decrement where available ≥ qty), so two agents can't both take the last seat. Update price or availability any time; quotes price-lock against it.

merchant → events → tiers · price · tax · availableCount
3
Set your fee and tax model real

Choose who bears the PSP processing fee, buyer or merchant, and your tax rate. It drives how Alyte routes to your PSPs.

4
Invite your team and manage keys real

Bring teammates into your org and mint or revoke API keys. Sandbox is self-serve; live keys unlock after go-live.

Straight about onboarding: Going live is a guided design-partner path, not a self-serve sign-up. We provision your tenant and flip you to live rails. A server-to-server inventory-sync API, for merchants who run their own ticketing system, outbound webhooks, and AI-ready catalogs are on the roadmap, not available today. We label what is real versus roadmap rather than blur it.

Pricing

A SaaS base you can commit to, plus a small share of what you win.

A monthly SaaS base, your committed, predictable line, plus a small percentage of successful transactions as upside, invoiced separately and never taken from funds in transit. You only pay the success fee when a ticket is actually issued. We only win when you do.

Committed, SaaS base

A predictable monthly subscription. This is the derisked line you can plan against.

Upside, success fee

A small percentage of successful GMV, invoiced. We only win when you do.

See a mandated agent buy a real ticket.

Watch an agent shop and buy under a scoped mandate it cannot exceed, and get refused when it overreaches, with oversold pinned at 0.

Book a demo See it live →