Understand the why.
Payments, banking and risk, from first principles. Start with how money moves, then learn to question what you see.
The life of a card payment.
Follow a €100 purchase from the checkout to the merchant’s payout.
Read the lessonWho does what in a payment?
Gateway, processor, acquirer, network, issuer: roles before logos.
Read the lessonWhen a payment is challenged.
Chargebacks, refunds and the work that happens after a sale.
Read the lessonOpen banking, without the mystique.
Permissioned access, account information and bank-to-bank payments.
Read the lessonFrom signal to evidence.
Learn to separate what you observed from what you believe it means.
Read the lessonWhat the queue cannot tell you.
Precision, recall and the customer cost of being wrong.
Read the lessonGive outcomes time to arrive.
Read disputes and cohorts without mixing their clocks.
Read the lessonThe person and the payment
A successful identity check is not a promise to pay.
Read the lessonA card number with boundaries
Understand what a payment token replaces—and what it does not.
Read the lessonUndo the right thing
Release a hold or return a completed payment: first identify the state.
Read the lessonOne intention. One payment.
Treat a timeout as uncertainty, not permission to charge again.
Read the lessonA message is not yet evidence
Receive payment events without trusting every incoming request.
Read the lessonThree records. One explanation.
Connect orders, processing records and cash without hiding differences.
Read the lessonThe second route is still a payment
Improve resilience without turning uncertainty into duplicate attempts.
Read the lessonOne purchase, several currencies
Keep the rate, the amount and the conversion moment together.
Read the lessonSolvent is not the same as ready
Available funds have a location, a currency and a deadline.
Read the lessonRead the full price of acceptance
Interchange is one component, not the entire merchant bill.
Read the lessonSeeing an account is not moving money
Separate access to information from authority to initiate a payment.
Read the lessonPermission has a lifecycle
Make the end of access as deliberate as its beginning.
Read the lessonSeconds change the operating model
When money moves quickly, decisions and recovery must be ready.
Read the lessonRules are not the same as rails
Separate the shared payment arrangement from the infrastructure carrying it.
Read the lessonA match is a useful boundary
Verify the destination without treating a name match as a verdict on intent.
Read the lessonPermission with a perimeter
Understand recurring payments through limits, purpose and customer control.
Read the lessonA balance needs a definition
Distinguish recorded value from the amount a customer can spend.
Read the lessonEvents arrive. State must make sense.
Build an explainable lifecycle instead of trusting the last message received.
Read the lessonDeliver twice. Apply once.
Separate transport retries from repeated business effects.
Read the lessonAnswer the allegation, not the inbox
Build a concise, relevant record for the specific disputed transaction.
Read the lessonThe rare-event trap
A strong detector can still create a mostly legitimate review queue.
Read the lessonWhat does confirmed really mean?
A model learns the labels you supply, including their blind spots.
Read the lessonA score is not a decision policy
Choose actions using consequences, capacity and uncertainty.
Read the lessonLook where the rule did not look
Audit the quiet population before declaring the controls complete.
Read the lessonThe next person should not start again
Turn an alert into a useful, bounded operational handoff.
Read the lessonRelated problems, different questions
Distinguish deception from the movement and concealment of criminal proceeds.
Read the lessonKnow the person. Understand the business.
Separate identity, control and the purpose of the relationship.
Read the lessonCollect for a reason
Make each field earn its place in the workflow.
Read the lessonProtected in which way?
The institution, the product and the failure event all matter.
Read the lessonThe name is a lead.
Resolve an alert through identifiers, evidence and accountable review.
Read the lessonA field has a meaning.
Richer messages help only when their information survives the journey.
Read the lessonWho starts the collection?
Separate a biller’s mandate from the payer’s scheduled instruction.
Read the lessonAccess is part of the control.
Give each operational role the actions it needs—and verify the boundary.
Read the lessonDo not let the model see tomorrow.
Evaluate using information that actually existed at decision time.
Read the lesson