Building blocks
| Capability | Main surface | Use it for |
|---|---|---|
| Customers | /v2/customers | reusable buyer profiles |
| Transactions | /v2/transactions | Pix and card payment creation and retrieval |
| Refunds | /v2/transactions/{id}/refund | full and partial reversals |
| Webhooks | payment event delivery | authoritative async status changes |
Recommended choices
- Use Pix when you want the fastest collection path in Brazil.
- Use Payment Element for new card checkouts.
- Keep one canonical status map in Transaction Statuses.
- Reconcile instead of guessing after network or worker failures.
Common journeys
- Create a Pix payment, show QR code data, and fulfill on
transaction.paid. - Create a card payment from a Payment Element token and handle
next_actionwhen 3DS is required. - Issue refunds from your backend and wait for the resulting transaction status to settle.