Most of the conversation about “fintech” in our region treats banking as a UX problem. It is not. It is an infrastructure problem. A pretty app on top of the same disconnected core gives you a pretty app on top of a disconnected core — better screenshots, the same exclusion.
At Virtual Capital of America (VCA), the line of Blackwood that engineers financial rails, we operate on a different premise: digital banking and financial inclusion are downstream of an operable substrate. If the substrate is right, accounts, cards, payments, credit, and compliance compose. If the substrate is wrong, every product is a one-off integration that decays the moment a provider, a regulator, or a counterparty changes.
What we engineer underneath a neobank
A neobank, in our view, is an application surface on top of seven things that have to work together:
- Identity that is real. Federated, contextual, KYC/KYB-grade. The user is not a row in a database. The user is an attributable, audit-graded actor that every other system can ask questions about at the moment of decision.
- Account primitives. Wallets, sub-accounts, escrow, multi-currency — modeled as ledger entries with causal events, not opaque balances.
- Payment orchestration. Cards, ACH-equivalents, local rails, cross-border, stablecoins where regulation permits — all behind a single contract so the application surface does not know which rail moved the money.
- Card emission and acceptance. Real BIN sponsorship, real settlement, real dispute workflows. Not a referral-link program dressed as a product.
- Risk and fraud, read from operational signal. Not a rules engine bolted on after a chargeback. Risk evaluates every action against identity, event history, and counterparty graph in real time.
- Compliance as runtime, not as PDF. Travel rule, sanctions screening, reporting — emitted by the system on every relevant action, not reconstructed from logs once a quarter.
- Treasury and settlement. Reconciliation across providers and rails so the operator knows what they actually owe and are owed, without a spreadsheet.
A neobank product team builds the screen on top. We build the seven layers underneath. Both matter. Confusing them is how most fintech projects die.
Why financial inclusion is downstream of this
The unbanked and underbanked are not a marketing segment. They are people the legacy stack literally cannot serve at a unit cost that closes. A user with thin credit history, no formal employment, and a $40-month income simply costs more to onboard, KYC, and risk-assess than they generate in fees — as long as each of those steps is a manual cost.
Operable infrastructure is what changes that math. KYC at marginal cost approaching zero. Risk decisions powered by behavioral signal, not by a credit bureau the person does not appear in. Payment rails priced by their actual cost, not by a payment processor’s markup. The product that emerges on top is one we could not build five years ago — not because of UX, but because the substrate did not exist.
This is what VCA is engineering. Not a neobank in the brand sense — the operating system a serious operator would build a neobank on top of.
What this looks like in practice
- We are not building one app. We are building rails that several front-end products can ride.
- We do not differentiate via interface. We differentiate via what is possible for partners who integrate.
- We treat regulators as first-class users of the platform — the same audit trail an internal investigation needs is what a supervisor needs.
- We measure our work in operations operable, not features shipped. A capability is real when somebody else is running their money on it without us in the room.
A longer dispatch on the specific architectures — ledger design, reconciliation, the contract layer between rails — is in the queue.