Your ERP becomes the customer's financial hub|

scroll

Automatic bank reconciliation, real-time bank data and Pix billing, inside your management software, with a single API.

Start free trial

Management software already running on Pluggy

Conta AzulNiboMarketUPF360KaminoBomControle

The problem

An ERP that only organizes data has become a commodity

Finance happens outside the ERP

Customers use your software to run the business, but leave it to reconcile at the bank and to collect payments in another app. Every task outside your product is an opening for a competitor.

Bank connections are expensive to maintain

Integrating and maintaining dozens of banks takes months of engineering. And every bank API change becomes maintenance for your team, in the middle of the roadmap.

No real-time view

Without automatic bank statements, customers can't see their consolidated cash position, and the ERP stays a record-keeping tool instead of a decision-making one.

With Pluggy

Data and Pix in a single API. You don't become a bank

Automatic reconciliation

Bank statements imported straight from the bank via Open Finance. Entries reconciled without anyone checking spreadsheets.

Consolidated multi-bank view

Balances and statements from 220 financial institutions in one place, in the same schema, whatever your customer's bank.

Native Pix billing

Pix, Pix Automático and boleto generated from inside the ERP. Automatic write-off when the payment arrives. Same-day settlement, no card fees and no chargebacks.

Cash management

Move balances between accounts of the same holder with rules set via API: sweeping, top-up and scheduled transfers.

New revenue with embedded finance

Monetize connectivity, billing and payments inside your ERP. Bank connectivity stops being a cost and becomes revenue.

Regulated infrastructure

Connections through Open Finance, regulated by the Central Bank of Brazil. The payment initiation (ITP) license is Pluggy's, not yours.

Why Pluggy

Read and move money with the same API

pluggy-quickstart
import { PluggyClient } from 'pluggy-sdk';

const client = new PluggyClient({
  clientId: process.env.PLUGGY_CLIENT_ID,
  clientSecret: process.env.PLUGGY_CLIENT_SECRET,
});

// 1. Connect an item (sandbox)
const item = await client.createItem(
  SANDBOX_CONNECTOR_ID,
  { user: 'user-ok', password: 'password-ok' }
);

// 2. Read accounts and transactions
const { results: accounts } =
  await client.fetchAccounts(item.id);

const { results: txs } =
  await client.fetchTransactions(accounts[0].id);

console.log(txs);

Data and payments, one contract

Reading bank statements, Pix billing and supplier payments come from the same API and the same credentials. One contract, one specialized support team.

Truly multi-bank

Your customer connects any bank in Brazil. You get the data in the same JSON, whatever the institution.

White-label Pluggy Connect

The widget handles the bank connection UX. You don't build the authentication flow, you embed it in hours.

Sandbox with realistic data

Test the whole flow with simulated data before going to production. No bank agreement needed.

Built for your niche

From horizontal to vertical ERPs

Each segment has a different reconciliation pain. The same API solves all of them.

ERPs for construction

Reconcile the finances of each project with real-time bank data, without depending on statements sent by email.

ERPs for agribusiness

The farm's bank statement flows into the system automatically, with no OFX files and no spreadsheets, even across multiple accounts and banks.

Horizontal SMB ERPs

One integration covers every bank your customers use. It replaces the OFX process for good and becomes a selling point.

Get started

Your ERP already has the customer. Now become the center of their money

Data and Pix in a single contract. We'll show you how to bring automatic reconciliation and billing into your product, and how that turns into revenue.

Start free trial

FAQ

Frequently asked questions

Still have questions?

Yes. Reading bank statements, Pix billing and supplier payments come from the same API and the same credentials. One contract, one specialized support team.
The ERP fetches transactions through GET /v2/transactions on the Pluggy API. Each transaction already comes with type, amount and payment method, and the ERP matches it against its internal entries and reconciles with no human intervention.
Yes. The ERP calls POST /payments/create-payment-request, receives a QR Code and tracks the payment through a webhook. When the Pix is confirmed, the ERP can write off the invoice automatically.
Traditional bank integration is point to point: each bank needs a separate integration, and it becomes maintenance for your team whenever the bank's API changes. With Pluggy it's a single API for 220 financial institutions, with standardized and enriched data, and it also includes Pix billing and payments.
No. Pluggy is authorized by the Central Bank of Brazil as a Payment Initiation Service Provider (ITP). You initiate payments without becoming a payment institution.
Yes, as long as the ERP can call a REST API. We have customers in management, construction, agribusiness, retail, franchise and services ERPs.
Data has a monthly minimum of R$ 2,500 and Payments of R$ 500, each with volume included; above that, overage is billed per request. You only contract what you need, and you can turn connectivity into revenue by charging your end users.
First request in 5 minutes in the sandbox. Most ERPs reach production in 2 to 4 weeks, with Pluggy Connect handling authorization and the SDKs (Node, Python, .NET and Java) speeding up the integration.