Authorize.Net · Decline codes
What does Authorize.Net 13 “The merchant login ID or password is invalid or the account is inactive” mean?
Checked
Authorize.Net response reason code 13 means the merchant login ID or password is invalid, or the account is inactive. Authorize.Net says you are posting the wrong API Login ID, connecting to a server that does not recognise your account, or using an inactive account. Check the credentials and that sandbox credentials go to the sandbox URL and live ones to production.
- Type
- Error (credentials)
- Who declined
- Your Authorize.Net credentials
- Retry
- No, until the credentials are fixed.
- Shopper action
- Nothing; the store has to fix its settings.
- Merchant action
- Check the API Login ID, environment URL and account status.
What PlatformDTC does
PlatformDTC stores a merchant's Authorize.Net Transaction Key encrypted and shows Authorize.Net's message for code 13; the code is not on its reroute list, so the store has to correct the credentials in its Authorize.Net connection.
Why it happens
Authorize.Net rejects every transaction when the login is wrong, the account is inactive, or a test account posts to the live URL (or the reverse).
What the store can do
In the Merchant Interface, click Settings, then API Credentials & Keys, to see the API Login ID and create a new Transaction Key; then confirm the account is active and the keys match the environment.
For developers
errors[0].errorCode "13". With the JSON/XML API the equivalent credential failure is E00007.
Frequently asked questions
- Why do I get Authorize.Net code 13 on every payment?
- The API Login ID or key is wrong, the account is inactive, or you are posting to the wrong environment.
- Can code 13 come from using a sandbox key on live?
- Yes. Authorize.Net lists posting to a server that does not recognise the account as a cause.
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
- E00007 — The API Login ID or Transaction Key is wrong, or sent to the wrong environment.
- 123 — A personal user login was used to connect software; it needs the API Login ID instead.
- 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).