Checkout fields and quick payment
Choose which contact fields a free checkout asks for, turn Apple Pay / Google Pay quick payment on or off for a paid checkout, and manage the consent checkboxes buyers see.
The Form & UX tab of the checkout editor decides what the customer has to fill in and which payment shortcuts they see. When you finish, your free checkouts ask only for the fields you need and your paid checkouts show (or hide) the one-click wallet buttons.
Contact fields on a free checkout
Open the Form & UX tab
Open a free checkout from Offers → Checkouts (/checkouts) and switch to the Form &
UX tab. The Contact fields section lists three rows: Email (always required), First
name and Last name. The email switch is on and cannot be turned off.
Pick the name fields
Turn First name and Last name on or off. The preview on the right updates after each click, without saving. A new free checkout starts with First name on and Last name off; free checkouts created before this setting existed keep both on.
Save and check the live page
Click Save changes (or Publish checkout if the checkout is still a draft) and open the page with Open live. Under Contact information the customer sees only the fields you left on. A field that is shown is mandatory: leaving it empty shows Field is required. With both name switches off, an email address alone is enough to sign up with Get Access.
Paid checkouts always collect the customer's email, first name and last name, so the Contact fields section does not appear on them. Extra fields for any checkout (Country, Phone, Additional info) live in the Additional fields section of the same tab.
Quick payment (Apple Pay / Google Pay) on a paid checkout
Find the switch
Open a paid checkout and go to Form & UX. The row Quick payment (Apple Pay / Google Pay) has a switch. New paid checkouts start with it on. Checkouts created before this setting existed start with it off until you turn it on and save.
See what the customer gets
With the switch on, the checkout page shows an Express checkout section with black Apple Pay and Google Pay buttons above the form, followed by the divider or fill in your details below. The required consent checkbox sits directly under the wallet buttons; it is the same consent as the one next to the pay button, shown twice and always in sync. Clicking a wallet button without ticking it shows To use express checkout, tick the required consents.
Turn it off or on and save
Flip the switch and click Save changes. The preview drops or restores the whole section immediately, and the public page follows a few seconds after saving. Turning quick payment off does not touch card or other payment methods.
Consents (checkboxes)
The Consents section of Form & UX lists the checkboxes this checkout shows. Add consent creates one; Manage workspace consents opens Workspace consents with every consent of the workspace and the products and checkouts each one applies to.
| Field | What it does |
|---|---|
| Internal name | Your own name for the consent, shown when you pick it in a workflow condition. Two active consents cannot share it. |
| Consent text | What the buyer reads next to the checkbox. Words can link inline: [text](https://example.com/privacy-policy). |
| Consent is required | The buyer cannot pay without ticking it. |
| Subscribes to marketing emails | Buyers who tick it join your marketing email audience. An earlier unsubscribe is never overridden. |
| Link URL (optional) | A link to the document the consent refers to. |
| Products and checkouts | Apply to all products or pick products, and optionally Limit to specific checkouts. |
Zanfia keeps the history of every consent. Each saved change becomes a new version, and every order stores the exact consent text the buyer saw together with their answer. Deleting a consent (Delete this consent?) archives it: it disappears from checkouts and from workflow conditions, while past orders keep their answers. Workflows can branch on the answers with the Consent answer condition, described in Workflow triggers, steps and variables.
Good to know
The wallet buttons appear only when your Stripe account supports them and the customer's device can pay this way: Google Pay needs Chrome with a saved card, Apple Pay needs Safari on an Apple device. If you see no buttons on your own machine, the setting can still be on. The buttons in the editor preview are a mock and do nothing when clicked. Free checkouts have no payment section, so the quick-payment row does not exist for them.
Was this article helpful?