Closed thgaskell closed 8 years ago
After looking into this a little more, it seems like the error might be coming from somewhere else.
I did receive this email from their support team though which suggests using the createTransactionRequest
method.
We have not made any changes to the createCustomerProfileTransactionRequest. We actually no longer recommend this method and new development all goes into just createTransactionRequest which can now take profile Ids.
Interesting, I'll double check regardless thanks for the heads up.
We recently have ran into issues because it seems that the XML API has changed on AuthorizeNet's side. I'm not sure if more changes need to be made to the other projects (durango/authorize-net-types and durango/authorize-net-request)?
It looks like the code responsible for generating the xml needs to be updated to comply with their new api?
http://developer.authorize.net/api/reference