MVP Specification

MVP Feature Specification

Architecture alignment note (2026-02-14): This document is pre-architecture research from the mobilebank-research phase. Drop ultimately chose a PSD2 pass-through model — no wallet, no balance held, no IBAN generation, no top-up. AISP reads bank balances, PISP initiates payments from the user's own bank account. Cards are a FUTURE feature (feature-flagged). This document is retained as research reference — it does NOT reflect the current Drop architecture.

Table of Contents

  1. MVP Philosophy
  2. Core Features
  3. Feature Specifications
  4. Timeline
  5. Success Metrics

1. MVP Philosophy

Focus Areas

What to Include

What to Exclude (MVP)


2. Core Features

Feature Priority Matrix

Feature Priority Complexity Timeline
User Onboarding P0 Medium Week 1-4
Digital KYC P0 High Week 2-6
Account Creation P0 Medium Week 4-8
IBAN Generation P0 Low Week 6-8
Virtual Card P0 High Week 8-12
P2P Transfers P0 Medium Week 10-14
Top-up (Card) P1 Medium Week 12-16
Bank Transfer P1 Medium Week 14-18
Transaction History P1 Low Week 8-10
Push Notifications P1 Low Week 10-12
Physical Card P2 High Post-MVP

3. Feature Specifications

3.1 User Onboarding

Goal: Complete signup in <3 minutes

Flow:

  1. Download app
  2. Enter phone number
  3. Verify via OTP
  4. Enter email
  5. Set password/PIN
  6. Accept T&C
  7. Start KYC

Requirements:

Acceptance Criteria:


3.2 Digital KYC (Know Your Customer)

Goal: Verify identity in <5 minutes

Flow:

  1. Select ID document type
  2. Capture front of ID
  3. Capture back of ID (if applicable)
  4. Take selfie (liveness check)
  5. Enter personal details
  6. Verification processing
  7. Result notification

Document Types:

Requirements:

Integration: Sumsub or Onfido API

Acceptance Criteria:


3.3 Account Creation

Goal: Generate EUR account with IBAN

Flow:

  1. KYC approved
  2. Account type selection (Personal)
  3. IBAN generation
  4. Account activated
  5. Welcome notification

Account Features:

Integration: BaaS provider (Swan/Treezor)

Acceptance Criteria:


3.4 IBAN Generation

Technical Requirements:

Provider Options:

Formats:


3.5 Virtual Card Issuing

Goal: Instant virtual Mastercard/Visa

Features:

Card Controls:

Security:

Integration: Marqeta or Stripe Issuing

Acceptance Criteria:


3.6 P2P Transfers

Goal: Send money to other users instantly

Transfer Types:

A) Internal (App-to-App)

B) SEPA Transfer

Flow:

  1. Select recipient method
  2. Enter/select recipient
  3. Enter amount
  4. Review details
  5. Authenticate (biometric/PIN)
  6. Confirmation

Requirements:

Limits (MVP):

Type Daily Monthly
Internal EUR 5,000 EUR 20,000
SEPA EUR 2,000 EUR 10,000

3.7 Top-up Methods

A) Card Top-up

B) Bank Transfer

C) Future: Apple Pay / Google Pay top-up

Integration: Stripe or Adyen for card payments


3.8 Transaction History

Features:

Categories:


3.9 Push Notifications

Mandatory Notifications:

Optional Notifications:


4. Timeline

Phase 1: Foundation (Months 1-2)

Week 1-4:

Week 5-8:

Phase 2: Core Features (Months 3-4)

Week 9-12:

Week 13-16:

Phase 3: Launch Prep (Months 5-6)

Week 17-20:

Week 21-24:

Milestones

Milestone Target Date Deliverable
Alpha Month 3 Core features working
Beta Month 5 500 beta users
Soft Launch Month 6 Public availability
GA Month 7-8 Marketing push

5. Success Metrics

Activation Metrics

Metric Target Threshold
Signup completion >80% >60%
KYC pass rate >85% >70%
First transaction >50% in 7 days >30%
Card activation >70% >50%

Engagement Metrics

Metric Target Threshold
MAU/DAU >30% >20%
Transactions/user/month >10 >5
App opens/week >3 >1

Quality Metrics

Metric Target Threshold
App crash rate <0.5% <1%
API latency (p95) <500ms <1000ms
Uptime >99.9% >99.5%
App store rating >4.5 >4.0

Business Metrics

Metric Target Threshold
CAC <EUR 30 <EUR 50
Monthly burn <EUR 50K <EUR 75K
Active users (6 months) >5,000 >2,000

Sources


Revision #6
Created 2026-02-18 08:44:55 UTC by John
Updated 2026-06-28 20:01:04 UTC by John