Guides

Pix MED: How the Special Return Mechanism Works for Businesses

Pix MED explained for businesses: what the special return mechanism covers, the 80-day, 7-day, 72-hour and 6-hour windows, and what a block means.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: Pix MED: How the Special Return Mechanism Works for Businesses
Cover image for Lumx blog article: Pix MED: How the Special Return Mechanism Works for Businesses

Pix (Brazil's instant payment system, run by the Central Bank) has a Mecanismo Especial de Devolução, the Pix MED: a set of Central Bank of Brazil (BCB) rules that lets a recipient's institution block and return a payment, without asking the recipient, when fraud is credibly suspected or a participant's system failed.

A business that receives Pix meets the MED as the account that gets blocked. This guide covers the scope, the return windows, what happens to the balance, and who handles the notice when the Pix settles in stablecoin. The basics are in the Pix for business guide.

What does the Pix MED cover, and what does it leave out?

The MED is defined in Article 41-B of the Pix Regulation, annexed to Resolution BCB 1 of August 12, 2020. It applies in three situations: a well-founded suspicion that the Pix arrangement was used for fraud, an operational failure in the IT system of any participant in the payment, and an error in sending a Pix Automático order (the recurring charge the payer authorizes once). The Central Bank's implementation guide, version 4.4, gives the examples below. The rules do not depend on the kind of account: the fraud marker described later is recorded against a CPF (individual taxpayer ID) or a CNPJ (company taxpayer ID) alike, so the same rules apply to an individual's account and a company's.

What the MED covers and what it leaves out, with who asks for the return. Source: BCB returns guide, version 4.4, and Pix Regulation Article 41-B.

Situation

Covered by the MED?

Who asks for the return

A scam, account takeover, stolen phone or coercion, even if the payer authorized it with a password or biometrics

Yes, as fraud

The payer's institution, after the payer's complaint

A seller who takes payment and never ships, or ships something entirely different

Yes, as fraud by the seller

The payer's institution

A duplicate send, or an amount different from the one the payer ordered

Yes, as an operational failure

The payer's institution, with 48 hours for the recipient's institution to decide

A Pix Automático order sent in error by the payer's institution

Yes

The payer's institution refunds from its own funds, then may ask the recipient's institution to return it

The payer typed the wrong key, sent twice by choice, or disputes late delivery

No

The recipient's goodwill, the courts or the seller's terms

Fraud proceeds already spent on goods from a good-faith third party

No

Not returnable through the MED

The guide's revision table dates the self-service MED section to September 30, 2025 (version 4.0). Since October 2025 an accepted notice also blocks the recipient's Pix key, and on September 1, 2026 (version 4.4) the time to contest a return grew to 80 days.

The guide is explicit that the MED is not a chargeback mechanism. A payer who does not recognize a purchase cannot get the money back by saying so, and a seller who acted in good faith is not debited.

How a MED fraud claim runs, step by step

From the payer's side, the claim starts with a report in the payer's own bank app or service channel, and the business that was paid learns of it when its own institution receives the notice. Any sale to a payer who later says it was a scam can lead to one.

  1. The payer reports the fraud to its own institution, in the app or the service channel, within 80 days of the original Pix.

  2. The payer's institution opens a Recuperação de Valores (funds recovery) in the DICT (the Central Bank's directory of Pix keys) right away, without judging the merits or asking for a police report.

  3. The DICT sends infraction notices to the institution of the first recipient and, through tracing, to the institutions of recipients of later Pix payments that carried the money onward.

  4. Each institution blocks at once the amount requested, or the whole balance if it is smaller. While the notice is open, a credit that arrives is blocked too, up to the total.

  5. Each institution has 7 calendar days to analyze whether its customer committed fraud, then accepts the notice and keeps the block, or rejects it and releases the money.

  6. If the first recipient's notice was accepted, the payer's institution has 72 hours to start the return. If it does not, the DICT closes the case and every block is released.

  7. Each institution in the chain has 6 hours to execute its return in 99% of cases, per the Central Bank's Pix timing manual. The requests run one after the other, so by our own arithmetic a chain of four adds up to about 24 hours.

  8. Each institution closes its request as fully accepted, partly accepted or rejected, for example for lack of balance or a closed account. The payer's institution can cancel the case at any time, and an institution that cannot return the money does not pay from its own funds.

At step 4, the institution that holds the account is the one that blocks. A Lumx named BRL account is issued by a banking partner. Before a deposit reaches that account's balance, Lumx's own transaction monitoring screens it: a flagged one is held for an RFI (request for information, a compliance hold that asks for a document before a transaction clears).

How long after a Pix arrives can it still be returned?

Up to 90 days, depending on the route. The windows are written in the Pix Regulation and in the guide, and they do not start from the same event.

Windows for each return route, counted from the original Pix unless the row says otherwise. Source: BCB returns guide, version 4.4, and Pix Regulation Articles 39-B and 41-A.

Route

Who starts it

Window

Voluntary return, total or in parts

The recipient

Within 90 days

Operational failure of the payer's institution

The payer's institution, through the DICT

The recipient's institution decides within 48 hours of the request, and returns only what the account holds

Precautionary block on suspected fraud

The recipient's institution

At most 72 hours from the credit, then return or release

Fraud claim (funds recovery)

The payer's institution

Opened within 80 days, then 7 days of analysis, 72 hours to start the return and 6 hours per institution to execute it, in 99% of cases

Fraud spotted by the recipient's institution on its own

The recipient's institution

Within 90 days, if funds are in the account

A Pix that reached a business account stays exposed to a fraud claim for 80 days and to its own institution's return for 90. Under Article 41-A, every return presupposes enough funds in the recipient's account.

Lumx's docs list Pix as running 24/7/365 with no cut-off and instant settlement, and add that Brazilian holidays may still affect dispute windows. A transaction held for an RFI is paused until it is resolved. See Payment rail cut-off times in the Lumx docs.

What the MED does to a business that receives a Pix

Every Pix participant must write into its customer contract that it can block and debit the account without prior authorization when the MED applies. The customer is told, not asked. For a business with a CNPJ, that clause is already in the account agreement.

Four mechanics matter in practice:

  • While the notice is open (the 7-day analysis window), the block takes the amount requested by the DICT, or the whole balance if it is smaller, and it can be built in several partial blocks as credits arrive until the total is reached.

  • A court order has priority over a MED block, and no other debit can overtake it.

  • When the institution accepts a fraud notice, a fraud marker is recorded in the DICT against the recipient's tax ID and Pix key, and every participant sees it when it queries that key or tax ID.

  • After acceptance, the account can no longer move money by Pix. Since October 2025, under Article 89, paragraph 2 of the Pix Regulation, the institution that accepts a notice must reject every Pix in which that user and account are payer or recipient, and the Central Bank blocks the Pix key automatically. The guide says this removes the need for multiple blocks and partial returns after the notice closes.

On Lumx, a deposit is screened before it reaches that point. A Pix from a payer consistent with the flow declared at KYB (know your business, the verification of a company and its owners) passes, and one outside the pattern can raise an RFI and, as a result, a return. If the customer does not answer within 24 hours, the transaction may be refunded to the sender. The rules on who may pay a Brazilian account are in the payer rules guide.

Pix in, stablecoin out: who handles the notice

The MED is a Pix procedure: the notice goes to the institution that holds the account the Pix reached, and the block and the return run on that account. A flow that collects BRL by Pix and settles in USDC or USDT follows the same path for its Pix leg. Keep the MED in your risk register: the risk register template shows how.

On a named BRL account at Lumx, MED notices reach the banking partner, which holds the Pix connection and answers the payer's institution. Lumx tells the customer directly and takes part in the case (Lumx's own statement, November 21, 2026).

A foreign company can hold the named BRL account without a local entity (see the named virtual account explainer). For a question about a specific notice, write to operations@lumx.io, the support and complaints channel.

If a balance is blocked: what a business can do

A block is not a verdict. Three things are open to the business.

First, answer the institution with evidence of real goods or services, such as the invoice and delivery record. It has 7 days to decide, and a notice it rejects releases the money.

Second, during a precautionary block, the recipient can still return the full amount itself and settle the deal another way.

Third, if the institution accepts a notice the business believes is wrong, the guide points to the dispute procedure of the Central Bank's Pix dispute manual, and then the courts. A recipient whose payer used the MED to take back money after delivery can contest the return within 80 days.

On Lumx, an RFI on a held transaction runs the same way: compliance asks for context, the customer answers, and compliance decides whether to release it.

I would write the MED path into the runbook before the first notice arrives: who reads the notice, who gathers the invoice and the payer's history, and who answers it. A payer that repeats on a flow declared in KYB is the strongest file to send back.

When the MED is the wrong tool for a payer

A wrong key, a late delivery or a buyer's regret are not MED cases. A seller that wants a card-style process builds it into its own terms and returns the Pix itself, within the 90 days of Article 41-A. On Lumx, a floating Pix on-ramp expires after 1 day, and a payment that lands after that is not processed and goes back to the sender on Pix.

What a Pix deposit looks like on Lumx

A business that collects BRL on Lumx creates a BUSINESS customer, completes KYB and, once approved, receives Pix on a named BRL account in its own name, issued by a banking partner. A one-off on-ramp returns a Pix code (brCode) for a single payment, and a standing autoconversion rule returns a static Pix QR code that every later payment can use. Both convert the BRL to USDC or USDT and deliver it to the customer's wallet.

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

For the MED, one part matters: a payer consistent with the declared flow passes, and one outside the pattern can raise an RFI with a 24-hour window to answer. Deposits also count against the customer's limits, which the limits page in the docs lists. The BRL to USDC page shows the live pair, the merchant checkout case shows the flow from the payer's side, and the product is on named virtual accounts.

Methodology and sources

Verified on November 21, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Ludde Lorentz on Unsplash.

  • What is the Pix MED?

    The Pix MED (Mecanismo Especial de Devolução) is the Central Bank of Brazil's set of rules that lets a recipient's institution block and return a Pix when fraud is credibly suspected or a participant's system failed. On Lumx, the BRL account is issued by a banking partner, and Lumx's own monitoring can hold a deposit for an RFI first.

  • Is the Pix MED a chargeback?

    No. The Central Bank's guide says the MED is not a chargeback mechanism: a payer who dislikes the goods cannot use it, and a fraud claim has to show the seller acted in bad faith. On Lumx, a Pix that arrives after its on-ramp expired is refunded to the sender on Pix.

  • How long does a Pix MED take?

    A fraud claim can be opened up to 80 days after the original Pix. The recipient's institution then has 7 days to analyze, the payer's institution has 72 hours to start the return, and each institution has 6 hours to execute it (99% of cases, per the timing manual). A precautionary block lasts at most 72 hours. On Lumx, Pix runs 24/7/365 with no cut-off, and the docs note that Brazilian holidays may still affect dispute windows.

  • Can a business account be blocked because of a MED?

    Yes. While the notice is open, the institution blocks the amount requested, or the whole balance if it is smaller, plus later credits up to the total. Once it accepts the notice, since October 2025, the account and its Pix key are blocked for Pix altogether. On Lumx, a deposit flagged by monitoring is held for an RFI with 24 hours to answer, and a question about a specific notice goes to operations@lumx.io.

  • Who handles a Pix MED notice when a business settles in stablecoins?

    The institution that holds the account the Pix reached receives the notice and answers the payer's institution. On a named BRL account at Lumx, that is the banking partner, which holds the Pix connection, and Lumx tells the customer directly and takes part in the case. Questions about a specific notice go to operations@lumx.io.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

pix-med-special-return-mechanism

A

pix-med-special-return-mechanism

Pix MED: How the Special Return Mechanism Works for Businesses

Copy link

Copied!

pix-med-special-return-mechanism

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Guides

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.