Over on BitcoinTalk, user egor994 started a thread about a transfer stuck on the exchange service Myxa.cc, which he'd found through the BestChange monitoring site. We're talking about six transfers of 50 XMR each, sent from KuCoin back in August 2025: five went through, but the sixth request (number 6588021) never got confirmed by the exchanger. According to the OP, he's got an official KuCoin withdrawal PDF report dated August 28, 2025, with the tx hash 5ea87ecbf10e87f8ef120c35f108e41239e2a71defba30e415a90ccdcdda7632 and a SUCCESS status, and the hash actually opens up fine in the public Monero explorer. He posts the recipient address shortened, the full one is in the thread. Separately, egor994 notes that the exchanger stopped replying to emails on October 1, 2026, and from a certain point on the monitoring site is basically answering on its behalf.

Per his version, BestChange confirmed in correspondence that the payment address belongs to a processing pool called merch.elpay.to, but said it isn't the wallet operator and doesn't have access to the funds. At the same time, the exchanger asked for a secret transaction key, which KuCoin refused to hand over, citing security risks — and the OP says he's got a support reply screenshot to prove it. The "check" itself, he says, was offered on these terms: about 3,400 USDT to take the server out of production and restore the old infrastructure for investigation, OR around $100 once the server is decommissioned in the normal way. On top of that, egor994 claims the exchanger publicly presented itself as a licensed Lithuanian VASP with €125k capital, whereas the Bank of Lithuania, responding to his inquiry, said no such entity is registered in the country; later he got a reply from the Lithuanian Financial Crime Investigation Service under the Ministry of Interior (ref. No. 25-16431) saying that between August 1 and December 31, 2025, the service didn't appear in the VASP registry. All of this should be taken as one side of the dispute — he promises to hand the supporting documents over to the regulators.

A BestChange rep under the handle Best_Change posted a detailed response on October 30, 2026. Per the rep, the order page had a warning that you need to make sure beforehand the sender can provide the data needed to verify the transaction, including the view key, and that the user ignored that warning by sending the funds straight from a centralized exchange; the fact that funds were sent from an exchange, the rep argues, doesn't yet equal the receiving side actually getting the payment. The monitoring site claims they've already run the check several times, that the user's other five transfers are visible in the system and were either processed or returned, while the disputed 50 XMR simply isn't found. Separately, Best_Change pushes back on the "$3,400 for a check" framing: per his version, neither the monitoring site nor the exchanger is asking for any money right now, and those figures were only mentioned as possible technical options for a deeper investigation. He also says the OP didn't actually contact the merch.elpay.to processing — he contacted a different company, elpay.io, and used its reply as an argument. The monitoring site also notes the exchanger has been listed with them for about five years, they see no reason to consider it a systematic scheme, but they're ready to reopen the case if new technical data shows up.

egor994 insists it was the monitoring site itself that gave him the merch.elpay.to link, that the site at that address is unreachable, and that they never handed him any contacts for the processor despite several requests — which is exactly why he ended up emailing elpay.io. He also asks them to show the logs, screenshots, and correspondence behind their conclusion that the funds never arrived, asks what the verification mechanism would even be if he did pay up, and reminds them he's still waiting on the processor contacts they promised him by email.

What the commenters think

Murat sympathized and asked what the monitoring site had actually done, suggesting the OP use cross-chain services like THORChain in the future. The Cryptovator noted that BestChange had helped him out for free in a similar situation before, and advised going the legal route and not paying anything, so as not to lose money twice. decodx was surprised the monitoring site had effectively taken the exchanger's side and asked for more details on the view-key request. RGBTC speculated that the real cost of a check is around $100, and that the $3,400 figure roughly matches the size of the loss itself. NotATether tore into the monitoring site and recommended an alternative catalog — being upfront that it's his own service.

Per RDAP, the domain myxa.cc was registered on March 30, 2012, the registrar is Cloudflare, it's renewed through March 2027, and DNS is handled by Cloudflare. Meanwhile, the exchanger's card on BestChange lists its age as five years and ten months, country as Cyprus, with 8,488 reviews, 272 financial claims, and declared reserves of around $412k. The address merch.elpay.to doesn't respond as of this writing, which lines up with the OP's complaint about the processor site being down. The tx hash egor994 references does belong to the public Monero ledger, but you can't confirm the recipient from it without the view key from the sender's side — and that's exactly the technical dead end the whole dispute revolves around. There's also an earlier BitcoinTalk thread out in the open with a similar description and the same exchanger mentioned, so it might be a related or even identical case.

This is an interim read, since the fact of the funds not arriving hasn't been independently confirmed by either side, but the verifiable parts of the story (the processor being down, the exchanger ghosting, the mismatch with Lithuanian regulator data) look concerning enough that you shouldn't be sending big sums through this service or paying for any checks upfront.