Search for how to use Ghost memberships from a country Stripe does not support and you will find the same answer within about three results. Register a company somewhere Stripe operates. Use a formation service. Open the Stripe account against it. Connect Ghost. Done.
It works. That is the problem with it.
Why it works at first
Stripe’s account opening does not investigate you. You give a registered entity, an address, an account, and the checks that run are automated and shallow at that stage.
So the account opens, the first charge succeeds, Ghost shows a paying member, and the whole thing looks solved. People write forum posts at this point saying it works fine.
The scrutiny is not at signup. It is later, and it is triggered by things you do not control.
What the requirement actually says
Stripe requires the business to be genuinely established in the country of the account. Not registered there. Established: operating from there in a real sense.
A formation-service address you have never visited, with no operations, no staff and no local activity, does not meet that. The company itself may be perfectly legal to own. The Stripe account against it is representing something that is not true, and those are two separate things that get conflated in every forum thread on the subject.
The pattern that gets caught
Here is what the arrangement looks like from Stripe’s side.
An account registered in one country. Payouts to a bank in another. A customer base concentrated in a third, usually the same one as the bank. Login traffic from that third country. A director resident there.
That shape is exactly what compliance review is built to detect, because it is also the shape of several kinds of fraud. Nobody has to suspect you specifically. The pattern is the flag.
Reviews are usually triggered by volume growth, a dispute or chargeback, or a routine sweep. All three arrive without notice, and the third one arrives for no reason at all.
The failure mode
The sequence is a documentation request, then a hold on payouts while it is assessed, then a resolution or a closure.
The part that hurts is the middle. During a hold you are still charging subscribers, because your Ghost site does not know anything has happened, and the money is not reaching you. If it ends in closure, you are unwinding a subscription business by hand while explaining to readers why their access is changing.
Recovering from it means more than finding a new payment provider. Every active subscription has to be recreated somewhere else, and each one is a customer being asked to re-enter their card. Some of them will not bother.
There is a version of this that stays fine indefinitely. Nobody can tell you which version they have until it is decided for them, which is the actual objection: it is a risk you cannot measure sitting on top of your revenue.
The reasoning behind it, and what it gets wrong
The thinking usually runs: Ghost needs Stripe, Stripe will not take me, therefore I need Stripe by another route.
The first step is where it goes wrong. Ghost does not need Stripe. Ghost’s built-in billing needs Stripe, which is a much smaller claim.
Ghost’s membership machinery, tiers, gated posts, newsletters, member records, is provider-agnostic. It grants access based on what a member record says, and the Admin API will create and modify those records for anyone holding a valid key. It has no opinion about where the money came from.
So the problem is not “I cannot use Ghost memberships.” It is “Ghost’s payment step assumes Stripe,” and that step can be replaced.
What replacing it looks like
Take the payment through a provider that operates where you actually are. Have something translate a completed payment into a Ghost membership.
The whole architecture is those two sentences. In practice: a custom integration in Ghost gives you an Admin API key, your provider sends a webhook when somebody pays, and a mapping says which product grants which tier.
You keep your real business in your real country. Your provider knows who you are and where you are. Nothing about the arrangement needs to be described carefully to anyone.
Which provider depends on one question that outranks all the others: can it pay out to your bank account? Check that in the provider’s own documentation rather than in an article, including this one, because coverage changes and articles do not.
The full comparison of routes is here. Why Stripe not operating in your country is not the end of the conversation.
When incorporating abroad is genuinely right
There are real reasons. Investors who want a familiar jurisdiction. A genuine team or customer base somewhere else. Market access that requires a local entity. A second base you actually operate from.
In all of those cases the entity is real, the establishment claim is true, and a Stripe account against it is not misrepresenting anything. The payment provider is a consequence of the decision rather than the reason for it.
Use that as the test. If the only thing the foreign company does is hold a payment account, the arrangement is doing exactly the thing the requirement exists to prevent.
The uncomfortable summary
The forum advice is not wrong about whether it works. It is wrong about what it costs, and the cost is deferred, which is why the people recommending it have usually not paid it yet.
The alternative is less exciting: use a provider that will have you, and put something between it and Ghost. It has no clever workaround in it, which is probably why it comes third in the search results.
Related: what to check when a payment produced no Ghost member, and how EU VAT applies when you sell from outside it.