Taking money in the form rather than after it is the single biggest change available to most order and booking flows. The gap between somebody filling in a form and paying an invoice is where a large share of orders quietly disappear.
Here is what the options actually are, and the parts people find out about too late.
Three shapes of payment
Almost everything is one of these, and which one you need determines how the rest of the form is built.
- A fixed price. One amount, same for everybody. Event tickets, a course, a set fee. Simplest to build and to reconcile.
- A calculated total. The amount comes from the answers: quantity times price, plus options, minus a discount. This is what an order form or a quote calculator needs.
- A deposit or part payment. A fixed amount or a percentage of a calculated total, taken to secure a booking with the balance due later. The most effective thing available against no-shows.
Which provider
Stripe and PayPal cover almost everybody, and the right answer is usually whichever you already have, because reconciliation is easier when the money lands where you already look.
Stripe suits businesses taking card payments regularly, has better reporting, and handles subscriptions properly. PayPal converts better with consumers in some markets purely because people trust the logo and already have an account.
Offering both is usually worth it for consumer-facing forms and rarely worth it for business ones. The second option costs you a decision at the moment of payment, which is not free.
Where the money goes
Worth checking before you build anything: does the form tool hold your money, or does it go straight to your own account?
With a form tool that connects your own provider keys, the payment goes directly from the customer to your Stripe or PayPal account. The form never touches it, there is no payout schedule to wait for, and no third party sitting between you and your revenue.
The alternative, where the platform collects and then pays you out, is how several tools work and it is a materially different arrangement. Ask specifically, because it determines when you get paid and what happens if the platform has a bad month.
Calculating a total correctly
The common mistake is building the calculation and never showing it. A running total that updates as somebody chooses options does two things: it stops the surprise at the end, which is the main reason baskets get abandoned, and it lets people adjust before they commit rather than after.
Show what is included in the figure, and show tax as a separate line rather than folding it in. A total that does not match the mental arithmetic somebody just did produces an email, not a sale.
And decide what happens when the calculation produces zero or something negative. A discount code bigger than the order is somebody else's bug report if you do not handle it.
A running total that updates as people choose options stops the surprise at the end, which is the main reason baskets get abandoned.
The compliance parts people find late
None of these are difficult. All of them are easier to handle before you take the first payment than after.
- Card details never touch the form. Payment is handled by the provider, which is what keeps you out of PCI scope. If a tool asks you to collect a card number in a text field, stop.
- Terms and a refund policy. Link them from the form and get an explicit tick. "By submitting you agree" is weaker than a checkbox in most jurisdictions and in every dispute.
- Tax. Whether you charge it, at what rate, and whether the price shown includes it. Consumer-facing prices usually have to be shown inclusive in the UK and EU.
- A receipt. Send one automatically with what was bought and what was paid. Most chargebacks start with somebody not recognising a line on a statement.
- Refunds. Issued in the provider's dashboard, not the form. Know where that is before you need it urgently.
What to do when a payment fails
This is the decision that separates a form that works from one that loses orders, and it is worth thinking about explicitly.
If the payment fails, do you keep the answers? Usually yes. Somebody who filled in a long order form and whose card was declined should not have to start again, and a failed payment with a stored response is a lead you can follow up. A failed payment with nothing stored is a stranger who left.
The exception is anything with limited capacity, where storing a response means holding a place somebody has not paid for. There, failing the whole submission is the right call, because a booking without payment is a double booking waiting to happen.
Reducing abandonment at the payment step
The payment step is where the largest single drop happens in almost every form that has one. Most of the fix is about surprise rather than about payment.
- Show the total before the payment step, not on it. A figure somebody sees for the first time next to a card field is a figure they leave over.
- Show the breakdown. A total that does not match the arithmetic somebody just did produces an email rather than a sale.
- Do not add anything at the end. Delivery, booking fees and tax appearing at the final step is the most reliable way to lose an order.
- Say what happens next. "You will be charged now and we will confirm within an hour" removes the main hesitation.
- Keep the form short before the payment. Every question before the card field is a chance to reconsider.
Deposits, instalments and paying later
Not everything has to be paid in full at the point of submission, and for larger amounts it usually should not be.
A deposit is the highest-value option available for anything with limited capacity. It converts better than full payment, it is far more effective against no-shows than a reminder email, and the balance can be taken when the work is done.
For recurring arrangements, a subscription through your payment provider is usually better handled outside the form, with the form collecting the details and the sign-up happening once. A form that creates a subscription is easy to build and hard to cancel cleanly.