The KYB Compliance Information Packet explains what a solution provider or NBFI will ask for when onboarding a licensed MSB, a crypto business, or a general fintech, across US, Canada, UK and EU entities. The framing point: the provider isn't just collecting paper — it's building a file its own compliance officer must be able to defend in an audit or regulatory exam, possibly years later.
The failure mode is quiet, not dramatic: "incomplete, inconsistent, or evasive packets do not get rejected loudly. They get slow-walked, deprioritized, and quietly dropped." Consistency is where most packets fail — names must match across the certificate, bank statements, website, AML policy and application down to punctuation and suffixes, and any undisclosed gap is treated as concealment rather than an oversight.
What the guide covers:
- Registry extracts and good standing certificates that must be three to six months old at most, with certified true copies before go-live
- A signed ownership structure chart covering every trust, nominee and SPV — the standard UBO threshold is 25%, though crypto businesses should expect 10%
- A source of wealth narrative, distinct from source of funds, required per beneficial owner
- Why an unlicensed or exempt business needs a written regulatory status memo rather than a blank section
- A flow of funds diagram and narrative that "answers half the questions a compliance analyst has"
- Nine named gaps that cause delay, from stale certificates to a visibly templated AML policy
A KYB packet is not a one-time artifact — reviews run annually for higher-risk clients and every two to three years otherwise.