Getting it back out

The withdrawal path, step by step

A deposit is a one-way door until you use the exit. This page describes that exit: the checks, the queue, and what to do if the door does not open.

Before you press withdraw

Most withdrawal problems start before the request is submitted. A few minutes of preparation removes most of them:

  • Check the destination. Read the address character by character, and check that the network matches the asset. A transfer sent on the wrong network is not a support ticket — it is usually unrecoverable.
  • Know what you are withdrawing. The asset, the network, any fee shown on the request screen, and the balance available after the request.
  • Have your second factor to hand. The company describes two-factor authentication and a secondary confirmation on sensitive actions. Expect to complete both; do not disable either to make a request faster.
  • Check your account details are current. If your identity documents have expired or your contact details are stale, the review step will stop and ask for updated information.
  • Leave room for the network. Confirmations on the receiving chain take time that has nothing to do with NPX.

What happens after you submit

The path below reflects how a reviewed withdrawal process works and how NPX describes its own controls. It is not a published service-level agreement, and no timeline is stated here because none has been published.

  1. Request

    You submit the withdrawal

    You choose the asset, network, amount and destination. The system records the request with a timestamp and an identifier. That identifier is the single most useful thing you can keep — every later question about the request will start with it.

  2. Authentication

    Your identity and session are checked

    Two-factor authentication confirms that the person making the request owns the account. Identity documents are checked for validity. This stage confirms who is asking, not whether the request should be granted.

  3. Second confirmation

    The request is confirmed out of band

    A separate confirmation — through a channel other than the one you are already using — prevents a stolen password or a hijacked session from being enough on its own. If you did not initiate a withdrawal and receive this prompt, treat it as an alarm, not an annoyance.

    Change your password immediately, revoke active sessions, and contact support. A confirmation prompt you did not trigger means someone else is inside the account.
  4. Review queue

    The request waits for a decision

    Most requests pass review without anything being asked of you. Some are examined more closely — a large amount, a new destination, a recent change to account details, or activity that does not fit your normal pattern. During this stage the funds are typically placed on hold so they cannot be spent twice.

  5. Release

    The asset is sent, and you close the loop

    Once approved, the transfer is broadcast. Check the destination against your own records, and confirm the amount received. If the request is rejected or returned, there should be a reason attached to it — ask for that reason in writing.

What “withdrawal review” actually means

It is worth knowing what review looks at, because that explains why the step exists and why it sometimes takes longer than expected.

  • Account takeover. Is the request consistent with how this account normally behaves? A new destination combined with a fresh password change and a login from an unfamiliar location is the classic signature of a stolen account.
  • Financial-crime checks. As a registered money services business, NPX is subject to Bank Secrecy Act obligations, which include customer identification and suspicious-activity monitoring. Some reviews are the company discharging those obligations.
  • Operational verification. Does the destination match what the account is set up to use? Is the withdrawal internally consistent — asset, network and amount?
  • Approval authority. The company describes role-based permissions and multi-party approval for high-risk internal actions. A withdrawal beyond a certain threshold may need a second person to sign off.

None of those checks is unusual, and none of them is personal. A review that asks you a question is generally a review that is working as designed. A review that goes silent is the situation worth chasing.

Why delays exist

A delay is usually neither routine nor catastrophic. The common causes are mundane: a longer queue, an expired document, an unfamiliar destination, network congestion, or a request that crossed a threshold and needs a second approver.

This site publishes no withdrawal timelines, because NPX has published none. Any specific number quoted elsewhere — “usually within X hours” — cannot be supported here. Ask support for the current expectation and your request's stage.

One uncomfortable possibility is worth naming: a queue that keeps growing across many customers, with no explanations, can signal that the operator cannot meet withdrawals rather than that it is being careful. One slow request is not evidence of that; a pattern of vague answers would be. The segregation page explains why that failure mode is connected to how client assets are held.

If your withdrawal is held

A hold is not a refusal. Work through this in order, and keep a record of everything you send:

  1. Find the request identifier and its status. Note the time of submission, the amount, the asset and the destination.
  2. Check your inbox and account notifications. Most reviews that need something from you will say so — an expired document, a mismatched name, an address confirmation.
  3. Reply through the official channel. Use the support channel inside the product or the address listed on the official site, not a link from an unsolicited message.
  4. Ask a specific question. “Is my request in review, what stage is it at, and is anything required from me?” produces a better answer than “where is my money?”
  5. Ask for the reason in writing if the request is refused or returned. A refusal without a stated reason is a fact worth recording.
  6. Keep timestamps. If the issue escalates, a plain log of dates and responses is far more useful than a thread of frustration.

While a request is held, do not open a second withdrawal for the same funds, and do not move assets into a newly created account to “test” the exit. Both make the review harder to complete.

One rule that prevents most disasters

Test the exit before you need it. A small withdrawal, completed while nothing is urgent, tells you more about how custody actually behaves than any statement about process. Do it early, and keep the record.

What protects you, and what does not

The controls are real and useful, but they are aimed at specific threats. Matching them against the actual risks is the honest way to read them.

What could still go wrong

Risks a review queue does not remove

  • You send to the wrong network or address and the transfer cannot be reversed.
  • You approve a secondary confirmation prompt that you did not initiate.
  • The asset falls in value while the request waits — custody does not protect against market risk.
  • A hold drags on with no explanation, and you cannot tell caution from insolvency.
  • You deal with an impersonator who mimics support and asks you to “verify” a withdrawal.
What is described as protecting you

Controls around the exit

  • Two-factor authentication on login and a second confirmation on the request itself.
  • A review step before release, with escalation for unusual requests.
  • Role-based permissions and multi-party approval for high-risk internal actions.
  • Customer-asset balances described as held apart from operating funds.
  • Monitoring and alerts on anomalous account activity.

The right-hand column summarises controls NPX describes. This site has not tested them; none of them is a guarantee, and none replaces your own care with addresses and credentials.

The three documents behind this site, and what each one does and does not prove.

Read the documents

For incidents and the operational side of withdrawals, see operational reliability. For the controls behind authentication and permissions, see security architecture. For a close reading of the documents, see the evidence archive.

Important

This site presents corporate and operational information about NPX Exchange Ltd. Corporate registration, an EIN, an MSB registration and a Form D filing are not financial licenses, regulatory approvals or endorsements, and none of them guarantees the safety of customer assets. Digital assets are volatile and involve risk, including possible loss of principal. Nothing here is investment advice or a solicitation.