Authorize.net CIM PHP Class
The Authorize.net CIM PHP Class allows you to interact with the Authorize.Net Customer Information Manager (CIM), which can be used to store your customers’ sensitive payment information on secure servers, simplifying payments for returning customers and recurring transactions. It can also help you to comply with the Payment Card Industry (PCI) Data Security Standard, since customer data is no longer stored locally. It is an ideal tool for businesses that need to securely save customer data and provide convenience for their customers.
| Tags | Information Management Records Management |
|---|---|
| Licenses | LGPL |
| Operating Systems | OS Independent |
| Implementation | PHP |
Recent releases
- 07 Jun 2008 08:34
Changes: Some miscellaneous updates were made to the PHP class because of recent changes to the Authorize.net CIM API. The only change that will affect users of this class is the removal of the Wells Fargo SecureSource implementation. A README.txt file that explains various inconsistencies in the Authorize.net CIM API manual was included. $version and $responseDelimiter variables were added in the class. The class now ensures that the $responseDelimiter is correct, and the regexp was updated for a few elements that required a dollar amount in the correct format.
- 19 Jan 2008 14:38
Changes: The error handling logic for some functions was incorrect. The refId element is now implemented. The Wells Fargo SecureSource eCheck.Net implementation was incorrect. echeck (bankAccount element) implementation was incorrect. getCustomerShippingAddress() was modified and renamed to getCustomerShippingAddressRequest(). order_purchaseOrderNumber() had an incorrect element name. Some examples were incorrect. Better examples for each method were added, with full details and all possible parameters. A Godaddy proxy option for curl was added.
- 04 Jan 2008 00:59
Changes: Some regular expression patterns were incorrect.
- 28 Dec 2007 23:05
Changes: Currently, only the credit card payment type has been tested. Checks (echeck) and WellFargo (securesource) payment types are implemented according to the manual, but not tested.
