#jack-tax
1 messages · Page 1 of 1 (latest)
it's disabled because of technical reasons with those wallets whereby you can't get the full shipping address of the customer before they authorise the payment, so it's not possible to accurately calculate the tax and show it dynamically before they pay.
There's no workaround I'm aware of
So for example, could I not create the customer separately with their postcode/country info and pass this customer id into Stripe for the Checkout session creation, and the taxation be based on those customer details
This might need to end up being a feature request.
But in my example after creating the customer before hand (e.g. API call) it appears that Stripe knows the customer location and should be able to calculate the tax when creating the Checkout session, and then we can authorise payment, given these tax details, via Google Pay / Apple Pay.
But let me know if this is/isnt supported today. Or if you can open a feature request for me 😄
supporting those wallets for automatic tax is one of our biggest feature requests/priorities but it's blocked on the actual implementation of those wallets with Google/Apple
it appears that Stripe knows the customer location
geo IP and stuff is not enough for accurate ax calculation, there reasons for needing the billing and shipping addresses specifically, tax is complicated
as far as I know there's no real workaround, customers can still pay, they just can't use those wallets for now
I mean specifically in the situation where I can create a customer with full address information and then pass this to Stripe Checkout
In this case, you would have this info
as far as I know there is just no workaround, I'm sorry. If there was I'd offer it
Ok so to confirm
If I create customer with full location info to https://stripe.com/docs/api/customers/create
And then pass the customer id to Stripe Checkout Session, with automatic_tax enabled https://stripe.com/docs/api/checkout/sessions/create, they would still not have Google Pay / Apple Pay support