What I look for while evaluating a payment system!For me, evaluating a payment system rarely starts with the architecture design. Not because architecture is unimportant, but most systems look reasonable in a diagram and the interesting information i1May 14 · 5 min readkratikajain.com
Every serious payment system needs a double-entry ledgerMost fintech engineering teams build a payments table first and a ledger later. Usually after: first reconciliation break first support ticket that cannot be answered the first settlement discrepan13May 11 · 11 min readkratikajain.com
The PSD2 participants mapA single payment flow, like customer paying at an outlet, can involve five different types of participants; each with different system boundary, security requirements, data obligations, and liability May 10 · 6 min readkratikajain.com
Your hero-engineer might be your biggest operational risk!There is a type of engineer almost every company has. The person who gets pulled into every serious incidents, knows which service is actually failing just looking at the dashboards, or who can SSH atMay 10 · 5 min readkratikajain.com
Do you need a PSD2 licence?Start from here One of the easiest mistake by a payments/fintech startup is to start with the product flow and leave the regulatory model for later. This may sound practical at the beginning to buildMay 9 · 9 min readkratikajain.com