ZenotiHelp

Processor: Ezypay

ZTZenoti Docs Team Updated September 5, 2026 6 min readGuide

Important β€” Retired. Zenoti discontinued support for EzyPay effective September 30, 2025. New EzyPay integrations cannot be activated. Existing configurations continue to function while Zenoti maintains the integration, but no new feature development or support commitments apply. Merchants still using EzyPay should migrate to a supported payment processor. Contact Zenoti Support or your account manager for migration assistance.

EzyPay is a retired payment processor that was configured at the center level, specialised in recurring billing and subscription-based payment models across Australia and New Zealand (see Regional availability). EzyPay supports card-on-file storage and was commonly used for membership and package auto-billing. This article is retained for reference by merchants completing their migration away from EzyPay.

Regional availability

EzyPay was available in Australia and New Zealand only. The wider Asia-Pacific regions (Singapore, Malaysia, Hong Kong, Philippines, Taiwan) listed in some V1 documentation reflect EzyPay's own geographic footprint, not the Zenoti integration scope.

Before you begin

Permission: You need center-level payment configuration permissions to configure EzyPay.

EzyPay merchant-side prerequisites

  • EzyPay merchant account activated for your region and settlement currency.
  • Direct-debit mandates β€” if you plan to run recurring direct-debit billing, EzyPay must enable the relevant local rail (DD in AU/NZ, GIRO in SG, etc.) on your merchant account.
  • Card-on-file enrolment β€” EzyPay provisions a customer vault linked to your MID (Merchant Identifier). Stored cards live in the EzyPay vault (local tokens), not in a global Zenoti vault.
  • Return / callback URL β€” EzyPay must know the Zenoti domain to send post-payment callbacks to.

Credentials

Field Source / owner What to enter
Merchant ID EzyPay account representative The MID issued on merchant activation.
API key / secret EzyPay account representative API key bound to the MID; used to sign transaction, refund, and void requests.

Note: Zenoti does not provide default credentials. Contact your EzyPay representative for the test-environment key before go-live.

Network requirements

Direction Port Protocol Why
Outbound from Zenoti to EzyPay API 443 HTTPS Charge, refund, void, status calls
Outbound from EzyPay back to Zenoti 443 HTTPS Post-payment and direct-debit status callbacks

EzyPay capabilities in Zenoti

Capability Supported
Online card payments Yes
Stored accounts (card on file) Yes
Global tokenization (shared token across processors) No β€” EzyPay tokens are local to EzyPay
Refund (full) Yes
Refund (partial) [SOURCE GAP β€” PM VERIFY]
Void (pre-settlement) Yes
Recurring / direct-debit billing Yes (EzyPay's core use case)
Terminal (POS (Point of Sale)) No
Webstore (HPP (Hosted Payment Page)) Yes

Configure EzyPay

  1. At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
  2. Select EzyPay as the payment processor.
  3. Enter the credentials from the credentials table above.
  4. Enable the payment types you want to accept.
  5. Select Save.
  6. Select Test to verify the credentials.

Toggle interactions

Card save on file (center) Recurring billing (memberships / packages) Behaviour
Off Off Only one-off guest-present payments. No auto-renewal.
On Off Cards stored for return-visit convenience, but no scheduled charges.
Off On Recurring schedules configured but will fail without a stored card β€” Zenoti prompts guests for card entry at the first charge and does not store it. Not a usable combination for memberships.
On On Recommended for subscription / membership businesses. Cards are stored and charged on the membership schedule.

Process a payment

One-off (guest-present) payment:

  1. On the invoice, select EzyPay.
  2. The guest enters card details (or staff selects an existing stored card).
  3. Zenoti calls EzyPay; the transaction result is returned inline.
  4. The invoice is closed on success.

Recurring payment (membership / package):

  1. The guest enrols in a membership or package; Zenoti stores the card in the EzyPay vault.
  2. On each scheduled billing date, Zenoti triggers an EzyPay charge using the stored token.
  3. Successful charges close the corresponding Zenoti invoice automatically. Failed charges flow into the dunning pipeline β€” see Recover failed transactions.

Manage stored accounts

See Manage stored payment accounts for the guest-profile workflow. Because EzyPay does not support global tokenization, cards stored against EzyPay cannot be moved to another processor without re-enrolment by the guest.

Process a refund

Refunds use the Merchant ID and API key configured at setup.

  1. Open the guest's invoice.
  2. Select the EzyPay transaction.
  3. Select Refund.
  4. Confirm. EzyPay returns a refund reference.

Refund β€” dual-system perspective

System What happens
Zenoti Negative payment line on the invoice; Collections report row referencing the original transaction.
EzyPay Separate refund record against the original charge ID; appears as a negative entry on the EzyPay merchant settlement report. Manual reconciliation uses the EzyPay charge reference or the Zenoti invoice number.

Process a void

Voids cancel an authorised but unsettled charge.

  1. Open the invoice.
  2. Select the EzyPay transaction.
  3. Select Void.
  4. Confirm.

After settlement, voids are unavailable β€” use a refund.

Edit or reverse a posted payment

Invoice state What you can do
Open Remove the payment line, then void (pre-settlement) or refund (post-settlement).
Closed Reopen if permissions allow, or post a compensating refund. The original line is preserved for audit.

Direct debit (bank account) flow

EzyPay supports direct debit from bank accounts as an alternative to card-on-file billing (AU/NZ only, subject to your EzyPay merchant agreement).

First transaction β€” bank account entry and authorization

  1. At checkout, the guest selects Direct Debit as the payment method.
  2. The guest enters their Bank Account Number and Bank Code (BSB in AU; branch code in NZ).
  3. EzyPay requires the guest to provide an authorization signature on the first direct-debit transaction β€” this is the mandate that authorizes future recurring debits from the same account.
  4. Staff capture or obtain the authorization form (digital or paper, per your EzyPay merchant agreement and regional regulatory requirements). Retain the authorization form as required by APCA/BECS rules (AU) or your NZ bank.
  5. EzyPay stores the bank account details against the guest's profile. The authorization covers all future recurring debits from this account.

Subsequent transactions β€” stored account

After the first successful direct-debit transaction, EzyPay stores the bank account details in the EzyPay vault (local token). No re-entry of account details or re-authorization is required for subsequent charges against the same account. Staff can select the stored bank account the same way as a stored card.

Important β€” dispute non-defendability. Direct-debit disputes (AU/NZ DDRs) are not defendable in the same way as card chargebacks. If a guest disputes a direct-debit authorization, the bank typically returns the funds without a dispute evidence window. Retain signed authorization mandates for the period required by your regional rules (APCA: 12 months after last use for AU; check NZ regulations separately).

Failure modes

Failure mode User-visible symptom Resolution
EzyPay API unreachable Transaction fails with a communication error. Check outbound HTTPS and EzyPay status. Retry.
Authentication expired / wrong API key Every call fails with an auth error. Re-verify with EzyPay; re-enter the key.
Card declined (guest-present) Inline decline; invoice stays open. Guest retries or uses another method.
Stored-card decline (recurring) Scheduled charge fails; invoice stays in the dunning queue. Zenoti retries per dunning configuration; notify the guest to update their card. See Update card details automatically for auto-update scope (EzyPay is not in the supported list).
Amount out of range Rejected at the gateway. EzyPay enforces per-market minimums and maximums; contact EzyPay for current limits.
Currency mismatch Transaction rejected. Confirm the center currency matches what EzyPay has activated for the MID.
Settlement failure Charge approved but missing from settlement. Raise with EzyPay using the charge reference; do not re-bill.
Direct-debit bounce (AU/NZ) Charge appears successful for days, then reverses when the bank returns the debit unpaid. The invoice reopens; the guest must provide an alternate method. This is a normal EzyPay workflow.

Settlement and reconciliation

Settlement timing depends on the region and the channel (card vs direct debit). Direct debits in AU/NZ settle T+3 and can reverse up to several days later if the bank returns the debit unpaid. [SOURCE GAP β€” PM VERIFY: exact T+N per region and channel.]

Source Report / view Match key
Zenoti Collections report (filter: Payment Method = EzyPay) EzyPay charge reference + Zenoti invoice number
EzyPay Settlement / transaction report in the EzyPay merchant portal Same fields

Recommended cadence: daily β€” direct-debit reversals in particular must be caught quickly to chase the guest.

Tips

  • EzyPay is well-suited for membership and package billing where recurring payments are needed.
  • Contact your EzyPay account representative if you encounter authentication errors.
  • Because EzyPay tokens are local, migrating stored cards away from EzyPay requires each guest to re-enter their card on the new processor.
Was this article helpful?
Your feedback helps us improve our documentation.