All docs

Checkout and booking steps

Take a payment or book a time inside a funnel, with a total the server calculates and a result you can trust.

Updated . 5 min read.

A funnel can take a payment and book a time without sending the visitor away. Add a Payment element and a Booking element to a screen like any other element. Both are themed with your funnel styling, work with the keyboard and screen readers, and read in English.

Add a payment step

  1. Open the funnel builder and add a Payment element to the screen where the visitor should pay.
  2. Set the currency and either one fixed amount or a list of priced items (see below).
  3. Choose the billing: One-time payment or Subscription.
  4. Publish the funnel.

Every funnel payment becomes an order in your workspace. Orders carry the line items, the total, the customer email when known, and their state (pending, paid, partially refunded, refunded, disputed, failed, canceled).

The total is always calculated by Formspring

The browser never sets a price. The visitor only chooses how many of each item they want, inside the minimum and maximum you set. Formspring calculates the total on the server from the prices saved in the funnel, so a changed request cannot lower the amount.

Priced items have a name, a price, a default quantity and a minimum and maximum quantity. A visitor who picks a quantity outside the range gets a clear error and nothing is charged. If the visitor changes a quantity after the card field opened, the card field resets and a new order is opened for the new total. The earlier unpaid order is canceled.

A payment is confirmed by the payment provider, not the browser

When the visitor finishes the card form, the page shows "Confirming your payment" and waits until the payment provider has confirmed the payment to Formspring. Only then does the funnel move on. This is also what protects you from a visitor who edits the page to skip the payment:

  • A screen with a required payment does not let the visitor leave until the order is paid.
  • The funnel cannot be submitted until every required payment is paid. To make a payment optional, turn off Required on the element.
  • Anything a visitor sends under the payment or booking answer names is discarded. Those facts are written by Formspring from its own records.

If the confirmation is slow, the page says so and keeps checking. The payment is safe and the funnel continues as soon as the confirmation arrives.

Card field or hosted checkout page

A one-time payment can use a card field inside the page (the default) or the hosted checkout page. A subscription always uses the hosted checkout page.

When the visitor leaves for the hosted page and cancels, they return to the same funnel on the same screen with their answers still filled in and a message that the payment was cancelled. They can try again. A retry opens a new checkout, so the cancelled attempt never blocks a later payment. Only the browser that left can resume the journey.

If the visitor already paid for the element in that journey, a second payment is refused. A repeated confirmation from the payment provider never creates a second order.

Subscriptions

Choose Subscription and the billing interval (day, week, month or year). The first payment is the first order. Each later renewal invoice becomes its own order linked to the first one, so renewals appear in your orders and in funnel revenue. A failed renewal is recorded as a failed order. When the subscription ends, the first order shows that it ended.

Refunds and disputes

Refunds and disputes arrive from the payment provider. They change the order state and its net amount, and they adjust the funnel's revenue without deleting the original sale. For this to work, the payment webhook endpoint in your Stripe dashboard must be subscribed to these events:

Event Used for
payment_intent.succeeded, payment_intent.payment_failed, payment_intent.canceled Card field payments.
checkout.session.completed, checkout.session.expired, checkout.session.async_payment_succeeded, checkout.session.async_payment_failed Hosted checkout.
invoice.paid, invoice.payment_failed, customer.subscription.deleted Subscriptions and renewals.
charge.refunded Refunds.
charge.dispute.created, charge.dispute.updated, charge.dispute.closed, charge.dispute.funds_withdrawn, charge.dispute.funds_reinstated Disputes.

If an event is not subscribed, the order simply does not learn about it, so check the list when you connect payments.

Where you see the sale

  • The funnel submission shows the order summary next to the answers: element, status, amount, refunded amount and whether it recurs.
  • The order itself lists its line items and its history of provider events.
  • Funnel reports count a paid order as revenue and subtract refunds and lost disputes.

Add a booking step

Add a Booking element, choose Formspring Bookings and enter the slug of a booking page from the same workspace. The visitor picks a day and a time, enters their name and email (filled in from earlier answers when possible) and confirms. The booking is created by the same booking system as the hosted page, so availability, calendar checks, double-booking protection and notifications behave exactly the same.

  • The times are shown in the visitor's time zone.
  • A visitor who repeats the same request gets the same booking; they never get two. A different time is a reschedule from the link in the confirmation.
  • Turn on Require a booking to stop visitors from finishing the funnel without one.
  • A booking page that takes a payment is completed on its own booking page. The step then offers a button to open it.
  • Only booking pages of your own workspace can be offered. A page from another workspace is never shown.

The funnel records the booking as an outcome next to leads and orders, and the submission shows the appointment.

Limits

  • Calendly and Cal.com embeds are not native steps; they open as embeds.
  • Card payments need the visitor's browser to load the payment provider's secure field.