#daisdead
grizzled swallow
Hi there 👋 making sure I'm understanding correctly, you're creating a Tax ID, but then it's not being included on Invoices until its verification.status field leaves the pending state?
manic granite
Hello! Yes, that is the case
grizzled swallow
Gotcha, hm, offhand my idea is to not generate an Invoice until the Tax ID is verified.
It looks like we typically expect the validation for VAT numbers to take a matter of seconds to complete:
https://docs.stripe.com/tax/invoicing/tax-ids#european-value-added-tax-(eu-vat)-numbers
When you say you have a custom checkout experience, am I correct in understanding that means you've built your own flow/UI for that?
manic granite
When you say you have a custom checkout experience, am I correct in understanding that means you've built your own flow/UI for that?
this is correct'
the flow consists of:
- updating customer information (includes creation of the tax ID object)
- then confirming either their payment or setup intent
in that order**
restive fjordBOT
grizzled swallow
Hm, where in that flow do you create the Invoice you're concerned about containing the customer's tax ID?
manic granite
That should be in the confirm payment intent scenario where we would be collecting payment immediately. The invoice creation/lifecycle is something we leave to Stripe to automatically manage.
The payment intent portion I am referring to is leveraging the client Stripe API of stripe.confirmPayment w/ React elements holding the card information. But again this is called after the mutation to update customer info + tax ID is completed
This is done in a single user step (1-click) but awaited for the successful response of the customer update
grizzled swallow
Are you using the Payment Intent that is being generated by an Invoice object?
manic granite
It should be from the created incomplete subscription
subscription.latest_invoice.payment_intent is what we're leveraging
grizzled swallow
Sorry, I'm struggling to understand the connection between the intents you mention that are part of your flow, and the Invoice where you aren't seeing the tax ID that you're hoping to.
If you're creating and finalizing the Invoice before updating the Customer, I believe it is expected for the Invoice to not pull in that tax id.
Ah, you're creating Subscriptions, I see.
I would recommend updating the Customer's tax ID before creating the Subscription for them.
The first Invoice of the Subscription is immediately finalized, and I wouldn't expect it to pull in a tax ID added after that finalization happens.
manic granite
I see, just to illustrate what is happening today and what youre suggesting:
today:
- create incomplete subscription
- update customer info + tax id
- confirming the payment intent
suggestion:
- update customer info + tax id
- create incomplete subscription
- confirming the payment intent