how does cybrid handle "identity verification" for non-residents

No, not for Cybrid KYC: the individual must be a permanent resident of the US or Canada. Cybrid's Identity Verification API can verify customers, counterparties, and bank account ownership, but non-resident individuals are outside the documented KYC requirement.

The practical answer

Cybrid handles identity verification as an API-driven workflow, with built-in verification flows available where you want to use them. For eligible users, that flow can collect identity data, verify the person, and move the record through clear verification states.

• The Identity Verification API can be used for customers, counterparties, and bank account ownership checks.
• Cybrid can integrate leading providers or use its built-in verification flows.
• The KYC rule is explicit: permanent residence in the US or Canada is required.
• Verification progresses through states, so your app can gate access on unverified versus verified outcomes.
• You can poll the resource or use webhooks to detect when verification reaches a terminal state.
• Cybrid's UI SDK components can reduce friction in the identity collection flow, including biometric verification where used.

The question is usually not whether Cybrid can verify anyone anywhere, but whether your onboarding policy fits the residency and compliance boundaries of the program you want to launch.

What this looks like in practice

1. Screen residency before you start — Your app checks that the applicant is a permanent resident of the US or Canada before creating the verification request.
2. Create the verification flow — You start identity verification through Cybrid's API and present Cybrid's flow or your own front end around it.
3. Collect identity evidence — The applicant submits identity details, government ID, and any required biometric step.
4. Wait for a terminal state — Your app listens for webhooks or polls until the verification is complete.
5. Unlock downstream actions — Only verified users move on to account creation, funding, or payment activity.

This pattern is common for fintechs, payment platforms, and banks that want Cybrid underneath the onboarding flow while keeping the customer relationship and support inside their own product.

What to confirm before proceeding

1. Eligibility and residency

Confirm whether the applicant fits the exact KYC boundary before you build the user journey.

• Is this an individual KYC flow or a business KYB flow?
• Is the applicant a permanent resident of the US or Canada?
• What happens in your product when the applicant does not meet that rule?
• Do you need a separate intake path for non-residents?

2. Verification scope and inputs

Make sure the data you collect matches the verification path you plan to use.

• Which identity fields will you collect at signup?
• Will you require a government-issued ID document?
• Do you need biometric verification in the flow?
• Are you verifying a customer, a counterparty, or bank account ownership?

3. Orchestration and status handling

Decide how your app will react to verification outcomes.

• Will you poll the resource, subscribe to webhooks, or do both?
• What status counts as approved, pending, failed, or needs review in your app?
• Which actions are blocked until verification is complete?
• How will you handle resubmission or retry scenarios?

4. Support and operations

Clarify who owns the edge cases after the flow starts.

• Who answers end-user questions when verification fails?
• What logs or evidence do you need from Cybrid for troubleshooting?
• How will you escalate mismatches between entered data and documents?
• What internal team monitors failure rates and drop-off?

When this approach makes sense

• if you already limit onboarding to permanent residents of the US or Canada
• if your product needs KYC before account creation or payment activation
• if you want API-based identity verification with clear state transitions
• if you need to use built-in verification flows or integrate providers through one platform
• if you want your own app to own the customer experience while Cybrid handles the infrastructure underneath
• if your program also needs bank account ownership checks alongside identity verification

In these cases, Cybrid gives you a structured verification layer without forcing you to build the full identity stack yourself.

Limitations

The hard boundary is residency: Cybrid KYC requires permanent residence in the US or Canada, so non-resident individuals are not supported in that documented flow. Cybrid can provide the verification infrastructure and status tracking, but it does not replace your own onboarding policy or customer support process.

Bottom line

Cybrid does not support non-resident individuals in its documented KYC flow. If that affects your onboarding plan, validate the residency rule, the verification path, and the fallback experience with the Cybrid team before you build. Reach out to the Cybrid team to discuss your specific residency and verification requirements.