Accepting Wave and Orange Money in Senegal: A Merchant's Guide

Senegal is a mobile wallet market. Many buyers expect to pay from a phone-based account, so a checkout built only around other payment types will miss a large share of them. That is why merchants planning a launch here usually start by checking which wallets their gateway connects to.

Payment Gateway Africa supports two local methods in Senegal: Wave and Orange Money. Both are processed in West African CFA francs (XOF). For the full market profile, including how these methods sit inside our product, see our Senegal payment gateway page.

This article covers the practical side of a Senegal launch: what your customers see, how money moves in each direction, how your systems learn payment outcomes, and which questions to settle with any provider. Payment Gateway Africa also operates as a wider payment gateway for African markets, so the same setup can extend to other countries later.

Key points to keep in mind:

Two local wallets are supported in Senegal: Wave and Orange Money.

Transactions are denominated in XOF, the currency shared across the BCEAO zone.

Pay-ins, payouts and merchant settlement are separate flows, each with its own logic.

You can connect through an API (host-to-host) or send customers to a Hosted Payment Page.

Payment status reaches your backend through postbacks and webhooks.

Wave and Orange Money each hold their own place in everyday Senegalese payments. A customer who has one may not have the other. Offering both gives your checkout broader coverage than relying on a single wallet.

From a merchant's point of view, the two methods share a pattern. The customer selects a wallet at checkout, provides the details the method requires, and confirms the payment inside that wallet's own environment. The exact confirmation step depends on the method's flow, so you should design your checkout to wait for the result rather than assume it.

Because both methods settle in XOF, you avoid running separate currency logic for each wallet in Senegal. Your pricing, order records and reconciliation can all use a single currency for this market.

| Item | Senegal |

| --- | --- |

| Currency | XOF (West African CFA franc) |

| Supported local methods | Wave, Orange Money |

| Monetary authority | BCEAO (Central Bank of West African States) |

| Connection options | API (host-to-host) or Hosted Payment Page |

| Status delivery | Postbacks and webhooks to the merchant |

A note on scope: this guide describes the methods Payment Gateway Africa supports in Senegal. We do not position card acceptance or QR payments as part of the Senegal offer, so plan your checkout around the two wallets.

A clear payment journey reduces abandoned orders. For a Wave or Orange Money payment, the sequence typically runs as follows.

1. The customer reaches checkout on your site or in your browser-based flow and sees the amount in XOF.
2. They choose Wave or Orange Money as their payment method.
3. They enter the details the selected wallet needs, either on your own form (API integration) or on the Hosted Payment Page.
4. The payment request is passed to the wallet, and the customer confirms it using that wallet's own process.
5. The gateway receives the outcome and sends the status to your backend.
6. Your system updates the order and shows the customer a success or failure message.

Two design choices matter here. First, show a clear waiting state after step 4, because confirmation happens outside your page. Second, never mark an order as paid based on the customer returning to your site. Base fulfilment on the status your backend receives from the gateway.

If your product runs inside a mobile app, plan for a browser-based payment page. The payment flow works through a page in the browser rather than a native in-app component.

Merchants new to the region often treat every money movement as one thing. In practice, a gateway handles three separate flows, and each needs its own place in your finance process.

Pay-ins are payments from your customers to you. In Senegal, these are Wave and Orange Money collections in XOF. They are the core of most launches.

Payouts are payments from you to your customers or other recipients, such as refunds paid back to a wallet, marketplace seller disbursements or rewards. Payouts are offered where available for the method and project, so confirm payout support for Wave and Orange Money as part of your onboarding rather than assuming it.

Settlement is the transfer of collected funds from the gateway to you as the merchant. Payment Gateway Africa dispatches merchant settlements same-day (T+0). This timing covers when we release the payout, not when the money reaches your account; bank posting times vary depending on the receiving institution.

Keeping these flows apart in your reporting makes reconciliation easier. Match pay-ins to orders, payouts to their recipients, and settlements to your bank or treasury records. Mixing them is a common source of month-end confusion.

Payment Gateway Africa offers two ways to connect. They are connection methods for the same gateway, not separate products, and you can choose based on your team's resources.

API (host-to-host). Your backend talks directly to the gateway. You build and control the checkout screens, collect the details each wallet requires and handle every response. This suits teams that want full control of the user experience and have developers to maintain it. Note that a host-to-host connection is not a white-label arrangement.

Hosted Payment Page. You redirect the customer to a payment page that handles method selection and data entry. Your work shrinks to creating the payment, redirecting the customer and processing the result. This suits teams that want to launch quickly or keep payment screens outside their own codebase.

| Consideration | API (host-to-host) | Hosted Payment Page |

| --- | --- | --- |

| Checkout design | Built and owned by you | Provided page |

| Development effort | Higher | Lower |

| Control over screens | Full | Limited to configuration |

| Status handling | Postbacks and webhooks | Postbacks and webhooks |

Our integration documentation explains both options in more detail. Whichever you pick, the status logic described in the next section applies.

Wallet payments are confirmed outside your checkout, so your system needs a dependable way to learn the result. Payment Gateway Africa sends payment status to the merchant through postbacks and webhooks.

Build your status handling around a few habits:

Treat the gateway's status message as the source of truth for whether an order is paid.

Make your handler idempotent, so a repeated message does not ship an order twice.

Record every status change with a timestamp to support reconciliation and customer service.

Handle pending states explicitly. A payment that has not yet been confirmed is neither a success nor a failure.

Status messages go to you, the merchant. There is no separate notification service that messages buyers on your behalf, so your own emails, SMS or in-app messages should tell customers what happened with their order.

If you are planning payouts, apply the same approach. Track each payout's status independently of pay-ins and settlements.

Before any project goes live, merchants pass a know-your-business (KYB) review. This confirms who you are, what you sell and how your business operates. Preparing documents early shortens the path to your first live transaction.

Expect to provide company registration details, information about owners and directors, a description of your products or services, and your website or platform for review. Additional questions may follow depending on your business model and target markets.

Our AML and KYC requirements page outlines what the review covers and how it fits into onboarding. Local rules can apply to your business independently of the gateway, so it is sensible to check your own obligations in Senegal with legal counsel.

Onboarding generally follows four stages: application, KYB review, a test project, and go-live. The test project is where you confirm your status handling and checkout behaviour before real customers pay.

Whether you are comparing options or confirming details with us, these questions help you avoid surprises after launch.

Which local methods are supported in Senegal, and is the list complete? With Payment Gateway Africa, the answer is Wave and Orange Money.

Are payouts available for each method on my project? Confirm this for your specific use case.

When do settlements go out, and how should I interpret that timing? We dispatch them same-day (T+0). That marks the moment we release funds, while bank posting times vary on the receiving side.

How will my backend learn the result of each payment? Ask about postbacks, webhooks and retry behaviour.

What does it cost to add methods later? Existing Payment Gateway Africa merchants can activate additional supported payment methods without any connection surcharge, and adding more methods leaves their connection price unaffected.

What will my quote depend on? Review our pricing approach to see which factors shape a proposal.

Clear written answers to these questions make internal sign-off easier and give your finance and engineering teams the same picture.

A staged rollout keeps risk low and gives you time to learn how Senegalese customers use your checkout.

Step one: confirm scope. Decide whether you need pay-ins only, or pay-ins plus payouts, and whether you will start with both Wave and Orange Money.

Step two: choose your connection. Pick the API for full control or the Hosted Payment Page for speed.

Step three: complete KYB. Gather company documents and answer review questions promptly.

Step four: test thoroughly. Use the test project to check success, failure and pending states, and confirm your order logic responds correctly to each.

Step five: go live and monitor. Watch status messages, settlement records and customer support tickets closely in the first weeks.

Step six: expand. Once Senegal is stable, consider neighbouring XOF markets. Mali uses the same currency and adds Moov Money alongside Wave and Orange Money. For existing merchants, activating an already supported method can take up to one day.

Revisit the Wave and Orange Money market overview for Senegal as you plan, and compare it with other markets on our countries page or the mobile money gateway overview.

Senegal rewards merchants who build around local wallets from day one. With Wave and Orange Money in XOF, clear separation of pay-ins, payouts and settlement, and status delivered straight to your backend, you have the components for a dependable checkout.

When you are ready, start your onboarding with Payment Gateway Africa. Tell us about your business, your target markets and how you plan to integrate, and we will guide you through KYB and your test project.