End-to-end Pix, inside your API.
Receive, pay, charge and manage keys on the same rail as the digital account. Settlement in seconds, real-time webhooks and automatic reconciliation — no middlemen in your experience.
The short path between the payer and your account.
Fewer hops between SPI and your product means lower latency, fewer failure points and simpler reconciliation.
Rail built into the account
- Pix native to the digital account — no orchestrating two vendors
- One webhook per event: received, sent, refunded
- Automatic reconciliation in the account's own statement
- DICT keys managed by the same API as the balance
Pix PSP separate from the account
- Two contracts, two SLAs and two integrations to maintain
- Reconciling PSP payouts against balances becomes a daily chore
- Duplicated or lost events between platforms
- Pix keys locked into the vendor — painful migration
Aurix runs Pix as part of Banking Core: the same account that holds the balance receives, sends and reconciles.
Everything Pix does, your API does.
Each capability exposed through its own endpoints, with signed webhook events.
Pix In
Real-time confirmation on receipt and instant credit to the account balance.
Pix Out
Send by key, bank details or QR Code — with approval chains and role-based limits.
Dynamic & static QR Codes
Charges with amount, due date, interest and fines — generated and settled via API.
DICT keys
Key registration, portability and claims managed programmatically.
Refunds & MED
Full or partial refunds via API, plus handling for Brazil's Special Refund Mechanism.
Real-time webhooks
A signed event for every movement — idempotent, with retries and guaranteed ordering.
From curl to Pix in production.
Predictable REST endpoints, native idempotency and a sandbox with simulated settlement — the sandbox contract is the production contract.
curl -X POST https://api.aurixfinance.ws/v1/pix/payments \
-H "Authorization: Bearer sk_live_..." \
-H "Idempotency-Key: 7f3a-…" \
-d '{
"amount": 24000,
"key": "finance@company.com",
"description": "Order #4092"
}'Four steps to your first Pix.
The integration path is the same as Banking as a Service — Pix is a module of the account, not a new project.
Sandbox on first access
Create test accounts, simulate Pix In and Out and receive webhooks — no contract, no cost.
Model limits and approvals
Set limits per account, time window and channel, plus your operation's approval chain.
Certify the flows
Guided script covering receiving, sending, refunds and contingency, with a production checklist.
Production with support
Assisted go-live, 24/7 monitoring and a direct channel to engineering.
Pix is money in motion. We treat it that way.
An operation designed for the money path: idempotency, auditability and continuous monitoring.
Native idempotency
Every write accepts an Idempotency-Key — retries are safe by default, no duplicated Pix.
Audit trail
Every transaction with an immutable state history, ready for BACEN and internal audits.
Layered anti-fraud
Per-transaction, category and time-window analysis, configurable limits and preventive blocking via API.
24/7 monitoring
End-to-end observability with proactive alerting — we usually call before your dashboard does.
Ready to switch on Pix in your product?
Sandbox available today. First production Pix in weeks.
Frequently asked questions
What technical teams ask before integrating Pix through Aurix.
Talk to the team