Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa Issuer Response Code 10: Approved, partial

soft decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
10
Response
10
Detailed Response
Approved, partial
soft decline
This transaction is retriable

Payments failing with code 10 are often recoverable with the right retry timing and routing. SmartRetry recovers up to 70% of soft declines with smart retries!

Actually, a big part of your declined transactions can be recovered

Recover your revenue >

What it means

Visa issuer response code 10 indicates a partial approval rather than a conventional decline. It occurs when a card's available balance is insufficient to cover the full purchase, but the merchant's payment request indicated support for partial authorizations. The issuer approves the remaining available balance on the card, requiring the merchant to collect the difference using another payment method.

Why does code 10 occur?

  • The cardholder's available balance is less than the total requested transaction amount.
  • The merchant system successfully flagged the transaction as supporting partial authorizations via the Partial Authorization Indicator (Field 60.10).

How to solve 10?

Calculate the remaining balance by subtracting the partially approved amount (returned in Field 4) from the originally requested amount (returned in Field 54). Prompt the customer to provide an alternative payment method to cover the outstanding balance. If the customer completes this split-tender checkout, clear only the partially approved amount against the original card. If the customer abandons the transaction or cannot provide another payment method, you must send an authorization reversal to release the partially approved funds.

Solving as a merchant

Ensure your checkout flow or stand-alone terminals correctly support split-tender transactions before sending the Partial Authorization Indicator. Train cashiers or update your e-commerce UI to clearly communicate the partially approved amount and the remaining balance due to the customer. Always reverse the partial authorization if the customer chooses to cancel the order.

Solving as a client

Review the partially approved amount and provide a secondary payment method, such as another credit card, to cover the remaining balance. Alternatively, choose to cancel the transaction, which will prompt the merchant to reverse the partial charge and release the held funds.

Tip from SmartRetry Never re-attempt the full transaction amount against the same card, as this repeatedly locks up cardholder balance without completing the sale. Instead, automate an immediate authorization reversal if a secondary payment method isn't secured within a strict checkout session window.

See the full list of Visa's decline codes >Find code on Visa's website >

Frequently asked questions about this topic

Share this article

Share on XShare on FacebookShare on LinkedIn
Kyle Regacho

Author

Kyle Regacho
LinkedInFind me on Linkedin

Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue

Read all articles >

Articles you may find interesting:

View all
How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

Discover how automated risk reviews trigger gateway freezes and how payment teams can insulate revenue through multi-acquirer setups and smart retry logic.

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Payment rejections cost merchants billions in lost sales and unforced churn. Discover the root causes behind issuer declines and how intelligent recovery strategies salvage legitimate revenue.

Why Payment Tests Pass in Staging and Fail in Production

Why Payment Tests Pass in Staging and Fail in Production

Passing a sandbox check rarely guarantees live authorization success. Learn how real-world issuer ambiguity, webhook delays, and network retry rules impact revenue pipelines.

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Sandboxes verify API formatting, but live issuers determine transaction success. Discover how multi-layered testing, safe retry logic, and real-time observability safeguard authorization rates and reduce involuntary customer churn.

Decline codes tell you why. We fix it.

SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.