# How to Automate Event Registrations and Payments

> Which event registration and payment jobs can run on their own, which should stay with a person, what Laces will not automate, and how to test the failures.

Source: https://laces.run/blog/how-to-automate-event-registrations-and-payments (HTML version of this page)

To automate event registrations and payments, make one event where each confirmed payment triggers the next step, so nobody copies anything between a form, a wallet and a list. You don't need scripts or a developer for this. You need one tool that holds all three, a clear idea of what stays with a person, and a test of what happens when things fail.

[Create your event](https://laces.run/app): Every payment creates its own registration and ticket. Set up your event free and test it yourself.

## Start with what you copy by hand

Think back to your last event and write down every time someone moved information from one place to another. It might look like this:

- Reading a payment message and ticking a name on a sheet
- Typing a confirmation message to each person
- Counting sign-ups to see whether a ticket has sold out
- Sending the door team the latest version of the list
- Chasing people who filled in the form and never paid

Each line is a job that can break, and each one gets worse as the event grows. That list is your automation brief. Anything not on it probably doesn't need automating.

## What runs on its own in Laces

Here is the chain for a paid ticket, trigger by trigger.

| When this happens | Laces does this |
| --- | --- |
| A buyer picks a ticket | Shows the ticket price, the service fee and the total before any PIN |
| They type a number | Works out the network from the number, with no network to choose |
| They approve on their phone | Waits for the payment to be confirmed |
| The payment is confirmed | Marks the order paid and adds each person to your list |
| The order is paid | Sends the ticket and receipt by email, and opens a ticket page with a QR code |
| An order comes in | Emails your team a notice of what was paid |
| A payment fails | Keeps the failed order on your list and emails the buyer about it |
| A ticket type fills up | Stops selling that ticket |
| Your closing date passes | Checkout refuses new registrations |
| The event is two days away | Emails paid participants a reminder, and your team a paid count |
| A ticket is scanned | Records the arrival, with no second button to press |

A free ticket skips the payment step. A valid ticket is one tied to a confirmed payment or a free order, so nobody gets a QR code for a payment that never landed.

The reminder is worth a closer look. It carries the order code, a link to the ticket, calendar links and your contact details. You can't add your own message to it, so anything specific, like what to bring, belongs in your event description.

Payment methods depend on your country: MTN MoMo, Airtel Money and cards in Uganda; M-Pesa and Airtel Money in Kenya; MTN MoMo, Telecel Cash and AT Money in Ghana; MTN MoMo and Airtel Money in Rwanda; MTN MoMo, Airtel Money and Zamtel Kwacha in Zambia.

[See your country's fees](https://laces.run/pricing/ug): See what a participant pays at checkout in your country, and what reaches you.

## What should stay with a person

Automation should remove copying, not judgment. These jobs stay with you, and most should.

| Job | Who does it | Why |
| --- | --- | --- |
| Getting cleared | You apply from the Earnings tab | Your organization needs clearance before any registration opens, free tickets included |
| Chasing unpaid orders | You tap **Nudge**, or **Send pay link** on one order | You choose when to contact people, and how often |
| Refunds | You issue them from the order | A refund can't be recalled, so someone should check the amount |
| Telling people about changes | You, on your own channels | Laces has no campaign tool, so use your own email list or group chat |
| Withdrawing | You, when you choose | Your first withdrawal is free, and later fees are shown before you confirm |
| Cash | You, on your own signed list | Laces does not record cash |

## What Laces will not automate

It's better to know these before you plan around them. Laces has:

- No automatic price rise on a date. A lower first price is a separate ticket type with limited places.
- No waitlist that fills a freed place.
- No WhatsApp integration. You paste your link into chats, and tickets come by email and on a ticket page.
- No discount codes, donations or merchandise add-ons.
- No import. Each person registers for themselves from the link.

If you want registrations on your own site, the [Partner API](https://laces.run/solutions/developers) is built for that, but it has no attendee-list or check-in endpoint.

## Test the failures, not only the success

Automation looks perfect until the first payment goes wrong. Once you are cleared, run these on a real phone before you promote the link. Buying a low-priced ticket will be a real payment, so use your own number and wallet.

1. **Pay normally.** The ticket email arrives, and you appear on the list.
2. **Reject the prompt on your phone.** The page should say so, and the order should show under Failed or Pending.
3. **Let the prompt time out.** See what the page tells you to do next.
4. **Sell out a test ticket.** Set one place, and buy it. Then see what a second buyer sees.
5. **Read every email** on a small screen, and check spam too.

Then write down one line for your team and put it in your pinned message. When a payment seems to fail, the buyer should stay on the payment page, tap **Check again**, then send the prompt again or change the number there. They should not start over from the event link, because that can cause a double charge.

## A ten-minute check that replaces the spreadsheet

Automation needs a little watching, not a lot. Once a day while sales are open:

- Open Orders and look at the Failed and Pending filters. Nudge if it has been a while.
- Compare your paid count with what you planned for food, seats or shirts.
- Read any email warning that a ticket couldn't be delivered.
- If the same question keeps coming in, add the answer to your event description.

Before the event, download your [participant list](https://laces.run/blog/manage-event-registration-payments-attendance) as a backup, and treat that file as a snapshot, not as the record. For door planning, see our guide to [QR code tickets and check-in](https://laces.run/blog/qr-code-tickets-event-check-in).

[Ask the team](https://laces.run/contact): Tell the team how you run registrations now. They can tell you what Laces will and won't do for it.

## Frequently asked questions

### What parts of event registration can be automated?

The order record, the fee and total, the ticket, the emails, stopping sales when a ticket is full, the reminder and the arrival record. Refunds, chasing and event news stay with you.

### Do I still need a spreadsheet?

Not to run the event. You can download one when a specific job needs it, such as giving a caterer a count.

### Does a ticket go out before payment is confirmed?

No. On a paid ticket, the ticket comes after the payment is confirmed. A scan of an unpaid registration shows as not paid.

### Can I schedule my own reminder messages?

No. Laces sends its own reminder two days before the event, and you can't change the wording. Send anything else from your own channels.

### Do participants need an app?

No. They register and pay from a browser. Only your team uses the app.
