What’s new in WooCommerce Stripe 4.0: European payment gateways and a new credit card form

Written by Matty Cohen on January 9, 2018 Blog, News, Product News.

Stripe is a popular payment service provider for eCommerce stores worldwide, and we’re pleased to announce we’ve shipped a major release with a multitude of new features to enhance your experience of working with WooCommerce and Stripe.

  • Payment acceptance using European and other non-U.S. payment gateways
  • Fully PCI compliant credit card form on your checkout
  • Improved support for Apple Pay and the Web Payment Requests API
  • Simpler way to connect your WooCommerce store to Stripe

To ensure this update is stable, we’ve done a lot of testing on our side: Releasing beta versions, testing with our own library of extensions and themes, and testing with the most popular extensions used alongside WooCommerce Stripe. 👏

WooCommerce Stripe 4.0 includes lots of code improvements and should be fully backwards compatible with 3.1 and 3.0, but it’s still best to perform a backup before updating.

We recommend viewing our documentation on how to update, making a backup, and updating extensions before upgrading WooCommerce Stripe via WP Admin.

Read on for full details of what’s new in WooCommerce Stripe 4.0!

Accept payments using European and other non-U.S. gateways 🎉

WooCommerce Stripe now fully supports Stripe’s “Sources” feature, a new way to receive payments through Stripe. Payment gateways (“sources”) include the default payment gateway we all know and love, Apple Pay, Bitcoin, and a new selection of European and other non-U.S. payment gateways offered through Stripe.

Visit our WooCommerce Stripe documentation for a list of supported sources.

A list of several supported Stripe Sources, for illustration purposes.

You can enable as many of the above sources as you’d like, at the same time!

Heads up! A new and fully PCI-compliant credit card form ⚠︎

We’ve introduced a new credit card form on the WooCommerce checkout screen. This uses Stripe’s new “Elements” feature, which creates and displays the credit card form entirely via Stripe. This means the credit card form is fully PCI compliant, and the credit card information is sent directly to Stripe, without interacting with your store.

A new fully PCI-compliant credit card form, at checkout.

This may slightly change the look and feel of your credit card form, although we’ve done our best to preserve the design of the previous one.

The Stripe Elements credit card form, in action.

Get Stripe 4.0 and let us know what you think

Ready to give WooCommerce Stripe 4.0 a shot? Review our documentation about how to update, make sure backups are in place, and then grab the update in WP Admin.

We’d like to know what you think of the release and what you’d like in the next one, so let us know in Comments!

We’re here if you need us:

Please note that we are not able to diagnose or solve potential issues in blog comments. The fastest way to get in touch is one of the methods listed above.


86 Responses

  1. Christoph Schmück
    January 9, 2018 at 6:56 pm #

    Slows down my checkout extremely. The spinner isn’t stopping..

    Should wait for 4.0.1 …

    • Bradley Nillen
      January 12, 2018 at 7:52 am #

      I originally had problems with 4.0.0 and Apple Pay not displaying. Now, I just installed 4.0.1 and still have issue with Apple Pay not displaying; AND also having a new issue with Apple Pay killing mobile menu on product pages only (hamburger doesn’t do anything when pressing). First I noticed disabling the Stripe plugin allowed the mobile navigation to work. Then I unchecked the Apple Pay feature and my mobile menu works again. Confirmed on desktop, android, and iphone. Running Storefront theme and Woo 3.2.6.

  2. Dr. Peter H. Markesteyn
    January 9, 2018 at 6:58 pm #

    We sell “events”, not physical products.
    Is woocommerce able to do this!?
    Does it need an extension, like “eventcallendarPro”?

  3. Olivier Karfis
    January 9, 2018 at 7:11 pm #

    Hi. Thanks for the update.
    When “Enable guest checkout” is NOT enabled, will Apple Pay still check out as guest if the buyer is not logged in or will it now actually create a proper account?

  4. tex77
    January 9, 2018 at 7:27 pm #

    How is this “Fully PCI compliant”? Or maybe a better question is — what exactly do you mean by “Fully PCI compliant”?

    According to Stripe, on https://stripe.com/docs/security#validating-pci-compliance:
    – All Stripe users must validate their PCI compliance annually.
    – Stripe “Checkout” and Stripe “Elements” require the “SAQ A” form (the simplest method of PCI validation).

    So this new version-4 of the Stripe plugin for WooCommerce does NOT mean we don’t need to submit a PCI compliance form.

    And, I’m not clear how this new Stripe “Elements” version of the plugin is any better than the prior version, which (I think) offered Stripe “Checkout” mode — since both modes still require SAQ-A validation.

    I could be misinformed, or misunderstanding something here, but in any case, I’d like some clarification on what you mean by “Fully PCI compliant” for the new Stripe plugin.

    • Bryan Hoffman
      January 9, 2018 at 10:42 pm #

      I too would like to know how this new plugin differs from previous versions regarding PCI compliance.

      @tex77 If you check in your Stripe account under Business Settings > Compliance – If you can answer three questions about collecting card data with tokenization, on pages with SSL, and never saving card data on the server then Stripe will complete a PCI assessment for you.

      I think this was all available before so I’m not sure what has changed with version 4.0

    • Matty Cohen
      January 10, 2018 at 9:47 am #

      Hi tex77, Bryan,

      Stripe Elements (the new credit card form on checkout) is generated in a secured iFrame by Stripe. When a customer inputs their credit card information at checkout, this information goes directly to Stripe for payment, without interacting with your Woo store’s server at all. This helps to prevent against bad actors, and helps Stripe to assist with the simplest form of PCI compliance, and generate the self assessment questionnaire on your behalf, to complete and submit.

      • Ahamed
        July 9, 2018 at 2:04 pm #

        cant i remove the iframe which has wrapper the inputs? because in order to use card swipe we need to access the fields. because of iframe we couldn’t use it. so please help us!

  5. John Zabkowicz
    January 9, 2018 at 8:52 pm #

    Backed up, upgraded and tested successfully with one hiccup.

    The credit card icons are now missing from my checkout screen. They reference the file “stripe-paymentfonts.css”. As an example the Diners card has html conten value of “\f013”. Now my checkout screen just shows a square instead of card image. I’ve cleared cache etc. Any suggestions?

    • Bryan Hoffman
      January 9, 2018 at 9:15 pm #

      If you are not seeing the icons, the webfont might be missing… On one of my sites it is located here: url(../paymentfonts/paymentfont-webfont.eot) – this would be in relation to the css file.

      Can you check if it’s there?

      You could also be running into a cache issue even after clearing your browser cache. Can you send a link?

      • John Zabkowicz
        January 9, 2018 at 9:31 pm #

        Thanks, Bryan. I’m at: https://sanitaryfittings.us/ Still trying to figure this out…

        • John Zabkowicz
          January 9, 2018 at 9:35 pm #

          Just noticed “squares” only show up in Chrome. IE shows nothing. Also, the previous version of Stripe showed icons just fine so I’m really trying to figure out what else changed here.

        • Bryan Hoffman
          January 9, 2018 at 10:13 pm #

          I think you are running into a font issue with your theme… The credit card icons are trying to use the theme font to render (Heebo) which won’t work. This a bit of a sledgehammer, but try adding this to your stylesheet:

          .woocommerce .woocommerce-checkout #payment .stripe-pf {
          font-family: PaymentFont;

          • John Zabkowicz
            January 9, 2018 at 10:18 pm #

            That worked great, Bryan. Thanks for your help.

          • Marina Pape
            January 10, 2018 at 4:55 pm #

            Bryan, hero!

  6. Kiril Climson
    January 9, 2018 at 9:09 pm #

    Interesting integration with Google Pay.

    Is there a way to remove the old checkout button is Google Pay is offered? Vice versa?

    • Matty Cohen
      January 10, 2018 at 4:59 pm #

      Hi Kiril,

      Thanks for your suggestion.

      While there isn’t currently a quick way to do this, I’d recommend logging this as an enhancement request on the WooCommerce Stripe GitHub repository, for further discussion.

      Thanks in advance!

  7. Jake
    January 9, 2018 at 9:35 pm #

    So, let me get this right, implementing this plugin will enable me to accept secure credit card payments on a http (not https) website by using stripe own ssl certificate? Is that right?

    • Bryan Hoffman
      January 9, 2018 at 10:48 pm #

      Stripe will require you to load checkout pages using https – whether it’s technically possible or not.

  8. Richard Udicki
    January 9, 2018 at 10:29 pm #

    Is it necessary or advised to upgrade the Stripe API version when performing this WooCommerce Stripe plugin update?

    • Matty Cohen
      January 10, 2018 at 5:00 pm #

      Hi Richard,

      WooCommerce Stripe 4.0 uses the latest version of the Stripe API. Any settings for the API version in your control panel should be at the latest version as well, although there should be no changes required, to my knowledge.

  9. Robert
    January 9, 2018 at 10:52 pm #

    I just upadated and it all looks good, but Apple Pay has now gone? Was working nicely before. Am I missing something?

    • Justin
      January 9, 2018 at 11:07 pm #

      Same issue. Apple Pay not functioning. Checked Stripe settings and the domain is still verified…

    • Brad Nillen
      January 11, 2018 at 5:33 pm #

      Update broke my Apply Pay as well. Just successfully configured the night before. Bummed, especially after reading how much testing went into this.

  10. Nicholas
    January 9, 2018 at 11:06 pm #

    Does this allow subscriptions to be used with apple pay, any idea when that will be supported?

    • Dorian
      January 10, 2018 at 12:12 am #

      Does stripe provide a card reader?

  11. milanjku
    January 10, 2018 at 12:44 am #

    Great work! Unfortunately, the payment process got very slow with the new update.

  12. vu nguyen
    January 10, 2018 at 1:19 am #

    Is it possible to remove the Apple Pay and the Pay button on the single product page?

  13. J. Alves
    January 10, 2018 at 3:47 am #

    I hate this new update. That is all.

  14. Stan Verhoeven
    January 10, 2018 at 10:24 am #

    I own a very small rental shop, where customers can rent polaroid cameras. Is it possible to authorise a creditcard with Stipe 4.0 and manullaly hold a certain amount or “release” a certain amount from customers? For example like some kind of deposit?

  15. Eren Ozkan
    January 10, 2018 at 10:33 am #

    Hello I am using stripe for my website http://www.boutiqueottoman.com Is this plug-in has 3D Secure feature?

    • Matty Cohen
      January 10, 2018 at 5:12 pm #

      Hi Eren,

      Yes, WooCommerce Stripe 4.0 includes support for 3D Secure.

  16. Noor
    January 10, 2018 at 10:49 am #

    Does this support Apply Pay subscription?

    • Matty Cohen
      January 10, 2018 at 5:15 pm #

      Hi Noor,

      While this is technically supported when using WooCommerce Subscriptions, it’s worth noting the following from Stripe’s documentation:

      Apple Pay tokens can be used to create one-off payments or subscriptions. For repeat purchases that are not related to a subscription, we recommend you create single-use tokens. Your customer must authenticate with the Apple Pay payment sheet each time—attempting to reuse payment information for a non-subscription payment can result in it being declined.

      A customer would need to re-authenticate with the payment sheet periodically, before being charged the recurring payment.

  17. Robert
    January 10, 2018 at 10:56 am #


  18. Kraken
    January 10, 2018 at 10:58 am #

    It’s probably a good update under the hood. But the new checkout card / expiry / cvc form is terrible. Will be a conversion killer on some sites I am sure – whether you go for the in line design or the row of 3 fields, they’re poorly labelled.

  19. anestis kalligas
    January 10, 2018 at 11:01 am #

    What about eshops in Greece, can we use this payment gateway in Greece?

  20. Ray Gillespie
    January 10, 2018 at 11:36 am #

    We’ve been using Stripe through WooCommerce for a while now, on several websites, and a couple of the features listed as “new” here are things that we have had for months:

    – Payment acceptance using European and other non-U.S. payment gateways
    – Fully PCI compliant credit card form on your checkout

    The current installations use Stripe.js (which is fully PCI compliant) and we’ve been taking card payments from UK/EU cards for a long time. Can you explain what the difference is here?


    • Matty Cohen
      January 10, 2018 at 5:02 pm #

      Hi Ray,

      With pleasure.

      The new features enable payments to be received via European and other non-U.S. banks. For example, in the Netherlands, a merchant can now receive their funds using iDeal, and a local Dutch bank account.

  21. Dietmar Hohn
    January 10, 2018 at 2:28 pm #

    Is subscription with recurring payment and SEPA now working? This would be great!

    • Matty Cohen
      January 10, 2018 at 5:11 pm #

      Hi Dietmar,

      This is now possible using SEPA Direct Debit, WooCommerce Stripe, and WooCommerce Subscriptions, yes.

      For more information on how this works with SEPA Direct Debit, please do see Stripe’s documentation.

  22. Mo Zhang
    January 11, 2018 at 12:11 am #

    Still no ACH support?

  23. Ella
    January 11, 2018 at 6:25 am #

    Sorry for newbie question, but does this mean we can use Stripe on http:// websites now?

    • Matty Cohen
      January 11, 2018 at 4:55 pm #

      Hi Ella,

      I would highly recommend an SSL certificate for any website created which is receiving payments. Although technically possible to use HTTP, I’d advise to err towards using HTTPS (adding an SSL certificate to your website) for each website in your care.

      Most hosts offer a free SSL certificate, these days, using efforts such as Lets Encrypt.

  24. Junior
    January 11, 2018 at 12:33 pm #


    Have you guys fixed the Stripe Payment Gate Way translation yet?

    There are a lot of people facing issues to translate it.


  25. Liam
    January 12, 2018 at 11:23 am #

    Hey Matty,

    The new fully PCI compliant form is great, however, it’s super ugly – the big grey form sticks out like a sore thumb!

    Is there any way to ditch the Stripe ui stylesheet and replace with our own custom styles?


    • Matty Cohen
      January 12, 2018 at 1:25 pm #

      Hi Liam,

      It’s definitely possible to customise the styling fo the credit card form, yes. Stripe has documentation around how this can be done.

      I’d recommend logging a ticket with our Happiness Engineers, if you have additional questions around this.

      • Liam
        January 13, 2018 at 1:24 pm #

        Great – thanks Matty!

  26. Liam
    January 12, 2018 at 11:56 am #

    Hey Matty,

    Another question:

    How can a U.K. based store take advantage of Stripe sources gateways – such as iDeal – without changing the store’s currency to Euros?

    • Matty Cohen
      January 12, 2018 at 1:28 pm #

      Hi Liam,

      Generally speaking, a U.K. merchant should use the U.K. supported payment option. Customers can use their local credit cards, regardless of where the card was issued. Sources is intended to be merchant-centric (for example, a Dutch merchant can set up iDeal).

      To run iDeal in the U.K., you’d most likely need to interact with a Dutch bank account (as a merchant) and set the price to Euros. It’s not currently possible to use iDeal without selling in Euros. You could set up the currency converter widget, though.

      • Liam
        January 13, 2018 at 1:30 pm #

        Ok, got ya!

        A bit off topic, but are you aware of any robust currency switching solutions? And, if so, do you think that it would be possible for sources to work?

        • Olivier Karfis
          January 16, 2018 at 3:55 pm #

          Hello Liam. I’ve been running the Aelia Currency Switcher plugin on my site for almost 2 years now. Works great and works with Stripe and others (I natively charge in USD, EUR and GBP. Support is awesome too (not affiliated, just a fan). Cheers Olivier

          • Liam
            January 16, 2018 at 9:35 pm #

            I’ll check it out – thanks Oliver!

            P.S. I can’t help but think it’s about time WooCommerce brought out an official solution.

  27. vasvee niyamosot
    January 12, 2018 at 9:37 pm #

    Hi. Thanks for the update.

  28. Adrian Wackernah
    January 13, 2018 at 6:01 pm #

    Hi Matty, if I have more then one woocommerce (more domains) connected to my stripe account and if I like to get Giropay activated, how do I setup a webhook in stripe dashboard? Each WC install shows me a different return url?

    • Adrian Wackernah
      January 14, 2018 at 11:44 am #

      Stupid question – after time to search about I found a solution. Sorry …

      • Matty Cohen
        January 17, 2018 at 11:59 am #

        I’m really glad you found a solution here, Adrian.

        For anyone reading along at home, Stripe has a great document on webhooks which is a great reference here.

  29. Collins Ngetich
    January 15, 2018 at 7:17 am #

    Do you have options for mpesa support? It’s about time you think about Africa’s largest payment platform with 19million users currently

  30. طراحی سایت
    January 15, 2018 at 12:24 pm #

    I really need to this article. Thank a lot.

  31. Julien
    January 16, 2018 at 1:50 pm #

    Thanks for this update and the introduction of 3D Secure !

    It seems that the labels on top of the fields have disapeared (credit card number / expiry date / CVC) to be replaced by the only “credit card/debit card” label.

    Is there anyway to get them back ?

    Best regards

  32. Pradeep Kumar
    January 16, 2018 at 2:34 pm #

    Great Service!! When can we expect this WooCommerce Stripe 4.0 in India? Thanks.

    • Kat
      January 25, 2018 at 10:18 pm #

      Hi there, countries served by Stripe are determined by Stripe, not WooCommerce so it will be up to them. You can sign up to be notified on their page: https://stripe.com/global Cheers! 🙂

  33. Abdul Rahaman A Rauf
    January 16, 2018 at 5:36 pm #

    Stripe and paypal is not available to Ghanaians and I live in Ghana so how do I get an online payment gateway to my woocommerce shop?

  34. Aime
    January 17, 2018 at 2:09 am #

    Any chance of Bitcoin being added in the near future?

    • Matty Cohen
      January 17, 2018 at 12:00 pm #

      Hi Aime,

      Bitcoin is a supported source in Stripe, today. 🙂

      • Olivier Karfis
        January 25, 2018 at 7:30 pm #

        Although Stripe has announced they are phasing out Bitcoin in the next 3 months…

  35. Brad
    January 17, 2018 at 4:56 pm #

    Can someone explain the intended behavior of Apple Pay? Before the 4.0.0 update it was working when you went to checkout. Since updating to 4.0.0 and 4.0.1, it is not displaying on the checkout page And it breaks mobile navigation menu on my product pages. I don’t follow if this is by design but it doesn’t appear to be working as described in the documentation. Any thoughts?

  36. Floral Maxi Dress
    January 19, 2018 at 9:14 am #

    Well, Im glad they just release a fix for most of the problems after the first update. All the payment style is working just fine now.

  37. Julien
    January 19, 2018 at 11:45 am #


    Thanks for the new updates. Glad that the labels are back 😉
    But now the language folder has disapeared. together with the .pot file.
    Can you please put it back.

    Best regards

  38. Bluehost Review
    January 23, 2018 at 4:21 pm #

    Glad to see Bitcoin in Stripe 4.0 🙂

  39. Avenir
    January 23, 2018 at 4:26 pm #

    I will definitely check it out.

  40. completimagero
    January 23, 2018 at 5:59 pm #

    Bitcoin in Stripe 4.0 ?

  41. Gildun Abdelkrim
    January 25, 2018 at 6:02 pm #

    Can we have an idea of when we’ll be able to process Apple Pay payment for recurrent payments (such as subscriptions).

    Thanks a lot for what you’ve done, the new PCI form looks fire !

  42. Faraz
    January 25, 2018 at 6:31 pm #

    When Stripe is coming to India ? Stripe is awesome and we love it.

  43. Perry
    January 25, 2018 at 7:44 pm #

    Bitcoin has now been phased out with Stripe.

    I think this update is a good one. Woocommerce and stripe are a great match.

  44. Floral Dress Rhalyn
    January 25, 2018 at 7:48 pm #

    Thanks for the feedback. After speaking with the theme creator they helped me to delete the extra “proceed to payment” button, added by the plugin update. Is there anyways we can get hid of the chrome payment button tho?

  45. Roopesh
    January 26, 2018 at 2:41 pm #

    Hi I have a store setup and primarily operate in South Africa.Can I use this on my site?

  46. Makuv
    January 29, 2018 at 6:07 pm #

    Extraordinary work! Sadly, the installment procedure got moderate with the new refresh. I will look at it.