Documents, payments and delivery from one submission
The same submission that captured the answers can produce the PDF, take the payment and hand over the goods — without a script, a stitched-together toolchain or a human copying values between systems.
-
PDF documents
Design templates from structured blocks — headings, tables, merge fields, conditional sections, images — or reproduce an existing PDF exactly, its own pages becoming the template with the type matched onto open faces and your fields bound on top. Certificates, decision letters, confirmations: merged, not mail-merged.
-
Payments, server-priced
A logic rule prices the payment from the submitted answers; Stripe collects it. Deposits, tiered fees, add-ons — whatever your formulas say, and only what they say. A workflow step can require payment before it proceeds.
-
E-signatures
A workflow step emails each signer their own link to a frozen, fingerprinted copy of the document. They draw or type a signature; the platform records who, when and from where, appends a certificate page to the signed PDF, and a later step can require everyone to have signed.
-
Digital delivery
Attach files from your library to a form’s rules and submitters get a stable download link when their submission — and, if priced, their payment — completes. Sell documents, deliver purchased files, hand out programme packs.
Reliability
Money moves like data: recorded first
Every payment and payout is written down before any request leaves for Stripe, and confirmations come from Stripe's signed webhooks — never from a browser's success page. A closed tab cannot lose a payment, and a retried webhook cannot double one.
Templates are data
A template cannot run code
Document templates are structured data rendered by the platform, not scripts. Merged values are escaped, conditions run through the same closed expression engine as form logic, and rendering has a budget — a malformed template degrades, it never takes the service with it.
Questions
Documents and payments, plainly
Who decides how much a payment is?
Your form’s rules, evaluated on the server. The amount is computed from the submitted answers by the same engine that computes every other value — a browser has no way to send its own price, because the request has no field an amount could ride in.
How do payments reach my bank account?
Through Stripe. You connect your Stripe account once; Faldaro creates the payment against it and Stripe handles cards, receipts and payouts. Card details never touch Faldaro.
When is a digital product released?
When the submission’s recorded payment status says it has been paid — checked at download time, every time. A free tier priced at zero releases immediately; a paid one releases when Stripe confirms settlement.
Can a workflow send someone their documents?
Yes. A transition can generate a document from a template and email it — the approval that finishes a claim can be the same step that sends the decision letter.
Close the loop on your process
Collect the answers, price the work, produce the paper and deliver the goods — one platform, one submission.
No card required.