How to verify a business with Myaza Trust
Verify a business against a supported registry and choose the additional evidence your onboarding policy needs. Company existence and authority to represent it are different questions.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- The business workflow uses the supported country and product.
- Found, not-found, inactive and unknown-status fixtures are handled.
- Owner due diligence can keep the final decision pending.
- The final business outcome maps to the correct company reference.
Verify a business against a supported registry and choose the additional evidence your onboarding policy needs. Company existence and authority to represent it are different questions.
Before you begin
Business verification enabled for your organisation
Supported registry and required company details
Separate requirements for representatives and key people
Use a team member with permission for this control. Check the organisation and environment before changing a setting. Review the current price before a paid check or ongoing enrolment. Screenshots show an example workspace or the public integration reference; they do not show a real customer or a completed paid check.
Set up and use the capability
Step 1: Check business access and country support
Choose the intended organisation and Sandbox. Confirm that business verification is enabled and that the current country catalogue supports the required registry product. Read the business guide’s current availability rather than assuming every individual ID market also supports KYB. Keep the company and its representative as separate subjects.
Integration reference: Products
Step 2: Create the business workflow
Open Configuration → Workflows → Create workflow and choose Business, then a suitable Standard KYB, screening or enhanced-declarations template. Set its name and inspect the subject type. Select the country and supported business product. A production KYB capture requires a published business workflow; an individual workflow cannot silently become KYB.
Dashboard example: Create the business workflow
Step 3: Choose the application evidence
Configure the offered company profile, documents, key people, applicant verification and declarations that your policy needs. Registry lookup establishes that a company exists; it does not establish that the submitter controls it. Where required, key people are screened and invited to their own identity-verification journeys. Treat corporate ownership-chain gaps as unresolved evidence, not as no beneficial owners.
Integration reference: The application (optional layers)
Step 4: Review the business decision gates
Inspect the decision graph for company status and the relevant key-people completion requirements. Decide whether the journey must wait for due diligence before acceptance. A registry-check completion can precede the overall workflow decision. Keep unavailable registry evidence, inactive company status and incomplete owner review distinct. Do not approve a company solely because a document was uploaded.
Integration reference: Decisioning fields
Step 5: Save and publish the workflow
Wait for Saved in the editor. Select Publish, or Publish changes for an existing workflow. In the publication review, check the target environment, workflow ID, price and readiness warnings. Resolve blocking issues, then confirm Publish version. A saved draft is not the version customers use. New sessions use the new published snapshot; sessions already created retain their original version.
Dashboard example: Save and publish the workflow
Step 6: Send the company its published journey
Embed the business workflow through a supported SDK or use a customer-bound hosted session. Bind externalUserId to the business reference; prefilled business details remain claims until checked. For the session’s business block, follow the documented country and registration fields. Return the link to the intended applicant and retain the workflow version.
Integration reference: Request body
Step 7: Read both the checks and final workflow outcome
Inspect the business result, registry record and current verification status. Confirm whether the workflow is still waiting for owner or representative due diligence. Store the overall decision and explanation in your business onboarding record. Use the latest authoritative status or workflow result rather than granting access from the first registry notification. Your application still enforces the onboarding decision.
Integration reference: Status and checkStatus
Get more from the capability
Require representative verification where your onboarding policy needs authority beyond company existence.
Use owner and corporate-shareholder evidence with its source and unresolved-chain state.
Test country and product differences with the current catalogue instead of hardcoding a global registry promise.
Test before relying on it
Run the supported Sandbox or simulator scenarios for this product. Where a tool is Production only, check access and scope first, then use only a permitted, deliberately reviewed Production test. A documentation screenshot or a successful page load is not an end-to-end integration test.
The business workflow uses the supported country and product.
Found, not-found, inactive and unknown-status fixtures are handled.
Owner due diligence can keep the final decision pending.
The final business outcome maps to the correct company reference.
Troubleshooting
Business verification is unavailable
Check organisation access and the supported registry product for that country.
The registry check passed but onboarding is waiting
Inspect the workflow’s owner, representative and decisioning requirements.
The representative changed a prefilled name
Prefill is a convenience, not verified evidence. Use the registry and captured checks as the source of result.
Open the setup and integration references
Read the integration reference
Back to Solutions. Choose the capability you want to activate, then follow its own guide.
Sources
Charles Archibong
Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
