< / > Meet PlugPix

Pix payments in your ERP, with a single integration.

With PlugBank PIX, you make a single JSON integration and open the doors of your ERP to the country's largest banks. We take care of homologation, stability, and business rules.

Your system gains a complete API, ready for billing, POS, settlements, and much more! With Dynamic and Static QR Code issuance, and instant reconciliation via Webhook.
PlugBoleto
A TECNOSPEED SOLUTION • A TECNOSPEED SOLUTION •
API PIX
The leading integration hub for Software Houses in Brazil
+4.100
integrated software companies
+40
supported banks
20
years in the market
+224
specialists
Contact

Make Pix payments available in your ERP. 

Fill out the form, and our team will contact you within 24 business hours to present the available modalities and the integration process.
+Dynamic QR Code +Hybrid Boleto +Real-time webhooks +Automatic registration in NF-e +Dev-to-dev support +Full sandbox for testing
Privacy Policies*
< > The problem

Making a Pix integration is simple. Maintaining dozens of them, not so much.

Pix is a unique standard from the Central Bank, but each bank implements, documents, and updates its own API in its own way. This requires not only code but also infrastructure, monitoring, and constant maintenance to keep up with every change, bank by bank.
01

Bank-to-bank homologation

Each bank has its own accreditation, certification, and testing process. Each approval can take months and requires ongoing maintenance.

02

APIs and different documentation

Itaú, Bradesco, BB, each has distinct endpoints, formats, and rules. Your team needs to learn and maintain each one separately.

03

Banks change rules without notice

A bank update could break the integration overnight. Your roadmap entails chasing a bank change.

04

No coverage for all customers

If the customer doesn't have an account at one of the approved banks, they can't use Pix. The solution doesn't scale to the entire portfolio.

05

Static key = no traceability

Using a static key for charges is insecure and not scalable. Without a txid, there's no automatic reconciliation, no identifying who paid for what.

How does it work

One integration. All banks. Zero maintenance after implementation.

The TecnoSpeed PlugPix API doesn't solve a complexity of Pix; Pix is already simple. It solves multiplication: instead of one integration per bank, it's a single integration for all. You implement once, in the standard your team already knows, and TecnoSpeed handles homologation, rule updates, and continuous maintenance. It's implemented and working, you don't need to touch anything else!
End-to-end flow 4 stages · cycle in seconds
  1. 01

    ERP Request

    ERP makes a JSON request to the PlugPix API with payer data, amount, and charge type.

  2. 02

    Payment authorized

    The payer scans the QR code in the bank app and authorizes the payment instantly.

  3. 03

    Real-time confirmation

    The API receives confirmation from the bank and triggers the Webhook to the ERP in real-time.

  4. 04

    Automatic reconciliation

    ERP records receipt, updates e-invoice, and closes reconciliation, without manual action.

All orchestrated by the API. Your team writes a single integration; homologation, maintenance, and regulatory updates are on us.

{ } JSON Example: Pix Payment Slip with Due Date
POST /v1/cob
{
  "account ID": "customer-account-123",
  "description": "March 2026 Tuition",
  "calendar": {
    "dueDate": "2026-03-31",
    "daysAfterDueDate": 5
  },
  "payer": {
    "CPF/CNPJ": "12.345.678/0001-90",
    "name": "ABC Company"
  },
  "value": {
    "original": 1500.00,
    "fine": {},
    "interest": {},
    "discount": {}
  }
}
Return

Dynamic QR Code + Copy and Paste Code ready to present to the payer. Webhook confirming receipt once payment is processed.

Modalities

All Pix modalities in a single API, from the simplest QR Code to the Hybrid Boleto

The PlugPix API supports the main Pix payment methods used in the business market. Each method has its use case, and the API delivers all of them with the same integration, the same JSON, and the same confirmation Webhook.
txid
Mode 1 · Immediate

Dynamic QR Code

For unmaturing charges, POS, standalone sales, and one-time charges. Each transaction generates a unique and trackable QR Code with txid.

  • +A QR code per transaction, no reuse
  • +Identify the payer who read the code
  • +Automatic reconciliation via txid
  • +Recommended by the BC for businesses
Cove
Expiration25/12
ValorR$ 1,299.00
Fine2%
Interest1%/month
PayerCNPJ
Plan 2 · Expiration

Pix Collection (Cobv)

For monthly fees, invoices, and accounts receivable with due dates. Supports fines, interest, and discounts, all in JSON.

  • +Configurable due date, penalty, interest, and discount
  • +Grace period after expiration
  • +Payer information (CPF/CNPJ, address)
  • +Ideal for management and billing ERPs
< > Resources

Everything a developer needs to deliver real Pix in their ERP

Banks

One integration, all banks

Itaú, Bradesco, Banco do Brasil, Santander, Sicredi, Sicoob, and GerenciaNet, without bank-by-bank approval. Single layout, no institution-specific rules.

Security

Security and Anti-fraud

Each charge is tracked by a unique txid. Dynamic QR Code ensures that each transaction is identified, with no code reuse, no duplicate payments, and no key change fraud.

Real-time

Real-time webhooks

As soon as payment is confirmed, the ERP receives the notification automatically, without polling or user intervention to check the bank. Payment status is always updated.

Maintenance

Zero maintenance, database changes, API absorbs

Every time a bank updates its Pix API, TecnoSpeed absorbs the change. Your development team doesn't stop the roadmap to resolve a bank issue.

Standard

Standardized JSON and complete documentation

Same request pattern for all modalities and all banks. Sandbox available for testing. docs.pix.tecnospeed.com.br with complete code examples.

Bank coverage

Brazil's main banks

The PlugPix API is approved by the main banks in the market. No friction, no barriers.
Comparative

Integrating Pix Alone or with the PlugPix API: What Changes for Your Team

Hard path

Without the PlugPix API

Integrate Pix the old way: each bank, each API, each homologation done manually and maintained forever.

  • Months of bank-by-bank approval
  • Different APIs, documentation, and rules for each bank
  • Bank updates break your integration
  • Manual confirmation via internet banking
  • Manual recording on e-invoices
  • Static key with no traceability
Not recommended
Recommended
Complete platform

With the PlugPix API

A single architecture connects the ERP to banks, with real-time Webhooks, unified JSON, and maintenance/approval handled by TecnoSpeed.

  • One integration covers all banks in weeks
  • Standardized JSON for all modalities
  • TecnoSpeed absorbs banking updates
  • Webhook notifies the ERP in real-time
  • Automated recording in fiscal documents
  • Dynamic QR Code with txid and reconciliation
Integrate the API now
Documentation

From zero to Pix in production, access our complete documentation 

Each Suite API has explanatory documentation per payment method. First steps, integration guides, JSON examples, webhooks, and authentication. Everything available at docs.pix.tecnospeed.com.br
>_ The market

Is your ERP still not offering this convenience to customers?

With over 180 million registered Pix keys and transactions exceeding R$1 trillion per month, Pix is not a trend, it is infrastructure. Any ERP that does not offer Pix billing is delivering less than what the customer expects.
180M+
registered Pix keys in Brazil
R$1T+
in monthly Pix transactions (BC)
4.100+
integrated Software Houses
20
years of API expertise

“An ERP integrated with a Pix API enables fully connected financial and fiscal management, making all the difference in positioning your Software House more competitively.”

TECNOSPEED BLOG · PIX API FOR COMPANIES

Most common questions

Frequently asked questions about the PlugPix API

PlugPix API is a solution built for Software Houses and IT teams that need to integrate Pix billing into ERPs and management systems. With a single integration and a standardized JSON layout, your ERP can issue Dynamic QR Codes, Pix Billing with due dates (interest, fines, and discounts), Hybrid Bank Slips, and Pix, without individual bank approvals or managing separate integrations.

Currently, PlugPix API is integrated and approved for Itaú, Bradesco, Banco do Brasil, Santander, Sicredi, Sicoob, and GerenciaNet (Efí).

No. That is the main advantage of PlugPix API: your Software House integrates once and gains access to all supported banks. TecnoSpeed handles and maintains all bank approval processes and standardized Pix generation. When a bank updates its implementation, TecnoSpeed absorbs the change with zero impact on your ERP code. sem impacto no código do seu ERP.

A Dynamic QR Code is generated for each transaction, contains full billing details (amount, payer, txid), and allows automated reconciliation in the ERP. Static Pix keys were designed for personal transfers—they don't identify the payer, lack transaction tracking, and don't allow automated reconciliation. For business billing, Dynamic QR Code is the correct standard recommended by the Central Bank.

A Hybrid Payment Slip combines a traditional barcode with a Dynamic Pix QR Code on a single document. Payers choose how to pay. If they choose Pix, settlement is instant and the slip is automatically cancelled/cleared at the bank with no D+1 clearing wait. The API generates the Hybrid Slip in a single request. Regulated by the Central Bank, it is currently available for Banco do Brasil via PlugPix.

Once you set up a Webhook receiver server, the PlugPix API notifies your ERP instantly whenever there is a status update (PAYMENT_CONFIRMED, PAYMENT_PROCESSING, PAYMENT_FAILED). This eliminates periodic polling and ensures the ERP reflects real-time payment status without users checking bank apps.

Yes. One feature of the PlugPix API is automatically logging Pix receipts into fiscal documents/e-invoices as required by current regulation. This eliminates manual entries and keeps your ERP compliant effortlessly.

Yes. All payments processed by the Payments API undergo real-time security validation (assignor data verified, barcodes validated, limits checked). PlugBank operates with SSL, PCI DSS, LGPD compliance, and Brazilian banking regulations. Open Finance APIs use OAuth 2.0, FAPI, and mTLS—the strictest financial security standards regulated by the Central Bank.

Start now

Pix is mandatory. The question is how long your ERP will stay without it.

With over 180 million registered keys and R$1 trillion in monthly transactions, Pix is the preferred payment method for Brazilians. ERP end-users already expect, and demand, that systems offer Pix billing via QR Code without logging into bank apps.

The PlugPix API is ready.
Awards and Certifications — TecnoSpeed
Great Place to Work Certification SESI SDG Seal Innovative Company Award Seal Selo Center Color White Reclame Aqui Seal
TecnoSpeed Footer