Skip to main content
Use this section if you are designing a new Pagou integration or replacing a legacy one.

Who this is for

  • Backend engineers who own payment and payout APIs
  • Platform engineers who own auth, retries, and webhook ingestion
  • Product and operations teams who need a shared lifecycle model

What you can build

  • Pix collections with QR code delivery and webhook confirmation
  • Voucher payments with local instructions such as Boleto, SPEI, Mercado Pago, Webpay, CODI, and PSE
  • Card payments with Payment Element and 3D Secure
  • Recurring subscriptions with saved cards and renewal webhooks
  • Pix Out transfers with operator-safe cancellation and reconciliation
  • Customer records for reusable buyer profiles
  1. Create payments and transfers only from your backend.
  2. Use external_ref as your stable idempotency key for creates.
  3. Treat webhooks as the primary source of truth for async state changes.
  4. Reconcile with GET /v2/transactions/{id} or GET /v2/transfers/{id} when the outcome is unclear.

Public surface

Before you build

  • Get separate sandbox and production credentials.
  • Decide where you will store external_ref, Pagou IDs, and requestId values.
  • Expose an HTTPS webhook endpoint before moving to production.
  • Keep frontend code away from secret credentials.