Grokking Modern API Design Interview
Vote

0% completed

​

Capstone: Design a Payment API

Payments make every hard API question visible.

A timed-out create may charge twice. A valid credential may still belong to the wrong merchant. A processor may receive a request and never answer. Two support agents may refund the same remaining amount at the same time. A cached response may show money that is no longer available.

The API cannot answer those problems with "eventual consistency," "secure tokens," or "we retry." Each one needs exact caller behavior.

This capstone designs the payment API using the same six steps and every convention published in Chapters 2 to 4

.....

.....

.....

Like the course? Get enrolled and start learning!