Use cases

What WalleoPay changes, trade by trade.

A payment gateway is not judged on a list of features, but on the work it takes off your hands. For each sector: what happens today without a gateway, what the platform changes, and the customer's actual journey.

3 %

in fees, charged only on payments that go through

3 payment methods

MTN MoMo, Orange Money and Card

100 FCFA to 1,000,000 FCFA

per payment, in whole francs

The same mechanism everywhere

Sectors change, the mechanics do not. Whatever your trade, taking a payment always follows these four steps.

Step 1

You create the payment

From your server, with an amount, an order reference and, if you want, your own metadata.

Step 2

The customer pays

On the hosted page, with their number. The operator is derived from the prefix and the approval happens on their phone.

Step 3

You are notified

A signed webhook is sent to your server, with retries if you are briefly unreachable.

Step 4

You verify, then you deliver

Your server queries the API with the payment identifier. It is that response which authorises delivery.

Selling online

When the order comes in through a website or an app

The checkout flow already exists; what it lacks is a payment method your customers actually use. Taking payment plugs in exactly where your code was already waiting for a confirmation.

Online shop

Today, without a gateway

The customer fills their basket, then reads “send the money to 6XX XXX XXX and message us on WhatsApp”. Some drop out right there. For the rest, someone has to read through SMS statements, find the matching order, and rely on a screenshot everyone knows can be faked.

What WalleoPay changes

Payment becomes a step in the checkout flow, not an after-sales conversation. The order is marked as paid once your server has re-checked the payment against the API, and not before. The WooCommerce and PrestaShop modules do that work without you writing a line.

The journey

The customer confirms their basket and lands on the payment page. They enter their number, approve the request on their phone, and come back to your shop. Your server receives the webhook, queries the API, and the order moves into preparation.

Mobile app

Today, without a gateway

Integrating MTN and Orange separately in an app means two contracts, two response formats and two ways of handling errors. Many developers give up and display a number to be credited by hand, which pushes all the work onto support.

What WalleoPay changes

The app has nothing to integrate on the operator side: it asks your server for a payment, opens the URL it gets back, and waits for the result. The secret key stays on your server, never inside the app shipped to phones.

The journey

The user taps “Pay”; your server creates the payment and returns the URL to the app, which opens it. Once the request is approved on the phone, the user comes back to the app. Your server confirms through the API before unlocking the feature that was bought.

Hosting provider or web agency

Today, without a gateway

You invoice domain names, hosting or services to dozens of clients. Every due date ends in a manual reminder, a wait for a mobile money transfer, then a hand-made reconciliation in your billing tool.

What WalleoPay changes

The invoice carries its own payment link and your tool updates itself once it is settled. The WHMCS module settles invoices by mobile money with automatic reconciliation; if you resell services to your own clients, each project can have its own service and its own separate keys.

The journey

Your tool issues the invoice with the payment link attached. The client pays from their phone, even without a bank card. The signed webhook marks the invoice as settled and releases the service without anyone re-reading a statement.

Taking payment without a checkout flow

When the sale closes over a message, a call or a counter

A large part of Cameroonian trade happens without any online shop. The payment link then replaces the number read out over the phone, and puts a usable record back on both sides.

Restaurants and delivery

Today, without a gateway

The order comes in by phone or by message. The rider leaves with change, sometimes takes a transfer on their own number, and the till only balances at the end of the day — when it balances at all. A customer who “already sent it” is impossible to contradict on the doorstep.

What WalleoPay changes

Payment is taken before the rider leaves, into the business account rather than an employee's. Each order has its own payment, with its exact amount and its time: no change to find, no gap to explain in the evening.

The journey

The restaurant takes the order and sends the payment link by message. The customer pays from their phone while the kitchen cooks. The order only goes out for delivery once the payment is confirmed through the API.

Transport and logistics

Today, without a gateway

Seat booking, parcel shipping, intercity trips: the deposit is paid in cash at the desk or by transfer to a personal number. The passenger has no proof, and the agency does not know who has actually paid until departure.

What WalleoPay changes

The booking is paid in advance and tied to its reference. The desk checks the payment status instead of hunting for an SMS, and the money lands in the company account, not in that of whichever agent was on duty.

The journey

The customer books by phone or online and receives a payment link, valid for 30 minutes. They pay, and the seat is held. At departure, the agent finds the booking by its reference, already marked as paid.

Merchant with no website

Today, without a gateway

You sell over messaging, by phone or in the shop. You read out a number, the customer gets a digit wrong or sends 15 000 instead of 1 500, and you spend the day sorting it out. No sale is recorded anywhere but in your message history.

What WalleoPay changes

A payment link is created with a single API call, from a small script or with the PHP SDK. You set the amount, the customer can neither change it nor send it to the wrong recipient, and the sale appears in your ledger like any other. There is no “create a payment” button in the dashboard yet: that call is still the only way.

The journey

You create the payment with its amount and its description, then send the link you get back to the customer, over the channel they already use. They pay from their phone, with nothing to install. Your dashboard shows the successful payment, with the exact amount and time.

Associations and fundraising

Today, without a gateway

Annual dues, tontine, a collection for an event: the treasurer takes the money on their personal number and keeps a notebook. Nobody questions their good faith, but nobody can check it either, and changing treasurer becomes a delicate exercise.

What WalleoPay changes

The collection goes through an account in the association's name and every contribution leaves a dated entry with its amount and its status. The ledger can be exported: the financial report is prepared from a file, not from a notebook.

The journey

The association sends the membership payment link to its members. Each one pays from their own wallet, in their own time. The treasurer follows the contributions in the dashboard and pays the balance out to the association's account.

Selling access, a seat or a subscription

When the payment has to grant a right, immediately

Here the payment does not trigger a physical delivery: it opens access. Checking through the API is therefore not an accounting precaution, it is what stops someone getting in without having paid.

Training and online content

Today, without a gateway

The applicant sends a transfer, then a screenshot, then waits for a human to open access. Between the payment and the first lesson a whole day can go by — long enough for them to ask for a refund or go elsewhere.

What WalleoPay changes

Access opens as soon as your server has confirmed the payment with the API, with nobody stepping in. Since the amount is set when the payment is created, a reduced rate or a promotion is handled on your side, with no haggling at the moment of payment.

The journey

The learner picks their course and pays on the hosted page. Your platform receives the signed webhook, verifies the payment, and creates the account or unlocks the module. The learner starts within the minute.

Ticketing and events

Today, without a gateway

Seats are booked by message and paid at the door, or by transfer with no receipt. On the day, the entrance is a bottleneck: you have to find a name on a list, check a phone screen, and settle disputes under pressure from the queue.

What WalleoPay changes

Every seat sold matches an identified payment, which can be checked before the event and at the door. You know at any moment how many seats are actually paid for, not how many were promised.

The journey

The buyer picks their seat and receives a payment link. They pay, and your system issues the ticket with its reference as soon as the API confirms. At the door, the check is on the ticket reference, not on a screenshot.

Subscriptions and recurring billing

Today, without a gateway

Every due date turns into a chase: message the customer, wait for the transfer, tick it off by hand, then reactivate the service. The cost of collecting ends up higher than the margin on small subscriptions, and unpaid dues go unnoticed.

What WalleoPay changes

Every due date becomes a dated payment, carrying its own reference and its own link. The renewal is extended automatically on confirmation, and unpaid instalments show up in the ledger straight away rather than when the customer complains.

The journey

On the due date, your system creates that month's payment and sends its link to the subscriber, who pays by mobile money, without a bank card. The signed webhook extends the subscription, and the payment appears in your ledger with its period.

Direct debit without any action from the customer does not exist in Cameroonian mobile money: every instalment requires an approval on the phone. The recurrence we make possible is that of the billing, not of a silent debit — and we would rather write it here than let you find out during integration.

Comparison

Taking payment by hand, or taking payment with WalleoPay

The manual method — a number read out, an SMS statement, a notebook — works, otherwise nobody would use it. It simply costs time and certainty. Here is the point-by-point comparison, without overstating the faults of one or the merits of the other.

What has to be done	By hand	With WalleoPay
Knowing that a customer has paid	Read an SMS statement, or believe a screenshot sent by the customer.	Your server queries the API and gets the real status of the payment at the operator.
Matching a payment to an order	Search the history for the time and the amount, hoping no other customer paid the same sum.	Your order reference is carried by the payment itself, from creation through to the ledger.
Avoiding a wrong amount	The customer types the sum themselves. A digit too many or too few has to be put right afterwards.	The amount is set when the payment is created; the customer does not type it.
Taking both MTN and Orange	Two numbers to give out, two histories to read through, and a customer who picks the wrong network.	A single link. The operator is derived from the prefix of the number entered.
Giving the customer proof	None, apart from the SMS from their own operator.	A payment identifier, a status that can be checked and a receipt your system can issue.
Knowing what is still owed	A notebook, a spreadsheet, or the memory of whoever keeps the till.	A dated ledger, with the balance after every movement, exportable.
Tracing a payout	The money stays on a personal number; money going out cannot be told apart from private spending.	The payout is a dated operation, with its fees stated up front, and the balance is credited back if the transfer fails.
Being notified automatically	Someone has to watch their phone.	A signed webhook is sent to your server, with retries until it answers.
Delegating to an employee	Handing over the phone that receives the money.	Giving them a limited role in the dashboard, revocable in one click.
Direct cost	No gateway fee, but time spent reconciling and sales lost at the payment step.	3 % per successful payment, nothing on failed payments.

What that looks like on a sale

Sale of 2,500 FCFA

2,425 FCFA

credited to your balance, after 75 FCFA in fees

Sale of 25,000 FCFA

24,250 FCFA

credited to your balance, after 750 FCFA in fees

Sale of 150,000 FCFA

145,500 FCFA

credited to your balance, after 4,500 FCFA in fees

The fee applies only to payments that go through: a customer who gives up, or whose payment fails, costs you nothing. The full detail, including payout fees, is on the pricing page.

Straight talk

What is not a good fit yet

Three situations where WalleoPay is not the right tool today. Better to know now than to find out after integrating the platform.

High volumes on a merchant code

As long as an account collects through a merchant code, the customer pays from their USSD menu then declares their reference: the payment moves to awaiting confirmation and a human reconciliation validates it, sometimes the next day. That is perfectly workable for a few dozen operations a day; it no longer is at several hundred.

Beyond that, you have to go through the operator API, which means an MTN or Orange contract and the credentials that come with it. The code on your side does not change: only the account configuration does.

Let's talk about your volume

The activities we do not process

Some activities and some goods cannot be processed by the platform, however profitable they are. This is not a moral stance taken after the fact: it is a condition set by the operators and by the regulations, and an account that crosses it is suspended.

The list is public and kept up to date. Read it before integrating anything, especially if your business touches gambling, currencies, regulated goods or the resale of subscriptions.

Read the list of prohibited activities

Countries other than Cameroon

A country is only open once an operator contract exists and its numbering plan is built in: without the prefixes, there is no way to know which operator to route a payment to. Today, the list fits on one line.

Cameroun +237 XAF

The other markets in the region are declared in the platform, not open. If you trade there, tell us: that is what decides the order of priority.

See the markets covered

Your case is not on this page

Describe your business and the way you take payment today. We will tell you straight whether the platform fits, and what would be missing.

Write to us

Try it on your own case

Signing up immediately gives you test keys and demo numbers. You can reproduce your own flow from end to end, with no commitment and no real money moving, before deciding anything.

Open an account See a real payment