Zippay (zip) payment processor
Configure ZipPay as a Buy Now Pay Later (BNPL) payment option for your Australian centers. ZipPay allows guests to make purchases now and pay later using the Zip in-store code flow.
Note: ZipPay is available only in Australia. It is a custom payment integration β not a V1 or V2 processor. It is configured using a custom payment agent.
Important β not supported for scheduled payments. ZipPay does not support scheduled (recurring) payments for memberships or packages. ZipPay is for one-time in-store transactions only. Do not use ZipPay as a payment method for membership auto-billing or package payment plans.
Audience: Center administrators and front-desk staff who process in-store payments.
Before you begin
Permission: You need center-level payment configuration permissions to configure ZipPay.
Zip merchant-side prerequisites
- Active Zip merchant account activated for in-store code purchases in Australia.
- In-store programme enrolment β Zip must enable the in-store code flow on your MID (Merchant Identifier) (some Zip merchant types are online-only).
- Location registration β each physical center must be registered with Zip; Zip issues one Location ID per registered location.
Credentials
| Field | Source / owner | What to enter |
|---|---|---|
| Location ID | Zip merchant portal / account representative | The Location ID assigned to this center. |
| Merchant In-store API Key (V1) | Zip merchant portal / account representative | Used for Basic auth (Base64-encoded) against the Zip in-store API. Treat as sensitive. |
Network requirements
| Direction | Port | Protocol | Why |
|---|---|---|---|
| Outbound from Zenoti to Zip in-store API | 443 | HTTPS | Purchase-request and status calls |
| Outbound from Zip to guest's Zip app | (Zip-side) | Handled by Zip; not a Zenoti concern. |
How ZipPay works
ZipPay uses an in-store code flow for payment:
- The guest logs in to their Zip account using the Zip mobile app or web wallet.
- The guest selects Shop In-Store and receives an in-store code.
- The guest provides the in-store code to the front desk.
- The front desk selects the ZipPay custom payment agent and enters the code in the Collect Payment screen.
- The guest sees a payment confirmation screen on their device and confirms the transaction.
- Zenoti retrieves the payment status via the Zip in-store API and closes the invoice.
Steps
Create a ZipPay custom payment agent
- At the organization or center level, navigate to Configuration > Payments > Custom payments > Allow custom payments.
- Select Add.
- Configure the following fields:
- Name β Enter a name for the payment agent (for example, "ZipPay").
- Description β Enter a description for the ZipPay payment.
- Active β Select this checkbox so that ZipPay appears as a payment option in the POS (Point of Sale) window.
- Monetary - Financial β Select this checkbox so that ZipPay payments appear in Sales reports.
- Monetary - Royalty β Select this checkbox so that ZipPay payments appear in Royalty reports.
- Select Finish.
Set up ZipPay at the center level
- At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
- Under Additional Payment Options, expand zipPay.
- Select Use center settings and configure the following fields:
- Enable zip β Select this option to enable ZipPay at the center.
- Agent Name β Select the ZipPay custom payment agent you created.
- Merchant API Key β Enter your Merchant In-store API Key V1 (provided by Zip).
- Store Location ID β Enter your Zip Location ID (provided by Zip).
- Select Save.
- (Optional) Select Test to verify that the credentials are valid.
Toggle interactions
| Organization-level ZipPay (if configured) | Center-level "Use center settings" | Behaviour |
|---|---|---|
| Off | Off | ZipPay unavailable. |
| On | Off | Center inherits organization-level configuration. |
| Off | On | Center-level configuration applies. |
| On | On | Center-level configuration overrides organization-level. |
Collect a ZipPay payment
- Launch the POS window for the appointment.
- Review and edit the invoice if needed.
- In the Collect Payment section, select Custom.
- Select the ZipPay custom payment agent from the drop-down list.
- Ask the guest for their in-store code (generated from the Zip app or web wallet).
- Enter the in-store code in the Store Code field.
- Select Add Payment.
- The guest confirms the payment on their device.
- Select Print or Email to close the invoice.
Process a refund
Refunds are initiated from Zenoti only. Do not issue refunds from the Zip merchant dashboard β it does not sync back to Zenoti.
Refund β dual-system perspective
| System | What happens |
|---|---|
| Zenoti | Negative payment line on the invoice; Collections report shows the refund row against the ZipPay agent. |
| Zip | Refund posted against the original purchase request on Zip's side; guest's Zip repayment schedule adjusts accordingly. Match key: Zip purchase request reference or Zenoti invoice number. |
Edit or reverse a posted payment
| Invoice state | What you can do |
|---|---|
| Open | Remove the ZipPay line if the guest has not yet confirmed on their device. If already confirmed, process a refund. |
| Closed | Reopen if permissions allow, or post a compensating refund. Do not mirror this on Zip's side β refunds from Zenoti sync through. |
Failure modes
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| Zip API unreachable | Payment fails with communication error. | Check HTTPS connectivity and Zip service status. Invoice stays open. |
| HTTP 401 / 403 | Authorization failure. | Verify the Merchant API Key is correct and active in the Zip merchant portal. |
| HTTP 404 | Invalid transaction ID or expired in-store code. | Ask the guest to generate a new in-store code from the Zip app. |
| Guest declines on device | Charge never completes. | Guest can retry with a new code or use a different payment method. |
| Amount out of range | Zip enforces eligibility limits per guest. | Guest uses a different payment method. |
| Currency mismatch | Payment rejected. | ZipPay supports AUD only; confirm the center currency is set to Australian dollars. |
| Settlement / funding failure | Approved in Zenoti but missing from settlement. | Raise with Zip using the purchase-request reference number. |
Settlement and reconciliation
Zip funds merchants on a schedule defined in the merchant agreement. Contact your Zip account representative to confirm your specific funding cadence, cutoff times, and the treatment of Australian public holidays.
| Source | Report / view | Match key |
|---|---|---|
| Zenoti | Collections by Invoices report (filter: Payment Agent = your ZipPay agent) | Zip purchase-request reference + Zenoti invoice number |
| Zip | Zip merchant dashboard settlement / funding report | Same fields |
Recommended cadence: reconcile weekly, aligned to the Zip funding cycle.
Limitations
- Australia only β ZipPay is supported only in Australia.
- No scheduled payments β ZipPay cannot be used for recurring membership charges or scheduled package charges.
- No charge-back management β Charge-backs are handled directly by Zip. Contact Zip for charge-back disputes.
- Refunds β Process ZipPay refunds through Zenoti only. Do not issue refunds directly from the Zip merchant dashboard.
Tips
- Use the Collections by Invoices report to review ZipPay payments and refunds. Filter by the ZipPay custom payment agent name.
- If center-level settings are configured, they override organization-level settings.
- ZipPay mobile payments are also supported through Zenoti Mobile.
- Always ask the guest to generate a fresh in-store code at the time of payment β codes expire quickly and cannot be reused.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| ZipPay does not appear in the POS payment options | The custom payment agent is not marked Active, or ZipPay is not enabled at the center level. | Confirm the agent's Active checkbox is selected and that Enable zip is turned on in the zipPay accordion under Additional Payment Options on Configuration > Payments > Settings (center scope). |
| "Authorization failure" error when entering the in-store code | The Merchant API Key entered in Zenoti is incorrect, expired, or has been rotated in the Zip portal. | Log in to the Zip merchant portal to retrieve the current Merchant In-store API Key V1, update the Merchant API Key field in the zipPay accordion under Additional Payment Options on Configuration > Payments > Settings (center scope), select Save, and retry. |
| Code entered correctly but payment does not complete | The in-store code has expired (codes are short-lived) or the guest's Zip account has insufficient credit. | Ask the guest to open the Zip app and generate a new in-store code. If the issue persists, the guest should contact Zip support to check their account status. |