Amount too small amount_too_small
What this decline means
The renewal was refused before it ever reached the cardholder: the charge was smaller than the minimum amount the payment gateway will process. The card was never asked, so nothing about the customer decides this one — the amount itself is the problem.
Why it happens on subscription renewals
- A recurring discount is applied to every cycle rather than only the first. A 100%-off or deep percentage discount that was meant as a welcome offer keeps landing on renewals, driving the charge to zero or a few cents.
- The subscription genuinely bills a tiny amount — a single cheap refill, a per-unit add-on, or a plan a customer downgraded until almost nothing was left on it.
- Line items dropped off. A subscriber removed products, reduced quantity, or an out-of-stock item fell out of the renewal, leaving a remainder that sits under the floor.
- Currency. Minimums are set per presentment currency, so the same catalogue price can clear in one market and fall under the floor in another after conversion — the failure appears in one market only and stays invisible in your main one.
- A prorated or catch-up charge from a mid-cycle change came out as a token amount that no gateway will run.
The merchant playbook
- Do not send a card-update email. This is the one failure where the customer has nothing to fix, and asking them to re-enter a working card is both useless and corrosive to trust.
- Diff the contract, not the card. Open the subscription's own discount and line items and compare them against what the first order charged — the gap between those two numbers is almost always the whole explanation.
- Check whether the discount was meant to recur. Welcome offers configured to apply to all cycles instead of the first are the single most common source of this code, and fixing the discount fixes every future renewal at once.
- Give cheap subscriptions a floor. If you sell low-cost refills on subscription, a minimum quantity or a bundled pack keeps the smallest possible renewal above the gateway minimum by design instead of by luck.
- Decide if the contract should be billing at all. A comped or zero-value subscription that grinds through billing attempts forever belongs recorded as free — not left failing every cycle and consuming retry counters.
- After you change the price or discount, sweep the cycle that already failed. The next scheduled attempt will work, but the missed cycle usually needs a manual retry — and check that auto-cancel did not already fire while the amount was wrong.
Should you retry?
No — not while the amount stays the same. This decline is deterministic, not a matter of timing or bank mood: the identical charge will be refused on every attempt, at any hour, on any day. Retrying becomes correct the moment the amount changes, and never before.
Common questions
What is the minimum amount a subscription charge can be?
There is no single universal number. The floor is set by the payment gateway and applies per presentment currency, typically in the range of a small fraction of a unit of that currency. Because it varies by provider and market, treat the code as 'below this gateway's floor' and confirm the exact figure in your own provider's documentation rather than assuming a number.
Nothing changed on my side — why did this start failing?
Something changed on the contract, even if not deliberately. A discount that only became visible at renewal, a quantity reduction, a removed product, or a line item that went out of stock all shrink the billed amount without anyone editing a price. Compare the failing renewal's total against an earlier successful one and the cause usually shows up immediately.
Should I tell the customer anything?
Not a payment-failure message. Their card is fine and there is no action they can take. If the fix takes long enough to delay a shipment, a plain service note works; a dunning email would be telling them to fix a problem that lives in your pricing.
Related codes: merchant_account_error · transaction_limit_exceeded · customer_not_found · or see the
full decline-code guide.
Where Moorly fits: Moorly reads the raw decline reason your subscription app records for each failed renewal, keeps it attached to the case instead of collapsing it to “payment failed”, and sorts failures into families, so the total you lost is broken out by the kind of failure behind it. Codes it has not yet classified are handled conservatively rather than guessed at. It starts read-only. Join the early-access list →
Moorly is an independent product by Velun Labs and is not affiliated with Shopify, Appstle Inc., or Seal Subscriptions. Code names follow Shopify's public API documentation as of August 2026; bank behavior varies by issuer — always confirm against your own admin.