Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Pay for Payment for WooCommerce · Version history

Pay for Payment for WooCommerce changelog and version history

Latest version
3.0.3
Oct 23, 2026 (18 days ago)
Releases
57
since 2014
In the last year
8
about one every 49 days
Tested up to
WordPress 7.1.4
PHP 8.0 or later

Releases each year

  • 20147 releases
  • 20153 releases
  • 20161 release
  • 20176 releases
  • 20185 releases
  • 20195 releases
  • 20206 releases
  • 20217 releases
  • 20225 releases
  • 20241 release
  • 20256 releases
  • 20265 releases

20265 releases

  1. Pay for Payment for WooCommerce 3.0.3Latest

    • 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.

  2. Pay for Payment for WooCommerce 3.0.2

    • 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…

  3. Pay for Payment for WooCommerce 3.0.1

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

  4. Pay for Payment for WooCommerce 3.0.0

    • 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…
    • 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.

  5. Pay for Payment for WooCommerce 2.2.2

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

20256 releases

  1. Pay for Payment for WooCommerce 2.2.2-rc1

  2. Pay for Payment for WooCommerce 2.2.1

  3. Pay for Payment for WooCommerce 2.2.0

  4. Pay for Payment for WooCommerce 2.1.11

  5. Pay for Payment for WooCommerce 2.1.10

  6. Pay for Payment for WooCommerce 2.1.9

20241 release

  1. Pay for Payment for WooCommerce 2.1.8

20225 releases

  1. Pay for Payment for WooCommerce 2.1.7

  2. Pay for Payment for WooCommerce 2.1.7rc1

  3. Pay for Payment for WooCommerce 2.1.6

  4. Pay for Payment for WooCommerce 2.1.5

  5. Pay for Payment for WooCommerce 2.1.5-rc.1

20217 releases

  1. Pay for Payment for WooCommerce 2.1.4

  2. Pay for Payment for WooCommerce 2.1.3

  3. Pay for Payment for WooCommerce 2.1.2

  4. Pay for Payment for WooCommerce 2.1.1

  5. Pay for Payment for WooCommerce 2.1.0

  6. Pay for Payment for WooCommerce 2.0.19

  7. Pay for Payment for WooCommerce 2.0.18

20206 releases

  1. Pay for Payment for WooCommerce 2.0.18rc2

  2. Pay for Payment for WooCommerce 2.0.18rc1

  3. Pay for Payment for WooCommerce 2.0.17

  4. Pay for Payment for WooCommerce 2.0.16

  5. Pay for Payment for WooCommerce 2.0.15

  6. Pay for Payment for WooCommerce 2.0.14

20195 releases

  1. Pay for Payment for WooCommerce 2.0.13.3

  2. Pay for Payment for WooCommerce 2.0.13.2

  3. Pay for Payment for WooCommerce 2.0.13.1

  4. Pay for Payment for WooCommerce 2.0.12

  5. Pay for Payment for WooCommerce 2.0.11

20185 releases

  1. Pay for Payment for WooCommerce 2.0.10

  2. Pay for Payment for WooCommerce 2.0.9

  3. Pay for Payment for WooCommerce 2.0.8

  4. Pay for Payment for WooCommerce 2.0.7

  5. Pay for Payment for WooCommerce 2.0.6

20176 releases

  1. Pay for Payment for WooCommerce 2.0.5

  2. Pay for Payment for WooCommerce 2.0.4

  3. Pay for Payment for WooCommerce 2.0.3

  4. Pay for Payment for WooCommerce 2.0.2

  5. Pay for Payment for WooCommerce 2.0.1

  6. Pay for Payment for WooCommerce 2.0.0

20161 release

  1. Pay for Payment for WooCommerce 1.3.8

20153 releases

  1. Pay for Payment for WooCommerce 1.3.7

  2. Pay for Payment for WooCommerce 1.3.6

  3. Pay for Payment for WooCommerce 1.3.5

20147 releases

  1. Pay for Payment for WooCommerce 1.3.4

  2. Pay for Payment for WooCommerce 1.3.3

  3. Pay for Payment for WooCommerce 1.3.2

  4. Pay for Payment for WooCommerce 1.3.1

  5. Pay for Payment for WooCommerce 1.3.0

  6. Pay for Payment for WooCommerce 1.2.5

  7. Pay for Payment for WooCommerce 1.2.4

Questions about Pay for Payment for WooCommerce’s releases

What is the latest version of Pay for Payment for WooCommerce?

3.0.3, released on Oct 23, 2026 (2 weeks ago). It’s tested up to WordPress 7.1.4 and needs PHP 8.0 or later.

How often is Pay for Payment for WooCommerce updated?

8 releases in the last year, about one every 49 days. Its first release on WordPress.org dates from August 2014.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Pay for Payment for WooCommerce’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.