PR #123 (HMAC signature); XML decoding fixes

• Issue #123 / PR #128 + #129 (HMAC signature further changes).
• PR #130 XML decoding fixes; no issue raised.

Support AIM retail data and fix query functions namespaces

See:

• Issue #101 retail data supported for AIM authorize/purchase request.
• Issue #125 fix namespaces for some AIM query functions that were not working at all.

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.

Issues #123 #118 #101 - RECOMMENDED INSTALLATION

Issue #123 Support HMAC SHE-512 hash rather than md5

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}')

Issue #118 InvalidArgumentException: Invalid header syntax bug

Issue #101 Add support for retail data to AIMAuthorizeRequest

Supporting Omnipay v3.0

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.

CaptureOnly Support

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

Various fixes and enhancements

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.

• Issue #25 PR #66
  Restore InvoiceNum to its proper intention, rather than as a placeholder for the transactionId.
• Issue #40 PR #74
  Return full message on authenticatino error.
• Issue #41 PR #77 PR #80
  Support opaqueDataDescriptor and opaqueDataValue in payment transactions.
  Additional work will be needed to wrap this into perhaps a cardReference setting/getter pair.
• Issue #42 PR #54
  Akamai SureRoute new endpoint URLs
• Issue #43
  Fix "description" field.
• Issue #50 PR #52
  Fix error on getTransactionReference if payment failed.
  Additional discussion on that issue raised other points about the format of the transactionReference.
  I'll try to get those moved to a new issue.
• Issue #58 PR #74
  Similar to issue #50
• Issue #59 PR #
  Fix customer email field
• Issue #69 PR #71
  Fix invoice number on CIM

Any issues found here, I'll aim to patch quickly.

Fixed shipping first name/last name mixup

PR46: shipping first name was being passed as the last name. This has been fixed.

Issue #38 fix

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.

2.4.0: Merge pull request #34 from anushr/xml-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

Make omnipay_transaction_id a hidden DPM field by default

See PR #27 for details.