Marupurupu Checkout for M-Pesa

Changelog

1.6.3 – 2026-09-24

• Fixed: The M-Pesa Transactions and Reports pages logged PHP 8.1 “Passing null to number_format()” deprecations on a store with no transactions yet.
• Fixed: If the plugin was activated while WooCommerce was inactive, its transactions table was never created. The activation hook is now registered before the WooCommerce check, and a missing table is created on the next load once WooCommerce is active. The “requires WooCommerce” notice is now translatable, and network-activated WooCommerce is recognised. The plugin header now declares Requires Plugins: woocommerce.
• Fixed: A failed payment attempt on the block-based checkout now shows the gateway’s own message instead of a generic error (the gateway returned fail, which WooCommerce Blocks does not recognise; it now returns failure).
• Changed: If the gateway is enabled but its credentials, shortcode, till number or passkey are not filled in, a payment attempt now stops with a friendly message instead of contacting Safaricom with empty credentials and showing “Failed to get access token”.
• Changed: “Test M-Pesa Connection” now also lists any of Business Shortcode, Till Number or Passkey that is still empty, instead of reporting success when only the Consumer Key/Secret were checked.
• Fixed: The Transactions list no longer shows a “View Order” button (and no longer logs a PHP deprecation) for transactions whose order has been deleted. Button/placeholder text inside HTML attributes is now escaped as attribute text, and the plugin-list “Settings” link is translatable.
• Changed: The order-received page’s payment-status script is fully translatable, no longer writes debug output to the browser console, and inserts messages as plain text rather than HTML.
• Security: CSV exports (transactions and reports) now prefix any text cell starting with =, +, - or @ so spreadsheet programs cannot run it as a formula.
• Changed: The usage-statistics opt-in no longer describes (or attempts) an “activation” event, which never fired. Only the opt-in “deactivation” event remains, and the readme now says exactly what it contains.
• Changed: WC tested up to raised to 11.1; the amount shown on the order-received page is escaped.
• Fixed: The transactions table definition now uses the exact CREATE TABLE form that WordPress’s dbDelta() expects (it previously read IF NOT EXISTS as the table name, so future column changes could never be applied).
• Changed: Author URI now points to the author’s WordPress.org profile.

1.6.2 – 2026-09-22

• Fixed: On admin pages, activating the plugin with opt-in telemetry enabled could trigger a WordPress “translation loading triggered too early” notice. The telemetry check was reading the gateway’s settings before WordPress had finished its own startup sequence, which also forced the gateway itself to load earlier than it should have; both now wait until WordPress is ready. No setting, saved credential, or behavior changes as a result.

1.6.1 – 2026-09-19

• Changed: The plugin’s display name is now “Marupurupu Checkout for M-Pesa” (the “and WooCommerce” suffix was removed), following WordPress.org Plugin Review Team feedback that “WooCommerce” is a restricted term in plugin names. The slug, text domain, settings, saved credentials, orders and the Safaricom callback URL are all unchanged. No functional change.
• Removed: Unused internal feature-flag code that was never connected to anything. Every feature remains available to everyone, as before.
• Changed: One more admin-screen check now sanitizes the section query argument before comparing it.

1.6.0 – 2026-09-19

• Changed: Unique naming prefix. Every class, function, constant, option, transient, scheduled event, hook, AJAX action, script handle and admin menu slug the plugin registers now uses the prefix marupurupu_ / Marupurupu_ / MARUPURUPU_ instead of the generic mpesa (which could collide with other M-Pesa plugins). The custom transactions table is now {prefix}marupurupu_transactions.
• Added: Automatic one-time data migration. On the first request after updating, data stored under the old names is moved across: the transactions table is renamed (a single atomic RENAME TABLE; no rows are copied or lost), saved options and dismissed notices are carried over, and leftover scheduled events are cleared. Your gateway settings, saved credentials and payment history are unchanged, and no action is needed. The migration retries by itself if it cannot finish, and never overwrites newer data.
• Unchanged on purpose: the payment method id (mpesa_till), your saved gateway settings, and the Safaricom callback URL (/wc-api/wc_mpesa_till_callback/) — orders, settings and Safaricom callbacks depend on them.
• Added: The phone number is now also validated again on the server at the start of payment processing, before any request is made to Safaricom (whether WooCommerce’s block checkout runs the classic field validation has varied between WooCommerce versions, so this makes the check independent of it). A trailing newline is no longer accepted as part of a phone number.
• Removed: The one-time credential-reset routine from the 2026-08 encryption upgrade (every existing install has already been through it; it could only ever cause harm on a fresh one).
• Added: A unit-test suite (composer test) covering credential encryption, the payment webhook, the STK Push request, the migration and the order-state guard.

1.5.6 – 2026-09-19

• Fixed: Block-based checkout could not collect a phone number. The block checkout component only displayed the payment description; the phone-number field, its validation and the code that submits it with the order had been lost in an earlier source-tree consolidation, so paying with M-Pesa on the WooCommerce Cart & Checkout blocks could not work. Restored. Classic checkout was never affected.
• Added: Declares WooCommerce Cart & Checkout blocks compatibility (cart_checkout_blocks), so WooCommerce no longer lists the gateway as incompatible with block checkout.
• Fixed: Readme said Paybill numbers were supported; the plugin supports Till (Buy Goods) only. Corrected, along with the minimum WordPress version (5.3), the Support section (no documentation files ship with the plugin) and the telemetry opt-out description.
• Added: “External services” section in the readme documenting the Safaricom Daraja API and the optional usage-statistics collector — what is sent, when, and links to their terms and privacy policies.
• Removed: config-sample.php, which described a constants-based credential mechanism that the plugin never implemented. Credentials are entered on the gateway settings screen and stored encrypted.

1.5.5 – 2026-09-18

• Changed: Renamed to “Marupurupu Checkout for M-Pesa” (slug, folder, main file, and text domain marupurupu-checkout-for-mpesa), following WordPress.org Plugin Review Team feedback that the previous name led with a third-party trademark. “Marupurupu” is a Swahili word meaning “allowances”. No functional change: internal identifiers, the database table (wp_mpesa_till_transactions), the option keys, and the Daraja callback URL (/wc-api/wc_mpesa_till_callback/) are all unchanged. Existing installs need a manual reinstall to pick up the new folder name (WordPress cannot rename an installed plugin’s folder in an update); stored settings are unaffected.
• Changed: “Not affiliated” disclaimer wording made explicit in the plugin description.
• Changed: Plugin URI and the readme’s source-code link now point to the renamed public repository, github.com/marto-karanja/marupurupu-checkout-for-mpesa (the previous repository name led with a third-party trademark).

1.5.4 – 2026-09-18

• Fixed: On the gateway settings page, the “Change” button for an already-saved Consumer Key/Secret/Passkey did nothing and there was no field to type a new value into, so saved credentials could not be replaced from the settings screen. Credentials can be changed again.
• Fixed: A stale daily “clean old logs” scheduled task, left behind by older versions for a function that no longer exists, could raise a fatal error on PHP 8 each time WordPress cron ran it. It is now unscheduled.
• Fixed: Bulk “Export to CSV” on the M-Pesa Transactions page sent its download headers after the page had already started rendering, so the file could not be delivered cleanly. It now runs before any output.
• Fixed: The transactions page stylesheet (admin.css) was referenced but not shipped, so the page’s styles came only from an inline block. It is now a real, enqueued stylesheet.
• Fixed: The customer-facing “retry payment” and “already paid? enter your code” actions could be used on an order that was already paid (overwriting its confirmed M-Pesa receipt and moving it back to on-hold) or on an order placed with a different payment method. Both now only act on unpaid orders placed with this gateway.
• Fixed: The retry-payment form on the thank-you page could re-appear after a payment succeeded within the first 2 minutes.
• Fixed: Blocks-checkout script now uses the plugin version as its cache-busting version, instead of a hardcoded 1.0.0.
• Security: Safaricom callback data is now sanitized (sanitize_text_field) before it is logged, stored, or shown in order notes; nonces are sanitized before verification; the callback secret is sanitized before comparison; the bulk-export IN (...) list now goes through $wpdb->prepare().
• Changed: All inline <script>/<style> blocks and onclick handlers moved to properly enqueued files (wp_enqueue_script/wp_enqueue_style, with report data passed via wp_localize_script).
• Changed: Late output escaping added where WooCommerce/WordPress return pre-built HTML (wc_price, paginate_links, wpautop), and wp_die() messages now use esc_html__().
• Changed: Bundled Chart.js updated from 3.9.1 to 4.5.1 (see Credits).
• Removed: Unused mpesa-blocks-improved.js (never loaded by the plugin).

1.5.3 – 2026-09-09

• Fixed: Plugin URI and Author URI in the plugin header were identical (https://billtoolbox.com) — flagged during WordPress.org submission review (both must be different, or one omitted). Plugin URI now points to the public GitHub source; Author URI stays https://billtoolbox.com.

1.5.2 – 2026-09-09

• Changed: Slug, folder, main file, and text domain renamed from mpesa-till-gateway to mpesa-payment-gateway, matching the v1.5.1 display-name change and made ahead of first WordPress.org submission (self-service slug changes go away once review starts). No functional change — internal identifiers, the database table (wp_mpesa_till_transactions), the WC_Mpesa_Till_Gateway class name, and the Daraja callback URL (/wc-api/wc_mpesa_till_callback/) are all unchanged, matching the same precedent as the earlier wc-mpesa-till-payment → mpesa-till-gateway rename. Existing installs on bonbargains.com/nairobistalls.com need a manual reinstall to pick this up — WordPress cannot rename an installed plugin’s folder via a normal update; deactivate, delete the old mpesa-till-gateway folder, install this version fresh, then reactivate. Stored settings are unaffected (kept under a WooCommerce option key, not tied to the folder name).

1.5.1 – 2026-09-09

• Changed: Display name updated from “M-Pesa Till Gateway for WooCommerce” to “M-Pesa Payment Gateway for WooCommerce” ahead of first WordPress.org submission — cosmetic only. The plugin slug (mpesa-till-gateway at the time; renamed again in 1.5.2, see above), text domain, folder name, main file name, database table, and the Daraja callback URL were all unchanged by this specific release; existing installs were unaffected.

1.5.0 – 2026-08-31

• Renamed from wc-mpesa-till-payment to mpesa-till-gateway (slug, folder, main file, text domain) — see the 1.5.2 and 1.5.5 entries above for the further renames, most recently to marupurupu-checkout-for-mpesa. WordPress.org restricts the term “wc” in plugin slugs — the previous name could never have been submitted. No functional change; internal identifiers, the database table, and the M-Pesa/Daraja callback URL are all unchanged, so existing installs keep working exactly as before once updated.
• Changed: Outbound Safaricom API calls (OAuth token, STK Push, status query) now use WordPress’s own HTTP API (wp_remote_get()/wp_remote_post()) instead of calling cURL directly — same behavior (timeouts, SSL verification), but works correctly on hosts that restrict direct cURL usage and follows WordPress.org coding standards.
• Fixed: 8 “Creation of dynamic property is deprecated” warnings on every settings-page load (PHP 8.2) — the gateway’s credential fields are now properly declared class properties.
• Fixed: numerous smaller correctness/compliance items found via a full run of the official WordPress.org Plugin Check tool — missing output escaping, missing translator comments on translatable strings with placeholders, date() calls affected by server timezone changed to gmdate(), superglobal reads missing wp_unslash(), wp_redirect() changed to wp_safe_redirect() for two admin actions added in 1.4.x, and a stale “Tested up to” header.
• Removed: two long-dead, unused logging methods that hand-rolled log files inside the plugin’s own (web-accessible) directory — this exact pattern was already fixed elsewhere in 2026-08-01 by switching to WooCommerce’s own logger; these had no remaining callers.

1.4.2 – 2026-08-28

• Fixed: Critical — every successful M-Pesa payment triggered a PHP fatal error partway through the callback handler (order was correctly marked paid, but processing stopped there — stock was never reduced, and any later code/hooks in that request never ran). Caused by a redundant, duplicate do_action('woocommerce_payment_complete', ...) call that passed a raw database string instead of an integer order ID, which crashes WooCommerce core’s own stock-reduction code (get_stock_reduced()) on this WooCommerce version. WC_Order::payment_complete(), called immediately before it, already fires this same hook correctly — the duplicate call is removed rather than just type-fixed, since it was firing every other plugin’s payment-complete listeners twice per order. Found live on a production install 2026-08-28; confirmed via WooCommerce core source that the fix doesn’t lose any behavior.

1.4.1 – 2026-08-28

• Changed: Saved Consumer Key/Secret/Passkey fields now show a masked fingerprint (bullets plus the last 4 real characters, same convention as a masked card number) with a “Change” button, instead of rendering completely blank. A blank field with only a placeholder was mistaken for “nothing saved” by a real merchant, causing them to keep re-entering credentials on every save. The real value is still never placed in the page as plaintext — only 4 of 32-64 characters are ever shown, purely to confirm at a glance that a specific value is genuinely stored.

1.4.0 – 2026-08-28

• Added: “Test M-Pesa Connection” button on the settings page — checks the currently saved Consumer Key/Secret against Safaricom right now and reports plainly whether they work, instead of only finding out via a failed checkout. Added after a real support case where a merchant couldn’t tell “saved and correct” from “saved but wrong” since credential fields never redisplay their value
• Fixed: A failed OAuth token request (wrong/invalid Consumer Key or Secret) now logs Safaricom’s HTTP status and response to the PHP error log — previously this specific failure mode logged nothing at all, making “Failed to get access token” undiagnosable from the server side

1.3.0 – 2026-08-25

• Security: Rewrote credential encryption from AES-256-CBC to AES-256-GCM (authenticated encryption) with an explicit format marker, fixing a real bug where a plaintext credential that happened to look like valid base64 could be silently stored unencrypted, then misreported as an “encryption key changed” error when the plugin later tried to decrypt it
• Security: Stored M-Pesa credentials are cleared once during this update and must be re-entered — the new encryption format is not compatible with the old one, and safely converting old encrypted values wasn’t possible without risking corrupted credentials being silently used against the live payment API. See the admin notice on the M-Pesa settings page after updating
• Security: Settings screen no longer redisplays your decrypted Consumer Key/Secret/Passkey in the page HTML on every visit — fields now stay blank (matching how Stripe/PayPal gateway plugins handle secrets) and only change what’s stored if you actually type a new value
• Security: The M-Pesa callback handler now verifies the confirmed payment amount against the original order total before marking an order as paid, and ignores duplicate callback deliveries for an already-processed transaction (Safaricom is known to occasionally redeliver the same callback)
• Security: Outbound Daraja API calls now set an explicit connection/request timeout, and explicitly require SSL certificate verification instead of relying on PHP’s default
• Security: The customer-facing payment-retry endpoint is now rate-limited (max 3 attempts per order per 10 minutes) — it previously allowed unlimited unsolicited STK Push prompts to any phone number, not just the order’s own
• Changed: Encryption key derivation now uses HKDF (combining WordPress’s AUTH_KEY and AUTH_SALT) instead of a bare hash of AUTH_KEY alone

1.2.0 – 2026-08-14

• Added: Anonymous usage telemetry is now fully functional (opt-in, off by default) — restored the settings checkbox, fixed a bug where activation could report in before the opt-in check ran, and pointed it at a real, dedicated collector backend
• Security: Telemetry activation reporting is now gated by the same opt-in check as every other telemetry event, with no exceptions
• Changed: Privacy Policy section now documents the exact field list sent for every telemetry event type

1.1.1 – 2026-08-02

• Security: Removed disabled SSL certificate verification on all outbound Daraja API calls
• Security: M-Pesa callback URL now includes a per-site secret token; requests without it are rejected
• Security: Callback logs now use WooCommerce’s protected logger instead of an unprotected custom log file
• Fixed: Encryption admin notices now proactively warn about a weak encryption key or degraded encryption instead of only logging silently
• Changed: Renamed to “M-Pesa Till Gateway for WooCommerce”
• Changed: Bundled Chart.js locally instead of loading it from a CDN
• Removed: Dead class-mpesa-blocks-support-v2.php (superseded by the active blocks support class)

1.1.0 – 2026-01-13

• Added: WooCommerce Blocks support for modern checkout
• Added: React-based payment method registration
• Added: Automatic checkout type detection
• Improved: Documentation and troubleshooting guides
• Fixed: Payment method not showing on block checkout
• Maintained: 100% backward compatibility with classic checkout

1.0.0 – 2025-12-24

• Initial release
• STK Push payment integration
• Payment callbacks and confirmations
• AES-256-CBC credential encryption
• Transaction reports and tracking
• Test mode support
• Admin dashboard
• Telemetry tracking (opt-in)
• Debug logging