Payment building blocks
| Capability | Public surface | Recommended usage |
|---|---|---|
| Customer records | /v2/customers | Create or fetch reusable buyer profiles |
| Transactions | /v2/transactions | Create Pix or card payments and inspect state |
| Refunds | /v2/transactions/{id}/refund | Reverse eligible transactions when your product allows it |
| Webhooks | transaction events | Receive authoritative status transitions |
Recommended choices
- Use Pix when you want the fastest collection path in Brazil.
- Use Payment Element for new card projects.
- Use Customers if your product keeps reusable payer data.
- Centralize status handling in Transaction Statuses.
Common journeys
Pix collection
Create a payment, render QR code data, and settle by webhook.
Card payment
Use hosted card fields and 3DS through Payment Element.
Refund operations
Reverse eligible transactions and reconcile refund outcomes.
Customer management
Create and fetch customer records used across payment operations.