InTouch Wants Africa’s Payments to Meet at One Counter

A payment ought to be the easy part. The customer has money; the merchant has something to sell. In Dakar, Omar Cissé discovered how much work could fit between those two facts. A small shop he opened in 2014 had to juggle roughly fifteen payment services. Each additional way to pay brought another thing to manage.

InTouch grew out of that inconvenience. The Senegalese company gathers payment methods and digital services into a common interface, then makes them available through websites, business systems and physical outlets. Its basic proposition has the appeal of a well-organized counter: put the things people need within reach.

Today, its website reports a presence in 27 African countries, 4,000 business customers and 60,000 TouchPoints. Those are company figures, describing a network whose appeal lies in connecting different habits. A customer paying online, an employer sending salaries and a shopkeeper arranging a transfer can all need the same underlying machinery.

The shop is part of the software

The original product’s name makes the pitch unusually clear. Guichet Unique means a single counter or one-stop shop. For an agent handling different mobile-money operators, consolidation reduces the need to hop between separate tools. For a service provider, it offers access to distribution without recruiting every outlet individually.

TouchPoint applies that logic to the neighborhood shop. An outlet can offer airtime, bill payments, insurance-premium collection and money-transfer services through the platform. These are errands that bring people through a door. InTouch gives a merchant more reasons to be useful between purchases of the shop’s usual goods.

The customer is therefore more than one kind of business. Agents distribute services. Merchants collect money. Large companies need payment flows across locations and departments. InTouch occupies the space between those businesses and the banks, wallets and service providers that complete their transactions. The interface is the visible part; the network of relationships does much of the work.

Petrol stations were a distribution strategy

In July 2017, Total and Worldline signed agreements combining investment, technology and commercial deployment. At the time, the platform was already operating in more than 170 Total service stations and over 600 independent sales outlets in Senegal. Worldline reported more than 30,000 transactions a day in that country.

The partners proposed deployment across eight African markets. Total supplied a route into its stations; Worldline supplied payment expertise and secure hosting. This was a useful combination for a company selling something that had to work both on a screen and across a retail network. A familiar place to stop became a place to transact.

The 2017 financing was reported at €10 million. In July 2021, CFAO and Mobility54 announced a further joint investment through a capital increase. The strategic pattern is instructive: investors with existing commercial operations could help make expansion concrete. For another founder, the copyable idea is to seek a partner whose everyday business creates a use for the product.

From the till to the payroll run

InTouch’s anniversary retrospective says small merchants and multiservice agents originally generated 99 percent of revenue. Demand from larger companies subsequently drew the business toward a wider offering. That helps explain why today’s catalogue contains both a payment terminal and tools for corporate disbursements. The company followed more complicated customer workflows.

Web Payment lets a business accept mobile money and cards on its website. MyTouchPoint addresses a different starting point: a merchant can put products and services on a personalized page and collect remotely without commissioning a custom integration. T!NG Business covers acceptance at a physical point of sale through a smartphone or terminal.

These options matter because a business does not necessarily arrive with a development team. A hosted page suits a seller who needs somewhere to send customers. A website checkout suits an existing online store. A direct API connection gives a company more control over how payment functions appear inside its own software.

Mass payments turn the flow around. An employer, insurer or organization can maintain beneficiary lists and send batches of salaries, commissions, reimbursements or aid. InTouch’s product page describes tracking and reconciliation, the accounting work that determines whether an instruction became a completed payment. Sending is only half the job.

Published customer testimonials make that distinction practical. Senegalese broadcaster RTS describes using Bulk for staff payments, including mission-related bonuses. Afrique Pesage discusses contractor payments and flexible customer acceptance. TotalEnergies describes adding everyday payment services at stations. These are company-published accounts, but the needs are refreshingly specific: pay people, collect money, keep the records straight.

The API has to answer a boring question

For a developer, a payment button is the beginning of a conversation. Did the transaction succeed, fail or remain in progress? InTouch’s developer support material describes a status request for checking that outcome and a callback endpoint for receiving transaction information. That is where a polished checkout meets the less photogenic business of correct records.

Its support page also distinguishes a web interface initialized through JavaScript from a REST API that developers can customize. The choice is consequential. A ready-made interface can reduce the work of presenting a checkout. A more direct integration gives the business responsibility for more of the surrounding experience, including how it communicates the result to a customer.

Custom development extends the offer further. InTouch advertises implementation work, hosting, API integration and e-commerce development, with support and maintenance through the project’s life. Its commercial offering consequently spans transaction services and commissioned technology work. Buyers should compare the whole deployment: integration, support, settlement arrangements and the markets they actually need.

The alternative might be separate relationships with payment providers, or another aggregator. A business already well served by one payment method has less to gain from consolidation. The value becomes easier to see when several methods, outlets or countries create repeated administrative work. That is a question of fit, not simply the longest list of features.

Four kilometers, 500 francs and a cash drawer

One rural example gives the network a human scale. UNCDF profiled Fatou, a cosmetics-shop owner in Thiamène Walo, Senegal, who introduced digital financial services in her village. Residents had previously traveled four kilometers and paid 500 CFA francs in transport to make transactions elsewhere. Moving the service closer changed the cost of an ordinary errand.

But Fatou still needed more liquidity: some larger transfers exceeded the cash she could provide. Her experience is a useful test of any payment story that promises convenience. The customer needs a completed transaction, including cash when cash is what they came for.

Earlier UNCDF research, published in 2019, identified connectivity and liquidity provision as obstacles to rural deployment. Those are concrete conditions under which the model becomes difficult. An agent needs a usable connection, sufficient funds and enough business to keep operating. Signing up an outlet does not settle those questions.

The follow-on rural programme put more emphasis on young agents after their performance in the first phase. It combined expansion with training and performance incentives. By March 2021, UNCDF counted more than 780 agents in that project, including 405 active ones. The distinction matters: recruited locations and working locations answer different questions.

A digital instruction could reach the shop before enough banknotes did.

When the counters closed

The pandemic tested the other side of InTouch’s model. Recalling April 2020, Cissé said, “Il y a eu une vraie panique pendant le mois d’avril.” There was real panic. Physical outlets closed, and the initial trajectory suggested a severe contraction. Online demand then strengthened as customers sought ways to pay without traveling.

For a business built around aggregation, the episode underlined the importance of offering several channels. The useful question was where customers could still transact. A physical network brings proximity; remote collection brings another route when travel becomes difficult. Keeping those routes connected gives a merchant options as customer behavior changes.

The next transaction is the real test

By its February 2025 anniversary retrospective, InTouch was describing an enterprise business alongside its merchant roots, with local teams supporting customers in its markets. Its careers pages span software engineering, operations, legal and compliance, finance and revenue assurance. The breadth suggests the work behind a payment network: someone must build it, operate it and account for what passes through.

Formal market access is another part of that work. BCEAO’s register dated September 15, 2025 lists InTouch entities in Burkina Faso, Guinea-Bissau, Mali and Togo. Those entries concern named local companies. For a prospective customer, the sensible unit of inquiry remains the particular service in the particular country where the business intends to use it.

InTouch’s published onboarding process begins with a conversation, a contract and requested documentation, followed by verification and activation. That sequence gives a buyer an opportunity to establish fees, supported payment methods and operational responsibilities before choosing an integration. The right product should match how the business already gets paid, and how it expects that to change.

The most useful lesson in the company’s history is wonderfully ordinary: begin with the merchant’s repeated nuisance. Then follow it through the whole transaction. A common interface helps with fragmented services. Distribution puts that interface nearby. Local support and adequate liquidity help finish the job. The counter earns its keep when the customer can leave with the errand done.