Skip to main content

How it works

High-level overview​

  1. The third‑party application sends transaction data to our backend.
  2. The backend resolves the referenced actors (e.g., people already verified through the platform) using the provided identifiers.
  3. The backend retrieves only the minimum required attributes from the user vault in the decentralized storage.
  4. The decentralized storage returns the requested attributes to the backend.
  5. The backend enriches the transaction with the retrieved attributes and prior checks.
  6. The backend submits the enriched request to the KYT engine.
  7. The KYT engine computes a risk score based on the enrichment and application‑defined rules.
  8. The KYT engine returns the risk score and explanatory reasons to the backend.
  9. The backend evaluates any triggers configured by the third‑party application.
  10. The backend returns the risk score and reasons to the third‑party application.
What is a trigger?

Triggers are application‑defined conditions evaluated against the risk score, reasons, and contextual attributes. Based on those evaluations, they can automatically:

  • Approve the transaction
  • Route it to manual review
  • Reject the transaction

Triggers are configurable per use case and are evaluated immediately after the KYT response is received.