The best KYC is the one you don’t repeat

KYC is often talked about as a toll you pay before reaching the product. I see it the other way round: it is one of the screens a person walks through most often and, quite often, the worst designed. My founder’s guide to KYC, KYB and AML explains what the acronyms mean. This piece is about something else: what compliance looks like when you design it as part of the product rather than as paperwork that runs behind it.

Don’t ask for the same thing twice

When a person has already provided a document, asking again is a product defect, not a requirement. At Bennu we keep what we receive in the member’s file and, when the flow allows it, we answer the provider with that information before asking the member again. I find that principle more important than any progress bar.

It has a limit worth saying out loud: the provider keeps its own rules and may require an update, for example if a document has expired. In that case, what is owed is an explanation of exactly what is missing and why. The aim is to reduce repeated work, not to promise there will never be another request.

Ask before, not during

The most expensive mistake is asking late. If a platform takes an interest in the origin of funds when the transfer is already on its way, the money sits still while somebody gathers papers in a hurry. That is why we try to collect activity, structure and expected flows at sign-up, and to check they are still current before a larger operation. A prepared file can still need new checks, but they are much easier to answer when nobody has a clock on them.

Say who decides

“Verified” at one provider is not “approved” at another. Evidence, each provider’s decision and account eligibility are different states, and the product should show them separately. I told it through two real, anonymized cases in One provider’s “Approved” isn’t another’s. When something is still under review, the app has to say so, and say what comes next.

Invitation-only access is also a product decision

Access to Bennu is by invitation and after a review. From outside it can look like a barrier; from inside it is a way of growing carefully: it is easier to explain a wait at the start than a hold later. It has an obvious cost, which is that some people wait, and I do not intend to hide it. But I prefer that cost to opening the door wide and discovering each client’s structure when money is already moving.

Somebody has to read the file

Automated rules are good for filtering. They are not good for understanding a structure with the company in one country, the owner in another and the customers in a third. That structure is not a problem in itself; what is hard is for the reviewer to understand it quickly. A complex file deserves someone connecting the articles of formation, the contracts and the source of payments. That does not remove the possibility of holds, new requests or an unfavorable decision, which is why we do not promise it.

What I don’t promise

I do not promise approvals or the absence of alerts. I promise, as a design goal, that the person knows where they stand and what comes next. The measure I care about is how many people need to write to us to find out, and I want that number to keep falling.

Bennu is a self-custody platform, not a bank; verification and fiat services depend on providers and on jurisdiction. You can read how we treat identity and anti-money-laundering on Bennu’s compliance page. If it fits, you can request access; requesting it does not imply approval.

I write as a co-founder of Bennu. Sumsub appears as a provider and public source; it does not sponsor or endorse this article. This text is informational and is not legal, regulatory or financial advice.

Sources

• Bennu: large volumes and preparing an understandable file.
• Bennu: anti-money-laundering and identity verification.
• Sumsub: how business verification works.