> For the complete documentation index, see [llms.txt](https://doc.youverify.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.youverify.co/one-platform.-one-view-of-every-entity..md). # One platform. One view of every entity. ### What Youverify Cowork is Youverify Cowork is **one platform for FRAML** (fraud and anti-money-laundering): a single place to onboard, verify, monitor and investigate the people and businesses you do business with, and to see everything you know about each of them. Instead of stitching together a KYC product here, a sanctions screen there, and a transaction monitor somewhere else, you work with one object, the entity, and one continuous record of everything that has ever happened to it. Behind it sits the same authoritative-data engine that powers Youverify across Africa, EMEA and beyond, reorganised around a model that reflects how compliance teams actually think: not “which check did I run?” but “what do I know about this customer, and what should I do about it?” ### The problem we are solving Most compliance stacks are organised around checks: an identity API, a separate business verification API, a separate screening API, and a separate transaction monitor, each returning its own report with its own identifiers. The result is fragmentation: a customer’s identity check lives in one system, their sanctions hit in another, their alerts in a third, their case in a fourth. Nobody has the full picture, false positives multiply, and onboarding slows down. Payment processors feel this most acutely: a processor often knows a customer by little more than an email, yet that customer still needs to be risk-assessed and monitored. A check-centric system has nowhere to put them. ### The shift: from checks to the Entity 360 Cowork inverts the model. The starting action is **Add Entity**, not “run a verification.” You add a subject the moment you have anything about it, even just an email, and the platform creates a tracked record with a risk score and a 360 canvas. From then on, every check, transaction, signal, alert and case attaches to that one entity, building a complete, queryable history: the **Entity 360**. Two consequences are easy to miss. First, adding an entity is **not an approval decision**; it produces a Created entity with a score and a canvas, and approval runs separately as an **AI-agent workflow** . Second, the score is computed at creation from whatever data is present, so an entity is useful immediately, however thin the inputs. ### Who this is for * **Payment processors, PSPs and BaaS providers** onboarding sub-merchants and fintech clients they often know only by email. Minimal-data entities, downstream hierarchies and progressive enrichment are built for this. * **Fintech and bank engineering teams** integrating KYC, KYB, AML screening and monitoring, who want a clean quickstart, predictable auth, SDKs and webhooks. * **Card issuers and acquirers** who need per-entity (and per-sub-merchant) screening and monitoring to meet scheme and regulatory obligations. * **Compliance leaders** evaluating Youverify, who need to understand the 360 value, risk scoring, compliance health and certifications. ### Why teams move to Cowork?

All-in-one

KYC, KYB, AML screening, transaction monitoring and case management on one platform and one set of credentials.

The Entity 360

Every fact about a customer in one record, so decisions are made on the full picture and false positives fall.

AI agents and workflows.

Decisions across onboarding, transaction screening, monitoring and fraud detection are automated by configurable AI-agent workflows, with Vyra as the compliance copilot.

Configurable risk scoring.

A transparent, weighted risk model you can tune to your risk

appetite

Regulator-ready

SOC 2 Type II, ISO 27001 / 27018 / 42001 (AI), GDPR, plus data-protection compliance across Nigeria, Côte d'Ivoire, Kenya, South Africa and the UK, among others.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.youverify.co/one-platform.-one-view-of-every-entity..md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.