How to Build a Minimal Viable Medical Aesthetic Credit System
This article walks through the complete design of a medical‑aesthetic consumer‑credit platform, covering market analysis, strategic positioning, business object definition, core process modeling, functional architecture, front‑end/back‑end interaction, prototype sketches, and key fintech terminology, offering a practical roadmap from concept to MVP.
Amid rising household debt and living costs, many consumers turn to consumption‑credit products for expenses such as renovation, travel, education, and medical services, prompting banks, consumer‑finance firms, and internet finance companies to focus on consumer‑credit business.
1. Overall Strategic Planning and Product Positioning
1.1 Product Strategy
The China Medical Aesthetic Industry Annual Development Survey reports that by 2018 the industry delivered over 10 million procedures, generating a market value of about CNY 1.25 trillion with a 7.2% annual growth, driven by a large demand pool (1.2 billion potential female consumers), rising incomes, and technology‑driven marketing.
Key insights: a massive market, over‑20% yearly growth, and profit heavily reliant on technical or marketing advantages (30‑50% of total profit).
1.2 Product Positioning
The product should target young users with personalized services and innovative marketing to improve retention, while addressing risk‑control and service challenges inherent to a younger, price‑sensitive demographic.
Technically, integrating big‑data analytics with financial logic is essential to build a multi‑dimensional risk‑control system.
1.3 Competitive Analysis
Numerous aesthetic‑finance platforms have emerged (e.g., Meimei Installments, Kuai Installments, etc.), but market bubbles led to many exits in 2017. By the end of 2018, only about 30 vertical platforms survived, with major players such as New Oxygen and Renmai offering stable business models and robust risk‑control capabilities.
2. Business Objects and Module Decomposition
2.1 Business Objects
The ecosystem involves three core participants: consumers (C‑end), aesthetic institutions (B‑end), and consumer‑finance institutions. Each has distinct functional needs.
Consumers : credit application, loan usage, transaction tracking, repayment setup.
Aesthetic Institutions : product management, order management, fund settlement, serving as a bridge between consumers and finance institutions.
Finance Institutions : loan product management, credit approval, financial accounting, transaction tracking, and customer management.
2.2 Core Process Decomposition
The system’s main flows are:
Credit application – consumer submits request, finance institution conducts agreement signing, identity verification, data entry, and quota allocation.
Credit approval – automated scoring (funnel model) plus manual review for high‑risk cases.
Credit usage (payment) – consumer selects installment plan, signs loan contract, and completes payment.
Loan accounting – double‑entry bookkeeping records each loan transaction.
Post‑loan management – risk tagging, marketing for good users, monitoring for overdue users.
User repayment – active repayment or automatic debit.
Fund settlement – periodic settlement (T+N, weekly, monthly) from finance institution to aesthetic institution.
3. Functional Requirements Decomposition
3.1 Front‑Back Interaction Design
The front‑end serves consumers and institutions, while the back‑end serves finance institutions and integrates with third‑party payment, credit‑reporting, and banking services.
3.2 Functional Coupling Design
Clients (PC, App, mini‑program) interact with a core business system and a public platform. The core system handles product, order, and loan management for internal staff; the public platform provides shared services such as risk engine, user management, and permission control, following a high‑cohesion, low‑coupling principle.
4. Functional Architecture Planning
4.1 User‑Side Modules
Four main modules: search management, credit quota management (including application and usage), order management, and billing management. Credit application and usage are grouped under quota management because both affect the credit limit.
4.2 Institution‑Side Modules
Four modules: product management, order management, billing management, and settlement management. Settlement follows a decentralized model where the finance institution periodically settles aggregated consumer bills to the institution.
4.3 Public Platform Modules
Six modules: loan product management, merchant management, customer management, product management, user management, and permission management. Customer management includes risk‑engine cycles for black‑list handling.
5. Prototype Design
5.1 User‑Side App Prototype
The mobile app features four navigation tabs: Marketplace, Loan, Bills, and My Profile, with orange branding. Marketplace shows curated institutions and products; Loan handles credit application and quota increase; Bills display repayment schedules and details.
5.2 Service‑Side PC Prototype
The PC interface provides a tree‑style navigation for all system functions, supporting data queries, filters, and batch operations, exemplified by the loan‑product management screen.
6. Consumer‑Finance Terminology
Revolving credit : a single credit line used multiple times.
Credit quota : unsecured, collateral‑free credit amount based on user credit.
Credit application : white‑list (auto‑approval) vs. non‑white‑list (manual review).
Credit audit : verification of user data, credit status, repayment ability, and fraud risk.
Automatic approval : data‑driven scoring model.
Manual approval : expert‑driven assessment.
Credit usage : consumer spends against approved quota.
Fund settlement : periodic transfer of consumer payments to merchants via escrow.
User repayment : active repayment or automatic debit before due date.
Double‑entry bookkeeping : each transaction recorded as equal debit and credit entries.
Accounting subjects and entries : classification and recording of financial activities.
Non‑performing asset disposal : write‑off or sale of bad debts.
7. Conclusion
The article presents a minimal viable product design for a medical‑aesthetic consumer‑credit system, highlighting market opportunities, risk considerations, and a complete end‑to‑end architecture that blends fintech with the aesthetic industry.
ITFLY8 Architecture Home
ITFLY8 Architecture Home - focused on architecture knowledge sharing and exchange, covering project management and product design. Includes large-scale distributed website architecture (high performance, high availability, caching, message queues...), design patterns, architecture patterns, big data, project management (SCRUM, PMP, Prince2), product design, and more.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
