Pay for Payment adds a fee to any WooCommerce payment method: a flat amount, a percentage of the cart, or both. Use it for a cash-on-delivery fee or a card surcharge, so the methods that cost you money pay for themselves. Give the fee a negative amount and it becomes a discount that rewards customers who pick the payment method that’s cheapest for you.

What it does

Flat amount and percentage: combine the two, for example “2.5% + 0.50”.
Minimum and maximum: for a percentage fee, set the lowest and highest amount to charge, fixed part included.
Discount instead of a fee: a negative amount favors cheaper payment methods instead of only penalizing the expensive ones.
Percentage base: add shipping and taxes to the cart subtotal, or subtract coupons.
Taxes: mark the fee as taxable, choose a tax class, or enter an amount that already includes tax. VAT-exempt customers are never charged tax on the fee.
Free shipping: switch the fee off per payment method when shipping is free.
Custom fee title: use placeholders such as [FIXED_AMOUNT] or [PERCENT_AMOUNT] in the title.
Block checkout: besides the classic checkout, it has basic block checkout support and recalculates the fee when the customer changes the payment method. The Checkout block has to sit directly in the page content, not in a template part.

Settings

You set everything on one screen under WooCommerce → Settings → Pay for payment, which lists all your store’s payment methods, enabled or not. It also works for gateways whose own settings leave no room for extra fields (WooCommerce Payments, Stripe, Klarna). When you upgrade from version 2.x, your settings carry over automatically. Developers can adjust the fee with filters such as woocommerce_pay4pay_apply or woocommerce_pay4pay_{$payment_gateway_id}_amount. The fee applies at checkout only, not on the “Pay for order” page or on orders created in the admin. I don’t recommend the plugin for PayPal: its terms prohibit surcharges, so give a discount on the other methods instead.

Pro version and documentation

The free version charges one fee per payment method on each order. Pro adds conditions (cart total, country, shipping method, user role and more), several fee tiers per method, and fees on manually created orders and on the “Pay for order” page, all without code. You’ll find documentation, examples and the free vs Pro comparison on payforpayment.com, and you can try Pro for 7 days without entering a card.

Go to payforpayment.com

I took the plugin over in 2017. It was originally written by Jörn Lund, thank you for the work.

Get involved

The plugin is free and open source. Reporting a bug, suggesting an improvement or leaving a review helps it most.

Do you need customization?

Modifications that will enhance the plugin development and help other users I offer for “adoption”. You pay half the development cost and I’ll deliver the other half for free.

If the modifications are only of limited use, are only for your usage, or do not match my idea of the plugin’s direction, they are charged at full price.

Give me a call or shoot me an e-mail

Changelog

3.0.3 – 2026-10-23

Accessibility: on the classic checkout, choosing a payment method with the keyboard no longer throws focus back to the top of the page on every arrow-key step while the fee updates. It stays on the payment method the shopper picked.
Accessibility: in the settings, an error, including a failed save, now stays on screen until you close it instead of disappearing after five seconds. A failed save is also flagged next to “Save changes”, where you clicked.
Accessibility: red error messages and the “No changes to save” line in the settings are darker, so they are readable on the gray background. A field you reach with the Tab key no longer ends up hidden behind the save bar or the admin header.
Tested up to WooCommerce 11.2.1.

Older versions (4)

3.0.2 – 2026-10-12

Security: the block checkout now charges the fee of the payment method named in the place-order request itself. Before, the fee followed the method the shopper’s browser had sent earlier – a request sent straight to the WooCommerce checkout API, skipping that step, placed an order on a fee-bearing method without its fee. Reported through Patchstack; thanks to the reporter.

3.0.1 – 2026-10-09

Updated Freemius SDK to the latest version.
Tested up to WordPress 7.1.3 and WooCommerce 11.2.0.

3.0.0 – 2026-09-23

Rewritten from the ground up. Everything 2.x could do, it still does – same fee maths, same developer filters, and your settings move themselves.

Upgrading from 2.x

Your per-gateway fee settings migrate automatically the first time the plugin runs. Nothing to reconfigure. The old settings are left exactly where they were.
Fees are now configured in one place: WooCommerce > Settings > Pay for payment. The fields no longer appear on each gateway’s own settings page.
Requires PHP 8.0 or newer and WooCommerce 7.7 or newer.
The plugin is listed as “Pay for Payment for WooCommerce – Payment Gateway Fees & Discounts” – same plugin, same slug, same settings.

New

One settings screen for every payment method, built with WooCommerce’s own admin components. It also covers gateways whose own settings screens have no room for extra fields – WooCommerce Payments, Stripe, Klarna and other React-based gateways.
The screen lists every payment method you have, enabled or not, so you can set a fee up before the method goes live.
Block checkout support: the fee is calculated and the total updates when the shopper changes payment method, the same as on the classic checkout.
Fee lines the plugin writes now carry _pay4payment_fee_gateway and _pay4payment_fee_source order-item meta, so accountants and exports can tell them from any other fee.
Uninstalling removes every option the plugin wrote, including the standalone rows 2.x left behind. The pay4pay_* keys stored inside each gateway’s own WooCommerce settings are left untouched – those are your 2.x configuration, and keeping them is what lets you roll back to 2.x.

Changed

A cart with nothing left to pay for – goods fully discounted and no shipping cost – no longer gets a payment fee. In 2.x the check looked at the cart total before discounts, so a 100 % coupon still paid the fee. Paid shipping on free goods still charges.
“Tax class based on cart items” now also applies when the fee amount excludes tax. In 2.x it only worked for tax-inclusive amounts and quietly fell back to the standard rate otherwise, so the fee’s tax may change on stores that mix tax classes.
Fees are charged only for the payment methods you have switched on in the settings screen. Everything that charged a fee in 2.x is switched on for you during the upgrade.
The “Extra Charge” column on WooCommerce > Settings > Payments is gone. WooCommerce rebuilt that screen and removed the hook the column was built on, so it no longer had anywhere to appear. Every method’s fee is shown on the plugin’s own settings screen instead.
VAT-exempt customers now pay the net of a fee whose amount includes tax, not the full amount. A fee set to 12.10 including 21 % tax is charged to everyone as 10.00 plus tax; a VAT-exempt customer now pays 10.00 with no tax, where 2.x charged them the whole 12.10. This only affects stores that both tick “Fee amount already includes tax” and have VAT-exempt customers.

Fixed

When a customer’s payment fails and they pay the order again with a different method, the first method’s fee is removed from the order instead of staying on it.
The previous method’s fee is likewise removed from block-checkout and express (Apple Pay / Google Pay) orders, before the payment amount is authorized.
The checkout no longer fatals when another plugin puts a cart entry without product data in the basket while the fee’s tax class is “based on cart items”.
The “Standard rate” tax class can be picked again. The settings screen was sending a value the server rejected, so the fee fell back to “based on cart items” and was taxed at the highest rate in the cart.
A fee you switched off stays off – updating the plugin used to switch fees migrated from 2.x back on.
Your settings migrate even if the update was applied while WooCommerce was deactivated. Before, the plugin recorded the migration as done and the store came back with no fees configured at all.
“Do not charge the fee on free shipping” looks at every shipping package again, as in 2.x. A cart split into several shipments charged the fee whenever the first package was not the free-shipping one.
“Charge at least” and “Charge at most” accept negative amounts again – the bound that limits a discount is itself negative, so “5 % off, never more than 50 off” can be set up once more. A method carrying such a cap from 2.x can also be saved again instead of blocking on a validation error.
A fee set up by hand in 3.0 now starts from the same defaults as in 2.x, so the same numbers produce the same charge: the amount you type contains its tax, the percentage is calculated on a base that includes cart taxes, and the standard tax class applies.
Stores using Price Based on Country charge the converted fee again, rather than the base-currency number in the customer’s currency.
With Multi Currency for WooCommerce (CURCY) active, an order created in the admin in a currency other than the shop’s no longer gets a payment fee in the shop’s currency – no fee is added, and the order says why.
Leaving the settings screen after saving no longer raises the browser’s “Leave site?” warning.
The settings screen is fully translated in all eight bundled languages (Czech, German, Spanish, Italian, Dutch (BE/NL), Slovak, Turkish) – a large part of it had fallen back to English.
Validation messages name the field they appear under (“Fee label”, “Minimum fee”) instead of internal field names.

Developers

All 2.x filters keep their names and signatures: woocommerce_pay4pay_charges_fixed, _charges_percentage, _charges_minimum, _charges_maximum, _apply, _applyfor_{gateway_id} and _{gateway_id}_amount. They still fire inside the calculation with the same intermediate values, and the fee is still added on woocommerce_cart_calculate_fees at PHP_INT_MAX - 1.
Those filters now receive one extra trailing argument: the index of the fee rule being calculated. Existing callbacks are unaffected.
woocommerce_pay4pay_get_current_gateway_settings keeps working. It is rebuilt over the new settings schema and fires with the same fourteen pay4pay_* keys, so a 2.x snippet runs unchanged at checkout. Returning false still switches the fee off. (On Pro it fires on the order-pay charge and in the per-method fee preview too – those paths do not exist in the free plugin, so there is nothing for it to shape there.) Two things to know when bringing a snippet across: it shapes a fee for a method that is switched on in the settings screen (a method whose fee lives entirely in your code is switched on for you during the upgrade), and COD’s enable_for_methods is read from the gateway rather than from the array you return.
REST: pay4payment/v1/settings (GET/POST, manage_woocommerce).
WPML string names are unchanged, so existing translations of the fee title and fixed charge keep working.
The five multi-currency integrations (Price Based on Country, WooCommerce Multi-Currency, Woo Multi Currency, WCML, WOOCS) are carried over.
HPOS and cart/checkout blocks compatibility are declared.

2.2.2 and earlier

Every release back to 1.0.0 (2013) is listed at payforpayment.com/changelog.