I sell laptops. Payments are my daily headache.
I run Kalinko Store, an e-commerce business selling laptops in Guinea. Every single sale forces me to juggle Orange Money, MTN MoMo, bank transfers, and cash. Different apps. Different flows. Different settlement timelines. I reconcile transactions by hand in spreadsheets because nothing talks to anything else.
A customer wants to pay with Orange Money but my checkout only shows MTN? Lost sale. A bank transfer clears two days late and I can’t tell which order it belongs to? I’m digging through screenshots in WhatsApp.
This isn’t a hypothetical problem. I live it.
What’s actually broken
Guinea doesn’t have a Stripe. There’s no single integration that lets a merchant accept all local payment methods. Every provider is its own silo with its own API (if they even have one), its own settlement rules, its own dashboard.
So every business that wants to accept digital payments has to build the same glue code. Connect to Orange Money. Connect to MTN MoMo. Connect to one or two banks. Handle failures on each. Build reconciliation logic. Repeat.
Most businesses don’t bother. They stick with cash and WhatsApp screenshots. The ones that do go digital end up maintaining fragile, provider-specific integrations that break when APIs change without notice.
The result: digital commerce adoption stays low, developers rebuild the same payment plumbing over and over, and customers deal with a worse experience than they should.
What I’d build
One platform. One API. One checkout. Every payment method in Guinea behind a single integration.
A customer pays with their phone number or email. They pick their funding source — Orange Money, MTN MoMo, bank account, or wallet balance. The merchant sees one transaction, one dashboard, one settlement. The developer writes one integration.
Think PayPal, but built for Conakry. A wallet layer that abstracts away the chaos underneath. Merchants get a checkout widget or API. Customers get a consistent experience regardless of which provider holds their money. Everyone gets a single source of truth for transaction history.
How it would work
The core is a payment orchestration layer. A single API endpoint receives a payment request, identifies the funding source, routes to the appropriate provider, handles the response, and normalizes everything into a consistent format.
Underneath: provider adapters for Orange Money, MTN MoMo, and partner banks. Each adapter handles the specific authentication, API quirks, and settlement logic for that provider. When one provider’s API changes (and they will), you update one adapter. Every merchant benefits.
On top: a wallet engine for stored balances, an identity service (phone or email-based), merchant dashboards, and developer SDKs. The checkout experience — whether on a website, mobile app, or in-store — all flows through the same system.
The hard parts
Telco APIs in Guinea are not Stripe-quality. They go down. They change without versioning. Documentation, when it exists, is incomplete. Building reliable payment flows on top of unreliable infrastructure means retry logic, fallback handling, and a lot of defensive engineering. I’ve built systems on unstable infrastructure before — at Hyphen, the lending platform I helped build processed real money on real African banking rails. Same kind of problems.
Regulation is the other big one. Payments means KYC, AML compliance, central bank licensing. Guinea’s regulatory framework for fintech is still evolving, which is both an opportunity and a risk. You can help shape the rules, but you can also get stuck waiting for approvals that don’t have clear timelines.
Then there’s trust. People in Guinea are cautious with money apps, for good reason. The product has to be rock-solid from day one. No “move fast and break things” when you’re handling someone’s rent money.
And liquidity — managing float across providers, ensuring cash-out is fast and reliable, handling the timing mismatches between different settlement systems. This is where fintech gets operationally complex, not just technically complex.
Where this connects
This gateway would plug directly into the Modular Business Suite I’m designing for Guinean businesses — the commerce module needs exactly this kind of payment infrastructure. It could also serve as the payment layer for the Headless LMS (tuition payments, course fees) and benefit from the Digital Identity Platform for verified user accounts.
Current status
This is a concept I’m actively researching, informed by the payment problems I deal with daily running Kalinko Store. The fintech experience from building Hyphen’s lending platform gives me a clear picture of what’s involved — technically and operationally.
If you’re working on payments infrastructure in West Africa, or you’ve solved similar fragmentation problems in another market, I want to talk: laminekalinko2@gmail.com