Request to pay
Your app sends the request, the customer approves with a PIN on the phone, and the order is confirmed.
For many businesses in Benin and West Africa, mobile money is the main way to get paid. We connect the wallets to your application, directly through the operator's API or through an aggregator, so that a payment confirmed on the phone is confirmed in your system at the same moment.
Today
After
One payment, entered once
The tools and AI we work with
Tick what sounds familiar.
Tick the ones that sound like you.
Your app sends the request, the customer approves with a PIN on the phone, and the order is confirmed.
The operator's own API when volume justifies it, FedaPay or KKiaPay when one contract for several wallets is simpler.
Salaries, commissions and refunds sent from a list that a manager approves.
A payment confirmed after a network delay still finds its order, and is never counted twice.
The operator's statement compared with your orders every day, with the differences listed.
Every payment on the customer's file in your CRM, with the number that paid.
Mobile Money holds the data. The AI reads it, with the access rights you decide, and takes over the reading, the sorting and the writing your team does by hand.
Double payments, wrong amounts and unknown senders flagged for a person to decide.
Confirmations and reminders written in the customer's language.
The day's collections by wallet, summed up each evening.
We write down what should happen, when, and which system owns each piece of data, before a line of code.
The integration runs on a test account first, with every case played out, the failures included.
The first real records are watched one by one, and the manual method stays in place until you trust the new one.
Alerts when a call fails, a log of every exchange, documentation and training. The accounts stay yours.
The signature of every event is checked, and each event is processed once, even when it is sent twice.
Secret keys never reach the browser or the code repository, and card numbers stay with the provider.
Declined payments, timeouts, partial refunds and disputes each have a path, tested before launch.
Fees, taxes and payouts are recorded so that the deposit in the bank matches the books.
Access to an operator's API requires an agreement with that operator, and the approval takes time. Limits, fees and available services differ by country and by wallet. We tell you early which route is realistic for your launch date.
MTN MoMo and Moov Money are the ones we are asked for most in Benin. Others can be reached directly or through an aggregator, depending on the country. We confirm the list for your market on the first call.
Often yes, through an aggregator or a local entity. It is a legal and banking question before it is a technical one, and we help you frame it.
You do. The account is opened in your company's name, with your own billing. We work with the access you give us, and you can remove it at any time.
It depends on the number of flows and of systems to connect. We start with a free 30-minute call, then give you a written quote before any work begins. Fees charged by the service itself are billed to you directly, not through us.
Yes. We build, document and train in French, in English or in both, on site or remotely.
An application is rarely connected to one tool. Here are the ones we most often build beside Mobile Money.
A free 30-minute call, in English or French.
What would you fix first?
On the call we walk through your sales process and find where leads and follow-ups get lost.
Ask TECHMA
Answers from our siteAsk in your own words. I answer from this site, tell you honestly when it is not something we do, and can book your free call right here.