Skip to main content
Each payment has one or more associated transactions. The following documentation covers transaction types, status codes, and descriptions after an HTTP 200 status is obtained and a transaction is processed.

Workflow

Types of transactions

Transaction codes

With every transaction, you’ll receive a response_code detailing more info about it. The details related to each status are presented below. Use the following buttons to navigate to the desired content. Provider response details, when available, appear in the transaction’s provider_data object. For refunds and cancellations, synchronous responses currently populate provider_data.response_code with Yuno’s normalized code. Asynchronous updates can populate it with the provider’s own code, so this field is not guaranteed to contain the original provider code for these operations. Use the transaction’s response_code for Yuno’s normalized result. When supplied by the provider, the original response is available in provider_data.raw_response, and the provider’s message is available in provider_data.response_message. Their availability and content depend on the integration. To look up what a specific provider code maps to, use the payment error code decoder. The decoder is a reference mapping maintained against each provider’s published documentation, so use it as a guide rather than as a description of a specific integration’s behavior.

Succeeded status

Won status

Created status

Pending status

Declined status

Rejected status

Error status

Expired status

Lost status

Prevented status

Succeeded status

Won status

Created status

Pending status

Declined status

Some declines include a merchant_advice_code (MAC) that indicates whether and when to retry. See Merchant Advice Codes (MAC).

Merchant Advice Codes (MAC)

These codes will provide useful guidance when dealing with declined transactions. You may find these fields in our public API responses:
  • transactions.merchant_advice_code and transactions.merchant_advice_code_message: Yuno-normalized fields providing standardized codes and explanations regarding the denial.
  • transactions.provider_data.merchant_advice_code and transactions.merchant_advice_code_message: Raw code and message from the provider.
Please refer to Merchant Advice Codes (MAC) for more information.
Merchant Advice Codes provide guidance from issuers/providers about retry behavior and policy. When present on a decline, use the MAC to determine whether to retry and the recommended timing.

Rejected status

Error status

Expired status

Lost status

Prevented status

PREVENTED is only applicable to transactions with type = CHARGEBACK when the provider/network indicates a predispute deflection. In these scenarios, Yuno emits only the chargeback webhook; no refund webhook is sent.

Chargebacks specific response_codes

For more details, please refer to the reason codes page in the Chargeback guides section.