CiviCRM Community Forums (archive)

Greetings:

We are fishing (phishing) for general feedback as to how Pay Junction (PJ) works as a reoccurring CC payment gateway within Civi.

According to their tech support, PJ is different from PayPal and Authroize.net in that there is no return path, no calling a file within the sites/all/modules/civicrm/extern directory to communicate back to Civi status codes for transactions.

Further, since within the PJ test area we see transaction amounts show up in green font saying "approved" then in PJ's support's opinion the charge was completely successful. However we see within Civi the transactions as "Pending (Incomplete Transaction)" Status. This does not give me warm fuzzies in the least!

Perhaps does that happen since they are not real-enough transactions, since they are against the test site?

Several months ago, I thought I had seen somewhere an Rx to take some file related to Authorize.net, change which server the file is suppose to communicate with, and operate as if it is configured for Authroize.net but in reality it is talking to PJ. Now I can not find that text, however I see this text here:

http://wiki.civicrm.org/confluence/display/CRMDOC33/PayJunction+Configuration

Talk of a custom module available by contacting someone via email to make Recurring Contributions work / work better / do not know exactly.

Yes, we will be using nearly 100% Recurring Contributions, and site membership is kept enabled via successful Recurring Contributions. (Thus our interest in "Getting Membership Types and Recurring contributions to work together" http://forum.civicrm.org/index.php/topic,16642.0.html )

So any feedback as to what we are getting into considering Recurring Contributions with PJ as the CC gateway?

<><><><>

Post multi-way phone meeting with PJ staff:

Seems that Recurring Contributions are only possible when using the Drupal module mentioned on the PayJunction+Configuration page and that those transactions are offloaded to PJ. Civi is not involved with submitting each recurring charge or receiving any sort of acknowledgment. We shall for the time being login to the PJ website, bump the memberships that the CC was successful for allowing access for another n days. I will contact that person in order to obtain the mentioned module... I understood otherwise Recurring Contributions are not possible with Civi / PJ. I think something about that module changes the transaction headed to PJ to put it in the format of a Recurring Contribution, at which point PJ hits the cruise control / auto-pilot mode... that it is for Civi thinking about the transaction.

Sooo....

We are indeed interested in utilizing the code that Lobo mentions is forthcoming to connect CiviContributions with CiviMembership... keeping the membership alive for another n days when transactions are successful. So automation of Recurring Contributions should provide CiviMember with the correct information that the proposed connector script will be looking for... noting that on PJ's radar map.

PJ did acknowledge of the existence of some documentation to utilize the Authorize.net return path module, modifying it, and use that to receive information back from PJ. That is good... now I feel better that it was not my imagination running away. 

Been a long day... 'nough 'puters!