Topic Hub

Payment architecture

Curated insights and technical field notes on Payment architecture.

Current note

The winning payment token may disappear at settlement

The newest published argument and its visual artifact lead the page.

Editorial posture

The library is organized around decisions that keep recurring in payment architecture, AI systems, and Doric product work. New notes lead by publish date, while topic lanes connect related arguments without turning the index into an archive wall.

Decision frame

Recommendation, rejected paths, and the operating proof behind the call.

Visual proof

Diagrams and original artifacts stay near the argument they explain.

Source posture

Public claims stay tied to released work or cited material.

Payments

The winning payment token may disappear at settlement

In one week of August 2026, the ECB, the RBA, and the BIS pushed the same pattern toward infrastructure design: customer instruments can compete on programmable networks while a central-bank asset closes the interbank obligation underneath. The architecture decision is to model the instrument, the network, the bridge, and the anchor as four separate choices.

Lead essay

The current Doric argument leads the index ahead of the chronological archive.

Read the note

01 / Payments

Commerce architecture

Merchant-of-record decisions, checkout ownership, billing operations, settlement, reconciliation, and risk boundaries.

02 / AI tooling

Practical AI systems

Agentic commerce, multi-agent orchestration, model fine-tuning, runtime governance, and production deployment.

03 / Build notes

From idea to system

The design, architecture, and operating decisions behind Doric Stack products as they move from prototype to public release.

Latest Notes

All

May 20, 2026By Navin AgrawalPayments3 min read

Under a second is the right answer to the wrong question

At an AWS Bedrock AgentCore Payments session the question was what happens at a thousand transactions a second, and the answer was settlement in under a second. Both are true and they answer different questions. The right frame for one payment crossing a trust boundary is the wrong frame for a million events a day inside one agent fleet, where the chain fee stacks up before anything else does.

May 4, 2026By Navin AgrawalAI systems4 min read

Most AI agents never reach production. Payments is where that gets expensive

The widely cited figure is that 88 percent of AI proofs of concept never reach production. Agentic payments inherit that gap, and the teams that cross it are not winning on model selection. They are winning on payments-specific infrastructure that makes an agent idempotent, governable, and rollback-safe at the rail boundary.

Feb 23, 2026By Navin AgrawalArchitecture3 min read

A multi-rail exception mesh, not best-effort dedupe

A duplicate payment in production is not an edge case. It is the control plane showing you what you never modeled. A retried request can land as a final success on one rail and a settlement reject on another, look clean on the dashboard, and still move two accounts twice. Best-effort dedupe is not a control.