CiviCRM Community Forums (archive)

I have a client that currently uses the Authorize.net payment processor in CiviCRM 3.x.  They'd like to integrate recurring payments, which folks have tried, but which has never been "finished" enough to get into the tree.

Looking through the sources, it's pretty unclear how to "correctly" write a payment processor.

Back in May, lobo wrote

1. A patch that applies cleanly against current v3.2 or trunk attached to an issue on our issue tracker

2. A community person who will take responsiblity to

* Respond to forum posts and help folks with the processor with various support issues
* Upgrade the code as needed for various civi releases / authorize changes

3. Would be good for the person doing item 2 to also do item 1. Ideally this person will support a few folks on the forum for some time before we add it to core

4. On a related note, we are working on improving the system so all payment processors can reside OUTSIDE civicrm distribution. We'd like to avoid getting into the payment processor business 

lobo

I'm potentially interested in doing this for Authorize, but right now, I need to know about an upgrade path for 3.3.  There isn't much documentation for this stuff using the lold-style API right now -- in particular, it isn't clear to me if the "correct behavior" for recurring donations is documented anywhere.  The implementation for PayPal Pro is, well, the implementation for PayPal Pro, and there isn't much in the code to indicate if there are any abstractions that need to be implemented.  More to the point, there are things that I know for a fact do need to be implemented, and they are, surprise, not documented in the code.  Leaving the question as to what else needs to get done that you wouldn't know just by reading the implementation for PayPal Pro.

What's documented at this point for 3.3?  Obviously, I don't expect formal docs, but I do need at least a spec, so I know what Michal intends to implement.  This will help me write a "future proof" solution to this problem.

Thanks,
Rob

Lobo,

Where could I find user-level documentation of how the PPP implementation is supposed to behave?  Part of the problem is that unless you're running that processor, you don't actually see  the UI.  This would help me make sure I've covered the right features.

Are there particular classes that call into a payment processor where an Authorize.net implementation would have to "fit".  I've probably found most, but not all, of the relevant places.

This is particularly important for the call back stuff, where I'm still unclear what the callback needs to do on CiviCRM's end.  My impression is that the Authorize callback is not that similar to the PayPal callback, so I'm not clear what services CiviCRM expects me to handle.