#top-rob_api

1 messages · Page 1 of 1 (latest)

merry cipherBOT
#

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

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

teal cloak
#

Will Smart retries apply in this scenario if enabled in the customer’s account?
Smart retries is a billing feature

#

It's not available when you create manually a PaymentIntent

drowsy trellis
#

We thought that might be the case. Is there a way we can make use of Stripe's technology in this scenario or do we have to create our own version of retry policies?

teal cloak
#

If you are using PaymentIntent APIs, you need to implement your own logic for retries.

drowsy trellis
#

Just to double check, does this also include when a customer has set a custom retry policy - it's not relevant as we need to handle it fully?

teal cloak
#

a customer has set a custom retry policy
Where exactly? can you share more details about this ?

#

But not using direct PaymentIntent APis.

merry cipherBOT
drowsy trellis
#

They've set custom policies up in billing/automatic -> Manage failed payments for subscriptions.
....but I presume because we're handling the subscription, this gets ignored?

placid scroll
#

Correct yes. If you're manually creating/controlling recurring payments outside of Stripe Billing (which seems is the case based on pi_3PMfitJv9yZRXqXy14Fl8fTG) then those rules won't apply. You'd need to build your own payment retries system

drowsy trellis
#

Ok, all confirmed. Thank you for your help.