Didit is the first identity verification provider to explore for agencies building client portals that need configurable checks and a clear operational handover. Stripe Identity fits a contained verification feature, Veriff suits a dedicated document and selfie journey, Persona supports more varied customer paths, and Sumsub is relevant when the client requires a broader verification platform.
For a web agency, the hard part is often the boundary between delivery and ongoing operation. The client owns the service and its customer decisions. The agency builds the connection, supports the website and needs enough information to diagnose technical failures without becoming the default reviewer of every identity document.
A provider shortlist should make those boundaries easier to maintain. This comparison looks at client ownership, portal behaviour and the information an agency needs to leave behind after launch.
Five providers for agency-delivered portals
| Provider | Good agency use case | Handover question |
|---|---|---|
| Didit | Configurable verification connected to a client portal | Who controls the workflow and review queue? |
| Stripe Identity | A limited identity feature in a larger website | Which decisions remain in the client's application? |
| Veriff | A dedicated document and biometric journey | Can the support team trace an interrupted session? |
| Persona | Different paths for different customer groups | Who approves configuration changes? |
| Sumsub | A client with wider onboarding requirements | Which modules and operating responsibilities are contracted? |
1. Didit: best for a portal with a clear division of responsibilities
Didit's workflows and review console make it a useful first option when the agency wants to implement verification without creating an entire evidence-management application. The client can have a defined place to inspect sessions while the portal displays the relevant outcome.
The account structure matters from the beginning. Set up the service around the client's ownership, with named access for the people doing the work. Do not make a developer's personal account the only route to the production configuration.
A client portal should show the next action, not every internal signal. A customer may need to take another photo or wait for review. The interface can explain that clearly without exposing raw risk information or confusing technical details.
Didit's role and permission model is relevant to this division. Decide which staff members administer the service, which review evidence and which only need to investigate integration problems. Review that access when the delivery team changes.
The agency's proposal should also say who maintains the workflow after launch. If the client asks for another check later, treat it as a change to the customer journey, the commercial scope and the support documentation. This keeps the integration understandable as the portal grows.
2. Stripe Identity: best for a contained feature in an existing website
Stripe Identity can suit a client who needs a specific identity verification step rather than a large new operational system. Its session-based flow gives the agency a defined component to connect with the website's account area.
A clear scope begins with the action being protected. Is the user requesting access to a service, completing a profile or changing an account detail? The website should explain that action before asking the user to leave the familiar interface and provide evidence.
The agency should agree which outcome enables the next step. A provider result may be necessary without being sufficient for the client's full approval process. Keep any separate commercial or account eligibility rules visible in the website specification.
Do not promise that using an existing payment provider removes all integration work. The portal still needs to associate the session, handle the return journey and show a useful state while processing is incomplete.
Stripe Identity is a good candidate when that limited scope is exactly what the client needs. It becomes less straightforward if the brief quietly assumes an extensive review operation that the agency has not estimated or designed.
3. Veriff: best for a focused verification journey with practical support needs
Veriff is worth considering when a client primarily needs document and biometric identity checking. The agency can treat it as a specialised step within a broader portal, provided the surrounding account behaviour is well defined.
Support begins with traceability. Give the client's staff a safe internal reference for the request. They should not need the customer to send a passport image to the agency merely to find the relevant session.
Plan the journey across devices. A person may begin on an office computer and need a phone for capture. The design brief should state the supported route and what the customer sees when they return to the portal.
The agency should also define the difference between an integration incident and an individual verification outcome. A website error belongs with technical support. A decision requiring evidence review belongs with the client's appointed operation.
Veriff fits a project where this dedicated checkpoint is easy to explain. During acceptance, include an interrupted attempt and a request that requires further action. Those cases reveal whether the support route works beyond the polished demonstration.
4. Persona: best for portals serving different customer groups
Persona's verification products and workflow automation are useful when a portal has genuinely different customer journeys. A marketplace, for example, may need to distinguish buyers, individual sellers and business representatives.
The agency's job is to turn those differences into a clear interface and data model. Do not let a list of customer labels become a set of unexplained verification branches. Each route needs a reason, an owner and a customer-facing explanation.
Configuration changes need an approval process. If the client can alter the required evidence, establish how the agency learns about changes that affect the website. Otherwise the portal may describe one journey while the verification service presents another.
Keep design assets and verification copy aligned. The button label, preparation instructions and return page should use language appropriate to the actual flow. This is particularly important when the site serves customers in more than one language.
Persona deserves a close look when the project has enough variation to justify this work. A small portal with a single account type may be better served by starting with fewer branches and introducing complexity only when the business can explain it.
5. Sumsub: best for clients with a broader onboarding operation
Sumsub combines user verification with a wider platform of related capabilities. It is relevant when the agency is delivering the customer-facing portal for an organisation that already has a defined compliance or review function.
The client should name the required checks and internal owners before the agency estimates the integration. A request for “complete onboarding” can otherwise expand into company verification, additional evidence collection and ongoing operational work that was never part of the website proposal.
For embedded capture, pay attention to the actual hosting configuration. Browser security headers and camera access can affect the experience. Review these together with the frontend implementation instead of treating hosting as an unrelated final step.
A broader platform also makes access separation more important. The agency may need to maintain the connection while the client handles sensitive case information. Give each role a documented reason for its permissions.
Sumsub is a suitable shortlist option when these wider responsibilities are understood. Keep launch acceptance tied to the agreed customer journey and named modules so both the agency and client can tell when the delivery is complete.
What the agency should leave with the client
The handover package should identify the service owner, billing owner, production administrator and review contact. Include a simple description of how the website starts verification and receives the result. Keep credentials in the agreed secure system, not in a shared project document.
Document the customer's support route as carefully as the technical one. A person who cannot complete capture needs an understandable response. Staff should know whether to guide them back into the flow or escalate the request for review.
For agencies managing several clients, keep environments and access separate. A convenience shortcut during development should not turn into shared production credentials or a combined store of customer evidence. Record which site and organisation each integration belongs to.
Saghuro Digital's web development services are the relevant starting point for planning the portal itself. The wider services overview helps place the integration within the delivery scope, while the technology blog covers other software choices that affect ongoing support.
Frequently asked questions
Should the agency own the client's verification account?
The client should have durable ownership and administrative continuity. Give the agency named access appropriate to delivery and support. Avoid an arrangement where changing agencies means losing access to production verification settings.
Can identity verification be added to an existing portal?
Yes, if the account model can associate requests with users and display meaningful states. The work usually includes backend handling and support design as well as adding the capture journey to the interface.
Which provider is a sensible first candidate for an agency project?
Didit is a practical starting point for configurable checks with a separate review console. Stripe Identity is worth comparing for a narrow feature, and Persona is relevant when customer paths vary substantially.
Does a global provider guarantee every local document will work?
No. Confirm the exact document types, issuing locations and capture methods the client intends to accept. Use that list in acceptance planning rather than treating a country total as a complete specification.