Fix ProceedRequest (WebdirectGateway::completeAuthorize)

Merge pull request #5 from niels-nijens/fix-proceed-request

Fix ProceedRequest (WebdirectGateway::completeAuthorize)

Fix StatusResponse::isSuccessful to return true when the response is successful

Fixes the StatusResponse::isSuccessful implementation to the implementation expected by the description of ResponseInterface::isSuccessful of Omnipay.

Change CaptureRequest on already captured payments back to successful

Fixes/changes CaptureRequest on already captured payments back to successful.

Please note that a capture request is still made to CM Payments (previously known as DocData Payments) and thee request is afterwards modified based on the status request.

Fix CaptureRequest implementation

Please note that this also changes a capture on an already captured payment to not successful. Also, capture SOAP calls are now always made to CM Payments (previously known as DocData Payments) and not faked within the Omnipay implementation.

Add isCancelled functionality

The isCancelled() functionality has been added to both Webdirect and One Page Checkout gateways. Before this a request would give a fail state when the user pressed cancel. Now it's possible to be more specific why the payment didn't go through.

One page checkout : select most recent payment

Onepagecheckout has a different flow for bank transfer now, and always select the most recent payment instead of the first.

Split Webdirect requests from OnePageCheckout requests

Unfortunately this is a backwards compatible break.

In the new version (2.0.0) there are two gateway files, one for requests that use webdirect (ideal, etc), and ones you don't want to use webdirect for (bank transfer, maybe credit cards). This functionality was delegated to the clients in version 1.0, by setting parameters in the data, but can now be managed by using the different gateways.

Webdirect request support

This release adds support for webdirect requests. This way you can send the issuer BIC for ideal, credit card information (if you wish to do so), and thusly skip docdata pages in-between. It should still be possible to handle one page checkout flows though.

Tested flows with ideal, bank transfer and credit card (one page checkout flow using the skip start / proceed parameters).