Skip to the operations

Banking

Mercado Pago in a decision flow.

5 Mercado Pago operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Banking
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

The payments arm of Mercado Libre, across Latin America.

Mercado Pago processes card, Pix, cash and wallet payments in Brazil, Argentina, Mexico, Chile and Colombia, and lends against the sales history it sees. It began as the payment rail inside Mercado Libre's marketplace and now serves merchants who have nothing to do with it. Its reach across several countries is what distinguishes it from the Brazil-only providers.

What a flow can call

5 operations, each one a step you can place on the canvas.

  1. GET/v1/payments/search?external_reference=$data.applicant_id

    Find a payer's payments

    Searches payments by your own reference, which is why every charge should carry external_reference set to an id you control.

  2. GET/v1/payments/$data.mercadopago_payment_id

    Check a payment's status

    The state of one payment, with the detail behind it.

  3. POST/v1/payments

    Raise a Pix charge

    Creates a Pix charge the payer settles from their bank app.

  4. POST/v1/payments/$data.mercadopago_payment_id/refunds

    Refund a payment

    Refunds all or part of a payment. amount is optional — omit it for a full refund.

  5. GET/v1/identification_types

    Verify the credential

    Lists the document types the account's country accepts.

Where it sits in the decision

Banking calls have a natural place in a flow.

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Whatever Mercado Pago returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Mercado Pago as a connection authenticating with an API key.
  • 02Mercado Pago has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Find a payer's payments” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Mercado Pago in a flow.

How do I connect Mercado Pago to a decision flow?

Add Mercado Pago as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Mercado Pago in a decision without ever seeing the secret.

Can I test Mercado Pago without touching production?

Mercado Pago exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Mercado Pago?

5 operations, including “Find a payer's payments”, “Check a payment's status”, “Raise a Pix charge”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Find a payer's payments”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Mercado Pago be called?

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Also in Banking

Ready when you are

Wire Mercado Pago into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs