· javascript

Author Q+A: finprim is a Case for One Financial Validation Library in TypeScript

InfoQ asked author Oluwatosin Adelaja what pushed him to build it, and where he wants it to stop.


InfoQ: What pushed you to build finprim? Adelaja: Honestly, it came from doing the same work too many times. At Sprint Technology Solutions we had several products, and each one ended up with its own copy of the same financial validation, sort code checks in one place, IBAN formatting in another, card validation somewhere else, all written slightly differently by whoever got there first.

The moment it really landed for me was on a payout flow. We had account and sort code validation on the web side, and then the mobile app needed the same thing. Rather than share it, the validation got rewritten for mobile, and the two copies drifted. One of them was a little stricter than the other, so a bank detail that the web form accepted would get rejected on mobile, and we had people re-entering details that were actually fine.

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.50 released
  2. OpenAI Daybreak brings AI agents for security testing, vulnerability investigation, and fixes
  3. Podcast: Doing The Right Thing: Accountability In The Age Of AI Coding Summary
  4. Is there a 'right amount' of AI?
  5. Your pinned MCP server may not be as pinned as you think