I quite liked OneID when I had a meeting with them. The banking solution was quite a neat one as regards user journey. In essence
IF you had a UK banking (and it was limited to UK banks) app installed on a phone/tablet device you can via Openbanking supply some information to another company (OneID) via this system. So OneID request some data (what depended on quite what you were doing) and the user authorised the transfer of the data from within their banking app. So it was nice in that assuming they had a banking app installed it didn't require faffing around with scanning IDs or your face or anything and was quite painless.
However for now I'd put them on the back burner as a possibility because I'd assumed we'd need to potentially validate ages over the entire globe. The other offering they had that would do that was the mobile phone check, but as discussed up thread I don't have confidence that the data returned by that is reliable (I think far too many contracts will be in an adults name when the user is a child and the actual user of the phone wont be logged with an age -it'll just be the adult - note I have no evidence that is the case, but it's my gut feeling
despite the claims).
So what about the freebie - well I'll ask my contact at OneID what they are getting out of it - maybe it's a loss leader?
Any use for us? Thinking out loud (sorry) I think that comes down to the scope of the OSA and what we are using age checking for. I guess we have four categories of people:
- UK adults
- UK children
- Rest of world adults
- Rest of world children
In terms of XF usage there are only a few models really:
- Anyone can register and Age verification "unlocks" access to some features
- Age verification to restrict to only adults/children from registering
If you are using (2) then this solution isn't of any use unless you only want to target the UK (and the 50M or so apparently they think they can check). So this is only of use if you are allowing anyone (adults/children) worldwide to register and you are then just saying "
if you want feature X you need to prove you are an adult". Given the only users you will be able to prove are adults are in the UK then it is a bit limited.
So realistically I can't see quite how you'd use it unless you tie it into a UK IP address database and require anyone with a UK IP (lets just forget for a second how easy that is to bypass) to do an age check. So you'd allow rest-of-the-world adults and children to do what they want (if indeed rest-of-the-world children are out of scope of the act), but if you have a UK IP then you force them to do an age check and then restrict/grant the account as appropriate. I guess if the scope of the act is limited that might work. The main reason for age restriction is to either wholesale avoid the children's risk assessment (ie site is adults only) or to help as a mitigation in risk assessment (eg children can't be contact by PM/DM or PM/DM people, etc.). If the act only requires you to mitigate risks for UK children then I could see it working - at least as far as the law went, although rather missing the "spirit" of the law of course. I think I'd need a lawyer to read the act and tell me if we're okay to go this direction.
Anyhow interesting I shall investigate a bit more.
As an aside I'm just coming to the end of a Shufti trial period. The actual system is easy enough to use once you get your head around the documentation. I can certainly add it into my existing solution (if I abstracted some more of that code - no bad thing). So I may do that as I feel I should tidy up my codebase anyway. I feel their privacy policy and what they use the data for is a bit more wooly than VerifyMyAge and I'm less clear about exact retention (eg they keep facial photos to weed out duplicate submissions - I guess as a mitigation against someone feeding in a youtube video of a face to a virtual camera for instance for an AI age estimate). And in the backend I can see the full scan of the user's ID, etc. So that makes me a little more twitchy - I'd rather not have that data floating around to be honest (I expect I can clear it however) - I generally prefer the approach to having as little data about someone as possible. Anyhow the system seems fine and there are a couple of ways you could integrate it with XF without too much trouble.
In essence you fire off a request to their API for a type of authentication (eg check ID, or selfie estimation, etc). You can customise this request so you could ask for both ID and a selfie and they have all sorts of interfaces for more business activities (so that might be of use to some). You then get back a URL you can give to your user to perform the verification. User fires that URL up and follows the steps (pic of ID, upload ID, etc). You can check the verification status either periodically or there is a webhook. It does look like it'd lend itself better to a "middleman" supplier model at least as the branding and templates are more customisable and generic.
Model is a "purchased credit" and I think you can spend the credits as you choose on their service (but need to confirm that). Selfie checks are about $0.20 and ID checks are $0.50 and you need to buy about $750 of credit to get going.