Skip to main content

Overview

When a payment is processed through Yuno, the response may include codes from multiple layers: Yuno’s own error codes, Merchant Advisory Codes (MACs), and raw provider/network response codes. This reference maps these codes to help you understand decline reasons and determine the correct retry strategy.

Merchant Advisory Codes (MAC)

Merchant Advisory Codes provide standardized guidance on how to handle declined transactions. These codes indicate whether a transaction should be retried and, if so, when.
MACDescriptionRecommended ActionRetryable
01New account information availableRequest updated card details from customer via account updater or direct inputNo
02Try again later / Cannot approve at this timeRetry the transaction after a brief delayYes
03Do not retry / Do not honorDo not retry; request alternative payment methodNo
04Token requirements not fulfilledVerify tokenization setup and ensure token data is completeNo
21Payment cancelledCustomer or issuer cancelled the payment; do not retryNo
24Retry after 1 hourWait at least 1 hour before retryingYes
25Retry after 24 hoursWait at least 24 hours before retryingYes
26Retry after 2 daysWait at least 2 days before retryingYes
27Retry after 4 daysWait at least 4 days before retryingYes
28Retry after 6 daysWait at least 6 days before retryingYes
29Retry after 8 daysWait at least 8 days before retryingYes
30Retry after 10 daysWait at least 10 days before retryingYes
MACs are returned in the merchant_advisory_code field of the payment response when available. Not all providers return MACs for every decline.

Soft vs Hard Declines

Understanding the difference between soft and hard declines is critical for implementing correct retry logic.

Soft Declines (Retriable)

Temporary conditions that may resolve on retry. Implement exponential backoff with the MAC-recommended delay.
ConditionTypical Response CodeRetry Strategy
Insufficient funds51Retry after delay; customer may add funds
Issuer temporarily unavailable91Retry with exponential backoff
Processing error06Retry immediately or after brief delay
Exceeds withdrawal limit61Retry after 24 hours or next billing cycle
System malfunction96Retry with exponential backoff
Issuer not available91Retry after brief delay

Hard Declines (Do Not Retry)

Permanent conditions that will not resolve on retry. Request an alternative payment method from the customer.
ConditionTypical Response CodeAction
Invalid card number14Request correct card details
Expired card54Request updated card
Stolen card43Do not retry; flag for review
Lost card41Do not retry; flag for review
Card not activated78Customer must contact issuer
Do not honor05Request alternative payment method
Restricted card62Request alternative payment method
Retrying hard declines wastes processing resources, degrades your approval rate metrics, and may trigger fraud monitoring by card networks. Always check the decline category before implementing retry logic.

Visa Response Codes

CodeDescriptionCategoryRetryable
00ApprovedSuccessN/A
01Refer to card issuerSoft declineYes
02Refer to card issuer, special conditionSoft declineYes
03Invalid merchantHard declineNo
04Pick up cardHard declineNo
05Do not honorHard declineNo
06ErrorSoft declineYes
07Pick up card, special conditionHard declineNo
12Invalid transactionHard declineNo
13Invalid amountHard declineNo
14Invalid card numberHard declineNo
15No such issuerHard declineNo
19Re-enter transactionSoft declineYes
21No action takenSoft declineYes
25Unable to locate recordHard declineNo
28File temporarily unavailableSoft declineYes
41Lost card, pick upHard declineNo
43Stolen card, pick upHard declineNo
51Insufficient fundsSoft declineYes
54Expired cardHard declineNo
55Incorrect PINSoft declineYes (with correct PIN)
57Transaction not permitted to cardholderHard declineNo
58Transaction not permitted to terminalHard declineNo
59Suspected fraudHard declineNo
61Exceeds withdrawal amount limitSoft declineYes (lower amount or later)
62Restricted cardHard declineNo
63Security violationHard declineNo
65Exceeds withdrawal frequency limitSoft declineYes (later)
75Allowable number of PIN tries exceededHard declineNo
76Invalid “to” accountHard declineNo
78Blocked, first use (card not activated)Hard declineNo
85No reason to decline (AVS/CVV check)SuccessN/A
91Issuer or switch inoperativeSoft declineYes
96System malfunctionSoft declineYes
N7CVV2 value mismatchSoft declineYes (with correct CVV)
R0Stop recurring paymentHard declineNo
R1Stop recurring paymentHard declineNo
Q1Card authentication failedHard declineNo

Mastercard Response Codes

CodeDescriptionCategoryRetryable
00ApprovedSuccessN/A
01Refer to card issuerSoft declineYes
03Invalid merchantHard declineNo
04Capture cardHard declineNo
05Do not honorHard declineNo
08Honor with IDSoft declineYes
12Invalid transactionHard declineNo
13Invalid amountHard declineNo
14Invalid card number (PAN)Hard declineNo
15Invalid issuerHard declineNo
30Format errorHard declineNo
41Lost cardHard declineNo
43Stolen cardHard declineNo
51Insufficient funds / over credit limitSoft declineYes
54Expired cardHard declineNo
55Invalid PINSoft declineYes (with correct PIN)
57Transaction not permittedHard declineNo
58Transaction not permitted to acquirer/terminalHard declineNo
61Exceeds withdrawal amount limitSoft declineYes (later)
62Restricted cardHard declineNo
63Security violationHard declineNo
65Activity count limit exceededSoft declineYes (later)
70Contact card issuerSoft declineYes
71PIN not changedHard declineNo
75Allowable number of PIN tries exceededHard declineNo
76Unsolicited reversalHard declineNo
77Previous message not foundSoft declineYes
78Blocked (first use, not activated)Hard declineNo
84Invalid authorization life cycleHard declineNo
85Not declined (AVS only)SuccessN/A
86Cannot verify PINSoft declineYes
91Issuer unavailableSoft declineYes
92Destination not foundSoft declineYes
96System errorSoft declineYes

Provider Response Code Mapping

Yuno normalizes provider-specific response codes into a standardized decline_reason field. This allows you to implement consistent decline handling regardless of which provider processes the transaction.
Yuno Decline ReasonDescriptionTypical Provider Codes
INSUFFICIENT_FUNDSCustomer has insufficient fundsVisa/MC 51
INVALID_CARDCard number is invalidVisa/MC 14
EXPIRED_CARDCard has expiredVisa/MC 54
STOLEN_CARDCard reported stolenVisa 43, MC 43
LOST_CARDCard reported lostVisa 41, MC 41
DO_NOT_HONORIssuer declined without specific reasonVisa/MC 05
FRAUD_SUSPECTEDFraud suspected by issuer or risk engineVisa 59
RESTRICTED_CARDCard has restrictions preventing useVisa/MC 62
EXCEEDS_LIMITTransaction exceeds amount or frequency limitVisa 61/65
INVALID_CVVCVV verification failedVisa N7
ISSUER_UNAVAILABLEIssuer system temporarily unavailableVisa/MC 91
PROCESSING_ERRORGeneric processing errorVisa/MC 06/96
NOT_PERMITTEDTransaction type not permittedVisa/MC 57/58
AUTHENTICATION_FAILED3DS or PIN authentication failedVisa Q1
STOP_RECURRINGCustomer requested stop of recurring paymentsVisa R0/R1
The normalized decline_reason is available in the payment response under transaction.decline_reason. Use this field instead of raw provider codes for consistent handling across providers.