If you work in compliance or onboarding, or are just a massive compliance nerd like we are, you’ve probably noticed recently that a lot of the hardest problems don’t announce themselves clearly.

A business looks fine on paper. A website checks out. Onboarding goes through. And then, a few weeks later, something no longer lines up.

In this edition of Compliance Compass, we’ve pulled together a few patterns we keep seeing in KYB reviews and customer conversations — places where assumptions quietly break, and where teams are adjusting how they work to catch issues earlier, with less rework.

If you’re only going to read one thing…

In a world where fraudsters can spin up a “legit” website in ~10 minutes, website monitoring is becoming a KYB requirement, not a nice-to-have. If you only check a site at onboarding, you’re approving a snapshot, not a business.

There’s been seeing a clear shift over the last few months: more teams are asking for website monitoring, not just website checks. The reason is simple: websites are often where the risk shows up first, and it can change overnight.

Here’s the pattern showing up more often:

  • GenAI makes “credible” storefronts cheap and fast. A payroll or SaaS site with policies, pricing pages, and clean copy can be vibecoded in minutes.

  • Bait and switch is real. A business presents as low-risk during onboarding, gets approved, then switches the site to something higher-risk, like gambling for instance, after the account is live.

  • One-time KYB stops being enough. A website check at onboarding tells you what the business claimed to be that day. Monitoring tells you if the business stays consistent with what you approved.

So, what can you do about it?

A simple change in mindset should do the trick - place website intelligence alongside registry checks and ownership verification as a core KYB control, with monitoring built in. It’s a practical way to catch business model drift early, before it becomes a compliance incident or a partner problem.

If you’re building your 2026 onboarding stack, the question is no longer “do we check the website?” It’s “how do we know when it changes?”

What changed in the last few years that makes you confident the number of businesses will keep growing this fast?

The definition of a company changed. Five years ago, a company usually meant a store or a factory. Today, it can be a TikTok creator, a YouTuber, or someone freelancing from home.

Those people are not doing business in their own name anymore. They create an LLC. That LLC pays taxes. It interacts with banks and payment platforms like any other merchant.

We’ve already seen this play out over the last five years. And the same forces are still accelerating. That’s why I think the number of businesses on the planet will quadruple, or even five-x, over the next five years.

When you imagine that future, what actually changes for onboarding and KYB teams day to day?

Volume changes everything. When you have that many businesses coming in, you can’t treat KYB like a slow, manual exception process.

If onboarding takes days instead of hours, good customers will go elsewhere. And if you push fraud and risk checks later, you end up paying much more down the line. The economics flip. Fighting fraud after onboarding is always more expensive than stopping it early.

So the pressure is not just more businesses. It’s more businesses that expect speed, without regulators accepting weaker controls.

What’s the mistake teams will make if they underestimate how big this shift is?

If your KYB process depends on manual reviews and local knowledge in every country, it simply won’t keep up. You either build long queues and lose good customers, or you cut corners and create risk.

The teams that do well will be the ones that accept this reality early: most KYB has to be automated, consistently, across countries, with humans focused on the cases that actually need judgment.

We hit a new usage milestone

Today, more than 2,000 compliance officers worldwide use AiPrise to run their day-to-day compliance operations.

We built a new dashboard for a new year

We’ve rolled out a completely redesigned AiPrise dashboard, now live in beta, and the result of a year of customer interviews, hands-on usage insights, and many design debates about how compliance teams really move through cases. Our goal was simple: make it easier to see what matters, act faster, and stay in control as volumes scale.

We introduced exciting new features

Quieter queues, cleaner monitoring

You can now mute repeated false-positive AML updates by marking them as irrelevant. Once closed, those alerts stay closed, even when providers refresh the same record.

Smarter AML filtering before cases hit review

Teams can now use the AML agent’s relevance score directly in risk rules. Low-probability matches can be filtered automatically, so only meaningful hits reach analysts.

AiPrise alerts, now in Slack

Compliance work happens in real time, and for most teams, that means Slack. AiPrise alerts can now flow directly into the channels your team already uses, so the right people see cases the moment they need attention.

We introduced the Risk Rule Library

Onboarding isn’t just approve or reject. Risk levels drive controls. We launched the Risk Rule Library with pre-built, commonly used risk rules that teams can apply in minutes, covering things like EDD requirements, review frequency, monitoring intensity, and approval routing.

Fun fact: this feature was built during a TurboBuildDay using AI, with no manual code written.

Together, these updates focus on one thing: helping compliance teams move faster without losing signal, control, or trust.

Questions, pushback, or curiosity welcome. These patterns tend to show up differently in every team and every stack. If you want to compare notes or see how others are handling this in practice, just reply to this email. We read them all and promise to get back to you!

Keep Reading