ZenotiHelp

Processor: Xendit

ZTZenoti Docs Team Updated August 20, 2026 6 min readGuide

Xendit is a V2 payment processor configured at the organization level, primarily serving Southeast Asia (Indonesia, Philippines, Malaysia, Singapore, Thailand, Vietnam). It supports card payments, e-wallets, QR-code payments, and virtual accounts through Xendit's Hosted Payment Page (HPP) iframe.


On this page


Before you begin

Permission: Organization administrator access is required to configure Xendit.

  • You need an active Xendit merchant account and access to the Xendit Dashboard at dashboard.xendit.co.
  • Decide which payment methods (card, e-wallet, QR, virtual account) you want to enable. Each method is subject to Xendit's regional availability β€” not all methods are active in every country.
  • Xendit is online-only. Zenoti does not integrate Xendit for terminal-based in-store payments.

Xendit capabilities in Zenoti

Capability Supported
Online card payments Yes
E-wallets (OVO, GoPay, Dana, ShopeePay, GrabPay, etc.) Yes (subject to regional availability in Xendit)
QR-code payments (QRIS, QR PH, etc.) Yes
Virtual accounts (bank transfer) Yes β€” asynchronous; confirmed by webhook
Stored accounts (tokenization) Yes (cards only)
Manual card add / manual charge Yes
Refund Yes
Void No explicit void API surface β€” pre-settlement reversals are issued through the refund path
Recurring payments Yes (stored card tokens)
HPP iframe Yes
Terminal / card reader No
Global tokenization No
Auto-save card (on payment) Configurable
Automatic card updating Configurable via Zenoti AccountUpdater (processor supports SupportsPaymentAccountUpdate when enabled)

Network requirements

Xendit is cloud-to-cloud. Zenoti calls Xendit's API, and the guest completes the payment in Xendit's HPP iframe in their browser. Virtual account confirmation and QR payment confirmation are asynchronous and delivered by webhook.

Connection Direction Protocol / Port Notes
Zenoti to Xendit API Outbound from Zenoti (cloud) HTTPS / 443 Managed by Zenoti.
Guest browser to Xendit HPP Outbound from the guest device HTTPS / 443 Card details and wallet credentials are entered on Xendit's hosted page.
Webhook notifications from Xendit Inbound to Zenoti HTTPS / 443 Must be configured in the Xendit Dashboard for each event Zenoti consumes.

External-system prerequisites

  1. Complete Xendit's KYC (Know Your Customer)/KYB (Know Your Business) verification in the Xendit Dashboard β€” Xendit cannot issue live keys until verification clears.
  2. In the Xendit Dashboard, open Settings > Developers > API Keys and create a key with the permissions required for card payments, refunds, and webhooks.
  3. In Settings > Webhooks, configure the callback URL provided by Zenoti Support for each payment method you plan to use (virtual account confirmations, e-wallet payments, QR payments, etc.).
  4. Enable the specific payment methods (cards, e-wallets by name, QR providers, virtual bank list) inside the Xendit Dashboard per country. Zenoti can only offer methods that Xendit has enabled on your account.

Configure Xendit

  1. Navigate to Configuration > Payments > Process payments > Payment processor onboarding.

  2. Select Xendit.

  3. Enter your Xendit credentials.

    Field Source / Owner What to enter
    Secret key Xendit Dashboard > Settings > Developers > API Keys (Xendit account owner) Xendit-issued secret key. Stored encrypted in Zenoti.
    Public key Xendit Dashboard > Settings > Developers > API Keys (Xendit account owner) Xendit-issued public key used by the HPP iframe.
    Auto-save card Zenoti configuration (admin) When enabled, Xendit returns a token for card payments and Zenoti saves it to the guest profile.
    Update payment account Zenoti configuration (admin) When enabled, Xendit cards participate in Zenoti's AccountUpdater batch service for card refresh.
  4. Enable the payment methods you want to accept (cards, e-wallets, QR code, virtual accounts). Only methods active on your Xendit account take effect.

  5. Assign the processor to the centers where it should be active.

  6. Select Save.

  7. Select Test to verify the credentials against Xendit.

Security: The secret key has full API access to your Xendit account. Rotate it if compromised and re-enter the new value in Payment processor onboarding > Xendit.


Payment-method toggle interactions

Xendit's payment methods are independently toggleable, but how they combine at checkout matters.

Cards E-wallets QR Virtual accounts Guest checkout experience
On Off Off Off Card-only checkout in HPP. Fastest confirmation.
On On Off Off Guest selects card or e-wallet in the HPP. E-wallet redirects to the provider app.
On On On On Guest picks from cards, e-wallet, QR, or virtual account. Virtual account and some QR flows are asynchronous β€” the invoice remains "pending" until Xendit sends the webhook.
Off Off Off Off Xendit is saved in Zenoti but offers no method. Enable at least one payment method before assigning Xendit to a center.

Mixing synchronous (card, e-wallet) and asynchronous (virtual account, some QR) methods is common. Train staff that a Xendit virtual-account invoice may remain "pending" for minutes or hours β€” that is normal and expected.


Process a payment with Xendit

  1. Open the POS (Point of Sale) or HPP checkout for the invoice.
  2. Select Xendit as the payment method.
  3. Zenoti loads Xendit's HPP iframe. The guest chooses a method and completes it (card details, e-wallet redirect, QR scan, or virtual account reference).
  4. For card and e-wallet, Xendit confirms the payment synchronously and Zenoti closes the invoice.
  5. For virtual account and asynchronous QR flows, Xendit returns a reference to the guest. The invoice remains pending until Xendit sends a confirmation webhook, at which point Zenoti applies the payment and closes the invoice.

Refund and void

Xendit supports refunds on card, e-wallet, and supported virtual-account flows. There is no separate void API in Zenoti β€” pre-settlement reversals flow through the refund path. Some e-wallet and virtual-account methods may not support refund directly; in those cases, contact Xendit for a manual reversal.

Process a refund

  1. Open the invoice in Zenoti.
  2. Select Refund and confirm the amount (full or partial).
  3. Zenoti calls Xendit's refund API against the original payment.
  4. Xendit confirms synchronously where possible and sends a webhook for asynchronous confirmation.

Dual-perspective behaviour

System What it records
Zenoti Refund line on the invoice; negative entry in the payment dashboard with the Xendit payment ID.
Xendit A refund record linked to the original payment. For cards, the refund appears in the next settlement batch. For e-wallets / virtual accounts, the refund may flow back via Xendit to the guest's wallet or bank, subject to the method's rules.

Reconciliation

Layer Source Match key
Zenoti Collections by Invoices filtered to the Xendit payment method Invoice number + Xendit payment ID
Xendit Xendit Dashboard > Transactions Xendit payment ID / external ID (carries Zenoti invoice number)
Bank Xendit Dashboard > Balance > Payouts (per settlement batch) External ID / Zenoti invoice reference

Recommended cadence: reconcile daily. For virtual accounts, allow up to 24 hours for the guest to complete the bank transfer before flagging an invoice as unpaid.


Handle transaction failures

Failure mode Symptom Resolution
Xendit unreachable HPP iframe times out or fails to load. Transient; guest retries. Confirm on Xendit's status page.
Secret key rotated All charges fail with an authentication error. Regenerate the key in Xendit Dashboard and re-enter it in Payment processor onboarding > Xendit.
Card declined Guest-visible decline on the card HPP. Guest tries a different card or payment method. Decline code appears in the Zenoti payment log.
Amount out of range Xendit rejects below-minimum or above-maximum amounts for the selected method. Limits vary by payment method and country. Confirm the method's limits in Xendit Dashboard or use a different method.
Currency mismatch Xendit returns "currency not supported for this method". Xendit accounts are configured per country/currency. Assign the center to a Xendit account that supports its currency, or enable the currency on the account.
Virtual account pending too long Invoice sits in "pending" for hours. Guest may not have completed the bank transfer. Ask the guest to pay or cancel the invoice and collect another way. Xendit's virtual accounts typically expire after a configured window.
Webhook not received Xendit shows paid but Zenoti shows pending. Confirm the webhook URL in Settings > Webhooks. Recent deliveries should show 2xx. Replay the event from Xendit if needed.
E-wallet not available Selected e-wallet is greyed out or missing at checkout. The wallet is not enabled on your Xendit account for that country. Enable it in Xendit Dashboard.

Tips

  • Enable only the payment methods relevant to your market to simplify the HPP experience for guests.
  • Virtual-account payments are confirmed asynchronously β€” Zenoti receives a webhook from Xendit when the bank transfer clears. Train staff to tolerate pending state.
  • Reconcile per currency if you operate across multiple Xendit countries β€” settlements happen per country.

Was this article helpful?
Your feedback helps us improve our documentation.