#mangle8582
1 messages · Page 1 of 1 (latest)
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.
- mangle-subscription-event, 27 minutes ago, 16 messages
- mangle8582, 3 hours ago, 60 messages
- mangle8582, 1 day ago, 10 messages
- mangle8582, 1 day ago, 41 messages
That event is always sent when 3ds is required
That's because payment is attempted and failed because 3ds is required
I was trying to search for a boolean there to not remove the subscription if it's 3d
And only trigger on payment fail from subscription recurring
To delete the subscription
Well recurring subscription payments can require 3ds as well
It's fairly rare
But still happens
You don't want any retries?
I don't wanna rely on automatic retries
Because i'm still not sure how can i do it.
On Frontend i will need to keep subscription unpaid, and Retry button doens't work.
Changing of Payment Method is only for future payments there on the subscription UI.
And i will need to trigger somehow on changing of the payment method. But he will need to add the same card there to trigger retry. I'm a bit confused
Failed payments happen all the time
It's not a good idea to just cancel the sub every time one happens
I can help you implement this if you want
That's true
But just warning you that you will have a ton of cancelled subs due to this
I wanted to do retries, but somehow deleting the subscription seemed easier, but i see it's not a reliable solution. So i need to do retries
You don't need to do anything to implement retries
Just change a setting on your dashboard
It's really easy
Yea, but the case where the user enters app, and he doens't wanna wait 1 day for retry.
He want to reactivate subscription imediately. He needs a button to retry that.
Yeah I mean you can do that if you want
Let's say he didnd't had money.
After one hour when the subscription is unpaid, he enters app and he wants to retry imediately
To continue working
Yeah you can do this, but I would put some restriction to prevent unlimited restries client side so someone doesn't just spam the api with retries
Because if the subscription is unpaid he won't be able to use the app's functionality
Yeah makes sense
Yea, i could add a rate limiter on API, and maybe a functionality like login block after few attemps, but in this case will be retries attemps
But how can i trigger the payment from backend with which stripe method?
Front -> HTTP call -> Backend -> await stripe. which method
You can just do https://stripe.com/docs/api/invoices/pay
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
To pay the underlying subscription's invoice
So i will need the invoiceId right in the database
Yeah or susbcription object
Sounds good!