Onboard a customer you only know by email

The payment-processor flow. Start with almost nothing, monitor immediately, enrich over time.

1

Step 1: Add the entity

You hold only an email. That is enough. The platform creates the entity, scores it on the limited data, and returns a Created entity (not an approval) with a 360 canvas.

POST {{baseUrl}}/v2/api/entities
{ "entityType": "individual", "isSubjectConsent": true, "email": "[e-mail]" }

2

Step 2: Attach transactions right away

Register the entity as a KYT client and start posting transactions, so monitoring begins before full KYC.

3

Step 3: Enrich progressively

As the customer supplies a phone, date of birth or ID, run the relevant verification on the same entity ID. The record fills out; nothing is duplicated.

4

Step 4: React to signals, escalate to a case

When a signal fires or an alert needs review, open a case on the entity and work it with Vyra's AI summary. Every action is written to the activity log. The approve / reject / restrict decision is driven by an automated AI-agent workflow applying your rules, escalating edge cases to a human.

This flow is impossible in a check-centric system, where a customer with only an email has nowhere to live until enough data exists to run a check.