Capstone Project
Design a Bitcoin/Stablecoin Powered Payout MVP
Project Objective
Apply everything you have learned across the 12 modules to design a Minimum Viable Product (MVP) for a payout system powered by Bitcoin and/or stablecoins.
This project simulates the real-world process of moving from theory to operational, user-facing systems.
The goal is not to build a product that "looks good." It is to design a payout system that can survive volatility, liquidity stress, operational errors, compliance scrutiny, and real user expectations.
Assignment Brief
You are tasked with designing a Bitcoin and/or stablecoin payout product for a fictional company, CrossSend, which provides cross-border payout services to freelancers across Africa and Southeast Asia.
CrossSend’s product goal is:
Allow users to receive Bitcoin or USDT payouts easily
Provide optional fiat cash-out in local currencies (NGN, GHS, KES, VND)
Operate 24/7 with minimal payout delays
Minimize trust failures and build operational excellence from the start.
Deliverables
YYou must design and publish a structured document (3–5 pages) covering the following elements:
1. User Flow
Describe the full user journey from onboarding to payout completion.
How will users sign up?
When will KYC/KYB checks happen?
How will users request payouts?
What assets will they be offered (Bitcoin, USDT, fiat)?
How will payout status updates be communicated to users?
2. Funding Model
Choose your funding model and justify it.
Custodial wallet model?
Dynamic on-the-fly funding model?
Hybrid model?
Explain why you chose this approach based on:
User experience
Treasury risk
Compliance needs.
3. Payout Lifecycle Design
Map the full lifecycle:
Quote generation
Payment funding
Confirmation
Fiat payout processing (optional)
Completion or failure handling.
Indicate webhook events you will send and major Trip milestones.
4. Liquidity and Treasury Plan
Describe how you will manage liquidity:
How much liquidity buffer per corridor?
How will you monitor liquidity health?
What will you do during liquidity shortages?
Will you split liquidity pools by asset (BTC, USDT) or centralize?
5. Error Handling Framework
Document how you will:
Handle expired quotes
Handle underpayment/overpayment
Handle payout rail failures
Handle user disputes or compliance blocks.
Outline user communication policies during errors.
6. Security Plan
List key security protections:
Hot wallet risk management
Webhook security
API key handling
Admin dashboard protections.
Focus on high-risk areas for Bitcoin, stablecoins, and fiat integrations.
7. Regional Adaptation
Select at least two target payout corridors (e.g., Nigeria NIP, Kenya Mobile Money, Vietnam Bank Transfer).
For each corridor:
Define expected SLA (funding-to-payout time)
Define specific liquidity or compliance risks
Define UX messaging specific to that corridor.
8. Success Metrics (KPIs)
Define 5–7 KPIs that you will use to measure payout product success in the first 90 days post-launch.
Example KPIs:
Payout Success Rate
Average Time-to-Funding-Confirmation
Liquidity Buffer Health per Corridor
User Support Ticket Rate per 1,000 payouts
Funding Conversion Rate (quotes initiated to payouts completed).
Final Deliverable
In addition to submitting your structured Capstone Document internally, you are strongly encouraged to publish your project publicly as an article.
Publishing your Capstone Project demonstrates:
Mastery of Bitcoin and stablecoin payout system thinking
Seriousness about building financial products that handle real-world money movement
A professional commitment to operational excellence in financial technology.
The article can be published on:
Your personal blog
Medium
Mirror.xyz
Any other professional publishing platform.
You are not only learning. You are building a public track record.
Guidelines for Publishing Your Capstone Project as an Article
title Example: "Designing a Bitcoin and Stablecoin Payout System: My Capstone Project"
Include the following sections clearly:
Introduction: Why Bitcoin/Stablecoin Payouts Matter
User Flow Design
Funding Model Choice and Justification
Payout Lifecycle Mapping
Treasury and Liquidity Strategy
Error Handling Framework
Security Model Overview
Regional Adaptations
Success KPIs
Final Reflections: Lessons Learned Building for Financial Trust
Keep the tone professional, structured, and clear.
Focus on operational realism, not hypothetical ideas.
Feel free to credit the course, but center your article on your own analysis and design.
Optional Recognition
Outstanding publicly posted Capstone Projects may be:
Featured in future Bitnob or partner newsletters
Recommended to hiring partners looking for product managers fluent in Bitcoin and payment system architecture
Invited to deeper collaborations with ecosystem builders.
Final Note for Students
The future of Bitcoin and stablecoin payouts will be built by people who are serious about liquidity, trust, operational excellence, and user-centered financial systems.
The best payout products survive not because of their front-end designs, but because their liquidity, risk management, operational monitoring, and user trust systems are built correctly from day one.
Publishing your project is your first step toward becoming one of them.
Build accordingly.
