1. Create a Policy
Define the Data Collection Flow
Datapoints are pieces of information collected about users during onboarding. These can be individual data fields or entire documents. datapoints serve as the foundational building blocks of Keyring's custom standard language. They can be collected through:
Keyring Connect: Data extraction (via TLSN). Any HTTPS website can be used as a datasource.
Keyring Pro: Collection via fully customisable forms (questionnaires).
Keyring can connect to any backend server that delivers data via TLS (the “s” in HTTPS). Data is translated into standardised datapoints that can be used for authorisation purposes. MPC-TLS solves the hard problem of data authentication (how do I know the source is valid) by “notarising” a user’s web session to extract select information.
Define the Rule Validation
Rules are evaluations performed on datapoints to determine whether a user is valid or "attestation-ready" for a given Policy. These evaluations are framed as questions and return a boolean value (true or false).
Keyring Connect features a validation module that performs automated checks on collected Datapoints, such as:
Is the user's registration address in a FATF blacklisted country?
Is the user's residential address in the US?
Is the user above 21 years old?
Is the user's KYC level above a certain threshold?
For each supported website, a data hook to the website's server is coded according to Keyring’s
datapointlanguage. The Policy Owner defines the set of user requirements from a menu of options. Typical verifications include: "valid KYC", "non-US resident", "accredited investor".The user is directed to the data source's website and their data is notarised via the Keyring browser extension, enabling secure exchange of keys and information (MPC-TLS) between the server, the notary and the user’s browser.
Verification process: the browser extension creates a to reveal certain information as defined by the policy and sends the proof to the notary server. That proof is verified by the Attestation service.
Once verified, the proof is fed to the Rule Validation service to yield a binary
{true,false}outcome, according to the requirements defined in 1. If true, the user is considered attestation-ready.
Keyring Pro has two main Rules:
Is the user considered valid according to the Policy Owner who has reviewed the onboarding?
Has the user provided all required Datapoints according according to the Data Collection Flow?
The user completes their onboarding questionnaire. Dynamic flow based on answers provided is available to minimise onboarding time for both users and compliance teams.
All information collected is securely forwarded to Policy Owner's compliance desk. Data can be directly downloaded for review from the Client's Admin App or received via API. The compliance officer can liaise directly with users to request further information via a Keyring-supported instance of Zendesk.
Once reviewed, the Policy Owner returns a binary
{approve, reject}response. If approved, the user is considered attestation-ready. They can be notified via email.Should a user fail onboarding, they will be able to dispute the decision using Zendesk.
Configure the Policy
Policies can be created by clients directly via the Keyring Admin App (self-service coming soon). A client can operate multiple Policies to permission different smart contract functions. A Policy is associated to a Data Collection Flow and a Rule Validation logic.
The other parameter to configure is the credentials' duration of validity or Refresh Rate. It is fully flexible. Most common durations include 1 year for Pro and 24 hours for Connect.
Policy Owners are customers of Keyring. They are responsible for defining and operating their Policy according to their regulatory standards. They also make the ultimate decision on users' attestation-ready status.
Build a Keyring Connect Policy today:
Last updated
