PHP Configuration Requirements
The following PHP extensions must be enabled in order for CiviCRM to interface with the eProcessing Network's payment services:
Use phpInfo() to check for these extensions. You should see the following lines:
The MHash extension is also recommended, although not required.
Advanced Integration Method vs Simple Integration Method
For eProcessing.com (Authorize.Net Emulation) Advanced Integration Method (AIM), card information is submitted to the server. The server then takes all submitted information, and submits it to Authorize.Net as an HTTP Post form. A reply is then received, which consists of a single CSV line. This reply is parsed to determine success or failure, and if failure, the reason for failure.
At this time, CiviCRM only supports the Advanced Integration Method.
Configure API Access
NOTE: The following assumes that you already have an eProcessing Network merchant account. If you don't, you can go to http://www.eprocessingnetwork.com/ to sign up.
If you do not already have an RestrctKey, generate this now from the eProcessing Network account page.
After this is done, create the eProcessing Network Payment Processor configuration in CiviCRM::
Remember that credit card information is being transmitted to the server. Unless the site is specifically being used for testing, and no live transactions will take place, it is highly recommended that Force Secure URLs be set
The following card numbers can be used for testing:
These numbers will always succeed in test mode as long as the expiration date is in the future. You can enter any value for the Security Code (CSC) when testing.
For more information on the eProcessing Network's Integration and Devloper utilities, see: http://www.eprocessingnetwork.com/Utilities.html
For more information on the Authorize.Net Advanced Integration Method, see the AIM guide: http://www.authorize.net/support/AIM_guide.pdf