Taking payments and getting paid: Laces

How mobile-money checkout works on Laces, how quickly your money is withdrawable, what KYC you need, and how to read your organizer statement.

This guide is about money: how a runner pays you, what they are charged, when that money reaches your account, and how to check the numbers.

If you only take one thing from it, take this: Laces is free for you, the fee is charged to the buyer at checkout, and your money is yours to withdraw as soon as each payment is confirmed. The rest is detail.

1. How a runner pays

A runner opens your race page, picks a distance, adds any kit or extras, and pays with mobile money. MTN MoMo and Airtel Money both work, and they do not need an account with anyone, just a wallet with money in it.

What happens on their phone:

They enter their number and press pay.
A prompt arrives on their handset.
They enter their Mobile Money PIN to authorise it.
The entry is confirmed and they get an order code on screen straight away.

Nothing leaves their account until they enter the PIN. If the prompt times out, nothing was charged and their place is still held for a few more minutes while they retry.

The things that go wrong, and what to tell people

You will be asked about all three of these.

What they say	What is actually happening
“No prompt came”	It is usually late rather than missing. They can dial their telco’s pending-request menu and approve it there, or press resend on the page
“It said failed”	Almost always insufficient balance, or the number they typed is not the one holding the wallet
“I paid twice”	Rare, and recoverable. Every payment attempt carries an idempotency key, and a genuine duplicate is refunded in full. Send them to support@laces.run with the order code

Cash at the desk

Runners will turn up on race week with cash. Record them in the Admin App as a desk registration and they land on the same manifest as everyone else, so the kit tent works for them.

Laces charges nothing on a cash registration: no money went through the platform. The cash is yours and it is yours to account for. Cash orders show on your statement marked as such and are excluded from settlement.

2. The fee line, and what it covers

A runner buying a UGX 50,000 entry sees this:

21KM Entry                    UGX  50,000
Laces Service Fee             UGX   1,950
                              ───────────
Total                         UGX  51,950

Laces Service Fee: UGX 500 + 2.9% of the order total. This is what Laces earns, and it applies to the whole order: entries, merchandise and add-ons alike. It is a single, consolidated charge; it already includes the cost of processing the payment, so there is no separate “Payment Processing” line added on top of it. Laces absorbs that cost rather than passing it through as its own line, which is why the fee is one number instead of two.

Two more things worth knowing:

The fee is charged to the buyer, not to you. It is added on top of your price. You set UGX 50,000 and UGX 50,000 is what counts towards your gross.
It is never called a “registration fee.” That label makes runners think it is your charge, and it starts an argument you should not have to have.

A free event costs nothing at all. No payment provider is involved and no fee is charged to anyone.

3. Getting set up to be paid

Before you can charge for entries you need:

A payout account (bank or mobile money) in the name of the organisation selling the entries.
KYC verification. Expect to provide your certificate of incorporation or registration, your TIN, identification for directors or signatories, and proof that you control the payout account.

Two rules that exist to protect participants more than they protect us:

We will not settle to an account we have not verified.
We will not settle to an account in a different name from the selling organisation without a documented explanation.

Do this early. It is the step most likely to hold up a first payout, and it is much less stressful in the week you create your event than in the week after your race.

You can start selling before verification completes: you just cannot be paid until it does. Entries sell, money accrues to your balance, and the moment verification clears it becomes withdrawable. Nothing is lost by starting early; the only thing that waits is the payout.

4. When your money arrives

Money is withdrawable as soon as the payment is confirmed. Since the move to Eversend, a mobile-money entry is not held at all: the moment the provider confirms the charge, that money is in your available balance and you can take it out.

There is no 24-hour wait and no settlement batch to sit through. You are not waiting for race day, and you are not waiting for a business day either.

Two narrow cases still take longer:

A charge we had to confirm by polling rather than by the provider’s own callback is held briefly until that callback independently corroborates it. This is a belt-and-braces check, not a real delay you should plan around.
Older payments taken through Flutterwave follow the previous rule: a 24-hour hold plus provider confirmation, with releases running three times a day.

Your balance always separates what is available from what is still clearing, so you never have to guess which case a given payment is in.

Getting the money out

Minimum withdrawal is UGX 1,000.
Your first withdrawal is free, once per organisation. After that: UGX 1,000 to mobile money at any amount, and UGX 5,400 for a bank transfer. These are Eversend’s rates, charged by them; Laces adds no margin. The exact fee is quoted to you before you confirm.
A code is emailed to you to authorise each withdrawal. It is tied to that amount and that destination.
Withdrawals run every day, weekends included. Eversend settles bank payouts and mobile money on any day, so a Saturday request goes through like any other. (Organizations still on the older Flutterwave rail keep the old restriction: bank transfers there only settle on a business day, so a weekend bank request is refused rather than accepted and silently stalled.)

There is no rolling reserve by default. We reserve the right to apply one (up to 10% of gross, released 30 days after the event) for a first event, an unusually large one, or an organizer with a history of disputes. If we do, you will see it in the Admin App before you go on sale, and we will not apply one to an event that is already selling.

The full terms are in section 5 and section 7 of the Organizer Terms.

If you cancel

You bear the refunds, and this is the part to think hard about. Because your money is available from each sale rather than being held until race day, an event cancelled close to the date has usually already been paid out, and possibly spent. Instant settlement makes this more important, not less.

If funds are still held, we refund runners from them and you do not have to find the cash. If they have already been withdrawn, you are liable to repay them. Section 6 of the Organizer Terms sets out exactly how that works.

The practical advice: treat entry revenue as money you may have to give back until the race has actually been run.

This is the single most important paragraph in this guide for anyone planning a first event on a tight budget.

5. Reading your statement

Every event has a statement. It shows:

Line	What it means
Gross collected	Everything runners paid you: entries, add-ons, donations
Laces service fee	Our fee. Charged to the buyer, shown here for completeness
Payment processing	The provider’s cost on those transactions
Refunds	What has been refunded, and to whom
Held	Collected but not yet released, per section 4
Released	Already paid out to you, with dates
Reserve	Held back against post-event disputes, with its release date
Net payable	What is coming to you

Every line traces back to an order. If a figure is not what you expected, open it and follow it down to the individual orders behind it. The usual causes of a surprise, in order of how often they come up:

Refunds you forgot you issued. They reduce gross.
Cash registrations counted in your head but not in settlement. They are on the manifest, but no money passed through the platform, so they are not in the payout.
The reserve. It looks like missing money and it is not: check its release date.
An event still inside its holding period. Check the settlement date shown on the statement.

Download it any time. If a number still does not reconcile after that, email finance@laces.run with your event and the figure you expected, and it can be traced line by line.

6. Issuing a refund

From the Admin App, open the order and refund it in full or in part.

The money goes back to the mobile-money account that paid. It cannot be sent to a different number, as that is how refunds get diverted.
You refund the entry price you set. The Laces service fee is not reversed: it paid to move the money, and that cost was incurred when the payment was processed. You are not asked to fund it, and you are not charged again to issue the refund.
Where the failure was ours (a duplicate charge, or a payment that took money without creating an entry) the full amount including the fee goes back, out of our margin rather than yours.
Refunds come out of held funds where there are any.
A refund cannot be recalled once submitted, so check the amount first.

Your event’s own refund policy decides whether a refund is owed. You publish that policy, and Laces will not let your event go on sale without one: an event selling entries with no stated refund policy is the most reliable source of disputes in this market.

Laces has its own platform refund policy covering how a refund is processed once it is due, and the handful of situations where we act regardless of your policy: duplicate charges, payments that took money without registering anyone, and cancelled events.

Consider allowing transfers as well. A runner who cannot make it can hand their place to someone else; you keep your number, they are not out of pocket, and nobody has to process anything.

7. A short checklist

Payout account added, in the selling organisation’s name
KYC submitted early, not the week of the race
Refund policy written and published, required before you can go on sale
Settlement schedule and reserve read and understood, in the Admin App
Someone briefed to answer “no prompt came” at the registration desk
Cash desk mode tried once before race week