amount_too_largemediumAffects MRR

Stripe amount_too_large Error — Causes, Fix & MRR Impact

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.

What this means

The charge amount is too large for this payment method or Stripe's limit. Reduce the amount, use another card, or split the payment if supported.

Why it happens

Stripe per-transaction limit

The amount exceeded Stripe's maximum for a single charge (check your account and currency).

Issuer limit

The card or account has a per-transaction or daily limit that was exceeded.

Wrong amount or currency

A bug sent the wrong amount (e.g. wrong unit or currency) resulting in an oversized value.

Product or plan limit

Your product or Stripe configuration may cap the amount for this type of charge.

MRR Impact

Amount limits cause failed charges; validating amount and offering alternatives protect MRR.

Validating amount and offering alternatives protect MRR when limits are hit.

Avg. recovery rate: Good when amount is fixed or customer uses another method; splitting can help for large amounts.

Urgency: within 24h

How to fix it

  1. 1

    Verify the amount

    Check that the amount and currency are correct (e.g. in smallest unit). Fix any bug in pricing, proration, or currency conversion. Compare with Stripe's documented limits.

  2. 2

    Do not retry same amount

    Do not retry with the same amount. Either fix the amount or ask the customer to use a card with higher limits or split the payment.

  3. 3

    Show clear message

    Tell the customer the amount exceeds the limit for this payment method and suggest using another card or splitting the payment if possible.

  4. 4

    Consider installments or split

    For large one-time or annual charges, consider offering installments or multiple charges if your product and Stripe support it.

  5. 5

    Log amount and currency

    Log the amount and currency when amount_too_large occurs; use to validate pricing logic and spot bugs.

Detect amount_too_large automatically

Track amount_too_large with amount; alert on spikes that might indicate a bug.

Monitor your Stripe health free →

FAQ

What does Stripe amount_too_large mean?
amount_too_large means the payment amount exceeds the limit allowed (e.g. Stripe's per-transaction limit or the issuer's limit). For SaaS, validate amount before charging; for large upgrades or annual plans, consider breaking into smaller charges or asking the customer to use another method. Fix the amount or get customer to use a card with higher limits.
Should I retry amount_too_large?
Do not retry the same amount. Either reduce the amount (if you had a bug), or ask the customer to use a payment method with a higher limit or split the payment if your product supports it.
How do I prevent amount_too_large?
Check Stripe's and your own limits before creating a charge. For very large amounts, warn the customer or offer installments. Ensure currency and amount are correct (e.g. smallest unit).
Does amount_too_large affect MRR?
Yes. Failed charges due to amount reduce MRR. Validating amount and offering alternatives (e.g. different card, split) protect MRR.

Related errors

amount_too_small

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.

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 MRRcard_velocity_exceeded

The Stripe card_velocity_exceeded error occurs when the customer has exceeded the card's balance, credit limit, or transaction limit, causing the issuer to decline and potential MRR loss for SaaS businesses processing subscription payments.

Affects MRR