We are about to go in production with our system and the client decided that now they want to separate parts of their business and use two different Authorize.Net Merchant accounts. That means two pairs of API Login ID and Transaction Key. On the development side, we used to have a process that was rounting all the payment requests to the Authorize.Net host, using the API Login ID/Transaction Key that was initially given to us. With this new change, the process needs to procure the proper pair API Login ID / Transaction Key with each payment request, since the request may use one of the Merchant Accounts or the other (both sides of their business operations can issue requests for payments). The question I have relates to the production URL for the SOAP Service we call for each payment request. Will that be the same for all Merchant Accounts or can it be different? I think I read somewhere that the service's URL (for the sandbox it is https://apitest.authorize.net/soap/v1/Service.asmx) in production is something like this:
https://api.authorize.net/soap/v1/Service.asmx
(at least that's what the CIM documentation indicates).
Are there other considerations that we should be aware of, when working with two different Merchant accounts? Obviously, the batch reconciliation must be done separately, for each Merchant Account. What else am I missing?
Thanks for your advice.
Regards,
Eddie
