Troubleshooting

Ensure the enrichment step has been properly configured and added to the workflow. Note that some enrichments might require you to provide your own API key.

Certain feature flags have to be enabled for the connected UBO/Individual workflow to function properly. Double check your feature flags on the Business Onboarding Setup Page.

Additionally, be sure that the UBO/Individual verification workflow is being called from the main Business Onboarding workflow and is returning results.

Be sure that the Partner(s) you are using within the workflow support the geographies you wish to cover. It may be that more than one Partner is required if you need to verify businesses from a broad range of countries.

While most of the time, Partners can return data nearly instantly, in some cases, KYB Partners will need to retrieve documents from registries and other sources asynchronously, which will take as long as a few minutes.

Double check spelling of the legal business name, and ensure you are not using a DBA. If you've not done so, be sure to include EIN, address, and website, as these can further help locate a company.

Review the configured risk rules and thresholds in your Business Onboarding workflow. Review the Decision Path in the Case Management page to see if Partner enrichments and other steps were properly called and do not produce errors.

Often sole prop data is harder to verify, and some Partners are unable to. The best course of action is to send sole proprietors through a traditional KYC flow, which you can do via the UBO/Individual Verification workflow.

Most of our Partners don't utilize the same data in sandbox vs. production API calls. Typically there will be a set of test data that can be utilized in sandbox environments vs. live data utilized in production environments.

This sometimes happens in the case of newer companies. If the business was formed within the last 30 days, often they will not have an EIN/tax ID since it typically takes 30 days for those to be issued.

Double check to ensure the webhooks are properly configured on both the Partner side and RiskOS. This is most often the reason for this status being persistent and unresolved.