Tip from SmartRetry Suppress automatic retries for identical payloads on Code 13 to avoid issuer velocity penalties, as this decline will repeat unless the underlying data is altered. Only allow re-submission if your orchestration layer can programmatically normalize currency decimal discrepancies or route the shopper through a fresh 3D Secure challenge.
Mastercard
Mastercard Issuer Response Code 13: Invalid Amount
technical declinehard decline
Last updated: September 25, 2026
About 13 - "Invalid amount"
Key details
- 13
- Issuer Response Codes
- 13
- Invalid amount
technical declinehard decline
What it means
Mastercard issuer response code 13, carried in Data Element (DE) 39, indicates that the issuer declined the transaction due to an "Invalid amount." This code typically signals that the payment payload contained a malformed amount, an unsupported currency, or a discrepancy between the 3D Secure authenticated amount and the final authorization amount. It may also occur if the specific card type, such as a Cirrus or Maestro debit card, is restricted from making online e-commerce purchases.
Classification & retryability
technicalhardRetryable: conditional
Do not attempt a blind, time-based retry. Only retry the transaction after correcting the submitted amount format, resolving any 3D Secure authentication amount mismatches, or confirming the card is eligible for the channel.
Why does code 13 occur?
- The amount submitted for authorization is greater than the amount that was originally authenticated during the 3D Secure process.
- The transaction payload contains an invalid amount format, an unsupported currency, or an incorrectly formatted field.
- The customer used a card type, such as a Cirrus or Maestro debit or prepaid card, that is restricted from making online purchases.
How to solve 13?
First, verify that the authorization request format is correct and that the amount field does not contain invalid characters. If you are using 3D Secure, compare the authenticated amount against the authorization amount to ensure they match exactly, accounting for taxes, shipping, or subsequent order modifications. If the authorization amount is higher, you must re-authenticate the customer for the correct final amount or split the transaction. If the amount and formatting are correct, the card itself may not be supported for this transaction type, and you should prompt for an alternative payment method.
Solving as a merchant
Inspect your payment logs to confirm the amount and currency fields are properly formatted before submission. Check your 3DS authentication logs to ensure the authenticated amount was not exceeded by the authorization request due to added fees or post-checkout order modifications. If the card is inherently blocked for online use, systematically suppress that payment method for the current transaction and gracefully ask the customer to use another card.
Solving as a customer
Verify that the order total is correct and attempt the payment again. If the transaction continues to decline, use an alternative payment method or contact the card issuer to ensure the card is authorized for online e-commerce purchases.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.