Contact Exchange No KYC
Use this page for questions about an exchange order, a technical issue, a content correction or a business inquiry related to exchangenokyc.io.
For the fastest review, include the information relevant to the issue without sending sensitive wallet credentials.
Exchange Order Support
If the question concerns an active or completed exchange, include as much of the following as you have available:
order ID;
send asset and receive asset;
source and destination networks, where applicable;
transaction hash for the deposit;
amount sent;
approximate time the deposit was broadcast;
current order status shown on the site;
a short description of what you expected to happen and what happened instead.
Do not send a wallet seed phrase, private key, password or recovery phrase. Those credentials are not required to identify or review an exchange order.
If the transaction is still pending or the order has stopped progressing, first check the delayed crypto swap guide. For questions about blockchain confirmations, see crypto exchange confirmations.
Wrong Amount, Refund or Network Questions
Different problems need different information.
| Issue | Useful details to include |
|---|---|
| Wrong amount sent | Order ID, expected deposit amount, actual amount, transaction hash |
| Deposit not detected | Order ID, source network, transaction hash, amount sent |
| Refund question | Order ID, current status, refund address if already requested by the order flow |
| Network mismatch | Asset, network selected in the order, network actually used to send |
| Payout question | Order ID, destination asset/network, receiving address, current status |
For background before contacting support, see what happens when the wrong amount is sent and how crypto exchange refunds work.
Technical and Website Issues
For a form, page or interface problem, describe:
- the page URL;
- the action you were trying to complete;
- the device and browser used;
- the error text, if one was shown;
- the approximate time the problem occurred.
A screenshot can be useful when it contains no private wallet credentials or other sensitive information.
Content Corrections
Exchange pages and Wiki guides are maintained separately so that each page owns a specific topic. If you notice an outdated statement, broken internal link, unclear network explanation or other content issue, send:
the page URL;
the exact heading or paragraph;
the correction you believe is needed;
supporting context, if available.
Content feedback is especially useful for route-specific network checks, address-format explanations and Wiki guidance that may change as exchange infrastructure evolves.
Partnerships and Business Inquiries
Use the business contact channel for partnership proposals, liquidity or infrastructure discussions, integrations, content cooperation and other non-support inquiries. Include the company or project name, website and a concise description of the proposal.
Contact Details
Support email: [CONFIRM BEFORE PUBLICATION]
The working master currently lists [email protected] as a proposed address, but the mailbox must be confirmed before this page is published.
Information submitted through support or business communication may be processed as described in the Cookies & Privacy Policy.