
The MVP That Never Ships: When the Finish Line Keeps Moving
An MVP that absorbs every new request stops being a learning instrument and becomes an unbounded delivery programme. The core journey may already work. Pilot users may already be …
Design system engineering · POS · Payments · Security
I’m Vincent Bevia. I work in payments at MultiSafepay (part of Ant Group), and I’ve spent years on design system engineering for POS, payments, and security — architecture, EMV, cryptography, and the infrastructure behind card-present and digital acceptance. I’m the author of Point-of-Sale Systems Architecture and The Obsolescence Paradox.
This site is where I write about payment platforms as systems: channels, orchestration, HSM and tokenisation, acquiring rails, and the ops layer that makes settlement and audit trustworthy. Also AI in payments, and the EE / telecom foundations underneath.
Less corporate, more personal. Opinions, reflections, and the kind of things I’d talk about over coffee.
If you’re into payment platforms, POS, or security architecture — or just curious how the pieces fit — welcome.
Latest field notes

An MVP that absorbs every new request stops being a learning instrument and becomes an unbounded delivery programme. The core journey may already work. Pilot users may already be …

A monolith can become difficult to change long before it becomes impossible to run. Deployments start affecting unrelated areas. A change in refunds requires regression testing …

System design discussions often collapse into technology comparisons: Kafka or SQS, PostgreSQL or DynamoDB, synchronous or asynchronous, monolith or microservices. Those choices …

Latency differences between scheme or product types are a recurring operational problem in SoftPOS and SmartPOS acquiring. Visa authorizations complete quickly. Mastercard Debit …

When Offline Data Authentication (ODA) fails, replacing Certification Authority Public Keys (CAPKs) at random is rarely productive. Most field failures sit earlier in the chain: …

ISO 8583 defines up to 128 data element positions. Treated as a flat numbered list, they are hard to reason about. Grouped by function — the way working engineers already inspect …

EMV is often treated as a solved security problem. Billions of cards, decades of deployment, and strong cryptography create the impression that the protocol is fundamentally sound …

Fraud-detection papers regularly report near-perfect accuracy on public datasets. Almazroi and Ayub’s 2023 IEEE Access paper is a recent example: a ResNeXt-embedded GRU …

An EMV contact decline is not a single error. It is the outcome of decisions made by the terminal, the card, or the issuer at different stages of the transaction. Treating …

EMV authorization is the easy part. The hard problems are timeouts, retries, SoftPOS lifecycle gaps, store-and-forward declines, and the financial question that remains when two …