ZenotiHelp

Process payments at the kiosk

ZTZenoti Docs Team Updated September 16, 2026 8 min readGuide

New experience available: New Kiosk is available in beta with Bluetooth card reader payment. See Process payments at New Kiosk.

The guest kiosk supports payment collection as part of the check-in flow, including credit card prepayment, card-on-file collection, guest self-checkout with tipping and donations, and automatic payment authorization. This article covers each payment method, the verification steps involved, and the screens the guest sees during the payment process.

Audience: Front desk staff and administrators who configure or support kiosk payment workflows.


On this page


Before you begin

  • Your organization must have Enable Kiosk turned on at the organization level and Enable Kiosk mode turned on at the center level. This article covers payment on the legacy kiosk. The new kiosk also supports in-app payment β€” see Process payments at New Kiosk for the new kiosk flow.
  • Payment processing must be configured at the center level (Stripe or Adyen).
  • For auto-pay functionality, auto-pay must be enabled at both organization and center levels.
  • For card-on-file with OTP verification, the Send OTP by [Email, Text, Either] setting must be configured in organization settings.

Card-on-file prerequisite β€” three conditions must all be true:

  1. Enable card on file during check-in (organization-level setting) must be turned on.
  2. Can save cards in Kiosk (center-level setting) must be turned on for the center.
  3. The kiosk must be running in in-store mode. Card on file is NOT available when Enable online kiosk (Deprecated) is active β€” guests accessing the kiosk remotely via a browser cannot save a card on file through the kiosk.

When kiosk payments are used

Kiosk payment processing is triggered in two scenarios:

  • Prepayment -- the center requires guests to provide payment information or pay before their service begins. This is common for walk-in businesses that want to secure payment before the guest sits down for their appointment.
  • Card on file -- the center requires guests to have a credit card on file so that payment can be charged automatically after the service is completed.

Whether the kiosk prompts for payment depends on the center's payment configuration. If prepayment and card-on-file collection are not enabled, the kiosk skips the payment step entirely and moves directly to the waiting screen after check-in.

Credit card prepayment via Stripe

When the center uses Stripe as its payment processor, the kiosk collects credit card information directly on the device using a PCI-compliant tokenization flow.

Card entry

After check-in, if prepayment is required, the kiosk displays a prepayment screen where the guest enters their credit card details:

  • Card number -- the full credit card number. The kiosk validates the card number format as the guest types.
  • Cardholder name -- the name as it appears on the card.
  • Expiry date -- the card's expiration month and year.
  • CVV -- the three- or four-digit security code on the card.

The kiosk validates the card number and CVV before allowing the guest to proceed. If the card number is invalid or the CVV does not match the expected format, the kiosk displays an error message and prompts the guest to correct the entry.

Card validation and tokenization

Once the guest submits their card details, the kiosk sends the card information to Stripe for tokenization. Tokenization replaces the actual card number with a secure token that represents the card without exposing sensitive payment data.

The tokenization process is PCI-compliant:

  1. The card details are sent directly from the kiosk to Stripe's servers -- the card number is never stored on your servers or in Zenoti.
  2. Stripe validates the card and returns a token.
  3. The token is saved as the guest's card on file for the current and future transactions.

Note: Because card tokenization happens directly between the kiosk device and Stripe, the process requires an active internet connection. If the connection is interrupted during tokenization, the guest sees an error and can retry.

Prepayment confirmation

After successful tokenization, the kiosk displays a prepayment confirmation screen. This screen summarizes the payment details and asks the guest to confirm before the payment is processed. The confirmation screen shows:

  • The last four digits of the card number
  • The cardholder name
  • The amount to be charged (if a specific prepayment amount is configured)

The guest taps the confirm button to authorize the payment.

Prepayment success

After the guest confirms and the payment is processed successfully, the kiosk displays a prepayment success screen. This screen confirms that the payment has been received (or that the card has been saved on file) and shows a summary of the transaction.

The kiosk then proceeds to the waiting screen or to the service forms step, depending on the center's configuration.

Adyen payment integration

For centers that use Adyen as their payment processor, the kiosk uses a different payment flow based on hosted payment pages.

Hosted payment page

When the kiosk initiates an Adyen payment, it loads a hosted payment page provided by Adyen. The guest enters their card details on this hosted page, which handles all PCI-compliance requirements on Adyen's side.

The hosted payment page flow:

  1. The kiosk requests the hosted payment page from the Zenoti server.
  2. The kiosk loads the payment page in an embedded view.
  3. The guest enters their card details on the Adyen-hosted page.
  4. Adyen processes the card and returns the result to the kiosk.
  5. The card is saved on file for the guest's account.

OTP verification for card on file

When a guest adds a card on file through the Adyen integration, the system can require OTP (one-time password) verification to confirm the guest's identity. The OTP channel is controlled by the Send OTP by [Email, Text, Either] organization setting, which offers three options:

  • Text -- the verification code is sent to the guest's registered mobile number.
  • Email -- the verification code is sent to the guest's registered email address.
  • Either -- the guest can choose whether to receive the code by text or email.

The OTP verification flow:

  1. After the guest submits their card details, the kiosk sends an OTP to the guest's selected channel.
  2. The guest enters the received code on the kiosk.
  3. The system validates the code. If correct, the card is saved on file and the process continues.
  4. If the code is incorrect, the guest can request a new code. A 30-second timer prevents repeated resend requests.

Note: OTP verification for card-on-file is separate from the general login OTP verification. Even if login OTP is disabled, card-on-file OTP can still be required based on the organization setting.

Guest self-checkout

The kiosk supports a self-checkout flow where guests can pay for their completed services without visiting the front desk. Self-checkout is useful for centers that want to minimize front desk interactions at the end of the visit, allowing guests to pay and leave on their own schedule.

Precondition β€” service must be marked Complete: Self-checkout is only available after a service provider or front desk operator marks the guest's service as Complete in the system. Until the appointment's status is Complete, the guest's invoice does not appear on the kiosk checkout selection screen and the guest cannot initiate checkout on their own. The kiosk does not expose a "start checkout" action to the guest β€” the checkout selection screen only lists invoices whose underlying services are already Complete.

Invoice summary

After the guest's service is marked Complete by the provider or front desk, the kiosk displays a checkout selection screen. The guest selects the invoice they want to pay from a list of their completed invoices. The kiosk then displays a full invoice summary with individual line items, showing each service, its price, and the total amount due.

Tip options

The checkout screen presents tip options so the guest can add a gratuity:

  • Preset percentages -- the guest can select 10%, 20%, or 30% as a quick tip based on the invoice total.
  • Custom tip amount -- the guest can enter a specific dollar amount instead of using a preset.

For group appointments with multiple providers, the kiosk supports per-provider individual tipping. Each provider in the group is listed separately, and the guest can assign a different tip amount to each one.

Donation options

The checkout screen can also present donation options, allowing the guest to add a charitable contribution to their payment:

  • Preset amounts -- a short list of suggested donation amounts configured by your center (commonly $1, $3, and $5). The specific amounts and their display order are set in your organization's donation configuration.
  • Custom amount -- the guest can enter a specific donation amount.

Donations are added to the invoice total and included in the payment.

Note: Donation preset values are center-configurable. If your center has not configured suggested donations, the guest sees only the Custom amount entry. Work with your Zenoti administrator to adjust the preset list.

Payment methods

The guest can pay using one of the following methods:

  • Saved card on file -- if the guest has a credit card saved on their profile, it is available as the default payment method.
  • Enter new card -- the guest can enter new credit card details directly on the kiosk.
  • Swipe or tap card machine -- if the center has a connected card reader, the guest can pay by swiping or tapping their physical card at the device.

Receipt options

After payment is processed, the guest chooses how to receive their receipt:

  • Print receipt -- the kiosk sends the receipt to the center's connected receipt printer.
  • Email receipt -- the receipt is sent to the guest's email address on file.

Auto-pay flow

When a guest already has a credit card saved on file and the center has auto-pay enabled at both the organization and center level, the kiosk can process payment automatically without requiring the guest to enter card details again.

The auto-pay flow works as follows:

  1. After check-in, the system detects that the guest has a card on file.
  2. The system pre-authorizes the estimated payment amount on the saved card.
  3. The guest sees a confirmation that their saved card will be charged after the service is completed.
  4. No manual card entry is required -- the kiosk proceeds directly to the waiting screen.

After the service is completed and the invoice is finalized, the pre-authorized amount is captured (or adjusted to the final amount). Returning guests who saved their card during a previous visit can complete payment without re-entering their details.

Note: Auto-pay requires that the guest's saved card is still valid and has sufficient available credit. If the pre-authorization fails (for example, due to an expired card), the kiosk falls back to the manual card entry flow.

Was this article helpful?
Your feedback helps us improve our documentation.