Skip to content
Jalel Dridi
All work

Potluck · 2026

Payments on Stripe Connect

Checkout, transfers, payouts, webhooks and reconciliation for a two-sided marketplace.

bigpotluck.com/how-it-works
Potluck's How it works page, with four steps for customers and four for chefs
How Potluck works: customers pay when they order, and the chef is paid after pickup.

Why it existed

I own the payments stack: checkout, transfers, payouts, webhooks and reconciliation. In a marketplace, every one of those has to be right for both the buyer and the seller.

What I built

  • An order is marked paid only after the payment is verified server-side against Stripe, with inventory decremented exactly once.
  • Checkout validation that rejects client-supplied prices, items no longer on sale and quantities above stock, covered by a suite of attack tests.
  • Alerts for failed and stuck payouts.
  • A daily reconciliation of the database against Stripe that classifies every mismatch by cause.

Outcome

Payout Ledger is a from-scratch public rebuild of these ideas. It shares no code with Potluck.

On screen

A product page on a phone: a chocolate chip cookie at five dollars, with pickup or delivery and an Add to cart button
A product page. The price shown is set on the server, never taken from the client.

How it fits together

Nothing the client sends is trusted: the server verifies with Stripe before an order is paid.
NextRealtime messaging