POST /gateway/transact.dll → endpoint removal
Authorize.net AIM/SIM
Deprecated, no date
Authorize.net deprecated POST /gateway/transact.dll without a shutdown date. Calls hitting this endpoint will fail under the planned removal. The deprecation covers both AIM integrations and SIM payment forms that submit to this gateway path.
Calls it hits
POST /gateway/transact.dll
What to use instead of these calls
Move AIM calls to the Authorize.net API by using createTransactionRequest on the newer XML or JSON request endpoint. Replace SIM payment forms with Accept Hosted, which requires configuring a new hosted payment page rather than simply switching an endpoint.
SIM's hosted form moves to Accept Hosted, a different hosted payment page the merchant configures anew.
In Authorize.net AIM/SIM's words
AIM | Deprecated | Authorize.net API | SOAP API | Deprecated | Authorize.net API | SIM | Deprecated | Accept Host |
Facts
- API
- Authorize.net AIM/SIM
secure.authorize.net - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Authorize.net AIM/SIM's own pages
Questions
When does this change take effect?
Authorize.net AIM/SIM deprecated POST /gateway/transact.dll without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Authorize.net AIM/SIM has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.