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.
| Moment | What happens |
|---|---|
| Buy | Anonymous 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 email | Organizer 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)
| Buy | See ticket | |
|---|---|---|
| Default | Your site (headless API or SDK embed) | AXYN-hosted page, venue-branded |
| URL | Your domain | https://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 only | None — 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
| Mode | When to use | What you do |
|---|---|---|
hosted (default) | Almost always | Rely on AXYN email links. Do not build /tickets/[token]. |
embed | You want the ticket UI on your domain | Mount 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)
| Field | Value |
|---|---|
| From display name | Your tenant display_name |
| From address | AXYN tickets domain (e.g. tickets@axyn…) |
| Reply-To | Your tenant contact email |
| Subject / body | Lead with the event title; receipt (ticket #, tier, amount) |
| CTA | Open Live Pass → hosted bearer link (no PDF, no admit QR) |
| Footer | Ticket 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
- Complete Get started through verify-payment with anonymous buyer JWT (never require AXYN login).
- Expect AXYN to enqueue ticket email with a hosted bearer link (no extra call from you for the default path).
- 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. - Do not invent a public “get raw bearer token later” API — the raw token is only available at mint for delivery.
- Do not build partner login, AXYN account walls, or public email→tickets lookup for the default guest path.
Web SDK checklist
- Mount checkout per Quickstart.
- After pay, confirmation can show
TicketDisplayin-session. - Email still sends the hosted link for guests / other devices.
- To keep ticket UI on your site long-term, mount
BearerTicketScreenwith 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 assume | Guidance |
|---|---|
| See-ticket today | Hosted page from email (+ optional same-session GET /v1/me/tickets) |
| Confirmation copy | Order success + open pass — not a forever screenshotable admit code |
| Receipt 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 Wallet | Last: saves the event in Wallet; show this page at the door — no static barcode that bypasses it |
| Extra device | May require email step-up (sid on the ticket URL) before mint |
| Send a pass | Holder 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.
| What it is | What it is not | |
|---|---|---|
| AXYN ticket email | Venue-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 receipt | Payment 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.
Related
| Page | Role |
|---|---|
| Choose a path | Hosted vs embed vs headless |
| Live pass | Rotating door code + step-up |
| Transfer | Send a pass / claim |
| Upgrade | Pay the difference; same URL |
| Headless API | Architecture |
| Get started | First API sale |
| Web SDK | Embed checkout |