NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #3043 most downloaded on Packagist
Authorize.Net gateway for the Omnipay payment processing library
Latest stable
3.3.0
Last release 8 years ago
no release in 18 months
Ships fairly regularly
a new release about every 4 months
Most releases are documented
notes for 11 of 18 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
18 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Issue #123 / PR #128 + #129 (HMAC signature further changes).
Issue #101 retail data supported for AIM authorize/purchase request.
See:
Was going to be a patch release for #125, but #101 new functionality tips it over into a minor release. Details are in the docs of the additional retail data parameters.
This change is urgent (January 2019) as the support for the legacy md5 hashing for SIM and DPM will be removed shortly. After updating, add the follow
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This change is urgent (January 2019) as the support for the legacy md5 hashing for SIM and DPM will be removed shortly. After updating, add the following attribute to your gateway:
$gateway->setSignatureKey('{long signatureKey generated in your account}')
The APIs AIM, CIM, DPM and SIM are all deprecated, and are now replaced by a single REST API, with some AJAX support to handle card token creation. Th…
This supports Omnipay v3.0.
Please see the Authorize.Net upgrade page here: https://developer.authorize.net/api/upgrade_guide/
The APIs AIM, CIM, DPM and SIM are all deprecated, and are now replaced by a single REST API, with some AJAX support to handle card token creation. These are best all served by a new Omnipay driver. The new driver can use JSON throughout, and not need the extra complexity supporting multiple API types.
Nothing published for this version
Additional functionality to support CaptureOnly, allowing funds to be captured through the authority of an external authorisation (authCode).
Additional functionality to support CaptureOnly, allowing funds to be captured through the authority of an external authorisation (authCode).
API details here - though the documentation is not correct at this time (see Issue #93 for an explanation).
Details in Issue #93
Code in Issue #94
There are no intentionally BC breaking changes, but just be aware of any workarounds you may have in place for long-standing bugs.
Release 2.5.0
There are quite a few changes in this release - many more than I ever intended - hence a minor version update rather than a patch release. There are no intentionally BC breaking changes, but just be aware of any workarounds you may have in place for long-standing bugs.
Any issues found here, I'll aim to patch quickly.
PR46: shipping first name was being passed as the last name. This has been fixed.
PR46: shipping first name was being passed as the last name. This has been fixed.
Fixes a problem with the ordering of some optional fields in the AIM XML message, resulting in rejection of authorisation request by Authorize.Net.
Fixes a problem with the ordering of some optional fields in the AIM XML message, resulting in rejection of authorisation request by Authorize.Net.
Fix is minor and recommended if using AIM with v2.4.0. It has no impact on DPM. I'm unsure of its impact on SIM.
Migrate to AIM and CIM XML API, from the original (positional parameter?) API.
Migrate to AIM and CIM XML API, from the original (positional parameter?) API.
This affects both the AIM and CIM APIs though should have no functional effect. It does move forward to the newer API that Authorize.Net recommend is used.
However, do test this release in UAT/pre-production thoroughly before deploying to production. A lot of changed code is incorporated in this release, so some edge-case bugs may have got past us. If you find any, we will aim to fix and add new tests quickly.
Many thanks to all involved. This change has been a long time in the making.
See PR #34 for more details of the changes
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix SIMGateway->purchase() mapped correctly to SIMPurchaseRequest (@manuelpayano)
Nothing published for this version
Nothing published for this version
SIMAuthorizeResponse now implements RedirectResponseInterface
SIMAuthorizeResponse now implements RedirectResponseInterfaceAIMPurchaseRequestNothing published for this version
One column per quarter.