cybrid is kyc automatic or manual

Cybrid's KYC is primarily automated, but it can include manual review in your own compliance workflow when needed. In practice, Cybrid provides the verification infrastructure and UI components, while your team decides how much exception handling or escalation to layer on top.

---

The practical answer

The question is usually not whether Cybrid is “automatic or manual,” but how much of the verification flow you want Cybrid to run versus what you want your own compliance team to own.

• Cybrid proactively applies KYC from the initial platform access in its standard onboarding flow.
• The KYC process can collect identity details such as name, date of birth, address, and a government-issued ID.
• Cybrid’s KYC flow also includes biometric verification in its standard identity checks.
• Cybrid provides UI SDK components to streamline the verification experience inside your product.
• The platform supports both KYC for individuals and KYB for business entities.
• Your app still owns the customer relationship, so your team handles support, escalations, and any manual exception process you add.

For most buyers, the better question is not “is it automatic or manual” but “what parts of onboarding should Cybrid automate, and what parts should stay in my compliance operations?”

---

What this looks like in practice

1. Start onboarding in your app — The user enters your product and begins the KYC flow through your Cybrid integration.
2. Collect identity information — The flow gathers required customer details and document images, and can include biometric verification.
3. Run the verification workflow — Cybrid processes the KYC steps and returns the result based on the configured program requirements.
4. Handle exceptions outside the core flow — If a case needs extra review, your team handles that in your own operations process.
5. Enable access after approval — Once KYC is approved, you can allow the user into the relevant account, wallet, or payment flow.

This pattern is common for fintechs, payment platforms, and banks that want a standardized onboarding flow without building every verification step from scratch.

---

What to confirm before proceeding

1. Automation model

You need to know exactly which steps are handled in the Cybrid flow and which steps remain yours.

• Is the verification decision fully automated for clean cases?
• Are there manual review points for exceptions, mismatches, or edge cases?
• How are failed submissions, retries, and partial matches surfaced?
• Can your internal team review cases that need a human decision?

2. Identity requirements

KYC requirements often vary by customer type, market, and sponsor bank.

• Which fields are required for your use case: name, DOB, address, ID document, biometric verification?
• Do requirements differ for KYC versus KYB?
• Are there different requirements by country or corridor?
• Which document types are accepted in your target markets?

3. User experience and integration

You should decide how much of the onboarding flow you want embedded in your product.

• Will you use Cybrid UI SDK components or build your own front end?
• Does KYC happen before account creation, or after the user starts onboarding?
• How much of the flow stays in your app versus a hosted or embedded step?
• How will you handle abandonment, resubmission, and retry paths?

4. Operations and support ownership

Cybrid provides the infrastructure, but your team still owns the end-user relationship.

• Who on your team handles KYC questions from end users?
• What status data do you need back from Cybrid for support and operations?
• How will manual exceptions be tracked and resolved internally?
• What is the escalation path between your support team and Cybrid?

---

When this approach makes sense

• if you need KYC from the start of platform access
• if you want a mostly automated onboarding flow
• if you need both individual KYC and business KYB
• if you want to keep identity verification inside your own product experience
• if you need document and biometric checks as part of onboarding
• if your compliance team will handle policy decisions and exceptions

In these scenarios, Cybrid gives you the verification infrastructure without forcing you to build the entire compliance stack yourself.

---

Limitations / What to keep in mind

Cybrid is not a purely manual KYC service, and it is not a replacement for your compliance policy or operating procedures. It also does not interact directly with your end customers, so your app team remains responsible for support, exception handling, and customer communication.

---

Bottom line

Cybrid KYC is primarily automated, with manual review handled by your own operations when needed. If you want to see where automation ends and your team’s compliance process begins, map your flow with the Cybrid team to confirm integration fit.