Mobile Money Payment Integration for Ghanaian Websites: A Developer's Guide

The Complete Guide to Mobile Money Payment Integration for Ghana Websites

If you run a website in Ghana and want to accept payments online, mobile money is an important checkout option. The Bank of Ghana reported 85.8 million registered and 26.4 million active mobile money accounts in August 2026. These are account counts, not unique customers, but they demonstrate the scale of the payment channel.

This guide covers everything you need to know about integrating mobile money into your Ghana website: from choosing the right payment gateway to technical integration steps, security requirements, and troubleshooting common issues.

The Mobile Money Landscape in Ghana

Mobile money has transformed financial transactions in Ghana. In August 2026 alone, the Bank of Ghana recorded 1.046 billion transactions worth GHS 518.8 billion. The same report defines an active account as one that transacted at least once during the preceding 90 days and notes that its data may be revised.

Examples of mobile-network payment services in Ghana include:

MTN Mobile Money (MoMo)

MTN MoMo is a widely used mobile money service and is commonly supported by Ghana-focused payment gateways. The Bank of Ghana's September 2026 summary reports market-wide totals, not provider market shares, so businesses should confirm current network coverage directly with each gateway instead of relying on an unsupported percentage.

Telecel Cash (formerly Vodafone Cash)

Following the Telecel Group's acquisition of Vodafone Ghana, the service was rebranded as Telecel Cash. Confirm current gateway support, settlement terms, and customer authorisation requirements before launch.

AT Money (formerly AirtelTigo Money)

AT Money is another network a Ghana-focused checkout may need to support. Confirm current availability with the gateway and test the complete payment, failure, refund, and reconciliation flows.

The practical takeaway is to support the networks your customers use. Gateway coverage changes, so verify the current network list instead of assuming that one integration includes every provider.

Payment Gateway Comparison for Ghana

You do not normally integrate with MTN MoMo, Telecel Cash, or AT Money directly. Instead, you integrate with a payment gateway — a service that acts as the intermediary between your website, the mobile money networks, and your bank account. The gateway handles the complexity of communicating with each network, processing the transaction, and settling funds to your account.

Here is a comprehensive comparison of the payment gateways available for Ghana websites:

Paystack

As of 7 October 2026, Paystack's Ghana pricing page lists 1.95% for both local and international transactions and does not list a GHS 100 cap. Confirm the currently supported mobile money networks, integration methods, settlement schedule, merchant requirements, and refund behaviour in Paystack's live documentation and contract.

Flutterwave

As of 7 October 2026, Flutterwave's Ghana pricing page lists 2.6% for local cards, 2% for wallets and mobile money, and 4.8% for international cards, excluding VAT and other applicable local taxes. Its Ghana onboarding guide distinguishes individual, sole-proprietor, limited-company, NGO, and trust accounts.

Other Gateway Candidates

expressPay, Hubtel, iPay Ghana, and theteller may also be candidates, depending on their current licensing, product availability, and merchant terms. Before recommending any provider, verify it in the Bank of Ghana licensed PSP register, obtain a current written quote, review the API and plugin maintenance history, and test the required networks, refunds, settlements, webhooks, and reconciliation exports.

Integration Methods: Which Approach Suits Your Website?

There are three primary ways to integrate mobile money payments into your Ghana website, ranging from no-code to full custom development.

Method 1: WordPress/WooCommerce Plugins (No Code Required)

If your website runs on WordPress with WooCommerce, a supported gateway plugin is often a lower-code starting point. Setup and approval time vary by provider and plugin. Here is how to set up Paystack as an example:

1. In your WordPress dashboard, navigate to Plugins > Add New.
2. Search for "Paystack WooCommerce" and install the official plugin.
3. Activate the plugin and go to WooCommerce > Settings > Payments.
4. Enable Paystack and enter your Public Key and Secret Key from your Paystack dashboard (Settings > API Keys & Webhooks).
5. Enable the payment channels you want: Card, Mobile Money, Bank Transfer, USSD, QR.
6. Set the gateway title customers see at checkout (e.g., "Pay with Mobile Money or Card").
7. Save changes and test with a small transaction.

Other providers may offer WooCommerce plugins or third-party integrations. Verify that the plugin is current, supported by the provider, compatible with your WooCommerce version, and suitable for every payment method you intend to enable.

Method 2: Hosted Payment Pages (Low Code)

Hosted payment pages redirect the customer to the gateway's secure page to complete payment, then return the browser to your site. They can work with many website stacks that support the required redirect, callback and server-side verification:

1. When a customer clicks "Pay," your server sends a request to the gateway API with transaction details (amount, email, reference).
2. The gateway returns a URL for its hosted payment page.
3. You redirect the customer to this URL.
4. The customer selects their payment method and completes payment on the gateway's page.
5. The gateway redirects the customer back to your callback URL with the transaction status.
6. Your server verifies the transaction via the gateway API and updates the order.

A hosted payment page can reduce the payment data your site handles, but the merchant site, redirect flow, provider due diligence and applicable PCI DSS controls still require protection.

Method 3: Custom API Integration (Full Code)

For more control over the merchant-side experience, integrate the gateway's API directly. The customer may still complete authorisation through a provider-managed page, app, USSD or handset prompt. This approach suits custom applications whose developers can implement the gateway's current API, webhooks and server-side security requirements.

Step-by-Step: Paystack Integration Overview

Using Paystack as one practical example, here is an overview of the integration process for custom websites. Compare current gateway coverage, fees, settlement terms, documentation, and support before choosing a provider.

1. Create Your Paystack Account

Sign up through Paystack's official site and follow its current Ghana onboarding instructions. Required documents and approval timing can vary by account and business type, so confirm the live checklist before applying and use Test Mode while preparing the integration.

2. Obtain Your API Keys

In your Paystack dashboard, navigate to Settings > API Keys & Webhooks. You will find test keys (for development — no real money) and live keys (for production). Each set includes a Public Key (safe for front-end code) and a Secret Key (server-side only — never expose this in client-side code or version control).

3. Initialise a Transaction

Your server sends a POST request to Paystack's initialise endpoint with the transaction details: amount in pesewas (GHS 50 = 5000 pesewas), customer email, and a unique reference. Paystack returns an authorisation URL where the customer completes payment.

4. Handle the Customer Payment

For mobile money, the customer selects a currently supported network such as MTN MoMo, Telecel Cash, or AT Money, enters the requested account details, and follows the network's authorisation prompt. Your server must still verify the final transaction status with the gateway before fulfilling the order.

5. Verify the Transaction

Always verify the transaction server-side by calling Paystack's verify endpoint with the transaction reference. Never trust redirect URL parameters alone — they can be manipulated by malicious users.

6. Set Up Webhooks

Webhooks provide asynchronous updates for the events a gateway documents and can keep your system synchronised when a browser redirect fails. Configure the webhook URL in the dashboard, confirm the current event list, and use the provider's verification or polling method when no webhook covers a final state. Ensure your handler:

• Validates the webhook signature using your Secret Key (HMAC SHA-512).
• Processes the event (updates order status, sends confirmation, triggers fulfilment).
• Returns a 200 HTTP status code to acknowledge receipt.
• Handles duplicate deliveries gracefully (idempotency).

Security Requirements and Compliance

Handling payments on your website carries serious security responsibilities. A breach can cost you customers, money, and your reputation. Our guide on classifying systems by security risk provides broader context on security frameworks.

SSL/TLS Encryption (HTTPS)

Serve the entire website over HTTPS and follow the selected gateway's current TLS requirements. HTTPS encrypts data in transit between the customer's browser and your server. If the site does not yet use HTTPS, ask the hosting provider which certificate and renewal process are included. Faciotech provides free Let's Encrypt certificates with its hosting plans and enables automatic renewal, subject to successful DNS and domain validation.

PCI DSS Compliance

The Payment Card Industry Data Security Standard applies to any business that accepts card payments. A gateway-hosted payment page or properly isolated payment fields may reduce your card-data environment, but SAQ A eligibility depends on meeting every applicable criterion. A custom or merchant-hosted collection flow can create a different and larger validation scope. Confirm the correct scope and validation method with your acquiring bank, payment provider, or a qualified security assessor; an SAQ is a validation questionnaire, not a compliance level.

Data Protection

Ghana's Data Protection Act, 2012 (Act 843) requires you to protect customer personal data. If your business determines why and how that data is processed, it is a data controller and must register with the Data Protection Commission as required by the Act. Do not store card numbers, CVVs or mobile money PINs unless your validated design and legal obligations expressly require it; encrypt sensitive data, limit access and publish an accurate privacy notice.

Testing Your Payment Integration

Never go live without thorough testing. Use the payment gateway's test or sandbox mode when one is available, and follow its approved live-verification procedure before accepting customer payments.

What to Test

• Successful mobile money payment: Use the test mobile money number provided by your gateway. Verify the order status updates correctly and the customer receives a confirmation.
• Successful card payment: Use a current test card and its matching validation steps from the gateway's official test-payment documentation; do not copy live card data into a test environment.
• Failed/declined payment: Test with designated "fail" numbers. Verify your website shows a clear error message and allows the customer to retry.
• Abandoned payment: Start a payment and close the browser mid-flow. Verify your webhook handler identifies the abandoned transaction correctly.
• Duplicate payment prevention: Attempt to pay for the same order twice. Your system should detect and prevent double-charging.
• Refund processing: Initiate a refund from the gateway dashboard and verify it processes correctly.
• Mobile responsiveness: Test the entire payment flow on an actual mobile device — not just a browser's device emulator. Ensure the payment modal displays correctly on small screens.

Going Live

1. Switch your API keys from test to live in your application configuration.
2. Update your webhook URL to the production endpoint.
3. If the provider permits it, process a small live verification transaction using its documented procedure.
4. Confirm the settlement arrives in your bank account on the expected day.
5. Remove or disable any test/debug logging that might expose sensitive data.

Troubleshooting Common Issues

"Transaction Failed" Without a Clear Reason

A failure can have several causes, including insufficient funds, rejected authorisation, invalid account details, a network timeout, account configuration or a gateway error. Show a neutral message, log the provider response securely, and let the customer retry or choose another method.

Customer Charged but Order Not Updated

This typically happens when the redirect callback fails (the customer closes the browser or the network drops) and the server-side confirmation path is not configured or working. Confirm payment with a verified webhook and/or the gateway's server-side transaction-verification API, depending on the provider's documented flow. Never mark an order paid from the browser redirect alone.

Mobile Money Prompt Not Received

Common causes include an account number that does not match the provider's required format, a device that is offline, delayed authorisation, or a temporary network or gateway issue. Validate the format against the selected gateway's current documentation and provide a safe retry path.

Webhook Signature Validation Failing

Verify you are using the correct Secret Key (live vs test) and that your signature validation logic matches the gateway's specification. Paystack uses HMAC SHA-512 — ensure your hashing function matches exactly.

Currency Mismatch Errors

Ensure the currency code in your API request matches your account's settlement currency. For Ghana, use "GHS". Sending "USD" or "NGN" will cause the transaction to fail unless your account is configured for multi-currency.

Choosing the Right Gateway for Your Business

A defensible gateway choice depends on the business rather than a universal ranking. Compare the current total cost for your payment mix, mobile money and card coverage, account eligibility, settlement timing, refund and dispute handling, reconciliation exports, recurring-payment needs, plugin maintenance, API quality, support, and licensing status. Ask shortlisted providers for written terms and test the complete live-like workflow in a sandbox before signing or launching.

Frequently Asked Questions

How long does it take to set up mobile money payments on my website?

A supported WooCommerce plugin can make the technical setup relatively quick, but account verification and approval times vary by provider, account type, and submitted documents. Confirm the current onboarding timeline directly with the provider and use its test environment while verification is pending.

Do I need a business registration to accept mobile money payments?

Requirements vary by provider and account type. For example, Flutterwave's Ghana onboarding guide lists an individual account as well as registered sole-proprietor and company accounts. If you register a business name, the Office of the Registrar of Companies lists a GHS 130 initial registration fee in its 2026 schedule. For tax identification, an individual uses a Ghana Card PIN as the person's TIN, while a company or organisation uses a GRA-issued organisational TIN. Confirm the exact onboarding and regulatory requirements before applying.

What happens if a mobile money transaction fails mid-way?

If authorisation appears to succeed but confirmation is delayed, keep the order pending and verify status through the gateway's documented server-side method. Reversal and review procedures vary by provider; use the transaction reference and follow the provider's support and reconciliation process.

Can I accept international payments alongside mobile money?

Some gateways can present international card payments alongside local methods, subject to account approval and configuration. As of 7 October 2026, Paystack's Ghana pricing page lists 1.95% for international transactions, while Flutterwave's Ghana pricing page lists 4.8% for international cards; check the live pricing pages, taxes, supported cards, settlement currency, and chargeback terms before launch.

Is it safe to accept mobile money payments on my website?

Online mobile money payments can be implemented more safely by using a reputable payment gateway and applying HTTPS, server-side transaction verification, webhook signature validation and data minimisation. Verify a provider's current status in the Bank of Ghana's licensed PSP register before contracting or going live.

What are the tax implications of accepting online payments?

Online payments are subject to the same tax rules as other business revenue in Ghana, and income from online sales must be included in the appropriate tax returns. Under the VAT rules effective from 1 January 2026, the registration threshold for businesses that deal in goods is GHS 750,000. VAT is 15%, with NHIL at 2.5% and GETFund Levy at 2.5%, for a total effective rate of 20% on taxable supplies; the COVID-19 Health Recovery Levy and VAT Flat Rate Scheme have been abolished. Other activities can be treated differently, so confirm your obligations with the Ghana Revenue Authority or a qualified tax adviser.

Get Expert Payment Integration Support

Mobile money can make checkout more useful when it matches your customers' needs, but coverage, reliability, fees and customer adoption vary by provider and market. Build the flow carefully and test it before launch.

Faciotech can scope mobile money integrations for WooCommerce and custom web applications. The agreed scope should identify the provider, customer flow, security responsibilities, testing, reconciliation and ongoing support.

Contact Faciotech to discuss WooCommerce plugin configuration or a custom API integration. We will confirm the provider, technical scope, testing, responsibilities, timeline and support before work begins.