Obtain JWT tokens to authenticate all other requests.
ConnectPSP API (2.0.0)
ConnectPSP is a PIX payment gateway designed for high-throughput platforms such as digital wallets, betting companies, and fintechs.
This API allows you to:
- 💸 Receive payments via PIX (Cash-In) — standard QR Code or OpenFinance
- 🏦 Send payments via PIX key or bank account data (Cash-Out)
- 📊 Manage your wallet — check consolidated balances and rebalance between transactional and proprietary accounts
- 🪝 Receive real-time events via Webhooks as transactions progress
All endpoints (except POST /auth/token) require two headers:
| Header | Description |
|---|---|
Authorization | Bearer <jwt_token> — obtained from POST /auth/token |
ApplicationToken | Fixed GUID token that identifies your integration |
For financial operations (Cash-Out, Rebalance), an additional header is required:
| Header | Description |
|---|---|
DigitalSignature | HMAC-SHA256 hash of your JWT + CryptoToken. See Authentication Guide |
For POST /cash-in and POST /cash-out, we strongly recommend sending the X-Idempotency-Key header (UUID v4). This guarantees that network retries do not result in duplicate transactions.
| Phase | What to confirm first |
|---|---|
| Setup | Credentials, environment, headers, and webhook readiness in Initial Setup |
| Authentication | JWT generation and DigitalSignature rules in the Authentication Guide |
| Transactions | Your first Cash-In or Cash-Out flow with idempotency and webhook validation |
Request
Returns the consolidated and detailed wallet snapshot across all banking partners (Delbank, Celcoin, StarkBank).
Two account types are tracked per bank:
- Transactional — funds available to cover Cash-Out requests (mirrors your users' exposure)
- Proprietary — reserve/buffer account (your operational capital)
ℹ️ Note: Historical balance lookup (
?date=) is currently in development. Only the current balance is available.
- Staging Environment (Testing)https://api.homologacao.connectpsp.com/account/balance
- cURL
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl https://api.homologacao.connectpsp.com/account/balance \
-H "Authorization: Bearer <token>" \
-H "ApplicationToken: <app-token>"{ "currency": "BRL", "referenceDate": "2026-03-10", "consolidated": { "totalBalance": 1500000, "transactionalBalance": 500000, "proprietaryBalance": 1000000 }, "banks": [ { … }, { … }, { … } ], "updatedAt": "2026-03-10T14:35:00Z" }
Request
Synchronizes your Transactional account to match the total exposure you report.
How it works:
- If
targetAmountis greater than the current transactional balance → funds are pulled from the Proprietary account (Top-up) - If
targetAmountis less than the current transactional balance → excess funds are swept back to the Proprietary account
The targetAmount represents the total exposure of your platform (sum of all user wallet balances + in-flight bets).
This endpoint requires the DigitalSignature header.
Fixed GUID that uniquely identifies your integration. Provided during ConnectPSP onboarding.
HMAC-SHA256 hash of the JWT token + your CryptoToken. Required for sensitive operations. See the Authentication Guide for the exact computation steps.
- Staging Environment (Testing)https://api.homologacao.connectpsp.com/account/rebalance
- cURL
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -X POST https://api.homologacao.connectpsp.com/account/rebalance \
-H "Authorization: Bearer <token>" \
-H "ApplicationToken: <app-token>" \
-H "DigitalSignature: <computed-signature>" \
-H "Content-Type: application/json" \
-d '{ "targetAmount": 1000000.00 }'{ "success": true, "message": "Rebalancing completed successfully." }