• Thursday, August 20, 2026
Beta Release

Paddle Billing for WHMCS v3.32 Beta Released

We are pleased to announce the release of Paddle Billing for WHMCS v3.32 Beta. This beta update focuses on safer subscription cancellation handling, improved WHMCS service-to-subscription linking, refund transaction logging improvements, and better client-area display compatibility.

This update is especially important for installations where clients may have multiple WHMCS services connected to separate Paddle subscriptions, including cases where a customer owns two of the same product.

Version 3.32 Beta Subscription Safety Update Backup Recommended
↔

What’s New in v3.32 Beta

More accurate linking between WHMCS services and Paddle subscriptions.
Exact Service References Paddle subscription checkout transactions now include WHMCS service reference metadata.
Safer Cancellation Cancellation requests now validate the selected service before processing.
Improved Subscription Linking Saved subscription records now include stronger local service-link metadata.
Client Ownership Checks Client-area cancellation requests now include stronger ownership validation.
Important: This update helps prevent incorrect subscription cancellation in situations where one client owns multiple active services or multiple subscriptions for the same WHMCS product.
✓

Subscription Cancellation Safety Improvements

The cancellation flow now verifies the selected service before contacting Paddle.
  • Product/Service cancel links now carry exact service context.
  • Cancel confirmation now preserves the subscription ID, service ID, and service type.
  • The module now validates the local subscription mapping before cancellation.
  • The module now checks available metadata and invoice data before processing cancellation.
  • WHMCS cancellation requests now validate the related subscription before Paddle cancellation is processed.
  • If a mismatch is detected, cancellation is stopped safely instead of processing the wrong subscription.
⟳

Callback and Subscription Linking Improvements

Subscription linking is now more precise during Paddle callback handling.
  • Improved subscription.created callback handling.
  • Paddle transaction custom data is now used first when linking subscriptions to WHMCS services.
  • Invoice item mapping is used as a fallback only when required.
  • Improved validation to confirm the linked WHMCS service exists on the original invoice.
  • Improved WHMCS Hosting subscription ID synchronization after Paddle subscription linking.
$

Refund Transaction Logging Improvements

Paddle refunds are now recorded more reliably inside WHMCS.
  • Improved refund processing so Paddle API refunds are also recorded correctly in WHMCS.
  • Added unique WHMCS refund transaction IDs using a refund suffix.
  • Added automatic fallback suffixes such as -R2, -R3, and higher when required.
  • Improved handling of WHMCS duplicate transaction ID restrictions for refunds.
◐

Light and Dark Mode Compatibility

Client-facing invoice and service sections now follow the selected module theme.
  • Improved invoice Active Subscription section visibility on light backgrounds.
  • Added light/dark mode compatibility for client-facing invoice sections.
  • Added light/dark mode compatibility for client Product/Service subscription sections.
  • Improved Card on File, Change Card popup, messages, and buttons for both light and dark display modes.
↑

How to Update from WHMCS Admin

The module includes a built-in updater, so you can upload the update package from WHMCS.
  1. Log in to your WHMCS Admin Area.
  2. Go to Addons > Paddle Billing.
  3. Open the Auto Update Addon & Gateway section.
  4. Upload the v3.32 Beta update ZIP.
  5. Click the update/install button and wait for the result screen.
  6. Confirm that the update result shows a successful installation and note the backup ZIP path shown on screen.
  7. Reload the Paddle Billing addon page after the update completes.
Before updating: Because this is a beta release, we recommend taking a full WHMCS file and database backup before installing it on a production system.
↩

Rollback Instructions

The updater creates a timestamped backup ZIP before replacing module files.

Rollback is straightforward as a file restore, but it is currently manual. The updater automatically creates a backup ZIP before installing the update and shows the backup path after the update completes.

  1. Find the backup ZIP path shown on the update result screen.
  2. Backups are stored under modules/addons/paddleBilling/storage/updates/backups/.
  3. Download or open the backup ZIP created before the v3.32 Beta update.
  4. Extract the backup ZIP into your WHMCS root directory, overwriting the Paddle Billing module files.
  5. Clear any WHMCS/template cache if needed.
  6. Reload the WHMCS Admin Area and verify the previous module version is active again.
Rollback note: The updater can restore files automatically if an update installation fails. For a manual rollback after a successful update, restore the generated backup ZIP over the WHMCS installation. Since this update does not require a new database schema, file rollback should be simple, but a database backup is still recommended before installing any beta release.

Recommended for Beta Testing

We recommend testing Paddle Billing for WHMCS v3.32 Beta first on a staging or development WHMCS installation, especially if your clients may have multiple active services or multiple Paddle subscriptions under the same account.

This update improves cancellation accuracy, subscription linking reliability, refund transaction logging, and client-area display compatibility.

Regards,
iBeeHost

Back