Withdraw

Overview

Withdrawal is the QAAY service for sending cryptocurrency from your QAAY account to an external wallet. You select the cryptocurrency, enter the destination address, choose the blockchain network, and submit the transfer. Since blockchain networks process and confirm these transactions, withdrawals are practically irreversible once broadcast. Therefore, it is essential to ensure the accuracy of the address, network, and any required routing fields.

Key Concepts

Term	Precise definition in QAAY (Withdraw)
Withdraw	Sending crypto from QAAY to an external wallet address on a blockchain network.
Currency to Withdraw	The cryptocurrency selected for withdrawal (e.g., BTC, USDT) and the available balance eligible for withdrawal.
Balance	The quantity of the selected cryptocurrency you want to withdraw.
Address	The destination wallet address for the cryptocurrency delivery.
Paste Address	A secure method to insert a copied address, minimizing typing errors.
QR Scan	Using your device’s camera to scan a destination address reduces entry errors.
Network	The blockchain network selected for the transfer must match the networks supported by the destination wallet.
Memo / Tag	A routing identifier is required for certain assets or destinations (for example, XRP destination tags) that the receiver uses to credit the correct account.
TxID / Transaction Hash	A unique on-chain identifier for tracking withdrawal status in a blockchain explorer.
Confirmations	The number of blocks added after a transaction is included; more confirmations indicate greater finality.
Pending	Indicates the request exists but is still processing, such as awaiting security checks or blockchain confirmation.
Completed	A status meaning the withdrawal was processed successfully, and the transaction was finalized according to the platform and network rules.
Failed	A status meaning the withdrawal did not complete due to a technical issue, network issue, or invalid input, and the asset was not transferred.
Cancelled	A status meaning the withdrawal stopped before finalization and did not change the balance.
Savings Balance	The internal QAAY account balance is used as the source for Withdrawals (withdrawals are deducted from Savings).
Credit line Value	The internal QAAY account is used for borrow mechanics. Transfer availability may be constrained by risk controls, even when balances are available.

How Withdrawals Work

Withdraw enables users to transfer digital assets from QAAY to any compatible external wallet. Users manage balances across internal accounts, such as Savings and Credit Line, each with a specific function. Withdrawal is intended for external blockchain transfers, so the final delivery of funds is subject to blockchain rules, including network Fees, transaction confirmations, and the receiving wallet’s compatibility.

Withdrawal is limited to cryptocurrency transfers to external wallets. Withdrawals to bank accounts or fiat conversion are not supported. As an on-chain transaction, withdrawal is subject to blockchain finality and current network conditions.

Withdrawals are available at any time and under all conditions. Even if a user is in a high-risk status, withdrawals remain permitted. There are no platform-level restrictions on withdrawals within QAAY.

Rules & Conditions

To successfully complete a withdrawal, the user must initiate the request with sufficient internal balance and provide accurate on-chain transfer details. In QAAY, withdrawals are deducted from the Savings account. Therefore, at the time of submission, the user must have a sufficient available balance of the selected asset in Savings. If the asset is held in another internal account (for example, Credit Line), the user must first perform an internal Transfer before proceeding with Withdraw.

From an input perspective, the withdrawal form requires at a minimum: selection of the cryptocurrency, entry of the destination wallet address, and selection of the blockchain network. Manual entry of the address is not recommended. The Paste Address and QR Scan features are designed to reduce typographical errors. This is technically critical because blockchain transactions, once submitted, cannot be cancelled or reversed like some traditional bank transfers. Entering an incorrect address may result in permanent loss of funds.

Network selection is equally critical. The selected network must exactly match the network supported by the destination wallet for the chosen asset. Fees and confirmation speed vary depending on the network and its current congestion. On networks such as Ethereum, the Fee market (“gas”) determines how quickly a transaction is included in a block and confirmed.

If the selected asset or network requires a Memo / Tag (or similar routing identifier), it must be entered exactly as provided by the recipient. Some networks, such as Stellar and the XRP Ledger, use memos or destination tags for internal routing within exchanges or custodial systems. Failure to provide this information correctly may prevent the receiving platform from automatically crediting the funds to the correct account.

From a security standpoint, Withdraw requires security confirmations such as email verification and two-factor authentication (2FA). Multi-factor authentication is a widely accepted security standard that requires proof of control over at least two independent authentication factors and is strongly recommended for asset transfers, given the irreversible nature of blockchain transactions.

For standard withdrawals, KYC verification is not mandatory. There is also no fixed minimum or maximum withdrawal Balance defined. Practical withdrawal limits depend on the available withdrawable balance in the Savings account, the current account status, and applicable network constraints.

Users pay a single withdrawal Fee displayed before confirmation. This Fee may include network, service, and operational costs. In eligible tiers, Qaay may subsidize part or all of this Fee.

Multiple withdrawal requests can be submitted, provided the user’s available withdrawable balance is sufficient. However, withdrawal requests are processed sequentially rather than simultaneously within the platform’s transaction processing flow.

Tier does not determine whether a user can withdraw, but it may affect withdrawal-related benefits such as Fee discounts, priority handling, or promotional coverage.

Most withdrawals are processed automatically after platform validation. However, large transactions may require additional internal review for security, risk control, or regulatory compliance. Users may be asked to provide further verification or supporting information in these cases.

What Happens Next

After a user submits a withdrawal request, the process follows two main stages: platform-level checks and blockchain processing. Initially, the request enters a Pending state while internal validation occurs. During this phase, QAAY verifies that the withdrawal is permitted under the current account conditions (including sufficient available balance in Savings and any applicable account status checks).

Once the withdrawal is approved and broadcast to the blockchain network, an on-chain TxID (Transaction Hash) is generated. This identifier is the authoritative reference for tracking the transaction. It allows users to verify whether the network has accepted the transaction, whether it remains unconfirmed, or whether it has been included in a block and is accumulating confirmations. In blockchain systems such as Bitcoin, broadcasting a transaction does not guarantee final settlement. Each block added after inclusion increases the confirmation count and strengthens finality.

During the on-chain phase, processing time depends on the selected network and current network congestion. On Ethereum-like networks, transaction inclusion is influenced by gas Fees. If the gas Fee is set too low relative to network demand, the transaction may experience delays or remain unconfirmed for an extended period. This is one of the primary reasons a withdrawal may remain in a Pending state.

Transaction statuses are interpreted as follows:

• Pending: The request exists but is still being processed, either awaiting platform validation or blockchain confirmations.

• Completed: The transaction has been successfully executed, and the asset has been transferred.

• Failed: The transaction did not execute due to technical issues, network conditions, or invalid input, and the asset was not transferred.

• Cancelled: The request was stopped before finalization and did not affect the account balance.

If a withdrawal is delayed, check the transaction status in the Wallet/Transactions section and review the TxID in a blockchain explorer. Follow this investigation process:

• If a TxID exists and shows the transaction as unconfirmed, the delay is due to network processing.

• If a TxID exists and shows the transaction as confirmed, but the funds are not visible in the destination wallet, the issue is typically on the recipient side. For example, the receiving service may require a Memo / Tag, or the recipient may be monitoring a different network from the one used for the transfer. On networks such as Stellar and XRPL, memos or destination tags are essential for correct internal routing within exchanges or custodial systems.

• If no TxID exists, the transaction did not reach the blockchain stage. In this case, the issue is platform-side (for example, the request failed validation or the required security confirmation was not completed), and the user should review the request status rather than wait for network confirmations.

A critical limitation after submission is that once a transaction is broadcast to a blockchain network, it generally cannot be cancelled, reversed, or recovered by the platform. Blockchain systems treat submitted transactions as irreversible once confirmed. As a result, careful verification before submission and accurate tracking after submission are essential operational practices.

Best Practices

Following a few simple guidelines in QAAY Withdraw can help prevent errors and losses.

• Safe and predictable withdrawals rely on careful verification rather than speed. Treat each withdrawal as a final transfer and pause to verify details before submitting. Use paste or QR scanning to enter addresses, as manual typing increases the risk of errors. After entering the address, visually check the first and last characters, and confirm that the destination wallet supports the selected network. For large withdrawals, consider sending a small test transaction first to confirm receipt before transferring the full Balance. This is a recommended safety practice to reduce operational risk.

  Users should interpret the “Pending” status calmly and accurately. Pending usually indicates the transaction is undergoing platform checks or awaiting blockchain confirmation. Processing times vary with network congestion and Fees. Avoid submitting multiple withdrawals during delays; instead, trace the existing TxID and only submit a new request if the original clearly failed or was cancelled.

  If the withdrawal form requests a Memo/Tag, it should be treated as mandatory for that asset/destination context. Stellar documentation explains the memo field as an optional transaction attribute used to embed identifying or routing information, and XRPL documentation describes destination tags as off-ledger routing identifiers used by businesses to credit the correct customer account. Users should not assume that an address alone is always sufficient at custodial destinations.

  Account security is a direct part of withdrawal safety. Users should keep 2FA enabled and protect login credentials with a strong, unique password, because modern authentication guidance emphasizes multi-factor controls for actions that carry significant risk. A secure blockchain does not prevent unauthorized withdrawals caused by compromised account access; the account layer remains a primary security boundary.