Information on Authorize.net migration

The content in this blog is over six months old, and the comments are closed. For the most recent product updates and discussions, you're encouraged to explore newer posts from Instructure's Product Managers.

zsgoreczky
Instructure Alumni
Instructure Alumni
10
3064

As Authorize.net made it public, they have deprecated and are sunsetting their SIM solution, a.k.a. the “classic” Authorize.net payment gateway. Their recommended upgrade path is Accept Hosted, which is offered by Payment Redirector, therefore is safe to use. (See https://developer.authorize.net/api/upgrade_guide.html#sim ) The time has now come for all our clients who still use the legacy SIM gateway to transition to the new solution. The transition should be smooth and requires minimal changes to the account’s Authorize.net configuration and no contractual changes as far as we know. 

If you are aware of your Catalog instance using Authorize.net, in the upcoming days please contact your CSM if they haven’t reached out to you about the migration yet. They will help to coordinate between you and the engineering team. You will likely need to apply some minor changes on your Catalog account, but please don’t worry about this, we will be there to help and they will be really minor. The migration will be done in batches, but be assured, until we finish processing migrations, all legacy SIM solutions will still work.

 

If you have any questions, please send those to your CSM. 

Thank you, 

Zsofi

The content in this blog is over six months old, and the comments are closed. For the most recent product updates and discussions, you're encouraged to explore newer posts from Instructure's Product Managers.

10 Comments