#ryanw-invoice-pi

1 messages · Page 1 of 1 (latest)

whole nexus
#

hello, an Invoice only has one PaymentIntent, since that PaymentIntent allows max one Charge to pay that Invoice

#

why would you want multiple PaymentIntents on an Invoice?

novel siren
#

I do not want multiple PaymentIntents for a single invoice. To clarify - I'm not asking if an invoice could have multiple PaymentIntents at a single point in time, I'm more wondering if the underlying PaymentIntent might ever be updated to a new PaymentIntent object with a new ID and client secret

#

If, say, it was possible that a payment intent for an invoice, could expire for example, and then a new one is created in its place

#

For context, I'm looking to create an invoice in advance, and then have a customer pay it later... I am thinking of storing the Payment Intent in a local DB at the time of invoice creation. Is it possible that the Payment Intent that I stored ever becomes invalid for that invoice? Or will that single intent from invoice creation time always be valid for that invoice?

whole nexus
#

I'm more wondering if the underlying PaymentIntent might ever be updated to a new PaymentIntent object with a new ID and client secret
ah gotcha, no only one PaymentIntent stays on an Invoice

#

possible that the Payment Intent that I stored ever becomes invalid for that invoice?
nope

#

Or will that single intent from invoice creation time always be valid for that invoice?
yes