Coast Systems

Review of Selected Money Apps in Côte d’Ivoire

A user’s review of selected money apps I actually use in Côte d’Ivoire. The apps covered are a representative sample of Mobile Money, Microfinance, and Banking players. This is not a complete market survey. It is a record of the things I have noticed that work, the things that still get in the way, and the small changes that would make these apps genuinely more useful.
NOTE
Note
This is a living review based on personal use. It is not an exhaustive audit, and fees and features change. There is no perfect winner here, but Djamo currently stands out for accounting. Some apps are good at one aspect and bad in another.

The good news: PI-SPI is finally here

The arrival of the PI-SPI system is genuinely good news. It does not replace the separate provider apps: each provider still has its own app, its own balance, its own way of sending money, and its own QR code (regrettably). PI-SPI adds another layer that provides yet another QR code and a means for the players to communicate with one another. The underlying app incompatibility problem is still there. But the practical consequence is important: before PI-SPI, if the person you wanted to pay used a different service, you could not complete the purchase at all. You had to withdraw cash and pay in person.

With PI-SPI interoperability in place, money can now move between providers that used to be isolated. That is a major step forward. I have a feeling the BCEAO and the government had to force the mobile operators to implement this, but at least they deserve credit for getting there.

One important limit is easy to miss: each wallet provider that participates in PI-SPI does not allow PI-SPI transfers between its own clients. In other words, an Orange customer sending to another Orange customer must use Orange Money; PI-SPI is used for transfers across providers. PI-SPI appears to have permitted this as a concession to the providers. This explains why the receipt story has to be split into two separate tracks.

Interoperability is also not the finish line. Once money can move, the big question here is whether the record of that movement is useful. That is where the apps (including PI-SPI) still have work to do.

The most frustrating part: receipts are second-class citizens

Receipts are not decorative. They are the evidence you need for budgeting, accounting, reimbursements, disputes, and tax records. Yet in several apps, saving a receipt still feels like an afterthought.

Image-only receipts are unacceptable for personal accounting

Two providers in this review, Wave and Ecobank, offer a downloadable native receipt as a PNG image. Wave offers no PDF or text option, and in the PI-SPI flow there is no downloadable receipt at all. A PNG is better than nothing in the native case, but it requires error-prone OCR to process. Images are not easy to search, reconcile, copy into a spreadsheet, or archive efficiently. OCR might rescue the text, but the user should not have to run a document-processing pipeline just to save a payment record. Ecobank does offer a text format, but who in the banking industry decided that a web image format is acceptable for a financial document?

PDF and text exports are the right direction

With the exception of Wave and Ecobank, the other providers on my list offer PDF receipts in the native flow. Both Wave and Orange have a disabled download feature in the PI-SPI flow. Was this intentional, lazy, or a conclusion that people do not need to track their spending?

PDF keeps a human-readable layout, while text is easy to index, parse, and paste into other accounting tools. Giving the user that choice is a small feature with a large practical payoff.

This should be the norm, even an absolute requirement. In addition, CSV or XML export would also be appropriate.

The main mobile operators (Orange and Wave, with MTN to be determined) provide no functional download or share button in their PI-SPI implementation. This is unacceptable. It should in fact be a non-negotiable requirement from the BCEAO. The exceptions here from my testing are Moov, Djamo, and Corismoney. Note that Corismoney (a bank, not a mobile operator) does provide the functionality to download and save the PDF to a location of the user’s choice. Moov Money also provides a 'save' button, but it saves to a deeply obscure location in the Android file system, and then it’s up to the user to retrieve it. There is also a 'share' button that is disabled. The functionality here is a real mixed bag between apps and operators.

Native transfers and PI-SPI transfers are not the same receipt

The native receipt has existed for years and belongs to the provider’s transfer flow. The PI-SPI receipt is a newer artifact from the interoperability flow. They are completely different documents, with different formats, fields, and filenames. Why has there never been collaboration among providers on a standard format? And why is there still no standardized format, not only across the legacy receipts from Orange, Moov, MTN, and Wave, but even more so across the new PI-SPI receipts?

No automatic archive

None of the apps provide a mechanism to save all receipts automatically. The user has to remember to export each receipt after each transaction. That is not a reasonable expectation. People are busy, phones get lost, and financial records should not depend on perfect manual discipline.

At minimum, an app should be able to keep a local receipt archive and let the user export it in one action. (Moov does this, but it is not user friendly to access)

No sync to online storage

None of the apps provide a mechanism to sync data to online storage providers. This leaves the user with a fragile, phone-local record.

If the receipts were at least saved in a predictable, user-accessible folder on the phone, a secondary app could sync them to a cloud service. But when receipts live inside app-private storage, even that workaround is impossible. A 'share all receipts' button, a user-selected export folder, or direct integration with a storage provider would solve this problem.

Filename collisions make a simple task error-prone

Some apps reuse the same filename when saving a receipt. The user is then forced to invent a date, description, or sequence number just to keep the file from overwriting an earlier one. This is tedious and easy to get wrong.

A useful default would be predictable and unique, for example:

YYYY-MM-DD_HHMM_{provider}_{transaction-type}_{counterparty}_{amount}_{reference}.{ext}

The exact format matters less than the principle: the app should generate a unique name automatically, and it should never silently overwrite an earlier receipt.

The missing payee name or transaction description is the biggest omission

The most frustrating omission, and the one I find hardest to excuse, is common, it seems, to every provider’s receipt (including PI-SPI): the payee name is missing. In the application itself, the wallet usually displays the merchant or recipient name while the payment is being made. The receipt then reduces the same transaction to a phone number or an account ID.

At small scale this is annoying. At scale it makes accounting impossible. A month with a hundred transactions becomes a list of phone numbers; reconstructing the payee or merchant is impossible. In the case of Ecobank, which provides a CSV statement download (in addition to PNG and TXT receipts), this also becomes problematic, as numerous statement transactions cannot be classified. The information was available at the moment of payment, so there is no valid technical reason for it to disappear from the record.

An exception here seems to be Nafolo. The Nafolo app has a 'motif' field that seems to hold a transaction description. It remains to be seen whether a future PI-SPI receipt will include it. In the meantime, Nafolo cannot be used to pay merchants directly. Not even CIE or Sodeci payments are supported.

Djamo is the closest thing to a clear winner

For accounting, Djamo is currently the best app I have tested. It is the only one that offers a transaction statement download for a custom period, the last month, the last three months, or the last six months, in PDF format, with transaction descriptions. That is exactly the kind of export the other providers should offer.

The only real downside at this point is that Djamo is not readily accepted by merchants. If and when merchants adopt PI-SPI codes and aliases, Djamo will be the most accounting-friendly app in this review.

The missing operator name is the second biggest omission

None of the operators, including PI-SPI, include an 'operator' field in the receipt data. Fortunately, some operators put their logo on the native PDF receipt, which can be read or extracted, and keeping a given operator’s receipts together is another workaround. But this information is obviously available when the transaction is generated, so it should be the first item on the receipt. Notably, Corisbank provides an 'Institution' field, but it is not Corisbank; it is the transaction’s correspondent institution. Nafolo also shows 'Réseau: Wave' for a transfer from Wave.

What a useful receipt should contain

A receipt that can actually be used for reconciliation should include, at a minimum:

  • operator producing the transaction receipt

  • date and time of the transaction

  • transaction ID or reference number

  • sender and recipient names, not only phone numbers or account IDs

  • amount and currency

  • fees charged, shown separately

  • resulting balance

  • transaction type and channel

  • status, especially for pending or failed transactions

This is not exotic data. It is the information the provider already has. The problem is that it is not always exported in a form the user can keep and use.

What I could test so far

The table below is a working summary, not a final scorecard. Cells marked TBD have not yet been verified against the current app version. Cells marked No mean I did not find the feature in the apps I tested.

The review concentrates on money wallet providers. Ecobank is the one exception: it is included as a sample bank provider of PI-SPI transfers, so that the wallet experience can be compared with a bank flow.

Receipt formats by operator

Operator Native receipt format(s) PI-SPI format(s) Auto-save all receipts Cloud/online sync Unique filenames Notes

Orange

PDF

Not available (error when attempting to share)

No

No

TBD

MTN

PDF

TBD

No

No

TBD

—

Moov

PDF

PDF

No

No

TBD

—

Djamo

PDF

PDF

No

No

Yes

The only app tested with a custom, last month, last 3 months, or last 6 months PDF statement with transaction descriptions. Not widely accepted by merchants yet.

Nafolo

PDF

Not implemented yet

No

No

TBD

Provides a 'Nafolo' title on the native PDF and a 'motif' field with a transaction description.

Ecobank

PNG + TXT

Not available

No

No

No (image.png)

Included as the one bank sample in this wallet review.

Corismoney

PDF

PDF

No

No

Yes

The PI-SPI receipt logo identifies Corisbank.

Wave

PNG only

Not available (download icon greyed out)

No

No

Yes

Image-only export is the least usable receipt format in this group.

I will update the table as I complete a consistent test pass on each app and each transfer flow. The important point is not the exact ranking today. It is that the same basic questions should be asked of every provider.

What I would like providers to do next

The good news is that most of these improvements are not exotic. They are basic product decisions.

  1. Export every receipt automatically. Let the user choose a folder or share target, then save each receipt without asking again.

  2. Offer PDF and text, never images. Machine-readable formats should be the default for records. PDF is both machine- and human-readable.

  3. Generate unique, predictable filenames. Include the date, time, amount, transaction type, and reference. Never overwrite silently.

  4. Put the payee name on every receipt. If the app can display the merchant or recipient name during payment, it can preserve that name on the receipt.

  5. Put the generating operator name on every receipt. This should be a given.

  6. Support the operating system’s share function and file picker. This gives users a path to their own cloud storage without the provider having to build a custom integration.

  7. Provide a history export in CSV or JSON. This is essential for accounting, budgeting, and anyone managing more than a handful of transactions.

The bottom line

PI-SPI is real progress, and it deserves to be recognised. Money can now move between providers in ways that were not possible before.

But moving money is only half the job. The other half is giving people a usable record of what happened. Receipts, exports, filenames, and sync are not glamorous features. They are the difference between an app that looks modern and an app that is actually useful. Djamo already shows how good that record can be when a provider takes statements seriously.

The providers that treat financial records as a first-class part of the product will earn trust. The ones that keep treating receipts as a nuisance will keep forcing their users to build workarounds and lose their respect and loyalty.