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.
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.

Hard Declines (Do Not Retry)

Permanent conditions that will not resolve on retry. Request an alternative payment method from the customer.
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

Mastercard Response Codes

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.
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.