A shop segments your inventory and its PSPs. A tenant can have several.
Select a shop above, or add your first one, to configure its inventory, payments, and Visa.
Inventory · events & tiers
What buyers can purchase. Add by hand, or import a whole catalog from a linked Stripe account.
—
Add an event or tier by hand
Payment providers
The payment processors you connect. Charges settle to your own PSP account — funds stay with your provider.
—
How this routes: charges settle to your own PSP. If you link more than one, The payment service picks among your PSPs by card scheme + rate (your Primary first) — it never routes to a PSP you haven't connected, and never chooses the card issuer (that's your PSP's job).
Connect a payment provider
Primary = tried first among the PSPs you've connected (not a route to any other processor).
Sent once, stored behind an opaque ref, never logged or returned.
Visa · agentic checkout
Stage Visa Developer Platform credentials so agents can pay via Visa (VIC mandates + Trusted-Agent identity).
The label these Visa credentials are stored under (Visa's processor is cybersource). Use the same id here and when you Test — it identifies which processor handles this shop's Visa charges.
Sent once, stored behind opaque refs, never logged or returned.
Fee model
Who bears the processing fee, and the tax rate applied to this shop's charges.
Delete this shop — removes its events, tiers, and PSP links. Irreversible.
Agent demand
How agentic buying is doing at this shop: agents your buyers have authorized, and
how many are queued to buy — waiting for a drop to open or in line for a sold-out release.
Counts only; who is waiting stays the buyer's business.
Public discovery
Off by default. When on, this shop's window — events, tiers, prices, and live
availability — is published for AI agents to find: a public catalog endpoint, an
agent-readable product feed, and structured data on the buyer page. Never exposes stock
counts, payment providers, or buyer data.
Website embedding
Off by default. When enabled, your own website can open the agent-authorization
page in a modal instead of redirecting. Only enter websites you control — an allowed site can
display the page where your customers grant spending authority.
Buyer sign-up · agent authorization
This shop's own front door: buyers sign in with a magic link, bring or create an
agent, add a card (in the payment provider's iframe), and grant a mandate locked to this shop.
Share this link on your site or in a "tickets drop soon" email.
Test your integration
Checks the wiring an agent purchase depends on — your payment provider,
what's buyable, and whether your webhook endpoint accepts a real signed delivery.
No purchase is made: nothing is billed and no ticket stock is used.
API tokens
Integration credentials for your backend. Scopes only — no spend authority.
—
Team
Invite a teammate into your organization (WorkOS email invitation).
Agent registry (TAP)
Which of your shops' Visa credentials transports agent-key lookups, plus your
VMRS merchant id. Agents signing with a key enrolled here can check out via Trusted Agent
Protocol. All three fields are required to enable; clear all to disable.