#mochi-subscription-status

1 messages · Page 1 of 1 (latest)

autumn tapirBOT
#

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.

signal oyster
#

Hi, let me help you with this.

#

Could you please share the Subscription ID sub_xxx?

runic stag
#

evt_1OZMe7BPM36OC3gXNwFVas5Z is the event Id where this happens

#

sub_1OMgGVBPM36OC3gXP0DO2do8

#

?

signal oyster
#

Looking, sorry for delay.

runic stag
#

thanks

signal oyster
#

What were you trying to do in the first place? Do the Invoice payments retry?

runic stag
#

there was an existing subscription so I reset the billing cycle to charge again and then for some reason with ach payments it transitions the subscription status from active -> past_due

#

and I dont want that to happen

#

what is the reason that is happening and is there any way I can change that behavior

#

if I cant change it I need to know what actions cause that behavior with subscriptions

signal oyster
#

I don't know why is this happening. How do you know this happens only with ACH?

runic stag
#

because its the only time I've observed this behavior

#

this is reproducible

signal oyster
#

Sorry I don't understand. Did it happen once? Or you were able to reproduce it?
Do you perform such an operation with Subscriptions with other payment method types?

runic stag
#

yea I've tested with ach and credit cards and this only happens with ach. I'm updating the exising subscription with the payload { "proration_behavior": "none", "billing_cycle_anchor": "now",

#

?

versed basin
#

👋 taking over

#

this is mostly expected behaviour. With card we know the payment succeeded immediately

#

With ACH we don't know, it takes a few days for the payment to succeed so we consider the Subscription not "paid" at that point so it goes to past_due

#

would happen with all bank debits like BACS or SEPA Debit too

#

mochi-subscription-status

runic stag
#

in general what other things cause a subscription to go into the past_due state or does it vary by the settings you have in the stripe dash

versed basin
#

We do the same dance at the end of a trial period for example where it can do trialing -> active -> past_due
I don't have other specific examples top of mind sorry. I'd recommend testing a lot of those with TestClocks

runic stag
#

thanks