domo-subscriptions | Stripe Developers | Page 1

crude dune Oct 11, 2021, 1:42 PM

#

this is a good question and I'm not really sure what people do (I think bank debit payment methods and our Subscriptions APIs don't really play well together)

dusky hearth Oct 11, 2021, 1:46 PM

#

Yeah it's left us little stumped. "past_due" seems to suggest that the payment has failed, or wasn't made which is why we didn't allow customers to use the system if the subscription was in this state. But it has been made and is just pending.

#

I have found this in the settings, and wondered maybe this could work? Allow customers to use the system if the subscription is "past_due", and then this will trigger the subscription into a new state which we would then not allow them to use it.

#

But was wondering if there is a slightly more elegant or appropriate approach.

crude dune Oct 11, 2021, 1:51 PM

#

I was thinking that and was going to suggest it, but I'm not sure if it works(since none of the dropdown options are about subscriptions being in past_due)

dusky hearth Oct 11, 2021, 2:02 PM

#

When a subscription/invoice is marked as "past_due", is this when the day counter begins incrementing in regards to the form fields in the screen shot?

I was thinking.
While the payment is pending the subscription is "past_due".
We allow them to use the system.
When the overdue by 30 days is triggered (by that dashboard setting), it would then move the subscription to unpaid.
If subscription is unpaid we then don't allow them to use the system.

I'd assume this would fit our situation. Although 30 days is a very long time. We would prefer to use "days_until_due", but this doesn't seem to work when collection method is "charge_automatically"

modest prairie Oct 11, 2021, 2:15 PM

#

Do you have the ID of a subscription that this happened for (sub_123)

dusky hearth Oct 11, 2021, 2:17 PM

#

It seems to happen with all subscriptions, but this is one that currently still pending and in "past_due" state.

sub_Gvu4WJYM6kLQ86

modest prairie Oct 11, 2021, 2:17 PM

#

Thank you. Looking in to it

dusky hearth Oct 11, 2021, 2:20 PM

#

Much appropriated 🙂

crude dune Oct 11, 2021, 3:03 PM

#

@dusky hearth ok sorry for the delay, it was a little complex. But basically yes, when you update the subscription to change the plan and generate a new invoice ,we try to charge the bank debt immediately. For a subscription like this, the "due date" is basically null, which means if the payment doesn't immediately succeed, then it's past_due . That's kind of a quirk, since for a payment method like BACS bank debits, the payment will never 'immediately succeed' — this part of the API is kind of card-centric :/

So anyway, the best solution here is likely to not treat past_due as meaning you need to cancel access to your service for the customer, since it's going to be a normal state subscriptions get into. You should wait before doing that until the subscription actually cancels after being overdue a while/some retries fail(which yep is the settings from the dashboard page you described above).

dusky hearth Oct 11, 2021, 3:10 PM

#

Fantastic @crude dune, much appreciated and thanks for clarifying everything 🙂

Out of interest, when we set the setting in the dashboard. Do you know if that will apply to prior subscriptions or only upcoming new ones?

Just so we know if we need to do any migrations/cleanup of any subscriptions in that current state

crude dune Oct 11, 2021, 3:14 PM

#

it affects new subscriptions, and existing ones, but for existing ones the way it works is they "pick up" the change the next time they cycle. it's like the setting is copied to the subscription, and the new version if it won't be copied until we have to look at the subscription again(like the next invoice)

#domo-subscriptions