Use “Observe a quote payment” in Recued. It carries out the named workflow using the connections and settings you choose.
Observe a quote payment
Use “Observe a quote payment” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Use Seller Quote Request in Recued for unspecified pricing, estimate, order, and reception. It includes 7 built-in actions and 4 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Open a quote request” in Recued. Exact-form template that turns one owner-accepted Reception intake response into an order awaiting your price, and records the request itself in the pack's own Records storage. Changes remain behind Recued's approval controls.
Use “Price and send a quote” in Recued. Pin your price onto a waiting quote request, then send the customer a payment link for exactly that figure.
Use “Quote board” in Recued. Every quote request against one offer, with the two things you act on: which ones are still waiting for your price, and which ones you have priced and are waiting on the customer. It reads information without changing data in the connected service.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
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.
- Install alongside Seller Quote Request and enrol the same Stripe connection the pricing recipe uses.
- Bind the
quote_payment_eventswebhook and subscribecheckout.session.completed+checkout.session.async_payment_succeeded(the async one matters for delayed methods — a bank debit completes minutes or days later). - Set Sender account if you want the customer to get a confirmation from you as well as Stripe's own card receipt.
⚠ 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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
stripe
setting
=
sender mail instance
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.