Payment Basics

Any form can take a payment when it is submitted — a registration fee, a workshop booking, a membership renewal. You set a base price, optionally adjust it based on the answers people give, and choose how they can pay. The payment is processed through your connected payment gateway and recorded as a transaction linked to the submission.

Payments may need to be enabled for your organisation. If you don't see the Payments area in the dashboard, contact support.

Before you start

• Connect a payment gateway. Card payments go through a Stripe gateway integration. Set one up first — see Connecting Stripe.
• Build the form. Add the fields you need before setting up pricing, especially any fields the price depends on. See Building Forms.

Turning on payments

1. Open the form and go to the Field Editor tab.
2. Below the field tree, click Payment Settings. The Payment Configuration panel opens on the right.
3. Switch on Enable Payments.
4. Choose the Currency.
5. Enter the Base Amount — the price before any adjustments. Leave it at 0 if the whole price comes from modifiers.
6. Add at least one Payment Method (see below).
7. Save the form.

The form preview in the field editor shows the payment section as you build, so you can check the total while you fill in sample answers.

Payment methods

A payment method is an option the person chooses when paying. You can offer more than one — for example card payment and pay later.

Setting	What it does
Title	The label shown to the person, such as "Pay now with card".
Database Key	A unique key for the method, generated from the title.
Integration	The payment gateway that processes the payment — your Stripe gateway.
Pay Later	Lets people submit the form without paying now, for example to pay by bank transfer or cash. When on, the Integration setting is hidden and a Payment instructions box appears so you can tell people how to pay.

If a payment is required and the person chooses a card method, the form can't be submitted until the payment is authorised.

Adjusting the price with payment modifiers

Payment Modifiers change the total based on the answers in the form — for example adding a fee for an optional extra, applying a member discount, or charging per attendee. Each modifier has:

• Label — shown to the person in the price breakdown, such as "Conference dinner" or "Member discount".
• Modifier — how it changes the total: Add, Subtract, Multiply, Divide or Set value to.
• Value Expression — the amount to apply, written as an expression. Amounts are in cents: 2500 means 25.00. For Multiply and Divide, the value is a plain number such as 2.
• Conditional Expression (optional) — an expression that must be true for the modifier to apply. Leave it empty to always apply.

Expressions can read the person's answers through model, using the field keys from your form. For example, for an "Annual Conference" registration:

• Base Amount 150.00.
• "Conference dinner": Add, value 4500, condition model.dinner — adds 45.00 when the dinner checkbox is ticked.
• "Member discount": Subtract, value 2000, condition model.membershipType == 'member' — takes 20.00 off for members.

Modifiers are applied in order, from top to bottom, and the total never drops below zero. If the final total is zero, the form is submitted without a payment step.

What happens when someone pays

1. The person fills in the form and sees the total, with a line for each modifier that changed it.
2. Qik recalculates the total on the server from the person's answers. If it doesn't match what the form showed, the submission is refused, so prices can't be tampered with in the browser.
3. For card payments, the person enters their card details in Stripe's secure card form. Card details never pass through Qik.
4. The amount is authorised, the submission is saved, and then the payment is captured. A transaction is recorded and linked to the submission.

How payments are authorised and captured, test mode and the minimum charge are covered in Connecting Stripe. To find payments, check their status or issue refunds, see Transactions and Refunds.

Testing a paid form

Before you share the form, open it in test mode (select the form and choose Test Form Link from the Actions menu) and submit it with a Stripe test card. Test submissions use your gateway's test keys, so no real money moves.

Related features

• Event tickets — to issue QR-code tickets to people who register through a form, see Event Tickets.
• Products and subscriptions — to sell ongoing access, such as a recurring membership that grants access passes, use products rather than a paid form. See Products and Purchases.

Tips

• Set up the fields a modifier depends on before writing its expressions, and use the field's exact key.
• Remember amounts are in cents: a value of 10 is 0.10, not 10.00.
• Test every combination of answers that changes the price before going live.
• If you offer Pay Later, decide how you'll follow up — for example a smart list of submissions with no paid transaction.