Collecting a payment on an intake form

An intake form can take money as well as answers — a deposit with a service request, a registration fee, an application fee, a donation, or an auto-renewing product a customer pays for every year. The payer fills in the form and pays on the same page, on your branded surface.

Adding the payment field:
1. Open the form and add a field of type Payment. A form takes one payment field.
2. Decide how the amount is set:
• Fixed — leave "Let the payer choose the amount" unticked and enter the Amount (USD). The payer sees the amount and cannot change it.
• Payer chooses — tick "Let the payer choose the amount (deposit / donation)" and set a Minimum amount (USD). The payer enters what they want to pay, and anything under your minimum is raised to it.
• Priced levels — add levels when the price depends on what the respondent picks; each level shows its own price and the choice sets the amount billed.
3. Decide whether payment is mandatory with "Payment required to complete the form".
4. Publish the form.

Auto-renew (recurring subscription):
Turn on "Auto-renew" to sell a subscription instead of a one-time charge — a resource product that renews yearly, a membership, a recurring service. Pick the interval (Yearly or Monthly; Yearly is the default). You can set it on a fixed or payer-chosen amount, or per priced level, so one form can offer a one-time level next to an auto-renewing level.

The payer sees "Renews yearly (or monthly) — cancel anytime" before they pay, and the price shows the cadence (for example $49/year). Checkout runs on the same branded, embedded card form — never a redirect to an outside checkout — and the charge settles to your own connected payment account, at cost. Turtini's standard platform fee applies to every invoice, including renewals.

Renewals and cancelling:
Every renewal is charged automatically and appears against the subscriber. The subscription shows up in your Subscribers list, where you (or the customer) can cancel it — cancelling is always at least as easy as signing up. A cancelled subscription stops renewing at the end of the paid period.

What the customer sees:
The payment field shows the amount (or the box to enter one) with a note that payment happens securely in the next step. The submit button reads "Continue to payment" rather than "Submit", so nobody is surprised by a payment step.

When they continue, the answers are recorded first, then card entry appears on the same page — your page, with your org's branding, not a redirect to somebody else's checkout. The charge settles to your own connected payment account, at cost.

Required vs optional payment:
This choice decides what happens if the payment does not go through.
• Required — the submission is recorded but is not complete until payment succeeds, and the payer is told what went wrong so they can try again.
• Optional — the submission is recorded and the payer sees the thank-you regardless. Use this for a suggested donation or a deposit you are willing to collect later.

Either way the answers are never lost. The submission is saved before the payment step, so a failed card does not throw away everything the customer typed.

Tracking payment:
Each submission carries its payment state — none, pending, or paid — along with the amount and the time it was paid. A one-time charge is backed by a payment request record you can find in Accounting; an auto-renewing one is backed by a subscriber in your Subscribers list. A submission that came in unpaid on an optional payment is visible as exactly that, so you can follow up.

Before you can take a payment, your org needs its payment account connected. If payments are not set up yet, do that first — a payment field on a published form is only as good as the account behind it.