Prerequisites
- Your organization governs the network. See Network roles.
- A sandbox API key exported as
SOLO_TOKEN. See Authentication. - Your network’s
network_id, from the network’s page in the dashboard.
1
Create a querying policy
A querying policy is the
standard a certificate query in your network is held to. Create one in
your network:
Response
2
Configure what counts
For each data model the policy covers, choose the conditions a furnished
record must meet. Each condition is a provenance option, such as “the
document was captured”; the policy editor in the dashboard lists every
option with its ID. This example requires a captured identity document:Models the policy doesn’t name keep the product’s own rules. You can also
build the whole configuration in the dashboard’s policy editor instead.
3
Activate it and make it the network default
In the dashboard, open the policy and choose Activate, then on its
Assignments tab add an enforcement window marked as the default, with
the dates it applies.From then on, a certificate query that names your network first and doesn’t
pass a
policy_id is held to this policy. Only active policies apply, and
default windows of two active policies can’t overlap.To offer a different policy to particular partners, add them to a window
with Assign members. That makes the policy available to those partners
when they choose a policy; it doesn’t change what applies when a query
names none.4
Furnish the verifications you hold
Contribute the verified customers your partners onboard, so their
certificates can be built from your work instead of repeated. Each record
is matched on SSN and date of birth, so a customer you and a partner both
furnish is one consumer.Every record is attested as furnished by your organization. When a
partner’s certificate uses it, the sub-product’s
furnishing_entity_id is
yours.Set
is_kyc_cip on identity corroboration events. The product’s default
rules for identity corroboration start with whether the check was part
of your Customer Identification Program; without it, the sub-product
can’t be satisfied.What your partners can read
A partner querying your network can read the records it furnished, the records your organization furnished, and records from institutions that granted it access through consent. It can’t read records other partners furnished. See Entitlement.Related
Golden path: fintechs
How partners consent, check, fill gaps, and query under your policy.
Querying policies
Everything a policy can express, and how the default is chosen.