By Kai Roen on Friday, 22 September 2017
Posted in Payment Gateways
Replies 5
Likes 0
Views 805
Votes 0
I am using your NETS payment integration, and we are having some issues with how Payplans handles transactions with NETS. If there are some problems with the card (expired or other temporary issues), the subscription will not be set to expired. All these transactions need to be monitored and handled manually - which take lots of time.

Could you please explain how this works for this payment integration?
There are no documentation released, so we do not know what this integration actually supports.
Hello,

For example - if you set 2 days in 'Wait for a payment' field then for payment it will wait for 2 days before marking any expiration to subscription.If payment not completed in 2 day's then subscription will be expired after 2 days.

In you case wait for payment is set to 1 , so it will request for recurring payment on every cron execution , after 1 day subscription will get expire.

Let me know if you have nay confusion.
·
Saturday, 23 September 2017 12:04
·
0 Likes
·
0 Votes
·
0 Comments
·
We have the same issue, though with ePay payment gateway. We have "wait for payment" set to 1 minute, so waiting for payment is clearly not the issue in our case.

I ran a query on our database and found 25 subscriptions that should have expired, but wasn't. Some with an expiration date a month ago. Our cronjob runs every minute. We can also see at the log files at ePay, that PayPlans continues to make a transaction attempt instead of expiring the membership (transaction attempt every minute).

Seems to be a bug somewhere...
·
Monday, 09 October 2017 17:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rasmus,

Please create new forum and share your site details and subscription id's for which this issue is coming.
So i'll check this issue at your end.
·
Monday, 09 October 2017 18:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi again - I did some more testing and found this:

From ePay (payment gateway) log, I found 3 users with expired cards, so payment could’t be made. After I manually expired those 3 memberships, I found each time, that a batch of those 25 users went through with payment and got renewed.

So to me it looks like an issue, where, IF a payment is somehow rejected on a recurring subscription, then the cron plugin doesn’t skip that user and doesn't move on to the next in line, but just keeps adding to the queue.

After I manually expired those 3 memberships, “Cron Job Executed Successfully” was again added to the Logs in PayPlans - was missing before.

So to sum it up.

1. Users with failing recurring payments should be expired - try e.g. 3 times, then expire
2. Skip failing attempts and move on to the next in queue.
·
Monday, 09 October 2017 19:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rasmus,

1. Users with failing recurring payments should be expired - try e.g. 3 times, then expire
We will look into this, as of now payment will be done on cron execution till wait for payment period.

2. Skip failing attempts and move on to the next in queue.
Can you please explain what do you mean to move into next queue. subscription will be expired immediately or something else.
·
Tuesday, 10 October 2017 11:13
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post