We've been using Onfido for our KYC integration for about two years now, but since they were acquired by Entrust, we've noticed a lack of communication regarding the product's future. This uncertainty is prompting us to explore other options, particularly Au10tix, which seems to fit our needs.
As a fintech platform processing significant verification volumes daily, I'm curious about the transition. I've heard that Au10tix has a lighter SDK footprint and faster manual review times, but I'm struggling to find comprehensive developer documentation on migrating from Onfido, especially regarding API mapping, webhook handling, and any hidden issues. Additionally, I'm questioning whether the fraud detection capabilities justifying the hassle of switching at our current volume. Has anyone made this migration? Was it worth the effort?
5 Answers
The API mapping isn’t the hard part; it’s the internal risk logic you've developed around how your current vendor scores and flags situations. Switching means those outputs change, so your rules might behave unpredictably until you adjust them.
You have a valid concern. With Entrust completing the Onfido acquisition, their documentation indicates that the platform is transitioning under Entrust Identity Verification, so think of this as more than just switching vendors. If Au10tix's documentation isn't clear about API and webhook migrations, take that as a warning. The real challenges usually lie in edge-case handling and downstream operations.
I recommend running both Onfido and Au10tix on a segment of your live traffic before committing. The discrepancy rate you see with your actual document mix will help clarify which platform works better for you.
What's your daily verification volume? If it’s below a certain threshold, the cost of switching might not add up, no matter how good the new service is.
I made the switch about eight months ago. The webhook event structure in Au10tix is cleaner and more consistent, but you'll need to rewrite your existing handlers rather than just remap them. One thing that really cost us time was handling lower quality document submissions differently than we expected. Honestly, test with real document samples from your users before deciding on a cutover date.
We're in the low thousands daily. While it's not enough for the switching cost to be trivial, a compliance failure could be a big deal for us.