Not sure how to take this. With a small tweak like "you can eventually do" I would let it pass without criticism.
I work with bank cores, imaging, BSA and related middleware on a daily basis. The scope and complexity of these systems is incomprehensible to most. Many of our clients don't even try to think about how fucked up their business is. They prefer to hire Deloitte and other vendors like us to be stressed about it for them.
To give you an idea of how comprehensive a "full" banking API is, our combined WSDL and XSD references total ~9 megabytes. This is before codegen. The final reference sources as generated into the .NET codebase total nearly 20 megabytes. This is just the types & method signatures. The actual implementations live in an IBM system manufactured some time during the previous millennium.
But, none of that really matters. Whatever API method you call against a specific bank will have behavior that ultimately depends on a million things specific to them _and the region within which they operate_. So, its not enough to simply integrate with this massive API. You also have to understand a multi-dimensional matrix of regulations, end-customer behaviors, technological constraints, active geopolitical affairs, et. al.