Pix API
This is the entry point for integrating with Fiserv PSP Pix APIs.
Use this page as a quick guide to understand the full journey, required prerequisites, and where each capability is documented.
Step 1: Choose Your Integration Path
Choose the approach that best fits your business needs. Both paths support core transactional operations, but differ in onboarding, resilience, and feature set.
| Feature | PSP Fiserv | Pix Hub | Description |
|---|---|---|---|
| PSP load balancing | ✗ | ✓ | Distributes transaction volume across PSPs |
| Failover to secondary PSP | ✗ | ✓ | Switches automatically if the primary PSP fails |
| Document validation (iGaming) | ✓ | ✗ | Validates user documents (ID and proof of address) |
| Settlement management (Grocery) | ✓ | ✗ | Handles settlement cycles, account checks, and compliance |
| Payer data | ✓ | ✗ | Provides payer data for tracking and reconciliation |
| Static QR-Code | ✓ | ✗ | Creates fixed QR codes for recurring payment links |
| Cash-out | ✓ | ✗ | Allows withdrawals to registered bank accounts |
| Automatic settlement | ✓ | ✓ (PSP Fiserv accounts only) | Transfers settled funds to the merchant account automatically |
Authentication: Both paths use the same OAuth token — no credential changes are required when switching paths.
PSP Fiserv at a Glance
Choose this path if:
- Single PSP operation — You run with one Fiserv PSP account (no failover or load balancing)
- iGaming or high-risk platforms — You need document validation (ID, proof of address)
- Retail/Grocery operations — You need advanced settlement management and compliance controls
- Custom integration needs — You need features tightly customized to Fiserv APIs
- Banking model workflow — You follow a traditional banking flow with account and transfer management
Pix Hub at a Glance
Choose this path if:
- Multi-PSP resilience — You need automatic failover to a secondary PSP
- Load balancing across PSPs — You want to distribute volume across PSP providers
- Charges-only operation — You only need payment collection (charges)
- Merchant marketplace — You are an ISV serving multiple merchants and need PSP flexibility
Step 2: Follow Your Path
PSP Fiserv
For the complete step-by-step integration guide — including endpoint sequence, async callbacks, and credentials to store — see Direct Integration Guide.
Pix Hub
For the complete step-by-step integration guide — including endpoint sequence, terms acceptance flow, store provisioning, and async callbacks — see Pix Hub Integration Guide.
Next Steps
After choosing your integration path:
- Review your path's checklist — Understand the exact sequence of API calls
- Study the sequence diagrams — Visualize the flow and key decision points
- Review the callback table — Plan your webhook handlers
- Access API documentation — Link to Fiserv API endpoint reference
- Start in Sandbox — Configure your test environment before production
- Monitor your implementation — Track webhook delivery and implement error handling
Updated 19 days ago