Use rulesets or policies
To scale your Middesk integration to satisfy your compliance needs and risk tolerance, use rulesets or Policies to define what results in a business approval.
Create rulesets
Rulesets is a generic term that refers to logic implemented on your end. A ruleset defines what actions your integration takes based upon the data Middesk provides.
For example, most Middesk customers create a ruleset based on the status or sub_label for each attribute.
statusis a bit less granular thansub_labelbut is consistent across the various review tasks. This field can only have the valuessuccess,warning, orfailure.sub_labelis a bit more granular thanstatusbut its value depends upon the attribute the review task is for. For example:nameuses thesub_labelvaluesVerified,Similar Match, andUnverifiedtinuses thesub_labelvaluesFound,Not Found,Error, andMismatch
Middesk recommends first creating your ruleset based on status, only moving to also using sub_label if you find that status is not granular enough for your use case.
The exact rulesets you apply to Middesk results depends upon your company’s compliance program, use case, and risk tolerance. The examples in these docs are common configurations, but do not represent legal advice or recommendations.
Create Policies
Policies is a Middesk feature that enables your compliance and risk team to make more automated and accurate onboarding decisions directly from a verification result. Policies can trigger new Orders, flag identities to review, or change a Business object’s status.
Note that even with Policies enabled, Middesk still generates complete reports.
If using webhooks, Middesk sends a business.updated notification once all attributes are processed and the policy decision is ready to be evaluated. This webhook event includes the Policy decision.
Enable Policies
Admins can enable and manage Policies in the Dashboard. (Other Middesk users cannot enable Policies, but can view policy decisions.)
View policy decisions and other details on a business in the Dashboard or using the GET /policy_results endpoint.
Default policy
Each Middesk account is pre-set with a disabled default policy, named Default Auto Approval. If you enable the default policy, a business is auto-approved if the business’ tasks satisfy all of these criteria:
If you edit the default policy, it converts to a custom policy.
Create a custom policy
On the Policies settings page of the Dashboard, you can configure multiple custom policies based upon any business attributes that match your compliance requirements. Policies can only be applied to the business attributes.
If KYC is enabled for custom policies, you can set an action on the business with the business’ tasks and the KYC decision.
