A neobank in stealth needed KYC verification — passport plus utility bill plus selfie — without storing the document set on a third-party server. AwaitVerify let them ship in two weeks.
Most KYC providers retain a copy of every document they verify, sometimes for years. For a regulated neobank, that meant adding a third party to the compliance perimeter — every breach, every subpoena, every retention review touches them too. They needed verification without retention.
The mobile app calls the AwaitVerify TypeScript SDK directly. The passport, utility bill, and selfie are fragmented client-side. Five masked views per document hit our reviewers — they verify tampering, expiry, font consistency, and selfie liveness — and return a typed result. The original images never touch our infrastructure.
const kyc = await verifyDocument({ files: [passport, utility, selfie], schema: KycResult, priority: "standard", }); // kyc.tampering.detected → false // kyc.expiry.valid → true // kyc.liveness.score → 0.98
“The first vendor pitch we got involved a 30-page DPA and a copy of every customer ID sitting in someone else's S3 bucket. AwaitVerify's pitch was 'we don't store the doc.' That was the whole conversation.”— CISO, neobank in stealth