WooCommerce Stripe Payment Gateway

Beskrywing

Accept Visa, MasterCard, American Express, Discover, JCB, Diners Club, SEPA, iDEAL, giropay, Alipay, and more directly on your store with the Stripe payment gateway for WooCommerce, including Apple Pay, Google Pay, and Microsoft Pay for mobile and desktop.

Take Credit card payments easily and directly on your store

The Stripe plugin extends WooCommerce allowing you to take payments directly on your store via Stripe’s API.

Stripe is available for Store Owners and Merchants in:

  • Australia
  • Austria
  • Belgium
  • Brazil
  • Bulgaria
  • Canada
  • Cyprus
  • Czech Republic
  • Denmark
  • Estonia
  • Finland
  • France
  • Germany
  • Greece
  • Hong Kong
  • Ireland
  • Italy
  • Japan
  • Latvia
  • Lithuania
  • Luxembourg
  • Malaysia
  • Malta
  • Mexico
  • Netherlands
  • New Zealand
  • Norway
  • Poland
  • Portugal
  • Puerto Rico
  • Singapore
  • Slovakia
  • Slovenia
  • Spain
  • Sweden
  • Switzerland
  • United Kingdom
  • United States
  • with more being added

Stripe is a simple way to accept payments online. With Stripe you can accept Visa, MasterCard, American Express, Discover, JCB, and Diners Club cards, even Bitcoin, directly on your store.

Why choose Stripe?

Stripe has no setup fees, no monthly fees, no hidden costs: you only get charged when you earn money! Earnings are transferred to your bank account on a 7-day rolling basis.

Stripe also supports the WooCommerce Subscriptions extension and re-using cards. When a customer pays, they are set up in Stripe as a customer. If they create another order, they can check out using the same card. A massive timesaver for returning customers.

Apple Pay Support

WooCommerce Stripe includes Apple Pay support, which means customers can pay using payment details associated with their Apple ID. Checkout is now just an authorization (Touch ID or Face ID) away on both mobile and desktop. Only supports simple, variable, and Subscription products for now. More support to come.

Web Payments API Support

WooCommerce Stripe includes Web Payments API support, which means customers can pay using payment details associated to their mobile devices, in browsers supporting the Web Payments API (Chrome for Android, amongst others). Checkout is now just a few taps away on mobile. Only supports simple, variable, and Subscription products for now. More support to come.

Screenshots

  • The Stripe payment gateway settings page used to configure the plugin.
  • Offer a range of payment options such as local methods and express checkouts.
  • Allow customers to save payment methods and add new ones for their future purchases.
  • Apple Pay and other express methods can be added to product pages, cart, and checkout.

Installation

You can download an older version of this gateway for older versions of WooCommerce from here.

Please note, v4 of this gateway requires WooCommerce 3.0 and above.

Automatic installation

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of the WooCommerce Stripe plugin, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.

In the search field type “WooCommerce Stripe Payment Gateway” and click Search Plugins. Once you’ve found our plugin you can view details about it such as the point release, rating, and description. Most importantly, of course, you can install it by simply clicking “Install Now”, then “Activate”.

Manual installation

The manual installation method involves downloading our plugin and uploading it to your web server via your favorite FTP application. The WordPress codex contains instructions on how to do this here.

Updating

Automatic updates should work like a charm; as always though, ensure you backup your site just in case.

Kwel-vrae

Does this support recurring payments, like for subscriptions?

Yes!

Does this require an SSL certificate?

Yes! In Live Mode, an SSL certificate must be installed on your site to use Stripe. In addition to SSL encryption, Stripe provides an extra JavaScript method to secure card data using Stripe Elements.

Does this support both production mode and sandbox mode for testing?

Yes, it does – production and Test (sandbox) mode is driven by the API keys you use with a checkbox in the admin settings to toggle between both.

Where can I find documentation?

For help setting up and configuring, please refer to our documentation.

Where can I get support or talk to other users?

If you get stuck, you can ask for help in the Plugin Forum.

Aanbevelings

Oktober 1, 2024 1 reply
During the latest updates, we were concerned about the future use of sources. The work of the developers seems to have paid off, as the migration of sources to paymentMethod is now carried out correctly without any intervention in the code.
September 4, 2024 1 reply
After persevering with this plugin over many years, the quality has notably reduced over the past 12 months or so. Several bugs have slipped through the cracks and the developers a missing things. I assume this is due to issues in quality control behind the scenes. Issues on Github remain unfixed after several months, and regression bugs pop up in almost every version. We’ve finally jumped ship and started using another author’s plugin instead.
Augustus 25, 2024 1 reply
Great plugin, works fine, there were some issues but they seem to be fixed now.
Julie 22, 2024 7 replies
Since the customer’s status is changed twice after ordering and payment,There was a bug where the same email was sent twice to administrators and customers.When I looked into it, it seems like it’s a bug that has been around for several years and hasn’t been fixed. Although it is a genuine WooCommerce plugin, what is it like? When I changed to this plugin, it was easy to set up, looked great, and solved the problem right away.Payment Plugins for Stripe WooCommerce
Julie 4, 2024 1 reply
Rather than work with a theme and do proper testing to figure out a bug caused by their new stripe checkout experience they just keep blaming the theme creator.Multiple times I pointed out I contacted the theme creator and yet they always kept sending me away. Even after the theme creator highlighted to them that their latest version is loading script that hides the coupon field unless counter acted through CSS. not ideal at all
Read all 192 reviews

Contributors & Developers

“WooCommerce Stripe Payment Gateway” is oopbron sagteware. Die volgende mense het bygedra tot die ontwikkeling van hierdie uitbreiding:

Contributors

“WooCommerce Stripe Payment Gateway” has been translated into 33 locales. Thank you to the translators for their contributions.

Translate “WooCommerce Stripe Payment Gateway” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

8.7.0 – 2024-09-16

  • Add – Introduces a new promotional surface to encourage merchants with the legacy checkout experience and APMs enabled to use the new checkout experience.
  • Fix – Prevent duplicate failed-order emails from being sent.
  • Fix – Support custom name and description for Afterpay.
  • Fix – Link APM charge IDs in Order Details page to their Stripe dashboard payments page.
  • Fix – Fix Indian subscription processing by forcing the recreation of mandates during switches (upgrading/downgrading).
  • Fix – Add back support for Stripe Link autofill for shortcode checkout.
  • Fix – Fix undefined method error caused by settings refactor when connecting Stripe account.
  • Fix – Fix multiple compatibility issues and deprecation warnings when running the extension on PHP 8.1.
  • Fix – Re-connect promotional surface blinking after disappearing for merchants that have already connected their Stripe account.
  • Fix – Fix possible fatal errors when Stripe settings format is invalid during account connection.
  • Fix – Clear webhook state after reconfiguring webhooks to remove outdated error and success statuses.
  • Fix – Prevent payment methods from being detached from Stripe customers on non-production sites when a WP user is deleted with the new checkout experience enabled.
  • Add – Log incoming webhook events and their request body.
  • Add – Show UPE payment methods in saved order on block checkout page.
  • Add – Display UI elements for connection type and expired keys status for Stripe accounts linked via the WooCommerce Stripe App.
  • Tweak – Delete the notice about the missing customization options on the updated checkout experience.
  • Fix – Prevent fatal error when canceling uncaptured orders by ensuring refunds array is expanded in Stripe API response.
  • Fix – Fix error in saving settings when express payment methods are disabled.
  • Fix – Catch error when getting intent from order.
  • Fix – Handle undefined array key when no matching customer account is found when guest customers checkout.
  • Tweak – Update capabilities to payment methods mapping.
  • Fix – Address QIT Security test errors.
  • Fix – Address QIT PHPStan test errors.
  • Update – Specify the JS Stripe API version as 2024-06-20.
  • Tweak – Use order ID from ‘get_order_number’ in stripe intent metadata.
  • Fix – Ensure payment tokens are detached from Stripe when a user is deleted, regardless of if the admin user has a Stripe account.
  • Fix – Address Klarna availability based on correct presentment currency rules.
  • Fix – Use correct ISO country code of United Kingdom in supported country and currency list of AliPay and WeChat.
  • Fix – Prevent duplicate order notes and emails being sent when purchasing subscription products with no initial payment.
  • Add – Display an admin notice on the WooCommerce > Subscriptions screen for tracking the progress of SEPA subscriptions migrations after the legacy checkout is disabled.
  • Add – Introduce a new tool on the WooCommerce > Status > Tools screen to restart the legacy SEPA subscriptions update.
  • Fix – Remove the Stripe OAuth Keys when uninstalling the plugin.
  • Fix – Resolve an error for checkout block where ‘wc_stripe_upe_params’ is undefined due to the script registering the variable not being loaded yet.

See changelog for all versions.