1. Create a Policy
Last updated
Last updated
Keyring Pro: list the datapoints required to onboard users with fully customisable questionnaires.
Keyring Connect: define the acceptable data sources and the data points to capture.
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.
Keyring Pro
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.
Keyring Connect
For each supported website, a data hook to the website's server is coded according to Keyring’s datapoint language. 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.
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.
