Fosia Pay Lite – PawaPay Mobile Money for WooCommerce
| 开发者 | fosialtd |
|---|---|
| 更新时间 | 2026年11月1日 01:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- WooCommerce payment gateway for the classic checkout and the block-based Cart & Checkout
- Works in the countries and with the operators enabled on your PawaPay account (MTN MoMo, Airtel Money, Orange Money, M-Pesa, Moov, Vodacom and more)
- PawaPay hosted payment page: the plugin never sees or stores Mobile Money PINs
- Automatic conversion from your store currency to the customer's Mobile Money currency, shown at checkout before the customer pays
- Clear return page: paid, "Payment not received yet" (with "Pay now" and "Check again"), failed (with the reason in plain words and "Try again"), or "Confirming your payment"
- Mobile Money is only offered when it can work: hidden without a PawaPay token, with a token PawaPay refused, or for a billing country your PawaPay account does not cover
- Payments re-checked with PawaPay in the background, so a customer who paid and closed the page is confirmed even without a callback
- Amounts follow the decimals and limits set on your PawaPay account
- Payment confirmation you can trust: every PawaPay callback, signed or not, is confirmed by reading the payment from PawaPay with your own token (status, amount and currency) before an order is marked paid
- Guided setup in about 3 minutes once you have your PawaPay API token: the token is tested with PawaPay before it is saved
- Dashboard: setup checklist with a "Test now" button, whether customers see Mobile Money at checkout, volume per currency, success rate and recent payments (with the operator and why an order is unpaid)
- Insights, computed on your site from your own orders: unfinished checkouts at the PawaPay page, failed payments by reason, refunds done by hand
- Sandbox mode for testing before going live
- Compatible with WooCommerce High-Performance Order Storage (HPOS)
- In English and French (more languages through translate.wordpress.org)
- Benin: MTN MoMo, Moov Money
- Burkina Faso: Orange Money, Moov Money
- Cameroon: MTN Mobile Money, Orange Money
- Congo (Brazzaville): MTN MoMo, Airtel Money
- DR Congo: Vodacom M-Pesa, Airtel Money, Orange Money
- Côte d'Ivoire: MTN MoMo, Orange Money, Wave
- Ethiopia: Safaricom M-Pesa
- Gabon: Airtel Money
- Ghana: MTN MoMo, Telecel Cash, AT Money
- Kenya: M-Pesa
- Lesotho: M-Pesa
- Malawi: Airtel Money, TNM Mpamba
- Mozambique: Vodacom M-Pesa, Movitel e-Mola
- Nigeria: MTN MoMo, Airtel
- Rwanda: MTN MoMo, Airtel Money
- Senegal: Orange Money, Wave, Free Money
- Sierra Leone: Orange Money
- Tanzania: Vodacom M-Pesa, Airtel Money, Mixx by Yas, Halopesa
- Uganda: MTN MoMo, Airtel Money
- Zambia: MTN MoMo, Airtel Money, Zamtel Kwacha
- Zimbabwe: EcoCash
- WooCommerce
- A PawaPay merchant account and API token
安装:
- Install and activate WooCommerce.
- Install Fosia Pay Lite from Plugins > Add New, then activate it. The guided setup opens.
- Choose Sandbox (test) or Live, paste your PawaPay API token: it is tested with PawaPay before it is saved.
- Copy the callback URL into your PawaPay Dashboard under System Configuration > Callback URLs (Deposits). Turning on "signed callbacks" there is optional: every callback is confirmed with PawaPay either way.
- In Sandbox, place a small order and pay with a PawaPay test number. Then switch to Live with your Live token.
屏幕截图:
常见问题:
How do I accept MTN MoMo payments on WooCommerce?
Install and activate Fosia Pay Lite, then follow the guided setup: choose Sandbox or Live, paste your PawaPay API token and copy the callback URL into your PawaPay Dashboard. Place a test order in sandbox mode, then switch to Live. Customers choose MTN MoMo (MTN Mobile Money) on the payment page and approve the payment on their phone. MTN MoMo is available in Benin, Cameroon, Congo, Côte d'Ivoire, Ghana, Nigeria, Rwanda, Uganda and Zambia, if it is enabled on your PawaPay account.
Does it work with M-Pesa (MPesa, Mpesa)?
Yes. M-Pesa is supported in Kenya, Tanzania (Vodacom M-Pesa), DR Congo, Mozambique, Lesotho and Ethiopia, if it is enabled on your PawaPay account.
Does it work with Airtel Money?
Yes, in Rwanda, Uganda, Tanzania, Zambia, Malawi, DR Congo, Congo, Gabon and Nigeria, if it is enabled on your PawaPay account.
Does it work with Orange Money?
Yes, in Cameroon, Côte d'Ivoire, Senegal, Burkina Faso, DR Congo and Sierra Leone, if it is enabled on your PawaPay account. Wave, Moov Money and Free Money are supported in West Africa too.
Is Fosia Pay Lite free?
Yes. It is free, with no limit on the number of payments, no licence key and no time limit. Fosia takes no commission on your sales.
Does Fosia Pay Lite take a commission on my sales?
No, never. The only fees are PawaPay's own processing fees.
Is there a limit on the number of payments?
No. Fosia Pay Lite has no payment limit and no time limit.
Do I need a PawaPay account?
Yes. Fosia Pay Lite connects to the PawaPay API to process payments, and the money goes to your own PawaPay merchant account, never through Fosia.
- Sandbox (testing): free, you open it yourself in a few minutes at dashboard.sandbox.pawapay.io, with no documents. Every country and operator is there.
- Live (real payments): PawaPay opens it after checking your business documents, from your Sandbox account (how to start). You then ask PawaPay for the countries and operators you need. The time this takes depends on PawaPay, not on the plugin.
Where do I find PawaPay test phone numbers?
In PawaPay's documentation: Sandbox test numbers. Each operator has numbers that complete, fail or stay in progress, so you can test every case. The guided setup links to it too.
What does the customer see if the payment fails or they come back without paying?
Never "Thank you, your order has been received". The return page reads the payment status from PawaPay before it is shown: "Payment not received yet" with "Pay now" and "Check again", or "Payment failed" with the reason in plain words (for example "The Mobile Money balance was not enough") and "Try again". You see the same on the order, in an order note.
Why is Mobile Money not shown at my checkout?
Fosia Pay Lite hides it when it cannot work, so customers never meet a payment error: no PawaPay token saved yet, a token PawaPay refused in the current mode (Sandbox or Live), or a billing country your PawaPay account does not cover. The Fosia Pay dashboard says which one, and "Test now" checks the token again.
WooCommerce asks my Rwandan customers for a postal code.
That is WooCommerce's address form, not Fosia Pay Lite. You can make the postcode field optional with a small snippet or an address-fields plugin; the payment works either way.
Which countries and operators are supported?
21 African countries: Benin, Burkina Faso, Cameroon, Congo, DR Congo, Côte d'Ivoire, Ethiopia, Gabon, Ghana, Kenya, Lesotho, Malawi, Mozambique, Nigeria, Rwanda, Senegal, Sierra Leone, Tanzania, Uganda, Zambia and Zimbabwe, with MTN MoMo, Airtel Money, Orange Money, M-Pesa, Moov Money, Wave, Telecel Cash, EcoCash and other operators depending on the country. See "Supported countries and Mobile Money operators" above. You can use those enabled on your PawaPay account.
Can my store keep its prices in US dollars or euros?
Yes. The amount is converted to the customer's Mobile Money currency at checkout, at the current exchange rate. Fosia Pay Lite sits next to your other WooCommerce payment methods (cards, PayPal and so on).
Does it work with the WooCommerce block checkout?
Yes. It works with the classic checkout and the block-based Cart & Checkout, and with High-Performance Order Storage (HPOS).
Does the customer stay on my site?
No: the customer is redirected to PawaPay's secure payment page, then back to your store. Fosia Pay Pro offers on-site checkout.
Can I refund from WooCommerce?
Not with Fosia Pay Lite: it cannot send money back through PawaPay. Send the refund from your PawaPay Dashboard, then record it on the order with "Refund" and "Refund manually" so your stock and reports stay right. The order screen explains it. Fosia Pay Pro, a separate plugin, adds refunds from WooCommerce.
Do I need to turn on signed callbacks?
No, it is optional. Every callback, signed or not, is confirmed with PawaPay before an order changes: the plugin reads the payment's real status, amount and currency from PawaPay with your own API token.
Does the plugin send data to Fosia?
Not unless you choose to. The dashboard insights are computed on your site from your own orders and are never sent. The optional "Connect this site to Fosia" (off by default) sends a random installation ID, the plugin, WordPress and PHP versions and the site language once a day; you can disconnect at any time and the record is deleted. When you deactivate the plugin, the "Quick feedback" window sends your answer only if you click "Submit & Deactivate" (your site address and e-mail only if you tick the box). See "External services".
Can I hide the insights and hints?
Yes. The insights card on the Fosia Pay dashboard has a "Hide" link, the hint on order screens has "Don't show again", and the "Mobile Money this month" widget on the WordPress dashboard can be hidden from Screen Options. Hiding them changes nothing else: every Lite feature keeps working. The only mention of Fosia Pay Pro is one plain line at the bottom of the Fosia Pay dashboard.
What happens to my data when I delete the plugin?
Deleting the plugin removes its settings (including your API token) and cached data, and, if the site was connected to Fosia, asks Fosia's server to delete its record. Your orders and their notes are kept.
更新日志:
- Security: the PawaPay API token is now stored encrypted in the database (AES-256-GCM, with a key made from the secret keys of your wp-config.php). A stolen database or backup alone no longer reveals it. Nothing to do: a token saved by an earlier version is encrypted on the next admin page load. If the secret keys of wp-config.php are changed, paste the token again (a notice says so).
- Security: a PawaPay callback is never applied on its signature alone. Every callback, signed or not, is now confirmed by reading the payment from PawaPay with your own API token, and only PawaPay's answer (payment id, amount, currency, status) is applied to the order. A genuinely signed callback for a payment your PawaPay account does not have changes nothing. If PawaPay cannot be reached, the order is left as it is, PawaPay is asked to send the callback again, and the background checks continue (security audit 2026-10-31, H1).
- Security: the saved PawaPay API token is no longer written into the settings page (WooCommerce > Settings > Payments > Fosia Pay Lite). The field stays empty with "Saved: leave empty to keep it"; saving with the field empty keeps the token, pasting a new one replaces it, and "Test Connection" with the field empty tests the saved token.
- Guided setup (shared design kit): the last screen's list keeps each line next to its mark on phones. No change to the steps.
- Fixed: a customer back from PawaPay after a failed or abandoned payment saw "Order received – Thank you". The payment status is now read before the page is shown: "Payment not received yet" (with "Pay now" and "Check again"), "Payment failed" with the reason in plain words and "Try again", or "Confirming your payment…" (the page checks again by itself). "Thank you" only for a paid order.
- Fixed: Mobile Money was offered at checkout when it could not work. It is now hidden without a PawaPay token, with a token PawaPay refused in the current mode, or for a billing country your PawaPay account does not cover (from the last connection test: the checkout never waits for PawaPay). Classic and block checkout.
- Fixed: pressing Enter in the guided setup's token field left the setup without testing the token. Enter now tests it.
- Fixed: a token PawaPay refused replaced the token that worked. Tokens are now tested before they are saved.
- Fixed: the setup's last screen said "is set up" while steps were left; it now says "Almost ready: N steps left", and a skipped step is not ticked.
- Fixed: a failed payment was counted both as an unfinished checkout and as a failed payment.
- Fixed: the dashboard could show "Connection OK" or "last test failed" for a token that had changed since; the test result now belongs to the token it tested.
- Added: the amount in the customer's Mobile Money currency at checkout (for example "about 26,605 RWF" for a $18 order), with the operators of their country and what happens next.
- Added: payments are re-checked with PawaPay in the background for a few hours, so a customer who paid and closed the page is confirmed even when no callback arrives.
- Added: "No PawaPay account yet?" in the guided setup and on the dashboard, with the Sandbox sign-up, the Live onboarding and the Sandbox test numbers pages.
- Added: "Test now" on the dashboard, and a line saying whether customers see Mobile Money at checkout and why not.
- Added: the token is tested as soon as you save the settings (unless you just tested it), and the result is shown on the same page: a wrong token is hidden from customers at once.
- Added: French shipped with the plugin (used until a translate.wordpress.org language pack exists for your site). The checkout title and description saved in English by earlier versions follow the site language.
- Changed: the countries and operators match PawaPay's own list (21 countries, 43 Mobile Money networks, checked on 30 October): Zimbabwe (EcoCash) and Wave added; Liberia, Mali and Moov Money in Côte d'Ivoire, which PawaPay does not serve, removed.
- Changed: clearer messages (no "401"), a warning when the callback address is local or http://, readable operator names ("MTN MoMo (Rwanda)") and why an order is unpaid in "Recent activity", order notes when the customer comes back without paying, a factual refund explanation, better contrast and phone layout, the new Fosia Pay film in the guided setup. The deactivation window no longer offers "too expensive" for this free plugin.
- Security: a payment result sent to your callback URL is never applied on its own, even when PawaPay's signature is valid. The plugin always asks PawaPay for the payment's status with your own API token, so a payment made on another PawaPay account can never mark one of your orders paid.
- Added: a guided setup that opens once, right after you activate the plugin (never on bulk activation): Welcome (what Fosia Pay Lite does, the video, which loads from YouTube only when you press play), Mode (Sandbox or Live), PawaPay token (saved and tested), Confirmations (the callback URL with a Copy button), Done (what is set up, next step, help links). "Exit guided setup" on every step saves what you entered; "Resume setup" stays on the FosiaPay dashboard until it is finished. Phone-friendly and keyboard-friendly.
- Added: a short "Quick feedback" window when you deactivate the plugin, with a link to support. Optional: nothing is sent on "Skip & Deactivate"; see "External services" for what "Submit & Deactivate" sends.
- Fixed: the "Test Connection" button in the gateway settings always answered "Request failed (400)", because WooCommerce does not load payment gateways during AJAX requests. The check is now registered when the plugin loads. The "Don't show again" link on the refund notice had the same problem and is fixed too.
- Added: "Insights" on the FosiaPay dashboard, computed on your site from your own orders (nothing is sent): this month's unfinished checkouts at the PawaPay page, failed payments by reason and refunds done by hand, each with a daily trend. Can be hidden.
- Added: failed payments now keep PawaPay's failure code on the order, so the dashboard can group them by reason.
- Added: on a Mobile Money order that failed or was refunded by hand, a one-line hint in the order details, with "Don't show again".
- Added: a "Mobile Money this month" widget on the WordPress dashboard (paid orders, unfinished checkouts, failed payments). Hide it from Screen Options.
- Added: optional "Connect this site to Fosia", off by default. Once you agree, a random installation ID, the plugin, WordPress and PHP versions and the site language are sent once a day; "Disconnect" (or deleting the plugin) deletes the record. See "External services".
- Changed: the refund notice on the order screen is no longer shown once the order has a refund.
- Added: a setup checklist at the top of the FosiaPay dashboard (turn on the gateway, add the PawaPay token, test the connection, paste the callback URL with a Copy button, first payment), with Sandbox/Live shown. Once everything is done it shrinks to a one-line status (connection tested, last callback received).
- Changed: no "Upgrade to Pro" page or menu item any more, and no Pro mention in notices or order hints; one plain line at the bottom of the FosiaPay dashboard says what the separate Pro plugin adds.
- Changed: the dashboard shows "—" instead of "0%" success rate when there is no transaction yet, splits transactions into paid / pending / failed, and the empty activity card links to "All time".
- Changed: no more monthly payment limit. Fosia Pay Lite is free with unlimited payments.
- Fixed: payments were never confirmed when PawaPay's "signed callbacks" option was off. Unsigned callbacks are now checked with PawaPay (deposit status) before an order is marked paid, with abuse limits. The "Webhook Secret" setting was removed (PawaPay has no such secret).
- Fixed: signed callbacks could never be verified because WordPress adds slashes to request headers.
- Fixed: a payment page rejected by PawaPay (HTTP 200, status REJECTED) showed "Payment Error: Unknown"; the customer now gets a clear message and the reason is added to the order notes. A timeout or PawaPay server error is checked instead of being treated as a failure.
- Fixed: amounts now follow the decimals and limits of your PawaPay account (amounts like "1500.00" were refused), and the order text sent to PawaPay respects its format.
- Changed: the customer types their Mobile Money number on PawaPay's page and may pay from any number. Optional setting to pre-fill and lock it to the billing phone (validated by PawaPay).
- Changed: the confirmation page checks the payment status when the customer comes back from PawaPay.
- Changed: PawaPay v2 public key endpoint; operator read from the v2 callback.
- Changed: logs go to WooCommerce > Status > Logs, without phone numbers or request bodies; new "Debug log" setting.
- Changed: the "Upgrade to Pro" page no longer downloads prices from pay.fosiarw.com; admin notices are limited to the relevant screens and can be dismissed.
- Changed: all texts are translatable; deleting the plugin removes its settings.
- Fixed: orders stay "Pending payment" until PawaPay confirms payment.
- Fixed: a late "failed" callback could mark an already-paid order as failed.
- Fixed: a completed payment with a different amount or currency now puts the order on hold.
- Security: stricter callback signature checks.
- Fixed: currency conversion rounding, dashboard totals per currency.
- Added: refunds notice on order screens. Fixed: checkout is blocked instead of under-charging when exchange rates are unavailable.
- Initial release.