Hey Kai,

I've checked your site and got the issue. This issue is coming because error coming in recurring payment from nets and cron stopped.
I mean cron not executing successfully that's why this issue is coming.

I am able to replicate this issue locally also and will apply the fix at your site once tested asap.

Thank you for understanding !

Hey Kai,

I've checked your site and got the issue. This issue is coming because error coming in recurring payment from nets and cron stopped.
I mean cron not executing successfully that's why this issue is coming.

I am able to replicate this issue locally also and will apply the fix at your site once tested asap.

Thank you for understanding !

Hey Manisha,
thanks for a quick response. I am happy that you will sort this out, and look forward for a fix

Hey Kai,

I am working on this issue. will let you know asap.

Thank you for understanding !

Hey Kai,

I've checked this issue and fixed issue related to get PanHash for further recurring payments.
But now i am hitting the error unable to register transaction, i've checked the parameters and we are sending correct params.

I've tried to found the reason for this error on nets site but their i get to know we need to contact nets support team to know the exact reason.I've tried to contact with nets team about this issue but didn't hear back.

Can you help me to ask Nets support team about this error. Find attached text file with aparameters we are sending for further recurring payments.Once you got response from them update me.

Thank you for understanding !

Hi, I am not sure what exactly to ask NETS about.
The error to all recurring transactions is: Recurr too soon

This is a bug that we have previously reported about in PayPlans 3, and was fixed by you earlier.
See: https://stackideas.com/forums/recurr-to-soon#reply-398991

Manisha, could it be Frequency is set to NULL?
["Frequency"]=> NULL

Hey Kai,

The error to all recurring transactions is: Recurr too soon

Do you mean you see this error in your merchant account recently ?
can you share screenshot with me.

This is a bug that we have previously reported about in PayPlans 3, and was fixed by you earlier.

Yes, we included that fix. Before upgrading to site to PP4 , have you backup your site or do you have any site running with pp3.x where nets Recurr too soon issue arises previously.

Thank you for understanding !

See enclosed screenshots.
I think you're not handling the "Frequency" correctly according to the NETS technical documentation.
https://shop.nets.eu/web/partners/query

This worked fine in PayPlans 3.7.x

Here is the NETS payment APP for PayPlans 3.7

Hey Kai,

Thank you for sharing detailed information on this. I'll check it and get back to you asap on this.

Thank you for understanding!

Hey Kai,

Sorry for the delayed response.

I've checked the changes we made previously on your site , the only thing missing is to manage faliure attempt.
I've include this at your site again and will include in upcoming release also.

I've checked the pp 3.7 as well as pp4 code, the parameters are sending correct. No change in the request which is working in pp 3.7. i attached the data in text file we are using, so need to confirm with nets support team. As the same thing work earlier which is hault now. So , need to share this text file with them so they can take a look on the data we are sending for requested recurring payment.
Can you help me to contact them.

Update me with response.

Thank you for understanding !

Have I checked the text file you sent me, and why have you set "Frequency" to NULL?
According to NETS, this value need to be sent to NETS for processing a recurring payment. See my screenshot in previous message

Hey Kai,

Have I checked the text file you sent me, and why have you set "Frequency" to NULL?

Yes, you are right. The frequency not sending correctly, which i've correct it already and compared the pp3.x nets plugin also you sent to me in earlier reply.

According to NETS, this value need to be sent to NETS for processing a recurring payment. See my screenshot in previous message

Yes, i've checked and already correct it. Now, Frequency also sending in recurring payment request as you see in my reply.
here : https://stackideas.com/forums/subscriptions-is-still-active-when-they-are-expired#reply-466463

I am checking the api again if any parameter also sending wrong.

Thank you for understanding !

The response from NETS support is:
"You have created a new transaction yesterday, but since the transaction hasn't been processed as SALE, it didn't finished. The next attempts failed due to RECURRING TO SOON, since the interval need to be minimum 29 days"

The last file you sent me, contains an empty string

["Frequency"]=> int(29)

Hey Kai,

"You have created a new transaction yesterday, but since the transaction hasn't been processed as SALE, it didn't finished. The next attempts failed due to RECURRING TO SOON, since the interval need to be minimum 29 days"

So it means, when recurring payment processed and transaction not finished then can not request for recurring payment till the interval period even if recurring payment needed ?
Can we set interval to 0 , so no need to wait for 29 days's, as i read in their document.

Can you share me the email id of nets support team or you can include me in the email (manisha@stackideas.com) , so i can ask them directly.

update me with response, so we can fix it asap.

There is no email, you have to file a task at their Zendesk support account
https://netsecommerce.zendesk.com/

Due to this bug, the CRON job mess up the transactions in PayPlans, and create lots of transactions.
The NETS documentation is available here: https://shop.nets.eu/web/partners/appi, and this should be all the details for how the API works.

Please fix this issue ASAP, because there are now lots of subscriptions on the site that need to be renewed.

According to NETS documentation for Frequency:

Indicates how often the merchant is allowed to make withdrawals based on the recurring agreement, in days. A recurring frequency of "1" will allow the merchant to make subsequent transactions on the card every day.

Minimum frequency is 0 day, meaning no limitation on the number of transactions per day. Maximum is 365 days.

Setting Frequency to 0 is not correct, because if there is a bug in PayPlans, you're risking to capture the customer money unlimited times, which is a huge drawback for us. I think this issue is related to bad error handling from your side, and a payment transaction should be handled carefully

It seems there are no grace period for bad transactions. According to PayPlans, the new transactions is being made every time CRON works, and since NETS is returning an error code, a new transaction is made. The most logical thing is to set this transactions that fails on hold.

Error handling in PayPlans is not good enough

Hey Kai,

It seems there are no grace period for bad transactions. According to PayPlans, the new transactions is being made every time CRON works, and since NETS is returning an error code, a new transaction is made. The most logical thing is to set this transactions that fails on hold.

Previously we added failed attempt parameter if response code is not ok. But it seem that checking is not working.

Thank you for sharing the detailed information. I am checking the code again from start with their api code and will create the account the zendesk also if need any help from them.

For now, i've disabled the cron job at your site , so multiple callback will not made till the issue get resolved. I am working on this issue as highest priority and will get back to you asap.

Thank you for understanding !

Hi Manisha, do you have an ETA for a fix for this issue?
The client is awaiting an answer. This is a online news site with payment and subscriptions, so it is important that this works

Hey Kai,

Sorry for the delayed response. I've contacted to nets team but didn't get any response yet.'I read the api docs again and do the changes as per api.

I've already fixed this issue at your site and also added error handing and maximum failure attempt to 3 times. this will include in upcoming release also.
Now i just run the cron and some of recurring payments come.

Just for information
1. i've enabled the debug mode and error reporting to maximum for while, i've already disabled it.
2. I've enabled the cron again on your site.

Can you please take a look on this and update me if still any issue persist.

Thank you for understanding !

Yes, I can confirm that some subscriptions are being renewed.
We have a lots of active subscriptions that should be renewed. Will CRON process these subscriptions?

Hey Kai,

Thank you for confirming.

We have a lots of active subscriptions that should be renewed. Will CRON process these subscriptions?

Yes, i've proccessed some of them while testing the recurring payments. Well next cron will run it will initiate payment request for those also and update the subscriptions accordingly.
Keep monitor these subscriptions further and i'll also.

Thank you for understanding !

I think this subscription 101 (8O56WJCMAKDR) is blocking the CRON job.
In NETS transaction, the errorcode is 07 (Refused by issuer). This means that the transaction can not be processed, due to technical error or insuffient funds on card.

I guess the settings "Wait for Payment before Expiring Subscription" settings is valid for these transactions as well?

Hey Kai,

I guess the settings "Wait for Payment before Expiring Subscription" settings is valid for these transactions as well?

Yes, this setting valid for all the transaction. It will wait for payment for 1 day before expiring the plan.

I think this subscription 101 (8O56WJCMAKDR) is blocking the CRON job.

How many transaction shown in nets , because, i've added the payment failure count also. So after 3 try it will not initiate payment request.

update me.

Here is the transaction list in NETS (11 transactions)

Hey Kai,

I missed this case.
Now , i handled this one also and cron is working fine and as well as recurring payments also.

Can you take a look on this and update me with response.

Thank you for understanding !

Thanks Manisha,
now it seems that this issue is fixed
Excellent work, and I hope you can monitor the log - and I will let you know if the problem occur again

There are still two transaction that should be renewed, but I guess the next CRON job will process these

Hey Kai,

There are still two transaction that should be renewed, but I guess the next CRON job will process these

Yes, let's wait for further cron execution.

now it seems that this issue is fixed
Excellent work, and I hope you can monitor the log - and I will let you know if the problem occur again

Your welcome. Keep me update if you face any issue.

Thank you !