Quick Checkout puts a payment form directly on your school's own website. A prospective student, a current student, or a parent can pay a one-off charge — an application fee, a registration deposit, a books-and-supplies kit — in two short steps. No account, no sign-in, no phone call.

Quick Checkout is not for loans, contracts, or payment plans. Those payers are steered to the student portal instead, so their money lands against their account.

Go to Payments › Quick Checkout Payments. If you don't see this menu item, your school either doesn't have the Payments product or hasn't finished setting up payment processing — that's the first thing to check.

Each row is one payment form and shows whether it's live (Enabled), how many items it offers, and which websites are allowed to display it. The row menu (⋮) holds Edit, Duplicate, Disable, and Delete. Disable is your kill switch — it stops the form taking money immediately, even though the code is still sitting on your website.

Click Create Widget, or Edit an existing one. Everything on this page takes effect on your live website right away — you never need to re-paste the code onto your site.

• Enabled Domains — the web addresses allowed to display this form. This is the only thing preventing another site from showing it, so fill it in. Use *.example.com to match all subdomains, and remember to include the www. version if your site uses it.
• Payment items — the only items a payer can buy through this form. Every amount comes from your invoice template; the form never sends a price.
• Required payer fields — first and last name are always required. Beyond that you can demand a Receipt email, Phone, Student ID, Campus, or a Payment note. Payers must always give an email or a phone number; receipts are only sent by email.
• Check this box to enable this widget — the on/off switch for the form.

The student portal callout is the panel at the top of the form that steers loan, contract, and payment-plan payers away from Quick Checkout and into their portal, so their payment stays tied to their contract. You can reword the heading and text, or switch the callout off entirely.

The two colour pickers — Button Background Color and Button Text Color — let the form match your own branding.

Embedded in your website, the form is a single card. Only the items you ticked appear, and ticking more than one combines them into a single payment with one total and one charge.

Below the items, the payer fills in their details. Anything that can be left blank is marked with a grey Optional chip.

A ticked item is outlined and shaded so the payer can see what they've chosen. Then they click Next.

On Review and pay the payer chooses Card or Bank account — if you only offer one, no tabs appear and that form shows directly. The card fields belong to your payment provider, so card numbers never reach Lumion.

Once the card is entered, a Paying with box replaces the card fields, with Use a different payment method if they want to swap it. The Payment summary repeats what's being bought and the details given; anything left blank simply doesn't appear rather than printing an empty row.

After paying, the form shrinks to a short Payment submitted panel telling the payer where their receipt is going. If they only gave a phone number, it reads "No receipt was sent — next time, add an email address to get one." There's no confirmation number and no print button, and refreshing the page starts a fresh, blank form.

The payment arrives as a normal invoice against the payer's record. There's no application or contract behind it, which is expected for this kind of payment. If the payer entered a Campus or a Payment note, those show up with the invoice.

• The payer can never set a price — the form only sends back which items were ticked; prices come from your own list at the moment of payment
• Only approved items are payable — an item you didn't tick never shows up on the form
• Only approved websites can show the form — anywhere else, it simply won't load
• You can stop it instantly — disabling the form stops it loading straight away, even with the code still on your site
• No surprise repeat charges — there's no "save my card" option and no automatic future payments
• Card details never reach Lumion — the card fields belong to the payment provider
• One school can't see another's — forms, items, and payments stay within your school
• Settings apply immediately — changes show on your live website on the next visit

"I paid but never got a receipt."
Almost always because they gave a phone number instead of an email. Receipts are email-only — there is no text receipt. If no email was given, the payment is perfectly fine; the receipt simply never existed.

"The payment form is blank on our website."
Either the page is on a web address that isn't in your Enabled Domains list (check whether the address uses www.), or the form has been disabled. Both show an empty space rather than an error message.

"A payer wants to pay for something that isn't on the list."
Only items ticked under Payment items can be paid for. Add it yourself and it appears immediately — no change to your website needed.

"Can they pay their loan or payment plan here?"
No, and they shouldn't — it wouldn't be applied to their account. That's exactly what the callout panel at the top of the form is for. Send them to the student portal instead.

"Which details does a payer have to fill in?"
Always first and last name, plus either an email address or a phone number. Beyond that it's up to you — you can also require a Student ID, a Campus, or a note.

"Do they need an account?"
No — that's the whole point. The payer never signs in, never sets a password, and nothing is remembered for next time.

"Can they pay for more than one thing at once?"
Yes. Ticking several items combines them into a single payment with one total and one charge.

"Can we make it match our website?"
Yes — set the button colour and text colour, and reword the portal callout, from the settings page.

Prefer a printable version? Download the full walkthrough as a PDF — same steps, with every screenshot.