#jogui_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1308737228595269702
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Sorry, the billing_details object had a typo:
billing_details: {
name: nameInput.value,
email: vueInstance.userEmail,
address: {
country: vueInstance.form.countryIso,
postal_code: vueInstance.form.postalCode,
},
},
this is not enough for a valid address
here's an overview of the billing_details object https://docs.stripe.com/api/payment_methods/create#create_payment_method-billing_details-address
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
We have been working with this billing_details for a year without problems (only Country and zipcode are enough) and the Stripe automatic tax is working, we have constrained to only use credit cards payment method.
Our UI does not ask for more information to our users.
yes but starting November 25 this won't be enough
you need to start collecting more info (e.g. line_1)
and ask all of your current customer's with valid subscriptions to update their billing details
and what happens with renews of all our current customers? we have to ask for this information?
5 days is a very short span to do such a change, and will impact tens of thousands of customers
you need to contact https://support.stripe.com/?contact=true for any more details or inquiry.
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
With whom should i contact there? I understand its out of your support scope but some advise would be very appreciated
this change will severely impact our bussiness
Does the email contain a documentation link? Can you share it?
Gonna check, one moment please
The email:
And the support documentation: https://support.stripe.com/questions/manage-draft-subscription-invoices-with-invalid-tax-location-details of the last link, "Support site"
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
The other link sends me to my dashboard
Thanks, let me familiarise myself with the changes
In this support documentation it does not explain me that I have to add more billing_details.address than now, in fact, i understand that all the people the current Stripe Tax automatic algorithm works, it will continue working (everyone)
FYI:
billing_details: {
name: nameInput.value,
email: vueInstance.userEmail,
address: {
country: vueInstance.form.countryIso,
postal_code: vueInstance.form.postalCode,
},
},
As you can see, requiring more address data would impact the kpis of our optimized paywall:
Yes, that is a fair assessment. If your current customers are Stripe Tax compliant (e.g. have a valid address we can use the calculate tax) then this is mostly a non-issue for you
This is only problematic in scenarios where we do not have a valid address to calculate tax as the API will now error in those scenarios, where as in the past it did not
My guess is that you've received this email as you're impacted in some way โ perhaps you've a customer with an invalid address and/or an invoice we didn't finalize/pay because the address was invalid
Ive followed the doc article and check for example, all last month invoices (several thousands) and not a single error in "Identifying invoices that failed to finalize due to invalid customer tax location" -> Last Finalization Error Code
Also in the second export "Identifying subscriptions with invalid customer tax location" -> Column "Tax Location Recognized" more than (several thousands) and not a single FALSE value
eveyrthing is cristal clear correct
Maybe we had in the past some edge case for a specific customer, gonna export the whole data to investigate, but in any case, the current implementation is not affected
Is there any way i can get a confirmation by your side, that on Nov 25 all the tax system won't stop working? In no place in the entire Stripe docs i have found what sections of the adress object should be fullfilled. We have talked with out tax / finances team and mostly in all the world , with Country and zipcode you can infer the taxes, thats therefore the minimum data we send to Stripe, to improve our paywall and our subscription conversions rates
No we can't provide that confirmation. As per the email there's clear steps on how to identify any problematic invoices/subs/customers and how to remedy them
okay, therefore if there is no problematic invoices/subs/customers following the email documentation, everything should work on Nov 25 right?
Gonna revise all our invoices/subs/customers in case we have received this because some very small corpus of users with problems hidden somewhere.
As always, thank you @wheat lodge for the help, being the developer responsable for the tax system of our company is always a very dificult thing haha
๐
My recommendation would be to follow the 'Identifying and exporting unpaid invoices' part of the link to understand potential impact and go from there
You can understand if we'll stop calculating tax for any subscriptions by doing that, then remedy those following the other steps on the page
Sure, i've just checked for the last month and everything correct, im going to check all our database, not only last month