Is the exchange automatic?
The request flow, live quote calculation, payment timer, notifications and blockchain checking are automated. Some requests may still be stopped or reviewed when risk controls require it.
Answers to common questions about the ExchangeWales request process.
The request flow, live quote calculation, payment timer, notifications and blockchain checking are automated. Some requests may still be stopped or reviewed when risk controls require it.
A public exchange shows trading-market prices from its order book. ExchangeWales shows a fixed service quote for the payment window, which can reflect liquidity, market movement protection, network and processing costs and operational risk.
An order book is the list of buy and sell orders available at different prices and quantities. The best displayed price may only be available for a limited amount.
Slippage is the difference between an expected market price and the average price available when an order is actually executed, often because of order size, liquidity or fast market movement.
The final service quote can include a market-movement and liquidity buffer for the payment window. This lets the request display a defined receive amount while the customer sends the payment.
Verification is required when configured volume thresholds are reached or when risk, jurisdiction, wallet activity or compliance checks require identity confirmation.
The visible limits apply per request. Daily, monthly and verification controls may also apply depending on current configuration and completed account volume.
You receive a request ID, fixed quote, payment wallet, QR code and payment timer. Send the exact asset on the selected network before the timer expires.
The configured launch networks for USDT are TRC20, ERC20, BEP20, Solana and TON. The exchange form shows the currently available networks and is authoritative.
Wrong-network payments can be permanently lost or require manual investigation. Always match the asset and network shown on the payment screen before sending funds.
Unpaid requests expire automatically. If you already sent funds after expiry, contact support with the request ID and transaction hash instead of creating a duplicate payment.
Processing depends on blockchain confirmation, network conditions and request checks. The account status is updated as the request moves through the workflow.
The sender wallet helps match the incoming blockchain payment to the request. The recipient wallet is where the output asset should be sent.
A centralized exchange can sometimes broadcast withdrawals from its own wallet infrastructure. Keep the request ID and transaction hash available if the observed sender address differs from what you expected.
You can cancel before payment. After funds are sent, cancellation may not be possible because blockchain transfers are normally irreversible.
The request may need additional review. Keep the request ID and transaction hash and contact support rather than sending another payment.
No. ExchangeWales provides an operational request workflow for supported digital assets and does not provide trading, tax, legal or investment advice.
A request can be rejected if payment cannot be matched, information is inconsistent, the wallet or network is unsupported, limits are exceeded, or risk controls require refusal.
Use the support button on the site and include the request ID. If you already paid, include the transaction hash and sending details.
Use the Supported assets and Networks pages or the exchange form. Availability can change, so the current exchange form is the final source before payment.