Menu

1 / 3

Designing Idempotent Payment Microservices & Guardrailed LangGraph Dispute Agents

DEV Community: microservices·Raghuvendra Kumar·about 15 hours ago
#lfuk6oHH
#devtomicroservices#devto#dev#redis#ledger
Long article (1269 words) — no AI summary yet.
Reading 0:00
15s threshold

How I built **SentinelPay —a fault-tolerant double-entry ledger and stateful AI dispute resolver where the LLM scores risk, and plain code decides who gets their money back.

In banking software, two failure modes destroy trust faster than anything else: corrupting balances under concurrent retries , and letting a probabilistic AI model make deterministic financial decisions .

Most AI fintech demos wire an LLM straight to a refund endpoint and call it a day. I built SentinelPay to do the opposite—enforcing strict distributed-systems invariants at the ledger layer while keeping generative AI strictly inside an auditable, deterministic guardrail boundary.

Three Non-Negotiable Guarantees

Every architectural decision in SentinelPay flows from three invariants:

Money is never created, lost, or double-charged. Transfers execute inside a single PostgreSQL ACID transaction with deterministic row locks and two-layer Idempotency-Key enforcement.

A retry or traffic burst cannot degrade the ledger.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.