The Fintech & Payments Power 50

The episode contains a handful of genuinely useful ideas - biometric reuse for ongoing authentication, cross-transactional risk profiles as an identity-intelligence network, and the three-stage automation model (extract → surface insights → decide) - but large portions of the runtime are consumed by the host's lengthy preambles, mutual agreement, and high-level platitudes that add little for an informed operator.

“we're doing half a million verifications a day. Right. You can't go and check each individual in each individual one, but we selectively check to continually monitor the accuracy of our output”

“we have what we call a cross, uh, transactional risk, um, profile that we can, if we have seen that individual elsewhere in our database, we can anonymize a flag”

The analogy of building identity intelligence networks similar to credit bureaus is a moderately fresh framing, and Sequoia's explicit refusal to own the decision layer is a clear architectural stance; however, most of the discussion recycles well-established RegTech talking points - layered KYC, AI explainability tensions, human-in-the-loop - without genuine contrarian argument or first-principles reasoning.

“we're now moving towards what we call, you know, um, identity intelligence if you like, perhaps in the same ways the credit bureaus have historically done it”

“the only country that has reduced fraud, I think I read an article recently, um, over the past year is Australia”

Steven Simmons as co-founder and CDO of an active platform is a legitimate practitioner with hands-on domain depth; Simon Kingston's title is Head of Partner Sales EMEA, making him a senior commercial rather than technical or product executive, which limits the operational depth he can provide on architecture and model governance decisions.

“we are unique in being able to extract all UK bank statements, all formats of UK bank statements and all UK payslips. And these are being used by providers like Experian and the Mortgage Advice Bureau”

“we have quite a significant investment in our own QA team. So we actually QA 10% of our verifications”

A small number of concrete data points appear - 500k daily verifications, 10% QA sampling, named clients Experian and Mortgage Advice Bureau - and specific regulations are correctly cited (DORA, Data Access and Usage Act, AI Act, UK cybersecurity resilience bill); however, fraud reduction rates, ROI figures, processing-time benchmarks, and case study outcomes are entirely absent, leaving most claims at the level of assertion.

“we're doing half a million verifications a day”

“we actually QA 10% of our verifications”

The host demonstrates genuine domain knowledge and occasionally frames sharp questions about architecture and automation trade-offs, but she habitually pre-answers her own questions in lengthy preambles, rarely challenges a guest claim, and allows both guests to stay comfortably within their marketing comfort zones throughout the conversation.

“how are your clients rethinking architecture so that identity becomes more of a living risk signal instead of just a tick box onboarding”

“you cannot abdicate your respons the responsibility in this with the provider”