iris2015

[native mesa]

When the invoice is created, the payment intent will be created and associated with the invoice. Are you creating a payment intent separately (outside of) from the one in invoice?

[rigid sluice]

Today we create an invoice and then rely on it being sent to the customer to be paid, but we are moving to introducing a checkout step directly within our product flow where a payment intent auth would be created separately.

So we’re wondering if we can not create a separate payment intent, or associate the payment intent we create it to an invoice after its creation for paper trail/receipt purposes

Broadly, any documentation of how invoices work with separate auth and capture would be helpful!

[native mesa]

Thanks for sharing! Checking how separate auth and capture can be worked in Invoicing

As per checking, separate auth and capture doesn't support on the Invoice. I'd recommend checking with Support https://support.stripe.com/contact if it's possible to attach an existing Payment Intent with auth and capture to an Invoice