How a Pix Automático payment works
Pix Automático has two phases:- Enrollment and first payment. The customer selects Pix Automático at checkout. Payrails sends the subscription schedule to the PSP, returns a redirect URL, and the customer authorizes the mandate in their banking app.
- Recurring charges. Payrails stores the enrollment as a payment instrument. You charge it as a merchant-initiated transaction (MIT) for each billing cycle. These charges need no redirect or customer interaction.
Supported currencies and countries
Pix Automático supports BRL (Brazilian real) as its only presentment currency. Pix Automático is available to customers based in:| Regions | Countries |
|---|---|
| Latin America | 🇧🇷 Brazil |
Integrate Pix Automático
Choose the PSP that processes Pix Automático for you. The guide covers the PSP-side setup, the Payrails configuration, the request fields for each phase and the rules for scheduling recurring charges.dLocal
Pix Automático via dLocal
Check PSPs
| Workflow | dLocal |
|---|---|
| Payrails SDK | ✔ |
| Payrails API | ✔ |
| Delayed / Manual Capture | ✖ |
| Instant Capture | ✔ |
| Cancel / Void | ✖ |
| Refund / Reverse | ✔ |
| Save Instruments | ✔ |
| Merchant Initiated Transaction (MIT) | ✔ |
Ways to integrate Pix Automático
- Payrails SDK: the Web SDK shows Pix Automático when your workflow returns it as a payment option, and redirects the customer to authorize the enrollment. Pass
meta.subscriptionwhen you create the execution. To control how the redirect opens, listen for theactionRequiredevent. - Payrails API: call lookup payment options, then authorize with
pixAutomaticoas thepaymentMethodCode. Send recurring charges from your server against the stored instrument. The PSP guide lists themetafields for each phase.