How I Built Nexorate's Checkout Flow

When I started on Nexorate's checkout, the brief looked simple: let a buyer purchase from multiple sellers in one order. In practice that meant every payment had to be split at the point of capture, not after — refunds, disputes, and payouts all depend on getting that right from day one.

I ended up modeling each cart as a collection of sub-orders, one per seller, all tied to a single payment intent. That kept the buyer's experience — one cart, one checkout, one confirmation — while giving the backend clean boundaries for accounting and payouts later.

The part that took the longest wasn't the payment logic, it was the failure states: what happens if one seller's item goes out of stock mid-checkout, or a payout account isn't verified yet. Most of the actual engineering time went into handling those gracefully instead of just the happy path.

Loading comments…