mangle8582

[wintry walrus]

to be clear, are these fields that stripe takes somewhere or are you always setting it as metadata?

[latent karma]

I saw them on a stripe checkout dashboard

[wintry walrus]

Metadata won't show up on invoices, but I think there are other ways to set up custom fields that I can look in to

[latent karma]

I need to do this but custom

And i need to show those values inside invoice, so user can deduct his Tax with the invoice

inside metadata i can send data so i can take it inside webhook i'm thinking

on invoice.paid or

[wintry walrus]

Ah in that case I believe you can create a tax ID for the customer https://stripe.com/docs/api/tax_ids/customer_create

Double checking how this works

[latent karma]

And it's good practice to send metadata

and update on webhook?

[wintry walrus]

Depends on your usecase. You can set this upfront when creating your customer object, so setting it as metadata later may not be necessary

For business name, it looks like we just set that as the customer's name https://stripe.com/docs/tax/checkout/tax-ids#existing-customers

[latent karma]

I'm creating customer when user is creating account but i would not add there the VAT fields.

I would want the user to have VAT Business Name and Tax Id only when he is subscribed. When he is no longer subscribed i will need to remove Tax Id and Business Name i suppose right?

Because i only care to have it so he can have the VAT data on his invoice or receipt only.

VAT Identification Number actually. Which i suppose is different than Tax ID right?

For Tax Id i would need a dropdown here to have all the values?

[wintry walrus]

Yep, this field is what Checkout uses for the VAT ID

And yes, you can have a dropdown with those options if that makes sense for your app

Same with deleting them, you can check with our support team if there is a regulatory requirement there but I am not aware of the need to immediately delete them

[latent karma]

Yea, on Stripe Dashboard i see it's no dropdown, but you can add it yourself

I wonder how can i save it if i need to add type payload to tax ID

[wintry walrus]

I think we may determine the type of tax ID based on its format

[latent karma]

Uff.. don't know how to do that, is there another way? Like update customer with the tax ID value only? And show on invoice just the business name and the value of tax Id? without type?

Without creating a tax with the API?

[wintry walrus]

Honestly a dropdown would probably be a good compromise. The user can choose themself and that would let you more easily use our built-in functionality. Otherwise you can try setting a custom field on the customer https://stripe.com/docs/api/customers/object#customer_object-invoice_settings-custom_fields

[latent karma]

But they need the VAT identification number on the invoice anyway

[wintry walrus]

Right, so my preferred method would be creating the tax IDs and passing in some value for that type

Unfortunately it is not possible to create a tax ID object without passing in that type somehow

[latent karma]

yeah 😦

But without it, it can be done right?

updating the customer with it

would the invoice have these values?

I could add another dropdown, i have the types values here, but i need the name of that tax type as well to show inside dropdown, not sure which is which

So user selects the type, i don't know personally about this on any website.

So the best way might be to determine the tax ID based on ValueID but that is harder than i think

For me atleast.

That means that if we create custom Stripe without checkout dashboard we can't really make subscriptions for Companies? I haven;'t seen a tutorial or something yet

[wintry walrus]

@latent karma apologies for missing this followup for a while. The invoice object will have the tax IDs on it, and I believe they will show up on the invoice PDF but I would reccommend testing this in test mode yourself to double check https://stripe.com/docs/api/invoices/object#invoice_object-customer_tax_ids

[wintry walrus]

Not sure about this. You can reach out to our support team to discuss regulatory requirements and such