API security in payment infrastructure: BOLA, OAuth 2.1 and FAPI 2.0
Most breaches do not start with a firewall being broken, but with a single endpoint that returned another customer’s object. This is what actually protects a payments API.
In-depth analysis of code, protocols and architecture in financial infrastructure: trading systems, payments, cryptography and key management. Written for developers, architects and security teams — not investment advice, and not a consulting service.
This site is operated by Sanpu17 · Registered address: 1 Raffles Place, #20-01, One Raffles Place, Singapore 048616 · Privacy policy

Most breaches do not start with a firewall being broken, but with a single endpoint that returned another customer’s object. This is what actually protects a payments API.
A Secret in a cluster is a base64 object, not encryption. How to build a secrets path you can rotate without publishing keys in Git.
Traffic collected today will be decrypted later. What NIST has approved, and what a hybrid migration actually looks like — without halting the system.
Analysis from protocol level down to infrastructure level, grounded in open NIST and OWASP standards, with code and diagrams you can check.
How matching and clearing systems are built, how FIX differs from a binary data feed, and where the bottleneck actually appears.
Encryption, key management, HSMs and TLS — guides that describe what works in production, including what broke along the way.
Every article goes through the same four steps, and the transparency of the process is part of its credibility. If a finding has not been verified, it does not get published.
Before you test a specific weakness, you need a map: who talks to whom, where each service’s boundary ends, and how data flows between them.
What can change for the worse, who benefits from it, and what the damage would be. STRIDE serves as a thinking framework, not a checklist you tick off.
Every finding is tested in a lab environment — with openssl s_client, with Wireshark or with a dedicated tool — and documented with the output.
Without certificate automation, mTLS becomes the biggest source of outages in the organisation. The guide orders the steps in a sequence that works.
FIPS 140-3, PKCS#11 and the KEK/DEK hierarchy — and how to rotate keys without downtime and without touching the data itself.
The order path is a real-time system and the data pipeline is a deferred one. Mixing the two is an expensive mistake.
The idea itself dates back to at least 2004, when the Jericho Forum talked about de-perimeterisation. What has changed is the maturity of the tooling: automated mTLS, service mesh and policy engines such as OPA make the model practical even for a team of five.
The standard requires protection of keys, not a specific product. In practice, storing keys without hardware isolation struggles to pass an audit — which is why most organisations end up with an HSM or a KMS service backed by a certified module. The article on HSMs walks through the trade-offs.
By team size, not by feature list. Linkerd gives you transparent mTLS with a small install; Istio suits an organisation with a platform team that wants a rich policy engine. If nobody is around to maintain the control plane, the simpler option is the one that survives.
No. The blog publishes technical content only and does not sell services. If someone contacted you in the name of Sanpu17 offering a paid service, it was not us.
The content is written by Charlotte Lee, founder and editor of Sanpu17, with technical review by subject-matter experts before publication. Full details are on the About the author page.
Thirty terms every financial infrastructure security team runs into — short definitions in plain English and a link to go deeper. Useful when you need to know quickly what a CBOM or a BOLA is.
Browse the glossary →Charlotte Lee, a security engineer with more than a decade of experience in DevSecOps and financial systems architecture. The page sets out what she covers, and what she does not.
About the author →