We use Didit at Quansa to verify users before sensitive financial actions, such as their first withdrawal. What we value most is the flexibility to combine document verification, liveness and facial matching in a workflow that integrates directly with our app and communicates decisions through webhooks.

Its broad document and nationality coverage is especially important for us because we serve frontline workers across Latin America, including immigrants and people using less common documents. We have successfully used it with Brazilian identity documents and recently expanded our flow to support residence permits.

The workflow configuration also gives us useful control over which cases can be approved automatically and which should go to manual review. Overall, Didit gives us a strong balance of security, implementation speed, international coverage and flexibility. We get good value for the price. Didit’s usage-based model is competitive compared with building and maintaining document verification, liveness, facial matching, international document coverage, and review tooling ourselves. It also reduces manual verification work, improving the overall return. As our volume grows, more predictable billing and stronger auto-refill safeguards would make the value proposition even better. Review collected by and hosted on G2.com.

Most of the friction appears in exception handling. Occasionally, a verification is approved in Didit but the user remains blocked in our product because the status or device relationship has not synchronized as expected. Some users have also needed to repeat the process, while unclear OCR or facial-match results can increase manual-review work. Some of this may be related to our integration, but clearer webhook diagnostics, more explicit failure reasons, and stronger balance and service-continuity safeguards would save our technical and support teams time. Review collected by and hosted on G2.com.