Description
Note: Version 3.0.0 includes breaking changes. When upgrading an existing installation, please make note of your CCBill account values in the WooCommerce -> Settings -> Payments -> CCBill section of the WordPress admin, as these values may need to be reentered after upgrading. Version 3.0.0 adds support for recurring payments when used with the official WooCommerce Subscriptions plugin.
Note: Version 3.0.1 (released January 12, 2026) contains a fix for a bug that affected version 3.0.0 when WooSubscriptions was not installed
About the Plugin
The CCBill payment gateway plugin for WooCommerce allows you to easily configure and accept CCBill payments on your WooCommerce-enabled WordPress Website.
There are dozens of providers who offer basic payment processing online, but CCBill is the payment services platform built to care for your buyers, automate your business and help you instantly grow into new markets.
Accept credit cards, debit cards, gift cards, online checks and bank transfers using CCBill – and protect your business with our leading fraud protection and 24/7 billing support for your buyers.
Offering a complete package at easy rates, CCBill’s service includes a payment gateway, merchant account, smart payment forms, mobile tools, multiple currencies and languages, PCI Level 1 compliance, direct settlements and a menu of tools to automate and expand your online business commerce.
With billions of consumers linked to a broad, flexible e-commerce platform, plus dozens of integrated software partners, CCBill represents reliability and integrity to consumers and merchants alike.
Click here to get started with taking payments online.
This plugin requires WooCommerce. WooCommerce Subscriptions is required to create and manage subscription products. This plugin is not owned by, developed by, or otherwise affiliated with WooCommerce.
External Services
This plugin connects to api.ccbill.com to collect payment information during checkout in order to process payment. When a customer places an order in your WooCommerce store and selects CCBill as the payment method, a request is made to CCBill to generate a secure billing token (Advanced Integration) or the customer is then directed to a form hosted by CCBill where payment information is securely entered and processed (FlexForms integration). The customer is then directed back to your WooCommerce website where the result of the payment (success or failure) is reflected in the order. All payment information is processed by CCBill and no payment information is stored by or transmitted through your WooCommerce website for a secure checkout experience. This service is provided by “CCBill, LLC”: terms of use, Privacy Policy.
Installation
Installation involves the following steps:
* Installing the CCBill payment module for WooCommerce
* Configuring your CCBill account for use with WooCommerce
* Configuring the module with your CCBill account information
Installation Options
The CCBill payment module for WooCommerce can be installed either by searching for the hosted WordPress plugin, or by uploading the plugin downloaded from the CCBill website.
Installing via WordPress Plugin Directory
From the WordPress administration menu, navigate to “Plugins.”
Type “CCBill” into the text field and click “Search Plugins.”
Locate the official CCBill plugin for WooCommerce from the search
results and click the “Install Now” link next to the module title.
Installing via File Upload
From the WordPress administration menu, navigate to “Plugins”
and selected “Upload” from the top menu. Click the “Choose File”
button and select the .zip file downloaded from the CCBill website
or WordPress plugin directory.
Once the file is selected, click “Install Now” to complete
the installation process.
Configuring your CCBill Account
Before using the plugin, it’s necessary to configure a few things in your CCBill account.
Please ensure the CCBill settings are correct, or the payment module will not work.
Enabling Dynamic Pricing
Please work with your CCBill support representative to activate “Dynamic Pricing” for your account.
You can verify that dynamic pricing is active by selecting “Feature Summary” under the
“Account Info” tab of your CCBill admin menu. Dynamic pricing status appears at the
bottom of the “Billing Tools” section.
Creating a Salt / Encryption Key
A “salt” is a string of random data used to make your encryption more secure.
You must contact CCBill Support to generate your salt. Once set, it will be
visible under the “Advanced” section of the “Sub Account Admin” menu. It will
appear in the “Encryption Key” field of the “Upgrade Security Setup Information”
section.
Disabling User Management
Since this account will be used for dynamic pricing transactions rather than
managing user subscription, user management must be disabled.
In your CCBill admin interface, navigate to “Sub Account Admin” and select
“User Management” from the left menu.
Select “Turn off User Management” in the top section.
Under “Username Settings,” select “Do Not Collect Usernames and Passwords.”
Important
CCBill provides two types of integration methods. Advanced Integration is our newest (and recommended) system, but FlexForms Integration is still supported.
Please see the official CCBill plugin page for detailed instructions for both integration methods.
Subscription support using either integration method will require some account configuration from CCBill support.
Screenshots
Changelog
1.0
- Initial Release
1.0.1
- Resolved repeated postback when communicating with CCBill
1.1.0
- Added support for CCBill FlexForms
1.1.1
- Fixed bug with order amount over 1,000
1.2.0
- Added support for WebHooks
1.3.0
- Added check for zero balance
1.4.0
- Classic forms deprecated
1.4.1
- Resolved incorrect 500 response code when communicating with CCBill
1.4.6
- Updated name, tested version, and documentation for compliance with WordPress Marketplace guidelines
2.0.0
- Added support for blocks checkout. NOTE: This version contains breaking changes. Upgrading to this version from a 1.x version will require you to reenter your CCBill account settings in WooCommerce -> Settings -> Payments -> CCBill
3.0.0
- Added support for recurring payments with subscriptions using the official WooCommerce Subscriptions plugin. NOTE: This version contains breaking changes. Upgrading to this version from a 1.x or 2.x version may require you to reenter your CCBill account settings in WooCommerce -> Settings -> Payments -> CCBill.
- Added support for Advanced Integration for a more seamless checkout experience.
- Currency is now set in WooCommerce rather than a manual settings in the CCBill plugin configuration.
- Added the ability to mark virtual orders as complete upon successful payment.
3.0.1
- Resolved payment error when Woo Subscriptions is not present
3.0.2
- Resolved an issue with logging
3.0.3
- Updates for security and reliability
3.0.4
- Resolved an issue with subscription renewals when using the advanced integration
3.0.5
- Added suspension support to resolve bug with subscription renewals
3.0.5
- Added suspension support to resolve bug with subscription renewals
3.0.6
- Suspend & resume for FlexForms subscriptions: putting a subscription On hold now cancels billing at CCBill; reactivating charges the customer for the current period and creates a new, linked CCBill subscription. Failed reactivations revert to On hold and trigger an admin notice.
- Free trial ($0 initial price) support: zero-total subscription checkouts now work in both Advanced and FlexForms modes (FlexForms requires CCBill to enable $0 initial pricing on the account). Zero-total carts without a recurring component are declined gracefully instead of crashing.
- Automatic recovery of timed-out charges: when a charge request to CCBill times out, the plugin now verifies with CCBill whether the charge actually completed: confirmed charges complete the order without charging again; unverifiable attempts block further charging on that order until resolved, preventing duplicate charges from customer retries or renewal re-runs.
- Payment notifications (IPNs) that are received but rejected (ex: security digest mismatch from an incorrect Salt setting or an amount mismatch) now leave a diagnostic note on the order explaining why it was not marked as paid and how to resolve it.
- Checkout now shows a clear “do not retry” message when a payment outcome could not be confirmed, instead of a generic “Payment declined” message.
- Subscriptions using FlexForms can now be suspended and reactivated from both the admin and the customer account page (added missing subscription_suspension/subscription_reactivation support flags; also fixes a “Unable to change subscription status” error logged on every FlexForms renewal).
- CCBill-side cancellation failures are now verified via DataLink (when active) before being reported, avoiding false failures when the cancellation actually succeeded.
- Fixed subscription billing periods being wrong for terms of one month or longer (e.g. annual terms sent as 0 days) due to incorrect php date-interval math.
- Fixed a fatal error (“critical error on this website”) when checking out with a $0 cart, and on several other payment-failure paths.
3.1.0
- Resolved an issue where subscriptions may not renew correctly in advanced mode
- Added IPN Security Token option for improved security with FlexForms
- Improved redirect handling after purchase for FlexForms
- Updates for security and reliability
3.1.1
- Resolved an issue where subscriptions may not renew correctly in advanced mode
3.1.2
- Security: payment notifications are now bound to the order they claim to pay for. The order must have been placed through CCBill and still be awaiting payment, the posted amount must match the order total even when the security digest verifies, and notifications for orders placed from this version on must carry the order key sent to CCBill at checkout. Repeat notifications for an already-paid order are acknowledged without changing it. Credit: Pedro Pinho for the original digest report (fixed in 3.1.0), and the technical review submitted by Katesofie.dk.
- Security: the IPN security token and customer personal data are no longer written to the debug log in clear text.
- Security: the automatic refund issued when CCBill bills a suspended subscription now targets the subscription stored in WooCommerce rather than a value from the notification, and a recovered reactivation is confirmed with CCBill via DataLink before it is adopted.
- Fixed: renewals billed in a currency other than the store’s (ex: a customer paying in EUR on a USD store) were rejected; they are now recorded in the store currency using CCBill’s accounting amount, with the billed amount noted on the order.
- Fixed: subscription sales delivered through the legacy Approval Post URL were flagged as a digest mismatch because the recurring price and period were left out of the check. If both the legacy Approval Post URL and the webhook URL are configured at CCBill, the webhook alone is sufficient.
- Fixed: a notification naming an order that does not exist, or carrying a non-numeric amount, caused a PHP error instead of a clean rejection.
- Fixed: the notification handler always answered HTTP 200, even when a handler had set another status. A renewal that could not be verified, or a cancellation CCBill’s records did not yet confirm, was therefore acknowledged and never redelivered.
- Changed: notifications rejected for a reason the merchant can correct (missing security token, Salt/digest mismatch, missing digest, amount mismatch, or a renewal arriving without DataLink credentials) now answer with an HTTP 4xx error. CCBill redelivers these, so the sale is recorded once the setting is fixed instead of being dropped. Rejections that could never succeed (unknown or already-paid order, wrong gateway, bad order key, unsupported event) are still acknowledged with HTTP 200.
- Note for merchants: an incorrect Salt no longer shows up as a rejected notification. CCBill checks the dynamic-pricing digest when its payment form loads, so a wrong Salt blocks the customer at the form with a “requested URL was rejected” error. A “digest mismatch” note on an order therefore points to a legacy Approval Post URL still configured at CCBill (remove it; the webhook URL is sufficient) or to a forged notification.

