amount_too_smalllow

Stripe amount_too_small Error — Causes, Fix & MRR Impact

The Stripe amount_too_small error occurs when the payment amount is below the minimum allowed for the currency or Stripe, causing the charge to fail for SaaS businesses processing subscription payments.

What this means

The charge amount is below the minimum allowed (e.g. currency minimum). Increase the amount or adjust your pricing logic.

Why it happens

Below Stripe or currency minimum

The amount was below the minimum (e.g. $0.50 USD or equivalent). Stripe rejects it.

Proration or credit too large

A large credit or proration reduced the amount to below the minimum.

Wrong unit or decimal

Amount was sent in wrong unit (e.g. dollars instead of cents) or rounded down incorrectly.

Tiny plan or add-on

The plan or add-on price is below the minimum for the currency.

MRR Impact

Usually small impact; fixing minimums and proration logic avoids failed charges and keeps MRR accurate.

Enforcing minimum amount in pricing and proration logic avoids this error.

Avg. recovery rate: N/A; fix in code or skip tiny charges per business rules.

Urgency: within week

How to fix it

  1. 1

    Check minimum per currency

    Look up Stripe's minimum charge amount per currency. Ensure your amount is at least that (in smallest unit).

  2. 2

    Fix proration and rounding

    When computing proration or credits, ensure the final amount is at least the minimum. Round up if necessary, or combine with the next invoice per your business logic.

  3. 3

    Do not retry same amount

    Do not retry with the same amount. Fix the amount in your code or skip the charge if your rules allow (e.g. zero or tiny proration).

  4. 4

    Validate before creating charge

    Before creating a PaymentIntent or Invoice, validate that the amount meets the minimum for the currency.

  5. 5

    Log for debugging

    Log amount_too_small with amount and currency; use to find pricing or proration bugs.

Detect amount_too_small automatically

Track amount_too_small; fix pricing or minimum logic to avoid recurrence.

Monitor your Stripe health free →

FAQ

What does Stripe amount_too_small mean?
amount_too_small means the payment amount is below the minimum allowed (e.g. Stripe or currency minimum). For SaaS, validate amount before creating the charge; ensure proration or plan price is at least the minimum for the currency. Fix the amount in your logic or combine with another charge if applicable.
Should I retry amount_too_small?
Do not retry with the same amount. Fix the amount (e.g. ensure it meets the minimum for the currency) or skip the charge if it is a tiny proration and your business logic allows it.
How do I prevent amount_too_small?
Check Stripe's minimum amount per currency (e.g. USD often has a $0.50 minimum). When computing proration or discounts, ensure the final amount is at least the minimum or round up.
Does amount_too_small affect MRR?
Usually minor; it often affects small prorations or one-off charges. Fixing pricing logic and minimums avoids failed charges and keeps reporting accurate.

Related errors

invalid_amount

The Stripe invalid_amount error occurs when the payment amount is invalid or exceeds the amount the issuer allows, causing the charge to be declined and MRR risk for SaaS businesses processing subscription payments.

Affects MRRamount_too_large

The Stripe amount_too_large error occurs when the payment amount exceeds the allowed limit (Stripe or issuer), causing the charge to fail and MRR risk for SaaS businesses processing subscription payments.

Affects MRR