cancel
Showing results for 
Search instead for 
Did you mean: 

CIM Soap / Switch from Sandbox to Live does not work

Hi there,

 

We are currently incorporate CIM into our website. We are using the SOAP solution. Anyway, in Sandbox Mode everything works like a charme. CustomerID and Payment Profiles are created, we can process payments and refunds. 

 

BUT, if we switch from Sandbox to a Live Environment, nothing works. Instead of the profiles just the email address and a customerid but no payment profile id is created.

 

And if we charge a payment using the customerid and profileid of a manually created profile, we get a success response, but no transaction id as the transaction is not executed.

 

What are we doing wrong ? Is there anything else we have to consider when we switch over ?

 

Any input or help is more than welcome. I also do not mind paying a specialist to have a look at the code and come up with a solution.

 

Thank you !!!

Fliavo
Member
5 REPLIES 5

You said there is no transaction id. Is the test mode turn on? Need to be off.

RaynorC1emen7
Expert

I presume the test mode is turned off as we are using https://api.authorize.net/soap/v1/Service.asmx" instead of the test link.

 

Am I missing something, and the test mode has to be turned off somewhere else ? The account itself is in live mode as well.

 

C.

If the test mode is off on the merchant account, then it is in live mode

 

And if we charge a payment using the customerid and profileid of a manually created profile, we get a success response, but no transaction id as the transaction is not executed.

Then you need to Talk to your developer see the error on why it is not creating transactions.

 

The problem is that we do not get an error message. We get a success response, but the transaction is not done.

 

Can someone recommend a provider to have a look at the code we have ? I do not mind paying for this service.

Certified Developer Directory

 

If the response is success, it should return detail info of why it didn't create the transaction.

Page 71   on http://www.authorize.net/support/CIM_SOAP_guide.pdf

directResponse should have the reason.