Choosing Between Drupal-Native and Gateway-Managed Recurring Payments

Subscription billing requirements have become more varied as payment providers expand their recurring payment capabilities. Writing for Centarro, Ryan Szrama argues that the decision between Drupal-native recurring billing and gateway-managed subscriptions is now more nuanced than when the Commerce Recurring module was first developed.

The article outlines where each model fits. Gateway-managed subscriptions are presented as a strong option for straightforward recurring charges, hosted checkout, plan management, payment-method updates, prorated plan changes, and built-in dunning workflows. Commerce Recurring, by contrast, is positioned for organisations that need ownership of subscription data, full cart and checkout integration, abandoned cart visibility, mixed carts with subscriptions and one-time purchases, or non-standard billing workflows.

Ryan also discusses hybrid architectures that combine Drupal-managed subscription entities with gateway-managed billing cycles. In these implementations, Drupal remains the system of record while services such as Stripe handle payment execution and lifecycle events through webhooks. The article also notes current gaps in Commerce Recurring, including customer-facing interfaces, plan-change workflows, dunning capabilities, and merchant-facing language, and outlines planned improvements to achieve tighter integration with the Drupal Commerce ecosystem.