Workspace
Settings
Everything you manage for this organization.
Organization
- General
Workspace identity, business address, and public URL.
- Branding
Logo, colors, page header, and social links on your public pages.
- Venues
Reusable locations and timing defaults for future events.
- Team
Invite teammates and manage their roles.
- Developers
Publishable keys for embedding your events on your own website.
Money
- Payouts
Money landing in your Stripe account.
- Disputes
Respond to chargebacks and track outcomes.
- Reconciliation
- Fees
How the attendee fee is presented to buyers.
- Settlement statement
One month of your Stripe balance, in Stripe’s terms.
Notifications
- Email Delivery
Monitor buyer email sends and failures.
- Email Templates
Customize transactional email content.
- Email Settings
Sender identity and delivery preferences.
Organization
General
Manage your workspace identity, business address, and public URL.
Business address
The organization's primary business address. Event venues and your email footer address stay separate.
Branded subdomain
Serve your public events page and checkout from your own subdomain.
3–63 characters; letters, numbers, and hyphens. Leave blank to remove.
Organization
Branding
Your logo, colors, and public page header. Events without their own appearance settings inherit your logo and colors automatically.
Logos
Shown on your public page and, unless an event sets its own logo, on event pages too.
Used on light backgrounds — the page top bar and headers without a photo. A transparent PNG works best.
A white or light version, used over your header photo and dark event heroes. Without one the primary logo is used with a shadow.
Colors
Your brand's primary and accent colors drive buttons, links, and highlights on public pages. Leave unset for the attendee default.
About
A short bio and a support contact, shown in the header of your public events page.
Shown as a “Contact support” button so buyers can reach you directly.
Page header
The banner across the top of your public events page — like an event page's hero, but for your whole catalog.
A wide image behind your name. Optional — without one the header stays clean text.
Darkens the photo so your name stays legible.
Titles on your public events page. Event pages choose their own font.
Social links
Shown on your public events page when set. Full https:// links.
Finance
Fees
Choose how the attendee fee is presented to your buyers. Override it per event when needed.
Your attendee fee
Set by the attendee team.
Default fee handling
Applies to every event unless an event overrides it.
Buyers pay the ticket price; the attendee fee comes out of your net sales.
Buyers pay the ticket price plus the attendee fee. You keep the full face value before Stripe’s processing fee.
Organization
Developers
Publishable keys for pulling your events into your own website — a calendar, a listing page, anything that links back to your ticketing pages.
Publishable keys
Safe to embed in your website's code — they can only read events that are already public. Revoking takes effect immediately.
Embed your events
A minimal example — fetch the feed and render each event with a link to its ticketing page. Events appear within a minute of publishing.
Replace any earlier copies with this corrected snippet. Event feeds require support activation after existing embeds have been checked.
<div id="events"></div>
<script>
fetch("https://your-site.example/v1/events?key=att_pub_YOUR_KEY")
.then((r) => {
if (!r.ok) throw new Error('Event feed unavailable');
return r.json();
})
.then(({ data }) => {
const container = document.getElementById('events');
const events = document.createDocumentFragment();
for (const ev of data) {
const row = document.createElement('p');
let name = document.createElement('span');
try {
const url = new URL(ev.ticketingUrl);
if (['https:', 'http:'].includes(url.protocol) && !url.username && !url.password) {
name = document.createElement('a');
name.href = url.href;
}
} catch { /* Invalid ticket links render as plain text. */ }
name.textContent = ev.name;
row.append(name, document.createTextNode(' · ' +
new Date(ev.startDate).toLocaleDateString(undefined, { timeZone: ev.timezone })));
events.append(row);
}
container.replaceChildren(events);
})
.catch(() => {
document.getElementById('events').textContent = 'Events are temporarily unavailable.';
});
</script>GET https://your-site.example/v1/events returns upcoming public events by default; add time=past or time=all for more. Dates are ISO instants — render them in each event’s timezone field. Each event includes imageUrl: its listing image, or its hero image when it has none. Add image=hero to get the wide hero image instead, which suits a carousel.
Notifications
Email Settings
The sender identity and legal footer applied to every email your buyers receive. Leave a field blank to use the attendee default. Edit the wording of individual emails under Email Templates.
Sender
The name buyers see in their inbox. The sending address stays your verified attendee domain.
Where replies go. Defaults to your support address.
Footer
Shown in the footer of every email (CAN-SPAM compliance).
Your account
Text alerts
Texts from attendee alerts when your automations reach a Text me step.
Team
Invite teammatesWhat each role can do
“Their events” means the events picked under Event access, or every event if access is set to all. Before removing someone or moving them to manager or staff, have them hand over any business reports they own from Reports. Private reports aren’t reassigned.
Venues
The places you run events, and the seat maps for each one.
Where is it?
Name the place and where it is. Buyers see both on the event page.
Timezone is set from the address
Timezone is set from the address
Change it when an address you typed yourself did not set it.
Keep this about the venue. A future event can replace or clear it.
Changes apply to new events. Existing events keep their copy.
Save changesEdit this seat map on a computer or a wider screen.
Super admin
Organizations
Every organization on the platform. Create one, then invite its first owner.
| Organization | Payouts | Members | Created |
|---|---|---|---|
Super admin
Revenue
Verified live revenue per organization, net of refunds, plus reconciliation status.
| Organization | Orders | Buyer fees | Refunded | Revenue (net) |
|---|---|---|---|---|
Super admin
Super admins
Platform administrators with access to every organization. Org-level members are managed on each workspace’s Team page.
| User | Platform role | Status | Joined | |
|---|---|---|---|---|
Super admin
Scanners
Fleet scanning devices, named by inventory sticker. Claim a phone once and it keeps its name at every event, in every organization.
| Hardware | Claim code | Status | Claimed | Added | |
|---|---|---|---|---|---|
Super admin
Card readers
The rentable Stripe Reader M2 fleet. Register a reader by its serial, then rent it to a client organization — a reader works in the POS app only while an active rental holds it.
| Reader | Condition | Held by | Registered | |
|---|---|---|---|---|
Super admin
Data imports
Bring an organizer’s history over from their old ticketing platform — events, orders, customers and the seats they hold.
| Organization | Status | Rows | Started | By |
|---|---|---|---|---|
Super admin
Mapping presets
A saved column mapping for one platform’s export. Presets are shared across every organization — save one from a file’s mapping editor.
| Preset | File shape | Fields | Updated | |
|---|---|---|---|---|
Identity
The workspace name and its URL slug.
Danger zone
Remove this organization from the platform — reversibly, or for good.
Soft-delete. Hides the organization and its events across the platform. All data is retained and it can be restored.
Soft-delete organizationDelete permanently. Erases the organization and all its data — events, orders, comps, team, everything — and deletes any member whose only workspace this was. This cannot be undone.
Delete permanently…Platform fee
What we charge this organization per ticket sold — percent of face + a flat amount, with optional caps.
Paid test rehearsal
Allow paid publishing and checkout with sandbox payments on a live deployment. Each permission change is recorded in the audit history.
Test orders issue valid tickets, emails, and automations. They are excluded from verified live financial reports. Turning this off blocks new paid test checkout and payment retries. Free tickets and completed purchases stay valid.
Text alerts
The most alert texts this organization's members can receive in one UTC day, all members together. 0 turns alert texts off. Each change is recorded in the audit history.
Archive test orders
Paste up to 100 order IDs from this organization. Tickets become invalid. Payment records and audit history are retained. Live orders and orders with unverified payment mode are refused.
Reserved seating
Gives this organization its own seats.io workspace and lets its events sell reserved seats.
- Files
- Mapping
- Dry run
- Import
Super admin
New import
One batch per organization at a time. Nothing is written until the dry run has run and you have confirmed it.
Source
Names this batch everywhere it appears, and is what an organizer sees on a migrated order. Something like “Eventbrite export, March 2026”.
Optional. Only super admins see it.
What a timestamp with no offset means in this file. A file that names its own zone per row wins over this.
What this batch may write
Currency is USD for every import.
Places events happen. Matched on name and address.
One event per name and local start date.
The tiers an event sold, with their face prices.
Buyers, matched on email. An existing attendee customer is adopted, never edited.
What was bought, for how much, and when.
Individual seats, with their barcodes carried over.
Marketing opt-ins. Never inferred — only an explicit opt-in in the file counts.
Notifications
Email Templates
Customize the subject and body of every email your buyers receive. Required content like QR tickets and order totals is always included automatically. Sender identity and the footer live under Email Settings.
Sent automatically when an order is paid — itemized totals.
Delivers the buyer’s QR tickets right after purchase.
Sent when a refund is issued to a buyer.
Tells a buyer their payment didn’t go through.
Pre-event reminder that re-sends tickets (7d / 24h / day-of).
Notifies ticketholders that an event was cancelled.
Notifies ticketholders of a date or venue change.
Sent once when someone registers for a registration event. Carries their pass and the event details.
Sent when someone requests a spot on an event that requires approval.
Sent with the tickets when a request is approved.
Sent when a request is declined, with the organizer's note if there is one.
Sent when someone joins the waitlist for a full registration type.
Offers a freed spot to the next person in line, with the claim link and deadline.
Sent when an offered spot was not claimed in time.
Sent when a request for a paid type is approved, with the pay link, the amount and the deadline.
Sent halfway through the payment window if an approved request or a paid waitlist offer has not been paid.
Sent when an approved registrant did not pay in time and the spot was released.
Notifications
Email templateOrder receiptTicketsRefund confirmationPayment failedEvent reminderEvent cancelledEvent updatedRegistration confirmedRequest receivedRegistration approvedRequest declinedWaitlist joinedWaitlist offerWaitlist offer expiredApproved, payment duePayment reminderSpot released
Sent automatically when an order is paid — itemized totals.Delivers the buyer’s QR tickets right after purchase.Sent when a refund is issued to a buyer.Tells a buyer their payment didn’t go through.Pre-event reminder that re-sends tickets (7d / 24h / day-of).Notifies ticketholders that an event was cancelled.Notifies ticketholders of a date or venue change.Sent once when someone registers for a registration event. Carries their pass and the event details.Sent when someone requests a spot on an event that requires approval.Sent with the tickets when a request is approved.Sent when a request is declined, with the organizer's note if there is one.Sent when someone joins the waitlist for a full registration type.Offers a freed spot to the next person in line, with the claim link and deadline.Sent when an offered spot was not claimed in time.Sent when a request for a paid type is approved, with the pay link, the amount and the deadline.Sent halfway through the payment window if an approved request or a paid waitlist offer has not been paid.Sent when an approved registrant did not pay in time and the spot was released.
Notifications
Email Delivery
Every email this workspace sends and what happened to it. Hard bounces and spam complaints are recorded and that address is automatically suppressed so we stop mailing it.
| Recipient | Status | Order | Detail | When | |
|---|---|---|---|---|---|
Suppressed addresses
Addresses we stopped mailing after a hard bounce or a spam complaint. Nothing further is sent to them.
Where sales came from
Orders placed within 7 days of a visit through a tracking link or attendee email. The last link clicked gets the credit.
Running now
Sends on the calendar, automations that are live, and codes buyers can use today.
Top tracking links
Ranked by gross sales over the last 7 days.Ranked by gross sales over the last 30 days.Ranked by gross sales over the last 90 days.
Traffic
Orders
Gross sales
Before fees and refunds
Conversion
Orders per visit to an event page
Delivered
emails · last 30 days
Opened
—
Not tracked yet
Clicked
clicked a link
Gross sales
orders within 7 days
Running
Entered · 30 days
Everyone who started a flow
Reached the goal
Gross sales
Open an automation for sales
Your automations
Emails that send themselves when someone does something. Numbers cover the last 30 days.
Start from a recipe
Proven flows with the copy written. Change anything before you turn it on.
Orders with a code
All time, across every code
Gross sales with a code
Gross sales, before the discount
Discount given
% of those tickets’ face value
Live codes
finished
Presale orders
All time, across every code
Gross sales with a presale code
Bought before general sale
Average order
Gross sales per order
Live codes
finished
Finance
Payouts
Connect a Stripe account to receive ticket revenue. Buyers pay your Stripe account directly; we collect the attendee fee.
Stripe Connect
Onboard with Stripe to accept payments and receive payouts.
Powered by Stripe Connect — onboarding, payments, and payouts are handled securely by Stripe.
Settlement statement
Monthly settlement statementPayouts Stripe has sent to your bank. Open an automatic payout to see the sales, refunds and fees Stripe put in it.
Withdrawn by Stripe for open disputes on your attendee sales, dispute fees included. The amount comes back if you win; the received fee does not.
| Amount | Status | Arrival | Initiated |
|---|---|---|---|
Payout
Payout
What’s in this payout
| Type | Reference | Date | Net |
|---|---|---|---|
Finance
Settlement statement
One month of your Stripe balance, in Stripe’s terms, so it ties to your bank statement.
The QuickBooks journal posts one balanced entry per currency against a Stripe balance account. Account names are placeholders; map them to your own chart of accounts when you import. Ticket sales is gross: it includes sales tax and buyer-paid fees.
Finance
Reconciliation
Discrepancies the reconciler found between your books and Stripe. Resolve one to acknowledge it — the reconciler re-opens it if the discrepancy persists.
| Kind | Reference | Expected | Actual | Flagged | Status | |
|---|---|---|---|---|---|---|
Check Stripe now
Evidence
Money
Owner
Payment
Signals on this order
If you refund
Activity
Tickets and admission
Customer emails
Purchase record
Prevent disputes
Payment
Signals on this order
If you refund
Activity
Tickets and admission
Customer emails
Purchase record
Prevent disputes
Payment
Signals on this order
If you refund
Activity
Tickets and admission
Customer emails
Purchase record
Prevent disputes
What happened
Who responds
Ticket impact
Money
The amount the cardholder disputed, in the payment’s currency. It is a claim, not money moved.
Figures come from the balance transactions Stripe recorded for this dispute on your Stripe account, in the currency Stripe settled them in. Other Stripe fees, such as a fee for countering the dispute or a Smart Disputes fee, are included only if Stripe reports them on this case. All amounts are USD.
Balance transactions
Owner
Stripe
Response
Evidence
Money
The amount the cardholder disputed, in the payment’s currency. It is a claim, not money moved.
Figures come from the balance transactions Stripe recorded for this dispute on your Stripe account, in the currency Stripe settled them in. Other Stripe fees, such as a fee for countering the dispute or a Smart Disputes fee, are included only if Stripe reports them on this case. All amounts are USD.
Balance transactions
Owner
Stripe
Purchase record snapshot
Customer
Tickets & admission
Organizer notifications
Money
The amount the cardholder disputed, in the payment’s currency. It is a claim, not money moved.
Figures come from the balance transactions Stripe recorded for this dispute on your Stripe account, in the currency Stripe settled them in. Other Stripe fees, such as a fee for countering the dispute or a Smart Disputes fee, are included only if Stripe reports them on this case. All amounts are USD.
Balance transactions
Owner
Stripe
Outcome by stage
Timeline
Assignment history
Money
The amount the cardholder disputed, in the payment’s currency. It is a claim, not money moved.
Figures come from the balance transactions Stripe recorded for this dispute on your Stripe account, in the currency Stripe settled them in. Other Stripe fees, such as a fee for countering the dispute or a Smart Disputes fee, are included only if Stripe reports them on this case. All amounts are USD.
Balance transactions
Owner
Stripe
Dispute settings
Contacts
Owners and admins who receive notices for cases nobody owns, and escalations when nobody acknowledges a case. Notices never include evidence.
Default owner
New cases are assigned here. If nobody acknowledges a case by 24 hours before its response deadline, the other contacts are notified.
Reminders
- New case opened
To the case’s owner, or to every contact when nobody owns it.
- 3 days before the deadline
To the same people, 72 hours before, while the case still needs a response. Held back when Stripe is set to respond.
- 1 day before the deadline
To the same people, 24 hours before, while the case still needs a response.
Who will be notified
With these settings.
- When a case opens
- If nobody acknowledges
- Platform alerts
Auto-respond
Cases opened
still open
Cases won
Prevented
closed as prevented by Stripe
Money not read
Stripe’s balance transactions not yet read for these cases
Unverified
not matched to their Stripe account · matched
Net balance so far
Median time to respond
from opened to submitted
Deadlines met
responses sent before due
Where cases ended up
- Needs response
- With the bank
- Won
- Lost
- Prevented
- Inquiry closed
- Missed deadline
Open cases as the Cases queue groups them, closed cases by the status Stripe reports. Amounts are what was disputed: claims, not money moved.
Prevented is Stripe’s own status for a dispute resolved before it became a chargeback; Inquiry closed means the inquiry closed without becoming a chargeback. Missed deadline: a case still open whose response deadline passed with nothing submitted.
Response time by source
| Source | Stages | Median |
|---|---|---|
Each time is the median from a stage opening to its response. Exact where attendee saw the submission happen. “≤” marks an upper bound.
Smart Disputes
- Eligible · Stripe responded
- Eligible · you responded with Stripe’s packet
- Eligible · you responded with your own
- Not eligible
- Unknown
Eligibility is from the check attendee made while each stage was open; unknown means it was not checked then, or the check could not tell. Checked on , eligible. “With your own” is your own response, sent in attendee or outside it.
Deadlines and evidence
Money
Figures come from the balance transactions Stripe recorded for these disputes on your Stripe account. The amount the cardholder disputed, in the payment’s currency. It is a claim, not money moved. “Other Stripe adjustments” are entries that are neither a withdrawal nor a return, their own fees included. All amounts are USD. A figure in words means attendee has no amount for it; it never stands for zero.
Open in reports: Dispute cash · Disputes and evidence
Cases are counted by when they opened: Stripe’s creation time when attendee has it, otherwise when attendee recorded the case. In this view, by Stripe’s creation time and by when attendee recorded them. These are measurements of what happened to your cases. Nothing here is compared with a target, and a small number of cases is not a trend.
Orders
Every purchase, comp and box-office sale, across all your events.
| Order | Buyer | Event and tickets | Status | |||
|---|---|---|---|---|---|---|
Customers
… people who’ve bought tickets, been comped, or registered.
| Customer | Since | |||||
|---|---|---|---|---|---|---|
Tickets ·
| Ticket | Holder | Price | |
|---|---|---|---|
Money
Net sales · Attendee fee kept · Refunded
Activity
Marketing email
Events and orders
What should we work on?
Events
Create eventEvents
Create eventEvents
Create eventEvents
Create eventOctober 2026
TodayQuestions
6 of 25 · 412 orders answered · edits apply to new orders only
Registrations
Everyone who registered, with their answers.
Settlement
What the event has earned once discounts, refunds and the attendee fee come out.
Fees and tax
Changes apply to new orders.
How buying a ticket works on your public page.
What buyers agree to at checkout.
Buyers accept this before paying. Every save is a new version, so each order keeps the exact text its buyer saw.
Who can find the event page.
How tickets get scanned on the night.
Issue free tickets in bulk from a pasted guest list. Comps use inventory and issue real scannable tickets, kept out of your revenue figures and reported here.
Comp drops
| Drop | Status | Issued | Face value | |
|---|---|---|---|---|
What kind of event is this?
Pick how people get in. It decides what the next steps ask for.
Name it and pick a venue
The venue sets the address, timezone and whether seats are reserved.
When is it?
The date and show time are required. Doors and on-sale times are optional.
What are you selling?
Add each ticket type. You can add tiers and presale codes from the event page later.
How should the page look?
A photo and two colors. All optional. Skip this if you’d rather do it later.
Set up the public page
Choose the link, who can find the page, and what it says.
Review and publish
Check the details. Each row links back to the step where it’s set.
Finance
Reports
Choose a template, open a saved report, or create your own.
Create a report
Per-ticket sales, check-ins, and the events behind every stub.
Search and filter templatesBlank report
Start from an empty tickets canvas.
Saved reports
New report
TicketsDraftNo unsaved changes.
Customize report
Choose columns to start your report.
Add columnsNothing to print yet
Start from a ready-made template, or build your own — pick columns, filter, and group; it prints here live.
Customize report
Event
Credentialing
Credentialing
Order Detail
Scanning for
Station settings
Station
Stations are identified by login — every sale, scan, and credential is attributed to this account. Hardware pairing below follows it.
Devices on this station
Local devices
Desktop stations: run attendee-bridge on this machine to drive USB RFID encoders. iPads can’t encode (no USB) — they sell, scan, and print over the network.
Card reader (Stripe Terminal)
On the reader: Settings → Generate pairing code.
Receipts & sound
Print on every completed sale
Prompt to add a customer at checkout
Play a confirmation tone on a completed sale
Welcome back to attendee.
Sign in to manage your events, tickets, and payouts.
No float · Your Stripe · Double-entry ledger
Join your organization
Setting up your account to join the team.
Administer attendee
Setting up your account as a platform super admin.
Set a new password
Choose a new password for your account.
Unsubscribe from reminders?
Stop sending event reminders and update notices to your email address. You’ll still receive tickets, receipts, and other transactional emails.
This link isn’t active
The tracking link you followed has been turned off by its organizer. If you were headed to an event, try searching for it or check with whoever shared the link.