Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
NOTICE: You must update to the new Authorize.net PHP SDK with this release. Authorize.net recently changed their libraries, and started hosting them on Github. Their changes necessitated some changes in this module, so it is highly recommended that you update both the library and this module. The new Authorize.net SDK can be downloaded here: https://github.com/AuthorizeNet/sdk-php/archive/master.zip
Fixed issue where admins trying to charge existing profiles were getting an error if the card was previously saved via checkout.
This is a followup release to the 6.x-1.0-alpha4 release, which was supposed to be a bug fix, but only worked temporarily. Now it should be fixed permanently.
Bug fix: Allow checkout to process successfully when customer selects an existing payment profile and "Set a reference only" is the default transaction method.
Default the payment profile selection to the one that was chosen during checkout, in the admin order terminal. Also add a little label to indicate that it is the one preferred for that order.
If a new payment profile is created for a customer, and the customer doesn't have a default payment profile already, set it as the default.
Change count() function of SimpleXMLElement so that it works with PHP < 5.3.
Set sandbox to FALSE if the sandbox flag is not set TRUE.
Only use validation if there are payment profiles assigned to a new customer profile. Otherwise Authorize.net complains 'Validation Mode is invalid without Payment Profiles. E00013'.
First official release of the authnet modules, including:
Authorize.net API (authnet.module)
This is the core Authorize.net API module. It provides Drupal wrapper functions for the Authorize.net SDK objects and functions. It is used by all the other sub-modules.
This module maintains an association between Authorize.net CIM customer profiles and payment profiles, and entities in Drupal. It does two main things:
Provides two database tables: one for linking Authorize.net customer profiles to entities in Drupal (ie: users), and one for keeping track of Authorize.net payment profiles (ie: credit cards).
Implements hooks provided by the authnet module to add/update/delete records from the abovementioned databases when customer profiles and payment profiles are updated via the API functions.
Authorize.net UI (authnet_ui.module)
Provides reusable UI elements like forms (ie: payment profile edit form).
Authorize.net User (authnet_user.module)
Maintains an association between Authorize.net CIM customer profiles and Drupal users. Depends on authnet_cim_entity and authnet_ui (above). It provides menu callbacks for users to add/edit/remove payment profiles (ie: manage their credit cards) at /user/[uid]/billing.