Currently, we authenticate with a Login ID and a Transaction Key for our connections to Authorize.Net and CIM.
We're considering switching our system to a different merchant, who wants us to move to a new account on Authorize.Net.
That would (I assume) result in a new Login ID and Transaction Key.
How does that affect CIM? Is there a way for Authorize.Net to move our data from the old account to the new one and all of the existing CIM IDs remain unchanged? Or is our only option the incredibly-unpractical method of attempting to capture all of the credit card information again from our customers?
07-11-2012 12:47 PM