Migrate to XML API for AIM + CIM support

[anush]

PR Highlights:

• Migrates the AIM gateway to use the new and improved XML API. As part of this change, the SIM classes have been completely decoupled from the AIM classes; they used to share some functionality earlier, but that's no longer possible since the endpoints and data format are now very different.
• Added integration tests that actually hit AuthorizeNet. These make me feel a LOT safer when rolling out big changes like this one. Note that these tests only kick in if the following environment variables are set: AUTHORIZE_NET_API_LOGIN_ID, AUTHORIZE_NET_TRANSACTION_KEY.
• Introduces support for a new CIM gateway (Customer Information Manager) which supports creating cards and customer profiles. Ideally, this should have been a separate PR, but Using the XML API for AIM gateway #6 (the original PR for migrating to the XML API) got quite stale over time and too much CIM work had been done to backtrack now and split it up.

Note: This PR replaces #6.

[delatbabel]

Looks good to me. Can someone who actually has gateway keys verify that this actually works in the real world? The PR that this replaces has been tossed around for a while so I think it's time we considered merging this.

[judgej]

Was hoping to look at this sooner, but got dragged into other things this weekend. I can look at this from the DPM view first, then work backwards into SIM, AIM and CIM. I've got codes for this, but generally am only using DPM in production for its easier PCI conformance. This week, definitely.

[anush]

Just an FYI, we deployed this to production last Tuesday. So far so good with AIM & CIM.

[judgej]

Thanks.

[judgej]

Am I looking at the right branch? The SIM gateway still seems to extend the AIM gateway. I used this to get the branch to test:

git clone https://github.com/anushr/authorizenet.git xml-api

When submitting a DPM form, this is giving me the following error at https://apitest.authorize.net/xml/v1/request.api

{
    "messages": 
{
    "resultCode": "Error",
    "message": 
[
            {
                "code": "E00001",
                "text": "Unexpected character encountered while parsing value: x. Path '', line 0, position 0."
            }
        ]
    }
}

I'm not sure if this is in response to the callback - I'll check.

[judgej]

Ah, got it. You changed the AIM endpoints to XML endpoints, but those URLs now filter down to SIM and DPM, for which they don't work as those methods don't use XML. SIM may, but DPM just uses a direct POST so no XML is involved.

If you could modify Omnipay\AuthorizeNet\SIMGateway::getDefaultParameters() to set the original endpoints for the default, then we can give it another go. This works for me, as a quick hack, but it's probably best done from your end than me trying to merge it into your PR to avoid branch hell:

    public function getDefaultParameters()
    {
        $parameters = parent::getDefaultParameters();
        $parameters['hashSecret'] = '';
        $parameters['liveEndpoint'] = 'https://secure2.authorize.net/gateway/transact.dll';
        $parameters['developerEndpoint'] = 'https://test.authorize.net/gateway/transact.dll';

        return $parameters;
    }

Maybe stick a comment in there too, and a test to check the default endpoints for each gateway (AIM/CIM/DPM), but that's not essential for merging.

Thanks :-)

[anush]

@judgej I've fixed the endpoints for SIM & DPM

[judgej]

Thanks - that's DPM working for me again. Will try SIM next.

[judgej]

Finally got around to testing SIM with my test account. All works without a hitch.

How's your production instance going? Any changes needed, or is it just ticking along taking payments? I'll merge if there are no further changes or surprises you've found in production.

[anush]

Awesome!

AIM & CIM have been working smoothly in production. No issues whatsoever. Pleasantly surprised :)

[aditya-cherukuri]

Would be nice if deleteCard is supported for CIM.

[judgej]

Sorry for the delay in merging - just up to my neck in all sorts here :-)

Would you like to give dev-master a try to confirm it all looks okay to you. I'll do the same this end on a test site. This would then be release 2.4.0.

[anush]

Nice!

I gave dev-master a whirl. Works fine locally and all the functional tests in our application passed. So looks good to me.

[aditya-cherukuri]

I have tried the AIM and CIM gateways with sandbox accounts I was successful in performing transactions.

[judgej]

Thanks. Just finding the time to try it on my DPM UAT system, then we can go for a release.

[judgej]

Works fine on my UAT system using DPM.