[philsnow]

disclaimer: I know some of the folks involved with Berbix

I love this, for the same reason I love Stripe (and before them authorize.net et al): I don't want every vendor I use that has KYC requirements to implement their own controls on the screenshots/scans/videos/whatever of government IDs, because then there will be a huge amount of variation and some of them will inevitably get it very very wrong.

Putting it all under one roof (or a few roofs) allows those few companies to get storing and handling this toxic data really right, extract a reasonable amount of revenue, and everybody wins (Berbix wins because money, their customers win because they don't have to pay the opportunity cost or real cost of developing this in house, and end users win because of better/safer handling of ID information).

[undefined3840]

Not really following your logic. Why do you care as a customer if there’s variation in KYC requirements from vendor to vendor?

Also not sure why this makes handling ID information “safer.” The vendor using this service still has access to all the images (ID and selfie) and data returned to them from this API that they can store a copy of on their own servers forever. This is not like your Stripe analogy where you only get the token and not the actual card number.