#persistent_invoice-metadata
compact brookBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- persistentcoder_api, 5 days ago, 15 messages
valid bluffBOT
đ 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/1237079311349973014
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
tacit cedar
persistent_invoice-metadata
@elder stirrup that's not something we support upfront. What you can do is update the PaymentIntent's metadata after it is created by the Invoice. But it's not possible to control the PaymentIntent's metadata on creation by the Invoice
elder stirrup
The only reason im listening on payment_intent.succeeded is there are other modes of payment like in-session checkout
i wanted to manage all of them in one event "payment_intent_succeeded"
elder stirrup
<@1022164646452535358> that's not something we support upfront. What you can do ...
So i create a invoice in draft state, update the payment_intent metadata of the associated invoice and then finialize the invoice?
tacit cedar
No you can not do that. The PaymentIntent is only created when you finalize the Invoice. You can update the PaymentIntent after finalization though (which is before payment)
But really you should use invoice.paid instead. You'll need this to handle $0 Invoices in the future for example even if you might not need this now
elder stirrup
alright, thanks.
one more question, lets say a scenario where i would like to charge the customer. But, his company will pay on his behalf. So when i create a invoice , can i use the existing customerid but send invoice to HR of his organization who will make the payment?
tacit cedar
Not really, the Invoice will be sent to the email associated with that Customer but they can work with their own company for this. Or in the Dashboard you can manually confirm To and CC emails for those (not in the API)
elder stirrup
aah, that is what i was wondering how to achieve recipients using API. Do you suggest creating stripe customer for the HR and use it ? But then how do i tie payments back to the original customer !
tacit cedar
Mostly you can't. So either you use the Dashboard feature for now or you create separate Customer objects and tie those back in your own database