Myxa (myxa.cc) is a veteran of the Russian-language crypto exchanger scene, built around the ruble/hryvnia/tenge ↔ crypto combo, running on autopilot 24/7 with human support on weekdays. According to BestChange, the domain is about 5 years and 10 months old (as of October 2026), the service has been listed on the monitor for 4 years and 11 months, has racked up 8,483 reviews and 272 financial claims over its entire history (all of them resolved), and shows stated reserves of $407,732. The claimed place of registration is Cyprus, but no legal entity is named anywhere in the public paperwork.

The exchange directions cover a wide fiat footprint across the CIS: cards from Russian banks (Sberbank, T-Bank/Tinkoff, VTB, Alfa, Gazprombank, Promsvyazbank, Otkritie, Raiffeisen, MIR, SBP), Ukrainian banks (Global24, Privat24, Monobank), Kazakh banks (Kaspi, HalykBank, Alatau, ForteBank, Eurasian), European EUR cards, plus Volet.com (Advcash). On the crypto side there's USDT (TRC-20/ERC-20/BEP-20), BTC, ETH, XMR, TRX, USDC. For the USDT→RUB pair, the rate at the time of checking was around 84.5 ₽ per coin, with a minimum of 35 USDT.

Technically, exchanges run fully automatic — once you've paid, the system checks the transaction itself and sends the payout, no need to type "I've paid" into the chat. Operators step in for non-standard cases and work Mon–Fri, 10:00 to 19:00 (per the main page; the contacts page says Mon–Fri 10:00–23:00 MSK with a "flexible schedule" on weekends — a small mismatch, but the fact that it exists at all is telling).

Regulatory status: Cyprus, minus the specifics

BestChange lists the country as Cyprus, but neither the site, nor the FAQ, nor the terms (recovered via cache and forum discussions) disclose a legal entity, a license, or a regulator. The service presents itself simply as "Myxa.cc" — a trade name with nothing identifiable behind it. That's standard practice for unlicensed exchangers, but it means the client has no formal counterparty to take claims to outside the monitors' arbitration.

AML approach: a 60% threshold and automatic checks

The main page spells it out: "The sending address undergoes an AML check. If AML is above 60%, the exchange will be halted and the funds returned minus a fee". That's a transparent, up-front mechanic — a plus. You can pre-check your address through third-party services, and the "Check address before exchanging" button on the site even takes you to an external AML tool — a gesture that lowers the risk of getting frozen out of the blue.

That said, "minus a fee" is an open-ended phrase: the size of the deduction isn't specified on the main page, and judging by the discussions, the service decides it case by case.

KYC/verification: a card photo, no passport — but video from your banking dashboard "on demand"

This is where Myxa runs a two-tier system, and it deserves a close look.

Tier 1 — card verification (mandatory for exchanges involving Russian cards). You register, add your card in the "Your accounts" section, and take a photo of the card with the site open in the background — so the number of the card you'll be paying from is readable. For virtual cards, it's a photo of your internet banking with the card number against the site's background. No passport, no selfie with a document — a moderate level of data collection, in line with what other exchangers in the segment do.

Tier 2 — "payment confirmation" (discretionary). And here's where it gets interesting. Clause 9.4 of the terms (quoted by the Myxa admin in a dispute with a client on BestChange) reads: "The Myxa.cc service has the right to request from the user all evidence necessary to verify and identify the payment (TxID, bank receipt, PDF statement, video recording from the bank's personal dashboard, as well as identity verification). The user has 3 business days from the date the order is created/paid to provide all requested data. Otherwise, the funds will be lost".

Let's break down what looks like a red flag here:

— Clause 9.4: "funds will be lost" after 3 business days. That's the harshest wording in the entire documentation. Not "frozen pending clarification", not "returned minus a fee" — specifically "lost" i.e., formally forfeited to the service if you don't hand over what they asked for. In a fresh case on BestChange (September 2026), a client named Zinaida ran into exactly this scenario: she paid 15,000 ₽ from T-Bank, provided a PDF receipt, but the service claimed "the payment system does not confirm receipt" and demanded a video recording from her online banking dashboard. The client refused (understandably not wanting to show her banking account and her voice), the claim sat in limbo for two days, and then the video was provided after all and the order went through. The "lost" wording paired with the right to demand video from someone's personal banking dashboard looks like a discretionary pressure tool: the service decides on its own when a receipt is "enough" and when it needs full visual access to the client's banking history.

— Clause 9.4: "as well as identity verification". The list of possible demands includes not just TxID, receipts, and video, but also "identity verification". That's a wide-open loophole: the scope of verification isn't defined in advance and is set by the service. Unlike exchangers with a transparent KYC tier (up to X amount — no verification, above it — video with a passport), here you can't know upfront what they'll ask of you.

— Clause 8.5: no going back after "Completed". The FAQ states it outright: once an order gets "Completed" status, "per Service Rules clause 8.5, the funds cannot be returned". In other words, all responsibility for getting the recipient's details right falls on the client, and if the payout lands on someone else's card because of a typo or a compromised account — there's no way to get it back.

— Clause 4.7: the service doesn't check the legality of ownership. From the terms (visible in search results): "The Myxa.cc service does not verify the user's right of ownership, or its legality, with respect to electronic currencies and/or cryptocurrencies". On the one hand, that's honest. On the other, it shifts all the AML responsibility onto the client: if your funds are "dirty", the problems are yours, not the service's (at least until a payment system blocks something).

Hours and timeframes: numbers worth reading closely

The main page says: "Standard payout time to bank cards is 10 to 90 minutes. In rare cases, due to bank regulations, crediting may take up to three days — that's beyond our control. The payout may be split into several payments". Split payouts and up to 3 days for fiat to land are simply the reality of working with Russian banks through chains of intermediaries, but clients should understand: fast auto-exchange is the norm, not a guarantee, and when something "non-standard" comes in, the manual cycle with evidence requests kicks in.

The pluses on the compliance side

To be fair: the AML threshold is announced upfront (60%), the address pre-check tool is available before you even create an order, the card photo with the site in the background is moderate verification without a passport for the basic case, and the structure of the rules (TxID, PDF receipt, statement) does look like an attempt at coherent compliance. The problem isn't the existence of AML — it's the discretionary level of requirements and the "lost" wording.

Checking reviews and monitors

BestChange is the main data source, and overall it's positive. Out of 8,483 reviews, the overwhelming majority are short thank-yous from repeat customers: "I exchange here all the time. Always everything good, fast and smooth!", "USDT — VISA RUB literally in a couple of minutes", "The guys work cleanly as always, even on weekends everything runs like clockwork". All those "as always", "yet again", "I always use these guys" are a marker that the service has a loyal base — which is unusual for scam projects that live for a few months.

But there is a negative side, and it clusters around one pattern. The fresh September 2026 cases (Zinaida, Anatoly, Artur on BestChange) show a recurring scenario: fiat payment not confirmed by the payment system → request for video from the online banking dashboard → funds frozen until it's provided → (in most cases) payout after the video or after escalation through a BestChange claim. Anatoly's case is telling: "The funds were only paid out after I filed a claim". So the money does come back in the end, but the service can use formal grounds to stall, and that creates operational friction clients should factor into their expectations.

Antiswap has logged 534 negative reviews on other monitors — an aggregated figure over the service's ~6-year history. Ratio that against 8,483 reviews on BestChange and an unknown number of positives on other platforms, and the negative share looks noticeable but not dominant.

The bits.media thread (topic 181762, March 2021) is the oldest red flag in the public domain. The thread opens with the headline "Careful, dubious! Myxa.cc — electronic currency exchange" and the author cites order 6588021, which Myxa.cc itself confirmed as "Paid" but never processed. Important: the thread is five years old, and since then the service hasn't vanished — quite the opposite, it's accumulated thousands of reviews and nearly five years of uninterrupted presence on BestChange. The thread itself contains positive reviews too ("I personally want to say this exchanger is top-notch... very quick"). It looks like an isolated conflict the author tried to inflate into a public warning, but it never snowballed into a wave of similar complaints.

Bottom line

Myxa looks like an exchanger with a genuine track record, a live customer base and working automation — which already sets it apart from the "here-today-gone-tomorrow project with a slick landing page" category. Six years on the market, thousands of reviews from repeat clients, a transparent AML threshold, no waves of mass scam complaints — all factors in its favor.

However, the service's compliance approach is built on discretion: the service decides when your payment is "unconfirmed", whose confirmation is good enough, and what exactly you have to provide. The wording of clause 9.4 ("funds will be lost" after 3 business days if you don't comply) is a legal instrument that, in a disputed scenario, gives the service free rein, and the combo of "PDF receipt rejected → now we need video from your bank dashboard" shifts the burden of proof onto the client and creates the risk of being forced to disclose data they may not be comfortable sharing.