Authorize.Net · Decline codes
What does Authorize.Net 123 “This account has not been given the permission(s) required for this request” mean?
Checked
Authorize.Net response reason code 123 means a user's personal login ID is being used to connect a website or billing software to the payment gateway. Authorize.Net does not allow personal logins such as Account Owner or Administrator for integrations, for security reasons. Generate an API Login ID and Transaction Key in the Merchant Interface and enter those in your software.
- Type
- Error (credentials)
- Who declined
- Your Authorize.Net credentials
- Retry
- No, until the right API credentials are used.
- Shopper action
- Nothing; the store has to fix its settings.
- Merchant action
- Generate an API Login ID and Transaction Key and use those in your software.
What PlatformDTC does
PlatformDTC connects to a store's Authorize.Net account with the API Login ID and Transaction Key only, which is the credential pair Authorize.Net requires; code 123 appears when a personal login is entered instead.
Why it happens
Authorize.Net separates user logins from integration credentials. Software must use the API Login ID.
What the store can do
In the Merchant Interface, open the API credentials settings, note the API Login ID, create a new Transaction Key, and update your software.
For developers
errors[0].errorCode "123". merchantAuthentication.name must be the API Login ID, transactionKey the Transaction Key.
Frequently asked questions
- Can I use my Authorize.Net username to connect my store (code 123)?
- No. Authorize.Net requires the API Login ID and Transaction Key for software connections.
- Where do I find the API Login ID?
- In the Authorize.Net Merchant Interface, in the API credentials settings.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
Related
- 13 — The API Login ID is wrong, sent to the wrong environment, or the account is inactive.
- E00007 — The API Login ID or Transaction Key is wrong, or sent to the wrong environment.
- 124 — Your processor does not support transactions flagged as recurring.
- 153 — The wallet payment data (such as Apple Pay) could not be processed as sent.
- 154 — Apple Pay is not switched on for this Authorize.Net account.
- 289 — Your processor will not run a $0 card check for this card brand.
- 19 — Authorize.Net did not get an answer from the card processor (a connection problem).
- 20 — Authorize.Net lost contact with the card processor before getting a response.