Stripe Fraud IPN history
So there is 0 ways to update the user's credit card on our end? Letting them cancel and resubscribe makes sense but is not user friendlykrileon wrote: That would be the problem then. Let Stripe cancel it and it will tell CBSubs. They can then renew at CBSubs. As I've said in several of these requests once CBSubs has the API to facilitate updating cards on file CBSubs Stripe will have the functionality to do so as well. Until then leave it be and let it cancel. Do not touch subscriptions established by CBSubs; it's an automated and delicate relationship with the gateway.
The reason I updated their card as such is because that is how I was instructed to do it previously. But to confirm, you're now saying that I never can update even their billing source through Stripe? Sorry I just need to be sure
In the case it was not manually updated, their subscription expired and then they renewed because their initial payment failed because they weren't able to update their billing card on file. So they then renewed and it restarts their expired subscription & also starts a new one.krileon wrote: They should not end up with 2 subscriptions as long as Stripe is configured as instructed
If you manually updated the payment source though it may have renewed the subscription (it shouldn't have renewed a cancelled subscription at Stripe), but CBSubs has already expired and cancelled. Will have to retest such a scenario to see what kind of IPN Stripe is sending in this case (they have a frustrating absurd amount if IPN types with several basically doing the same thing) as CBSubs already handles subscription and invoice payments which in theory should renew it at CBSubs unless Stripe is sending some other IPN type not accounted for in this specific scenario.
Sorry what I meant was, if I make the change in the CBSubs/Gateways/Stripe/version drop down..... will it automatically start showing that API as being used in the Stripe dashboard?krileon wrote: 2018-02-06 should be fine as there was no breaking changes there. No CBSubs won't force usage of newer API once supported; you'll have to manually change that in your gateways settings as I've been maintaining B/C for previous versions via that version dropdown
I understand you are very busy and I appreciate your time and efforts! Happy to help if I cankrileon wrote: I won't have time to dig into this deeper until I've completed the Privacy Suite integration changes for core CB. So likely won't be this month.
Please Log in to join the conversation.
krileon
