You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been running a2billing for 3 years but in the last couple of months I have been receiving notifications from paypal that my IPN is not responding. This is for recurring payments and also customer balances are not being updated on loading. I looked at the IPN history in Paypal and they fail and there is no http response code on the failed ipn transactions.
I have checked the a2billing github repository and I noticed a change in 2015 to the checkout_process.php file due to IPN changes. I have applied this, but still Paypal IPN fails. I have also noticed from the commit, the PAYPAL_VERIFY_URL is now hardcoded and not driven by config. Is this intended? Also not sure it is related, Paypal have moved SSL to SHA256 and plan to move to TLS by mid next year. Also the ipn url is changing to ipnpb.paypal.com.
How do I diagnose the problem and resolve it?
The text was updated successfully, but these errors were encountered:
I have been running a2billing for 3 years but in the last couple of months I have been receiving notifications from paypal that my IPN is not responding. This is for recurring payments and also customer balances are not being updated on loading. I looked at the IPN history in Paypal and they fail and there is no http response code on the failed ipn transactions.
I have checked the a2billing github repository and I noticed a change in 2015 to the checkout_process.php file due to IPN changes. I have applied this, but still Paypal IPN fails. I have also noticed from the commit, the PAYPAL_VERIFY_URL is now hardcoded and not driven by config. Is this intended? Also not sure it is related, Paypal have moved SSL to SHA256 and plan to move to TLS by mid next year. Also the ipn url is changing to ipnpb.paypal.com.
How do I diagnose the problem and resolve it?
The text was updated successfully, but these errors were encountered: