Mercado Pago

Mercado Pago

This connector reads a Mercado Pago seller account through the official REST API (https://api.mercadopago.com): payments and their fees and release dates, merchant orders, subscriptions, payment methods and the two account reports, released money (Dinero liberado / Dinheiro liberado) and account money (Dinero en cuenta, formerly "all transactions"). Nothing in it moves money: there are no refunds, payouts or charges.

Setup (about 3 minutes)

1. Sign in at https://www.mercadopago.com/developers/panel/app (the Mercado Pago account whose data you want), open Your integrations and create an application if you have none (any name; product "Checkout Pro" or "Payments" is fine).
2. In the application open Production credentials and activate them (accept the terms). Copy the Access Token (APP_USR-...) into MERCADO_PAGO_ACCESS_TOKEN. The Public Key, Client ID and Client Secret are not needed.
3. Install and run mercado_pago_get_account to check the token. It shows the country site: MLA Argentina, MLB Brazil, MLM Mexico, MLC Chile, MCO Colombia, MPE Peru, MLU Uruguay.

The access token reaches the whole account: keep it secret and reset it in the same panel if it leaks. Test credentials only see test data, and reports of test accounts are empty.

Payments

• mercado_pago_search_payments covers the last 12 months: filter by status, a date range (range picks which date, begin_date / end_date take NOW-30DAYS style or ISO 8601 with milliseconds and offset, e.g. 2026-10-01T00:00:00.000-03:00) and external_reference; 1 to 100 per page, paging.total counts the matches. Each row carries the gross transaction_amount, net_received_amount after fees, fee_details, money_release_date and the payer.
• mercado_pago_get_payment returns the full payment, including refunds and additional_info (items, shipping).
• mercado_pago_search_merchant_orders (last 90 days) and mercado_pago_get_merchant_order group the payments of one Checkout Pro or QR sale.
• mercado_pago_search_subscriptions lists subscriptions (preapprovals); mercado_pago_list_payment_methods the methods of the account's country.

Reports: for bookkeeping and reconciliation use the reports rather than paging through payments.

1. mercado_pago_list_release_reports / mercado_pago_list_settlement_reports show what already exists, including the scheduled reports set up in the Mercado Pago panel.
2. mercado_pago_create_release_report / mercado_pago_create_settlement_report generate one for a period (begin_date, end_date in UTC, e.g. 2026-10-01T03:00:00Z for midnight in Buenos Aires). Generation is asynchronous and takes a minute or more; Mercado Pago refuses an end date beyond its cut-off and says which date is allowed.
3. List again until the report's status is processed, then mercado_pago_download_release_report / mercado_pago_download_settlement_report with its file_name. CSV files come back as semicolon-separated text with a header row (columns as configured in the panel, e.g. DATE, SOURCE_ID, DESCRIPTION, NET_CREDIT_AMOUNT, NET_DEBIT_AMOUNT, GROSS_AMOUNT, MP_FEE_AMOUNT); XLSX files come back as a file. Text over 200 KB is cut: use shorter periods.

Amounts and dates: amounts are in the account currency (currency_id: ARS, BRL, MXN, CLP, COP, PEN, UYU), as decimals. Payment dates carry the account's time zone offset; report dates are UTC.

Errors: 401 means a wrong, reset or test token. 403 means the token's application lacks access to that resource. 404 on a payment means it belongs to another account. 429 (local_rate_limited, too_many_requests) means too many calls in a short time: wait a minute.