Commerce CCAvenue Payment Gateway

Commerce CCAvenue integrates the CCAvenue payment processing service into Drupal Commerce. It was the first project I created on drupal.org, in November 2011, and it is the only one still receiving releases: the current stable version declares compatibility with Drupal 10.1 and Drupal 11, and shipped in October 2025.

The problem it addressed was regional and completely practical. Drupal Commerce in 2011 assumed a Western payments world — PayPal, Authorize.Net, a card gateway with a familiar API. An Indian merchant needed CCAvenue, which meant credit cards, ATM-cum-debit cards, direct bank debits, cash cards and mobile payments through a single processor with its own redirect flow, its own checksum scheme and its own conventions about what a completed transaction looks like. Without a module, every one of those merchants was writing the same integration privately.

Fifteen years of maintenance is not my doing alone; the project has several maintainers now and I am one name among them. But it is the clearest illustration I have of what open source actually returns. A payment adapter written for one client's problem in 2011 became infrastructure that outlived the version of Drupal it was written for, three major core releases, and my own move out of the ecosystem entirely.

It also set a pattern I have used on every commerce platform since: put the gateway behind an internal abstraction so the order pipeline speaks one language, and let each processor's peculiarities live in an adapter that can be replaced without touching the checkout.