Interface Language and Support Language Are Not the Same Thing
A practical community guide
The strongest form of transparency is procedural. It tells the user what happens first, what information is required, when the network takes over, and what record should be kept until the exchange is complete. Separate the languages visible in the interface from the languages the Contacts page says the support team can use. This article keeps the discussion close to the current DEX.fo workflow rather than extending the feature into claims the source material does not support.
Why this topic matters
Interface Language and Support Language Are Not the Same Thing matters because a crypto transfer becomes difficult or impossible to correct after broadcast. The useful question is therefore not only whether the feature sounds private, fast, or convenient. The better question is where it changes the order, which information the user must verify, and which parts remain dependent on a blockchain or an external wallet. Choose the interface language that helps you check the order, but use a listed support language when requesting assistance.
What the documented flow says
This matters because The current interface presents multiple language options, including English, Russian, German, Spanish, French, Polish, and Chinese. The point should be checked on the live order page rather than remembered from an earlier transaction.
A careful reading shows that The Contacts page says English is preferred and also mentions German, Spanish, Russian, and Ukrainian for communication. That detail becomes most important before the deposit is broadcast, while the user can still correct the order setup.
In practical terms, A translated interface does not automatically mean full support coverage in that language. It also gives support a clearer record if the order later needs to be reviewed.
For the person creating the order, For complex order issues, clear written details and the order reference reduce misunderstanding. The mechanism is more useful than a broad promise because it can be observed and verified.
Where it fits in the order
A DEX.fo order begins with the exchange pair and the live route conditions. The user then provides a destination address and a required refund address, reviews the displayed minimum and maximum, and chooses an available execution mode. The service generates a one-time input address for that order. After the expected amount reaches the required confirmation state, the route is processed and the output is sent to the destination address.
This sequence is short, but the fields are not interchangeable. The destination address receives the purchased asset. The refund address is the return route for the asset being sent and cannot be changed after order creation. The one-time input address is the order-specific place where the deposit is made. Keeping those three roles separate prevents a simple interface from becoming a source of avoidable confusion.
Practical checklist
- Never share a seed phrase, private key, password, recovery phrase, or wallet backup.
- Open dex.fo directly and verify the domain before using any support or Onion link.
- Check the asset and network together, especially when the same ticker exists on more than one chain.
- Review the destination address, refund address, live limits, selected mode, and calculated receive amount.
- Send only the amount expected by the order and retain the order reference plus relevant transaction IDs.
- Use the SimpleX link on the official Contacts page or info@dex.fo for an order-specific support request.
Limits of the claim
Timing estimates are not guarantees. The incoming blockchain must confirm the deposit, the route must be processed, and the outgoing blockchain must confirm the payout. Each stage can move at a different speed.
Takeaway
Choose the interface language that helps you check the order, but use a listed support language when requesting assistance. Follow the route, verify the details, and keep the order record until the payout confirms.
Website: https://dex.fo