Use “Start paid document fulfillment” in Recued. It carries out the named workflow using the connections and settings you choose.
Start paid document fulfillment
Use “Start paid document fulfillment” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Use Paid Document Fulfillment in Recued for transactional offer, paid workflow, form response, and payment. It includes 10 ready-to-run workflows and 4 related packs in one install.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Reconcile document payments against Stripe” in Recued. Owner-attended payment sweep - the manual safety net under the webhook observer.
Use “Reconcile a paid document refund” in Recued. Owner-attended refund close for one order.
Use “Inspect a paid document dispute” in Recued. Owner-attended read-only inspection binding one Stripe Dispute to one order.
Use “Generate paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Review paid document artifacts” in Recued. It carries out the named workflow using the connections and settings you choose.
Show all 11 recipes
Use “Approve and deliver paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Reconcile paid document delivery” in Recued. Owner-attended mail-claim reconciliation for one order's two sends: the checkout-link mail (start) and the delivery mail (approve-deliver).
Use “Reject or cancel paid document” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Reconcile and expire paid document fulfillments” in Recued. Manual order sweep.
Use “Close and archive a paid document fulfillment” in Recued. Owner-attended close for one order that never took money: draft, pricing, awaiting payment (verified unpaid at Stripe by a fresh read of its own session), or expired moves to cancelled. A session the provider reports paid refuses loudly - run the payment sweep instead.
One paid outcome, not an access tier
This is the inert entry template for the complete Paid Document Fulfillment pack. One owner-accepted form response can become one provider-verified payment, one reviewed PDF, and one governed delivery. The Marketplace install intent resolves to the full workflow pack or fails closed; it never installs this recipe alone and does not create a Seller access tier, customer token, entitlement, or usage row. It also creates no Seller outcome offer unless the saved recipe explicitly opts in and runs.
Configure before the first run
- After an owner accepts an intake response, open Data -> Form responses, select that response, and choose Automate this form.
- In Kitchen, choose Use installed workflow template, review the exact-form clone, and save it. The clone keeps the pack-owned shared-state namespace, records its fork provenance, and creates a paused trigger scoped to that one form.
- Configure the saved recipe before running or arming it: positive minor-unit price, currency, exact Stripe connection, exact notification-mail sender, owner-authored checkout-link subject/body, durable Markdown template file, Checkout success/cancel HTTPS URLs, expiry, product copy, and generation mode. The checkout body must retain
[[checkout_url]]; both fields may use[[product_name]]. These closed placeholders are rendered deterministically and the exact subject is pinned before mail. AI never writes customer communications. To register the outcome in core Seller, also choose a stable local offer id and explicitly enable Register Seller outcome draft. Leave it disabled when the recipe should remain unlisted. - Return to the accepted response in Data, choose Run this response, and review the routing context and configuration. If Seller registration is enabled, the run exact-validates an existing definition or creates one draft and attaches that still-unlinked offer to this exact saved recipe. It never activates the offer, edits its definition, redirects an existing recipe link, or copies transaction state into Seller. The normal run starts the first fulfillment manually without re-emitting acceptance. Continue through the payment-verification, generation, artifact-review, and governed-delivery surfaces below until the order is complete.
- Only after one manual fulfillment proves the configuration, open Automation and explicitly arm the saved exact-form trigger. Installing, upgrading, cloning, and saving never arm it or register a Seller offer.
Static generation remains the default. AI mode additionally needs a configured LLM gateway and a literal [[ai.draft]] placeholder in the pinned Markdown template. Model refusal, invalid output, or a missing placeholder leaves recoverable state and requires an explicit static retry; it never silently changes the selected mode.
Operate and recover
- Seller orders show each order's durable phase, revision, artifact pins, and owner-actionable error copy.
- Verify payments re-reads exact Stripe source truth and advances only complete-and-paid sessions.
- Generate document source-checks the selected static/AI plan and creates bytes only from provider-verified paid or already-generating state.
- Review artifacts presents hash-pinned PDFs and the source-checked approve, regenerate, reject, cancel, and delivery-recovery actions.
- Reconcile delivery observes one already-fenced mail attempt. Missing or uncertain evidence never authorizes resend.
Seller is a core-owned surface: durable outcome offers use author-chosen stable local offer ids and fixed core.seller.* capabilities that any normally authorized recipe may compose against. This recipe supplies only offer content and fixed price; core stamps recipe provenance and creates only a draft. On the first opted-in transaction-free run, one core operation may attach an unlinked offer only to the exact executing creator recipe. That attachment is navigation only and grants no fulfillment or transaction authority. This pack, its publisher, and its version are Marketplace distribution provenance only, never Seller identity or authority. Payment, artifact, approval, delivery, and reconciliation authority remains inside the source-checked recipes and server capabilities.
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
=
currency
setting
=
usd
sender mail
setting
=
amount minor
setting
=
5000
generation mode
setting
=
static
seller offer id
setting
=
template file ref
setting
=
—
checkout cancel url
setting
=
[object Object]
checkout success url
setting
=
[object Object]
checkout expiry hours
setting
=
24
checkout product name
setting
=
Prepared document
register seller offer
setting
=
false
checkout link email body
setting
=
Your prepared document request is ready for payment.
Complete payment securely with Stripe:
[[checkout_url]]
Stripe controls this hosted checkout and its expiry. If you did not request this document, you can ignore this email.
checkout link email subject
setting
=
Complete payment for your prepared document
checkout product description
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.