Skip to content

The blog / Fintech & technology

Notes from the systems
that move money.

Practical perspectives on payments, architecture, security, AI, and engineering leadership. Collected from my LinkedIn writing and technical carousels, with original PDFs to explore.

29 Articles & perspectives18 Downloadable PDFsFollow on LinkedIn ↗

Showing 29 articles

Cover of Your cheapest payout partner may be your most expensive route.

PaymentsPDF included

Your cheapest payout partner may be your most expensive route.

Compare FX, funding, and settled costs before choosing a payout route.

Cover of Valid signature. Wrong payment state.

SecurityPDF included

Valid signature. Wrong payment state.

A genuine callback still needs identity, amount, currency, state, and ledger checks.

Cover of Approved for A. Paid to B.

SecurityPDF included

Approved for A. Paid to B.

An approval should authorize a fixed instruction, not a beneficiary profile that can change.

Cover of One customer. Two payouts. One avoidable loss.

PaymentsPDF included

One customer. Two payouts. One avoidable loss.

Why an unknown outcome should block a blind retry through another partner.

Cover of Your API works. Can a partner use it?

EngineeringPDF included

Your API works. Can a partner use it?

Measure the path from sandbox access to a successful, traceable test payment.

Cover of Your payment works. Can the business run on it?

ArchitecturePDF included

Your payment works. Can the business run on it?

Connect compliance, finance, promotions, reporting, and payment operations.

Cover of Build a payment system, not only a transfer screen.

ArchitecturePDF included

Build a payment system, not only a transfer screen.

The production architecture behind controlled money movement.

Cover of Smart contracts as settlement controllers.

BlockchainPDF included

Smart contracts as settlement controllers.

A hybrid architecture for locking funds, verifying outcomes, and reconciling settlement.

Cover of Compliance belongs inside the payment lifecycle.

CompliancePDF included

Compliance belongs inside the payment lifecycle.

Versioned policies, explainable decisions, review cases, and execution gates.

Cover of A transaction status is not the money truth.

LedgersPDF included

A transaction status is not the money truth.

One ledger can support finance, reconciliation, treasury, and revenue.

Cover of Every fintech needs a transaction control layer.

ArchitecturePDF included

Every fintech needs a transaction control layer.

Visibility, recovery, and operational evidence around every payment.

Cover of A failed transaction should never be a black box.

PaymentsPDF included

A failed transaction should never be a black box.

Make the failure location, financial state, and recovery path visible.

Cover of KYC is more than an ID upload.

CompliancePDF included

KYC is more than an ID upload.

Connect document checks, identity evidence, risk signals, and review.

Cover of Language should not be a barrier to remittance.

AI & DataPDF included

Language should not be a barrier to remittance.

A conversational interface still needs a controlled payment system underneath.

Cover of One payment rail is not enough as complexity grows.

PaymentsPDF included

One payment rail is not enough as complexity grows.

Orchestration connects availability, liquidity, cost, and recovery.

Cover of Build control before scaling the volume.

LeadershipPDF included

Build control before scaling the volume.

More transactions create more edge cases, handoffs, and financial questions.

Cover of In fintech, reliability builds trust.

LeadershipPDF included

In fintech, reliability builds trust.

Clear states and dependable recovery matter after the launch announcement.

Cover of Where specialist fintech engineering helps.

EngineeringPDF included

Where specialist fintech engineering helps.

Architecture reviews, complex integrations, production recovery, and financial visibility.

BP / FIELD NOTESPayments

PaymentsArticle

What if a remittance arrived ready to spend?

An architecture idea connecting a regulated local wallet and payment card.

BP / FIELD NOTESAI & Data

AI & DataArticle

An AI agent needs payment authority, not just a tool.

Identity, explicit consent, limits, revocation, and audit evidence for agentic workflows.

BP / FIELD NOTESAI & Data

AI & DataArticle

Forecast demand before liquidity becomes the bottleneck.

Historical activity and corridor patterns can inform operational planning.

BP / FIELD NOTESAI & Data

AI & DataArticle

Use AI to improve the fraud investigation workflow.

Extract context, connect related evidence, and explain risk to reviewers.

BP / FIELD NOTESBlockchain

BlockchainArticle

The stablecoin opportunity is also in the plumbing.

Wallets, custody, compliance, orchestration, and settlement infrastructure.

BP / FIELD NOTESArchitecture

ArchitectureArticle

Reuse the architecture behind the next corridor.

Shared connectivity helps when the platform can handle local differences.

BP / FIELD NOTESArchitecture

ArchitectureArticle

Fintech directions: a look back at my 2023 article.

AI, connected financial services, and programmable rails through an engineering lens.

BP / FIELD NOTESSecurity

SecurityArticle

Fraud monitoring starts with connected signals.

Behavior, identity, device, and transaction evidence work together.

BP / FIELD NOTESAI & Data

AI & DataArticle

AI in cross-border payments: the operational opportunity.

A look back at my August 2025 article on decision support in payments.

BP / FIELD NOTESEngineering

EngineeringArticle

High-traffic PHP APIs: start with the workload.

A retrospective on database queries, connection pressure, and production tuning.

BP / FIELD NOTESSecurity

SecurityArticle

Fast, secure, and reconcilable belong together.

Combine authenticated APIs, controlled state changes, financial records, and operational evidence.

From an idea to an implementation

Have a similar challenge?