インドでのGitHub請求が自動継続支払いに対応GitHub billing in India now supports automatic recurring payments

GitHub has begun supporting automatic recurring payments for customers in India, allowing eligible saved credit cards to be charged automatically for both monthly and annual bills. The change, detailed in GitHub's changelog, addresses a long-standing friction point for Indian developers and organizations who have often needed to manually renew their subscriptions each billing cycle.

Under the update, customers in India can now designate an eligible saved credit card to cover their recurring GitHub charges. The system relies on a payment mandate, a mechanism sometimes referred to in India as an e-mandate, which authorizes GitHub to collect payment automatically when each invoice comes due. This applies to both monthly and annual billing cycles, meaning subscriptions should renew without the account holder needing to re-enter card details or manually approve every charge.

A payment mandate is essentially a standing authorization that a customer grants to a merchant, permitting scheduled or recurring charges against a specified payment instrument. Rather than treating every transaction as a one-off that requires fresh approval, the mandate establishes the terms up front — such as the payment method and the recurring nature of the charge — so future collections can proceed automatically within agreed limits. This is the same category of tooling that underpins recurring billing for many subscription services.

The context behind this change lies in India's regulatory framework for recurring digital payments. The Reserve Bank of India has, in recent years, introduced rules governing automatic recurring card transactions, including requirements around customer consent, notifications, and additional authentication for certain amounts. Those rules disrupted many international subscription services when they took effect, because cards on file could no longer simply be charged on a recurring basis without a compliant mandate in place. By adopting a payment mandate approach, GitHub appears to be aligning its billing in India with these local requirements while restoring the convenience of hands-off renewal.

For GitHub's paid customers, the practical benefit is a reduced risk of service interruption. Individuals and teams who rely on paid tiers — such as GitHub Pro, GitHub Team, or GitHub Enterprise, as well as add-ons like GitHub Copilot — have historically risked lapses in access if a manual renewal was missed. Automatic recurring payments reduce that administrative overhead and lower the chance that a forgotten renewal leads to a downgraded or paused subscription.

The move also reflects a broader industry pattern. When India's updated recurring payment rules came into force, a range of global software and cloud providers had to rework how they billed Indian customers, in some cases pausing automatic renewals until they could implement compliant mandate flows. Companies offering everything from streaming media to productivity software and developer tools have gradually reintroduced automated billing as payment processors and banks built out support for the e-mandate framework. GitHub's update can be read as part of that ongoing normalization, bringing its India billing experience closer to what customers in other regions already have.

It is worth noting that eligibility is tied to specific saved cards; the changelog specifies "eligible saved credit cards," which suggests that not every card or issuer may support the mandate mechanism, and that support likely depends on the customer's bank and card network participating in the relevant framework. Customers who want to enable automatic payments would typically do so through their GitHub billing settings, where the saved payment method and mandate authorization are managed.

For developers and organizations operating in India, the update is a modest but meaningful quality-of-life improvement. It does not change GitHub's pricing or the underlying plans on offer, but it removes a recurring manual step and brings the payment experience in India more in line with global expectations. As with any billing change, customers may want to verify that their preferred card is eligible and confirm the mandate details before relying on automatic renewals for critical subscriptions. The shift is less about new functionality within GitHub itself and more about adapting the platform's commercial plumbing to the realities of a large and fast-growing developer market.