Skip to main content
Payment processors and PSPs regularly onboard merchants or end-users who share nothing more than an email address at sign-up. Youverify’s entity model is built for exactly this case: you create the entity with minimal data, the platform scores it immediately against AML databases, and you enrich the record progressively as more information becomes available — all without ever creating a duplicate record.
The email-only creation path is reserved for downstream entities — merchants, fintechs, or end-users that belong to a platform customer rather than directly to your organisation. Set isSubjectConsent: true on every request to confirm the subject has consented to verification.

​
Prerequisites

  • A Youverify account at cowork.youverify.co
  • Your API secret key (retrieve it from the dashboard under Settings → API Keys)
  • Webhooks configured to receive enrichment and signal events (recommended)

​
Steps

​
Key concepts

isSubjectConsent

Must always be true. It certifies that your customer has explicitly consented to identity verification. Omitting it or passing false will return a validation error.

Progressive enrichment

Every verification, update, and transaction on the same ent_… ID tightens the risk score. You never need to recreate an entity as more data arrives.

Automatic AML screen

Youverify runs sanctions, PEP, watchlist, and adverse-media checks automatically at creation — and again after significant enrichment events. You don’t need to trigger these manually.

Created, not approved

Entity creation always returns a Created status. Approval and rejection are driven by a separate AI-agent workflow that you configure in the dashboard.

​
What’s next

  • Set up webhooks to receive real-time enrichment and signal events
  • Run AML screening on the entity at any point in its lifecycle
  • Open a case if a signal warrants investigation
  • Read the Entity 360 to understand what the full entity record contains