What should a website for West African customers handle: payments, currency and language?

Customers in Kumasi, Lagos and Abidjan reach a checkout page with different expectations about payment, currency and language. A site built for one of those markets can lose buyers in the other two.

Tribal House is a brand and web design studio in Accra. This guide covers the build decisions for a site that sells in Ghana, Nigeria and Côte d'Ivoire, and it follows our hub on how to run a brand across West Africa. Payment details come from Flutterwave's and Paystack's own documentation, which differ in places, and the guide flags each difference.

What must website design for West Africa handle first?

Handle payments, currency and language first, because they decide whether a visitor can buy. Offer the payment methods each country supports, show prices in the local currency, and publish English pages for Ghana and Nigeria and French pages for Côte d'Ivoire. Then make the site fast on phones and meet each country's data protection rules.

Currency and language come from Wikipedia's country articles. Payment methods come from the Flutterwave and Paystack pages named in the sources. Providers add and drop methods, so confirm the current list with the provider before you design the checkout.

Which payment methods can a website accept in Ghana, Nigeria and Côte d'Ivoire?

A West African website can accept cards, mobile money and bank transfers, and the mix changes by country. In provider documentation, Ghana centres on mobile money and cards, Nigeria lists the widest set of bank-based options, and Côte d'Ivoire lists mobile money in CFA francs. Pick methods per country instead of one global checkout.

Cards

Paystack's documentation says card payment channels are available on all Paystack accounts, and Flutterwave's payment methods page lists cards for NGN, GHS and XOF. Cards give you one method across all three countries. They do not cover buyers who prefer to pay from a phone wallet or a bank app.

Mobile money

Flutterwave lists Ghana mobile money on MTN, Telecel and Tigo. For Côte d'Ivoire it lists MTN, Orange Money, Moov and Wave in CFA francs. The customer enters a phone number, then approves the charge on the phone with a PIN. Flutterwave's Ghana page warns that a success status means the charge started, not that the customer paid, so confirm each payment through a webhook and a verify call before you ship an order.

Bank transfer, USSD and bank-based options

Flutterwave's payment methods page lists these for Nigeria: bank transfer, USSD, account debit, internet banking, NQR codes, eNaira and OPay. Paystack's documentation describes Pay with Bank, Pay with Transfer and USSD for Nigeria. A Nigerian checkout therefore lists more options than a Ghanaian one.

Which payment provider covers which country?

Flutterwave documents payment methods in all three countries. Paystack documents mobile money in Ghana and, in its help centre, in Côte d'Ivoire, and bank-based options in Nigeria. The two page sets differ in detail, so ask each provider to confirm coverage for your company's country and your customers' countries.

Paystack's pages disagree on Côte d'Ivoire. Its help article lists Wave, Orange and MTN mobile money for Côte d'Ivoire, yet the article's introduction names Ghana and Kenya, and the older documentation page limits mobile money to businesses in Ghana and Kenya. Flutterwave's pages differ on small details, such as VODAFONE and Telecel for the same Ghana network. Treat both sets as a starting point and verify with the provider.

• Ask where your company must be registered. Providers set rules for the country of the merchant account.
• Ask which currencies settle. A GHS charge, an NGN charge and an XOF charge each settle in their own currency.
• Test each network. Run a test payment on each mobile money network you list.
• Plan a fallback. Offer a second method when a network is down.

How should a website show prices in cedis, naira and CFA francs?

Show each visitor the price in the currency they pay with: GHS in Ghana, NGN in Nigeria and XOF in Côte d'Ivoire. Keep one price list per market on its own page. Label the currency with its code, so a buyer can tell whether 5,000 means cedis, naira or francs.

The CFA franc follows different rules from the other two currencies. Eight UEMOA states share it, the Central Bank of West African States issues it, and it holds a fixed rate of 655.957 francs per euro, according to Wikipedia and the French foreign ministry. A 2019 agreement announced a rename to the eco. Wikipedia describes the eco as a target, with the fifth target date set for July 2027. Store the currency name in a site setting, so a rename needs one edit instead of a rebuild.

Ghana carries a legal point for dollar prices. On 9 October 2025 the Bank of Ghana governor said the Foreign Exchange Act 2006 makes the cedi the sole legal tender, and that quoting prices or invoices in foreign currency, such as US dollars, needs the bank's authorisation. GBC Ghana reported the statement. A Ghana-facing site should price in cedis unless the Bank of Ghana or a lawyer confirms an exception.

• Detect the market by URL, not by guess. Send a visitor to /gh/, /ng/ or /ci/ and keep the currency fixed on that path.
• State what the price includes. Say whether tax, delivery and payment fees sit inside the number.

How do you set up French and English versions with hreflang?

Give each language and country version its own URL, then tell Google how the versions relate with hreflang annotations. Each version lists itself and all other versions, and the links must be reciprocal. Google ignores annotations that do not point back, so check both directions after each release.

Google Search Central lists three URL structures for multi-regional sites. Each has trade-offs.

For most Ghana-based businesses entering two or three markets, a subdirectory keeps one site, one CMS and one team. Use a country-code domain when each country needs a separate company, hosting and legal entity. Google does not recommend URL parameters for this job.

The values follow Google's rule: a language code from ISO 639-1, then an optional region code from ISO 3166-1 Alpha 2. A country code on its own does not work, because Google does not derive a language from it. Google describes small regional variations as a valid reason for separate versions, so a Ghana page and a Nigeria page in English can differ in price and still count as alternates.

1. One language per page. Google reads the language from visible content, so avoid side-by-side translations on one page.
2. Full URLs. Write annotations with the protocol, such as https://example.com/ci/, not a path alone.
3. One method. Choose HTML link tags, HTTP headers or sitemap entries. Google treats the three the same, and using more than one gives no gain.
4. An x-default. Point it at the selector page for visitors whose language matches no version.
5. No automatic redirects. Google advises against redirecting visitors by IP address or browser language, because crawlers may not reach all versions.
6. Visible links. Add a language and market switcher to each page.

How should a site handle slow networks and phone-first browsing?

Design for a phone on a mid-range connection first. DataReportal counts 38.3 million mobile connections in Ghana, 150 million in Nigeria and 46.4 million in Côte d'Ivoire in January 2025. Keep pages light, make buttons large, and test on a real handset, because a fast office connection hides the problems your buyers meet.

Speed varies by network and over time. Ookla data in DataReportal's Nigeria report shows a median mobile download speed of 18.91 Mbps in January 2025, down 7.57 Mbps (28.6%) over the previous twelve months. Internet penetration differs too: 69.9% in Ghana, 45.4% in Nigeria and 39.6% in Côte d'Ivoire. DataReportal warns that some mobile connections carry no internet access.

Google's web.dev sets the Core Web Vitals targets at the 75th percentile of page loads: main content within 2.5 seconds, a response to taps within 200 milliseconds and a layout shift score of 0.1 or less. Measure those numbers on mobile, and follow the sequence in our guide to mobile-first web design for Africa.

• Compress and size images. Serve a small image to a small screen.
• Limit scripts. Remove tracking tags and widgets that do not earn their weight.
• Keep the layout stable. Reserve space for images and embeds so buttons do not jump.

Which data protection regulator applies in each country?

Each country has its own authority. Ghana's Data Protection Commission, Nigeria's Data Protection Commission and Côte d'Ivoire's ARTCI each oversee personal data. A website that collects names, phone numbers or payment details falls inside their scope, so state what you collect, and check registration duties with the regulator or a lawyer.

The official pages say little about thresholds, fees and deadlines, and the Ghana page gives two renewal windows. Do not rely on a summary, including this one. Write a privacy notice for each market in its language, and collect only the data the checkout needs.

What belongs on a build checklist for a West African website?

A build checklist covers market structure, payments, prices, language, speed, legal pages and testing. Work through it in order, because early choices such as URL structure and currency are costly to change after launch. Assign each line to a named owner and a date.

1. Choose the markets and the URL structure. Subdirectory, subdomain or country-code domain.
2. Pick payment providers per country. Confirm coverage in writing.
3. List the payment methods per market. Cards, mobile money networks, bank transfer and USSD where offered.
4. Set one price list per currency. GHS, NGN and XOF, each with its code.
5. Check Ghana price rules. Ask the Bank of Ghana or a lawyer before showing dollar prices.
6. Write the English and French copy. Use a French-language writer for Côte d'Ivoire.
7. Add hreflang. Reciprocal, self-referencing and fully qualified, with an x-default.
8. Build for phones first. Test on real handsets over a mobile connection.
9. Measure Core Web Vitals. Aim for 2.5 seconds, 200 milliseconds and 0.1 at the 75th percentile.
10. Publish privacy and terms pages. One set per market, in its language.
11. Confirm data protection duties. Contact the regulator in each country where you collect data.
12. Test each payment path. Run a live low-value payment on each method and network before launch.

How does Tribal House build a multi-country website?

We build the site, the brand system and the content structure together, so one team owns the market modules. For Brassica Pay, we shipped the positioning, identity assets and a full marketing page built into the brassicagroup.com architecture, so the product launched without a separate stack to maintain. The Brassica Pay project describes the work.

Brand and website projects ship in four to eight weeks, with Loom walkthroughs, a CMS guide and a launch checklist at handover. Engagements start from US$6,000, and a project sprint from US$2,500 covers one defined outcome such as a landing page. Ghana-based clients receive a cedi quote. Bugs found in the 30 to 60 day support window after launch get fixed at no extra cost. See our services and plans, or book a call.