Event ticket payments
Sell tickets and collect registrations without the form and spreadsheet mess
Flint gives you a hosted event payment page with ticket tiers, capacity limits, attendee fields, confirmation flow, and clean order tracking. It is the fast path for teams that need event payments to work without adopting a bloated ticketing platform.
The workflow problem
Event payment collection breaks down when the payment flow lives in too many places
Most teams do not need reserved seating, arena operations, or a giant event suite. They need a clean way to publish a page, collect payments, enforce limits, and stop cleaning up the resulting mess by hand.
The old way
With Flint
How it works
A simple event payment flow, end to end
This is the part most teams actually need: a hosted page that publishes quickly, captures the right details, and keeps sales and cleanup from turning into a side job.
Create the event payment link
Set the event date, time, location, total capacity, ticket prefix, and any attendee fields you need to collect.
Add ticket tiers or registration options
Create line items for General Admission, VIP, team entry, sponsor table, workshop seat, or any other tier with its own pricing and limits.
Share one link everywhere
Post it in email, text, social, or your site. Buyers select quantities, fill in attendee details, and move through hosted checkout from any device.
Let the event run without manual cleanup
Flint tracks sales, stops oversells, sends ticket confirmation, surfaces sold counts, and keeps refunds tied back to the original order history.
What you get
The event payment features that matter most
Flint already supports the core event-payment primitives that stop organizers from patching together forms, emails, and payment buttons around every event.
Ticket tiers and registration options
Sell general admission, VIP, team entry, sponsor tables, or class seats from one hosted flow instead of separate forms and buttons.
Capacity limits that actually close sales
Set a total cap so the page shows sold out when you hit the limit. No manual cutoff and no overselling because someone forgot to update the form.
Attendee fields at checkout
Collect meal choice, team name, player division, accessibility notes, or any other event-specific details directly with the payment.
Event date and location on the page
Show buyers exactly what they are registering for before they pay. Event details stay attached to the hosted page and confirmation flow.
Confirmation emails and ticket delivery
After payment, buyers can receive ticket confirmation and see ticket details without you stitching together an extra email workflow.
Refunds without spreadsheet reconciliation
Issue full or partial refunds and keep the order, payment, and refund history connected instead of patching together records after the fact.
Ticket numbering with prefixes
Use a ticket prefix for cleaner confirmations and event operations when you want a visible ticket code attached to each purchase.
Hosted flow instead of custom buildout
You get a mobile-friendly checkout page immediately, which is the right default for organizers who need to launch fast and keep the workflow clean.
Common workflows
Built for real event payment scenarios
The same hosted event flow can support ticket sales, registrations, and paid attendance across multiple verticals already represented on the site.
Fundraiser galas and dinners
Sell seats, tables, and sponsorship tiers while collecting attendee names and meal details in one payment flow.
Tournaments and team registrations
Charge for team entry, divisions, or side events without juggling forms, Venmo, and a separate roster spreadsheet.
Workshops, classes, and trainings
Use limited-capacity registration when every seat matters and buyers need a clear confirmation immediately after payment.
Community and member events
Handle reunions, banquets, association events, club outings, and neighborhood events with one shareable hosted page.
Nonprofit and church events
Use the same payment layer across events, donations, and merchandise instead of adding another event-specific platform.
Pop-up and local events
Move quickly when the main requirement is a clean event page, a working checkout, and less manual cleanup before the event starts.
Built on real product surfaces
This page maps to shipping dashboard and checkout behavior
Flint already exposes event settings in the dashboard and event mode in hosted checkout. This is not a speculative marketing narrative detached from the product.
const link = await flint.paymentLinks.create({
name: "Spring Gala 2026",
mode: "EVENT",
lineItems: [
{ name: "General Admission", amountMoney: { amount: 12500, currency: "USD" } },
{ name: "Sponsor Table", amountMoney: { amount: 150000, currency: "USD" } },
],
eventConfig: {
eventDate: "2026-05-15T19:00:00Z",
location: "River House, Richmond VA",
maxTotalQuantity: 300,
ticketPrefix: "GAL-",
sendTicketEmails: true,
},
customFields: [
{ key: "meal", label: "Meal Choice", type: "DROPDOWN", isRequired: true },
],
});Keep exploring
Follow the right next step for your team
This workflow page should hand buyers into the deeper product, industry, and documentation surfaces without losing the thread.
Event Payments
The deeper product page on Flint's event-mode payment links and API surface.
Fundraisers
See the operator-facing page for tickets, donations, and merchandise in one fundraising workflow.
Nonprofits
Donation, recurring giving, and event collection patterns for nonprofit teams.
Youth Sports
Registration fees, tournaments, and event collections for leagues and parent-run organizations.
Fire Stations
An operator-facing page for fundraising dinners, raffles, registrations, and community event checkout.
Givebutter vs Flint Pay
A comparison page for organizations deciding between event and fundraising suite breadth versus a flexible payment layer.
Payment Links API
The API reference for the hosted payment-link surface behind this workflow.