Describe your event, tickets, attendee questions, and Square checkout flow. Makeform creates an editable online registration form with guest details and payment context.
Route registrations to Square, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, and send it to the Makeform builder. Every example field can be changed.
Audience
Adults booking a limited-seat workshop
Format
Single-ticket registration with Square payment
Prompt size
326 chars
Example form structure
Single-ticket registration with Square payment
Attendee name and contact details
Pottery experience level
Accessibility or accommodation requests
Workshop policy acknowledgment
$75 workshop ticket
Suggested registration tags
Payment pending
Paid
Needs follow-up
Ask for a unique registration reference in the Square payment note so organizers can reconcile paid orders with attendee submissions.
Step 1
Choose
ticket, quantity, and session
Step 2
Register
attendee and guest details
Step 3
Pay
matching Square checkout
Step 4
Reconcile
registration and payment status
Registration plus payment
Present the right ticket, gather event-day details, and preserve a reference connecting registration with Square payment.
Show passes, sessions, quantities, and prices first. Conditional sections keep sponsor, student, guest, or group questions relevant.
Capture badge names, guest lists, dietary needs, accessibility requests, and sessions as structured fields.
Carry a registration reference and expected total into payment, with a status field for matching and follow-up.
Flexible event formats
Start with the event model closest to yours, then change ticket logic, attendee questions, and Square payment details in the builder.
Choose a date or time slot, gather skill level and accommodations, then charge a fixed price for each seat.
Offer pass tiers, collect company and badge details, and reveal session choices based on the selected ticket.
Sell seats or tables, repeat guest questions, and record meal choices without mixing them into Square order notes.
Let families or teams choose a session and enter several participants while one buyer handles the Square payment.
Build the registration flow
Describe the event, check the logic, connect Square, and test the handoff before sharing.
Provide the event schedule, capacity, prices, quantity rules, and required attendee details.
Review required fields, conditions, quantities, policies, and the total shown before payment.
Connect Square, map the amount, and pass a reference matching the form response.
Test the amount, reference, payment flow, and confirmation before publishing or embedding.
Choose a registration setup
A connected flow collects attendee fields and provides a practical key for matching registrations with Square records.
Field guide
Build around the information your event team actually uses. These six sections cover ticket selection, attendance operations, payment matching, and useful confirmation details.
Event basics
Show the event name, schedule, venue or online format, age guidance, and deadline before buyers choose a ticket.
Tickets and quantities
Use structured ticket, session, and quantity options. Display each price and reveal eligibility, add-on, or guest questions only when relevant.
Buyer and attendee details
A buyer may register a family, team, or table. Capture their contact once, then repeat necessary questions for each attendee.
Event-day needs
Use clear fields for dietary needs, accessibility requests, emergency contacts, and sessions. Route operational notes only to relevant staff.
Square payment match
Calculate the ticket total, generate a registration reference, and include it in the Square handoff where supported. Track payment separately from submission.
Confirmation and follow-up
Confirm the ticket, session, total, reference, venue, and payment step. Notify organizers about records needing payment matching or a response.
Related tools
Start with a broader registration, RSVP, conference, workshop, or payment form when your event does not need this exact Square-focused setup.
Create a general attendee signup with ticket, session, and contact questions.
Open toolBuild pass tiers, badge details, and session selection for conferences.
Open toolCollect class dates, participant details, and workshop preferences.
Open toolUse a lighter attendance-confirmation flow when no ticket payment is required.
Open toolFAQ
Practical answers for organizers combining attendee registration with a Square payment step.
It collects attendee information, presents ticket or session choices, calculates the expected charge, and guides the registrant into a Square payment step.
Add a Square checkout or payment handoff after submission. Configure the ticket amount, pass a reference where supported, and test it with your Square setup before publishing.
Carry a unique reference into the payment note, metadata, or checkout context when supported. Buyer email, amount, time, and status provide secondary matching details.
Yes. Collect buyer details once, then repeat an attendee section for each guest. Quantity can control the repeated blocks and expected total.
Yes. Add priced pass, table, or session options. Use conditions for ticket-specific questions and review the calculated total before payment.
Mark payment pending separately from submission, notify the organizer, and confirm a payment next step. Staff can match Square payments before following up.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect registrations without a form or response cap. The paid tier removes the Makeform badge.
Test every ticket, quantity, condition, calculation, Square destination, reference, confirmation, and notification. Include unpaid and multi-attendee paths.
Open registration with a clearer payment path.
