Title: WooPayments: Integrated WooCommerce Payments Author: WooCommerce Published: Avril 8, 2020 Last modified: Avril 16, 2026 --- Search plugins ![](https://ps.w.org/woocommerce-payments/assets/banner-772x250.png?rev=3234740) ![](https://ps.w.org/woocommerce-payments/assets/icon-256x256.png?rev=3234740) # WooPayments: Integrated WooCommerce Payments By [WooCommerce](https://profiles.wordpress.org/woocommerce/) [Download](https://downloads.wordpress.org/plugin/woocommerce-payments.10.7.1.zip) * [Details](https://hat.wordpress.org/plugins/woocommerce-payments/#description) * [Reviews](https://hat.wordpress.org/plugins/woocommerce-payments/#reviews) * [Installation](https://hat.wordpress.org/plugins/woocommerce-payments/#installation) * [Development](https://hat.wordpress.org/plugins/woocommerce-payments/#developers) [Support](https://wordpress.org/support/plugin/woocommerce-payments/) ## Description **Payments made simple, with no monthly fees – designed exclusively for WooCommerce stores.** Securely accept major credit and debit cards, and allow customers to pay you directly without leaving your WooCommerce store. View and manage transactions from one convenient place – your WordPress dashboard. See payments, track cash flow into your bank account, manage refunds, and stay on top of disputes without the hassle of having to log into a separate payment processor. **Manage transactions from the comfort of your store** Features previously only available on your payment provider’s website are now part of your store’s **integrated payments dashboard**. This enables you to: * View the details of [payments, refunds, and other transactions](https://woocommerce.com/document/woopayments/managing-money/). * View and respond to [disputes and chargebacks](https://woocommerce.com/document/woopayments/fraud-and-disputes/managing-disputes/). * [Track payouts](https://woocommerce.com/document/woopayments/payouts/) into your bank account or debit card. **Pay as you go** WooPayments is **free to install**, with **no setup fees or monthly fees**. Our pay-as-you-go pricing model means we’re incentivized to help you succeed! [Read more about transaction fees](https://woocommerce.com/document/woopayments/fees/). **Supported by the WooCommerce team** Our global support team is available to answer questions you may have about WooPayments installation, setup, or use. For assistance, [open a ticket on woocommerce.com](https://woocommerce.com/my-account/contact-support/?select=5278104). ### Getting Started #### Requirements * WordPress 6.0 or newer. * WooCommerce 7.6 or newer. * PHP 7.3 or newer. #### Try it now To try WooPayments (previously WooCommerce Payments) on your store, simply [install it](https://wordpress.org/plugins/woocommerce-payments/#installation) and follow the prompts. Please see our [Startup Guide](https://woocommerce.com/document/woopayments/startup-guide/) for a full walkthrough of the process. ## Screenshots * [[ * View Transactions * [[ * View Transaction Details * [[ * Track Payouts * [[ * Manage Disputes ## Blocks This plugin provides 1 block. * Multi Currency Switcher ## Installation Install and activate the WooCommerce and WooPayments plugins, if you haven’t already done so, then go to “Payments” in the WordPress admin menu and follow the instructions there. ## FAQ ### What countries and currencies are supported? If you are an individual or business based in [one of these countries](https://woocommerce.com/document/woopayments/compatibility/countries/#supported-countries), you can sign-up with WooPayments. After completing sign up, you can accept payments from customers anywhere in the world, as long as they are paying with [a supported currency](https://woocommerce.com/document/woopayments/currencies/available-currencies/). We are actively planning to expand into additional countries based on your interest. Let us know where you would like to [see WooPayments launch next](https://woocommerce.com/payments/#request-invite). ### Why is a WordPress.com account and connection required? WooPayments uses the WordPress.com connection to securely communicate with our payments server. This is necessary for WooPayments to function correctly, so it’s not possible to use WooPayments without connecting. Please see [this document](https://woocommerce.com/document/woopayments/our-policies/connection/) for more information. Note that you do not need to host your site itself on WordPress.com, nor do you need to host _any_ site on WordPress.com at all. You only need an account. Note that you do not need to host your site itself on WordPress.com. You only need an account on WordPress.com to establish the connection. You can create a WordPress. com account [at this link](https://wordpress.com/start/account/user-social). ### How do I set up a store for a client? If you are a developer or agency setting up a site for a client, please see [this page](https://woocommerce.com/document/woopayments/account-management/developer-or-agency-setup/) of our documentation for some tips on how to install WooPayments on client sites. ### How is WooPayments related to Stripe? WooPayments is built in partnership with Stripe [Stripe](https://stripe.com/). When you sign up for WooPayments, your personal and business information is verified with Stripe and stored in an account connected to the WooPayments service. This account is then used in the background for managing your business account information and activity via WooPayments. [Learn more](https://woocommerce.com/document/woopayments/account-management/partnership-with-stripe/). ### Are there Terms of Service and data usage policies? You can read our Terms of Service and other policies [here](https://woocommerce.com/document/woopayments/our-policies/). ## Reviews ![](https://secure.gravatar.com/avatar/04a831c38d65bf8fe4bae6026b270c9bf6c17fb51f7d5c0f3420355e57f70fed? s=60&d=retro&r=g) ### 󠀁[Ottimo supporto tecnico](https://wordpress.org/support/topic/ottimo-supporto-tecnico/)󠁿 [Giovanni](https://profiles.wordpress.org/phototablehm/) Avril 18, 2026 1 reply Davvero grazie a tutto lo staff per aver risolto velocemente il mio problema con la visualizzazione delle transazioni Woopayments, in particolare all’lngegnere della felicità Aarav 😉 thank you ![](https://secure.gravatar.com/avatar/956682ced00d3168157690679ba6e39a8de013f07b0e483cc48ed4722d290cf5? s=60&d=retro&r=g) ### 󠀁[Tan malo y costoso como Stripe (es lo mismo)](https://wordpress.org/support/topic/tan-malo-y-costoso-como-stripe-es-lo-mismo/)󠁿 [jgcaprocel](https://profiles.wordpress.org/jgcaprocel/) Avril 12, 2026 1 reply Tan peligroso o peor que Stripe (que es lo que lleva detrás), cualquier disputa es retenida y es casi imposible que se resuelva a favor del comercio por más pruebas que se presente y cobran además una comisión escandalosa por el trámite de la disputa( por eso siempre pierdes).No aporta nada en términos de riesgo de pago y además es carísimo.Hay que buscar alternativas. ![](https://secure.gravatar.com/avatar/44eb33197b3e4664f8af0d08bfd50d6db84ca9b555f493c1b3ad88a12fe6fb4e? s=60&d=retro&r=g) ### 󠀁[WooCommerce support was great](https://wordpress.org/support/topic/woocommerce-support-was-great/)󠁿 [yorkshire2028](https://profiles.wordpress.org/yorkshire2028/) Avril 10, 2026 1 reply I made a fundamental error migrating a test site to a live one and didn’t realise at the time that this would later bite me back – the Woo payments was stuck in safe mode – but the ‘Happiness Engineers’, particularly Jake, got me back on track in good time despite me making even more mistakes during the rectification process Full marks Dave ![](https://secure.gravatar.com/avatar/d7d6f6f536803b6205cfc3ea67b014d886940b23aeaa28916fd289951f57220b? s=60&d=retro&r=g) ### 󠀁[Amazing service](https://wordpress.org/support/topic/amazing-service-86/)󠁿 [Jose Angel Navarro](https://profiles.wordpress.org/angelguitarrist/) Avril 10, 2026 1 reply Great and useful tool for any online payment. Thanks ![](https://secure.gravatar.com/avatar/c773098b06f0f471f4cc8c1d6bfafc8b941f44325922865e30109b48eb9ea0bd? s=60&d=retro&r=g) ### 󠀁[Helpful Support and a decent checkout experience – however](https://wordpress.org/support/topic/helpful-support-and-a-decent-checkout-experience-however/)󠁿 [originalpwah](https://profiles.wordpress.org/originalpwah/) Avril 9, 2026 1 reply This is a decent integration in terms of checkout flow, however the fees are higher than a regular Stripe / WooCommerce set-up, and it is much harder on the accountant since there’s no Xero integration. These are serious drawbacks and I have considered reverting due to them. Support is very helpful and pleasant, however. ![](https://secure.gravatar.com/avatar/d4eaed53f157296ff258632e0af76df9689549e122e7a5d0048803246c8c8709? s=60&d=retro&r=g) ### 󠀁[If you actually wish to have your money at the end of the day STAY AWAY!!](https://wordpress.org/support/topic/if-you-actually-wish-to-have-your-money-at-the-end-of-the-day-stay-away/)󠁿 [hermesonlinehandel](https://profiles.wordpress.org/hermesonlinehandel/) Avril 5, 2026 1 reply For starters i have a legally operating side business here in Germany. VAT number and everything else is in order. Any other payment processor eg. Paypal works totally fine. You sell a Product you get your money (most of the time instantly). Woopay however just takes your money indefinetly however they see fit. Let you tell me my story before installing this. I made my hobby into a legally operating side business a few years back. Most of my sales are locally via “ebay kleinanzeigen” i do custom metal art/wedding gifts like fire baskets with custom personalized logos and designs for each customer. Never had even one unhappy customer i take my time to personalize everything to their expectations sometimes spending many hours on one design so it is a perfect fit. So i took it upon me to create a website to be visible. unfortunately i chose to trust woopayments as i thought they would be credible and reliable because of woocommerce. little did i know that it almost broke my neck (had i not installed PayPal too which like 95% of customers used i would have been finished). In July 2025 i made a product prototyped it put it on the website for sale after producing a few. Made an Instagram video which suddenly burst viral like 8 million views 1st day so people ordered like crazy. I am only one Person and unfortunately on the 2. day or so i noticed that not even setting the delivery date to in 14 days would stop people from ordering. I worked at my limit the whole weekend no sleep just trying to produce as many as possible ( like 200 300 a day) after noticing i was running out of stainless steel sheets and my local provider could not send me enough in time and orders keept pouring in i set the product to not aviable in the moment calculating how much steel i could get from my local steel reseller and how many i could produce i had to cancel like a few 100 orders in order to be able to get most people (except of the like few 100 orders) their products on time. I ordered much more Stainless Steel and fortunately Paypal processed my payments. Woopay however did not (they just suspend your payouts indefinetly no email no clarification from support it has been 7 close to 8 months and they still keep the money). If everything went over woopay i would have had to pay over 8 thousand euro of material out of my pocket ( keep in mind im a normal working man with a regular income and a side hustle) then i would have had to pay the Taxes (VAT and income Tax) on money i never recieved after the year ended. The product went so viral several chinese sellers popped up on amazon after like 3 days and sold below material price… So that was a fun ride nevertheless i cannot do anything against those chinese sellers ^^. However Woopay is still holding like 2.2 thousand euro (fortunately only a small small fraction of the sales) close to 8 months after (keep in mind i already paid taxes on the money i did not receive). The support is not helping i tried to contact them for weeks Stripe dashboard shows the money but i cannot pay out the money. Stripe support says the issue lies with woopay since they suspended the payout. Woopay support does not want any verification like Tax id Vat id i was ready to provide everything to them they did not want anything. I was told i had to build a Payment history with them which is like the sudden influx in those few days. (which is impossible it vent viral how do i do that again and the chinese sellers are lowballing so hard its impossible to sell). So basically i was told we keep your money until you give us more money constantly until we are happy with the turnover. The Money processed untill then will be kept too. I was given no turnover amount which i had to reach. I tried to communicate my situation how should i trust a payment processor which does not tell me what they require to pay me my earnings (normally they should just process the payment ???? like a payment processor does?) . I was totally confused Paypal processed everything perfectly no problems. Woopay however just took everything they processed. I deactivated the plugin. As a small time side business owner how can i trust someone who does not do what he is supposed to do doesent respond for days/weeks and then basically cryptically says hey you just have to give us more money until we are happy but we cannot tell you the amount… If i didnt integrate PayPal and almost everyone used it. I would have had no earnings, would have had to pay several thousands ontop for material and then Pay taxes on money i never got this would have put me into serious Problems. Now close to 8 months in i am kinda fed up since i see the Suspended amont every day in the dashboard. I will start to inform people of this in every possible kind of way social media/reddit will be next mabye someone working for woopay will see this and hopefully stop this practice or help in any way. I cannot fathom how people can do business this way. Mabye this will prevent people from really getting financially hurt by this (i was lucky for installing paypal too). Mabye other people have the same experience mabye it was all a mistake (which i cannot really believe since i spoke to the woopay support several times and i was not “supported ^^”) [ Read all 146 reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/) ## Contributors & Developers “WooPayments: Integrated WooCommerce Payments” is open source software. The following people have contributed to this plugin. Contributors * [ WooCommerce ](https://profiles.wordpress.org/woocommerce/) * [ Automattic ](https://profiles.wordpress.org/automattic/) “WooPayments: Integrated WooCommerce Payments” has been translated into 10 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/woocommerce-payments/contributors) for their contributions. [Translate “WooPayments: Integrated WooCommerce Payments” into your language.](https://translate.wordpress.org/projects/wp-plugins/woocommerce-payments) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/woocommerce-payments/), check out the [SVN repository](https://plugins.svn.wordpress.org/woocommerce-payments/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/woocommerce-payments/) by [RSS](https://plugins.trac.wordpress.org/log/woocommerce-payments/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 10.7.1 – 2026-04-16 * Fix – Fix changelog entries for 10.7.0 release. #### 10.7.0 – 2026-04-15 * Add – Add client-side async price renderer for cache-optimized multi-currency mode * Add – Add digital product/service evidence matrix entries for all dispute reasons * Add – Added dispute evidence document suggestions for the Other product type across all dispute reasons. * Add – Add event product type evidence matrix entries for all dispute reasons * Add – Add evidence matrix entries for physical_product disputes and fix cover letter attachment ordering * Add – Add fonts.wp.com to the WooPay font domain allow list so merchants using Automattic’s GDPR-compliant font proxy see their theme fonts in WooPay checkout. * Add – Add offline service evidence matrix entries for all dispute reasons * Add – Enable WooPay themed checkout from all entry points, including merchant font rendering. * Add – feat: add tool to manually clear computed styles cache * Add – Re-introduce asynchronous customer updates as an optimization of the checkout process. * Add – Send WooCommerce store ID to the server with onboarding and account requests for Tracks event attribution * Fix – Accept account_data parameter in test-drive account init endpoint * Fix – Add defensive checks before initializing WC_Payments_Captured_Event_Note to prevent fatal errors when timeline data is missing or malformed. * Fix – Add fallback skeleton styles for WooCommerce versions before 10.2 * Fix – Add Link payment method token support in subscription payment method change order notes * Fix – Add visible focus indicator to WooPay express checkout button for WCAG 2.4.7 compliance * Fix – Change WooPay express button to an anchor element when first-party auth is enabled for correct screen reader semantics. * Fix – Convert screen-reader text to target currency in cache-optimized multi- currency mode * Fix – Disable auto-complete hooks for inactive accounts. * Fix – Enable first-party auth for stores running adapted extensions (Points & Rewards, Gift Cards) * Fix – feat: allow translation of Stripe card error messages at checkout * Fix – fix: amazon pay manual capture compatibility * Fix – fix: avoid fatal error on invalid currency option in DB * Fix – fix: ensure that page doesn’t crash if wallet icon is missing * Fix – fix: express checkout to show recurring subscription info for free trial subscriptions with sign-up fees, not just pure $0 free trials * Fix – fix: MCCY tooltip messaging for payment methods supporting multiple currencies now uses “or” instead of “and” * Fix – fix: prevent payment error string being written in the order meta * Fix – fix: trim whitespace for postcode at checkout * Fix – fix: unit tests after new WC version * Fix – Fix active plugin list being empty on older WooCommerce versions * Fix – Fix additional wc pay tracking call on order creation * Fix – Fix Apple Pay manual capture error when using confirmation tokens * Fix – Fix Docker preflight skipping infrastructure startup when database container is missing * Fix – Fix Docker setup: regenerate .htaccess rewrite rules and skip WooCommerce onboarding wizard to prevent blank screens * Fix – Fix email confirmation field not appearing on first-time email setup * Fix – Fix express checkout incompatibility with the Add to Cart with Options block by using a div placeholder instead of button and updating product page DOM selectors * Fix – Fix fatal error when themes use ref objects in theme.json for style values like fontFamily * Fix – Fix multi-currency cache mode: retain geolocation currency across session creation and Store API requests * Fix – Fix NOX in-context onboarding flow detection from referer URL * Fix – Fix reset account modal always hiding pre-reset guidance steps * Fix – Fix Stripe Payment Element losing styling on shortcode checkout with non- standard themes like Avada * Fix – Fix test card copy button using wrong font on themes with button font overrides * Fix – Fix undefined index warning when store country is empty in terminal locations controller * Fix – Fix WooPay admin preview footer card logo sizing and layout at narrow widths. * Fix – Fix WooPay Direct Checkout not working in iAPI mini-cart (WooCommerce 10.4 +) * Fix – Fix WooPay themed checkout header color not applied when template part is nested inside a wrapper block * Fix – Handle duplicate KYC session initialization gracefully * Fix – Harden public multi-currency config REST endpoint with permission callback * Fix – Improve cover letter print preview to safely render content. * Fix – Intermittent empty cart after switching from guest to an existing customer * Fix – Invalidate multi-currency exchange rate cache when the store base currency changes. * Fix – Prevent caching empty disputes list on API failure, which could hide active disputes from admin task list * Fix – Prevent unnecessary Stripe JS and express checkout scripts from loading when no express checkout methods are actually available * Fix – Refresh account cache after card reader registration. * Fix – Remove unnecessary confirmation modal when disabling payment methods on the settings page * Fix – Remove validator npm dependency and replace with inline email validation * Fix – Resolve block pattern references and style variations when extracting WooPay header/footer appearance colors from block theme template parts. * Fix – Skeleton loader styling issue when step numbers are enabled on checkout blocks * Update – Align payment method notice copy with Figma designs * Update – chore: add key validation to failed order received message * Update – feat: update e2e tests coverage * Update – Moved multi-currency store settings state to Redux store * Update – Prevent Stripe card element from temporarily rendering country and zip fields * Update – refactor: payment methods settings UI reuse * Update – update: add better on-session error message for `authentication_required` decline * Update – Update the manual capture settings UI with improved modal copy, Learn more link, and a warning banner on the payment methods list when manual capture is enabled * Dev – Add @critical E2E smoke job for fast PR feedback and cache Playwright browsers in CI * Dev – Add E2E tests for async multi-currency price renderer * Dev – Avoid redundant Playwright install in QIT setup and skip an incompatible WC 9.9.7 analytics assertion * Dev – Build WCPay Dev Tools plugin after pulling updates in post-merge hook * Dev – Bump WC tested up to version to 10.7.0 * Dev – chore: rename ECE constants to `shipping-limits.js` * Dev – chore: update browserslist / caniuse-lite database from 1.0.30001718 to 1.0.30001780 * Dev – chore: update `validator` dependency * Dev – Comment: Add git worktree safety rules to AGENTS.md * Dev – Comment: Update AI knowledge docs from appearance cache compound analysis * Dev – Convert async price renderer to TypeScript and add sessionStorage caching * Dev – dev: Clarify terminal payment failure notification logic and add tests * Dev – E2E tests for the repeated checkout attempt after the card decline. * Dev – Extract styles cache methods from WC_Payments_Utils into dedicated WC_Payments_Styles_Cache class * Dev – fix: failures in e2e PW tests for blocks * Dev – Fix QIT E2E workflow to use PR build artifact instead of marketplace release. * Dev – Improve E2E setup with preflight checks, auto-build, better output, and. env.example * Dev – Improve E2E test reliability: guard placeOrder loop, replace waitForTimeout/ networkidle, enable retries, add afterEach reloads, increase CI workers * Dev – Optimize webpack build process * Dev – refactor: move express checkout standalone button files to shortcode-buttons- express/ subdirectory * Dev – refactor: remove `CC_Payment_Method` in favor of `CardDefinition` * Dev – refactor: replace React-based express checkout availability check with vanilla TypeScript implementation * Dev – Refactor the update subscriptions token flow and improve test coverage. * Dev – Resolve WC version number instead of passing ‘latest’ to QIT CLI to work around invalid download URL construction. * Dev – Simplify core Skeleton component injection using React Context instead of prop threading * Dev – Skip async renderer QIT E2E tests pending environment investigation (WOOPMNT- 5992). #### 10.6.0 – 2026-03-11 * Add – Add credit_not_processed evidence for booking/reservation (refund has been issued) * Add – Add E2E testing skill and automated local setup script for running Playwright E2E tests against a local Transact Platform Server * Add – Added local development workflow for QIT E2E tests with npm run test:qit- e2e-up, test:qit-e2e-down, and test:qit-e2e-reset commands * Add – Add evidence matrix entry for fraudulent × physical product dispute combination * Add – Add evidence matrix entry for product not received × physical product dispute combination * Add – Add evidence matrix entry for Product Unacceptable + Booking/Reservation disputes * Add – Add evidence matrix support for credit_not_processed × booking_reservation( refund was not owed) dispute combination * Add – Add feature flag and admin UI setting for cache-optimized multi-currency rendering mode * Add – Add infrastructure for displaying express checkout methods (Apple Pay, Google Pay, Amazon Pay) in the payment methods list. Requires WooCommerce 10.6.0 + or dev mode. * Add – Add proof of delivery evidence upload to shipping details page for product not received disputes * Add – Add REST API endpoint and skeleton markup for cache-optimized multi-currency rendering * Add – Add WooPayments review prompt on Payments Settings page * Add – feat: add Amazon Pay subscriptions support * Add – feat: add mccy merchant orders e2e tests * Add – feat: enable amazon pay by default * Add – Store ipp_channel from Stripe intent metadata on WooCommerce orders and suppress IPP receipt email for POS orders * Add – Surface WooPayments support phone number status in the System Status Report. * Fix – Add email confirmation field and warning notice to account notification email settings to prevent typos and improve security awareness * Fix – Auto-focus the search input in the Add/remove currencies modal for improved usability * Fix – fix: address formatting in disputes * Fix – fix: checkout errors with plugins that dynamically change currency * Fix – fix: display ECE buttons on pay-for-order pages * Fix – fix: ensure that subscriptions with free trials are consistently handled by the ECE * Fix – fix: notice on cart block * Fix – fix: shipping rates on ECE for subscriptions with free trial * Fix – fix: WooPay & Stripe Link mutual compatibility in settings * Fix – fix: WooPay typo when saving customer * Fix – Fixed duplicate payment method dismissed notices option type from bool to array, allowing notice dismissals to persist across page refreshes. * Fix – Fixed iDEAL / Wero logo: removed baked-in stroke causing double border in admin, fixed missing rounded corners on checkout, consolidated into a single SVG file, and added dark mode icon for night theme checkout * Fix – Fixed stale WP object cache entries persisting after cache invalidation on sites with Memcached/Redis. * Fix – Fixed WooPayments incorrectly shown as incompatible with block-based checkout in the editor * Fix – Fix express checkout buttons appearing on block-based cart when the cart location is unchecked in display settings. * Fix – Fix fatal error when WC_Payments_Explicit_Price_Formatter class is loaded before loan approved note * Fix – Fix flaky disputes E2E test by polling for saved evidence instead of asserting stale state * Fix – Fix memory exhaustion and null customer fatal errors in BNPL site messaging on product and cart pages * Fix – Fix Stripe IntegrationError for invalid currency when canMakePayment is called during WC Blocks store hydration * Fix – Fix the case of double exchange rate applied to the displayed fee amount in some scenarios. * Fix – Fix the logic of the WooPay button on single product pages. * Fix – Fix themed checkout extracting incorrect accent/link colors by using more specific CSS selectors for links, headers, and footers * Fix – Fix translation pattern in admin authentication email templates to use esc_html_x for proper i18n support * Fix – Fix WCPay account defaulting to Test mode when user selects Live during onboarding * Update – chore: remove subscriptions SCA dead code * Update – fix: ECE previews on block editor; Add amazon pay preview in block editor. * Update – fix: WC Beta unit tests compatibility * Update – Improve messaging when WooPayments is forced into test-only mode by environment configuration * Update – refactor: change UI of dynamic place order button settings * Update – refactor: deprecate is_amazon_pay_enabled setting in favor of enabled_payment_method_ids * Update – Replace old external icon with new arrow symbol on Preview cover letter button in disputes * Update – Updated iDEAL branding to ‘iDEAL / Wero’ for Wero brand transition compliance. * Update – Update evidence matrix for Product Not Received + Booking/Reservation disputes * Update – Use disputed amount to create a refund for lost disputes instead of an order total. Provide dispute fees and costs in the order view. * Dev – Add agent-address-comments workflow for automated PR comment resolution * Dev – Add architecture documentation and reference guides to CLAUDE.md * Dev – Add internal documentation for WooPayments Mode system (dev/test/live mode hierarchy) * Dev – Add PR reviewer and label requirements to CLAUDE.md * Dev – Add root AGENTS.md symlink for cross-agent discoverability * Dev – Align .claude/ documentation structure with CIAB Admin conventions. * Dev – Bump WC tested up to version to 10.6.0 * Dev – chore: move ECE utilities into separate files * Dev – chore: rename option for dynamic place order button * Dev – Comment: Add agent pipeline review stage with compound reviewer and WCPay- specific review rules * Dev – Comment: Make AGENTS.md the primary agent guidelines file, CLAUDE.md references it via @AGENTS.md per fieldguide * Dev – Fix flaky disputes e2e test by retrying field fill against async overwrite * Dev – Fix lint-staged to only lint staged CSS/SCSS files instead of all files. * Dev – Remove server-side appearance caching in favor of client-side caching * Dev – Respect custom dev-tools path in Docker setup script via local.env. * Dev – Show QIT report URL in CI workflow logs #### 10.5.1 – 2026-02-11 * Fix – Cache the affected orders check for the canceled auth fee remediation note to avoid an expensive query on every admin page load #### 10.5.0 – 2026-02-05 * Add – Add “Other” and “Booking/Reservation” product type support for dispute evidence (feature flag gated) * Add – Add ability to specify preferred communications email. * Add – Add evidence matrix entry for subscription_canceled + booking_reservation dispute combination * Add – Add remediation tool to fix incorrect analytics data from canceled authorizations * Add – feat: add Amazon Pay settings storage * Add – feat: add confirmation tokens feature flag * Add – feat: Amazon Pay ECE button front-end implementation * Add – Show an informative notice when a previously eligible merchant loses instant payout eligibility, instead of silently hiding the button. * Fix – Allow subscription renewals with saved Link payment tokens even when Link is disabled at checkout * Fix – fix: payment method title displayed on page editor for block-based checkout page * Fix – fix: subscription behavior with confirmation tokens * Fix – fix: text wrap of google pay/apple pay descriptions * Fix – Fix E2E test for non-admin WP-Admin access to expect ‘Connected’ instead of ‘Complete’ account status. * Fix – Fixed fatal error in email preview when viewing third-party plugin emails * Fix – Fixed iDEAL logo sizing in checkout to match other payment method logos. * Fix – Fix exit survey option not being preserved due to string type validation failure. * Fix – Fix migration log file cleanup compatibility with WooCommerce 8.6+. * Fix – Fix REST schema type for stripe_billing_subscription_count and stripe_billing_migrated_count from ‘int’ to ‘integer’ * Fix – Fix the case of double exchange rate applied to the displayed fee amount in some scenarios. * Fix – Fix the logic of the WooPay button on single product pages. * Fix – Improved subscription migration log file merging to use stream-based operations for memory efficiency and preserve chronological order. * Fix – Make sure that nonces are loaded correctly for the Add Payment Method page. * Fix – Prevent fatal error on sites running WooCommerce Subscriptions < 5.0.0 by not instantiating the Stripe Billing migrator when required functions are unavailable. * Fix – Update AVS Mismatch fraud filter copy to remove street check * Fix – Update dispute evidence fields to match specification document * Update – Bump the minimum required PHP version to 7.4 * Update – chore: update Alipay/WeChat Pay settings descriptions to state restrictions with regional versions * Update – Improved and simplified Visa Compliance dispute screen. * Update – refactor: ECE to use confirmation tokens instead of payment methods * Update – Tested up to WooCommerce 10.5.0 * Update – update: allow server-side control of confirmation token logic * Update – Use badge component in ‘Respond by’ column of the Disputes table for consistency with the ‘Response needed’ status badge * Dev – Add error logging for embedded KYC session failures to improve debugging. * Dev – Add non-interactive changelog command for automation * Dev – Add QIT E2E workflows for PR, scheduled, and pre-release testing with L- 1 WooCommerce version support. * Dev – Add WooCommerce core reference instructions to Claude Code configuration * Dev – Bump the version of WP in tested up to readme * Dev – chore: removed unused entries from the `wcpay_payment_fields_js_config` filter; ensured single call of the `wcpay_payment_fields_js_config` filter; * Dev – chore: remove unused ECE utilities * Dev – Clean up after rolling out the new Account Details in the Overview page. * Dev – Migrate subscription E2E tests to QIT test-package infrastructure. * Dev – refactor: scoping of UPE utilities at checkout * Dev – Remove flaky E2E admin analytics test in favor of QIT coverage * Dev – Stop using dynamic keys for the database cache and move cached payment methods to user meta. * Dev – [E2E][QIT] Migrate shopper subscription E2E test specs to QIT test-package #### 10.4.0 – 2026-01-07 * Add – Add duplicate charge documentation field for “Not Duplicate” dispute scenario. * Add – Adding ability to support payment method promotional campaigns (spotlight and badge treatments). * Add – feat: add Amazon Pay payment gateway class * Add – Open up new Account Details in the Overview page by enabling the feature flag by default * Add – When editing subscriptions, load payment methods whenever the customer is changed. * Fix – Add order note when WooPay checkout fails. * Fix – Attempt to fix when items remain in the cart after successful checkout ( Affirm). * Fix – Avoid race conditions while capturing payments. * Fix – Comment: Update links to the WooPayments fees documentation. * Fix – fix: ensuring that the Express Checkout Buttons show the correct amounts for currencies formatted in unusual ways (e.g.: USD with zero decimals) * Fix – fix: order attribution data on block-based checkout * Fix – fix: payment method definitions merge conflicts * Fix – fix: payment method logos compatibility with WooCommerce Blocks in WC>= 10.4 * Fix – fix: redirect message styles on block-based checkout page * Fix – Fix: Stripe Link availability on checkout outside of USD * Fix – fix: VAT error messages localization * Fix – fix: when WooCommerce Core sends the email about the activated payment method, redirect the merchant to the main settings page instead of a non-existent page. * Fix – Fix number format when converting order prices. * Fix – Implemented amount mismatch detection for an already paid order. * Fix – refactor: remove Stripe Link autofill modal button from checkout * Fix – Resolve JavaScript errors in WooPay Direct Checkout on sites with WooCommerce 10.4+ * Fix – Respect merchant tracking preferences for shopper events * Fix – Update wording related to the Visa Compliance disputes. * Update – chore: remove unused `wcBlocksCheckoutData` constant * Update – chore: update account fees docs URL * Update – Improve how server-side and client-side check tracking usage eligibility. * Update – refactor: convert Klarna payment method into a payment method definition * Update – refactor: Google Pay/Apple Pay settings storage consistency * Update – refactor: remove Afterpay_Payment_Method in favor of AfterpayDefinition * Update – refactor: remove payment_request_enabled_locations and woopay_enabled_locations in favor of a more future-proof express_checkout_product_methods express_checkout_cart_methods express_checkout_checkout_methods * Update – refactor: update payment method definition classes to delegate capabilities to PaymentMethodUtils * Update – update: bring back card borders on settings screens. * Update – update: payment method definition to determine eligible countries * Update – update: remove Google Pay test mode notice with live account, it’s no longer necessary * Update – update: usage of WP best practices * Update – Update dispute evidence fields and cover letter for Booking/Reservation duplicate disputes * Update – Update suggested evidence for the Subscription Cancelled dispute reason. * Update – Update wording on promo rate information tooltip * Update – Update “WooPayments” to “WooCommerce” mobile application in the Card Readers page. * Dev – Add validation to prevent Request classes from using empty hook names, which could cause fatal errors on PHP 8.0+ * Dev – Bump WC tested up to version to 10.4.0 * Dev – chore: remove CC_Payment_Gateway class in favor of WC_Payment_Gateway_WCPay * Dev – Cleanup unneeded asset. * Dev – Fix failing E2E tests * Dev – Log exceptions during the payment process. * Dev – Migrate remaining shopper E2E specs to QIT (my account, multicurrency, alternative payment methods) * Dev – refactor: add Apple Pay and Google Pay payment definitions * Dev – refactor: migrate remaining non-card payment methods into payment method definitions * Dev – refactor: updating some payment methods to use payment definitions instead * Dev – Update Jetpack packages. #### 10.3.1 – 2025-12-22 * Fix – Fix fatal error on WooCommerce Settings Payments tab caused by missing hook in Get_PM_Promotions request class #### 10.3.0 – 2025-12-10 * Add – Add backend support for additional dispute evidence types (event, booking, other) behind feature flag. * Add – Adding ability to support payment method promotional campaigns (spotlight and badge treatments). * Add – Allow non-reusable payment methods to be used for the manually renewed subscriptions. * Add – chore: add amazon pay feature flag. * Add – Handling of the Visa Compliance disputes with attention to a specific dispute fee. * Fix – Comment: Update links to the WooPayments fees documentation. * Fix – fix: ensuring that the Express Checkout Buttons show the correct amounts for currencies formatted in unusual ways (e.g.: USD with zero decimals) * Fix – fix: payment method logos compatibility with WooCommerce Blocks in WC>= 10.4 * Fix – fix: text color of payment method icons on checkout page when a dark background is used * Fix – Fix deprecation warning about usage of `parent` in callables. * Fix – Fix styling of the WooPay button to make sure that the spinner is visible when loading. * Fix – Fix WooPay express button text clipping * Fix – Refunds and fees should not be tracked for canceled authorizations * Fix – WooPay component spacing issues on blocks and classic checkout. * Update – Change payout texts for New Account Waiting Period to be consistent with new Account Details * Update – chore: update account fees docs URL * Update – Update “WooPayments” to “WooCommerce” mobile application in the Card Readers page. #### 10.2.0 – 2025-11-06 * Add – Add WooCommerce Tool to delete test orders. * Add – Sync store setup details with the Transact Platform. * Fix – Comment: fix JCB logo. * Fix – Fix – WCPay Subscriptions setting not persisting when unchecked * Fix – Fix missing payment method logos (JCB, CUP, CB) in checkout. * Fix – Fix payment method logos overflow in shortcode checkout after adding JCB and UnionPay logos. * Fix – Only show WooPay error messages for connection errors in available countries. * Fix – Prevent Express Checkout from being disabled on product page when updating quantity of variable products. * Fix – Prevent WooPayments-specific styles for the Checkout block to leak to other payment methods * Fix – Use Woo custom cap `pay_for_order` for validating the owner of order * Update – Avoid loading shipping zones when adjusting currencies for free shipping methods. * Update – Hide bundled subscription management UI while preserving renewal processing functionality * Update – Minor copy update to the delete test orders tool. * Update – Show message about bundled subscriptions until 10.2.0. * Dev – Add CLAUDE.md file to improve AI code assistance. * Dev – Bump WC tested up to version to 10.3.0. #### 10.1.1 – 2025-10-27 * Fix – Overrides the core `AbstractAutomatticAddressProvider`‘s `load_scripts` method to only run if the core setting (`woocommerce_address_autocomplete_enabled` is enabled). #### 10.1.0 – 2025-10-15 * Add – Disputes – Add a loading state to the “Challenge dispute” flow * Add – Pre-fill product type in dispute evidence form based on order products. * Fix – Add caching to address autocomplete token * Fix – Fix edge case when shipping information is added by mistake for digital products. * Fix – Fix _load_textdomain_just_in_time error when loading a non-existing payment method * Fix – Handle dispute counts for menu items between live and test mode * Fix – Single use coupons issues on WooPay. * Fix – Use Woo custom cap `pay_for_order` for validating the owner of order * Update – Show message about bundled subscriptions until 10.2.0. * Dev – Comment: Skip SSL verification when running the PHP tests locally. * Dev – Removed clear_cache method from the mutli-currency interface #### 10.0.0 – 2025-09-24 * Add – Add new feature flag for the dynamic checkout place order button, and new option on payment settings. * Add – New AccountDetails: Add feature flag, TypeScript definition, and basic component * Fix – Do not ask for shipping info for digital products dispute. * Fix – Fix Google/Apple Pay “State / County is required” error during checkout for Saudi Arabia * Fix – Fix possible errors when WooPay is enabled while the store is in Coming Soon mode * Fix – Name is required for the Affirm payment method. * Update – Improve messaging around test accounts and development mode on the Payments Overview page. * Update – Introduce account.deleted webhook processing for a smoother experience when an account is deleted from the Transact Platform. * Dev – Bump WC tested up to version to 10.2.0 * Dev – Fix flaky E2E test in addSavedCard function #### 9.9.0 – 2025-09-03 * Fix – Conditionally set Stripe Link wallet option based on payment method configuration * Fix – fix: adding some missing i18n wrappers * Fix – Fix checks for the billing details for the BNPL methods on the Pay for Order page. * Fix – Fixed WooPay terms and conditions text for merchants using blocks checkout. * Fix – Fix margins for phone number input and add styling to match other inputs * Fix – Fix VAT setup modal for unsupported merchants * Fix – Generate payment method details in WooPayments instead of Woo core, cache them for performance improvements. * Fix – Ignore webhooks whenever the order key in their body does not match the local order. * Fix – Show Activate payments notice in WooPayments Settings only for test accounts. * Update – update: label text on the support phone number in test mode * Update – update: settings page design audit. * Update – Update WP components for development and tests. * Update – Update “Finish setting up WooPayments” task to redirect to NOX flow. * Dev – Fix E2E subcription shopper test failures because the core changes text from “Sign up now” to “Add to cart” * Dev – Update JS packages mini-css-extract-plugin and shelljs #### 9.8.0 – 2025-08-13 * Add – Add address autocomplete to Checkout * Add – Add support for small screens on the evidence submission form. * Fix – Fix customer details section when name and/or email are very big. * Fix – Fix Google/Apple Pay “State / County is required” error during checkout for Croatia * Fix – Fix the icon border of the Steps component for a dispute. * Fix – Reset the enabled payment methods to default value on account reset. * Fix – Suppress sending completed-renewal-order email after dispute resolution * Update – As of this change, we stop bundling WordPress Components in favor of using the wp.components available in the WordPress installation. * Update – Make onboading pages use the pw.components available in the WordPress installation. * Update – Make the connect acctount components use the wp.components from the installation. * Update – Make the KYC onboarding use the WP components available in the installation. * Update – update: ensure Google Pay/Apple Pay can check out w/ LT addresses * Update – update: fraud protection rules to use WP components bundled within the WP installation * Update – Update documents page to use WP components available in the WordPress installation. * Update – Update loan page to use the installation WordPress components. * Update – Update the “Learn more about disputes” link in the confirmation screen of the disputes documentation. * Dev – Fix: enhances the robustness of the selectPaymentMethod method in end-to- end tests * Dev – Fix: Respond to a dispute e2e tests * Dev – Fix: select payment method shopper util * Dev – Removed all the Progressive Onboarding (PO) code. * Dev – update: use React 18 * Dev – Update tested WooCommerce version to 10.1.0 #### 9.7.0 – 2025-07-24 * Add – Add a confirmation screen to the new flow for submitting dispute evidence. * Add – Add Credit not processed logic for the new evidence submission form. * Add – Add external help link to the recomended documents section. … ## Meta * Version **10.7.1** * Last updated **3 jou ago** * Active installations **900,000+** * WordPress version ** 6.0 or higher ** * Tested up to **6.9.4** * PHP version ** 7.4 or higher ** * Languages * [Dutch](https://nl.wordpress.org/plugins/woocommerce-payments/), [Dutch (Belgium)](https://nl-be.wordpress.org/plugins/woocommerce-payments/), [English (Australia)](https://en-au.wordpress.org/plugins/woocommerce-payments/), [English (US)](https://wordpress.org/plugins/woocommerce-payments/), [Japanese](https://ja.wordpress.org/plugins/woocommerce-payments/), [Lao](https://lo.wordpress.org/plugins/woocommerce-payments/), [Spanish (Chile)](https://cl.wordpress.org/plugins/woocommerce-payments/), [Spanish (Colombia)](https://es-co.wordpress.org/plugins/woocommerce-payments/), [Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/woocommerce-payments/), [Spanish (Spain)](https://es.wordpress.org/plugins/woocommerce-payments/), and [Spanish (Venezuela)](https://ve.wordpress.org/plugins/woocommerce-payments/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/woocommerce-payments) * Tags * [apple pay](https://hat.wordpress.org/plugins/tags/apple-pay/)[credit card](https://hat.wordpress.org/plugins/tags/credit-card/) [google pay](https://hat.wordpress.org/plugins/tags/google-pay/)[payment](https://hat.wordpress.org/plugins/tags/payment/) [woocommerce payments](https://hat.wordpress.org/plugins/tags/woocommerce-payments/) * [Advanced View](https://hat.wordpress.org/plugins/woocommerce-payments/advanced/) ## Ratings 3.1 out of 5 stars. * [ 71 5-star reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/?filter=5) * [ 5 4-star reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/?filter=4) * [ 4 3-star reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/?filter=3) * [ 5 2-star reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/?filter=2) * [ 61 1-star reviews ](https://wordpress.org/support/plugin/woocommerce-payments/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/woocommerce-payments/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/woocommerce-payments/reviews/) ## Contributors * [ WooCommerce ](https://profiles.wordpress.org/woocommerce/) * [ Automattic ](https://profiles.wordpress.org/automattic/) ## Support Issues resolved in last two months: 7 out of 10 [View support forum](https://wordpress.org/support/plugin/woocommerce-payments/)