By Jérôme on Thursday, 09 May 2019
Posted in Payment Gateways
Likes 0
Views 574
Votes 0
Hi Team,

Something needs to be improved for Stripe subscriptions (and maybe for other gateway, too).

When a subscription is "expired" (juste before), a cron generates a payment request. The problem is that PayPlans will generate a payment request at each cron call if the payment fails. In summary, if the subscription payment fails at expiration, it will retry at each cron request (every 5 minutes for instance). Stripe will be spammed by the requests.

We have clients calling us after they have been contacted by their bank about somebody trying to request a payment every 5 minutes during 48 hours...

We should be able to define the following settings: max_payment_tentative_per_day or something equivalent.

Thank you for your help!

Kind Regards,

Jerome
Hey Jerome,

Before expiring the subscription , recurring payment request initiated on cron job. If payment failed then it will try again to process on next cron execution till Wait for Payment period set in settings.

The purpose of wait for payment period is , before expiring the subscription it will wait for at least the particular time period for the payment. If payment not come on that time , after that subscription will expired only.

We should be able to define the following settings: max_payment_tentative_per_day or something equivalent.
Currently there is no setting to decide the number of payment request per day. I'll log this issue into our issue tracker Feature Request section and we will see how we can add this.

For now, i would like to suggest to setup cron job on server and disable Automatic Cron Job Execution. Setup cron job on server to run once in a day. In this way , payment will be processed once in a day as cron will also run once in a day.
Refer below mentioned document for more details.
https://stackideas.com/docs/payplans/administrators/cronjobs/cronjobs

Let me know if you have any qyery or correct me if i misunderstodd.

Thank you for understanding !
·
Thursday, 09 May 2019 18:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Making the cron to run only 1-2 times a day solve the issue for the moment. I hope that you will be able to find a proper solution in a next release

Thank you for your support.

Kind Regards,

Jerome
·
Wednesday, 15 May 2019 15:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jerome,

Thank you for updating us on this. It sounds good that your issue is resolved now.
We already added this into our issue tracker feature request, we will see how we can add this.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.
·
Wednesday, 15 May 2019 15:13
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post