Introduction
PagusPay is a payouts API for sending USDC → Pix — you fund a stablecoin balance in USDC, and PagusPay converts and settles to Brazilian bank accounts via Pix, using standard Pix keys (CPF, CNPJ, email, phone, or EVP) to identify recipients.
Maker-only by design
The API is intentionally maker-only. Everything you can do programmatically stops at submission:
- Create recipients
- Create payout batches (draft)
- Submit a batch for approval
Approval and execution are always human. Every payout batch that moves money requires a maker/checker step with two-factor confirmation (2FA by email), performed by a person in the PagusPay dashboard. There is no API endpoint to approve, reject, or execute a batch — this is a deliberate security boundary, not a missing feature.
API (you) Dashboard (human)
────────── ──────────────────
POST /v1/recipients ──►
POST /v1/payout-batches ──► draft
POST .../{id}/submit ──► pending_approval
│
▼
approve + 2FA (maker/checker)
│
▼
executing → completed
What you can build
- Automated payroll or vendor payout runs that stop at
pending_approval, ready for a human to approve - Recipient management synced from your own system of record
- Read-only dashboards over balances, recipients, and batch status
Next steps
- Authentication — how to create and use API tokens
- Payouts Walkthrough — the full recipient → batch → submit flow with real requests
- API Reference — complete endpoint documentation, generated from the OpenAPI specification