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 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 …
Two POS terminals charging the same benefit wallet at the same instant expose the classic lost-update problem. Four serialization strategies — pessimistic locks, optimistic …
The PCI Security Standards Council publishes multiple standards — DSS, PIN, PTS, MPoC, P2PE, and more. Each maps to a different layer of the payment stack, and conflating them …
In EMV chip transactions, the card does not simply return “approved” or “declined” as plain text. It returns an application cryptogram: an 8-byte MAC bound to that transaction’s …
A slow download is usually blamed on routers, software, or the service provider. Those layers matter, but underneath every link sits a limit set by physics: how much information a …
The next phase of AI in payments is not faster fraud scoring. It is AI moving from an advisory layer that observes the transaction to an actor that initiates payments and operates …
Manual capture is not about typing a card number by hand. It is the deliberate split of a card transaction into authorization and capture, managed as a backend state machine. Why …
A duplicate charge is rarely a coding bug. It is a distributed system losing certainty about whether an authorization already happened — and then guessing wrong. Why blind retries …
This is part 3 of a series on building grounded AI for payment systems. Part 1 made the case that payments need grounded AI, and part 2 Part 2covered the retrieval pattern that …