SWStuart Watkinsinzenoo.hashnode.dev·Jul 5 · 7 min readWhy we invert the KYC pipeline: device intelligence before documentsWhen we design identity verification pipelines, the first architectural decision is also the one most teams get wrong: the order of the checks. Document verification first, device intelligence last. I00
SWStuart Watkinsinzenoo.hashnode.dev·Jun 28 · 9 min readHow we architected KYB verification to survive a regulator's questionsWhen we sat down to design our KYB verification layer, the design constraint was not a feature list. It was a single question: can this system answer anything a regulator asks, quickly, accurately, an00
SWStuart Watkinsinzenoo.hashnode.dev·Jun 2 · 1 min readINTERNAL TEST 1780390761 (auto-deleting)This is an automated end-to-end test of the Hashnode publishing path. It is deleted within seconds. Nothing to see here. Verifying the API works after the gql-beta endpoint migration.00
SWStuart Watkinsinzenoo.hashnode.dev·May 1 · 7 min readThe most expensive phrase in financial services is 'that'll do'Last week, I reviewed a compliance survey where 67% of fintech leaders admitted their 'temporary' KYC setup had been running for over two years. One respondent calculated it was costing them three ful00
SWStuart Watkinsinzenoo.hashnode.dev·Apr 28 · 7 min readZenoo vs RiskNarrative: a practical guide to choosing the right compliance platform for your stackBy the end of this, you will have a clear decision framework for choosing between Zenoo and RiskNarrative, grounded in real integration timelines, performance benchmarks, and the architectural trade-offs that actually matter when you are building com...00
