Payments

Forms takes payments through Stripe Checkout. To charge for a form:

1. In the builder, add a Product field for each thing respondents can buy, and an Order total field to show the total. The Field types guide covers both.
2. Open the form's settings and go to Payments → Gateways.
3. Turn on Enable payments.
4. Pick the Currency: USD (the default), EUR, GBP, INR, CAD, AUD, JPY, CHF, SGD or BRL.
5. Under Charge, choose One-off (the default) or Subscription. A subscription also takes a Billing interval: Monthly (the default) or Yearly.
6. Choose Save changes.

Payments run through the Stripe account your deployment of Forms is connected to. If Stripe isn't set up, Gateways shows a warning that starts "Not configured on this deployment.", and respondents aren't sent to checkout.

When a respondent submits a form with payments on and an order total above zero, Forms saves their response with the status Awaiting payment, then sends them to Stripe Checkout. Each product they picked is a line on the checkout page, with any coupon taken off, and their email is filled in when the form collected one.

• After paying, they return to the form and see Payment received.
• If they cancel, they see Payment not completed, their response stays Awaiting payment and Start over lets them fill in the form again.

Once Stripe confirms the payment, the response's payment is marked Paid and its status becomes Complete. When the form has approval steps, it becomes Pending instead, and the first approvers are asked then. A subscription charges the same amount every month or year.

A response with nothing to pay, such as one where no product was picked, is saved without checkout.

Payments → Order Builder in a form's settings lists the form's Product fields, each with its price and whether respondents pick a quantity or add a single item. Change the quantities, and type a coupon code under Try a coupon code, to see a Sample order worked out the same way as at checkout, with the discount and total.

Prices, quantity limits and new products are set in the builder. Until the form has a Product field, Order Builder only links to the builder. While payments are off, it reminds you to turn them on under Gateways.

Coupons take money off an order. To add one, open the form's settings, go to Payments → Coupons and choose Add coupon.

• Code: what respondents type, like SPRING20. Codes are saved in capitals without spaces, and respondents can type them in any case.
• Type: % off or a fixed amount off in the form's currency, such as USD off.
• Value: the percentage (up to 100) or the amount.
• The switch sets the coupon Active or Paused. Paused codes don't work.

Every coupon needs a code, and codes must be unique: Forms won't save until they are. Choose Save changes to keep your coupons, and the trash icon on a coupon to remove it.

Respondents enter a code in the form's Order total field and choose Apply, so the form needs one. An amount off never takes the total below zero. On a subscription, the discount applies to the first payment only. Coupons only work while payments are on.

A response's Payment tab, in its details in the Response Inbox, shows the payment's status, its amount and currency, and Stripe's reference for it. Under Order, it lists what was bought, any coupon and the total. A response without a payment shows "No payment was collected with this response."

The payment status starts as Pending while the respondent is at checkout, then becomes Paid, or Failed if the payment fails. Until a payment is confirmed, the response's own status stays Awaiting payment. Filter the Response Inbox by that status to follow up, or use the Awaiting payment count on the project overview. See Responses.

When you print a response that has a payment, the printed record includes a Receipt once it's paid, or an Invoice before then. It lists each item with its quantity and amount, the total, and the payment's status, reference and date. To keep a PDF, choose to save as PDF in your browser's print dialog.

Printing a response is covered in Approvals and automations.

Forms marks a response Paid when Stripe tells it the payment went through. If respondents have paid but their responses stay Awaiting payment, those messages from Stripe aren't reaching Forms.

1. Open Templates & Admin → Workspace Settings and find the Configuration card.
2. If Stripe webhooks shows Not configured, ask whoever runs your deployment of Forms to set them up.

Payments made before then aren't marked Paid on their own, so check them in Stripe.