WooCommerce Subscriptions support
WooCommerce Subscriptions compatibility via Cardflo provides merchants with a reliable WooCommerce subscriptions payment gateway. The orchestration layer connects to acquirer partners for tokenised recurring billing, managing merchant-initiated transactions and automated renewal retries directly from the WordPress backend.
- Category
- Plugins
- Capabilities
- 10
- Available on
- All plans
Cardflo integrates directly with WooCommerce Subscriptions, enabling merchants to manage recurring revenue efficiently. This integration provides a robust payment infrastructure for subscription-based businesses, ensuring consistent payment processing and enhanced customer retention.
Merchants can leverage Cardflo's advanced features within their existing WooCommerce setup.
This plugin enhances WooCommerce subscription management by automating renewals across multiple MIDs and utilising decline recovery mechanisms. It measurably improves recurring billing approval rates and strengthens customer retention for your subscription services.
WooCommerce Subscriptions support overview
WooCommerce Subscriptions support within a payments stack operates as an orchestration layer between the WordPress environment and the acquiring infrastructure. This integration facilitates the management of recurring transaction lifecycles, moving beyond simple one-off authorisations to handle complex logic such as scheduled billing cycles, trial periods, and proration.
By utilising a specialised plugin interface, merchants connect to a payment gateway that supports asynchronous payment notifications and vaulted credentials. The mechanic relies on merchant-initiated transactions (MIT) where the initial cardholder-initiated transaction (CIT) establishes the mandate for subsequent billing.
This structure allows the system to manage the technical requirements of Strong Customer Authentication (SCA) while minimising friction.
It sits between the WooCommerce database and the payment scheme networks, ensuring that payment tokens are securely stored and that individual subscription updates are communicated to the acquirer with the correct transaction flagging to maintain compliance with PSD2 regulations.
How wooCommerce Subscriptions support works
Establishment of payment mandate
When a customer completes a checkout, the system performs an initial authorisation with 3D Secure verification. This creates a secure token and a payment mandate documented by the issuer. This initial cardholder-initiated transaction sets the required flags for all future automated billing cycles to be processed as merchant-initiated.
Secure vaulting of tokens
Sensitive primary account numbers are not stored on the WooCommerce server. Instead, they are transmitted to a PCI DSS compliant vault. The gateway returns a unique token to the merchant platform, which is utilised for subsequent recurring requests, reducing the scope of data security requirements for the business.
Automated billing cycles
The plugin monitors the subscription schedule defined in WordPress. At the required interval, it triggers a request to the payment processor using the stored token. The request includes specific recurring indicators and the original transaction identifier to ensure the issuer recognises the payment as part of an established agreement.
Management of declined payments
If a recurring charge is declined, the system categorises the failure as either a soft or hard decline. Soft declines, such as temporary insufficient funds, trigger secondary retry logic or dunning processes. Hard declines, like a cancelled card, prompt the system to notify the customer to update payment details.
Why wooCommerce Subscriptions support matters
Recovering failed WooCommerce renewals
Involuntary churn occurs when active subscriptions fail due to technical payment issues or expired credentials. Integrating sophisticated subscription support allows for the use of tools like account updaters and smart retry logic. These mechanisms ensure that revenue remains consistent without the need for manual intervention from the customer, which typically leads to higher retention over the lifecycle of the subscriber.
Compliance and Flagging Accuracy
Recurring payments are subject to specific regulatory frameworks under PSD2 and scheme rules. Failure to correctly flag an MIT can result in high refusal rates from issuers. A robust integration ensures that each transaction carries the correct metadata, such as the original transaction ID and the appropriate Merchant Category Code, to satisfy issuer risk models and authentication requirements.
WooCommerce Subscriptions support use cases
WooCommerce subscription box renewals
Subscription box operators need WooCommerce Subscriptions renewals approved before allocating chilled or date-sensitive stock to each fulfilment run. Cardflo supports tokenised recurring payments, routes renewal attempts through its acquirer partner network and returns payment status so failed orders can be held before warehouse picking begins.
WooCommerce SaaS billing
SaaS operators using WooCommerce Subscriptions must align monthly or annual renewal outcomes with software licence activation, grace periods and account suspension. Cardflo provides recurring payment routing and webhook events that let developers update access after successful payments, declines, retries or customer cancellations.
Metered plan renewal adjustments
WooCommerce SaaS merchants may add usage charges or updated seat quantities to the next scheduled renewal, creating variable amounts against an existing token. Cardflo routes the tokenised payment to an appropriate acquirer partner and returns authorisation results for WooCommerce Subscriptions to update the order and billing state.
WooCommerce Subscriptions support by the numbers
Typical gains observed in the industry when transitioning from manual to automated recurring flagging and utilising smart retry logic.
Industry research indicates this range of recovery is possible when account updaters and automated dunning are effectively implemented.
The standard duration for processing recurring API calls between the plugin and the payment gateway in stable environments.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with WooCommerce Subscriptions support
- Synchronisation of merchant-initiated transaction flags to satisfy issuer requirements and reduce authorisation refusals.
- Storage of payment credentials in a PCI-compliant vault to minimise local data security risks.
- Automated dunning sequences to manage and recover revenue from failed recurring transaction attempts.
- Support for multiple currencies through the WooCommerce interface to facilitate global subscription expansion.
- Real-time status updates via webhooks to keep subscription records accurate across the entire platform.
- Integration with network tokenisation services to automatically update expired or replaced credit card details.
- Granular control over retry schedules for soft declines based on specific issuer refusal codes.
- Execution of prorated billing for customers who change their subscription tier mid-cycle.
- Comprehensive reporting on customer lifetime value and subscription renewal success across all payment methods.
- Verification of cardholder identity via 3DS on the initial transaction to establish payment mandates.
A short scoping call, then a written plan for your MIDs.
Questions about WooCommerce Subscriptions support
How are WooCommerce subscription cancellation events synchronised with recurring billing?
WooCommerce Subscriptions can send cancellation events through integration webhooks so the gateway orchestration layer stops subsequent recurring payment requests. The subscription reference and stored payment credential remain linked to the WooCommerce record, allowing operators to reconcile the cancellation against earlier renewals.
Webhook authentication, idempotency controls and event logging help prevent duplicate processing or a cancelled subscription remaining active after a delayed notification.
What happens when a subscriber's credit card expires?
The system can utilise account updater services provided by card schemes to manage card expiry. When an issuer replaces a card, the updated details are retrieved via the acquirer and the token in the vault is refreshed.
For issuers not supporting this, the dunning logic within the plugin provides automated email notifications to the customer, prompting them to provide a new payment method before the subscription is suspended or cancelled by the system.
Can I offer trial periods with these subscription settings?
Yes, the logic supports trial periods where a zero-amount or nominal-fee authorisation is performed initially to validate the card and establish the mandate. Once the trial period expires, the system automatically transitions to the full billing amount.
The integration ensures that the shift from trial to full payment is correctly communicated to the issuer to avoid fraud triggers or unexpected declines during the first full billing event.
Are multiple payment methods supported for recurring billing?
While credit and debit cards are the most common, the infrastructure supports various alternative payment methods (APMs) that allow for recurring mandates, such as SEPA Direct Debit. The availability of these methods depends on the acquirer's capabilities and the specific regional regulations.
The integration organises these diversely within the checkout, ensuring the customer can select their preferred method while the system maintains the necessary mandate documentation.
Is it possible to pause a subscription instead of cancelling it?
The technical framework allows for the suspension of the billing trigger without deleting the payment token or the mandate record. When a merchant or customer pauses a subscription, the scheduled billing requests are halted.
Upon reactivation, the system resumes the cycle using the existing token. This maintains the continuity of the original agreement and avoids the need for a new 3DS challenge unless the billing amount or terms have significantly changed.
How are declines categorised and managed by the plugin?
The gateway returns specific decline codes for every failed transaction. The system categorises these into soft declines, such as 'insufficient funds', and hard declines, such as 'stolen card'.
For soft declines, merchants can define an automated retry schedule, such as attempting the charge again after 24 or 72 hours. Hard declines immediately stop the retry attempts to avoid scheme fees or penalties from the acquirer for excessive failed authorisations.
Related guides.
See how Cardflo compares.
From the blog
The subscription model provides predictable revenue through recurring fees for SaaS and streaming services. While it fosters long-term customer loyalty, businesses must manage higher acquisition costs and potential churn. This approach offers stability for companies providing ongoing value through continuous access to products. It is designed to generate a steady income stream and build relationships.
Read articleSubscription payments are a specific subset of recurring billing where customers pay at the start of each cycle. These automated payments occur at weekly, monthly, or annual intervals until the service is terminated. This model helps businesses reduce churn and secure predictable revenue while helping customers budget effectively. It is an ideal system for strengthening long term loyalty.
Read articleA recurring payment is an automated billing system where a customer authorises a business to charge their card or bank account at regular intervals. This model is common for gym memberships, insurance premiums, and streaming services. It provides convenience for consumers while ensuring consistent revenue for service providers. Payments occur at fixed or variable amounts without manual customer input.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.