> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Pix Automático

> Accept recurring Pix Automático payments from customers in Brazil, and check the PSPs that process Pix Automático through Payrails.

<picture noZoom>
  ![Pix Automático logo](https://assets.payrails.io/img/logos/pixautomatico/logo.svg)
</picture>

Pix Automático is the recurring payment scheme for Pix in Brazil, run by the Central Bank of Brazil. The customer authorizes a recurring mandate, called an enrollment, once in their banking app. After that, you charge the mandate on a schedule without the customer present. It works like a card-on-file subscription or a direct debit. Payrails processes Pix Automático through dLocal as the payment service provider (PSP).

## How a Pix Automático payment works

Pix Automático has two phases:

1. **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.
2. **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.

Both phases return a pending payment, and Payrails updates it when the PSP confirms the final result. Payrails captures Pix Automático payments immediately, so a successful payment is final. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## 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:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Latin America**</td><td>🇧🇷 Brazil</td></tr>
  </tbody>
</table>

## 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.

> [card]
>
> dLocal logo
>
> dLocalPix Automático via dLocal
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/pix-automatico/dlocal.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[dLocal](https://docs.payrails.com/docs/integrations/payment-methods/pix-automatico/dlocal.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✔</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✔</td></tr>
  </tbody>
</table>

For Save Instruments, the enrollment is the stored credential, and later MIT payments charge it.

## Ways to integrate Pix Automático

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Pix Automático when your workflow returns it as a payment option, and redirects the customer to authorize the enrollment. Pass `meta.subscription` when you create the execution. To control how the redirect opens, listen for the [`actionRequired` event](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `pixAutomatico` as the `paymentMethodCode`. Send recurring charges from your server against the stored instrument. The PSP guide lists the `meta` fields for each phase.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status. Every Pix Automático payment, including each recurring charge, starts as pending.


## Related topics

- [Pix](https://docs.payrails.com/docs/integrations/payment-methods/pix.md)
- [Pix Automático via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/pix-automatico/dlocal.md)
- [Pix via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/pix/dlocal.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.