The 95% balance policy: what to script for support

swype

SPENDING & ACCEPTANCE • BALANCE BUFFER

The 95% balance policy: what to script for support

A single transaction can't use more than ~95% of available balance. This is one of the most common "decline with funds available" tickets — here's how to resolve it without escalating.

AUDIENCE

B2B Clients

MAX SINGLE TXN

~95% of balance

DECLINE FEES

Still apply

Summary: a single transaction cannot exceed approximately 95% of available card balance. The buffer accounts for authorization holds, rounding, or point-of-sale fees. Declines triggered by this policy still incur the standard decline fee — build that into your end-user messaging.

①

Why the buffer is necessary

This connects directly to how authorization holds work under the Card Program Terms: some merchants authorize for more than the final price (rounding, currency conversion, point-of-sale fees), and certain merchant categories — hotels, car rentals — authorize for amounts that may exceed the final transaction entirely. The 95% threshold keeps a margin available so those holds don't fail outright against an exact balance.

Card Balance

Maximum Single Transaction

$20.00

~ $19.00

$50.00

~ $47.50

$100.00

~ $95.00

②

First-line support script

This is a frequent "decline with funds available" ticket pattern. Before escalating, your support team can resolve it directly:

Compare the transaction amount against the card balance at time of attempt — if it's above ~95%, this is very likely the cause

Confirm the policy and the math using the reference table, rather than treating it as an unexplained decline

Offer the same three resolutions every time: add a small buffer, reduce the transaction amount, or split the payment if the merchant supports it

③

Fees still apply on these declines

The 95% policy doesn't make the resulting decline exempt from standard decline fees under the Card Program Terms:

●

$0.15 domestic decline fee

●

$0.55 international decline fee

If a specific end-user population is repeatedly hitting this threshold (e.g., funding cards to the exact spend amount), that's a fee leakage pattern worth addressing through funding amount guidance in your own product, rather than letting it recur silently.

Important

If your platform funds cards programmatically, consider funding slightly above the intended spend amount by default rather than to the exact cent — it prevents this exact decline pattern at scale.

Seeing this pattern at volume?

Share the merchant and typical funding amounts and we'll help you tune your funding logic.

Contact Support →