Flair BuchiMiracle Okonkwo

WritingApril 2026

A Checkout Quote Is a Promise

Once a payer is shown commercial terms, accepting the quote must create payment work from those terms, not from whatever live pricing says a moment later.


A payer sees a number on a checkout screen.

They decide to pay it.

Somewhere between that screen and the payment the system creates, a quiet question appears: was that number an estimate, or was it the amount checkout actually promised?

Building hosted checkout for merchants at Xpend B2B forced us to answer that question in code, not in UI copy.

If the answer is “estimate,” then clicking Pay can become a second pricing event. Rates move. Fee configuration changes. Merchant adjustments update. The amount on the next screen may no longer match the amount that persuaded the payer to continue.

If the answer is “promise,” acceptance has to consume the terms already shown.

We chose promise.

The Number on the Screen

A checkout quote is not a number waiting to be recalculated later.

When a client requests a quote, the system resolves live commercial inputs at that moment: amounts, assets, rates, fees, merchant adjustments, and the checkout context that produced the request. That work is price discovery. It belongs at quote creation.

The payer then sees a result of that discovery. A crypto amount. A fiat outcome. A rate that already includes the adjustments the merchant configured.

The failure mode is easy to invent and hard to forgive. Recalculate everything when the payer accepts. Re-read the market. Re-apply pricing config. Create payment work from whatever the system believes now.

From the payer’s point of view, the number moved after they agreed to it.

From the merchant’s point of view, the checkout stopped honoring the number the payer had already agreed to.

Price Discovery and Obligation Are Different Operations

Quote creation asks: given current pricing and context, what commercial terms should we show?

Acceptance asks: given the quote the payer saw, what payment work should we create?

In our checkout flow, quote creation resolves live pricing and persists the terms that were shown, with an expiration time.

When the payer accepts, the acceptance flow checks that the quote is still valid, then creates the payment work from those accepted terms.

Price discovery ends when the quote is issued. Obligation creation begins when it is accepted. Those stages should not silently collapse into one.

Freeze the Terms

A quote that can be reinterpreted later is not a quote. It is a draft.

So we persist a snapshot of the quoted terms when the quote is created: the commercial amounts, rates, fees, assets, and checkout context shown to the payer.

The snapshot is not an audit souvenir. We persist the terms that were shown instead of expecting the system to reconstruct them later. That gives acceptance a stable baseline to work from.

That freeze is the product promise in storage form.

Acceptance Should Consume the Quote

The acceptance flow makes sure an active quote can only be accepted within its valid window.

Then it creates the payment work from the accepted quote. Amounts and assets come from what was quoted, not from a fresh rate lookup. The checkout context that mattered when the terms were shown can travel forward without asking the merchant to restate the deal.

Acceptance turns a shown quote into payment work. It does not reopen price discovery because a few seconds passed.

The Small Detail That Matters

There is a detail on the acceptance path that shows how seriously we take that baseline.

Crypto assets have different decimal precision. When a quoted amount has to be represented using the precision supported by the asset, we round in the direction that cannot reduce what the payer was shown.

It is a small implementation detail, but that is where product decisions become real. The system should not preserve a quote in storage and then quietly weaken it when turning that quote into payment work.

A Quote Still Expires

Freezing terms does not mean prices are valid forever.

Each quote has an expiration time. Acceptance rejects expired quotes. The promise has a clock.

Inside the quote’s life, the commercial terms stay stable enough for a payer to act on them. Outside that life, the market and merchant pricing configuration are free to move again. The next quote request can discover prices anew. The previous quote cannot be accepted as if time had not run out.

Stability without expiration would pretend markets and pricing configs never change. Expiration without a freeze would make every refresh a possible renegotiation. Checkout needs both: a bounded promise, then a clean stop.

The Checkout Is Now a Handoff

Once the quote is accepted, its job is mostly done.

Payment work takes over. The payer pays. The normal payment process continues from there.

Those later stages matter. They are also a different problem. The quote’s responsibility is to hand a known commercial baseline into obligation creation.

The resulting checkout has its own public link. The quote promised terms. The checkout is where payment progresses.

What the Number Meant

Return to the screen.

The payer saw a number produced by live price discovery. They chose to accept it. During that quote’s lifetime, the system owes that number coherence: acceptance should create payment work from those terms, not reopen discovery because a few seconds passed.

When software shows someone a commercial term and asks them to act on it, that term needs a defined lifecycle. Price discovery can be live. Obligation creation should not silently become a second round of discovery. Freeze what you showed. Bound how long the freeze lasts. Then create the work from the promise you actually made.

A checkout quote is a promise. Treat it like one.