Skip to content

Custom API

Ticket delivery

Reference only. Not a decision unless cited in product/DECISIONS.md.

Ticket delivery

After a buyer pays, they need a ticket they can open without logging in. This page is the ELI5 for where they buy vs where they see the ticket, including the completely anonymous white-label headless path.

Who this is for

Venue engineers on headless or Web SDK paths who need to know what AXYN sends by email and what you must (or must not) build.

Anonymous guest (white-label default)

Headless checkout uses an anonymous buyer JWT (signInAnonymously). That is enough for the full purchase. Guests are not AXYN account holders.

MomentWhat happens
BuyAnonymous JWT + your UI; purchaser_email for delivery
Confirm (same tab)Optional: GET /v1/me/tickets with that JWT — show order success / open-pass CTA on your domain
See ticket (any device)Venue-branded hosted page via email bearer link — no login
Lost emailOrganizer resend + AXYN /me/sign-in?intent=recover — not an open email→tickets API

White-label today means: venue display name / brand on email + hosted ticket page (no AXYN QR center mark when powered_by_axyn_required=false or kind=aggregator). Mail and ticket domains stay on AXYN until a later custom-domain option ships.

Buy vs see (one screen)

BuySee ticket
DefaultYour site (headless API or SDK embed)AXYN-hosted page, venue-branded
URLYour domainhttps://axyn.events/tickets/{token} (or your env’s WEB_AXYN_BASE_URL)
You build?Checkout UI (or use SDK)Nothing for the default path
Login?Anonymous session onlyNone — bearer URL is the credential
Buyer pays on your site
        │
        ▼
AXYN mints a one-time ticket link
        │
        ▼
Email: From "{Your venue name}" <tickets@axyn…>
       Reply-To: your contact email
       Body: event name + "View ticket" → hosted page
        │
        ▼
Hosted page shows your name + event + QR (no AXYN mark if white-label)

Modes: hosted vs embed

ModeWhen to useWhat you do
hosted (default)Almost alwaysRely on AXYN email links. Do not build /tickets/[token].
embedYou want the ticket UI on your domainMount SDK TicketDisplay / BearerTicketScreen and deep-link there yourself

There is no required config flag today. Email always points at the hosted URL. Choose embed only if you deliberately replace that link in your own post-purchase UI.

Custom ticket domains (tickets.yourvenue.com) are not available yet — email and ticket links use AXYN domains with your venue branding.

What the email looks like (honest)

FieldValue
From display nameYour tenant display_name
From addressAXYN tickets domain (e.g. tickets@axyn…)
Reply-ToYour tenant contact email
Subject / bodyLead with the event title; receipt (ticket #, tier, amount)
CTAOpen Live Pass → hosted bearer link (no PDF, no admit QR)
FooterTicket delivery for {your name} via AXYN

Say to stakeholders: buyers see your brand; the mail domain is still AXYN until a later custom-domain project.

Do not say: “Email comes from @yourvenue.com” as an MVP promise.

Headless checklist

  1. Complete Get started through verify-payment with anonymous buyer JWT (never require AXYN login).
  2. Expect AXYN to enqueue ticket email with a hosted bearer link (no extra call from you for the default path).
  3. Optional same-session UI: GET /v1/me/tickets (buyer JWT) and/or a CTA that opens the hosted pass when you have the link from your confirmation flow — default recovery remains email.
  4. Do not invent a public “get raw bearer token later” API — the raw token is only available at mint for delivery.
  5. Do not build partner login, AXYN account walls, or public email→tickets lookup for the default guest path.

Web SDK checklist

  1. Mount checkout per Quickstart.
  2. After pay, confirmation can show TicketDisplay in-session.
  3. Email still sends the hosted link for guests / other devices.
  4. To keep ticket UI on your site long-term, mount BearerTicketScreen with the token from your own routing (embed mode) — otherwise leave buyers on the hosted page.

Live pass (do not promise a static admit barcode)

AXYN’s day-of ticket is a live pass: the code guests show at the door rotates on the hosted (or embed) ticket page. Design your post-pay UI around open your pass, not “save this barcode forever.”

What partners should assumeGuidance
See-ticket todayHosted page from email (+ optional same-session GET /v1/me/tickets)
Confirmation copyOrder success + open pass — not a forever screenshotable admit code
EmailReceipt details + Open Live Pass link; no PDF; no static door QR
Arm email (doors − 6h)Organizer-branded Your {event} entry code is live. Open it now. Same /p/{share_code} Live Pass as purchase email; no remint; no confirmation URL
Wallet / Add to WalletLast: saves the event in Wallet; show this page at the door — no static barcode that bypasses it
Extra deviceMay require email step-up (sid on the ticket URL) before mint
Send a passHolder can transfer; recipient claims and opens a new live pass

Ticket email must not embed a scannable admit code. Guests open the live pass from the link. Full contract: Live pass and Transfer.

Secret API keys do not serve tickets. Guest pass APIs use the ticket-url bearer (or buyer JWT for signed-in My Tickets). See Live pass.

White-label QR

On the hosted page, the AXYN center mark is omitted when your tenant has powered_by_axyn_required=false or kind=aggregator. Direct tenants that require powered-by keep the mark.

Dual email (keep both for now)

Buyers may get two emails after pay. That is intentional today.

EmailWhat it isWhat it is not
AXYN ticket emailVenue-named From, Reply-To venue, event subject, receipt fields, Open Live Pass link, paid tickets also get Upgrade this pass (?upgrade=1, no login wall; comps omit it), honesty footer (no PDF)Not the bank/card receipt
Stripe receiptPayment confirmation from Stripe / the connected account (receipt_email on the PaymentIntent)Not your ticket QR

Say to venues: “Buyers get your ticket email from us, and a separate Stripe payment receipt. We are not turning the Stripe receipt off yet.”

Do not disable receipt_email on the PaymentIntent. A single combined inbox may come later; until then, keep both.

Card statement text (merchant of record) comes from the venue’s Stripe Connect account descriptor, not from the email From line.

When the event requires a name for every ticket, an attendee with an email gets their own pass email with no amounts. The buyer's email always contains every pass of the order, so a mistyped email can be fixed by transferring the pass. See Attendee details.

PageRole
Choose a pathHosted vs embed vs headless
Live passRotating door code + step-up
TransferSend a pass / claim
UpgradePay the difference; same URL
Headless APIArchitecture
Get startedFirst API sale
Web SDKEmbed checkout

Next