payinOPERATIONS MANUAL

READ BY RESPONSIBILITY

Follow the work.

A shared operating language for engineering, support and finance.

Latest articles

Three new operating guides: checkout expiry and inventory, private response caching, and authorization capture deadlines.

  1. 01

    Checkout expiry is an inventory decision, not just a countdown

    An editorial operating guide to aligning Stripe-hosted Checkout expiration with scarce-stock reservations, release decisions, and exception handling.

    · New article

  2. 02

    Can a checkout response be cached? Separate public assets from private payment state

    Distinguish no-cache, no-store and private, then test checkout responses across browsers and shared caches without confusing caching policy with authorization.

    · New article

  3. 03

    Manage authorization capture as a deadline-bound decision

    An editorial guide to Stripe authorization deadlines, eligible payment methods, partial capture, and operational decisions before a monetary hold expires.

    · New article

Latest articles

Three new operating guides: amount precision, query retry budgets and address-poisoning checks.

  1. 01

    Integer or decimal payment amounts? Precision and rounding boundaries

    Define currency scales, exact calculations, rounding steps and remainder allocation, then protect payment amounts across API, JSON and database boundaries.

    · New article

  2. 02

    Payment lookups returning 429 or 503: backoff, retry budgets and recovery

    Protect read-only payment queries with Retry-After handling, jitter, total deadlines and aggregate retry budgets, then restore load gradually.

    · New article

  3. 03

    Stablecoin address poisoning: checks before copying a past recipient

    Replace trust in transaction history with authenticated payment instructions, full-address comparison and separate network and asset checks.

    · New article

Design the collection flow

Hosted or self-hosted: decide who owns the midnight incident →Order payments or deposit addresses? Model the business event first →

Operate reliably

Visible onchain is not the same as ready to fulfill →Two webhook deliveries must not become two fulfillments →

Close the loop

Write the stablecoin refund policy before the first sale →Reconcile the order, the transfer and the business result →