Mercado Pago

Integração com APIs do Mercado Pago

Actions6

Overview

This node integrates with the Mercado Pago API to manage payment-related operations. Specifically, for the Payment > Refund operation, it allows users to refund a previously made payment by providing the payment's unique ID.

Common scenarios where this node is beneficial include:

  • Automating refunds in e-commerce workflows when customers request returns.
  • Managing payment reversals in subscription or service platforms.
  • Integrating refund processes into broader business automation pipelines.

For example, after detecting a refund request in a CRM system, this node can be used to trigger the refund process automatically by passing the payment ID to the Mercado Pago API.

Properties

Name Meaning
Payment ID The unique identifier of the payment to refund. This is required to specify which payment should be refunded.

Output

The node outputs a JSON object representing the response from the Mercado Pago API refund endpoint. This typically includes details about the refund transaction such as status, amount refunded, timestamps, and any related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Mercado Pago API credential configured in n8n for authentication.
  • Internet access to call the Mercado Pago REST API at https://api.mercadopago.com.
  • Proper permissions on the Mercado Pago account to perform refund operations.

Troubleshooting

  • Missing Payment ID: If the "Payment ID" property is empty or invalid, the node will throw an error indicating that the payment ID is mandatory. Ensure you provide a valid payment ID string.
  • API Authentication Errors: If the API key or credentials are incorrect or expired, the node will fail to authenticate. Verify your Mercado Pago API credentials in n8n.
  • Refund Not Allowed: Some payments may not be refundable due to their status or time elapsed. The API response will indicate such issues; check the payment status before attempting a refund.
  • Network Issues: Connectivity problems can cause request failures. Confirm network access and retry if necessary.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one refund fails, returning error messages in the output.

Links and References

Discussion