ZenotiHelp

Processor: Plutus (PineLabs)

ZTZenoti Docs Team Updated September 5, 2026 9 min readGuide

Plutus (PineLabs) is a V1 payment processor configured at the center level. It processes card, UPI, and EMI payments through PineLabs cloud-connected terminals, primarily serving the Indian market. All transactions are routed through the PineLabs Cloud API.

Important β€” Unsupported features: Plutus does not support refunds, voids, stored accounts (card saving), recurring payments, or Webstore purchases through Zenoti. CanProcessorSaveCards = false, SupportsGlobalTokenization = false, and the processor class has no RefundTransaction or VoidTransaction methods. Review the Limitations section before setup to confirm Plutus meets your center's payment requirements.


On this page


Before you begin

Permission: You need center-level payment configuration permissions to configure Plutus (PineLabs).

PineLabs merchant-side prerequisites

Complete these on the PineLabs side before starting the Zenoti configuration.

  • PineLabs merchant account β€” activated by PineLabs for the region and card schemes you accept.
  • Terminal registration β€” each physical terminal must be registered with PineLabs Cloud and provisioned with a store POS (Point of Sale) code. PineLabs performs this during terminal delivery.
  • EMI activation (optional) β€” Brand EMI and Bank EMI are separately activated by PineLabs per merchant and per partner bank. Confirm activation before enabling either in Zenoti.

Credentials

Field Source / owner What to enter
Merchant ID PineLabs account representative Unique merchant identifier assigned by PineLabs.
Security Token PineLabs account representative 32-character API authentication token. Keep secure; store only in the Zenoti payment settings page.
Device IMEI Printed on the physical terminal / PineLabs portal The IMEI of each PineLabs terminal at this center. One entry per terminal.
Merchant Store POS Code PineLabs account representative Store-level POS identifier issued by PineLabs for this terminal.

Ensure each terminal is powered on, connected to the internet, and registered with your PineLabs merchant account before configuring it in Zenoti.

Network requirements

Direction Port Protocol Why
Outbound from PineLabs terminal to PineLabs Cloud 443 HTTPS (TLS 1.2) Terminal-side payment processing. Handled by the terminal's network connection.
Outbound from Zenoti to PineLabs Cloud API 443 HTTPS (TLS 1.2) Transaction initiation and status polling.

If either leg loses internet connectivity, transactions fail immediately β€” Plutus does not queue offline.

Key details

Detail Value
Configuration level Center (V1 processor)
Navigation Configuration > Payments > Settings (center scope)
Market India
Cloud-based Yes β€” PineLabs Cloud API
Refund Not supported
Void Not supported
Stored accounts Not supported
Recurring payments Not supported
Cancel pending transaction Yes β€” pending transactions only, before terminal approval
Auto-cancel timeout 2 minutes

Plutus (PineLabs) capabilities in Zenoti

Capability Supported Notes
Card payments Yes Credit and debit cards via terminal
UPI Sale Yes UPI payment through terminal
UPI Bharat QR Yes QR code-based UPI payment
Brand EMI Yes Organization-level toggle required
Bank EMI Yes Organization-level toggle required
Terminal (POS) Yes PineLabs cloud-connected terminals
Multiple terminals per center Yes Each terminal uses its own Device IMEI and POS Code
Stored accounts (card saving) No Each transaction requires guest to present card or scan QR
Refund No Contact PineLabs directly for refunds
Void No Only pending transactions can be cancelled
Recurring payments No Cannot be used for membership billing or scheduled charges
Webstore purchases No Not available for online transactions

Configure Plutus (PineLabs)

Center-level terminal setup

  1. At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
  2. Select Plutus (PineLabs) as the payment processor.
  3. Enter your PineLabs credentials:
  • Merchant ID
  • Security Token
  1. Configure the terminal device:
  • Device IMEI β€” The IMEI number of the PineLabs terminal at this center.
  • Merchant Store POS Code β€” The store-level POS identifier for this terminal.
  1. Enable the payment types you want to accept.
  2. Select Save.

Enable EMI payment modes (organization level)

Brand EMI and Bank EMI are controlled by organization-level settings, not center-level configuration:

  • Brand EMI β€” Enable the organization-level Brand EMI setting to allow installment payments through brand partnerships.
  • Bank EMI β€” Enable the organization-level Bank EMI setting to allow installment payments through bank partnerships.
  • Additional payment modes β€” Your organization can enable additional PineLabs payment modes at the organization level. Contact your PineLabs representative for the list of available payment mode codes.

Toggle interactions (EMI modes)

Brand EMI and Bank EMI operate independently at the org level. When both are enabled, the terminal offers the guest a selection between brand and bank EMI options on eligible cards. When only one is on, only that flow is offered.

Brand EMI (org) Bank EMI (org) Behaviour at checkout
Off Off No EMI option appears; guest pays upfront.
On Off Terminal offers Brand EMI plans only (requires card partnered with the brand programme).
Off On Terminal offers Bank EMI plans only (based on issuing bank eligibility).
On On Terminal offers both sets of plans; guest picks. Eligibility depends on the guest's card.

Note: EMI availability also depends on the guest's card eligibility and the bank or brand partnership terms. Not all cards qualify for EMI.

Process a payment with Plutus

After setup, front-desk staff can accept Plutus payments at checkout:

  1. On the invoice, select a Plutus payment method (Card, UPI Sale, UPI Bharat QR, Brand EMI, or Bank EMI).
  2. Zenoti sends the transaction to the PineLabs terminal via the Cloud API.
  3. The guest completes the payment on the PineLabs terminal device (tap, swipe, insert card, or scan QR code).
  4. Zenoti polls the PineLabs Cloud API for the transaction result.
  5. When the terminal confirms approval, the payment is applied to the invoice automatically.

[!CAUTION] Do not close the payment window while a transaction is in progress. The transaction continues processing on the PineLabs terminal even if the Zenoti window is closed, resulting in inconsistent data between Zenoti and Plutus. Always wait for the transaction to complete or explicitly cancel it.

Important: If the guest does not complete the transaction on the terminal within 2 minutes, Zenoti automatically cancels the pending transaction. The front-desk staff must re-initiate the payment.

Cancel a pending transaction

You can cancel a transaction only while it is still pending on the PineLabs terminal β€” that is, before the guest completes the payment. Once the terminal approves a transaction, it cannot be voided or refunded through Zenoti.

To cancel a pending transaction, select Cancel during the payment process before the terminal returns a result.

Edit or reverse a posted payment

Invoice state What you can do
Open (unclosed, payment not yet recorded) Cancel the pending transaction on the terminal as described above.
Open (payment recorded, invoice unclosed) Plutus does not support void or refund. Remove the Plutus payment line only if you are absolutely certain no money moved at the terminal β€” otherwise record the payment, close the invoice, and process a refund outside Zenoti (see below).
Closed (posted) You cannot edit or reverse a posted Plutus payment through Zenoti. Contact PineLabs directly to issue a refund, then post a compensating refund line in Zenoti as an "Other" or custom payment to keep the ledger balanced. Mark the refund in the guest's notes with the PineLabs refund reference.

Failure modes

Failure mode User-visible symptom Resolution
PineLabs Cloud unreachable Terminal or Zenoti reports "Cloud API error." Check internet at both the terminal and Zenoti. Plutus does not queue offline β€” retry when connectivity is restored.
Authentication expired / wrong token Every transaction fails with "Invalid Account Details." Re-verify Merchant ID and Security Token with PineLabs. Re-enter in Zenoti.
Terminal not found (IMEI mismatch) Transaction fails with IMEI or device-ID error. Verify the IMEI printed on the physical device matches the configured IMEI.
Card declined Terminal shows issuer decline. Ask the guest to try another card or payment channel.
Amount out of range (EMI) EMI option rejected at terminal. EMI plans have per-bank minimum/maximum amounts. Guest must use a non-EMI method or a different card.
Currency mismatch Transaction not attempted. Plutus processes INR only for the Indian market. Confirm center currency is INR.
Settlement failure Approved on terminal but missing from PineLabs settlement report. Contact PineLabs with the terminal's transaction reference. Do not re-charge.
2-minute terminal timeout Transaction auto-cancelled after 2 minutes of inactivity. Re-initiate at the POS.

Settlement and reconciliation

PineLabs settlement timing depends on your merchant agreement and the payment channel used (card, UPI, EMI have different settlement cadences). [SOURCE GAP β€” PM VERIFY: exact T+N for each channel.] Working days in India exclude weekends and bank holidays (including regional festival holidays such as Diwali and Holi).

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

Recommended cadence: daily for high-volume centers, weekly otherwise. Because Plutus has no refund or void surface in Zenoti, reconciliation discrepancies are usually resolved on the PineLabs side.

Limitations

  • No refund β€” Plutus does not support refunding completed transactions through Zenoti. For refunds, contact PineLabs directly or use an alternative refund method at the center.
  • No void β€” Completed transactions cannot be voided. Only pending (in-progress) transactions can be cancelled before terminal approval.
  • No stored accounts β€” Plutus does not support saving cards for future use. Each transaction requires the guest to present their card or scan a QR code.
  • No recurring payments β€” Plutus cannot be used for membership billing, package auto-renewals, or scheduled charges.
  • No Webstore purchases β€” Plutus is not available for online or Webstore transactions.
  • Cloud dependency β€” All transactions require an active internet connection between the terminal and the PineLabs Cloud API. If the terminal or center loses internet connectivity, transactions cannot be processed until the connection is restored. Transactions do not queue offline β€” they fail immediately if the cloud is unreachable.
  • 2-minute auto-cancel β€” Transactions that are not completed on the terminal within 2 minutes are automatically cancelled by Zenoti.

Set up multiple terminals

Plutus supports multiple PineLabs terminal devices at a single center. Each terminal is configured with its own Device IMEI and Merchant Store POS Code.

To add additional terminals:

  1. At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
  2. Add a new terminal entry with the Device IMEI and Merchant Store POS Code for the additional device.
  3. Select Save.

When processing a payment, the system routes the transaction to the appropriate terminal based on the card reader selection.

Tip: Verify each terminal's IMEI and POS Code with your PineLabs representative before configuring. An incorrect IMEI or POS Code causes transactions to fail on that terminal.

Troubleshooting

Symptom Possible cause Resolution
Transaction times out after 2 minutes Guest did not complete the payment on the terminal Re-initiate the payment. Ensure the terminal is powered on and connected to the internet.
"Invalid Account Details" error Merchant ID or Security Token is incorrect Verify credentials with your PineLabs account representative and re-enter them in the configuration.
Terminal not responding Terminal lost internet connectivity or is powered off Check the terminal's network connection and power status. PineLabs Cloud API requires an active internet connection.
Transaction declined Card issuer declined the transaction Ask the guest to try a different card or payment method. Check if the card type is supported for the selected payment mode.
EMI option not available at checkout Organization-level EMI settings not enabled, or guest's card does not qualify Verify Brand EMI or Bank EMI is enabled at the organization level. Confirm card eligibility with PineLabs.
Terminal IMEI mismatch error Incorrect Device IMEI configured in Zenoti Verify the IMEI number on the physical terminal device and update the configuration to match.
Transaction completed on terminal but not reflected in Zenoti Network interruption during status polling Check the Collections - Online Transactions report for status. If the transaction shows as initiated, the system attempts to reprocess it automatically.

Device compatibility

PineLabs offers multiple terminal models. The Zenoti integration works with any PineLabs terminal that supports the PineLabs Cloud API. Contact your PineLabs account representative to confirm which terminal models are cloud-API compatible and supported for your merchant account.

Security best practices

  • Protect the Security Token. Store it securely and limit access to authorized payment configuration personnel only. Do not share it via email or messaging platforms.
  • Rotate credentials periodically. Contact PineLabs to regenerate your Security Token per your organization's security policy, or immediately if you suspect the token has been compromised.
  • Keep terminal firmware updated. Ensure all PineLabs terminals run the latest firmware version as recommended by PineLabs for security patches and feature updates.
  • All API communication uses TLS 1.2 encryption between Zenoti and the PineLabs Cloud API.
Was this article helpful?
Your feedback helps us improve our documentation.