What incumbent neo-banks have to assemble
Building a modern neo-bank with banking + payments + cards + securities + crypto requires integrating somewhere between 40 and 80 separate vendors: a sponsor bank, a payment processor, a card-issuing platform, a debit-rails provider, a securities BD, a transfer agent, a custody platform, a KYC vendor, an AML vendor, a sanctions-screening vendor, a fraud-detection vendor, a tax-reporting vendor, a Form 1099 e-file vendor, a Form D filer, a blue-sky filing service, a crypto-conversion partner, a stablecoin issuer relationship, a corporate-actions provider, a proxy-distribution agent, a WORM-storage vendor, a SOC 2 audit firm, and so on.
The engineering team for that integration is 200-500 people at a typical neo-bank in production. The annual vendor and compliance cost runs into the tens of millions before meaningful AUM is on the books.
What W3A members ship with
The W3A substrate vertically integrates the same eight capability surfaces into one platform with one engineering team. The integrations are not optional partner-vendor relationships — they are first-party adapters in the substrate's own codebase, maintained by the Coordination Layer, deployed as part of the substrate's release cadence, audited under one SOC 2 sub-service-organisation umbrella.
| Capability | Incumbent path | W3A path |
|---|---|---|
| Banking ledger | Sponsor bank + middleware | Hanzo Base + member sponsor bank |
| Payments + cards | Marqeta + Stripe + Lithic + Modern Treasury | 14+ first-party adapters in luxfi/treasury |
| KYC / AML / sanctions | Persona + Alloy + ComplyAdvantage | luxfi/amld overlay + member regulated BSA |
| Securities BD / TA / ATS | Apex + Drivewealth + Folio Dynamics | NCPS via luxfi/broker northcapital adapter |
| Custody | Fireblocks + BitGo + Anchorage | luxfi/mpc threshold-MPC + KMS envelope |
| Tax 1099 e-file | Sovos / Tax1099 / Track1099 | luxfi/captable/tax/iris adapter |
| EDGAR + Blue Sky | Workiva + CSC + Cogency | luxfi/captable/edgar + bluesky adapters |
| WORM retention | Smarsh + D3P letter | luxfi/transfer/worm S3-Object-Lock |
| Pre-trade compliance | In-house build (5-15 FTE) | luxfi/broker/pretrade (G-37) |
| Legal-process workflow | In-house build (3-8 FTE) | luxfi/transfer/legalprocess (G-08) |
What the 90% reduction means concretely
A neo-bank shipping the comparable feature surface on the W3A substrate:
- Engineering team: 20-50 people (vs 200-500 incumbent).
- Vendor cost: $0.5-2M/yr (vs $15-40M/yr incumbent).
- Time to first GA: 6-12 months (vs 18-36 months incumbent).
- Compliance audit cost: sub-service-organisation SOC 2 inheritance from W3A; ≈ $50-150K/yr incremental (vs $500K-$2M/yr standalone).
- Per-customer cost-to-serve: <$0.50/mo at GA (vs $5-15/mo industry).
The open-banking framing
EU PSD2 and equivalent open-banking regimes give consumers the right to direct their banking data and payment authorisations across providers. The W3A substrate is the equivalent primitive for the next generation: post-quantum-secure, FHE- confidential, decentralised at the consensus layer, non- custodial by default, and operating across all regulated financial-services capability surfaces rather than just retail banking.
A neo-bank built on the substrate is structurally portable: its customers can move to another W3A member without re-onboarding (one KYC, one identity registry, one custody key); its product surface can integrate with any other member's product through the substrate's first-party adapters; and the entire operation can be relocated to a different member's regulatory jurisdiction by toggling the routing layer. None of this is possible on the incumbent stack.