CiviCRM Community Forums (archive)

Is there already a workaround to implement other Payment Processors in version 1.8? Because the workaround mentioned in here http://forum.civicrm.org/index.php/topic,275.0.html, is not suitable anymore I think.

Thnx.

Brian

Brian - The first thing you should probably do is post info about the processor(s) you want to use - to see if others are working on the same thing :-) (post to forum and to civicrm-dev mailing list)

The architecture for handling Payment Processors has changed a bit in 1.8 - which added the ability to have multiple active processors in one CiviCRM install. This means that each new processor needs to be "registered" by adding a row of 'meta' information in the civicrm_payment_processor_type table.

Bottom line however is the same - you need to:
* compare the behavior of your new processor to the existing ones and determine which existing processor implementation is MOST similar
* review the code for the existing (1. implementation
* refer to Marshall's notes which should be mostly applicable - http://www.idealso.com/civicrm/AUTHORIZENET_NOTES
* clone and implement your new processor

Ask questions on IRC as you get into the coding.
...dave