Accepting EcoCash and card payments on your website
How online payments work in Zimbabwe, what a payment gateway does for you, and what to plan before you start taking money online.
By Kuzikode Intelligent Technologies5 November 20264 min read
Customers increasingly expect to pay online: for an order, a booking or an invoice. In Zimbabwe that usually means mobile money such as EcoCash, OneMoney and InnBucks, as well as Visa, Mastercard and Zimswitch cards. This guide explains how it fits together and what to decide before you start.
You need a payment gateway
Your website should never collect card numbers or mobile money PINs itself. A payment gateway (for example Paynow or PesePay) sits between your site and the payment networks. Your site tells the gateway who is paying, how much and for what; the gateway handles the sensitive part and tells your site whether the payment succeeded.
To use a gateway you register a merchant account with it, provide your business details and bank account for settlement, and receive integration keys. The gateway sets your integration live once it is satisfied with your application. Until then you can build and test in its test mode.
How a mobile money payment works
The customer chooses EcoCash or OneMoney on your checkout and enters their phone number.
Your site asks the gateway to start the payment. The customer's phone shows a prompt to approve it and enter their PIN.
The gateway sends your site a status update when the payment is paid, cancelled or failed. Your page can also check the status while the customer waits.
Only when the gateway confirms the payment do you mark the order or invoice as paid and send a receipt.
InnBucks works slightly differently: the customer receives a code (often shown as a QR code) to approve in the InnBucks app.
How a card payment works
For cards, the customer usually enters their details on the gateway's own secure page and is then returned to your site. This keeps card data out of your systems. Some gateways can save a card as a token for faster repeat payments, without your site ever storing the card number.
Things to get right
Trust the confirmation, not the redirect. A customer arriving back on your "thank you" page does not prove they paid. Always wait for the gateway's confirmed status before releasing goods or marking an invoice paid.
Handle duplicates. Gateways can send the same status update more than once. Your system should record each payment once, however many times it hears about it.
Reconcile regularly. Compare what your system recorded with the gateway's reports and your bank statements, so nothing slips through.
Be clear about currency. Show the currency on every price, invoice and receipt, and check which currencies each payment method supports for your account.
Tell customers what to expect. A short message such as "Check your phone and approve the EcoCash prompt" reduces abandoned payments.
Plan for more than one gateway. If your system is built so the gateway can be swapped or added to, you are not stuck if fees, features or availability change.
Fees and settlement
Gateways charge per transaction and settle money to your bank account on their own schedule. Fees and terms differ by gateway and payment method, so compare the current terms from each gateway directly before you choose.
Where to start
If you already invoice customers, the simplest first step is a "Pay online" link on each invoice. If you sell products or bookings, the payment step is built into your checkout. Either way, start in the gateway's test mode, test each payment method you plan to offer, and only then go live.
We integrate Paynow, PesePay, EcoCash, OneMoney, InnBucks and cards into websites and business systems, with reconciliation built in. Tell us about your project if you would like help.