#amanda688_best-practices
red sailBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255581247934173406
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
random sedge
If you're using Checkout, you can use : https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-invoice_creation-invoice_data-custom_fields
Which should propogate the custom fields to the first invoice
cinder inlet
we're just using UI-configured checkout atm
random sedge
Got it. We don't have context on the Dashboard route. We can only really talk about API integrations
cinder inlet
is there a way to update the first invoice via the API?
I am updating the Subscription/Customer objects via API at that point with some other metadata, but the out-of-the-box checkouts have met our needs up to now 🙂
random sedge
That's what the invoice_creation parameter does. That's the only way to update the first Invoice when using Checkout
cinder inlet
hmm, could I force the first invoice to be recreated?
also, I guess can I update the Checkout object of a checkout configured via the Dashboard, or does it have to be a totally API controlled Checkout?
random sedge
hmm, could I force the first invoice to be recreated?
No, unfortunately not