Authorize.net API
cardholderAuthentication body parameter removal on POST /xml/v1/request.api
Deprecated, no dateSubscribe to Authorize.net APIShare
The body parameter cardholderAuthentication on POST /xml/v1/request.api has been deprecated without a shutdown date. Authorize.net API states that this field should not be used. Subsequent calls that continue to rely on this parameter will fail.
Calls it hits
POST /xml/v1/request.apibody parameter cardholderAuthentication
What to use instead of these calls
Stop sending cardholderAuthentication, including authenticationIndicator and cardholderAuthenticationValue, in transaction requests.
In Authorize.net API's words
cardholderAuthentication | Important: This field is deprecated and should not be used.
Facts
- API
- Authorize.net API
api.authorize.net - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Authorize.net API's own pages
Questions
When does this change take effect?
Authorize.net API deprecated POST /xml/v1/request.api, body parameter cardholderAuthentication without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Authorize.net API 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.
More from Authorize.net API 1
-
No date
/soap/v1/*Removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.