Nils Silinevics
Partner · AML & Crypto Compliance · Former FIU Investigator
You've had your KYC rejected after multiple attempts on FixedFloat. FixedFloat is a non-custodial swap service based in distributed (no single HQ), regulated under varies by user jurisdiction. Unlike traditional exchanges, FixedFloat can hold your funds during AML checks even though you never created an account. The service uses Crystal Blockchain for transaction screening. FixedFloat holds transactions when Crystal Blockchain flags source addresses with high risk scores, requiring source-of-funds proof before releasing funds. You submit your ID documents and selfie, but receive a rejection notification. The rejection may not explain why — the platform often just says 'verification failed' without specifics, leaving you to guess what went wrong.
FixedFloat holds transactions when Crystal Blockchain flags source addresses with high risk scores, requiring source-of-funds proof before releasing funds. FixedFloat suffered a major hack in 2024 that compromised their operations and eroded user trust. The hack also affected their compliance processes — they became more aggressive in holding transactions, partly to compensate for the hack losses and partly because their compliance infrastructure was disrupted. This background matters because it shapes how FixedFloat handles compliance — and how we approach resolving your case.
The compliance framework: FixedFloat operates under varies by user jurisdiction, overseen by unclear (no single jurisdiction). Their compliance infrastructure uses Crystal Blockchain for blockchain analytics and manual for identity verification. FixedFloat is known for fixed-rate and floating-rate crypto swaps, Lightning Network support, serving traders who want predictable swap rates and Lightning Network users — and their compliance team is calibrated to flag deviations from typical user behavior in that segment.
What triggers kyc failed on FixedFloat:
Real case — post-hack paranoia: After the 2024 hack, a user's ongoing swap on FixedFloat was held indefinitely. FixedFloat's support — already disrupted by the hack — didn't respond for 3 weeks. The user's 1.2 BTC was stuck. We submitted a legal demand citing consumer protection obligations and the fact that holding user funds indefinitely without explanation constitutes conversion (unlawful detention of property). FixedFloat released the funds within 5 days of receiving the legal letter.
What FixedFloat requires to resolve this: Depending on the trigger, FixedFloat may ask for government-issued photo ID (verified through manual), proof of address (utility bill or bank statement within 3 months), identity verification process (exchange statements, bank records, payslips, tax returns, or business documents), detailed transaction explanations with on-chain evidence, and in some cases a video verification interview. The challenge: FixedFloat rarely tells you which specific trigger caused the kyc failed, so you're guessing at what documentation to provide — and each rejected submission makes the next one harder.
Our approach is specific to FixedFloat: FixedFloat's post-hack compliance posture is defensive and uncommunicative. Their distributed structure (no clear HQ) makes regulatory escalation harder — there's no single regulator to complain to. We use legal pressure focused on the conversion claim (unlawful detention of property) rather than regulatory complaints. FixedFloat's lack of clear jurisdiction actually works in our favor — they can't invoke a specific regulatory framework to justify indefinite holding.
KYC Failed on FixedFloat — our strategy: We analyze the likely failure reason — document quality, name mismatch, expired ID, nationality restriction, or liveness check failure — and prepare a clean resubmission package that addresses the specific issue.
The submission that matters: Instead of submitting through FixedFloat's standard support channels (where you'll get automated responses or generic template replies), we prepare a professional legal submission — a structured compliance package with a cover letter from a Swiss law firm citing unclear (no single jurisdiction) obligations and varies by user jurisdiction. FixedFloat's compliance team processes legal submissions differently from regular user tickets — they're assigned to senior compliance officers, not support agents, and they bypass the automated response loop that delays most cases by weeks.
When standard compliance isn't enough: Some situations fall outside the normal compliance flow — inherited crypto holdings, accounts registered under another person's name, unprovable source of funds through conventional documentation, or cross-jurisdictional complications where your residence, the exchange's jurisdiction, and the fiat banking path all differ. If that sounds like your case, our complex cases practice handles scenarios that other firms decline.
Further reading: our guide on what to do when a crypto exchange freezes your account covers the documentation and legal strategy in more depth.
We identify why KYC failed: expired/damaged ID, photo quality, name mismatch, nationality restriction, address verification gap, or liveness check issue. {p_name} rarely tells you the specific reason — we find it.
We prepare a clean resubmission: correctly formatted ID photos (no glare, full frame, valid expiry), matching name across all documents, proof of address within 3 months, and if needed, a legal name-change document or translation.
We resubmit through {p_name}'s verification team with a legal cover letter explaining any discrepancies (name variations, dual citizenship, transliteration issues). We cite {regulator} KYC requirements.
KYC verification passed — full account access restored. We advise on keeping documents current and avoiding KYC expiry issues on {p_name}.
The hack disrupted FixedFloat's operations, including their compliance and support teams. If your swap was held during or after the hack, response times are significantly longer than pre-hack. FixedFloat has not been transparent about the hack's full impact, which makes resolution harder. We use legal pressure (specifically, a demand for release of property) to force FixedFloat to process held transactions, regardless of their operational disruptions.
FixedFloat operates without a publicly disclosed headquarters, which creates regulatory ambiguity. This is both a problem and an advantage: there's no single regulator to complain to, but FixedFloat also can't invoke a specific regulatory framework to justify indefinite fund holding. We use general legal principles (conversion, unjust enrichment) rather than specific regulatory complaints.
Common reasons include: expired or damaged ID document, document photo too blurry or with glare, selfie doesn't match the ID photo, name on account doesn't exactly match the ID, nationality not supported, or liveness check failed. The platform rarely tells you which specific reason caused the rejection.
Most platforms allow 3-5 KYC attempts. After that, your account may be permanently restricted. Each failed attempt makes the next one harder because the system flags repeated failures as suspicious. If you've already failed twice, we strongly recommend professional help before your next attempt.
Yes. Platforms operate under regulatory restrictions that may prevent them from serving nationals of certain countries (typically sanctioned jurisdictions). Even if you're a resident of an allowed country, your nationality can trigger a refusal. We help dual nationals navigate this by demonstrating their primary jurisdiction and compliance with applicable regulations.
Tell us what KYC documents were rejected and what reason FixedFloat gave. We respond within 6 hours.