Issue #12 support basic auth

Issue #12 support basic auth

Thanks go to @gallib for this enhancement.

Issue #7 partial fix

Handling pending transactions in some circumstances, as detailed in issue #7

There are some pending transactions that we still do not have test data for, so cannot fix the issue fully until we do and can reproduce the issue. The documentation is a little sparse here (putting it politely), so we need some real examples before taking it further.

Also fix for issue #6 and issue #4

uppAliasOnly is deprecated; use useAlias

See issue #5

This should have no noticeable change to functionality and requires no change of use.

There may be a subtle change to the way the gateway works. Previously, fetching a card alias only (by setting a zero amount) did not fully authenticate the card; it only validated the card. This was not fully clear in the documentation, but it meant a card that had a valid lunn check always came back as a successful fetch of a cardReference, whether the card was really valid or not. This would only be discovered at the back-end "repeat payment" use of that card alias. The older uppAliasOnly flag has been deprecated for a while and appears to be disappearing from the documentation now.

The new method will authenticate the card too, using whatever method the gateway uses (often done by authorising a small amount then instantly cancelling it). This allows the merchant site to catch an invalid card a little earlier in the repeat payment process.

Remove some old Guzzle references

Omnipay 3.x uses PSR-7 messages for responses, so does not need to be explicit for Guzzle.

Default errorUrl() to returnUrl()

See Issue #4

Support isCancelled()

See Issue #3

Support isCancelled()

Issue #3

First 3.0 release

Support for Omnipay 3.0

General tidy up

General tidy up

Remove PHP dependancy

Leave it up to the dependencies to make the decision.