> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Accept Pix at checkout

Turn on Pix to unlock new revenue in Brazil, with no configuration required. Available for one-time items.

---

## What's new?

We've updated the Paddle platform to support [Pix](https://developer.paddle.com/concepts/payment-methods/pix.md) as a [payment method](https://developer.paddle.com/concepts/payment-methods/overview.md). This means that `pix` is now allowed value for the `payments[].method_details.type` field against a transaction in the Paddle API.

- **method_details** (object): Information about the payment method used for a payment attempt.. Allowed values: `pix` (Pix, a popular payment method in Brazil.)
  - **type** (string): Type of payment method used for this payment attempt.. Allowed values: `pix` (Pix, a popular payment method in Brazil.)

## How it works

Brazil is one of the fast-growing emerging market economies, with a population of over 200 million and an online payment market worth over $500 billion per year. It has its own unique payment landscape, with mobile payment apps like Pix deeply integrated into people's financial lives.

You can now turn on Pix as a payment method for [Paddle Checkout](https://developer.paddle.com/concepts/sell/self-serve-checkout.md). Once enabled, Paddle automatically presents it as a payment option for one-time purchases for customers in Brazil — no additional configuration required.

### Deferred capture

Most [payment methods](https://developer.paddle.com/concepts/payment-methods/overview.md) supported by Paddle are instant capture type payment methods. This means that payment is authorized and captured in one step.

Pix is a deferred capture type payment method, which means funds are captured after payment is authorized. For Pix, this typically happens within ten minutes, but may take longer in some cases depending on the customer's bank or app.

Paddle Checkout includes a new screen to let customers know that funds are being captured. The checkout is completed at this point, so Paddle.js emits a [`checkout.completed`](https://developer.paddle.com/paddlejs/general/checkout-completed.md) event.

The transaction is completed when payment is fully captured, at which point a [`transaction.completed`](https://developer.paddle.com/webhooks/transactions/transaction-completed.md) event occurs.

For this reason, we recommend avoiding using Paddle.js events for [fulfillment](https://developer.paddle.com/build/subscriptions/provision-access-webhooks.md). To be sure a payment was fully captured, use [webhooks](https://developer.paddle.com/webhooks/overview.md) and wait for [`transaction.completed`](https://developer.paddle.com/webhooks/transactions/transaction-completed.md) to occur.

## Next steps

This change is available now.

It's a non-breaking change, meaning it doesn't impact existing integrations. You should test [your checkout success workflows](https://developer.paddle.com/build/checkout/handle-success-post-checkout.md) to make sure they're compatible with deferred capture payment methods.

You can enable Pix in **Paddle > Checkout > Checkout settings**. You don't need to establish a local entity or sign up for any merchant accounts.
## Summary of changes

| Name | Type | Change | Entity | Description |
| --- | --- | --- | --- | --- |
| `payments[].method_details.type` | Enum value | added | Transaction | Returns pix. |