Industry Insights 24 min read

Why Copying Proven Account System Designs Beats Building From Scratch

The article analyzes real‑world account system architectures across online car rental, offline amusement, tourism stores, housekeeping, ETC, e‑commerce points, and bank acquiring, showing how reusing validated designs reduces development cost, improves reliability, and adapts to diverse business models through configurable rules and multi‑account handling.

Chen Tian Universe
Chen Tian Universe
Chen Tian Universe
Why Copying Proven Account System Designs Beats Building From Scratch

01. Online Car Rental – Design Overview

Online car‑rental SaaS platforms match vehicle‑rental merchants with renters, handling payment, refunds, and settlement. The system provides account opening, balance queries, and transaction flows. It distinguishes frozen and usable balances: frozen balances record receivable/payable entries, while usable balances reflect actual funds from third‑party payment accounts. Account updates follow a task flow where each entry must complete all steps or be rolled back.

02. Offline Amusement – Account Needs

In the offline amusement industry, roles include equipment manufacturers, content creators, brand owners, and franchisees. Two business models exist: (1) brand owners package equipment and content for franchising, and (2) brand owners act as a platform linking manufacturers, content creators, and franchisees. The article focuses on the first model, where the brand builds a self‑service management system that offers cash‑register capabilities, revenue‑sharing settlement, and reporting.

Revenue sharing can be time‑based or per‑use, independent of order amounts. Two settlement modes are described: a prepaid model where franchisees receive a prepaid account and the brand settles manually, and a split‑account model where a third‑party institution holds brand and franchisee accounts, with the system only recording data.

03. Tourism Stores – Account System

Tourism‑store SaaS platforms enable franchise stores to handle deposits, product bookings, after‑sale services, penalties, etc. Payments flow from customers to the head office, then to store wallets, and later from stores to the head office for profit sharing. The system also supports credit‑score accounts that can restrict store ordering when balances fall below thresholds.

04. Housekeeping – Account System

Housekeeping platforms match service providers (e.g., nannies, cleaners) with consumers. The system must settle service fees for workers, commissions for introducers, and revenue for channel partners. Multiple account types are created: worker income accounts, partner profit‑sharing accounts, and deposit accounts for guarantees.

05. ETC – Wallet System

ETC wallets store prepaid balances for highway tolls. Users must recharge before travel; otherwise, the wallet goes negative and may be placed on a restriction list. Negative balances trigger a deposit wallet for overdue penalties. Operators may also provide subsidy wallets for promotional discounts.

ETC transaction rules are hard‑coded; however, when business scenarios expand, configurable rule engines allow flexible assignment of amounts, freezing, and unfreezing across multiple accounts.

06. E‑commerce – Points Account System

Points‑based e‑commerce platforms issue both points and cash accounts for merchants. Points accounts handle discount calculations, while cash accounts record actual monetary settlements. Order fulfillment triggers accounting entries: cash flows to merchant cash accounts, points flow to merchant points accounts, and platform fees are calculated from product‑level point ratios.

07. Campus Card – Account System

Campus card platforms manage student recharge and consumption for meals, utilities, and other services. The core account center provides account opening, balance queries, and transaction logs. Accounts are hierarchical based on account subjects, enabling clear bookkeeping.

08. Bank Acquiring – Account Architecture

Bank acquiring systems involve settlement accounts, internal accounts, and virtual accounts. Settlement accounts are merchant‑owned, internal accounts are bank‑controlled transition accounts, and virtual accounts record multi‑scenario bookkeeping without touching real funds.

The acquiring platform creates a multi‑level account hierarchy, voucher management, and automated rule‑based bookkeeping to support new business lines without code changes.

Payment, split‑payment, settlement, and withdrawal flows are illustrated with concrete examples (e.g., a user pays 1000 CNY via WeChat, the platform splits 900 CNY to the merchant and 100 CNY to the platform). Settlement occurs T+1, and withdrawals are routed through a regulated bank account, ensuring fund safety.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

SaaSaccount systemtransaction processingfinancial servicespayment architectureindustry case study
Chen Tian Universe
Written by

Chen Tian Universe

Chen Tian Universe, payment architect specializing in domestic payments, global cross‑border clearing, core banking, and digital payment scenarios. Notable works: “Ten‑Thousand‑Word: Fundamentals of International Payment Clearing”, “35,000‑Word: Core Payment Systems”, “19,000‑Word: Payment Clearing Ecosystem”, “88 Diagrams: Connecting Payment Clearing”, etc.

0 followers
Reader feedback

How this landed with the community

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.