Installing Xendit Payment For WHMCS

Requirements

• A licensed WHMCS installation and an administrator account permitted to manage payment gateways.
• A valid HTTPS WHMCS System URL and publicly reachable HTTPS callback endpoint.
• PHP compatible with your WHMCS version. The reviewed module declares PHP 8.0+; this alone is not a tested compatibility matrix.
• PHP cURL and JSON support, a working certificate trust store and outbound HTTPS access to api.xendit.co.
• An eligible Xendit account with card payments enabled, appropriate API permissions and test credentials.
• An IDR test invoice with a positive balance. Do not change a live customer’s currency simply to test the module.

Obtain And Back Up

Obtain the package through the delivery channel on the HERZA product page. Back up the WHMCS files and database, and retain the previous gateway version and settings privately. If another module already uses the name xendit, resolve that conflict before replacing anything.

Upload The Files

Extract the supplied package locally and preserve its paths relative to your WHMCS installation root:

modules/gateways/xendit.php
modules/gateways/callback/xendit.php
modules/gateways/xendit/whmcs.json  # include when supplied

Use your hosting account’s normal file ownership and permissions. Keep configuration secrets out of public archives. Do not upload the entire ZIP or backup files into a publicly browsable directory.

Activate The Gateway

1. Open WHMCS administration → Configuration → System Settings → Payment Gateways. Menu wording can differ by WHMCS version.
2. Find Xendit Credit Card in the available gateways and activate it. This is a payment gateway, not an Addon Module or provisioning module.
3. Complete Gateway Configuration using test credentials first.
4. Set the callback endpoint using the Webhook Guide, then complete the test checklist before making the method available to live customers.

Upgrade And Roll Back

During an upgrade, temporarily stop new checkout attempts for this gateway and account for outstanding sessions. Back up both PHP files, upload the matching gateway/callback pair and repeat the test journey. If a regression occurs, restore the previous pair and configuration. Keep the callback reachable for in-flight payments and reconcile outstanding payments before removing or deactivating the gateway. Do not roll back the entire billing database after live payments without a reconciliation plan.