# How to Track Event Payments and Know Who Has Paid

> How to answer "did they pay?" without reading payment messages: order statuses, what to do about "I paid" messages, and the checks a treasurer should run.

Source: https://laces.run/blog/how-to-track-event-payments-and-know-who-has-paid (HTML version of this page)

The reliable way to know who has paid for your event is to let the payment write its own record, with a status and a name, so nobody has to read messages or judge a screenshot. On Laces, that record is the order. This guide shows how to read it, how to deal with the person who says "I paid", and which checks catch mistakes before your treasurer does.

[Create your event](https://laces.run/app): With Laces, every payment arrives with a name and a ticket. Creating your event costs you nothing.

## "Paid" means one thing

Before anything else, agree what your team counts as paid. A filled-in form is not paid. A screenshot is not paid. A promise from a group leader is not paid. An order is paid when the payment has been confirmed, and that status is the only one you should plan around.

In the app, each event has an **Orders** tab with these pills:

| Pill | What it shows | What you do |
| --- | --- | --- |
| Paid | The money has landed | Nothing. They have a ticket |
| Pending | Waiting on the buyer or the network, plus unsuccessful orders | Wait, or follow up if it has been a while |
| Failed | Failed, expired or cancelled | Consider a nudge, covered below |
| Refunded | Refunded in full or in part | Remember it when you count places and money |
| All | Every order | Use it when you search |

Note that the Pending pill also lists unsuccessful orders. To see only the ones that went wrong, use Failed.

## When someone says "I paid"

This message will arrive, often from someone anxious. Don't argue, and don't take a screenshot as proof. Work through this instead.

**1. Search for them.** The search field on the Orders tab takes a name, phone number or order code. Use the All pill. Try the number they paid from as well, since a parent or colleague may have paid.

**2. If the order is paid,** they're fine. They may simply not have found the ticket. It went to the email on the order, so ask them to check spam, or to open [Find your ticket](https://laces.run/o) with their order code.

**3. If the order is pending or failed and their payment page is still open,** they should stay on it and tap **Check again**. If that shows no payment, they can send the prompt again or change the number from that same page.

**4. If you find nothing, or money left their wallet with no paid order,** they should write to support@laces.run with the number they paid from.

**In every case, they should not start again from your event link.** It can create a second order and a second charge. Put this in bold in your helpers' notes.

If they sent money to someone's personal number, it isn't in Laces at all. You will have to trace that yourself, and it's a good reason not to publish one.

## Open one order when you need the detail

Tapping an order shows what was bought, how it was paid, its timeline, the contact details and who it covers. The last part matters because one order can carry several people. A group leader may be the buyer and never attend.

So don't treat order count as headcount. Twelve paid orders might mean 30 people. Use the participants list for people, and Orders for money.

## Chasing unfinished payments

When people started and did not finish, you have a few honest options.

- **Nudge.** With the Failed pill selected, a banner can show how much didn't go through, and a Nudge button emails those buyers. It goes to failed and expired orders, not cancelled ones.
- **Contact them yourself.** The order carries their contact details. Keep it short, and don't pester.
- **Leave them alone.** Failed orders aren't a debt. Some people changed their minds.

To tell people who have paid about something, use your own email or group chat. Laces has no message tool for that, but the orders file lists each buyer's email and phone.

[Talk to the team](https://laces.run/contact): Tell us where your list stands today, and the team can help you plan the switch.

## A routine that takes ten minutes

**While tickets are on sale,** look at Paid and at Failed once a day, and watch for a sudden jump in failures. It may be a network having a bad day, which is worth a line on your event page.

**In the last week,** download the lists your team will need. Open them on a phone, because that's where you will use them.

**At the door,** don't use a list to decide. Your door team [scans each QR ticket](https://laces.run/blog/qr-code-tickets-event-check-in) in the app, which confirms payment and records the arrival. This needs a data connection. Volunteers are tied to one event and see no revenue.

**After the event,** have your treasurer run the checks below.

## Checks your treasurer should run

Earnings won't equal what buyers paid, because the service fee goes on top. Here's an illustration using Uganda's MTN mobile money rate (UGX 500 + 4%), assuming 40 single-ticket orders at UGX 50,000:

- Each buyer paid UGX 52,500 (UGX 50,000 plus UGX 2,500 in fees).
- All buyers together paid UGX 2,100,000.
- Your earnings are UGX 2,000,000, and that is the number to reconcile.

Other countries have their own rates, such as [Kenya's](https://laces.run/pricing/ke). Then check these:

- **Paid orders times ticket price, by ticket type, matches earnings,** less any refunds.
- **Foreign balances are on their own lines.** A buyer paying from another country shows up in that currency, and it [isn't added to your main total](https://laces.run/blog/how-to-sell-event-tickets-in-multiple-currencies).
- **Available isn't the same as earned.** In Uganda, Airtel Money and card money become available in your Standard Wallet the next day, so a figure can be earned and not yet withdrawable.
- **Withdrawals match the ledger.** The app's ledger lists every line of money in and out.

**Cash needs a separate record.** Laces doesn't record cash and has no desk or walk-in registration. If you take cash yourself, keep your own signed list and add it up separately. Better still, ask the person to register on their own phone from your link.

## Getting it into a spreadsheet

Exports are per event, and only the owner, an admin or someone with the finance role can download them.

- **Orders file:** CSV, Excel or PDF, with one row per order. This is the one for money.
- **Participant CSV:** one row per paid person. Answers to your own questions are included when an owner or admin downloads it.
- **Ledger:** every line of money in and out.

Exports don't record who scanned in at the door. For more about what to collect, see [what a registration database should hold](https://laces.run/blog/event-registration-database), and for the full event-day picture, read [managing registrations, payments and attendance](https://laces.run/blog/manage-event-registration-payments-attendance).

## Frequently asked questions

### Can I mark someone as paid by hand?

No. An order becomes paid when the payment is confirmed. If you took cash, record it outside Laces.

### Can my whole team see who has paid?

Not all of it. Volunteers see no revenue, and only the owner, an admin or the finance role can see the money and export.

### How do I find one person quickly?

Use the Orders search with a name, phone number or order code, on the All pill.

### Why is someone on the failed list when they have a ticket?

They may have tried, failed and then paid in a separate order. Search for their name or number and look for a paid order before you chase them.

### Do participants need an account for me to track them?

No. They need no app or account. Their details and payment are recorded when they register from your link.
