Refund support for Global Gateway

[davidwoodmansee]

Global Gateway has a parameter called transaction_tag that is used to identify the original transaction you want to modify for a prior-auth capture, void or refund. From what I've seen in other Omnipay gateways, that should be the parameter used for the transactionReference property. In keeping with that pattern, I changed the method getTransactionReference to return transaction_tag, and added a method getAuthorizationCode which returns the authorization_num response, similar to how the Authorize.net gateway works.

Other than that, the refund functionality should be straightforward.

Cheers!

[davidwoodmansee]

Hi, I was wondering if there were any issues that would prevent this branch from being merged? This functionality is a requirement for some of my clients and it also sets up the Global Gateway plugin so that its ready to add prior-auth capture and void functionality, should the need arise. Any feedback is welcome and appreciated.

Thanks!

[SethTompkins]

+1 for this change.

[delatbabel]

Since you're using this gateway I'll give you a heads up on a planned change.

First Data have divested themselves of the Global Gateway e4. It is now called the Payeezy Gateway. First Data have renamed a number of their gateways and this one now no longer belongs to the First Data Global Gateway suite.

I have a repository aside with the changes here: https://github.com/delatbabel/omnipay-firstdata

Note that I have already made the changes to implement pre-auth, void, refund and capture, however the backwards compatibility breakage is that the gateway will be renamed from FirstData_Global to FirstData_Payeezy.