Building an app in Cameroon? 63 payment solutions to explore before choosing
Your customer is debited but the order remains unpaid. Who traces the money? Explore 63 Cameroon payment leads, profile-specific choices and cost models that include settlement.
The key points of this analysis, checked by the editors.
Start with the operation: collection, renewal, revenue splitting, payouts or international receipt.
Average ticket size, fixed charges and settlement can reverse a comparison of collection percentages.
Fapshi documents an unregistered-business route but now requires account activation before API testing.
Shortlists identify evidence and limitations; the 63 inventory entries are not 63 certified active offers.
A timeout does not establish payment failure: recover the status before requesting another debit.
“A sale is not complete when the money leaves the customer.”
Imagine a parent paying XAF 85,000 in school fees through your application. Their phone confirms the debit, but your platform displays “Payment failed.” They call the school. The school calls you. Suddenly, the commission you negotiated matters less than one urgent question: where is the payment, and who can trace it?
This is an illustrative scenario, not an incident attributed to a provider. It captures what an integration needs to achieve: collect, confirm, match the transaction to the correct record and make the funds available to the merchant.
Choosing a provider means following the customer’s money all the way to the merchant’s account. This guide examines 63 providers, products and projects, distinguishing what their resources establish from the answers still needed. Mobile Money gateways, payout infrastructure, orchestrators and overseas-income services serve different parts of that journey.
What this guide helps you decide. You will find different starting points for an MVP, an unregistered business, agency projects, WooCommerce, SaaS renewals, marketplace distributions and international invoices. Recommendations follow documented capabilities. This is neither a reliability ranking nor a certification of 63 active services in Cameroon.
Documentary review: 16 October 2026. We did not open merchant accounts, make real payments, measure KYC times or test support tickets for this edition. Simulations are our calculations from public prices, with explicit assumptions. Links beside factual statements let you check the underlying sources.
Start with the operation your product needs
Collecting for your own business. You need an MTN MoMo or Orange Money payment, server-side confirmation and settlement to your account. Hosted checkout may be enough; a subaccount architecture may add complexity without solving an immediate need.
Selling a SaaS subscription. Recurring invoices, monthly reminders with payment links and customer-authorised automatic debits are different features. A provider may offer the first two without supporting the third on your chosen payment method. Your application must also decide when to extend access and how to handle unpaid renewals.
Collecting for third-party sellers. A marketplace needs allocation of proceeds, identified beneficiaries, refunds and a contractual definition of who holds the funds. A transfer API alone does not establish that the provider accepts your marketplace model.
Receiving an overseas client's payment. Check merchant eligibility, the payer's method, the incoming currency and the withdrawal route to Cameroon. Displaying euros on an invoice does not create a euro receiving account.
Begin with three questions: who pays, on whose behalf do you collect, and where must the money end up? Choose the technical integration after answering them.
Which providers should you examine for your profile?
An MVP with a tight budget
MeSomb is worth examining for development without moving funds. Its test-mode documentation describes simulations from account creation and says that test mode stops working when the account is submitted for verification. Plan this transition and retain your test scenarios.
CamPay is another candidate for a straightforward local flow. Its official website separates demo and live access and links HTTP documentation, a Python SDK and WordPress integrations. That supports examining it for a Python backend or online store; it does not establish how quickly a new account is actually approved.
Fapshi belongs in a checkout comparison, but not under a promise of immediate testing without verification. Its activation guide explicitly says account activation is now required before API testing. Its sandbox then provides successful and unsuccessful outcomes without real funds. Sandbox availability and the steps required to access it are separate criteria.
Fapshi explicitly describes an unregistered-business option in its activation requirements. Identity, business details and address are still reviewed. A documented route is a reason to shortlist the service, not a guarantee of approval.
PayUnit describes identity documents and a selfie for level-one KYC, followed by business documents at level two. Its KYC page, dated 2023, associates level one with some Mobile Money methods. Confirm the current country and account conditions before making that level a launch dependency.
ZITOPAY distinguishes individuals from businesses. Its FAQ lists identity documents, a taxpayer card, a location plan and a photograph for individuals. An individual account does not mean no paperwork.
If your legal status prevents production access, a more convenient SDK will not resolve it. Establish which collection and withdrawal operations your profile can actually use, with what limits.
An agency delivering several client projects
Account ownership becomes central. Clients should retain their funds, credentials and transaction history when the engagement ends. Using one agency merchant account for unrelated clients creates an operational dependency and may conflict with the relevant contracts.
MeSomb and PayUnit describe services or applications. MOALA documents notifications, refunds and transaction tracking. BUI Corporation publishes country-specific services, separating MTN and Orange collections from payouts in Cameroon. These are reasons to examine them, not evidence that reseller access or client-management permissions are included.
For teams already managing several provider accounts, Cartflox and Zayono address integration orchestration. Cartflox advertises a bring-your-own-keys offer without a Cartflox commission; underlying gateway charges still apply. Zayono also presents a multi-provider API. Check exact connectors, permissions and the handling of payments whose outcome is unknown.
Choose a direct integration when it covers the requirement. Consider orchestration when the maintenance or coverage benefit justifies an additional dependency.
A WordPress or WooCommerce store
My-CoolPay, CamPay, Notch Pay and ZITOPAY publish e-commerce resources or integrations. Start with My-CoolPay's official resources, CamPay's WordPress links and the other providers' documentation. PayUnit also has a WooCommerce section.
Test a copy of your store rather than just the payment button. Check version compatibility, order status, emails, refunds and a payment confirmed after the customer page has expired. A downloadable plugin does not demonstrate recent maintenance.
A SaaS product that renews access
For local collection, MeSomb, CamPay, PayUnit, Fapshi or MOALA may enter a shortlist depending on merchant status and integration. The next filter is the renewal model: payment link, invoice, mandate or an authorised recurring debit.
ZITOPAY advertises subscriptions, but that commercial label does not establish automatic Orange Money or MTN debits for your account. Request the precise consent, first-payment, renewal, failure, cancellation and refund flow.
A fixed charge per transaction matters more for an XAF 1,000 subscription. Annual payment changes cash flow and the importance of refund rules. Product pricing and payment design should be considered together.
A marketplace or a business paying many beneficiaries
ZITOPAY deserves a specific evaluation because its Split Payment offer describes allocation to linked accounts. That positioning is more specific than a generic transfer feature. Confirm your business model, eligible sellers, settlement rules and Cameroon-enabled operations.
For bill processing and batches of payments, Maviance/Smobilpay presents enterprise, agent and institutional use cases with reconciliation in its official solutions. HUB2 and Bizao are additional B2B leads to qualify. Obtain terms and pricing for your actual activity and volume.
Invoicing overseas clients in dollars or euros
SupraPay addresses a different need from local checkout. Its public offer describes USD/EUR receipts followed by Mobile Money withdrawals: 3% on incoming transfers, with no SupraPay withdrawal commission advertised. Card payment links advertise 6%, paid by the customer. First-account activation requires a 10 USDC deposit, credited back after USD 100 in incoming transfers under the stated conditions.
A 3% charge on USD 100 is USD 3; the XAF amount depends on conversion terms. Zero withdrawal commission does not establish zero exchange cost. Confirm eligibility and the final amount quoted before transacting.
How much of XAF 1 million actually reaches you?
We reviewed five public price pages on 16 October 2026. These are advertised standard offers, not negotiated quotations.
For 100 payments of XAF 10,000, collection alone amounts to XAF 18,000 excluding tax for My-CoolPay, 20,000 for CamPay or Notch Pay, 27,000 for ZITOPAY and 30,000 for Fapshi.
For 1,000 payments of XAF 1,000, revenue is unchanged. ZITOPAY's fixed component raises its calculated collection charges to XAF 36,000, while the other collection calculations remain unchanged under the listed formulas. At this stage only, that exceeds the XAF 30,000 calculated for Fapshi.
The two collection formulas meet at XAF 2,500 per payment: 2.6% × 2,500 + 10 = XAF 75, equal to 3% × 2,500. Tax and contractual differences are not normalised. This calculation demonstrates ticket-size sensitivity, not a universal winner.
The settlement route changes the result too
Mobile Money model: 100 payments of XAF 10,000, fees borne by the merchant, then withdrawal of the post-collection balance. We assume the withdrawal percentage applies to that balance. The pages do not establish every charging-base, rounding and tax detail, so these results require confirmation.
My-CoolPay: XAF 1,000,000 − 18,000 leaves 982,000. A 0.5% exit charge on that balance is 4,910, leaving XAF 977,090 before annual maintenance and applicable taxes. Assigning the full XAF 10,000 annual fee to this batch leaves XAF 967,090 before applicable taxes.
CamPay and Notch Pay: XAF 980,000 after collection, then 9,800 in modelled withdrawal charges, leaves XAF 970,200, before any unnormalised tax or additional terms.
Fapshi:XAF 970,000 after collection, with zero withdrawal charges advertised. ZITOPAY:XAF 973,000 after collection if the advertised absence of transfer commission applies to the chosen exit route. Offer conditions still apply.
The modelled difference between CamPay/Notch Pay and Fapshi is now XAF 200 per million, before tax normalisation. An additional charge could move it. Comparing only 2% and 3% collection rates would not demonstrate a guaranteed XAF 10,000 saving.
Bank-transfer model: sending the balance to a bank account in one XAF 5,000 transfer produces XAF 975,000 for CamPay and 977,000 for My-CoolPay before annual maintenance and taxes. Decide the settlement route at the start.
A small launch: XAF 100,000 collected in 100 payments of 1,000 produces modelled My-CoolPay charges of 1,800 for collection, 491 for withdrawal and 10,000 for maintenance if the whole annual charge is allocated to this activity: XAF 12,291 excluding tax. Higher volume spreads the same fixed cost differently.
Ask finalists for a written calculation covering customer payment, collection charge, tax, available balance, exit charge, fixed costs and final amount received. An unknown price is not a zero price.
KYC, delays and support: prevent a blocked launch
KYC is verification of the merchant's identity and activity. Dashboard access, test credentials, live collections and withdrawal may represent four different stages.
Fapshi's activation guide advertises processing usually within 48 hours or less. PayUnit's KYC page, dated 2023, advertises less than 72 hours. These are provider statements, not our measurements or verified contractual commitments. Missing documents or an activity requiring review can change the process.
Confirm documents, limits, enabled methods and suspension or hold conditions. For fund availability, ask a concrete question: if a payment is confirmed at 4 p.m. on Friday, when can it actually reach your account? Weekends, checks and limits matter.
ZITOPAY's FAQ, for example, mentions weekly or monthly settlements while other pages emphasise flexible withdrawals. Confirm the rule applicable to your offer and channel rather than inferring a deadline from a “Withdraw” button.
We do not award support rankings without testing them. Phone, WhatsApp or round-the-clock availability claims do not establish resolution time. Give each finalist the same scenario: “The customer has been debited, the transaction remains uncertain and I have its reference. Who traces it, which evidence is required, and what procedure follows?”
Assess whether the answer identifies a useful process and contact, then request available written commitments. A fast but unusable reply does not help the school in our opening scenario.
Python, Node.js, WordPress or Flutter: what should you check?
Python, Django and FastAPI: MeSomb publishes a Python SDK, CamPay links its Python SDK and PayUnit has a dedicated section. HTTP APIs can also suit Fapshi, MOALA, BUI and others without a framework-specific library. Compare status tracking, error handling and library maintenance.
Node.js and TypeScript: examine MeSomb and PayUnit resources, provider examples and REST response stability. A JavaScript package does not establish comprehensive TypeScript types. Pin versions and review contract changes before upgrading.
PHP, Laravel and WordPress: distinguish backend libraries from store plugins. For My-CoolPay, CamPay, Notch Pay, PayUnit or ZITOPAY, check the exact product, publisher, latest release and your installed versions.
Flutter and Android: MeSomb and PayUnit present mobile resources; CamPay links an Android SDK. Keep secrets on your server. The mobile application requests a payment and displays its status; it should not independently decide that a subscription has been paid.
C# and ASP.NET Core: a documented REST API may be sufficient. Require response examples, stable references, status lookup and an explicit notification-authentication mechanism.
Four protections for the first integration
A stable business reference connects payment to order or instalment. Retain the provider reference and the specific attempt too.
Idempotency prevents the same business action being performed repeatedly. A duplicate notification must not extend access twice or create two shipments. Follow a provider's idempotency-key scope where available and protect your own processing as well.
Reconciliation regularly compares your orders with provider states. A timeout says the response did not arrive in time; it does not establish payment failure. Recover the outcome before requesting another debit.
Server-side verification checks notifications using the documented mechanism, then validates amount, currency, reference and status. A redirect to a success page is not payment evidence.
The 63 names in this guide: which ones fit your project?
A school collecting tuition, an agency delivering several stores and a freelancer paid in euros need different services. Start with the role a provider would play in your project. These 63 names cover gateways, infrastructure, orchestration tools and specialised products; inclusion does not guarantee current availability or merchant eligibility in Cameroon.
Local collections: compare the whole payment journey
For a first Mobile Money payment, an important difference appears before coding begins. MeSomb allows test mode from account creation but says it stops when the account is submitted for verification. Fapshi requires activation before API testing. That difference can affect the date of your first demonstration.
CamPay presents HTTP, Python, Android and WordPress integrations. PayUnit documents applications, environments and identity-verification levels, while ElyonPay provides testing resources. Compare them by reproducing a complete order: initiate payment, receive its notification, retrieve its status and establish how funds reach you. Your programming language affects development; your account permissions determine what you can launch.
Cost needs a separate comparison. Notch Pay and My-CoolPay publish pricing information to examine alongside the simulations above. For My-CoolPay, include annual charges, the stated tax treatment and the withdrawal channel. A lower collection fee may save little once settlement is included.
When an application involves several beneficiaries, inspect the specific functions. ZITOPAY presents revenue splitting; Tranzak Cameroon documents subaccounts and notification tracking. MOALA describes notifications, tracking and refunds, while BUI Corporation separates its Cameroon collection and payout services for MTN and Orange. These capabilities serve different purposes: transferring money to a seller does not, by itself, establish permission to operate your marketplace.
IntaSend has a Cameroon page covering Mobile Money collections and XAF transfers. It offers a concrete starting point for examining that journey, followed by confirmation of the production functions available to your business.
Broader payment coverage: establish merchant eligibility first
Flutterwave, CinetPay, AfriGate and KKiaPay are options to investigate when a project extends beyond one market. This edition does not establish each offer’s current eligibility conditions for a business based in Cameroon. Obtain written confirmation of your merchant country, activity, enabled payment methods and settlement account before comparing interfaces.
For DusuPay, NOKASH and XFIN, also establish the direction of the payment. Sending money into a country and collecting revenue there for your business are separate capabilities. Confirm your complete payment route, including currencies, limits and charges.
Business operations: examine the infrastructure
A business paying many beneficiaries needs to trace each transaction and reconcile its accounts. PawaPay documents operators and collection and payout flows; its documentation explains that the account’s active configuration determines usable operators. Maviance / Smobilpay presents business solutions including bills and reconciliation. Operational tracking, exports and incident handling therefore matter alongside integration.
HUB2 and Bizao are B2B options whose coverage and commercial terms need confirmation for your activity. Kang Open Banking calls for checking which financial services are accessible beyond a store checkout. For DigitWace / WacePay, establish which entity provides the product and which executes transactions, so your contract identifies who handles a problem.
The information gathered here on Beyonic and Softeller does not establish their current offering for a Cameroon project. Obtain an updated product description and access conditions before comparing them with the infrastructure above.
Connecting several gateways: understand the orchestrator’s role
Cartflox and Zayono position themselves around payment orchestration. The questions become how your application selects a provider, tracks a payment and handles failure. Cartflox advertises a model using your own keys without a Cartflox transaction commission; the underlying aggregators still charge their fees. Compare the full cost and available connectors.
Simiz and PAYCORE are further options, but this edition does not confirm their production connectors and full access conditions. Before planning automatic failover, ask how the tool handles a payment with an unknown outcome. Retrying elsewhere can create a second debit if the first attempt eventually succeeds.
Overseas income and specialised services
SupraPay presents USD/EUR receipt with Mobile Money withdrawal. A freelancer should follow the money to the final amount received: account eligibility, any activation charges, receipt fees, conversion and withdrawal. This serves a different need from paying for a local order on your website.
Examine Diool against the specific B2B service required. The crypto-related option WakaPay requires a separate assessment of conversion, settlement and the applicable framework. The evidence gathered here does not support recommending either as a general-purpose collection API.
Other names: what you need before shortlisting them
Other offers may warrant a conversation with their teams, but the information available in this edition does not support an equally detailed comparison. For Monetbil, Dohone, MMGate, Dropme, ZoPay, Paynote / Y-Note, CamerPay and Paymooney, current product scope, merchant access or settlement needs clearer confirmation. Obtain a test journey and production terms matching your project before committing a delivery date.
GetMiPay, WalleoPay, AdwaPay, JonalePay, WaZaPAY, TrustPayWay, DeaconPay, Codees Pay and PayOnUs also need more information about accounts, integrations and transaction tracking. The practical question remains whether you can obtain access, trace a payment by reference and receive funds under written terms.
For Kola, SoleasPay, DrimzWallet and Porsa, first establish whether an independent merchant API is available to third-party developers. Payment functionality inside a product or wallet does not settle that question.
NelsiusPay requires confirmation of splitting features and contractual acceptance of your marketplace model. For ElemiPay, the precise payment offering and multicurrency conditions remain unestablished. Require a demonstration of your intended flow before building around either option.
Finally, the available information does not adequately establish the product, current activity or access conditions for DigitalisPay, Kratos Pay, SP-Heavy, Nexpay, e-nkap and KTCPay. Their names remain here so readers can find them, without attributing unverified functionality or availability. Documented answers from their teams could change their treatment in a future edition.
Turning these names into a shortlist
Choose two or three finalists by identifying what could block your launch. For an MVP, examine test access. Before company registration, establish the merchant documents required. For a marketplace, obtain confirmation of the allocation model. For overseas invoicing, follow receipt and conversion through to the final account. This gives you a consistent journey on which to compare the remaining offers.
Offers with missing information can enter your shortlist once you obtain verifiable answers. Their treatment here reflects the available evidence, without establishing their quality. Infrastructure and orchestration describe roles; neither label establishes reliability or licensing.
Payment services operate within a CEMAC framework published by BEAC. Identify your contracting entity, its role, partners and applicable authorisations. Business registration or partner logos alone do not establish every claimed permission.
The test that separates two or three finalists
Step 1: establish access. Record required documents, enabled functions and the cost of moving from demo to production. Retain the dated contractual price schedule.
Step 2: reproduce the same journey. In sandbox, test success, rejection, expiration, duplicate callbacks and a notification arriving after the browser is closed. After a server interruption, recover the transaction without requesting another debit.
Step 3: reconcile the amounts. In an authorised, low-value live test, compare customer payment, fees, balance, withdrawal and money received. Distinguish a refund from an ordinary transfer to a customer.
Step 4: exercise support. Ask every finalist the same question, measure time to a useful reply and identify escalation. One successful test does not establish annual reliability.
Step 5: check the exit. Agency clients should keep their accounts. Merchants should be able to export transactions. Changing providers should not break the connection between payment, invoice and refund.
A second gateway may reduce some dependencies. It does not resolve an outage shared by both routes or an unknown payment outcome. Blindly switching providers after a timeout can request two payments for the same order.
A decision you can explain to your team
You should be able to say: “We chose this provider because it accepts our merchant status, covers our payment methods, supports this exact flow and fits a cost model that includes settlement. Here is what we tested, what remains unconfirmed and how we handle an incident.”
That is more useful than an unexplained podium. When the parent in our opening scenario calls, your team will need a reference, a reliable status and a procedure. That moment will reveal how well the integration works.
Find the right payment integration for your business.
63 leads, guided choices and a fee calculator. Missing information stays unknown — never zero or unsupported.
Step 1 of 6
What are you building?
Frequently asked questions
Which payment API should I choose for an app in Cameroon?
Start with the operation: local collection, subscriptions, marketplace splitting, payouts or international receipts. Then compare merchant eligibility, enabled payment methods, notifications, settlement and full costs. The guide explains the evidence and limitations behind each shortlist.
Can I collect payments before registering a company?
Fapshi describes an unregistered-business option; PayUnit and ZITOPAY also publish onboarding routes to examine for your profile. Identity and activity verification still apply. Approval and enabled functions are not guaranteed.
Can I test a Mobile Money API without real funds?
Simulation environments exist. MeSomb describes test mode from account creation, with a specific transition at verification. Fapshi requires activation before API testing and then provides a sandbox. Check the access journey as well as sandbox availability.
Which provider costs less for small payments?
Average payment size and fixed charges matter. For collection alone, ZITOPAY's 2.6% plus XAF 10 and Fapshi's 3% formulas meet at XAF 2,500 per payment. Include taxes, settlement and fixed costs before deciding; this does not establish an all-in winner.
Which providers document Python integrations?
MeSomb and CamPay publish Python SDKs; PayUnit has a Python section. A documented HTTP API can also suit Django or FastAPI. Check maintenance, notifications, status lookup and errors, and keep credentials on the server.
Is a transfer API enough for a marketplace?
No. Revenue allocation also requires identified beneficiaries, refund rules and contractual permission for the business model. ZITOPAY presents a split-payment offer; another provider's payout documentation does not automatically establish that capability.
Does SupraPay replace a local Mobile Money checkout?
Its presented offer focuses on receiving USD/EUR income and withdrawing through Mobile Money. Evaluate it for international invoicing, including eligibility, charges, activation and conversion, rather than automatically treating it as a local collection API.
Does the guide list 63 active licensed aggregators?
No. It retains 63 inventory entries across gateways, infrastructure, orchestrators, specialised fintechs and unqualified leads. Inclusion does not certify current activity, production availability or licensing.
Sources and method
Facts that may change over time were checked against the sources below. Observations and interpretations are presented as such in the article.
CEMAC has launched a common QR code so different payment networks can work together. The real test is much more practical: price, simplicity, security and whether merchants actually use it.
Payments in Cameroon: 63 solutions for your SaaS or app (2026) | Trigenys Insights
