topic Re: Test gateway returns XML production AIM gateway will not in Integration and Testing

Test gateway returns XML production AIM gateway will not

aaronogle — Tue, 30 Apr 2013 21:53:23 GMT

We just finished developing our application using the developers gateway. The response was always returned in XML. So we coded to handle XML.

Now we have switched to the live/production gateway, and suddenly its throwing errors. Apparently you have to have either x_relay_response or x_delim_data has to be true, while the other has to be false. So regardless I can't get XML back?

Can someone help me understand this? Why would the developer gateway allow it and production not?

I understand that this gateway is used for multiple api types.. But surely there is a way to get XML back? We've spent weeks on this. Makes no sense to now have to go in and write a function to parse a delimited string.

Thanks,

Re: Test gateway returns XML production AIM gateway will not

RaynorC1emen7 — Tue, 30 Apr 2013 22:52:46 GMT

it is sending to the production xml url?

https://api.authorize.net/xml/v1/request.api

http://www.authorize.net/support/AIM_guide_XML.pdf

Re: Test gateway returns XML production AIM gateway will not

aaronogle — Wed, 01 May 2013 02:28:17 GMT

No we are submitting POST vars. As the AIM documentation details doing. Using the gateway the AIM documentation recommends. https://secure.authorize.net/gateway/transact.dll

Unless its possible to submit POST vars in non XML to the XML api.

Re: Test gateway returns XML production AIM gateway will not

RaynorC1emen7 — Wed, 01 May 2013 11:15:37 GMT

Shouldn't be able to post vars and get result in XML. Probably a bug in the test server setup on authorize.net

What AIM fields are you sending to the test server?

Re: Test gateway returns XML production AIM gateway will not

aaronogle — Wed, 01 May 2013 13:59:47 GMT

Simply leaving off both x_relay_response and x_delim_data on the test server returns XML. The production one fails with out one of the two.

For sure need to either make this consistant and use xml or the test gateway needs to respond like the production gateway.

Opted to just parse the delimited string. Which just seems dirty. XML is so much cleaner to parse.

Re: Test gateway returns XML production AIM gateway will not

RaynorC1emen7 — Wed, 01 May 2013 14:10:36 GMT

If I do that on the test server I get (92) The gateway no longer supports the requested method of integration.

Re: Test gateway returns XML production AIM gateway will not

aaronogle — Wed, 01 May 2013 14:38:03 GMT

We were using https://test.authorize.net/gateway/transact.dll

We may have had something present that makes it return xml. I'm not sure. The code has changed since that point, while trying to debug it and get it to put out xml on the production.

Regardless. XML should be an option.