All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Commerce Recurring vs. Gateway-Managed Subscriptions: Centarro's Guide for Drupal Billing Decisions

By

Staff Reporter

6h ago· 1 min readenInsight

Summary

Ryan Szrama's Centarro article examines the evolving landscape of subscription billing in Drupal, comparing Commerce Recurring (Drupal-native) vs. gateway-managed subscriptions (e.g., Stripe). Gateway-managed subscriptions work best for straightforward recurring charges, hosted checkout, plan management, and built-in dunning. Commerce Recurring offers more control over subscription data, carts, and custom workflows. The article also explores hybrid models where Drupal maintains subscription records while the payment provider handles billing execution.

Key quotes

· 3 pulled
The decision between Drupal-native recurring billing and gateway-managed subscriptions is now more nuanced than when the Commerce Recurring module was first developed.
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.
The article also outlines hybrid models that keep Drupal as the subscription record while offloading billing execution to the payment provider.
Snippet from the RSS feed
Recurring billing in Drupal no longer has a single obvious implementation path. Ryan Szrama’s Centarro analysis explains when Commerce Recurring gives organisations useful control over subscription data, carts, and custom workflows, and when gateway-manag

You might also wanna read