ZenotiHelp

Processor: Airpay

ZTZenoti Docs Team Updated September 28, 2026 11 min readGuide

AirPay is an actively supported V1 payment processor for the India market. It is configured at the center level and processes transactions exclusively in Indian Rupees (INR). AirPay supports POS (Point of Sale) terminal payments, Webstore hosted payment page (HPP) payments, and multiple Indian payment methods including cards, UPI, net banking, and EMI.

Important: AirPay does NOT support CMA (Customer Mobile App) payments. If your business uses the Zenoti mobile app for guest payments, you need to use a different processor for mobile transactions.

Audience: Center administrators and front-desk staff who configure or process payments using AirPay.


On this page


Before you begin

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

Admin path: Configuration > Payments > Settings (center scope) > Payment processor

  • Active AirPay merchant account.
  • Center currency set to INR.
  • Compatible AirPay-certified POS card reader (if you plan to accept terminal payments).

The credential fields in Zenoti's AirPay configuration screen are:

Field Source / owner What to enter
Merchant Id AirPay account representative The MID issued on AirPay merchant activation.
Secret Key AirPay account representative API secret for your merchant account. Also used to authorise voids β€” there is no separate "void password."
Username AirPay account representative AirPay API username for your merchant account.
Password AirPay account representative API password bound to the username.
Terminal uniqueid AirPay terminal provisioning team One per physical POS terminal; printed on the device or listed in the AirPay merchant portal.

AirPay merchant-side prerequisites

Complete these on the AirPay side before starting the Zenoti configuration. Your AirPay account representative is the owner of each value listed below.

  • Merchant account activation β€” AirPay must activate your MID (Merchant Identifier) for the region and currency (INR) you operate in. Certain payment channels (EMI, net banking banks) require per-channel activation by AirPay.
  • Terminal enrolment β€” For each physical terminal, AirPay assigns a uniqueid. You will need one per terminal device.
  • Webhook / return URL allow-list β€” AirPay must know the Zenoti domain that will receive hosted-page returns. Confirm this with your AirPay representative before testing Webstore payments.

Network requirements

Direction Port Protocol Why
Outbound from Zenoti to AirPay gateway 443 HTTPS Transaction, refund, void, and status-polling API calls
Outbound from AirPay hosted page back to Zenoti (Webstore) 443 HTTPS Payment-completion callback that closes the invoice
Outbound from POS browser/terminal to AirPay terminal API 443 HTTPS Cloud-routed terminal transactions

Plain HTTP is not supported. If your center is behind a restrictive firewall, whitelist the AirPay gateway hostname provided by your AirPay representative.

Supported payment methods

AirPay supports the following payment methods for the India market:

Payment method Description
Credit/Debit Cards Standard card payments via payment gateway
UPI Unified Payments Interface β€” real-time bank-to-bank transfers
Net Banking Direct bank transfers via online banking portals
EMI Equated Monthly Installments β€” split payments over time
Prepaid Cards Prepaid card payments
BharatQR QR code-based payments
AmexEZEclick Amex one-click payment

Note: Transaction limits vary by payment method and are enforced by the AirPay gateway, not by Zenoti. For example, UPI has per-transaction caps, wallets have balance limits, and net banking may have daily limits set by the issuing bank. Contact your AirPay account representative for current method-specific limits.

Supported platforms

Platform Supported Details
POS Terminal Yes In-store payments via card reader terminal
Webstore (HPP) Yes Online payments via AirPay hosted payment page
Consumer Mobile App (CMA) No Not supported β€” use a different processor for mobile app payments

AirPay capabilities in Zenoti

Capability Supported
Sale Yes
Refund (full) Yes
Refund (partial) Yes
Multiple partial refunds on one txn Yes
Void (pre-settlement) Yes
Terminal (POS) Yes
Stored accounts No
Card saving / Tokenization No
Recurring payments No
Currency INR only

Configure AirPay

AirPay is a V1 processor. Configure it at the center level, not through the organization-level onboarding flow.

Steps

  1. At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
  2. Select AirPay as the payment processor.
  3. Enter your AirPay credentials (see the credentials table above).
  4. Enable the payment types you want to accept.
  5. Select Save.
  6. Select Verify to confirm the credentials are valid.

For POS terminal payments, configure the card reader terminal:

  1. In the AirPay processor settings, locate the terminal configuration section.
  2. Enter a descriptive Terminal Name label (for example, "Front Desk Terminal 1").
  3. Enter the device Serial Number printed on the device label.
  4. Enter the AirPay-assigned terminal uniqueid for each terminal device.
  5. Test the terminal connection by processing a low-value test transaction and voiding it immediately after.

Tip: After configuration, verify end-to-end function by processing a β‚Ή1 test transaction using a real card (not a test card), confirming the payment appears in the Zenoti Collections report, then voiding it. This confirms both the API credentials and the terminal routing are correct.

Toggle interactions

When more than one AirPay payment channel is enabled, they operate independently β€” both are offered to the guest on the hosted payment page, and the guest picks one. The matrix below shows the common two-channel combinations; extend the pattern for more channels.

Cards UPI Behaviour on Webstore HPP
Off Off AirPay cannot be used as a payment option.
On Off Guest sees the card form only.
Off On Guest sees UPI collect/intent only.
On On Guest sees both and picks; Zenoti records the channel the guest picked.

The same rule applies to Net Banking and EMI toggles. Enabling a channel in Zenoti does not override an AirPay-side disabled state β€” AirPay must have the channel activated for the merchant account.

Worked example: two-channel setup

A center wants to accept both credit/debit cards and UPI. The administrator enables both toggles in Zenoti, and AirPay has already activated both channels on the merchant account. At checkout on the Webstore, the guest sees: (1) a card-entry form and (2) a UPI collect prompt. The guest selects UPI and completes payment via their banking app. Zenoti records the payment channel as UPI and closes the invoice. No further configuration is needed on the Zenoti side.

Process payments

POS terminal payments

When a guest pays at the POS terminal:

  1. The front-desk staff selects AirPay as the payment method on the invoice.
  2. Zenoti sends the payment request to the AirPay terminal using the configured terminal unique ID.
  3. The guest completes the payment on the terminal β€” chip insertion, swipe, or contactless tap for cards; QR scan for UPI and BharatQR.
  4. The terminal returns the transaction result to Zenoti, and the invoice is updated accordingly.

Note: AirPay terminal transactions support chip insertion, magnetic stripe swipe, and contactless (NFC/tap) for card payments. PIN entry support depends on the specific terminal model and AirPay's provisioning for your merchant account.

Webstore (online) payments

When a guest pays on the Webstore:

  1. The guest selects AirPay as the payment method during checkout.
  2. The guest is redirected to the AirPay hosted payment page and selects their preferred channel.
  3. The guest completes the payment on the AirPay page.
  4. AirPay redirects the guest back to the Webstore with the payment confirmation, and the invoice is closed.

If the payment fails mid-flow, the guest sees a prompt to retry or select an alternative method. From the business side, failed or abandoned online payments remain in an "initiated" status in Zenoti. The system polls AirPay for up to 2 days; if no confirmation is received, the transaction is marked failed and the invoice remains open for re-payment. See Failure modes below.

Note: AirPay requires the guest's email address, phone number, and name for billing validation on Webstore (HPP) transactions. Ensure guest profiles have these fields populated before processing online payments.

Process refunds

AirPay supports both full and partial refunds on settled transactions. Multiple partial refunds are allowed up to the original transaction amount.

Full refund

  1. Open the guest's invoice in Zenoti.
  2. Select the transaction to refund.
  3. Select Refund. The full transaction amount is pre-filled.
  4. Confirm the refund. The refund is processed through AirPay and a confirmation ID is returned.

Partial refund

  1. Open the guest's invoice.
  2. Select the transaction to refund.
  3. Select Refund and enter an amount less than the original transaction total.
  4. Confirm the refund.

You can process multiple partial refunds on the same transaction until the total refunded equals the original charge. Each returns its own AirPay confirmation ID.

Note: Refunds can only be processed after the transaction has been settled by AirPay. For same-day cancellations before settlement, use the void option instead.

Refund β€” dual-system perspective

System What happens
Zenoti Creates a negative payment line on the invoice; Collections report shows a matching refund row referencing the original transaction.
AirPay Creates a separate refund transaction with its own reference ID; appears on the AirPay settlement report as a negative line against the original MID entry. Manual reconciliation uses the Zenoti invoice number or the AirPay original transaction ID as the match key.

Process voids

A void cancels a transaction before it has been settled by AirPay. Voids authenticate using the same merchant secret/password configured during setup β€” there is no separate "void password."

  1. Open the guest's invoice.
  2. Select the transaction to void.
  3. Select Void. Zenoti sends a void request to AirPay using the original transaction reference number (RRN).
  4. Once confirmed, the transaction is cancelled and no funds are transferred.

Note: Voids are only available for same-day transactions that have not yet been settled. After settlement, use a refund.

Edit or reverse a posted payment

The editable surface depends on the invoice state:

Invoice state What you can do
Open (unclosed) Remove the AirPay payment line and re-take the payment. If AirPay has already authorised, void (pre-settlement) or refund (post-settlement) first, then remove the line.
Closed (posted) You cannot edit a posted payment directly. Reopen the invoice if your permissions allow, or post a correcting refund. The original posted payment line is preserved for audit.

Failure modes

Failure mode User-visible symptom Resolution
AirPay gateway unreachable Terminal shows "communication error"; Webstore shows "payment service unavailable." Check AirPay status page and outbound HTTPS from Zenoti / the terminal. Retry. Invoice remains open.
Authentication expired / wrong credentials All transactions fail at the first API call with an auth error. Re-verify Merchant ID, Username, and Password with your AirPay representative. Re-enter in Zenoti.
Card declined Terminal or HPP shows an issuer decline reason. Ask the guest to try another card or channel. No invoice side-effect; the attempt is logged but no payment line is written.
Amount out of range (per-channel limit) HPP / terminal shows "amount exceeds limit." AirPay enforces channel-specific caps (UPI, wallet, EMI). Ask the guest to split the payment across channels or use a different method.
Currency mismatch Transaction rejected at gateway. AirPay supports INR only. Ensure the center's currency is INR.
Connectivity loss mid-transaction Terminal loses network connection during an in-progress payment; result is unknown. Do not re-charge until you confirm the transaction status in the AirPay merchant portal using the RRN. If confirmed successful, close the invoice. If not found, the transaction did not complete β€” re-take payment.
Timeout error Terminal or Webstore shows a timeout message before a result is returned. Common causes: slow network, gateway congestion, or an oversized payload. Retry once. If the timeout recurs, check network connectivity and contact AirPay support with the terminal ID and approximate transaction time.
Settlement failure (post-approval) Transaction approved but reconciliation report shows a settlement hold. Raise with AirPay support using the RRN; do not re-charge the guest. The transaction remains in Zenoti.
Webstore mid-flow abandonment Transaction stays in "initiated" in Zenoti for up to 2 days, then auto-fails. Zenoti's polling handles this β€” no manual action needed unless the guest asks about a stuck invoice; reopen and clear if the invoice is still open.

Settlement and reconciliation

AirPay deposits funds into your bank account within 2 working days of the transaction date. Working days exclude weekends (Saturday and Sunday) and Indian bank holidays, including national holidays and regional festival periods (such as Diwali, Holi, and state-specific bank holidays). During extended holiday periods, settlement may take longer.

Example: A transaction processed on Monday, March 10 would typically be deposited by Wednesday, March 12. However, if March 11 is a bank holiday, the deposit would arrive on Thursday, March 13.

Reconcile AirPay transactions

Use the Collections – Online Transactions report in Zenoti and the Airpay reconciliation report available in your Airpay merchant portal for transaction reconciliation.

Source Report / view Match key
Zenoti Collections – Online Transactions report (filter: Payment Method = AirPay) AirPay transaction ID / RRN + invoice number
AirPay Airpay reconciliation report in the AirPay merchant portal Same fields

Recommended cadence: daily for high-volume centers, weekly for low-volume. Investigate any row that appears in one report but not the other β€” common causes include pending refunds, voided transactions, or transactions still in processing.

Tips

  • AirPay processes transactions exclusively in Indian Rupees (INR). Ensure the center's currency is set to INR before enabling AirPay.
  • AirPay does not support card saving or tokenization. Each transaction requires the guest to enter payment details fresh.
  • Contact your AirPay account representative if authentication errors occur during setup or transactions.
  • If a POS terminal payment fails, check the terminal's network connection and verify the terminal unique ID is correctly configured.
  • Failed online payments are polled for up to 2 days. If a transaction remains in "initiated" status beyond this period, it is marked failed.
  • AirPay requires the guest's email address, phone number, and name for billing validation. Ensure guest profiles have these fields populated before processing online payments.
  • For centers with multiple terminals, assign a distinct uniqueid to each device and label each terminal clearly in Zenoti to avoid routing errors.
  • Enable only the payment channels that AirPay has activated on your merchant account. Enabling a channel in Zenoti that AirPay has not activated will result in transaction failures.
  • If a connectivity loss occurs mid-transaction, always verify the transaction status in the AirPay merchant portal before re-charging the guest to avoid double billing.

Troubleshooting

Problem Symptom Resolution
AirPay not appearing as a payment option at checkout Payment method is missing in the POS or Webstore Confirm AirPay is configured and saved at Configuration > Payments > Settings for this center. Verify the processor is set to active.
All transactions failing with an auth error Every payment attempt returns an authentication failure Re-enter the Merchant ID, Username, Secret Key, and Password. Use Verify to confirm credentials are correct.
Terminal not responding POS terminal shows a connection or communication error Check the terminal's network connection. Confirm the uniqueid in Zenoti matches the value from AirPay. Restart the terminal if needed.
Connectivity lost mid-transaction Terminal or Webstore shows a timeout or communication error and result is unknown Do not retry immediately. Check the AirPay merchant portal for the transaction using the terminal ID and approximate time. If confirmed, close the invoice. If not found, re-take payment.
Webstore payment stuck in "initiated" Invoice remains open and guest says they completed payment Zenoti polls for up to 2 days. If the guest has a bank confirmation, raise with AirPay support using the RRN. If the 2-day window has passed, the transaction is auto-marked failed; reopen the invoice and re-take payment.
Settlement not received within expected period Bank deposit does not arrive within 2 working days Check for Indian bank holidays in the settlement window. If the delay exceeds the holiday-adjusted period, contact AirPay support with the RRN.
Was this article helpful?
Your feedback helps us improve our documentation.