august_api

[light sail]

👋 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/1250514344136151100

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

[plain jewel]

Failure is a terminal state for a Charge. The Payment Intent can be retried after a Charge fails though

[muted zephyr]

Okay, but only my app can retry the PaymentIntent, correct? Unless my app retries the PaymentIntent, no additional Charge will be instantiated? (There's no way for the customer themself to trigger the PaymentIntent to retry?)

[plain jewel]

Correct

[muted zephyr]

solid. thanks for clarifying!

Wait, one more related question; I want to check the assumptions implicit in my first question lol:
For off-session PaymentIntents, the value of error_on_requires_action is basically irrelevant, because off-session PaymentIntents always fail if they transition to requires_action. Correct?

[plain jewel]

If you attempt to capture a Payment Intent off-session when the Payment Intent has requires_action, then yes it will always fail

[muted zephyr]

Okay, I think that makes sense. I was a little confused about the lifecycle; I was conflating creating, confirming, and capturing the PaymentIntent. But I think that makes sense. Thanks!