Accept Visa, MasterCard, American Express, Discover, JCB, Diners Club, SEPA, Sofort, 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:
- Czech Republic
- Hong Kong
- New Zealand
- Puerto Rico
- 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.
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 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”.
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.
Automatic updates should work like a charm; as always though, ensure you backup your site just in case.
Does this support recurring payments, like for subscriptions?
Does this require an SSL certificate?
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.
Laguntzaileak eta Garatzaileak
“WooCommerce Stripe Payment Gateway” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.Laguntzaileak
WooCommerce Stripe Payment Gateway 31 eskualde-ezarpenetara itzuli da. Eskerrik asko itzultzaileei beraien ekarpenengatik.
Garapena interesatzen zaizu?
7.0.2 – 2023-01-11
- Fix – Expand charges object from incoming webhooks using Stripe API version 2022-11-15.
- Fix – Expand refunds on charge object from incoming webhooks using Stripe API version 2022-11-15.
- Fix – Fix critical error on PHP 8+ when php_uname() is disabled