Alovio Payments · 8 pages
Xendit for Booknetic: setup
Connect Xendit to Booknetic through Alovio Payments: countries and currencies, the HTTPS requirement, the secret key and its permission, webhook topics and the verification token.
On this page
Xendit takes payments on its own hosted payment page, where the customer picks a method — QR, e-wallets, bank transfer or cards, whichever Xendit has switched on for your account. Alovio Payments uses Xendit’s Payment Sessions to create that page and marks the booking paid once Xendit confirms the payment.
Before you start
- Your site must run on HTTPS. Xendit only sends customers back to HTTPS addresses, so on a plain
http://site a Xendit payment cannot be started — the plugin says so instead. - Your Xendit account. Xendit decides who can open an account. Its documentation says accounts are for registered businesses, that going live needs Xendit’s business verification (create an account), and that in Indonesia, the Philippines and Malaysia individuals and sole proprietors are only allowed as sub-accounts — in Thailand, individuals (Indonesia, Philippines, Malaysia, Thailand). Check with Xendit before you plan around it.
Countries and currencies
| Booknetic currency | Xendit country |
|---|---|
| IDR | Indonesia |
| PHP | Philippines |
| MYR | Malaysia |
| THB | Thailand |
| VND | Vietnam |
| SGD | Singapore |
Your Booknetic currency decides the country of each payment. In any other currency, Xendit is not offered at checkout.
IDR and VND are whole numbers only. Xendit takes these two currencies without cents, so a total with cents cannot be sent — it is refused, never rounded, because a rounded amount would not match the booking. Keep IDR and VND prices whole.
Where the keys go
- A regular Booknetic site: Alovio Payments → Gateways → Xendit, under Set up Xendit → Enter your API key. The Xendit tab in Booknetic → Settings → Payment methods edits the same values.
- Booknetic SaaS: every business enters its own keys in its own Booknetic → Settings → Payment methods. See Booknetic SaaS.
| Field | What goes in it |
|---|---|
| Mode | Test (no real money moves) or Live. |
| Test secret key | Starts with xnd_development_. From the Xendit dashboard → Settings → API keys; give it Write permission for Money-in. |
| Live secret key | Starts with xnd_production_. |
| Test webhook verification token | From the Xendit dashboard → Settings → Webhooks, in Test mode. |
| Live webhook verification token | The same page in Live mode — each mode has its own token. |
A public key (xnd_public_…) is refused: enter the secret key. A key that belongs to the other mode
is refused too.
Save & check saves the keys and asks Xendit whether they work. If Xendit answers that the key may not read payments, give it Write permission for Money-in in the Xendit dashboard, or check Xendit’s IP allowlist if you use one.
The webhook
The webhook lets Xendit tell your site when a payment completes or a refund finishes. It is optional but recommended: without it, payments are still confirmed when the customer comes back and by the background checks.
- Copy the Webhook URL from the Xendit page in the hub (or from the Xendit tab in Booknetic’s payment
settings). On a regular site it looks like
https://your-site.example/wp-json/alovio-payments/v1/notify/xendit. On Booknetic SaaS each business has its own URL, shown in its own payment settings. - In the Xendit dashboard open Settings → Webhooks, in Test mode first (Live later).
- Paste the URL into Payment Session – Completed, Payment Session – Expired and Unified Refunds (Succeeded and Failed).
- Copy the Webhook Verification Token from the same page into the form. It is how your site knows a webhook really came from Xendit; without it, Xendit’s webhooks are ignored.
Xendit checks webhook addresses itself and only accepts a public HTTPS URL (Xendit help).
Xendit’s webhook carries a token rather than a signature, so a webhook is only ever a prompt: the payment is then read back from Xendit’s API before anything changes.
Good to know
- A payment can arrive after the page expired. Xendit can still take a payment after its page has expired or been closed. The payment’s own status always wins over the page’s, so a late payment is still recorded as paid — and if what it paid for is gone, it shows under Needs a look.
- Refunds can be full or partial. A refund needs Xendit’s payment id; if Xendit has not reported it yet, the refund asks you to press Check now and try again. Xendit does not refund every payment method — its payment methods page lists which ones can be refunded. When Xendit refuses a refund, the refund is marked failed, Xendit’s answer is shown, and nothing changes on the booking.
- Refunds finish even without a refund webhook. The background checks ask Xendit about every open refund. See Transactions & refunds.
$29 · Product page
A salon on Booknetic SaaS taking rand — book with a bank transfer, then mark it received as the salon. It resets every hour.