ZenotiHelp

Payment processing overview

ZTZenoti Docs Team Updated September 5, 2026 3 min readGuide

Zenoti supports over 35 payment processors, allowing you to accept credit cards, debit cards, digital wallets, QR codes, and Buy Now Pay Later (BNPL (Buy Now, Pay Later)) payments across your centers.

V1 and V2 processors

Zenoti uses two configuration frameworks for payment processors:

  • V1 processors β€” Configured at the center level via Configuration > Payments > Settings (the center-scope caption of the Payments row). These processors use per-center credentials and settings. CaisseAP, most regional processors (eGHL, EBS, JusPay, AirPay, Plutus, QNB, Moneris Canada, Payment Express, Payworks, Checkout.com, EzyPay, BBVA, FreedomPay, Element Express / Worldpay, Amazon Payment Services, Zuora via direct flow) are V1.
  • V2 processors β€” Configured at the organization level via Configuration > Payments > Process payments > Payment processor onboarding. The unified V2 onboarding supports Adyen, Stripe, ZPay Lite (Zuora), ICPlus, Xendit, Sunbit, and Walletdoc. Always check the FS capabilities table when in doubt β€” V1 and V2 paths are not interchangeable.

Supported processors by region

Region Processors
United States Adyen, Stripe, FreedomPay, Element/Express (Worldpay), Sunbit, Moneris Canada
Canada Adyen, Stripe, Moneris Canada, Payworks
Australia Adyen, Stripe, Payment Express, ZipPay
Europe Adyen, Stripe, CaisseAP, Walletdoc
Middle East Adyen, QNB, BBVA, eGHL
Asia Adyen, Xendit, AirPay, JusPay, EBS, Plutus/PineLabs
Latin America BBVA

Payment capabilities

Different processors support different capabilities. Common capabilities include:

  • Sale β€” Charge a card at the point of sale
  • Refund β€” Return funds to the guest's card
  • Void β€” Cancel a transaction before settlement
  • Pre-authorize and capture β€” Reserve funds and capture later
  • Recurring payments β€” Charge stored cards for memberships and packages
  • Stored accounts β€” Save card details for future charges
  • BNPL β€” Buy Now Pay Later options (Sunbit, Stripe Express with Affirm/Afterpay/Klarna, ZipPay)

Buy Now Pay Later

Zenoti supports the following BNPL options:

  • Sunbit β€” Available in the United States only. Guests apply in-store and receive financing on the spot. A flat 5% fee applies per transaction. Minimum transaction: $60; maximum: $10,000.
  • Stripe Express BNPL β€” Supports Affirm, Afterpay, and Klarna where available. A 5.9% fee applies.
  • ZipPay β€” Available in Australia only. Guests generate an in-store code from the Zip app and provide it at checkout.

Card migration

When switching payment processors, Zenoti supports card migration to transfer stored guest card tokens to the new processor without requiring guests to re-enter their payment details.

Dispute management

For supported processors, you can view and respond to payment disputes (chargebacks) directly from the Zenoti admin console.

Processor-level prerequisites and source of values

Every payment-processor setup requires values that Zenoti does not supply. Each processor's article lists a credentials table with a Source / owner column naming where to obtain each value (the merchant portal, your acquirer's representative, or the V2 onboarding wizard). Plan to collect these before starting setup:

  • Merchant identifier / MID (Merchant Identifier) β€” always issued by the processor.
  • API key or secret β€” from the processor's merchant portal.
  • Terminal / card-reader IDs β€” from the processor's terminal-provisioning workflow.
  • Return / callback URL allow-listing β€” the processor must know the Zenoti domain that will receive post-payment callbacks. Share this with your processor representative before go-live.

Network requirements (common pattern)

Most payment integrations require outbound HTTPS (port 443) from Zenoti to the processor's API, from the guest browser to the processor's hosted page, and from the processor back to Zenoti for post-payment callbacks. Terminal-integrated processors also require HTTPS from the POS (Point of Sale) client or the card reader to the processor's cloud. Review the processor-specific article for the exact hostnames to whitelist.

Failure-mode coverage

Every processor article in this category now includes a failure-mode table covering: processor unreachable, auth expired, card declined, amount out of range, currency mismatch, and settlement failure. Use the processor's article when triaging a failed transaction in the POS β€” the failure modes and resolutions are processor-specific.

Reconciliation

Every processor article names the Zenoti-side report (Collections filtered by payment method), the processor-side report or dashboard, the match-key fields, and a recommended cadence. The standard match-key pair is processor transaction ID + Zenoti invoice number; daily reconciliation is recommended during the first month after go-live, weekly thereafter.

Terminal hardware

Physical card terminals must be associated with the correct payment processor at the center level. Terminal firmware is updated on the terminal itself; enter the firmware update PIN when the terminal prompts for it and refer to your payment processor's terminal documentation for the current PIN. For terminal setup details, see Configure payment terminals and card readers.

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