Skip to main content
This section is for engineers designing a new integration or restructuring an existing one around the recommended v2 flow.

​
What you can build with Pagou

Pix collections

Create Pix transactions, display QR code data to buyers, refund eligible payments, and reconcile state.

Card payments

Use Payment Element for the recommended browser flow and the transactions API for backend orchestration.

Pix Out payouts

Send money to recipients, track transfer states, and cancel pending payouts when allowed.

Webhooks

Consume asynchronous payment and transfer events as your primary source of status truth.

​
The Pagou integration model

  1. Authenticate every API call using one standardized auth method.
  2. Create resources with a stable external_ref from your system.
  3. Treat webhooks as the primary state update channel.
  4. Use GET endpoints for reconciliation and operator tooling.
  5. Keep v1 flows isolated behind the legacy archive unless you are maintaining an existing merchant.

​
Scope of these docs

This site documents the supported public integration surface:
  • v2 customers
  • v2 transactions
  • v2 transfers
  • Payment Element as a frontend integration product
  • webhook handling patterns
  • TypeScript SDK usage
  • v1 legacy compatibility
Internal transport routes and partner-only endpoints are intentionally kept out of the main authored guides.

​
Next step

Go to the Quickstart if you want the shortest path to a live sandbox transaction.