WooCommerce Subscription Payment Gateways: Check the Full Lifecycle

Write the recurring offer in plain English

Describe the billing interval, any signup fee or trial, and what the customer receives each cycle. Decide how cancellation, pauses and changes should work. A monthly product box and a service subscription can share a billing schedule while needing very different fulfilment rules.

Distinguish new subscriptions from a migration of existing customers. New signup tests do not tell you whether saved payment references can move between systems. Flag existing billing agreements at the start so gateway and migration work can be scoped correctly.

Check the exact gateway extension

WooCommerce Subscriptions distinguishes manual and automatic renewals, and gateway integrations support different lifecycle features. Check the actual extension in your store, rather than assuming every plugin using the same payment provider behaves identically.

Build a short capability list: automatic renewal, customer payment-method change, date or amount changes, trial/signup handling and the checkout experience you intend to use. Confirm each required action against the extension’s current documentation. A gateway that handles a one-off order can still be the wrong choice for your subscription model.

Check account changes and failed renewals

Open the customer account journey and try the actions you plan to offer. Can the customer update their payment method? Does the new method apply to future renewals? Are cancellation and pause options clear, and does the next billing date match the business policy?

Keep the customer-facing wording aligned with what the integration supports. If a change needs staff intervention, say so and give staff a procedure. Offering an account control that does not update the underlying billing arrangement creates avoidable support work.

Ask what happens after a declined renewal: whether another attempt is made, how the customer is notified and when fulfilment pauses. These are business decisions as well as gateway settings. Staff need to distinguish an unpaid renewal order from the status of the continuing subscription.

For a reported failure, compare the provider event, renewal order and subscription record privately. Do not trigger repeated real charges to discover what happens. Use the integration’s supported test workflow, and keep transaction references out of public tickets.

Use a staging setup that cannot bill real customers

Before testing, isolate the copied store from live billing, customer email and fulfilment. Use test gateway credentials and subscriptions created for the test. A copied production subscription is not a harmless demo record.

Rehearse signup, the required account changes, a renewal and a supported failure case. Check the resulting order, subscription state and notification. Record any sandbox limitation so the team knows which provider-specific confirmation or controlled launch check is still outstanding.

Choose the gateway on the required behaviour

Compare gateways against the same subscription workflow, not only transaction fees or familiar branding. Include country/currency availability, operational support and who will investigate a renewal mismatch. Leave unsupported features visible in the decision.

Keep the accepted cases for extension updates. If existing subscriptions are being moved, treat payment references and future renewals as a separate migration checkpoint. The setup is ready when both the customer and store team can complete the recurring workflow you intend to run.

Useful documentation

• WooCommerce Subscriptions gateway capability matrix (opens in a new tab) ↗