Authorize.Net · Decline codes
What does Authorize.Net 5 “A valid amount is required” mean?
Checked
Authorize.Net response reason code 5, "A valid amount is required", means the value submitted in the amount field did not pass validation as a number. It is an integration problem on the store's side, such as an empty, zero, negative or badly formatted amount. The shopper cannot fix it; the store or its developer needs to correct what the checkout sends.
- Type
- Error (integration)
- Who declined
- Authorize.Net's validation
- Retry
- Only with a valid amount.
- Shopper action
- Nothing; contact the store if checkout keeps failing.
- Merchant action
- Check that your checkout sends a positive amount in the right format.
What PlatformDTC does
PlatformDTC always computes the Authorize.Net charge amount on its server from the cart, never from the browser, and refuses the charge if no server price is available, so a malformed amount does not reach Authorize.Net from its checkout. If a renewal ever came back with code 5, it would not be retried on the same amount; the customer would be asked to update their payment method.
Why it happens
Authorize.Net's note: "The value submitted in the amount field did not pass validation for a number."
What the store can do
Ask your developer or platform to check the amount sent: the order total as a decimal number with a decimal point and no currency symbol.
For developers
errors[0].errorCode "5". Authorize.Net's API reference defines amount as the total, a decimal of up to 15 digits with a decimal point and no currency symbol.
Frequently asked questions
- Who fixes Authorize.Net code 5?
- The store's integration; the shopper cannot.
- What amount format does Authorize.Net expect?
- The total amount as a decimal with a decimal point, up to 15 digits, and no currency symbol, per Authorize.Net's API reference.
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
- 49 — The amount is above the maximum transaction amount allowed on your account.
- 39 — The currency sent is not the one your Authorize.Net account is set up for.
- 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.
- 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.