Details
-
Type:
Task
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Duplicate
-
Affects Version/s: 4.1.2
-
Fix Version/s: None
-
Component/s: Core CiviCRM
-
Labels:None
Description
Extensions are great, but we still have to maintain the IPN files in extern for offsite payment processors, and part of the aim with extensions was to remove that task.
http://forum.civicrm.org/index.php/topic,21543.0.html discussed a few concepts for implementing.
I've started work on this for Flo2Cash Donate -
https://github.com/GiantRobot/nz.co.giantrobot.flo2cashdonate
My approach there is that we have a single file, extIPN.php which is part of CiviCRM. This file should accept a set of $_GET and $_POST params, eg
sites/all/modules/civicrm/extern/extIPN.php?reset=1&module=contribute&extension=nz.co.giantrobot.flo2cashdonate&contactID=2&contributionID=26
The extension=nz.co.giantrobot.flo2cashdonate then gives extIPN.php enough information to bootstrap the used processor and perform IPN.
https://github.com/GiantRobot/nz.co.giantrobot.flo2cashdonate/issues/1 is the issue against the processor.