# How to Collect Event Registration Fees Through M-Pesa in Kenya

> How to collect event fees through M-Pesa in Kenya with one link: what participants see, what fees apply, how withdrawals work and what to test first.

Source: https://laces.run/blog/mpesa-event-payments-kenya (HTML version of this page)

To collect event registration fees through M-Pesa in Kenya, use a registration page that sends a payment request to the participant's phone, so each payment is tied to a name and a ticket. On Laces, you create the event, share one link, and participants pay in KES by M-Pesa or Airtel Money.

The rest of this guide covers what that looks like in practice, and what to check first.

[Create your event](https://laces.run/app): Create your event and share one link. Each payment arrives with a participant's name attached.

## Why not just share your M-Pesa number?

Many events begin with a phone number or a till on a poster. It works until the messages pile up. Then you have M-Pesa messages on one side and a list of names on the other, and someone has to match them by hand.

Typical problems look like this:

- The person who paid is not the person attending.
- Two people send the same amount within a minute, and you cannot tell them apart.
- A participant sends a screenshot, and you have to decide whether it is genuine.
- A treasurer's phone becomes the only record of who has paid.
- Nobody has a ticket to show at the gate.

When payment and registration happen in one step, these problems mostly disappear. Each payment arrives with a participant's details attached.

## What a participant sees

A participant needs no app and no account. The flow runs in the browser:

1. They tap your event link or scan your QR code.
2. They choose a ticket and enter their name, phone number and email.
3. The checkout shows the ticket price, the Laces Service Fee and the total, before any PIN is entered.
4. They enter their M-Pesa or Airtel Money number and tap Pay. The field starts with +254, so they type the rest without the leading 0, and the network is detected from the number.
5. A prompt arrives on their phone, and they enter their PIN to approve.
6. Once confirmed, they see an order code, and their ticket arrives by email with a QR code.

The email address matters. It is where the ticket and receipt go, so remind people to use one they can open.

**One thing to avoid.** Our general [how to register and pay page](https://laces.run/how) mentions USSD codes for checking a pending request. Those codes are for Ugandan networks, so do not pass them on to participants in Kenya. If someone gets no prompt, they should stay on the payment page and tap **Check again**. If the payment has not gone through, they can send the prompt again or change the number from that same page. They should not go back to the event link and start over, because a second order can mean a second charge.

## Setting up your event: a short checklist

Create the event in the Laces app, then work through this list.

- **Get approved to collect payments.** Your organization needs payment approval before it can accept any registrations, even free ones. Apply early, well before your first poster goes out.
- **Check your organization's country.** An event takes its organization's currency, and there is no per-event picker. A Kenyan organization sells in KES, so set this correctly when you create it, because it cannot be changed later.
- **Add your ticket types.** Each one has its own price and number of places. For a multi-day event, a ticket type for each day or pass makes the choice clear.
- **Ask only what you need.** You can ask your own questions at registration, and you read the answers on each order in the app.
- **State your refund policy.** Write it into your event description. Without one, the [Laces refund policy](https://laces.run/legal/refund-policy) applies. Decide what you will honour, including what happens if the date moves.
- **Write the page for a phone.** Date, start time, the town and venue, what the ticket includes, and how to reach you. The location should make it clear that this is an event in Kenya, because people from other countries will see the link too.

Then buy one ticket yourself from your own Kenyan number, at a real price, before you advertise. Check the prompt, the confirmation screen, the email and how the order appears in the app. Service fees apply to that payment like any other.

## Who pays what

As an organizer, you pay Laces nothing to sign up, list or run an event. Each participant pays a single service fee on top of the ticket price, so nothing comes out of your ticket money. A free event costs nothing, for you or your guests.

The rates differ between countries, so use the [Kenya pricing page](https://laces.run/pricing/ke) and not figures you may have seen for Uganda. It has a calculator for your own ticket price.

As of November 2026, the fee on M-Pesa and Airtel Money in Kenya is KES 20 + 2.9% of the order. On a KES 2,000 ticket, that is a fee of KES 78. The participant pays KES 2,078, and you receive KES 2,000.

Before you print a price, decide how you will present it. If your poster says one number and the checkout shows that number plus a fee, some people will ask why. A short line such as "plus a small service fee at checkout" prevents most of those messages.

[See Kenya pricing](https://laces.run/pricing/ke): See what a participant pays in KES at checkout, and the withdrawal fees that apply to you.

## Getting your money out

Here is what the Kenya pricing page says about withdrawals:

- Your first withdrawal is free, once per organization.
- Each withdrawal after that carries a fixed transfer fee: KES 70 to mobile money and KES 110 to a bank, as of November 2026. You see it before you confirm.
- These fees are charged by the payment providers that move your money, not by Laces, and they cannot be waived.

That page lists the fees and does not state a withdrawal time for Kenya. Rules you may have read for Uganda do not automatically carry over. If a supplier payment depends on an exact date, [ask our team](https://laces.run/contact) before you commit to it.

Until your event has actually run, treat ticket money as money you may have to return. If you cancel, the refund obligation is yours. See [taking payments and getting paid](https://laces.run/guides/accept-payments) for how refunds work, keeping in mind that the guide's figures and wallet timing describe Uganda. For the steps in the app, see [how to withdraw to mobile money](https://laces.run/blog/how-to-withdraw-event-ticket-revenue-to-mobile-money).

## Know which payments actually came through

Someone who tapped Pay has not necessarily paid. A prompt can be missed, or a wallet can be short. Count an entry only once its order shows as paid.

The Orders tab in the app has pills for Paid, Pending, Failed and Refunded, and you can search by name, phone number or order code. When someone forwards an M-Pesa message and says they have paid, look up the order and do not rely on the message. [Tracking who has paid](https://laces.run/blog/how-to-track-event-payments-and-know-who-has-paid) goes through what to do in each case.

## Who your checkout leaves out

In Kenya, Laces offers M-Pesa and Airtel Money. Cards are not offered, and that has real consequences for some events:

- **International delegates and visitors** may not have either wallet. A visitor with a wallet from Uganda, Ghana, Rwanda or Zambia can choose that country under Paying from and pay in their own currency, and that money lands in a separate balance. Anyone else needs someone with a wallet to pay for them, so warn them early on the event page. Our guide to [international payments](https://laces.run/blog/how-to-accept-international-payments-for-events-in-africa) has wording you can use.
- **A company paying for its staff** will need someone with a wallet to complete the order. One order can carry several people, and each gets their own ticket.
- **Large tickets** can run into a person's own wallet limits. If your ticket is expensive, tell people to check their limit before registration day.

If those people matter to your event, plan for them from the start, and do not wait for complaints.

## Bring it to the gate

A smooth checkout is only half the job. Your door team scans each QR ticket in the Laces app, which confirms payment and records the arrival. Scanning needs a data connection, so test the network at the venue. There is a full [door checklist](https://laces.run/blog/qr-code-tickets-event-check-in) in our QR ticket article.

[Talk to the team](https://laces.run/contact): Send us your event details, and the team can answer questions and help you get it set up.

## Frequently asked questions

### Does Laces support M-Pesa in Kenya?

Yes. Participants in Kenya pay in KES by M-Pesa or Airtel Money.

### Can a participant pay by card in Kenya?

No. Cards are not offered in Kenya at the moment. The Kenya pricing page lists the current methods.

### Does a participant need an app or an account?

No. They register and pay in a browser from your link, and approve the payment on their phone.

### Do Uganda's fees apply in Kenya?

No. Kenya has its own rates in KES, shown on the Kenya pricing page.

### What should a participant do if the payment fails?

Stay on the payment page and tap Check again. If the payment has not gone through, send the prompt again or change the number from that same page. Do not start again from the event link.

### Can someone in Uganda or Ghana pay for my Kenyan event?

Yes, from a wallet in their own country. They choose it under Paying from on the payment page and pay in their own currency.

### What if money left a participant's account but no ticket arrived?

Ask them to write to support@laces.run with the number they paid from. They should not pay a second time while this is being checked.
