ZenotiHelp

Processor: Eghl

ZTZenoti Docs Team Updated September 5, 2026 5 min readGuide

eGHL is a V1 payment processor configured at the center level. It supports hosted-payment-page card and digital-wallet transactions primarily for Southeast Asian markets. eGHL uses V1 configuration only β€” there is no V2 onboarding for eGHL.

Before you begin

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

eGHL merchant-side prerequisites

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

  • eGHL merchant account activated for your region and currency.
  • Per-channel activation β€” eGHL activates card schemes, e-wallets, and local payment rails individually. Confirm each channel you plan to enable in Zenoti is activated on the eGHL side first.
  • Hosted-page return URL β€” eGHL must know the Zenoti domain that receives the post-payment redirect. Share this with your eGHL representative.

Credentials

Field Source / owner What to enter
Merchant ID eGHL account representative The MID (Merchant Identifier) issued on merchant activation.
Password eGHL account representative API password bound to the MID. Used to sign transaction and refund requests.
Provider URL eGHL account representative The eGHL payment gateway endpoint URL. Must be the exact URL provided; test and production URLs differ.

Note: Zenoti does not provide a default Provider URL. Do not guess β€” using a wrong or stale URL causes every transaction to fail.

Network requirements

Direction Port Protocol Why
Outbound from Zenoti to eGHL Provider URL 443 HTTPS Transaction, refund, and void API calls
Outbound from guest browser to eGHL hosted payment page 443 HTTPS HPP (Hosted Payment Page) flow
Outbound from eGHL hosted page back to Zenoti 443 HTTPS Post-payment redirect / server-to-server callback

eGHL capabilities in Zenoti

Capability Supported
Online (HPP) card payments Yes
Digital wallets Yes
Refund Yes (RefundTransaction present)
Void Yes (VoidTransaction present)
Stored accounts / card saving No (CanProcessorSaveCards = false)
Global tokenization No (SupportsGlobalTokenization = false)
Recurring payments via stored cards No β€” each transaction requires fresh guest input on the hosted page
Terminal (POS (Point of Sale)) No (TerminalSupported = false)

Capability correction (April 2026): Stored accounts and recurring payments are NOT supported by eGHL in Zenoti. The processor class has CanProcessorSaveCards = false and no saved-card flow. If you require recurring or stored-card behaviour in the same region, choose a different processor.

Configure eGHL

  1. At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
  2. Select eGHL as the payment processor.
  3. Enter the credentials from the credentials table above.
  4. Enable the payment types you want to accept β€” cards and/or digital wallets.
  5. Select Save.
  6. Select Test to verify the credentials.

Toggle interactions

Card payments Digital wallet Behaviour on HPP
Off Off eGHL cannot be selected at checkout.
On Off HPP shows card entry only.
Off On HPP shows wallet options only.
On On HPP shows card + wallet selection; guest picks. Zenoti records which channel the guest used.

Both sides of a toggle must also be activated on eGHL β€” a Zenoti-side toggle does not override an eGHL-side disabled channel.

Process a payment

  1. The guest selects eGHL on the Webstore checkout.
  2. Zenoti redirects the guest to the eGHL hosted payment page using the configured Provider URL.
  3. The guest completes the payment on the eGHL HPP.
  4. eGHL redirects the guest back to Zenoti and sends a server-to-server confirmation.
  5. Zenoti closes the invoice when confirmation is received.

If the redirect path or confirmation fails mid-flow, the invoice remains open. Zenoti polls eGHL for status and will either close the invoice or leave it open for re-payment. See Failure modes.

Process a refund

Refunds use the same Merchant ID and Password configured at setup β€” there is no separate refund credential.

  1. Open the guest's invoice.
  2. Select the eGHL transaction.
  3. Select Refund and confirm (full) or enter an amount (partial). [SOURCE GAP β€” PM VERIFY: whether eGHL supports partial or multiple-partial refunds β€” the processor class calls RefundTransaction with a paymentdetails dictionary but does not enforce a partial-amount constraint.]
  4. Zenoti sends the refund request to eGHL and records the returned reference.

Refund β€” dual-system perspective

System What happens
Zenoti Negative payment line on the invoice; Collections report shows a refund row tied to the original transaction.
eGHL Separate refund record against the original transaction ID; appears as a negative entry on the eGHL merchant settlement report.

Process a void

A void cancels an authorised but not yet settled eGHL transaction. Voids use the same Merchant ID and Password.

  1. Open the guest's invoice.
  2. Select the eGHL transaction.
  3. Select Void. Confirm.
  4. After settlement, use a refund instead β€” void is not available.

Edit or reverse a posted payment

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

Failure modes

Failure mode User-visible symptom Resolution
eGHL gateway unreachable HPP fails to load, or redirect returns a gateway error. Check Provider URL + outbound HTTPS. Confirm with eGHL that the gateway is up. Invoice remains open.
Authentication / signature mismatch All transactions fail with an auth error on the HPP. Re-verify Merchant ID and Password with your eGHL representative. Re-enter in Zenoti.
Card declined HPP shows issuer decline. Guest retries or uses another method. Invoice stays open.
Amount out of range eGHL returns an amount-limit error. Per-channel limits are eGHL-side. Split the payment or use a different channel.
Currency mismatch Transaction rejected at gateway. Confirm eGHL has activated the center's currency.
Settlement failure Transaction approved but missing from settlement report. Raise with eGHL support using the original transaction ID; do not re-charge.
Missing billing fields Transaction is never initiated; error about billing email/phone/name. The processor class validates these before sending. Populate email, phone, and name on the guest profile.

Settlement and reconciliation

Settlement timing is eGHL-side and varies by channel and merchant agreement. [SOURCE GAP β€” PM VERIFY: exact T+N per channel.] Working days are determined by the eGHL-side region (Malaysia, Singapore, Indonesia, Philippines, etc.) and exclude local bank holidays.

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

Recommended cadence: daily during the first month after go-live; weekly once stable.

Tips

  • The Provider URL is required and must be the exact URL provided by eGHL. An incorrect URL will cause all transactions to fail.
  • eGHL supports both production and test environments. Verify you are using the production Provider URL before going live.
  • Contact your eGHL account representative if you encounter authentication or connection errors.
  • eGHL requires the guest's email, phone, and billing name β€” populate these on the guest profile before the first payment.
Was this article helpful?
Your feedback helps us improve our documentation.