How CBI Due Diligence Works: What Gets Checked (and How Bitcoiners Don’t Get Rejected)
- Adam Juchniewicz
- Feb 24
- 5 min read
Updated: Feb 28
Bitcoiners will spend a week optimizing fees to save $12 . . . and then walk into a citizenship-by-investment (CBI) process with the documentation habits of a guy who “definitely has it somewhere in his inbox.”
Let’s fix that.
CBI due diligence isn’t a vibe check. It’s not a sales call. It’s not a “pay the fee and receive passport” vending machine.
It’s a sovereign state asking a simple question:
Are you a risk we’d regret onboarding?

That’s it. That’s the game.
If you understand how the checks actually work, you stop treating the process like magic—and start treating it like what it is: a high-stakes compliance review with a human being on the other end deciding whether your file feels clean or questionable.
What due diligence is (in plain English)
CBI due diligence is the screening process governments use to decide whether to approve your application. Think of it like private banking onboarding—but with a passport at the end instead of a debit card.
Most programs run some version of:
identity and document verification
background checks across law enforcement and security databases
sanctions and watchlist screening
adverse media searches (yes, Google counts)
financial review: source of funds + source of wealth
And they don’t just do this once. It happens in layers: your agent, third-party firms, government units, sometimes more than one jurisdiction.
This is why people get delayed: not because they’re criminals, but because their file creates questions.
And questions create time.
What due diligence is NOT
Let’s kill the internet myths before they reproduce:
Not a “passport purchase.” You’re applying for approval. Payment doesn’t override “no.”
Not optional. Every serious program screens. The difference is how strict and how fast.
Not something you can outsmart. If your strategy is “hide,” you’re already losing.
Not anti-Bitcoin. But it is anti-unclear-money, anti-unknown-history, anti-chaos.
CBI doesn’t hate Bitcoin. It hates ambiguity.
Why Bitcoiners get tripped up
Bitcoiners tend to be legitimate, privacy-minded, and allergic to bureaucracy. That’s fine—until you meet a process designed by compliance people whose entire job is to assume worst-case scenarios.
The most common problem isn’t “bad intent.” It’s bad paperwork.
names spelled three different ways across documents
residency history that’s true but undocumented
wealth that’s real but poorly explained
money movement that’s clean but hard to prove
online history that creates the wrong impression
CBI due diligence doesn’t reward cleverness. It rewards clarity.
What they actually check
Here’s the part people want as a simple checklist. Real life is messier, but the categories are consistent.
Identity + document authenticity
They want to know:
you’re the same person across every passport, ID, and certificate
your documents are authentic
your timelines don’t contradict each other
Most “issues” start here. One mismatch leads to follow-up questions. Follow-ups lead to delay. Delays lead to stress. Stress leads to people sending sloppy “explanations.” That leads to more questions.
Keep it clean from the start.
Criminal and security screening
They check for:
criminal records (obvious)
open cases or serious allegations (depends on jurisdiction)
warrants, travel flags, or international database hits
Here’s the blunt truth: if something exists, assume it will surface. The smartest applicants don’t “hope it won’t show.” They disclose properly and document properly.
Sanctions, watchlists, restricted parties
This isn’t personal. It’s defensive.
Governments screen:
sanctions lists
watchlists
high-risk jurisdictions and counterparties
Bitcoin angle: you can be totally clean and still get questions if your funds touched the wrong ecosystem at the wrong time. The fix isn’t panic. The fix is documentation and a coherent narrative that makes the reviewer’s job easy.
PEP status (politically exposed persons)
PEP doesn’t mean “bad.” It means “higher scrutiny.”
If you (or close family/associates) have political exposure, expect:
more questions
more documentation
slower review
The mistake is trying to minimize it. The correct move is disclosure + context + evidence.
Adverse media and reputational risk
This is where people get blindsided.
They will search your name and related entities. They will look for:
lawsuits and disputes
accusations (even if unproven)
controversial business activity
weird headlines and “crypto scandal adjacency”
If your name shows up online in a way that could be misread, you don’t argue with the internet. You build an explanation packet that’s calm, factual, and backed by documents.
Source of Funds vs Source of Wealth (the big one)
These are not the same thing.
Source of Funds (SoF): Where the specific money for the CBI investment comes from. Source of Wealth (SoW): How you became financially capable overall.
Bitcoiners often have a real SoW story but present it like this:
“I bought BTC years ago. I held. I’m up.”
That may be true. It’s also not a file.
A strong CBI file ties your wealth story to records:
exchange statements (where applicable)
bank records for on/off ramps (where applicable)
business income records (this is where an LLC helps)
tax filings where relevant
sale events and documentation where relevant
CBI isn’t asking you to dox yourself for fun. It’s asking you to prove your money isn’t criminal, sanctioned, or reputationally radioactive.
A quick word about the Wyoming LLC (because people misuse it)
A Wyoming LLC is a powerful tool for operations and structure. It can help you:
document legitimate business activity
separate business income from personal life
build clean contracts, invoicing, and accounting
present a coherent story that reviewers can follow
What it cannot do:
It cannot “hide you” from due diligence.
CBI due diligence looks through entities to real control and beneficial ownership. If your plan is to use an LLC like invisibility tech, congratulations—you’ve invented a rejection engine.
Use structure to reduce chaos, not to manufacture mystery.
What gets people rejected (or delayed into oblivion)
Rejection is often death by a thousand cuts. The most common triggers are:
inconsistencies across documents or timelines
“missing” details that look like omissions
unclear provenance of crypto funds
exposure to high-risk counterparties with no explanation
adverse media with no context packet
agents who rush submissions and “wing it”
Governments don’t approve “confidence.” They approve coherence.
How to avoid rejection (minimum viable strategy)
You don’t need a compliance department. You need discipline.
Start with a pre-screen mindset: before you submit anything, ask:
Can a skeptical reviewer understand my identity, history, and money without guessing?
If the answer is no, fix it before the file leaves your hands.
Then build a simple “proof packet”:
identity documents + name changes (if any)
residency history support (addresses, permits, records)
business documents (if relevant): formation docs, ownership, contracts
SoF/SoW evidence: statements, records, and key events
a short written narrative that ties it together
Not a novel. Not a manifesto. A clean explanation.
Your goal is not to overshare. Your goal is to make the case boring.
The Bitcitizen take
Bitcoin taught you the right lesson: verification beats trust.
CBI due diligence is the same principle—just pointed at your identity and your wealth instead of a block header.
If you’re legitimate, you don’t “beat” due diligence. You prepare for it. You remove ambiguity. You document the story. You submit a file that doesn’t create questions.
Because in CBI, questions are expensive.
And the cleanest files—like the best security setups—don’t rely on luck. They rely on structure.
Ready to Start Your Second Citizenship Journey?
Bitcitizen helps Bitcoiners navigate CBI due diligence with clean documentation and expert guidance. Explore our 21 CBI service to learn how we prepare your file, or check our FAQs for answers to common questions. Book a free consultation to get started.
_edited.jpg)



Comments