Skip to content
Blog

Africa travel agency booking platform, built for mobile money

Tekravel Editorial
Written with the help of AI

A customer in Lagos picks a fare to Nairobi on your site, types her phone number and waits for the prompt on her handset. It arrives. She enters her PIN. Then nothing happens on your screen for a while, because the confirmation from the wallet operator is still travelling back through two systems that do not know your booking exists. She refreshes. She messages you on WhatsApp with a screenshot of the debit. By the time the payment is confirmed, the fare she chose has repriced. Every Africa travel agency booking platform gets judged on that moment, and most imported ones were designed by people who have never had to live through it.

Mobile money is not a payment method you add to a card checkout. It changes the order in which a booking has to happen, the volume and shape of your support, and what you can honestly promise in a refund policy. This piece walks through those three changes, plus two things that sit next to them: routes inside the continent, and pages that keep working when the connection does not.

The payment confirms after the fare has moved

A card checkout is built on an assumption so old nobody states it: the answer comes back while the customer is still on the page. Approved or declined, the booking engine knows within the same request, so it can price, take the money and issue the ticket in one breath.

Mobile money breaks that assumption. The customer approves the payment on a different device, or the same phone in a different app, and the confirmation travels back asynchronously. Usually it is quick. Sometimes it is not — the USSD session times out, the network is congested at the end of the month, the wallet operator's callback is delayed, or the customer simply puts the phone down to find the PIN. A platform that treats "no answer yet" as "failed" will cancel bookings that were paid for. A platform that treats it as "succeeded" will issue tickets nobody paid for. Both happen, and both cost real money.

The flow that holds up separates the steps a card checkout fuses together:

  • Price and hold first. Before you ask for money, the booking should exist on the supplier side in a held state, so the fare the customer saw is the fare that is waiting for them. Whether a given fare can be held, and for how long, is the airline's and the supplier's rule, not yours — find out before you design around it.
  • Ask for payment against the held booking, with a reference the customer can see and quote back to you.
  • Issue only on a confirmed payment, never on the customer's word or a screenshot, however genuine it looks.
  • Decide in advance what happens when the confirmation lands after the hold expired. This is the case that hurts.

That last line is where the money goes. The customer has paid. The seat is gone or the fare has moved. You now owe either a reprice conversation or a refund back to a wallet, and the refund path for mobile money is rarely as quick as the debit was. An agency that has not written this rule down ends up improvising it on WhatsApp, at night, with an annoyed customer who has the receipt and is right to be annoyed. Over a season, the cost is not the one refund. It is the reputation for "they took my money and there was no ticket", which spreads through exactly the channels you depend on for sales.

So the first question to put to any platform you are considering is not "do you support mobile money?" It is: what state is the booking in while the payment is pending, and what does the system do if the payment confirms late?

Card-first checkout against mobile-money-first

The differences are easier to argue about side by side. Some rows here depend on the rail and the country, which is the point — read them against your own market.

 Card-first checkoutMobile-money-first checkout
When you know you have been paidInside the same requestLater, from a callback or a status check
Booking state while waitingBarely existsMust be held and visible to the customer
Customer's proof of paymentYour confirmation pageThe wallet's SMS, which reaches them before yours does
Where the first support message landsEmail, if at allWhatsApp or a phone call, within minutes
Refund routeBack to the card, through the acquirerBack to the wallet or a bank account, often by hand
Main failureFraud and chargebacksPaid but not issued, or issued but not paid

People will disagree with the refund row — some rails handle reversals cleanly, some agencies refund by bank transfer on principle. Disagreeing is fine. Not having decided is the problem.

Routes inside the continent, and the content you will not find

Intra-Africa travel is where a generic storefront shows its gaps fastest. A search between two African capitals can come back with itineraries routed through hubs far outside the continent, while a sensible connection through a regional hub is missing, because the carrier that flies it is not in the content source the platform happens to use.

Before launch, write down the city pairs your customers actually ask for and search each one. Not the obvious long-haul routes to London or Dubai — those will be there — but the regional ones that make up your WhatsApp traffic. Where a route is missing, you need to know whether that is the supplier's coverage, a carrier that only sells direct, or a fare your consolidator could load. Each has a different fix, and only one of them is a software problem.

Pages that survive a dropped connection

Your customers are on mobile data, often prepaid, often switching between networks in the middle of a booking. A checkout that loses everything when the page reloads loses the booking. The fixes are not exotic, and they matter more here than any visual polish:

Show the booking reference early, before payment, so a customer who drops off can come back to the same booking instead of starting again. Give the pending-payment state its own page that can be reopened from a link, rather than a spinner that only exists in one browser tab. Keep traveller details the customer has already typed. And keep the pages light: every image you do not need is money on a prepaid bundle and seconds on a slow cell.

Language and currency belong in the same list. On this platform the storefront ships in 40 languages, among them French, Portuguese, Swahili and Arabic, and each white-label sets its own default currency and the list it offers — a Nairobi agency shows KES by default, a Dakar one XOF, a Lagos one NGN — with prices converted from the tenant's own rate table. The same constraints shaped what we wrote about Central Asian agencies selling over mobile data, and the checkout point echoes how LatAm payment habits change the cart.

Support lives on WhatsApp, so the refund policy has to as well

In a card market, a customer with a problem sends an email and waits. In most of the markets this piece is about, they send a voice note within minutes, attach the wallet receipt, and expect someone to answer who can see the booking. That is not a channel preference you can train away. It is how trust works there, and an agency that answers fast on WhatsApp wins repeat business on it.

What you can do is make sure the person answering has the facts. A booking record that shows the payment status, the hold, the ticket and the history in one place turns a long back-and-forth into a short answer. Staff roles in the admin panel decide who can see what and who can issue or refund, so a junior agent answering the weekend shift does not need to escalate everything.

The refund policy itself should be written around the rail, not copied from a card-market template. Say plainly where refunds go — back to the wallet that paid, or to a bank account — and who initiates them. If you sell through sub-agents who collect cash or mobile money from their own customers and settle with you, their credit limits and settlement invoices need to be part of the same system rather than a spreadsheet beside it; on this platform they are first-class records, which is what makes a disputed payment traceable months later.

Before you switch on a mobile-money checkout

  • Find out which fares you can hold, through which supplier, and for how long.
  • Decide the booking state while payment is pending, and show it to the customer with a reference.
  • Write the rule for a payment that confirms after the hold expired: reprice, refund, or both, and who calls the customer.
  • Agree with your payment provider how reversals work, and how long they take.
  • Search your real regional city pairs and note every gap.
  • Decide who answers WhatsApp, in which hours, and what they are allowed to do without escalating.

Notice how little of that list is code. The platform can make the right sequence possible; it cannot choose your refund policy or your support hours.

Trying it before you commit

The quickest way to judge any of this is to put a booking through it. The signup wizard provisions a branded site on a platform subdomain without asking for a card, so you can set your currency and language, run the routes from your list, and see what each step of the checkout does before a single customer touches it. Then put the questions from the checklist to whoever will process your payments.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.