3 ms·
I feel like a lot of comments are missing the point of this blog post. In the past 5 years or so, there has been an explosion of "XaaS" API companies that many
by hn_throwaway_99 5y ago
I feel like a lot of comments are missing the point of this blog post. In the past 5 years or so, there has been an explosion of "XaaS" API companies that many of the new fintechs or "challenger banks" build on top of. For example:
1. There are lots of Banking as a Service platforms for fintechs that want to essentially be the end-user facing platform, but then funds are held at a chartered, FDIC-insured bank. Companies like Q2 and Treasury Prime.
2. There are then a slew of companies for things like Card Issuing as a Service, KYC as a Service, Fraud Monitoring as a Service. Companies like Stripe, Marqeta and Lithic on the card issuing side; Alloy, Socure, Unit21 on the KYC side; Sift on the fraud monitoring side, etc.
This post is basically arguing about open source companies providing "lower level primitives" in the form of libraries that people can build on top of, i.e. libraries for creating and processing ACH files, sending and receiving wire transfers, financial ledgers, syncing for required OFAC checks, etc. Building these things from scratch today is extremely difficult, not just because it takes time, but because (at least to me), it feels like so much stuff in the financial industry is poorly documented, or perhaps its better to say that the documentation is only half the story - what is required in practice and by what regulators really care about just takes "tribal knowledge" from banking experience.
Not saying one way or the other whether I think the author's thesis is correct, but I think it's a good topic for discussion, and is orthogonal to things like Open Banking APIs.