Payment Gateway Senegal

Payment Gateway Africa lets you accept local mobile wallet payments in Senegal. When you connect to our payment gateway in Africa, Senegal becomes one market within a single integration, alongside six other countries served through the same project setup.

For Senegal, the confirmed local methods are Wave and Orange Money. Both run in XOF, the West African CFA franc. You do not need a separate contract or a separate technical build for each wallet: one integration routes the customer to the method they choose and sends the outcome back to you.

This page explains what the Senegalese route covers, how a wallet payment moves from your checkout to a confirmed status, which operations you can run, and what to prepare before going live. Where a feature depends on the method or on your project configuration, we say so plainly.

The table below summarises the facts that matter when you plan collections in Senegal.

XOF is shared by several West African economies, and electronic money in the zone falls under the BCEAO framework. Treat this as background context rather than a statement about any individual merchant's status. Whether your business can be connected is decided during onboarding, based on your profile and the methods enabled for your project.

Because Wave and Orange Money both use XOF, pricing on your storefront, the amount in the payment request and the figures in your reports all stay in a single currency for this market. That keeps reconciliation simpler than routes where conversion steps sit between the order and the payment.

The steps below describe a typical pay-in on the Senegalese route. The exact screens a shopper sees depend on the wallet and on how they access it.

1. The order is created. Your platform calculates the total in XOF and starts a payment, either by redirecting the shopper to the Payment Gateway Africa hosted payment page or by sending a request through the API.

2. The shopper selects a wallet. They pick Wave or Orange Money and provide the details the method asks for.

3. Approval happens on the customer's side. The shopper confirms the payment in their chosen wallet, following the method's own prompts.

4. The result is recorded. Once the method returns an outcome, the transaction receives a final status: successful, declined or otherwise not completed.

5. Your system is notified. A postback or webhook delivers the status to your backend so you can update the order, release goods or show the shopper a confirmation. These notifications go to you as the merchant; Payment Gateway Africa does not message your customers separately.

Build your order logic around the server-side status rather than the browser redirect. A shopper may close the page before returning to your site, while the postback still reaches your backend.

Payment Gateway Africa treats three money flows as distinct. Keeping them apart in your own accounting avoids confusion when you reconcile.

Pay-ins. Customers pay you with Wave or Orange Money. This is the core of the Senegalese route.

Payouts. Sending funds to customers, such as refunds to a wallet, seller earnings on a marketplace or winnings on a platform, is offered where available for the method and project. Confirm payout scope for your use case during onboarding instead of assuming it matches your pay-in setup.

Settlement. This is the transfer of your collected balance to you. We dispatch merchant payouts on the same day as collection (T+0). This timing covers when the transfer leaves us. When the funds show up in your account depends on your bank or receiving provider.

Reporting. Transaction records let you match each payment to an order reference and track statuses across methods. Finance teams can reconcile Wave and Orange Money activity together, since both share the same currency.

Read more about how these wallets compare across our markets on the page covering Wave and Orange Money payments and the other mobile money methods we route.

You can connect in one of two ways. They are connection options for the same gateway, not separate products.

Hosted Payment Page. You redirect the shopper to a payment page served by Payment Gateway Africa, where they complete the payment. This suits teams that want to launch with limited development work or keep payment screens outside their own codebase.

H2H (API). Your backend talks directly to the gateway, and you control the checkout experience on your side. This suits platforms with existing payment orchestration, custom flows or several storefronts sharing one backend. An H2H connection is a direct technical integration; it is not a white-label arrangement.

In both cases, payment flows run through a browser-based payment page or your own web checkout. Status updates arrive through postbacks and webhooks, which is where your order logic should listen.

The integration guide for hosted page and API connections explains request structure, redirect handling and how to process status callbacks. Full API reference and credentials are provided after merchant onboarding.

Before your project goes live, Payment Gateway Africa runs a know-your-business review. Expect to provide information about your legal entity, ownership, the products or services you sell, the websites or apps where payments will be taken, and the countries and methods you plan to use.

Local rules in Senegal and the wider XOF zone may affect what you sell and how you present terms to buyers. Your own legal obligations, such as consumer protection, tax and data handling, remain your responsibility, and we recommend local legal advice where your situation is not straightforward.

Our AML and KYC onboarding requirements describe the review process, the documents usually requested and how ongoing checks work after launch. Preparing those documents early is the most reliable way to shorten the path from application to first live payment.

Payment Gateway Africa does not publish a fixed public tariff. Your quote reflects your business model, expected volumes, the methods you enable and whether you need payouts as well as collections.

If you already work with us in another market, adding Senegal follows the same commercial logic. Existing merchants can switch on additional supported payment methods without any extra connection charge, and the connection price stays the same however many methods you enable. For existing clients, an already supported method can usually be activated within one day.

See how Payment Gateway Africa pricing works for the factors that shape a quote, then share your Senegalese volumes and use case with our team.

Senegal sits within a group of West African markets that you can add without a second integration.

Also available in Mali: the Mali payment route with Wave, Orange Money and Moov Money uses the same XOF currency, so a merchant already live in Senegal can extend to Malian shoppers with familiar reporting.

Also available in Guinea: our Guinea Orange Money route in GNF lets you reach customers who pay in Guinean francs through Orange Money.

For the full set of seven markets, including East and North Africa, browse the list of countries we cover.

If your customers are in Senegal, one Payment Gateway Africa connection gives you Wave and Orange Money in XOF, merchant postbacks for every status and same-day dispatch of settlements.

Apply to start accepting payments in Senegal and tell us about your business, target methods and expected volumes. Our team will guide you through onboarding, a test project and go-live.