Closing the loop

Without this recipe a quote reaches awaiting_payment and stops: core.seller.order.confirm-payment is the only route to paid, and it needs provider evidence that only a webhook-scoped run can gather.

1. Install Seller Quote Payment Events. If Seller Quote Request is not installed yet, the same dialog lists it under the packs it brings in: choose Read + write for it. Its own workflows open and price requests, and Read only refuses them. (If the dialog does not list it — a server older than this feature — install Seller Quote Request first, with Read + write.)
2. The install asks you to pick the Stripe webhook ingress that quote_payment_events listens on — enabled, paired with your Stripe connection, and subscribed to checkout.session.completed + checkout.session.async_payment_succeeded (the async one matters for delayed methods — a bank debit completes minutes or days later).
3. Use the same Stripe connection the pricing recipe uses.
4. Set Sender account if you want the customer to get a confirmation from you as well as Stripe's own card receipt.

⚠ Why this lives in its own pack. Seller Quote Request keeps its requests in pack-owned Records storage, and a Records pack cannot carry a webhook binding — its install promotes storage atomically and a webhook sidecar cannot join that. Until this recipe moved here, quote_payment_events had nowhere to be bound, so a paid quote never reached paid.

⚠ The webhook payload is never the evidence. Every figure that authorizes the transition comes from a fresh Session read over your connection. That is why an attacker who could forge a delivery still cannot mark an order paid.

⚠ Offline payments do not come through here. A cheque or bank transfer produces no Stripe session, so no evidence can exist and the order stays in awaiting_payment by design — paid is evidence-backed on purpose. Track that work on the job board instead of forcing it through an order.