Doocat

Mobile Money Interoperability in Ghana: How GhIPSS MMI Works

Content authorBy DoocatPublished onReading time10 min read
Close-up of hands holding a smartphone displaying a banking app, set in a cozy home office with blurred background elements.

This article maps the four transfer flows supported by Ghana's national mobile money interoperability platform and shows who owns each step of them. It covers transaction direction and the questions to settle before a new connected channel goes live.

Mobile money interoperability basics

Mobile money interoperability means a customer on one platform can move funds to a customer on another without both sides sharing a provider. GhIPSS, a wholly owned subsidiary of the Bank of Ghana incorporated in May 2007, runs the shared switch that makes this possible across participating wallets, with bank accounts and e-zwich cards on the same switch.

The GhIPSS mobile money interoperability service covers four documented functionalities, and they don't all behave the same way. One pulls funds. The others push them. Treating them as a single capability is how operations teams end up with reconciliation breaks they can't explain.

Mobile money interoperability in Ghana went live on May 10, 2018, and the volumes of mobile money interoperability ghana since then are not small.

GhIPSS MMI transfer flows

A clean, modern graphic illustrating the e-zwich card transfer validation process in Ghana's mobile money system, featuring smooth UI cards and charts.

By 2025, the GhIPSS mobile money interoperability platform processed 290.31 million transactions worth GhS 51.60 billion, up 37.80 percent in volume on the prior year. Wallet-to-wallet accounts for the overwhelming majority of that, at 282.95 million transactions. The remaining three flows are smaller in volume but carry most of the operational complexity.

Archie Hesse, who led GhIPSS from 2012 until July 2025, described the pre-switch era plainly in an interview with Oxford Business Group: "The landscape became fragmented, with each telco offering the service only within its network." The switch removed that fragmentation. Each participant needs to know exactly what its own system is doing in each flow, which is why mobile money interoperability deserves a flow-by-flow map.

Each example below uses a hypothetical cedi amount to make the direction unambiguous.

Cross-network wallet transfers

A customer holding a wallet with Provider A sends GH¢150 to a customer on Provider B. She initiates it herself, from her own handset, through her provider's short code or app. GhIPSS instructs customers to dial their existing short code and follow the prompt.

Provider A is the sending institution. It sends a name enquiry through the switch so Provider B can validate the destination wallet and return the registered name, after which the sender confirms before the debit happens. Funds are pushed from her wallet to the destination wallet, and the final status comes back to Provider A, which is the party that must tell the customer what happened.

Bank account to wallet

This is the flow that gets described incorrectly most often. The documented functionality lets mobile money users "debit or pull funds from their bank accounts and credit their wallets or other wallets." A customer with a linked account at a participating bank initiates a GH¢300 pull from her wallet channel, and the bank is the one being debited.

So the initiating channel is the wallet and the source of funds is the bank account, with the destination a wallet that need not be the initiator's own. The bank validates the account and the mandate, then checks the available balance before releasing anything. Calling this flow bank-initiated inside your procedures will send your support team to the wrong system when a customer calls, because the bank's channel logs will show nothing at all.

Bank-to-wallet and wallet-to-bank together accounted for 7 percent and 6 percent of mobile money transaction value respectively in 2024, according to the Bank of Ghana's FinTech sector report. The GhIPSS mobile money interoperability rules govern the switched portion of those volumes, and providers also run non-GhIPSS bank-to-wallet arrangements that the same report counts separately.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Wallet to bank

Now reverse it. A customer initiates GH¢500 from his wallet through his mobile money channel, and the funds land in a bank account at a participating institution. The wallet provider debits the wallet, and the switch routes the credit instruction so the receiving bank can credit the account after validating it.

The customer journey differs from the pull flow in one way that matters for support. Here the wallet provider holds the debit and owns the first explanation, while the bank owns the credit posting. In the account-to-wallet pull, the bank holds the debit even though the customer never touched a banking channel. Mobile money interoperability in Ghana put both directions behind the same menu, which is precisely why your mobile money interoperability ghana scripts need to separate them.

Wallet to e-zwich

The fourth documented flow moves funds from a wallet to an e-zwich card. e-zwich is Ghana's biometric smart card system connecting all financial institutions in the country, and it predates the switch by a decade.

The customer initiates from the wallet channel. The wallet provider sends a validation request for the destination card through the switch, and the e-zwich platform confirms the card and its issuing institution. The funds are pushed to the card after the debit clears. Three systems are involved, so your timeout and status rules have to account for a longer confirmation path than a wallet-to-wallet transfer.

The transfer responsibility matrix

Put the four transaction flows side by side, and the ownership questions become clear. The following reflects direction and GhIPSS mobile money interoperability documentation. Confirm each row against your own participation agreement before publishing it internally.

For a wallet-to-wallet transfer of GH¢150, the receiving wallet provider validates the destination, while the sending wallet provider initiates and sends the transaction and communicates the final status. Both providers retain the record, with the switch holding the routing log. The sending wallet provider takes the first inquiry.

For a bank account-to-wallet transfer of GH¢300, the debited bank validates the destination, with the receiving wallet provider also validating the credit leg. The wallet channel initiates the transaction, and the bank releases the funds. The wallet provider communicates the final status to the customer. The bank keeps the debit record, while the wallet provider keeps the credit record. The wallet provider takes the first inquiry because that is where the customer transacted.

For a wallet-to-bank transfer of GH¢500, the receiving bank validates the destination. The sending wallet provider initiates and sends the transaction and communicates the final status. The wallet provider keeps the debit record, while the bank keeps the credit record. The wallet provider takes the first inquiry.

For a wallet-to-e-zwich transfer of GH¢200, the e-zwich platform and card-issuing institution validate the destination. The sending wallet provider initiates and sends the transaction and communicates the final status. The wallet provider keeps the transaction record, while the issuing institution retains the card balance record. The wallet provider takes the first inquiry.

One pattern runs through every row of mobile money interoperability: the institution that owns the customer's initiating channel owns the first conversation, regardless of which balance actually moved.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Common operational exceptions

GhIPSS publishes the functional scope. Almost everything below the functional layer is set by each participating institution and its scheme agreements, from reference formats to retry windows. Keep that line visible in your runbook, because support agents will otherwise quote implementation behavior as though it were a national rule.

  • Mismatched references. The switch carries its own transaction identifier and each participant generates its own. When a customer quotes the receipt number from her wallet app and your bank operations team searches on the switch reference, both parties conclude the transaction doesn't exist. Agree the mapping before launch.

  • Delayed or missing confirmations. A debit posts and the confirmation message doesn't arrive, so the customer sees money gone with no credit. Your definition of "final" has to be the switch response, since the customer's SMS is institution-dependent in both timing and wording.

  • Duplicate attempts. A customer who sees no confirmation retries twice. Without idempotency keyed on the originating reference, you post the transfer twice and recover it manually.

  • Inconsistent histories. The sending wallet statement and the receiving institution's ledger can describe the same transfer with different timestamps and different status labels, as can the switch log. That's normal. Reconciling on amount and reference with settlement date is what keeps the break list short.

Complaint handling is where these exceptions become regulatory. Under the Bank of Ghana's Consumer Recourse Mechanism Guidelines, a provider must resolve a complaint and present its decision within twenty working days of receipt, with up to ten additional working days where it notifies the complainant of the need for more time. Mobile money interoperability in Ghana does not pause that mobile money interoperability ghana clock while two institutions argue about whose log is authoritative.

The commercial context changed in 2025 too. The 1 percent electronic transfer levy was repealed by the Electronic Transfer Levy (Repeal) Act, 2025, effective April 2, which removed a line item from receipts and dispute calculations that your older support scripts probably still mention. GhIPSS attributed part of the jump in average transaction size on the GhIPSS mobile money interoperability platform that year to the removal.

Questions before implementation

Settle these in writing with your partner institutions and your own product owner. Each one has produced a live incident somewhere.

  1. Which of the four flows are you actually enabling, and which are advertised on your channel but not yet certified?

  2. Which channel initiates each flow, and does your customer-facing copy match the direction of funds?

  3. How is the destination validated, and what name is shown to the customer before confirmation?

  4. What counts as a final status, and what does the customer see while a transfer sits in an indeterminate state?

  5. How long is the timeout on each flow, and what happens to the debit when it expires?

  6. Who authorizes a reversal, within what window, and what evidence does the counterparty require?

  7. What is the reconciliation cycle, and which field is the matching key across all participants?

  8. Is there a shared test environment that covers every flow you plan to launch, and does it cover e-zwich?

  9. Who is the named escalation owner at each institution outside business hours?

  10. Which team answers the customer first, and what does it tell someone whose GH¢500 is in neither balance?

  11. Where do all participants log exceptions so the same case isn't worked twice?

That list is the operational core of mobile money interoperability. Answer it before integration testing and you'll spend the test window confirming behavior. The Payment Systems and Services Act, 2019 (Act 987) sets the licensing and conduct obligations sitting behind every one of these answers, and mobile money interoperability in Ghana is supervised against it.

Mobile money interoperability readiness

Sign off on the GhIPSS mobile money interoperability connection only when the scope and the handoffs are documented and tested. Mobile money interoperability in Ghana rewards precision at a mobile money interoperability ghana launch far more than speed.

Service scope confirmed

Every advertised flow and initiation method matches current GhIPSS documentation and your institution's enabled capabilities. Directionality is verified per flow and partner responsibilities are signed, with the audit evidence filed.

Operations handoffs tested

End-to-end tests cover failures and duplicate attempts, with a named owner at each provider. Monitoring and reconciliation routines are live before production sign-off, together with support scripts and escalation paths.

Doocat builds core and digital banking platforms for banks and fintechs, with integrations into national payment systems and mobile network operators. Book a call with our team to scope your mobile money interoperability connection.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Document each enabled flow as a separate product capability. Record the initiating channel, debit owner, destination validation, final-status rule, reconciliation key, reversal process, and named escalation contacts. This prevents a wallet pull from being handled like a push transfer.

Classify the case by the initiating channel and the balance that was debited, then check the receiving ledger separately. Mobile money interoperability incidents often cross institutional boundaries, so the first support team should preserve both references and route the case using the agreed escalation path.

Yes. The repeal, effective April 2, 2025, removed the levy from applicable receipts and dispute calculations. It doesn't determine other provider charges, so each institution should update customer messages, reconciliation rules, and complaint scripts against its current tariff.

Collect the originating reference, switch reference, amount, currency, timestamps, initiating channel, destination details, and each institution's status response. Store the case under controlled access because account and card identifiers can be sensitive. This record lets participants compare events without relying on a customer’s SMS.

Involve Doocat before integration testing when your scope, partner handoffs, and exception rules still need review. The client can assess the required banking and mobile network connections, then help define the work. Book a call with Doocat to discuss the connection and its operating requirements.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

Two diverse professionals engaged in a friendly discussion over a tablet in a bright, modern office with large windows and blurred coworkers.

Murabaha Financing: Contracts and Examples for African Banks

This article walks through how murabaha financing becomes a working bank product: the transaction sequence and the controls your core system has to enforce. It is written for the teams who have to build the thing and then defend it in an audit.

A mid-aged manager reviews documents at a warm wood desk in a sunlit office, with a monitor displaying analytics in the background.

SACCO Management System: A Buyer’s Guide for Kenyan SACCOs

This article walks through how a Kenyan savings and credit cooperative can define what it actually needs from new software and check vendor claims against evidence before it plans a migration that doesn't break member balances. It ends with a checklist you can score vendors against before any price talk begins.

A business manager discusses loan strategies in a bright office, holding a tablet displaying a banking dashboard, with employees working nearby.

How African MFIs Can Reduce Fraud in Cash Loan Collections

Cash collection fraud shrinks when every repayment carries a unique, device-generated receipt reference tied to one borrower and one loan, and when the officer who collects cash never posts or reconciles it. Add daily handover matching and an independent borrower complaint channel, and most leakage becomes visible within 24 hours instead of months.

A business-casual office worker demonstrates a payment process on a smartphone to a customer in a bright, modern office setting.

Ijara Financing: Asset Leasing Workflows for African Banks

This article walks through how an asset-based lease moves from supplier quotation to contract closure inside a bank, and what each step leaves behind in documents and system records. It is written for the teams that have to build or review that workflow together.