Wallet-as-a-Service vs In-House: Cost, Control, Compliance

Every fintech eventually faces the build-vs-buy decision for core infrastructure. Digital wallets—storing balances, facilitating transfers, managing payment methods—are no exception. Should you build from scratch or use a Wallet-as-a-Service (WaaS) platform?

What is a Digital Wallet?

At its core, a digital wallet is:

• Ledger system: Track balances per user
• Payment method store: Securely store card/bank account credentials
• Transaction engine: Execute transfers, payments, top-ups
• Compliance layer: KYC, AML, fraud monitoring

Think of it as a bank account abstraction that sits on top of existing financial rails (cards, ACH, wire transfer).

Wallet-as-a-Service Platforms

WaaS providers offer turnkey wallet infrastructure:

Leading Providers

• Stripe: Stripe Issuing + Connect for marketplaces
• Adyen: Wallet, balance accounts, payouts
• Checkout.com: Issuing + embedded wallets
• Rapyd: Global wallet with local payment method support
• Modulr: Embedded finance for Europe
• Unit: Banking-as-a-service with wallet functionality

What They Provide

• Pre-built ledger: Double-entry accounting system
• Regulatory licenses: E-money or banking charter
• Compliance infrastructure: KYC, AML monitoring, SAR filing
• Payment method linking: Card tokenization, bank account verification
• API: RESTful endpoints for balance checks, transfers, payouts
• Dashboard: Operations tools for support teams

Pricing Model

Typically:

• Setup fee: $0-$50K (enterprise)
• Per-transaction: 0.5%-1.5% of value + fixed fee ($0.25-$0.50)
• Monthly platform fee: $500-$5K depending on volume
• Additional services: KYC ($1-$5/check), card issuing, FX markup

In-House Wallet: What You're Building

Building a wallet from scratch means:

1. Ledger System

• Database schema: Users, accounts, transactions, balances
• Double-entry accounting: Every debit has a matching credit
• Idempotency: Retries don't duplicate transactions
• Concurrency control: Prevent race conditions on balance updates
• Audit trail: Immutable transaction log

Tech stack: PostgreSQL with row-level locking, event sourcing, or purpose-built ledger DB (TigerBeetle).

2. Payment Method Integration

• Card tokenization: Integrate Visa/Mastercard token vaults
• Bank account verification: Plaid, Stripe, or micro-deposit verification
• Payment processing: Connect to acquirers or processors

Complexity: Each payment method (cards, ACH, wire, crypto) requires separate integration.

3. Regulatory Compliance

• E-money license: Required in EU, some Asian markets
• State Money Transmitter Licenses (MTL): US requirement (50 states = 50 licenses)
• KYC/AML program: Identity verification, sanctions screening, transaction monitoring
• Reporting: SAR filings, regulatory audits

Cost: Legal, compliance staff, audit fees = $500K-$2M/year minimum.

4. Fraud & Risk Management

• Transaction limits: Daily/monthly caps per user
• Velocity checks: Max transfers/hour
• Behavioral monitoring: Anomaly detection for account takeover
• Chargeback handling: Dispute workflow

Team: Fraud analysts, risk modelers, ML engineers.

5. Settlement & Reconciliation

• Pooled accounts: Where user funds are held (partner bank)
• Daily reconciliation: Your ledger vs actual bank balance
• Reserve requirements: Maintain 100%+ coverage of user balances

Risk: Ledger bugs = money loss. Reconciliation failures = regulatory penalties.

Cost Comparison

Wallet-as-a-Service

Year 1:

• Platform fees: $50K
• Transaction fees: $200K (on $20M volume at 1%)
• KYC: $10K (10K users at $1/check)
• Total: ~$260K

Year 3:

• Transaction fees scale with volume: $1M (on $100M volume)
• Platform + KYC: ~$100K
• Total: ~$1.1M

In-House Build

Year 1:

• Engineering (4 FTEs): $800K
• Compliance (2 FTEs + legal): $500K
• Licenses: $200K (MTL applications)
• Infrastructure: $100K
• Total: ~$1.6M

Year 3:

• Engineering (6 FTEs): $1.2M
• Compliance (3 FTEs): $600K
• License renewals: $100K
• Infrastructure: $200K
• Total: ~$2.1M

Break-even: Around $150M-$200M annual volume, assuming WaaS fees are 1%.

Control & Customization

WaaS Advantages

• Faster time-to-market: Weeks vs 12-18 months
• No regulatory burden: Platform handles licenses
• Managed compliance: KYC, AML monitoring included

WaaS Limitations

• Feature constraints: Limited to provider's roadmap
• Pricing lock-in: Hard to negotiate once dependent
• Data ownership: User data lives in vendor's system
• Regional restrictions: Not all platforms operate globally

In-House Advantages

• Full control: Build exactly what you need
• Cost efficiency at scale: No per-transaction margin after break-even
• Data sovereignty: All user data in your systems
• Competitive moat: Unique features competitors can't replicate

In-House Challenges

• Regulatory expertise: Hire compliance team or consultants
• Slow iteration: Can't "move fast and break things" with money
• Operational burden: 24/7 monitoring, reconciliation, support

Compliance Considerations

WaaS Compliance

• Regulator of record: Platform's e-money license covers you
• Shared responsibility: You still do KYC, but platform monitors transactions
• Audit exposure: If platform fails audit, you're exposed

In-House Compliance

• You are the regulated entity: Direct relationship with regulators
• Full liability: Compliance failures = fines, license revocation
• Flexibility: Customize KYC/AML policies for your risk appetite

Key risk: WaaS platforms can change terms, raise prices, or exit markets. In-house = control but full burden.

Hybrid Approach

Many fintechs start WaaS, then selectively bring components in-house:

Phase 1: Full WaaS (Year 1-2)

• Launch fast with Stripe or Adyen
• Validate product-market fit
• Scale to $50M-$100M volume

Phase 2: Selective In-Sourcing (Year 3-4)

• Build custom ledger for core flows
• Keep WaaS for edge cases (international, crypto)
• Negotiate volume discounts with remaining WaaS usage

Phase 3: Full In-House (Year 5+)

• Obtain own licenses
• Migrate all flows to proprietary stack
• WaaS as backup or secondary provider

Example: Robinhood started with Apex Clearing, then built in-house clearing. Revolut used Banking Circle, then got own banking license.

Decision Framework

Choose WaaS if:

• Early stage: Pre-product-market fit, <$20M volume
• Non-core differentiator: Wallet is table stakes, not your moat
• Resource-constrained: Engineering/compliance headcount limited
• Geographic expansion: Need multi-country support quickly

Build In-House if:

• Scale: $200M+ annual volume, WaaS fees unsustainable
• Unique features: Core product requires wallet customization
• Data control: User data sovereignty is critical (B2B, enterprise)
• Long-term vision: Wallet is strategic asset, not vendor dependency

Hybrid Makes Sense if:

• Selective control: Own core flows, outsource edge cases
• Risk mitigation: Diversify across in-house + WaaS providers
• Gradual transition: De-risk migration over years, not big-bang

Key Takeaways

• WaaS is faster, lower upfront cost, but expensive at scale
• In-house is slow, high upfront cost, but cheaper long-term
• Break-even is around $150M-$200M volume
• Compliance is the hidden cost—licenses, audits, staffing
• Hybrid is the pragmatic path for most fintechs

There's no universal answer. The right choice depends on stage, volume, team capabilities, and strategic importance of the wallet to your product.

Start with WaaS. Build in-house when the vendor bill exceeds the cost of hiring a team.