Actions5
- Pagamento Actions
Overview
This node integrates with the Mercado Pago payment platform to perform various payment-related operations. Specifically, for the Pagamento - Obter (Payment - Get) operation, it retrieves detailed information about a specific payment using its unique payment ID.
Common scenarios where this node is beneficial include:
- Fetching the status and details of a payment after it has been created or processed.
- Verifying payment information before fulfilling an order or service.
- Auditing or reporting on individual payment transactions.
Practical example:
- After a customer completes a payment on your e-commerce site, you can use this node to obtain the payment details by providing the payment ID. This allows you to confirm whether the payment was approved, pending, or rejected before proceeding with order fulfillment.
Properties
| Name | Meaning |
|---|---|
| ID do Pagamento | The unique identifier of the payment to retrieve. This must be a numeric string representing the payment ID in Mercado Pago. |
Output
The node outputs a JSON object containing the full details of the requested payment as returned by the Mercado Pago API. This includes fields such as payment status, amount, payer information, timestamps, and other metadata related to the payment.
If the payment includes PIX (a Brazilian instant payment method) data, additional fields like pix_qr_code, qr_code_base64, and pix_ticket may be present, providing QR code information for the payment.
The node does not output binary data.
Dependencies
- Requires an API key credential for Mercado Pago with a valid access token.
- The access token must be correctly configured in the node's credentials and should correspond to the appropriate environment (sandbox or production).
- The node makes HTTP requests to the Mercado Pago API endpoint:
https://api.mercadopago.com/v1/payments/{paymentId}.
Troubleshooting
- Missing or invalid payment ID: The node requires a non-empty numeric payment ID. If the ID is missing or contains non-numeric characters, the node will throw an error indicating that the payment ID is mandatory and must be numeric.
- Invalid or expired access token: If the API token is missing, too short, or invalid for the environment, the node will raise configuration errors. Ensure the token is correct and matches the sandbox or production environment.
- Network or API errors: Errors from the Mercado Pago API, such as invalid URLs or unauthorized access, will be reported with descriptive messages. Verify network connectivity and API credentials.
- Unexpected response format: If the API returns a string instead of JSON, the node attempts to parse it. Parsing failures may cause errors.
- Rate limits or API restrictions: If the API enforces rate limits or restrictions, handle these according to Mercado Pago's guidelines.