Mercado Bitcoin pauses deposits and withdrawals: check pending transfers

What the reporting confirms

The central operational fact is straightforward: Mercado Bitcoin paused transfers into and out of the platform following a security incident. PANews reported the company's statement that customers were not affected. Attribute that assurance to the company; the public report cannot independently reconcile an individual customer's account.

BitNotícias reports that Mercado Bitcoin published destination addresses to help monitor and track assets. The exchange's restoration message concerns the service interruption; checking an individual transfer still requires its own account record.

A pause in deposits and withdrawals changes the next decision for someone preparing to send money. An address saved before the incident does not answer whether the receiving service has resumed. The practical response is to check the relevant service state before issuing another transfer, rather than treating an old address or a previous successful deposit as evidence that the current route is open.

The same distinction applies to a withdrawal already requested. The announcement that services are paused does not identify the state of each request. Open the individual record and preserve what it actually shows. A pending request and a transaction with an identifiable blockchain record need different follow-up questions.

If you were about to deposit

Keep the assets at the sending end while establishing whether the receiving route is available. Review the coin and network you intended to use, then compare them with the service information shown by Mercado Bitcoin.

If a withdrawal from another platform has already been submitted, collect that platform's withdrawal identifier, the destination, the selected network and any transaction hash shown. Record the amount and the time displayed alongside them. Do not replace those details with the amount in a news headline: an aggregate incident estimate cannot explain the status of one transfer.

A useful record keeps the sender's status and the receiver's status in separate fields. Write down what each service says, including whether the sender provides a transaction hash and whether Mercado Bitcoin shows a deposit entry. That leaves a concrete question for support: which stage of this particular transfer remains unresolved?

Avoid sending another payment merely to see whether it arrives. A second transfer introduces another record without resolving the first one. The unresolved issue is receiving-service availability and the state of the original transaction. Resolve those questions from the service update and transaction history before preparing a new instruction.

If a withdrawal is pending

Start with the withdrawal record inside the account. Preserve its identifier, asset, amount, destination and displayed status. If a transaction hash is available, keep it with the record rather than copying it into a separate note without context. These details make it possible to compare the same request across later updates.

Record the displayed time with its timezone. The first report cited here was published at 21:50 SGT on 2 November; that reporting timestamp does not establish when your withdrawal was requested or processed. Keeping the clocks distinct avoids describing an earlier request as a transfer initiated after the pause.

If your request has no transaction hash displayed, ask about the request's processing state. If a hash is shown, ask about the transaction identified by that hash and the receiving account's record. Neither question requires guessing how the security incident occurred. Supply the details from your own request and retain the response with it.

Do not infer that a new request will move ahead of an existing one. The reports opened for this article contain no confirmed queue order, processing deadline or account-specific exception. A promised shortcut would need support from the exchange's actual instructions, not from someone responding to the news on social media.

The company's assurance and your account record

PANews reports that Mercado Bitcoin said customers were not affected. That is a material statement about the company's position. It should remain attributed, because the article has no access to customer ledgers or a completed independent reconciliation. Readers can compare their own account balance and transfer history without turning an attributed statement into a conclusion about every request.

Save a dated view of the relevant balance and pending transfer, then keep later changes with that original record. The purpose is to document what the account showed at each check. A screenshot of a balance alone can omit the asset, account section or pending request that explains the question you want answered.

For an outstanding deposit, retain the sending record as well. For an outstanding withdrawal, retain the destination details supplied at submission. Use the existing account's support route to ask about the specific record.

Three actions for the pending record

1. Open the original request and save its asset, network, amount, destination and identifier together. For a deposit, include the sending platform's record; for a withdrawal, include the request inside Mercado Bitcoin.
2. Write down the displayed status and check time. Add any transaction hash to that same record. Keep the sender's status separate from the receiver's deposit entry so a later reply can identify the unresolved stage.
3. Compare the next service update with the route in your record, then check that original request again. If it remains unresolved, ask support about the same identifier and retain its response beside the earlier status.

What a useful reopening update needs to answer

Look for an update that identifies the service being restored. “Operations” can be a broad description; your decision concerns the particular deposit or withdrawal route. Keep the coin and network alongside the update when reviewing whether it answers your situation.

Then check the pending record again. A service reopening and completion of a request are separate observations. Save the new status and its time so it can be compared with the previous check. If the record remains unresolved, refer to that same identifier when asking for clarification.

The sources reviewed here do not establish a final incident loss, a verified technical cause or a timetable for every customer. Those questions require further evidence. An exchange response about service availability is the relevant next fact for a transfer decision; a technical theory from an outside commentator does not substitute for it.