Flutterwave Gateway

Changelog

1. Version 1.0.12 27 Oct 2026

   - Reads its keys whether they are stored as typed or sealed by the store, so a later update can keep gateway keys sealed in the database. A sealed key that can no longer be opened counts as not set, and the gateway refuses the payment instead of sending it.
   - A sealed key that cannot be opened is never sent to the payment provider, even when the store's key-sealing support is missing: the gateway refuses the payment as if the key were not set.
   - Check with gateway now works for Flutterwave on Payment requests. A buyer who paid with Flutterwave and closed the tab before returning to the store is no longer lost: before an unpaid-looking request is closed, Flutterwave is asked whether it was paid, and a paid one is credited. This covers checkouts started after the update.
   - If the store can't record a checkout's reference, the buyer is asked to try again before paying, instead of paying a payment the store couldn't look up later.

2. Version 1.0.11 23 Oct 2026

   - A payment settled by Flutterwave is recorded as paid through Flutterwave, even if the buyer switched the request to another gateway in a second tab first.

3. Version 1.0.10 23 Oct 2026

   - A Flutterwave payment that comes back after its order was already paid or had expired is now recorded as a Flutterwave payment, so it is never mistaken for one made with another gateway.

4. Version 1.0.9 21 Oct 2026

   - Needs kernel 1.1.812 or later, so a payment settled on another gateway never closes this gateway's held row.
   - If a buyer's payment was held while its plugin was off and they then paid the order with a different gateway, that held payment now stays listed as owed back for you to refund, instead of being closed as sorted.
   - When the buyer pays for something the store can't fulfil right now, the buyer now sees 'payment held for review' instead of 'Payment failed – try again', and payments held for review are closed or flagged for refund more reliably once the order is paid.
   - A Flutterwave payment waiting for review is no longer marked as sorted when you settle its request by hand, with coins or through Check with gateway; it stays in review so you can refund it.
   - A Flutterwave payment that comes back after its order was already paid or had expired is now kept for you to refund or review, instead of being lost.
   - Buyers who were paying while you switched Flutterwave off now still have their payment confirmed and their order completed.
   - If a Flutterwave payment arrives while the add-on that fulfils it is switched off, the buyer is no longer shown a false success: the payment is listed for your review, and the listing closes on its own once the order completes.

5. Version 1.0.8 18 Oct 2026

   - When two payments race for one request, the request now records the one that won, and the other is kept for a refund instead of being lost. Needs kernel 1.1.497; on an older kernel it settles as before.

6. Version 1.0.7 18 Oct 2026

7. Version 1.0.6 16 Oct 2026

8. Version 1.0.5 15 Oct 2026