Mercado Bitcoin Hack Refund: What Finance Teams Should Do

Mercado Bitcoin, which Decrypt describes as Brazil's biggest Bitcoin exchange, says it will refund users after a hack of roughly $40 million. For finance teams, that pledge is good news but not a settled accounting outcome. Until funds actually return, any balance held on the platform needs careful classification, evidence and disclosure, and the right crypto accounting software makes that far easier to manage.

What we know, and what we don't

The confirmed facts

The facts that can be stated safely are short. A hack of around $40 million hit Mercado Bitcoin, the exchange has said it will refund users, and the report was published on 3 November 2026. We have previously covered the earlier accounting steps after the Mercado Bitcoin withdrawal halt, and that piece is the natural starting point if your team has not yet dealt with the freeze itself.

The details that are still open

The source material available to us does not set out the attack method, the timetable for refunds, whether reimbursement will be in kind or in local currency, or whether any regulator has opened a review. We are not going to guess at any of those. Treat every one of them as an open question to put to the exchange in writing, and record the answer you receive with a date.

That discipline matters. A statement of intent from an exchange is evidence of management's position. It is not, on its own, a contractual right to a specific amount at a specific time. Your accounting should reflect that distinction until the exchange gives you something firmer.

Why a refund pledge is an accounting event

Balances on a compromised platform

If your firm or your client holds assets on an exchange that has suffered a loss, the first question is what you still control. Assets in your own self-custody are unaffected by the hack. Balances recorded at the exchange are a claim on the exchange, and the strength of that claim depends on the terms of service, the exchange's solvency and its stated intent to refund.

A promise to refund supports the view that the claim has value, but it does not remove uncertainty about the amount or the timing. Preparers generally need to consider whether the balance should still be carried at the last confirmed position, whether an impairment or credit-loss assessment is needed, and whether a separate receivable-style line is more transparent than leaving the balance inside the normal holdings category. The correct answer depends on your reporting framework, the facts of your exposure and your auditor's view, so agree the approach before the period-end rather than during the audit.

Gain, loss and recovery are different things

A hack loss, a later recovery and any market movement in the interim are three separate items. Mixing them makes the ledger unreadable. If a refund arrives in a different asset or in fiat, or at a different valuation date than the loss, the difference needs its own treatment and its own support. Keeping these as distinct entries with clear references is what lets a reviewer follow the story a year later.

Practical steps for accounting firms and CFOs

Establish your exposure

Start with a precise list of wallets, sub-accounts and API-connected accounts at the exchange, and the balances recorded in your books at the last date you can verify. Our guide to spotting exchange exposure with crypto accounting software sets out the same approach in the context of a larger incident, and the method transfers directly.

• Pull the most recent transaction history and balance snapshot from the exchange, and store the export with its timestamp.
• Reconcile that snapshot to your ledger and list every unreconciled item.
• Identify any client or fund entities with assets there, including those held through omnibus or nominee arrangements.

Preserve the evidence trail

Keep every notice, email, help-centre statement and terms-of-service version from the exchange, with the date you captured it. If the refund later arrives in a form or amount that differs from expectations, that file is what supports the entry. Auditors will ask for it, and it is far easier to assemble in real time than to reconstruct.

Decide on interim presentation

Agree with the engagement partner or the audit committee how affected balances will appear in management reports before the refund lands. Options include a separate line for assets held at a platform under a loss event, a note describing the pledge and its uncertainty, or both. What you should avoid is a silent reclassification that a reader cannot trace.

Plan for the refund itself

When funds or tokens come back, you will need to match each receipt to the original balance, record any difference, and set the valuation date and method consistently. If your team uses digital asset accounting software, check that it supports tagging a receipt as a recovery against a prior loss entry, rather than treating it as a new acquisition. Plain crypto bookkeeping software that only captures deposits and withdrawals can leave you with a recovery that looks like fresh income or a fresh purchase.

Tax and compliance implications

For firms advising several jurisdictions

The source describes a Brazilian exchange, so the first tax question for Brazilian taxpayers is how local rules treat a loss at a custodian and a later reimbursement. We have no statement from the tax authority in the source and will not describe one. What can be said generally is that the tax treatment of a theft or custodial loss, and of a later recovery, varies by country and by taxpayer type. Firms with clients in several jurisdictions should check each one against the relevant authority's published guidance and document the position taken.

For individual clients

If you are advising an individual who had funds at the exchange, the plain advice is to avoid taking a final tax position until the refund terms are clear. Record the facts, keep the exchange's statements, and revisit the position once the outcome is known. If a filing deadline falls before then, document the reasoning for the interim treatment so it can be amended cleanly if needed.

AML and counterparty risk

Any hack raises a monitoring question: could stolen funds flow toward your own platform or clients? Teams should make sure their screening picks up addresses linked to publicised incidents as intelligence becomes available. The same logic appears in coverage of automated laundering after the Binance hack, where speed of movement was the central lesson. We do not know where the Mercado Bitcoin funds went, and nothing here suggests a link to any particular actor, but the control is the same: be ready to screen quickly if addresses are published.

What this means for your tooling

What good software should do here

An incident like this tests whether your records can answer basic questions fast: what did we hold at the exchange, at what cost, as of which date, and what has been received since? Good crypto accounting software keeps an auditable link between on-chain or exchange data and the ledger, supports snapshot reports at a chosen date, and lets you annotate entries with the supporting evidence.

Questions to ask your team this week

• Do we have a dated, reconciled snapshot of every account at the exchange?
• Who owns communication with the exchange, and where is it logged?
• Have we agreed the interim presentation with our auditor or reviewer?
• Can our system record a recovery against a prior loss, not as a new acquisition?
• Is our counterparty-risk register updated with custodian concentration at this exchange?

For broader policy context on reporting duties and controls, see our overview of crypto compliance and reporting.

FAQ

Has Mercado Bitcoin confirmed how and when users will be refunded?

The report we relied on says the exchange will refund users after the roughly $40 million hack. It does not give us a timetable or the form of reimbursement, so do not assume either. Ask the exchange directly and keep the reply.

Should I write off a balance held at the exchange?

Not automatically. A stated intent to refund affects the assessment of recoverability, but the right treatment depends on your reporting framework, the terms of service and your auditor's view. Document the judgement and the evidence behind it.

How should a later refund be recorded?

As a recovery matched to the original balance or loss entry, with the valuation date and method stated. It should not be booked as a new purchase or as unrelated income unless your advisers conclude that treatment is correct.

Does this affect clients' tax filings?

Possibly, and it varies by country. We have no tax authority guidance in the source, so check the relevant authority's published position and record the interim treatment so it can be amended once the refund outcome is known.

What is the first thing a CFO should do?

Reconcile your records to the last verified exchange balance, preserve every notice from the exchange, and agree with your auditor how affected balances will be presented until the refund is completed.

Source: Decrypt