#bruno224466
1 messages · Page 1 of 1 (latest)
Thank you for checking this.
To provide more context, this is my checkout form:
When the user selects the Country, we're:
- Updating Customer billing address country
- Then creating a subscription on the backend
- Then calling
stripe.confirmCardPayment()
Since the last step is actually creating a payment method, I can't think of any other way (other than Radar rule) to enforce customer's billing address country actually matches card issue country.
This is entirely up to you if its a rule you wish to enforce.
Which flow are you using for your subscription creation?
Hm, I don't know the exact name of the flow for subscription creation. It's been a while when this was first implemented.
I'm using vanilla JS on the frontend and Rails server on the backend. I'm not using Stripe hosted pages.
Is there anyone at Stripe I can contact regarding these "edge case" Stripe Tax questions?
I think the docs don't address the question: what if a user enters random country address to pay lower taxes. Yet, I think it's a legit concern.
You can see the priority of addresses used here: https://stripe.com/docs/tax/customer-locations#address-hierarchy
For a more general concern about taxes and customer locations and information they provide, you can write in your our support team: https://support.stripe.com/contact