Open jobthomas opened 5 years ago
Changing priority to High, as it makes us unable to test any SEPA scenario, or even confirm if it's working or not.
So it is actually working in test mode, you just need Stripe to give you permission to use SEPA in test mode. I'm not sure this is something we can change on our side @madeincosmos
Closing as we've confirmed that to test SEPA, Stripe.com needs to activate SEPA on the Stripe.comaccount.
Internal discussion - p6q7sZ-6Do-p2
cc @grigorijurasov @jrick1229
I'm reopening this, I think the error notice should be more clear towards the users. It took us a while to figure out why it wasn't working; I assume that's the same for users.
I believe providing a correct error message relating to what is or isn't enabled on the Stripe.com account will need checking account status via the API - I'm unsure if that is available.
In that case, some conditional response would be nice
Or something like that
In 2776631-zen the customer contacted Stripe directly while testing SEPA and they reported this back from Stripe:
I checked the latest test and noticed that while you already use version 4.2.3 of the Plugin, charges still seem to created with the v1/charges endpoint, which is why the test fails. You may therefore want to reach out to WooCommerce to check with them why that is the case.
I think the 4.2.3
is a typo here, because the current version of the Stripe extension is using an older version of the API:
https://github.com/woocommerce/woocommerce-gateway-stripe/blob/4.3.2/includes/class-wc-stripe-api.php#L16-L17
https://stripe.com/docs/upgrades#api-changelog
@jobthomas Any chance you can test to make sure SEPA is still working in test mode for you?
Yup, just tested it:
@jobthomas Great, thank you!
Describe the bug When I enable Stripe SEPA together with Stripe Test Mode, I can't get it to work. I get the following error in the checkout:
I've tested with both the
DE89370400440532013000
BE62510007547061
-- the address I entered was a Belgian oneIn the Stripe logs, the only thing I see is:
Link to image here: https://cld.wthms.co/HCTYZq.
To Reproduce Steps to reproduce the behavior:
Error confirmed by @treibalen and @dougaitken p1573115109025900-slack-C2C8F5PNJ