#worming_best-practices

1 messages ¡ Page 1 of 1 (latest)

dull shoalBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1298393346259157082

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

final fulcrum
#

Hi there

stoic merlin
#

Hey roadrunner

final fulcrum
#

If your goal is to prevent customers from being able to pay any Invoices tied to canceled Subscriptions, you should update the Invoices to void status

#

uncollectible will not block customers from being able to pay those Invoices

stoic merlin
#

ok

#

and what about draft invoices for canceled subscriptions

#

the process is going to be, list all open invoices and void them... but i dont really know all the scenarios that we can face... what if we have a draft invoice related to the subscription?

#

and we also want to know why after the 8 retries that we have configured in Smart Retries, Stripe still charge the invoice

#

note: the subscription is set to charge_automatically, we never send the invoice to the customer

final fulcrum
#

why after the 8 retries that we have configured in Smart Retries, Stripe still charge the invoice
Stripe should not attempt to automatically charge after the 8 retries

#

If you have an example of where this happened, can you share the Subscription ID here?

stoic merlin
#

yes i have

#

sub_1Ln6Z3LN0iJa18ZedFgDRjwa

#

but i just got a message from Stripe support team saying this:

Hello,
I took a deeper look into the example subscription invoice you shared and confirmed that your dashboard retry settings are being obeyed as you have them set (smart retries, up to 8 times: https://dashboard.stripe.com/settings/billing/automatic).

This invoice has ten payment attempts:
1 initial payment
8 retries
1 manual payment from the customer

That "manual payment" came from the customer opening the Hosted Invoice Page and providing their card information for payment.

If you'd like to avoid that possibility, you could call to void (https://docs.stripe.com/invoicing/overview#invoice-statuses) the relevant invoice.

final fulcrum
#

The request to cancel the Subscription resulted in an update to the Invoice that was in open state. The Invoice's auto_advance property was changed to false, which means Stripe will no longer attempt to collect payment automatically.

#

The Invoice was still open , which means payment could still be attempted (either by calling /pay or via the Hosted Invoice Page)

stoic merlin
#

ok cool, so, as soon as we get the subscription.deleted event from Stripe, we should list all open invoices related to the subscription and mark them as void

final fulcrum
#

Right, if your goal is to prevent the customer from paying any invoices tied to that Subscription

stoic merlin
#

yes, what should be the reason to charge an invoice for a canceled subscription?

#

maybe there is something that im not seeing

final fulcrum
#

Well, some merchants choose to keep those Invoices open because they still intend to charge a customer for the services rendered during that period

stoic merlin
#

ok, thanks for your help roadrunner