To manage event registrations, payments and attendance in one place, use a system where registering, paying and getting a ticket are one step, and where the entrance scan reads that same record. Then you have one list to trust, and nobody has to match payment messages to names by hand.
Below: the workflow, the numbers to watch, who should see what, and what to do when things go wrong.
Why disconnected tools fail
A common setup looks harmless: a form for details, a personal mobile money number for payment, a WhatsApp group for questions and a printed sheet at the gate. Each one holds part of the truth.
The failures tend to show up at the worst time:
- A payment arrives from a number that is not on the form.
- Someone registers and never pays, but still appears on the list.
- Two versions of the spreadsheet disagree, and nobody knows which one is current.
- Staff at the gate call the treasurer to ask whether someone has paid.
The fix is structural. Every step should write to the same record.
The workflow, from start to finish
Here is how that looks on Laces.
- Create the event in the app, with ticket types, prices and any places limit. Ask your own questions at registration where you need more than the basics.
- Get approved to collect payments. Your organization needs approval before it can accept any registrations, even free ones, so apply early from the Earnings tab.
- Share one link. Each event gets its own short link and QR code.
- Participants register and pay from the link: no app to install, no account to create.
- Tickets go out. Participants get their ticket and receipt by email, with a QR code. A ticket page also appears straight away.
- You see it live. Watch registrations and sales come in from the app.
- Staff scan at the door. A valid scan confirms the ticket is paid and records the arrival.
- Withdraw your earnings. Your first withdrawal is free. See the Uganda pricing page for what applies after that, and for how each payment method clears.
How Laces works, end to end follows a real example through all these steps.
Know which screen answers which question
A single event opens on four tabs in the app. Each answers a different question.
| Tab | The question it answers |
|---|---|
| Overview | How is the event doing at a glance? |
| Participants (named for your event type) | Who is coming? |
| Orders | What was paid, and where did it get to? |
| Earnings | How much is mine, and can I withdraw it yet? |
The difference between Orders and participants matters. One order can carry several people, because a group can sign up together and pay once. So an order count is not the same as a headcount.
Keep these numbers separate
Numbers blended together make an event look healthier than it is. Track each of these on its own:
- Registered: people who filled in the form, whether or not they paid.
- Paid: registrations with a confirmed payment. This is the number you plan catering around.
- Pending or failed: people who started and did not finish. Worth following up.
- Earnings: the ticket prices you have earned. The service fee was added on top for the buyer, so it does not appear as your income.
- Available and pending: how much you can withdraw now, and how much is still clearing.
- Checked in: each valid scan records an arrival on that person’s ticket. You see it per person on the scan screen, not as a total.
A planning note: exports cover registrations, sales and money, not check-ins, and the app has no attendance list or count. If you need a final attendance figure for a report, keep a tally at the door.
Decide who sees what
Not everyone on your team needs the same access. Invite people by email from the app, and match each role to the job.
| Person | What they need | How Laces helps |
|---|---|---|
| Gate volunteer | The scanner | Hand a volunteer the scanner for one event and nothing else |
| Event coordinator | Registrations and logistics | Event managers do not see your revenue |
| Treasurer | The money | Only finance, admin and owner see the money and can export |
| Registration lead | Participants’ answers | Answers are visible only to the people you trust with them |
Export for the people who need a spreadsheet
Sponsors, boards and auditors often want a file. You can download an event’s orders as CSV, Excel or PDF, with one row per order, and its paid participant list as CSV, with one row per person. The participant list includes answers to your own questions when an owner or admin downloads it. Exports work per event, so a season of events means one file for each event. Only the owner, an admin or someone with the finance role can export.
Send a file only to the people who need it, and delete old copies.
Plan for exceptions in advance
A two-line plan beats improvising in a queue, so agree on these before the day:
| What happens | What to do |
|---|---|
| “No prompt came” | It is often late. They can approve the pending request from their network’s menu, or resend from the page |
| A payment shows as timed out | Check again before paying again, because the charge may still land. Paying twice is how people get debited twice |
| An order expired | Use Nudge, or Send pay link on the order |
| Someone mistyped their email | Laces asks for it twice, and warns you by email if the ticket could not be delivered |
| A cracked screen at the gate | Type the order code, or search by name or phone |
| A walk-up with cash | Have them register and pay on their own phone from your link or QR code, so they land on the same list. If you take the cash instead, Laces does not record it, so keep a separate signed list and reconcile it yourself |
| Money left a wallet but no ticket came | Participant writes to support@laces.run with the number they paid from |
| A refund | Issue it in the app from the order. It goes back to the account that paid, and cannot be recalled, so check the amount first |
Your event’s own refund policy decides whether a refund is owed, so write that policy with care and put it in your event description. If you don’t set one, the Laces refund policy applies. If you want to compare approaches for different kinds of events, start at solutions by event type.
Once your organization is approved, test the whole chain yourself: create a small event, register, scan your ticket and find yourself in every list.
Frequently asked questions
Can I export the registration list?
Yes, as a CSV of paid participants from the app, one event at a time. Orders are also available as CSV, Excel or PDF. Only the owner, an admin or finance can do it.
Does every registration mean a successful payment?
No. A registration can be pending or failed. Check the paid status on each person or order before you plan around a number.
Can gate staff scan tickets?
Yes. Give a volunteer the scanner for one event and nothing else. Scanning needs a data connection, as our QR ticket guide explains.
Does the organizer need a computer?
No. Everything an organizer does happens in the app on a phone. Laces is also available on the web if you prefer a bigger screen.
Can I see all my events together?
Each event has its own live numbers, and your organization’s earnings sit in one statement. Exports are done one event at a time.
Run your next event from one record
Registrations, payments and check-in in one app, free for organizers. Participants pay the service fee at checkout.
Read next
For organizersEvent Registration Database: What Organizers Need to TrackThere is no public Laces database. See what an event registration database should track, what organizers get in the app, and how attendee data stays private.5 Nov 2026 · 8 min read
For organizersHow QR Code Event Tickets Work: Creation, Scanning and Check-InHow QR code event tickets are issued and scanned, what each result at the gate means, how repeat scans show up, and how to prepare your check-in team.5 Nov 2026 · 8 min read
For organizersHow to Create an Online Event Registration Form That Collects PaymentsWhat to ask, what to leave out, and how to tie each registration to a confirmed payment and ticket, with no screenshots to chase.5 Nov 2026 · 7 min read
