TL;DR Short answer: Pagar.me, often written Pagarme, is Stone's payments platform for Brazil, and Pagar.me ETL tools move its orders, charges, customers, recipients, balance operations and receivables into a warehouse for payment and marketplace reporting. Kondado offers a ready-made Pagar.me connector, Airbyte's Connector Builder and dlt build on the Core API v5, and webhooks cover real-time payment events. Build on API v5, because Pagar.me has deprecated v4 and earlier. Seven Pagar.me ETL tools compared:
Airbyte Kondado Custom code with the Pagar.me API v5 Pagar.me webhooks Pagar.me dashboard reports dlt n8n The Pagar.me constraint: Pagar.me states that API v4 and earlier are no longer updated and will stop working, so any pipeline built on the legacy API must move to the Core API v5, which has a different data model centred on orders and charges. Pagar.me ETL tools extract payment data from Pagar.me, one of Brazil's leading online payment gateways, and load it into a warehouse. There, finance, operations and marketplace teams reconcile payments across cards, Pix and boleto, track split payments and receivables, and join payment data with orders and customer data. For a global payments comparison, see our guide to Stripe ETL tools .
What is Pagar.me (Pagarme), and what data does it hold? Pagar.me is the API-first online payments platform of Stone Co., one of Brazil's largest financial technology companies, and it absorbed Stone's Mundipagg gateway. Its data reflects how payments work in Brazil:
Payment methods: credit and debit cards, Pix, boleto bancário and vouchers, each with its own statuses and settlement timing.Orders and charges: an order is the top-level object, and each order holds one or more charges, one per payment attempt or method.Instalments: card payments are often split into parcelas, which settle over several months as receivables.Marketplace objects: recipients, split rules, transfers and balance operations for platforms that pay out to sellers.Subscriptions: plans, subscriptions and invoices for recurring billing.Because instalments settle over time, sales, receivables and actual cash usually need separate models.
Every Pagar.me ETL tool reads the same Core API v5 objects:
Orders and charges: order items, totals and status, and each charge's method, amount, status and gateway response.Customers: customers with their cards and addresses.Subscriptions: plans, subscriptions, invoices and their cycles.Recipients and transfers: marketplace recipients, bank accounts and transfers out of their balances.Balance operations: the ledger of credits, debits, fees, refunds and chargebacks on each balance.Receivables and settlements: future instalment payments, anticipations and actual settlements.How do the Pagar.me ETL tools compare? Tool Approach Data covered Best for Cost Airbyte Connector Builder on API v5 Any API object you configure Pagar.me next to commerce and CRM data in a warehouse Free self-hosted Core; paid Cloud plans Kondado Managed Pagar.me connector Orders, charges, customers, recipients, balance operations, receivables Brazilian teams wanting a ready-made connector Subscription plans Pagar.me API v5 Custom code Every Core API object Exact control Free, engineering time Webhooks Real-time push Order, charge, refund, subscription and chargeback events Event-driven pipelines Included with Pagar.me Dashboard reports Built-in reports and exports Transactions, balances and receivables Quick finance checks Included with Pagar.me dlt Python REST API source Any API endpoint Python teams loading a warehouse Free, open source n8n Workflow automation API data and webhook events Self-hosted automation Free self-hosted; paid cloud
Which Pagar.me ETL tools should you consider? Seven Pagar.me ETL tools, from managed connectors to Pagar.me's own features:
1. Airbyte Airbyte is the open-source data connectivity platform for AI and analytics. It does not have a maintained pre-built Pagar.me connector, so among Pagar.me ETL tools Airbyte works through the no-code Connector Builder: you configure Core API v5 endpoints such as orders, charges and balance operations with Basic authentication and pagination, and the Builder's AI assistant can pre-fill much of the setup from Pagar.me's API reference. For other ELT options, see our guide to ELT tools .
That puts Pagar.me payments next to Shopify, WooCommerce, CRM and marketing data from 700+ connectors, which is where reconciliation and revenue analysis happen. Airbyte runs in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Key features Connector Builder: configure authentication, endpoints and pagination visually.AI assistant: pre-fills configuration from API documentation.Incremental syncs: use date filters where endpoints support them.Any destination: BigQuery, Snowflake, Postgres, Databricks and more.Best for: teams that want Pagar.me data next to commerce and CRM data in their own warehouse.
Pricing: self-hosted Airbyte Core is free; Airbyte Cloud is billed on volume, and Pro and Airbyte Flex on capacity.
Pros Cons Custom Pagar.me source with no code No maintained pre-built Pagar.me connector Payments next to commerce and CRM data Custom source needs testing and upkeep Cloud, Flex or self-hosted Core Endpoints must be configured individually
2. Kondado Kondado is a Brazilian data platform with a ready-made Pagar.me connector made up of pipelines for customers, cards, addresses, charges, balance operations, orders, recipients and receivables. It loads into databases, warehouses and spreadsheets on schedules from every few minutes to daily, and suits Brazilian teams that want a managed option. For ecommerce data to join with, see our guide to Shopify ETL tools .
Key features Pagar.me pipelines: customers, cards, addresses, charges, orders, recipients, balance operations and receivables.Schedules: from every few minutes to daily.Destinations: databases, warehouses and spreadsheets.Local focus: built for Brazilian data sources and teams.Best for: Brazilian teams that want a managed Pagar.me connector.
Pricing: subscription plans with a free trial; check current pricing.
Pros Cons Ready-made Pagar.me pipelines Another platform to manage Covers marketplace and receivables data Subscription pricing Built for Brazilian sources Fewer destinations than general ELT platforms
3. Custom code with the Pagar.me API v5 Underneath every Pagar.me ETL tool, the Core API v5 covers orders, charges, customers, subscriptions, recipients, transfers, balance operations, receivables, settlements and chargebacks. It uses HTTP Basic authentication with your secret key, the same base URL serves test and live data depending on the key, and Pagar.me publishes SDKs for several languages and per-route rate limits.
Key features Orders and charges: full payment detail, including gateway responses.Marketplace endpoints: recipients, splits, transfers and balance operations.Receivables: future instalments, anticipations and settlements.SDKs: official libraries for several languages.Best for: engineering teams with specific reconciliation needs.
Pricing: free with your Pagar.me account; you pay for engineering and infrastructure.
Pros Cons Every Core API object You own scheduling, state and retries Official SDKs Per-route rate limits One base URL for test and live keys Ongoing maintenance
4. Pagar.me webhooks Pagar.me webhooks notify an endpoint you control when orders and charges change status, such as when a Pix payment is confirmed, a boleto is paid, a card charge is refunded or a chargeback opens. They are the real-time option among Pagar.me ETL tools and keep order and payment status current between batch syncs.
Key features Order and charge events: paid, failed, refunded and cancelled statuses.Subscription events: new, renewed and cancelled subscriptions.Chargebacks: notifications when disputes open.Retries: failed deliveries are retried.Best for: teams that need payment status in other systems in real time.
Pricing: included with your Pagar.me account.
Pros Cons Real time Requires your own endpoint Covers Pix, boleto and card status changes No historical backfill Included with Pagar.me Events need storing and deduplicating
5. Pagar.me dashboard reports Before reaching for Pagar.me ETL tools, note that Pagar.me's dashboard includes reports for transactions, balances, receivables and transfers, with exports for further analysis. They suit quick finance checks and reconciliation without a pipeline. For subscription billing platforms, see our guide to Chargify (Maxio) ETL tools .
Key features Transaction reports: payments by method, status and period.Balance and receivables: current and future balances.Transfers: payouts to bank accounts.Exports: download report data.Best for: finance teams that need quick payment reports.
Pricing: included with your Pagar.me account, with no separate reporting fee.
Pros Cons No setup Manual rather than scheduled Receivables and balance views Hard to join with other data Exports for reconciliation Limited flexibility
6. dlt dlt is one of the code-first Pagar.me ETL tools: an open-source Python library whose REST API source can page through Core API v5 endpoints with Basic authentication and load the results into DuckDB, BigQuery, Snowflake or Postgres, merging on IDs so status changes update existing rows. For more code-first options, see our guide to Python ETL tools .
Key features Declarative REST source: endpoints, authentication and paging are configuration.Incremental: load only records changed since the last run where filters allow.Nested data: child tables for order items and charges.Many destinations: DuckDB locally, warehouses in production.Best for: Python teams that want Pagar.me pipelines in code.
Pricing: free and open source under the Apache 2.0 licence; you pay for where it runs.
Pros Cons Merge on ID for status changes You write and schedule the pipeline Incremental loading on date filters Requires Python skills Free and open source Rate limits are yours to handle
7. n8n n8n is one of the self-hostable Pagar.me ETL tools: it can call the Core API v5 with its HTTP Request node on a schedule or receive Pagar.me webhooks with its Webhook node, then route the data to databases, sheets or chat, such as alerting on failed payments. For more workflow options, see our guide to open-source workflow automation tools .
Key features HTTP Request node: call Pagar.me endpoints on a schedule.Webhook node: receive Pagar.me events.Code nodes: reshape data with JavaScript or Python.Hundreds of destinations: databases, sheets, chat and more.Best for: teams that want self-hosted Pagar.me automations and alerts.
Pricing: the self-hosted Community edition is free under n8n's Sustainable Use License, which is fair-code rather than OSI open source; n8n Cloud is paid.
Pros Cons Self-hosting option No dedicated Pagar.me node Handles API calls and webhooks Not built for large historical loads Code nodes for transformation You run and maintain it if self-hosted
How do split payments work in Pagar.me, and how do you analyse them? Split payments, or split de pagamento, let a marketplace divide each payment between itself and its sellers automatically. In Pagar.me this involves:
Recipients: each seller is a recipient with its own balance and bank account.Split rules: each charge carries rules for how the amount is divided, by percentage or fixed amount, and who pays fees.Balance operations: every split creates ledger entries on each recipient's balance.Receivables: instalment payments create future receivables per recipient, which can be anticipated.Analysis: join charges, split rules and balance operations to report commission revenue, seller payouts and fees per recipient.Model split rules as their own table, because one charge can produce several recipient entries.
Pagar.me API v4 vs v5: what changes for data pipelines? Pagar.me has marked API v4 and earlier as no longer updated and soon to stop working, so pipelines need to move to the Core API v5:
Data model: v4 centred on transactions, while v5 centres on orders that contain one or more charges.Authentication: v5 uses HTTP Basic authentication with a secret key instead of an api_key parameter.Identifiers: object IDs and statuses differ, so historical v4 data needs mapping to v5 tables.Marketplace objects: recipients, balance operations and receivables have v5 equivalents with new fields.Migration tip: run v4 and v5 extraction in parallel briefly, reconcile totals, then switch reporting to v5 tables.What should you check before syncing Pagar.me data? Whichever Pagar.me ETL tools you choose, check these first:
API version: build on the Core API v5, since earlier versions are being retired.Test and live keys: the same URL serves both, so make sure pipelines use the live secret key and keep test data out of reports.Status changes: Pix, boleto and card charges change status after creation, so re-read recent records or use webhooks.Instalments: separate sales, receivables and settled cash in your models.Amounts: amounts are returned in centavos, so divide by 100 for reais.Personal data: customer records include CPF or CNPJ numbers and addresses, so limit fields and follow LGPD requirements.How do you start pulling Pagar.me data with Airbyte? If you decide to test Airbyte, setting up a Pagar.me pipeline takes three steps.
Step 1: Get your secret key In the Pagar.me dashboard, open the API keys settings and copy the live secret key for the account you want to extract.
Step 2: Build a Pagar.me source in the Connector Builder In Airbyte, open the Connector Builder and create a source for Core API v5 endpoints such as orders, charges and balance operations, with Basic authentication and pagination. Test it, then publish it to your workspace.
Step 3: Set up a destination and connection Pick a destination, such as BigQuery, Snowflake or Postgres, and schedule syncs. The process is the same whether you start with Airbyte Cloud or run self-hosted Airbyte Core .
Which Pagar.me ETL tool should you choose? Choosing between Pagar.me ETL tools depends on how much you want to build. For a ready-made connector, Kondado is the most direct option. For Pagar.me next to commerce and CRM data in your own warehouse, build on the Core API v5 with Airbyte's Connector Builder or dlt. Use webhooks for real-time payment status, the dashboard for quick finance checks, and n8n for automations. For ecommerce platforms that often sit alongside Pagar.me, see our guide to WooCommerce ETL tools .
Move Pagar.me data with Airbyte Build a Pagar.me source on the Core API v5 with the Connector Builder and sync it next to Shopify, WooCommerce and 700+ other sources, in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. What are the best Pagar.me ETL tools? Kondado has a ready-made Pagar.me connector, and Airbyte's Connector Builder and dlt build on the Core API v5. Webhooks cover real-time payment events, the dashboard covers quick reports, and n8n handles automations.
2. Does Airbyte have a Pagar.me connector? Airbyte does not have a maintained pre-built Pagar.me connector. You can build a Pagar.me source on the Core API v5 with Airbyte's no-code Connector Builder.
3. Is the Pagar.me API v4 still supported? Pagar.me states that API v4 is no longer updated and will stop working, and asks integrations to move to the Core API v5.
4. Who owns Pagar.me? Pagar.me is part of Stone Co., one of Brazil's largest financial technology companies.
5. How do I analyse split payments in Pagar.me? Load charges, split rules, recipients and balance operations into a warehouse, then calculate commission revenue, seller payouts and fees per recipient.
Suggested reads Stripe ETL Tools
PayPal ETL Tools
Braintree ETL Tools
WooCommerce ETL Tools
