FinTech Platforms

2.20.1Definition & Purpose

FinTech platforms manage, move, or provide insight into users' money — banking, payments, lending, investing — operating under financial regulation that shapes the product as much as user needs do. Unlike most product categories in this Part, compliance is not a constraint layered on top of the product; it is frequently the product's actual shape.

2.20.2Architecture Priorities

Auditability and precise transaction records are non-negotiable — every balance change must be traceable and reconcilable, typically via an append-only ledger pattern rather than simply updating a balance field in place. Security requirements (encryption at rest and in transit, strict access controls) are typically mandated by regulation, not optional hardening.

2.20.3UX Priorities

• Absolute clarity around fees, terms, and transaction status — ambiguity here creates both user harm and regulatory exposure.
• Strong, visible security signals (biometric/2FA options) to establish trust with money-handling products specifically.
• Accessible, clear error and dispute-resolution paths for failed or disputed transactions.

2.20.4Common Mistakes

• Treating compliance as a legal afterthought layered on after the product is built, rather than a foundational design constraint from day one.
• Mutable balance fields instead of an auditable transaction ledger, making reconciliation and dispute resolution unreliable.

2.20.5Best Practices

• Model money movement as an append-only ledger of transactions, deriving balances from that ledger rather than storing and mutating a balance directly.
• Involve compliance and legal review from the earliest architecture decisions, not just before launch.