Authorize.Net · Decline codes
What does Authorize.Net E00007 “User authentication failed due to invalid authentication values” mean?
Checked
Authorize.Net E00007, "User authentication failed due to invalid authentication values", means the API Login ID or Transaction Key submitted is invalid. Authorize.Net adds that if both are correct, check the URL: test accounts must post to the sandbox and live accounts to production. Every payment fails until the credentials match the environment.
- 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
- Re-enter the API Login ID and Transaction Key and check sandbox vs live.
What PlatformDTC does
PlatformDTC treats Authorize.Net E00007 as a store credential fault, not a customer decline: a subscription renewal that hits it is deferred and retried, with no dunning step and no "payment failed" email to the subscriber.
Why it happens
Authentication fails when the key pair is wrong, has been regenerated, or belongs to the other environment.
What the store can do
Generate a new Transaction Key in the Merchant Interface if unsure, update it everywhere it is used, and confirm live keys go to the live endpoint.
For developers
messages.message[0].code "E00007". Sandbox endpoint apitest.authorize.net, production api.authorize.net.
Frequently asked questions
- Why did Authorize.Net E00007 start suddenly?
- Commonly the Transaction Key was regenerated, which disables the old one, or sandbox and live credentials were mixed up.
- Is E00007 the same as code 13?
- Both are credential failures; E00007 is the API message code, 13 the transaction reason code.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
- Authorize.Net API reference: createTransactionResponse fields — Authorize.Net
Related
- 13 — The API Login ID is wrong, sent to the wrong environment, or the account is inactive.
- 123 — A personal user login was used to connect software; it needs the API Login ID instead.
- E00001 — Authorize.Net hit an internal error; the request was not completed.
- E00003 — The request sent to the API was malformed, so Authorize.Net could not read it.
- E00013 — One field in the request has an invalid value; the response text names it.
- E00039 — A customer profile with the same details already exists on the account.
- E00040 — The customer or payment profile you referenced does not exist on this account.
- E00044 — Saved customer profiles (CIM) are not switched on for this account.