How to Integrate Xendit with systeme.io
Introduction
Xendit powers card, e-wallet, and local payment methods across Indonesia, the Philippines, and wider Southeast Asia. On systeme.io, Xendit is a native payment gateway: you connect production API keys and the webhook verification token, then enable the gateway on each sales funnel—similar in spirit to Razorpay or Flutterwave.
This guide follows How to integrate Xendit with systeme.io.
What You Need
Step 1: Generate API Keys in Xendit
In the Xendit Dashboard, open Settings → Developers → API Keys.
Public API key
Copy your Public API key. It starts with xnd_public.
Secret API key
- Click Generate secret key under Secret keys
- Name the key (e.g. systeme.io)
- Select permissions as required by Xendit for checkout—at minimum allow Money-in (write) and read access for balance/transactions as shown in the generator
- Confirm with your password and copy the secret immediately (shown once)
Use live credentials when your Xendit account is in Live mode; test keys only for sandbox checkouts.
Step 2: Get the Webhook Verification Token
Still in Xendit: Settings → Developers → Webhooks.
- Enable auto-retry for failed webhooks so missed events are retried
- Click View Webhook Verification Token
- Enter your password
- Copy the token—you will paste this as webhook secret in systeme.io
This token lets systeme.io verify that payment notifications genuinely come from Xendit.
Step 3: Connect Xendit in systeme.io
- Profile picture → Settings
- Payment gateways
- Connect on Xendit
- In the popup, enter:
- Organization name (your Xendit organization / business name as shown in the dashboard)
- Webhook secret (verification token from Step 2)
- Public and Secret access tokens (API keys from Step 1)
- Save
If the connect screen also shows a webhook URL for Xendit, copy it and add it under Xendit Developers → Webhooks for the payment/invoice events your integration uses (same pattern as other gateways). Follow any URL hints shown in the systeme.io popup after save.
Step 4: Finalize Webhooks in Xendit
- Keep auto-retry enabled
- Ensure live-mode webhook settings match live API keys
- After a test payment, confirm the sale appears under Sales → Transactions
If money settles in Xendit but Transactions stay empty, webhook delivery is the first place to check—many sellers fix this by aligning verification token + outbound webhook URL with systeme.io’s connect instructions.
Step 5: Enable Xendit on the Funnel
- Sites → Sales funnels → your funnel
- Funnel settings
- Check Xendit
- Save
Pair with order form and offer pricing in local currency.
Troubleshooting
Checkout fails immediately
Wrong secret/public pair, test keys in live mode, or incomplete Xendit KYC.
Paid in Xendit, no sale in systeme.io
Webhook secret mismatch; webhooks not configured; auto-retry off and one failed delivery.
Do I need Pabbly/Zapier?
Native integration should handle funnel checkout; third-party bridges are optional workarounds, not required by systeme.io’s documented flow.
Contact systeme.io support with organization name, funnel URL, and Xendit payment ID (never paste secret keys in tickets).
Frequently Asked Questions
Which countries use Xendit on systeme.io?
Primarily merchants where Xendit operates—commonly Indonesia and the Philippines; confirm availability for your entity in Xendit and systeme.io gateway list.
Can I use Xendit with subscriptions?
Depends on offer type and Xendit products enabled; test recurring offers after webhooks work for one-time sales.
Last updated: July 11, 2026 · Based on How to integrate Xendit with systeme.io