Notifications
Clear all
Topic starter
10/06/2026 10:32 pm
TL;DR: Compliance is shifting from a separate control layer to a platform-native governance requirement that teams cannot treat as optional, according to Sumsub. Monavate’s integration of Sumsub verification into its API-driven onboarding flow embeds KYC, liveness checks, sanctions screening, and ongoing monitoring directly into regulated payments operations, with support for more than 220 countries and territories and 14,000 document types.
NHIMG editorial — based on content published by Sumsub: embedded KYC, document verification, and monitoring in Monavate's onboarding flow
By the numbers:
- Sumsub's verification coverage spans more than 220 countries and territories.
Questions worth separating out
Q: How should payments teams govern KYC when it is embedded in an onboarding platform?
A: They should treat embedded KYC as part of the regulated identity control plane, not as a separate vendor feature.
Q: Why do native verification flows matter in regulated onboarding?
A: Native verification matters because it reduces handoffs and keeps identity evidence inside the same system that approves the customer.
Q: What do teams get wrong about ongoing monitoring after onboarding?
A: They often treat screening as a one-time onboarding checkpoint instead of a recurring identity control.
Practitioner guidance
- Define the onboarding identity control boundary Map where KYC, liveness, sanctions screening, and monitoring begin and end in the customer journey.
- Require auditable evidence for every verification decision Ensure the onboarding flow records document checks, deduplication outcomes, screening hits, exception decisions, and reviewer actions in a form audit teams can reconstruct later.
- Treat ongoing monitoring as a lifecycle control Link sanctions, adverse media, and deduplication signals to recurring review processes so customer risk can be reassessed after onboarding, not only at approval.
What's in the full article
Sumsub's full product post covers the operational detail this post intentionally leaves for the source:
- The exact verification capabilities available inside MonavateOne for programme managers who need implementation detail
- The full list of supported document and screening checks, including the operational scope behind each control
- The geographic rollout context for the UK and EEA and what future expansion means for programme design
- Direct commentary from Monavate and Sumsub on how the integrated flow is intended to support regulated payments operations
👉 Read Sumsub's post on embedded KYC and verification in MonavateOne →
Embedded KYC in onboarding flows: what it means for compliance teams?
Explore further
11/06/2026 2:36 am
Embedded verification turns onboarding into an identity governance boundary. When KYC, document verification, and ongoing monitoring move into the platform layer, programme managers stop owning a separate verification stack and start governing a control plane. That changes the accountability model because compliance evidence now depends on how the platform captures, stores, and enforces identity decisions. The implication is that payments onboarding should be treated as a governed identity process, not a front-end workflow.
A few things that frame the scale:
- 92% of NHIs expose NHIs to third parties, raising concerns about supply chain security, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: How can organisations prove their onboarding controls are working across jurisdictions?
A: They need evidence that the same verification logic, exception handling, and review process apply consistently across every region they serve. Proof comes from audit logs, documented policy rules, and repeatable decision trails, not from a claim that the platform is compliant. Cross-border scale only works when the control model remains traceable.
👉 Read our full editorial: Embedded KYC in payments onboarding changes compliance governance
