Fundamentals 7 min read

Design and Architecture of the Three‑Entity Account System in Financial Technology

The article explains the three‑entity (customer, user, account) account model, its architectural layout, and how it supports diverse fintech scenarios such as marketing, risk control, intra‑ and inter‑business line operations, and external service provisioning.

JD Tech Talk
JD Tech Talk
JD Tech Talk
Design and Architecture of the Three‑Entity Account System in Financial Technology

Account systems are a core module of financial services; a well‑designed system not only supports innovative business models and integrates various play‑styles, but also enables external technology services. The three‑entity model (customer, user, account) links real‑world persons, login credentials, and account management for unified handling, allowing account aggregation independent of login barriers and improving user experience.

Background: Modern third‑party payment, consumer finance, and e‑commerce innovations all rely on robust underlying account designs, covering payment cards, balances, coupons, credit accounts, membership tiers, risk strategies, and marketing rules. Most companies base their designs on the three‑entity model.

Three‑Entity Architecture

1. Customer – Represents natural persons or legal entities (individuals, enterprises, merchants) independent of third‑party attributes, verified by legal documents such as ID cards, passports, or business licenses. A single person may hold multiple accounts across platforms.

2. User – The account‑level entity tied to third‑party platforms, containing login credentials, nickname, level, contact info, etc. One user can own multiple accounts and holds basic identity information.

3. Account – Manages monetary information (balances, ledgers). In fintech, these are typically virtual accounts linked to accounting systems (single‑ or double‑entry). Payment platforms often use master‑sub account structures to aggregate funds across scenarios.

Business models built on the three‑entity system:

Marketing – Rules can be applied at the customer level (e.g., membership marketing) or user level (e.g., registration incentives). Multiple accounts per user enable differentiated or unified marketing strategies.

Risk Control – The model allows granular risk management across layers; for example, a bad‑debt flag on an account can propagate to the associated user and customer, enabling linked risk controls.

Intra‑Business Line – Enables complex scenarios such as a customer using an account created under a different user, facilitating account migration or authorization and improving cross‑account experiences.

Inter‑Business Line – Shared customer information across business lines allows unified management of users and accounts, breaking silos between different services.

External Output – Unified customer management supports joint risk assessment and credit granting across fintech firms, and can generate new financial products (e.g., QR‑code payments) based on categorized account types.

Conclusion: As financial markets evolve, refining the underlying account design—often based on the three‑entity model—remains a vital research topic. Decoupled designs facilitate marketing, risk control, and cross‑line innovations, while also enabling seamless external integrations and new business opportunities.

risk managementmarketingFinTechfinancial technologyaccount architecturethree-entity model
JD Tech Talk
Written by

JD Tech Talk

Official JD Tech public account delivering best practices and technology innovation.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.