Short answer - I used s2member --> Stripe Options --> Stripe should collect a customers billing address.
And for Stripe should verify ZipCodes --> No, do not validate…
Actually I cannot find the tax rate calculations under Paypal Options anymore… Has this been removed a few versions ago? So I cannot try the internal address option anymore.
Oh yeah, and I have a German credit card (Postal code is demanded). But it is not mentioned on the card nor would I have a clue where it was issued.
I think Europe this is usually not known.
Yes. Had to figure out the pro-form’s JavaScript and got the tax section working with the new Stripe integration. And made the zip code field optional.
I’m tidying up some things to send you the updated beta soon.
Thanks a lot for your work about this, I try to do maximum of tests with your beta versions but I don’t have as much time as I would like for test this.
Address is there - and seems to work. However one small caveat. I use a 3rd party tax handling - and this requires the address - but the sales tax 0.00% applied information is confusing (the 3rd party option (quaderno as stripe plugin) is calculating the taxes after buying and decreases the actual price before taxes so customer always pays the same no matter where he is from).
Maybe you could remove the bogus tax and make a real address option instead.
I used the Stripe card: 4000002500003155
and get the following error:
“Action required: 3D Secure authorization”
above and below the form:
"This PaymentIntent pi_1FQ86HJ1O9wogKkFdpTLNT72 cannot be confirmed using your publishable key because its confirmation_method is set to manual. Please use your secret key instead, or create a PaymentIntent with confirmation_method set to automatic.
what is going wrong here?" Maybe I missed something that I need to change in my Stripe account? Or in the Stripe settings of s2member? Sorry haven’t got time today to continue on this. But if something needs to be changed here still please mention it here and in the instructions for upgrading s2member.
Well - even updating the Stripe API version to 2019-09-09 did not change anything here. The 3D Secure Authentication is not opening. I’m rolling back to 2018-08-23 for now as i don’t know if the current API version is supported by old s2member versions. Would be nice if you, Christian, can help us out here if update is safe and also of course inform that the upgrade of Stripe API is needed (or did you set this in the new s2member manually which is possible so manual updating not needed?) - because I think 3D Secure will only work with the 2 latest Stripe API versions.
Anyone else got an idea what else could be running wrong here? Because I’m sure I’m still missing something - 3D Secure is simply not working and I’m sure this credit card has been tested already.
All credit cards listed under:
Regulatory test card numbers
and
3D Secure test card numbers and tokens
should work for my understanding before the new s2member version is published…
just started a thread and replied to the one you correctly found. BTW my main other gripe for a long time that paypal payments were missed is solved since the update 190822
(it was solved by this patch here: Error with Paypal Auto-Return URL )
I used to have about 1-2% of all payments gone into Nirvana (especially troublesome because if s2member sent them into Nirvana - I had to manually write invoices because my invoicing solution depends on s2member getting the payment recognized so each VATMOSS return I spend 5-6 hours using excel to find the payments missing by comparing invoices registered to paypal activity downloads and then repairing s2member accounts and manually by hand writing the invoices)
The address is asked for using bogus tax - but it isn’t forwarded to Stripe!!!
So right now asking for the address is simply broken!
A similar bug got fixed 2 or 3 days before 01.01.2015
(asking for address and then not storing it is a useless as it can be)
Please fix this ASAP and send out a new beta. The current version is not production ready…
EDIT:
(to try out - check that all of the following three are different and working: a) credit card country b) address country as user indicated c) postal code as user indicated d) IP address forwarded to Stripe.
I think right now c) is somehow broken. Having all of them is essential for correct VAT calculation (as most countries require 3 independent proofs).
Edit2: I first thought I found the address data - as I could find it under Metadata. But that address was still present as I used the same email as previously once to pay via ThriveCart test payment. So actually right now the billing address is not forwarded at all.
Tax address is not collected. Country and postal code are, when taxes are configured in s2, but that was never stored. The taxes part is behaving as it used to, or am I wrong?
I’m not saying it shouldn’t be improved, and there’s many things I have planned to make the taxes part of s2Member better, but it’s unrelated to the updated Stripe integration and SCA support to collect payments.
The card’s country and postal code don’t need to, or have to match the tax country or postal code, or the customer’s IP. Stripe’s card element doesn’t require the postal code, but it can ask for it optionally as an extra verification.
You haven’t understood the problem at all. S2member only needs to forward the billing address to stripe. The new release breaks this. It’s been working since 2015.