ZenotiHelp

Process payments with the New POS Experience

ZTZenoti Docs Team Updated July 13, 2026 3 min readGuide

Beta: The New POS Experience is currently in beta. For the stable experience, see Payment processing.

The Payment segment of the right pane lets you apply one or more payment methods to an invoice. You can split-tender across multiple methods, retry on failure, and (when configured) require OTP verification on a sensitive charge.

Audience: Front desk staff taking payments at checkout in the New POS Experience.

On this page

Before you begin

  • The invoice has at least one line item.
  • You have the Take Payment permission.
  • For credit-card payments, the cloud reader (if used) is paired with the surface; for saved-card payments, the guest has a saved card on file.

Payment methods

The Payment segment shows the following sub-tabs:

Sub-tab Description
Credit card (cloud reader) Charge through a paired Stripe terminal or cloud reader. See Process cloud payments.
Credit card (manual entry) Enter card details by hand for back-office charges.
Saved card Charge a card stored on the guest profile.
Cash Cash tender; the surface shows the change calculation.
Check Check tender with check-number capture.
Gift card Redeem a Zenoti gift card by code.
External gift card Redeem a third-party gift card.
Prepaid card Redeem a prepaid card.
Custom Organization-configured custom payment methods (BNPL providers, gift certificates, third-party vouchers).

Loyalty points and member credits are applied via the Discounts segment, not as a payment method.

Steps

1. Open the Payment segment

Select the Payment segment on the right pane. The footer balance shows the amount due.

2. Pick a payment method

Pick the sub-tab for the method you are using. Enter the amount (defaults to the full balance) and complete any method-specific fields:

  • Cash β€” enter the tendered amount; the surface shows the change to give.
  • Check β€” enter the check number.
  • Saved card β€” pick the card from the guest's saved-card list.
  • Cloud reader β€” see Process cloud payments for the terminal interaction.

3. Apply the payment

Select Charge (or Apply for cash and check). The system processes the payment and updates the footer balance.

4. Verify the receipt

If the method is a credit card, the credit-card receipt screen surfaces after the charge clears β€” it shows the transaction ID, amount, last 4 digits, status, and date / time.

5. Close the invoice

When the balance is zero, the primary action changes to Close invoice. See Close an invoice with the New POS Experience.

Split-tender across multiple methods

When the guest is paying with more than one method (for example, $50 cash plus the remainder on card):

  1. Apply the first method with the partial amount.
  2. The footer balance recalculates to show the remainder.
  3. Apply the next method for the remaining amount (or another partial amount).
  4. Repeat until the balance is zero.

If the invoice has a positive balance after all selected payments, you can close the invoice as a due-balance invoice (subject to permission) or add another payment method.

Tips

  • Failed payments do NOT close the invoice. The processor error appears on screen and the failure is logged to the invoice audit log automatically.
  • For organizations that require OTP verification on a sensitive charge (a large refund or a card-on-file save), the OTP verification screen prompts the user (or a manager) for the code sent to a registered device.

Troubleshooting

  • The cloud reader does not respond. Confirm the terminal is paired with the surface, the terminal screen is on, and the network is reachable. See Process cloud payments for details.
  • The saved card was declined. The processor returns a decline reason. The guest may need to provide a different card, or update the billing address used for AVS.
  • The guest's address is required for the charge. AVS is required by your organization or by the processor. Enter the cardholder's billing address when prompted.
Was this article helpful?
Your feedback helps us improve our documentation.