Our Solutions
Integration Routes
For Local Payments
Choose the flow that fits your product: hosted checkout, API pay-in, API pay-out, status checks, confirmations, and balance requests.
Choose the flow that fits your product: hosted checkout, API pay-in, API pay-out, status checks, confirmations, and balance requests.
Each route is meant for a different level of merchant control, from no-code links to server-side API orchestration.
Redirect customers to a PagaSul payment page when you want a faster front-end launch.
Create a payment request from your backend and pass method, payer, and callback data.
Disburse funds to recipients through supported local account and payment-method fields.
Check payment state and submit extra confirmation data for flows that require it.
Request account balances through the documented client balance endpoint.
Initialize a payment and collect funds from a payer.
Create a pay-out request for recipient disbursement.
Track current payment state and submit required confirmation data.
Retrieve account balance information by currency.
A production integration needs account credentials, signed requests, callback handling, and method-specific customer fields.
Use the commercial page for the readable country breakdown; use the API documentation for exact method codes and field requirements.
Pass a method code when you want to preselect a payment method for checkout.
Provide country-specific payer or payee fields when local rails require them.
Process status updates from PagaSul so your internal order state stays synchronized.