We have an existing old SIM solution working, want to migrate to our new API Accept Hosted iFrame solution for just processing cc transactions.
I'd like to have a safe migration path and hopefully use our old SIM and our new API solution in parallel. Is this possible?
- We have an OLD SIM solution that uses a "Transaction ID". There is no Signature Key!
- First, I am not sure how this is possible seeing that everything I have read says the SIM method uses a "Signature key". Maybe I am confused, but the only thing I can figure is that this version of SIM we use pre-dates Signature keys? Can you please explain why our existing SIM method uses a transaction key instead of a signature key for processing CC transactions?
- Our new solution is using Accept Hosted iFrame and seems to work pretty well in my separate sandbox account(s).
- FWIW, our existing SIM uses Transaction version 3.0, and our new solution's sandbox reports that it is using 3.1. I assume this a something that needs to be addressed to be used with the new API?
1) To go live with our new API Accept Hosted iFrame solution, do we need to create a new transaction key in our existing production environment for it to work? Or can we use the existing one that is used with the old SIM?
2) Do we need to upgrade the transaction version in our live account from 3.0 to 3.1? Will that break the existing old SIM method?
3) Will it be possible to run our old SIM solution and our new Accept Hosted iFrame API solution in the same Authorize.Net account with the same transaction key in parallel? Or is this impossible?
4) We don't want to break our existing solution, and would like to gradually move our system to using the new API. What steps and strategy would you recommend to accomplishing that safely?
Much thanks for your insight!