MaDDogx

[rich sedge]

I don't believe so, you'd need to manually re-attempt payment by confirming the associated PI. Should be easy enough to test with a clock

[shut basin]

On the settings page, there seems to be an Advanced Invoicing features where we can configure the Retry Schedule. Does it do something like this? Where we don't have to manually re-attempt the payment via the Invoice's Payment Intent?

[rich sedge]

I believe those only apply if payment fails when there's a payment method attached

[shut basin]

Is there an article or documentation on Stripe for trying to confirm the failed Payment Intent after the Payment Method gets attached to the Customer?

[rich sedge]

Nothing specific you'd just bring the user back online and initiate a confirmPayment with the pi_abc_secret_xyz from the Invoice like in this flow: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements

[shut basin]

No no, the Invoice is the Stripe's Invoice entity. We are creating it on a background job so would confirming the associated Payment Intent just work?

[rich sedge]

I understand that. What I mean was you follow that flow to confirm the PI (skip the creation). This part: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment

[shut basin]

On the server side itself, right? For example:

# invoice_id from a webhook event
invoice = Stripe::Invoice.retrieve(invoice_id)
Stripe::PaymentIntent.confirm(
  invoice.payment_intent
)

[rich sedge]

No, you'll need to do this client-side so that the customer can complete 3DS/auth if requested