Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.6.3
-
Fix Version/s: 4.6.4
-
Component/s: None
-
Labels:None
-
Documentation Required?:Developer Doc
Description
The recommended IPN path for payment processors is now
civicrm/payment/ipn/xx where xx is the payment _processor ID.
This patch means authorize.net & Paypal Pro supports these IPNS and we should recommend people start to use the new style instead.
Paypal standard still seem to interact too much with the http request - I thought I'd fixed that but I guess not. I think I'll fork the IPN processing so that the ones that have been upgraded to the new path support hooks etc & paypal standard & google IPN can lag behind until someone fixes them or transitions them into the omnipay extension which implicitly supports this.