#keithm5699

1 messages · Page 1 of 1 (latest)

tiny vergeBOT
#

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.

weak saffron
#

Hmm I am not sure I am fully following, but

where we aren't aware of the failing payment intent/existing invoice
You should receive some webhook events, right?
Ultimately it's up to you what to do after received a webhook event notify about a failed transaction. You can delete/remove the original Sub, or you can notify your customer "Hey we couldn't charge but we will retry some times later"

#

Then use the status of the Subscription to distinguish

crystal osprey
#

ah the payment_behaviour looks like exactly what we need here

#

thank you very much for this ,we'll try it out

#

sorry, on this, is it possible to provide this when creating schedules? can't quite see how to do this via the create schedule flow

#

would we just update the payment behaviour on the subscription created by the schedule?

weak saffron
#

Yeah it's not available on Sub Schedule API AFAIK

#

and yes let's try to update the underlying Sub

crystal osprey
#

ok great we'll test this over weekend to verify it works

#

thanks so much for the super quic kresponse, really appreciate it