Topic Hub

API architecture

Curated insights and technical field notes on API architecture.

Reader guide

Start with the newest decision note, then follow the topic lanes when you need payments, AI systems, or product architecture depth.

Decision notes

Clear recommendation, rejected paths, and proof trail.

Systems maps

Visual artifacts sit near the section they explain.

Source posture

Public claims stay tied to released work or cited material.

Architecture

Payment platforms have docs. Almost none have a developer experience

Payment integration usually starts with a PDF, a sandbox that takes days to provision, and a support email that answers in 48 hours - and the third email is where patience dies and a competitor gets Googled. I built a self-service workbench to close the distance between what a platform can do and what a developer can figure out alone.

Lead essay

Start here when you want the current Doric argument instead of a 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

Jul 15, 2025 By Navin Agrawal AI systems 3 min read

Payment APIs are having their USB-C moment with MCP

Most payment integrations still look like 2015 - custom code per platform, months-long builds. The Model Context Protocol turns MxN integrations into M+N, and payment platforms are starting to ship it. The promise is real; so are the enterprise security gaps.