22 Comments

  1. Marcus Tibesar
    · Reply

    Question – does Woocommerce charge a percentage in addition to what Stripe charges for each transaction?

    Report

    • Matt Mullenweg
      · Reply

      It’s the same. :) No additional costs, just a much better user experience.

      Report

      • Stephen Vaughan
        · Reply

        Hi Matt,

        While I have you there, when will WooCommerce go to the block editor? I don’t mean in terms of blocks for front end layout, more in terms of UI for the WooCommerce data entry.

        I have a rudimentary plugin that removes the block editor parts on custom post types. It just leaves custom field metaboxes that one might create when using ACF and Toolset. Good for where you might be restricting a user to data entry where the front end is catered for by template made elsewhere with blocks.

        The reason I like this set up a lot more now rather than the classic UI is the fact that the block editor UI saves and updates asynchronously. This saves a lot of time where the older classic UI has to reload for these actions to take place (3.8Mb bandwidth where I work).

        I appreciate that converting the WooCommerce UI is probably not a trivial task for developers.

        Report

    • M
      · Reply

      Developers of payment gateways are remunerated by the payment providers/collectors on a revenue share basis, in this case, it’s Stripe.

      But those agreements are usually time bound (at about two years). However, with this new “private label” payment gateway, WooCommerce/Automattic has a stronger position in negociations for a longer time period or even an unlimited one. The reason being they could try to switch their payment collector if they don’t get the period length they would like.

      Report

  2. Glenn Martin
    · Reply

    The Jetpack requirement is the solitary reason I don’t use this.

    That’s such an unfortunate requirement.

    Report

    • M
      · Reply

      Indeed, I feel like it’s less a JetPack than it is an Anvil.

      Report

    • Brent Shepherd
      · Reply

      Hi Glenn, we’re working to bring the connection to WordPress.com that Jetpack provides into the WooCommerce Payments plugin itself, so that you can choose to use the Jetpack plugin if you want the security, performance, and marketing tools it provides, rather than being required to use it to use WooCommerce Payments.

      Report

  3. Callum
    · Reply

    While the feature itself looks good minus the Jetpack requirement, I don’t understand why all of WooCommerce’s menu items aren’t all placed under the WooCommerce menu item?

    The addition of the standalone analytics menu item was bad enough, but Payments is just ridiculous. If a Not-for-profit is using WordPress for example, they are more than likely going to be collecting payments through a forms plugin and a donation plugin in addition to Woocommerce. The expectation of a user is going to be that Payments is an all-inclusive payment area for their site. Already seeing a similar thing with people being frustrated with the Analytics menu link.

    Report

  4. Yordan Soares
    · Reply

    I just translate this plugin to Spanish and saw in a string that there is a Github repository, but I tried to access and didn’t appear, it’s a private repository?

    Report

    • Brent Shepherd
      · Reply

      Hi Yordan, thanks for translating the plugin! For now the GitHub repository is private. We’ve discussed making it public and hope to be able to do that in future in some capacity.

      Report

  5. Brent Shepherd
    · Reply

    Hi Callum, thanks for the feedback. The Woo design team are reviewing the WooCommerce navigation to look for ways to fit everything it takes to manage a successful store within WordPress.

    To give some idea of the scope of the challenge, the team just stated usability testing on their 3rd iteration since February.

    I don’t understand why all of WooCommerce’s menu items aren’t all placed under the WooCommerce menu item?

    The key reason WooCommerce Payments has its own top level menu right now is because it has sub-menu items for screens a store owner will visit regularly (potentially many times per day for active stores).

    With the current design, a store owner can get to their deposits, disputes and other transactions in a single click. If we were to add Payments as a submenu on WooCommerce and hide those pages behind tabs, we’d require store owners to make extra clicks to get to those pages. We’d also make it harder to discover those pages for new merchants.

    When putting WooCommerce up against pure eCommerce competitors, like Shopify, this would make WooCommerce, and by extension WordPress, the sub-par experience for eCommerce. Something we need to avoid.

    If a Not-for-profit is using WordPress for example, they are more than likely going to be collecting payments through a forms plugin and a donation plugin in addition to Woocommerce.

    It seems like the core issue in that scenario is two independent eCommerce systems being used on a single site. The WooCommerce top level menu item is a symptom of that and there would be others, potentially worse, like if the merchant needs to have PayPal Standard sending two IPNs back to the same site with different payloads which can conflict.

    While it’s inevitable in an open ecosystem that this can happen, the ideal situation for site owners is to have one system that serves their needs. IMO that’s what we should all be working towards, whether we are working on WooCommerce, a forms plugin, or a donation plugin, because the impact of plugins conflicting usual ends up in reputation damage to WordPress itself.

    Report

    • Jake
      · Reply

      I think the main point was that WooCommerce is often an add-on to an existing site that handles many aspects beyond eCommerce.

      A sub-menu item does cause more clicks potentially for eCommerce tasks. Using a dashboard or tabbed interface is in my opinion a great solution, because I believe that too many menu items cause confusion. If you take for example a blog, portfolio, business, or non-profit site they all may have eCommerce but also many other functions for their site. Having made many destination resort sites that handle everything you can imaging the best solutions were fewer menu links where possible to funnel users, and then provide options.

      For this reason, I also have to agree with Callum and his original assertion that a single main menu item is more appropriate.

      Further, that on existing installs I have to use the following filters to hide overhanded implementation on the main menu is telling.

      /**
       * Remove WooCommerce Admin Notices
       */
      add_filter( 'woocommerce_helper_suppress_admin_notices', '__return_true' );
      
      /**
       * Disable the WooCommerce Marketing Hub Menu
       */
      add_filter( 'woocommerce_marketing_menu_items', '__return_empty_array' );
      //add_filter( 'woocommerce_admin_disabled', '__return_true' );

      Report

  6. Kevin Kovadia
    · Reply

    This is really a great initiative. I am waiting for the day when WooCommerce Payments is active in India also. Till now, I am using Instamojo.com as my payamnet gateway for WooCommerce site.

    Report

  7. David Anderson
    · Reply

    Presumably this plugin is largely based around the Stripe API (even if not calling it directly). It might be nice for someone to fork it, strip out the woocommerce.com stuff, and make it work directly with the existing WooCommerce/Stripe extension. As the article says, managing your payment inside your dashboard is nicer than switching between multiple dashboards.

    Taking that thought further, it would have been better for the ecosystem generally if the plugin was split, so that the dashboard/interface bits were available for all payment gateways, and the woocommerce.com-linked bits separate. It’d be nice to have something that all payment gateways could hook into. Even for people using the woocommerce.com gateway may have other gateways on their site for payment methods that Stripe don’t handle (e.g. PayPal).

    Report

  8. Jacob Jack
    · Reply

    A very useful and innovative feature that has been introduced! It will definitely provide ease to a lot of users!

    Report

  9. Anh Tran
    · Reply

    This is awesome! I like the idea and the implementation. The screenshots look nice, too.

    One question: do shop owners need a Stripe account to receive payments?

    Report

  10. Web Guy
    · Reply

    I’m working on WooCommerce websites for the last 5+ years. On woo-commerce website payment gateway integration is easy though I’ll use woocommerce own payment option.

    Report

  11. Steve
    · Reply

    What about Bitcoin payments being supported out of the box? Decentralized payments anybody? blockchain??

    Report

    • Justin Tadlock
      · Reply

      I don’t know enough about cryptocurrencies to know whether it’s worth it. However, is the user base wide enough for it to be a default part of the plugin rather than as an add-on payment gateway like it is now? What percentage of users are going to pay with Bitcoin, for example, in comparison to a standard debit/credit card?

      Report

      • Steve Albur
        · Reply

        So here in Argentina, our national fiat currency has collapsed due to hyper inflation. Lot of vendors accepting the USD and bitcoin payments. Entire society is going through a sea of change.

        We really do not want to transition to another fiat currency which the government prints and supplies their relatives who use it to purchase prime properties devaluing the currency for everyone. If WordPress can adopt BTC and help spread usage that would be great.

        Report

Leave a Reply to Jacob Jack Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: