At a glance
Top decline reasons grouped by Square’sfailure_codeenum. The first card to open whensqu_decline_ratespikes. Tells you whether the cause is issuer-side, fraud-side, or expiration.
Calculation
Calculated automatically from your Square data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
7-day window, breakdown of 34 declines:
Reads:
- Generic
CARD_DECLINEDat 35% is the diagnostic black box. Cluster check oncard_details.bin(BIN = first 6 digits). INSUFFICIENT_FUNDSat 23.5% is normal. Below 15% suggests issuers obfuscating; above 30% suggests subscription book has too many low-balance customers.EXPIRED_CARDat 15% is rebill-driven. Square’s card-updater catches ~70% via Visa / MC network tokens.CVV_FAILUREat 12% suggests typing errors on Square Online checkout, or fraud testing.CHIP_INSERTION_REQUIREDat 6% is cashier-training territory.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Square Dashboard:
Reports → Risk Manager → Failed payments breakdown (where Risk Manager is enabled), or Reports → Transactions filtered by Status: Failed, grouped by reason.
Why our taxonomy may look slightly different:
Cross-connector reconciliation: decline-reason taxonomies differ between PSPs. Square’s
CARD_DECLINED ≈ Stripe’s generic_decline; Square’s INSUFFICIENT_FUNDS matches across the industry; Square’s CHIP_INSERTION_REQUIRED is POS-specific and has no Stripe equivalent.
Known limitations / merchant FAQs
“GenericCARD_DECLINED is 40% of my declines, what does that mean?”
The issuer rejected without specifics. Cluster check: slice by card_details.bin. If 60%+ of generic declines come from one BIN, that issuer has a fraud-filter triggered against your store; contact Square support.
“INSUFFICIENT_FUNDS jumped 50% week-over-week, normal?”
Often seasonal (post-payday vs pre-payday). If the spike persists 3+ weeks, subscription book quality is degrading.
“EXPIRED_CARD is mostly subscription rebills, can I prevent it?”
Square’s card-updater (Visa / MC network tokens) automatically refreshes ~70% of US issuers. Remaining 30% need a customer-facing email asking to update card.
“CVV_FAILURE rate of 10%+ on Online, what’s wrong?”
Either typing UX issues (mobile autofill conflicts) or a fraud test (someone trying card numbers without matching CVV). If clustered on one IP / device fingerprint, it’s a fraud test; block via Square Risk filters.
“CHIP_INSERTION_REQUIRED keeps coming up, can I stop the magstripe fallback?”
Cashier training reduces it. Some legacy mag-only foreign cards still need magstripe; you cannot fully disable.
“CARD_DECLINED_CALL_ISSUER what does that mean?”
The issuer wants the cardholder to call them, almost always a fraud-flag. Tell the customer to call the number on the back of their card.
“Multi-currency, does the breakdown work?”
Yes; failure_code is currency-neutral.
“Tap to Pay on iPhone reasons, any unique?”
Mostly the same as Square Reader. One unique: DEVICE_TIME_OUT (the iPhone Tap to Pay session timed out); cashier should re-initiate.