Design System Engineering

Design System Engineering, here, means designing payment and security systems end to end — not UI kits. Channels, orchestration, cryptography, acquiring rails, and the operational layer that keeps money and audit trails consistent.

I work on this stack at MultiSafepay (part of Ant Group). Corebaseit is where I document the architecture thinking — so the expertise is visible, not packaged as a service offering.

What this site covers:

POS and card-present acceptance — terminals, SoftPOS, TMS, switch adapters
Payment architecture — authorization, wallet/ledger models, orchestration, scheme routing
Security controls — HSM clusters, PIN, signing, tokenisation, key management
End-to-end system design — how ecosystem, channels, platform, crypto, and ops fit together

The diagram below is a system-level view. Detail lives in the layer table; the picture only shows how the major planes connect: ecosystem → channels → platform → payment infrastructure → finance & ops, with security on the payment path.

Reference architecture


flowchart TB

    ECO["Customer ecosystem
Employer · Consumer · Merchant · Partners"]
    CH["Channels
Portal · Wallet · POS · Checkout · APIs"]
    PL["Payments platform
Identity · Eligibility · Wallet · Orchestration · Risk · Ledger"]
    INF["Payment infrastructure
TMS · POS switch · Acquirer · Card / bank / A2A rails"]
    SEC["Security plane
HSM · PIN · Signing · Tokenisation · Keys"]
    OPS["Finance & operations
Clearing · Settlement · Recon · Reporting · Monitoring"]

    ECO --> CH
    CH --> PL
    CH -->|"Card-present path"| INF
    PL --> INF
    PL <-->|"Crypto on the payment path"| SEC
    INF <--> SEC
    PL --> OPS
    INF -->|"Rails & settlement feeds"| OPS

Click diagram to expand

How to read the layers

Layer	Job in a payment system
Customer ecosystem	Who funds, who spends, who accepts, who integrates
Channels	Where intent enters — portal, wallet, POS, checkout, partner APIs
Payments platform	Identity, eligibility, balances, orchestration, risk/limits, ledger
Payment infrastructure	TMS, POS switch, acquirer/processor, card / banking / A2A rails
Security plane	HSM (keys, PIN, signing), tokenisation — shared by platform and POS path
Finance & operations	Clearing, settlement, reconciliation, reporting, monitoring / audit

Security is not a side box. It sits on the payment path for both digital orchestration and the card-present switch. Ops closes the loop from ledger and rails so payout and audit stay consistent.

Where this shows up in practice

POS path: channel → TMS / switch → platform — SoftPOS and traditional devices meet at the infrastructure boundary
Orchestration & risk: policy and ledger posting before money moves on external rails
Crypto boundary: HSM-backed PIN, keys, and signing; tokenisation as the control plane for sensitive material
Money lifecycle: ledger + rails → clearing / settlement → recon and merchant payout

For the book-length treatment of POS stacks, EMV, and scheme-facing messaging, see Point-of-Sale Systems Architecture. For field notes, start with the POS, Security, and Architecture categories.