• I have been using Stripe for years and didn’t have many issues however when I noticed WooCommerce had this plugin I thought I would give it a go, the payments are still being processed by Stripe so why not.

    Been using this now for some time, not had many issues, the issues I have had I contacted support and within a few minutes chatting to someone and get any issues sorted pretty quickly.

    With this all being integrated into WooCommerce it makes the whole experience for me a load smoother, just click and see my transactions, drill into transactions from orders, see my deposits etc.

    Few items I would love them to invest in would be
    1) Dynamically showing the payment options, showing the card section before an address is filled seems pointless. Not a huge issue but would makes things more clear to customers. This could be more WooCommerce vs WooPay
    2) Making it clear to a customer that a payment has failed due to an incorrect “billing” address, or alternatively allowing us to set the fraud level we are happy with so it’s not as stringent. Missed some sales because of this which is a bummer considering with Stripe this was never an issue.
    3) Storing the fees in the metadata (have a feeling this may have just been implemented) I run some MySQL queries so I can easily identify sales, volumes, etc… just some analysis and PayPal store the fees as meta but WooPay did not meaning I had to scrape the notes for the fee values.

    Overall very happy, will continue to use.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Chris M. – a11n

    (@csmcneill)

    Howdy @idonaldson1,

    I’m glad to hear that you’re enjoying WooCommerce Payments so far!

    I greatly appreciate you sharing your candid feedback. I wanted to touch on the three items you shared:

    Dynamically showing the payment options, showing the card section before an address is filled seems pointless. Not a huge issue but would makes things more clear to customers. This could be more WooCommerce vs WooPay

    This definitely seems more of a WooCommerce core issue, but it’s possible that this could be implemented at the gateway level. I’ll share this with the product team as a potential enhancement.

    Making it clear to a customer that a payment has failed due to an incorrect “billing” address, or alternatively allowing us to set the fraud level we are happy with so it’s not as stringent. Missed some sales because of this which is a bummer considering with Stripe this was never an issue.

    If a provided postcode doesn’t match what the card-issuing bank has on file, it will return an incorrect_zip code. When this happens, the following error should be displayed to the customer:

    We’re currently working on refining this system a little bit with our partners at Stripe, and we plan on introducing some more granular, customizable fraud prevention tools in future releases of WooCommerce Payments. Keep an eye on the changelog for more details!

    Storing the fees in the metadata (have a feeling this may have just been implemented) I run some MySQL queries so I can easily identify sales, volumes, etc… just some analysis and PayPal store the fees as meta but WooPay did not meaning I had to scrape the notes for the fee values.

    I’ll flag this to our product team as a feature request so they can consider it as a potential enhancement in future releases.

    Thread Starter idonaldson1

    (@idonaldson1)

    Thank you for the response, I can already see one of those improvements. The fee is now stored in the postmeta table with the meta_key value being “_wcpay_transaction_fee” which is amazing. (Just in case anyone else is interested)

    Did not realise the postcode/zip was being flagged to customers, I will have to do a little test myself, maybe I might need to do some CSS styling to make it stand out if it is not already.

    Great to see WooCommerce is constantly implementing features to improve the system. Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Simple and Easy’ is closed to new replies.