Can I use Ghost memberships from India at all?

Yes. Ghost's membership features, tiers, gated posts and newsletters, work anywhere. What is constrained is the payment step, because Ghost's built-in billing only speaks to Stripe. Move the payment to a provider that works for you and Ghost keeps doing everything else.

Why does my recurring subscription fail on renewal even though the first charge worked?

Most likely the mandate rules for recurring card payments in India rather than anything in your setup. Renewals need a registered mandate and often an authentication step, and a first payment succeeding says nothing about whether the second will. Test a real renewal before you rely on it.

Should I use a merchant of record or a processor?

A merchant of record removes the cross-border tax question if most of your readers are abroad. It also has to be able to pay out to an Indian bank account, which is the constraint that usually decides it. Check payout availability first and treat tax handling as the tiebreaker.

Is a foreign company just to get Stripe worth it?

Rarely, and it is not the shortcut it looks like. Stripe requires the business to be genuinely established in that country, and foreign payouts against a domestic customer base is exactly the pattern account reviews catch. There are legitimate reasons to incorporate abroad; access to a payment provider is a bad one on its own.

What if my readers are mostly in India?

Then a domestic provider with UPI and local card support will convert far better than an international checkout, and the cross-border tax question mostly disappears. The trade is that you handle your own compliance rather than a merchant of record doing it.

Ghost Memberships in India: Payment Options That Actually Work

Most advice for Indian publishers running Ghost addresses one problem. There are two, they are independent, and solving only the first leaves you with a membership system that takes a first payment and then quietly stops.

Problem one: Ghost asks for Stripe

Ghost’s membership billing is built directly on Stripe’s API. Not a payment abstraction with Stripe as the first implementation, but Stripe objects wearing Ghost’s interface.

For an Indian publisher that is an immediate wall, and it has nothing to do with your business being viable. The feature is simply not reachable.

This one is solvable, and the solution is the same everywhere: take the money through a provider that works for you, and put something in between that turns the payment into a Ghost membership. Ghost’s Admin API has no opinion about where money came from. The full set of routes is here.

Problem two: recurring payments in India are genuinely hard

This is the one that gets skipped, and it is the more interesting problem.

India regulates recurring card payments more tightly than most markets. Renewals require a registered mandate, there are authentication requirements around them, and the rules have changed more than once. The practical effect for a subscription business is that a successful first charge tells you very little about whether the second one will go through.

That is a different failure mode from anything in this blog’s other guides. Elsewhere, if the setup works once it generally keeps working. Here it can work once and stop, and the failure surfaces a month later as a member who quietly lost access, or one who kept it without paying.

So the test that matters is not “did the purchase work”. It is “did the renewal work”, and you cannot answer it on the day you set things up.

What this means for how you choose

Payout availability first. Everything else second.

A provider with a better dashboard, lower fees or nicer checkout is worth nothing if it cannot send money to your bank account. This is the only binary question in the list, and it eliminates more candidates than anything else.

Do not take this from a blog post, including this one. Provider coverage changes, and an article that names specific countries is out of date the month after it is written. Open the provider’s own payout documentation, find your country, and confirm it before you spend an evening on integration.

Then, in order:

Where are your readers? If they are mostly in India, a domestic provider supporting UPI and local cards will convert dramatically better than an international checkout asking for a card. If they are mostly abroad, an international merchant of record makes more sense and the cross-border tax question becomes the deciding factor.

This one question changes the answer completely, and it is worth being honest with yourself about it rather than optimistic.

Recurring or one-off? Given how much friction sits around recurring payments here, a one-time purchase granting permanent access, or an annual payment rather than monthly, avoids a large amount of machinery. Fewer renewals means fewer chances for a mandate to fail. For many small publications an annual tier is a better product anyway.

Who files the tax? If your readers are international, a merchant of record removes the question entirely. What that actually means.

The route that keeps coming up, and why it is a bad one

Incorporating abroad specifically to open a Stripe account.

Stripe requires the business to be genuinely established in the country of the account. A registered address you do not operate from does not meet that, and the resulting pattern, foreign payouts against a largely domestic customer base, is exactly what account reviews are designed to catch.

The failure mode is a freeze while you are holding subscribers’ money.

There are real reasons to incorporate abroad. Access to a payment provider, on its own, is not one of them, and the people recommending it in forums are usually not the ones who have had an account frozen.

What the working setup looks like

Once you have a provider that can pay you, the rest is the same as anywhere.

Connect Ghost through a custom integration in Settings, then Integrations. Ghost gives you an Admin API key.

Connect your provider: webhook URL in, signing secret back out, events selected.

Map one product to one Ghost tier.

One thing differs depending on whether you have a Stripe account. With one connected, even an idle one, buyers become comped members and Ghost’s own gating handles the rest. Without one, Ghost will not mark anybody as paid at all, so access is carried by a label on the member and the paywall script checks that label. Both work. The second means the script has to be in your theme rather than dropped into a single post. The full comparison of the two.

Then buy it yourself. And this is where the India-specific advice differs from every other guide on this blog: do not stop at the purchase. Let a renewal happen, or force one if the provider allows it, and confirm the member still has access afterwards. Then cancel and confirm the access goes away.

Three tests, not one. The purchase is the part that fails loudly. The renewal is the part that fails quietly and expensively.

Being honest about the limits of this article

I can tell you how Ghost’s constraint works, because Ghost is open source and I have read the part that imposes it. And I can tell you how to get past it, because that is what I build.

Worth being exact about what “past it” means. The constraint does not go away. Ghost still wants a Stripe account connected before it will show you its membership settings, and that stays true with PayGlue in the picture. What changes is that the connected account no longer has to be the one taking your money. It can sit there idle while a provider that actually operates where you live does the work.

I cannot tell you which provider will pay out to your specific bank next month, and any article that claims to is guessing or repeating something it read. Payout coverage is the one thing to verify at the source, and it takes ten minutes.

What is worth taking from here is the shape of the problem: it is two problems, not one, and the second only shows up after you think you are finished.