Accept PalmPay
payments on WooCommerce
Install the free PaymentHood plugin for WooCommerce, connect your PalmPay account, and PalmPay appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.
- NGN
- Platform
- WooCommerce 6.0+
- Provider
- PalmPay
- Install via
- Plugins → Add New → Upload Plugin
- Billing
- One-time
- PaymentHood fee
- None
PalmPay on WooCommerce at a glance
- WooCommerce version
- WooCommerce 6.0+
- Where you install it
- WordPress admin → Plugins → Add New → Upload Plugin
- Coverage
-
- Nigeria
- Currencies
-
- NGN
- Billing models
- One-time checkout payments. Recurring billing is not supported by the WooCommerce plugin yet.
- Cost
- The plugin is free and open source. You pay PalmPay's own fees, published on their pricing page (opens in new tab). PaymentHood adds nothing on top.
Coverage, currencies and payment methods as published by PalmPay, who set and update them. For the current list see PalmPay's own site (opens in new tab).
What WooCommerce customers can pay with
Each method PalmPay supports appears in your WooCommerce checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WordPress side.
PalmPay wallet
Payment from the customer's PalmPay balance
Bank transfer
Transfer confirmed against the order
Cards
Card payment where enabled on the account
Connect PalmPay to WooCommerce
Four steps, no code. The full walkthrough with screenshots is in the WooCommerce installation guide.
Open a PalmPay account
Register with PalmPay and finish their onboarding. Funds settle from PalmPay to your own bank account.
Add it in PaymentHood
Paste your PalmPay credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.
Install the plugin
Download the WooCommerce plugin and install it from Plugins → Add New → Upload Plugin in your WordPress admin.
Enable and test
Paste your PaymentHood API key into the plugin settings, run a sandbox order end to end, then switch to live.
Rather than a direct PalmPay plugin
A single-provider plugin works until you need a second provider. These are the parts you would otherwise build and maintain yourself.
- Webhook security
- Signed payment notification, validated before an order is released
- Payment verification
- Server-side transaction status re-check before fulfilment
- Credentials
- Merchant credentials with request signing, held server-side in PaymentHood
- Add a second provider without touching your WooCommerce checkout
- Automatic failover when PalmPay is unreachable, instead of a failed order
- Idempotent charge creation, so a double-submitted order is not a double charge
- One reconciliation view across every provider you run
- Free and open source — read the plugin on GitHub (opens in new tab)