Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard Issuer Response Code 10: Partial Approval

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
10
Response
10
Detailed Response
Partial Approval

What it means

Mastercard response code 10 indicates a Partial Approval. The issuer has successfully approved the transaction, but for an amount lower than the original requested amount. This occurs when the merchant indicates support for split tenders, and the approved amount is returned in Data Element 6 (DE 6).

Why does code 10 occur?

  • The cardholder's available funds or authorization capacity on their debit or prepaid Mastercard only cover a portion of the requested purchase amount.
  • The merchant terminal correctly signaled support for partial approvals (via DE 48, subelement 61, subfield 1) and the issuer opted to authorize a partial amount.

How to solve 10?

This is a successful partial authorization, so no error resolution or retry is needed for this specific transaction. Capture the approved amount indicated in DE 6 and process the remaining balance as a separate transaction using another payment method.

Solving as a merchant

Process the capture for the partially approved amount. Prompt the customer to pay the remaining balance using an alternative payment method.

Solving as a client

Complete the purchase by providing an alternative payment method for the remaining balance.

See the full list of Mastercard's decline codes >Find code on Mastercard'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.