You integrated a PIX API. Everything worked in sandbox. Went to production. Two days later, support tickets start: “payment didn’t land”, “QR Code expired”, “webhook didn’t arrive”. You check the dashboard and discover 12% of transactions failed on timeout, retry didn’t exist, and reconciliation became a spreadsheet. It’s the most common scenario for teams that contract the first PIX API they find instead of evaluating which one is right for operations at scale.
This guide is for developers, tech leads and product managers who need to choose a PIX API that handles 10, 100 or 1000 transactions per minute without breaking. You’ll understand what a real PIX API needs to deliver, how the technical flow works (Cash-In, Cash-Out, Cob, Split), 8 criteria to evaluate vendors, honest comparison of market alternatives, and common errors that kill conversion.
A PIX API is the programmatic interface that lets your system create, receive and manage PIX transactions without human intervention. Your application makes HTTP/REST calls to the provider endpoints, which communicates with the Brazilian Central Bank and PIX participants to settle payment in seconds. The API covers charging (static and dynamic QR Code), receiving (Cash-In), sending (Cash-Out), automatic split and confirmation webhooks.
PIX API isn’t a single thing. There are 4 main types, and what your operation needs depends on the business model:
Imagine a $99 digital product sold at 8:47pm on a Saturday. Technical flow of a well-architected PIX API:
/v2/cob with amount, order ID (txid) and payer data. Expected latency: <300ms.Total time from customer click to product release: 10-30 seconds. That’s the benchmark for a good PIX API. More than that, there’s a bottleneck in the provider infrastructure.
PIX is free for end-users, but not perfect. Companies lose up to 15% of payment attempts for reasons that a professional PIX API solves:
The BSPay PIX API was built for operations scaling from 100 to 100,000 transactions/day without rewrite. Covers Cash-In, Cash-Out, Cob, CobV and native Split — all in the same REST integration. Technical differentiator: the internal orchestrator manages multiple PIX providers behind the unified API, so when one falls, transactions automatically rout without you doing anything. Over 30,000 active businesses process PIX through BSPay today.
Rates starting at 2.99% volume-negotiable, webhook with automatic retry, official SDKs in Node/Python/PHP, complete sandbox, dedicated technical support via exclusive 24h WhatsApp group. Our team helps migrate from any current PIX API without downtime — you keep the operational flow running while swapping the payment layer. See all features on the home page or talk to a specialist.
Basic integration (create charge + receive webhook) takes 1-3 days for a mid-level developer. Complete integration with Cash-Out, Split and automatic reconciliation takes 1-2 weeks. With official SDKs, both timelines drop by half.
In professional APIs, PIX approval rate is between 96% and 99%. Rate below 94% indicates problem in the provider or QR Code TTL. PIX declines are usually blocked account, insufficient balance at the moment or expired QR — not “cancelled card” like in cards.
For end-users, PIX is free. For merchants, API charges fee per transaction (between 0.99% and 4%, depending on provider and volume). Aggregate volume above $60K/month allows negotiation for rates below 2% in the professional market.
Yes. Any serious PIX API offers free sandbox environment with simulated transactions identical to production. If the vendor refuses sandbox or asks for signature before testing, red flag. You should be able to integrate and test the complete flow before any commercial commitment.
PIX API is the technical interface (REST endpoints, webhooks). PIX gateway is the product layer aggregating API + checkout + dashboard + reconciliation + anti-fraud as a package solution. A pure PIX API requires you to build everything in your backend; a gateway delivers more turnkey. At BSPay, you have both: raw REST API for full control, and ready gateway for speed.
Yes. Automatic PIX (launched by Brazilian Central Bank in 2025) allows recurring charge authorized by the customer once, similar to direct debit. Modern PIX APIs already expose this flow — enabling SaaS subscriptions, course recurring fees and recurring plans without depending on cards.
Depends on the provider. Professional APIs allow multi-entity operations with separate credentials per entity, consolidated dashboard and isolated reconciliation. If the vendor requires separate integration per entity, you’ll duplicate engineering and accounting work.
Yes, following standard practices: mandatory HTTPS, OAuth 2.0 or rotatable API key authentication, optional IP whitelisting for critical endpoints (Cash-Out), HMAC signature verification on webhooks. Real risk is not the API itself, but misconfiguration on your side (credentials in public source code, webhook without authentication).