#min-dailyinvoice-retyschedule

1 messages · Page 1 of 1 (latest)

unreal capeBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

odd latch
#

Hi 👋

By "grace period" you mean defining the retry schedule. We do not have a cadence that would work with a daily invoice schedule. In that case you would likely need to implement your own retry schedule.

fickle coyote
#

I don't understand what you mean.

#

First, Stripe Support retry schedule. Please see image

odd latch
#

The shortest retry schedule that can eb configured is 1 day. So how would that work for you?

fickle coyote
#

This will generate an invoice for each day of the month.

However, the Retry Schedule will also retry up to 21 days (when set to 7 days, 7 days, 7 days in the Stripe Dashboard).

Here's an example.
Let's set the Recurring for Price to DAY.

  1. 2023-01-01 - First subscription payment starts (invoice generated)
  2. 2023-01-02 - Second invoice generated but payment failed
  3. 2023-01-02 - Third invoice generated and paid successfully
  4. ...
    ...
  5. 023-01-02 - 20th invoice generated and paid successfully

Question 2. In the above situation, if Retry was performed for the 2nd invoice and the payment still failed, will the subscription be canceled?

#

If you set it to 1 day, you have the same problem.

My ultimate question is how does this work if the period that can be set as the Grace Period is greater than the Recurring Schedule period of the subscription?

  • Recuring Schedule(each 1 day) < Retry day
odd latch
#

My ultimate question is how does this work if the period that can be set as the Grace Period is greater than the Recurring Schedule period of the subscription?
This is why I don't think automatic retries would be a good fit for this integration