Best practices for Stripe international subscriptions?

Unfortunately, pricing in local currency won't reduce failed international transactions in Stripe. It may reduce friction when people are deciding whether to buy or not, but it has no bearing on whether the transaction fails or succeeds. It's not the currency that determines whether the transaction is "foreign" or not - it's the location of your company. I know this from years as a Canadian company, charging in US dollars to US customers, many of whom still had failed transactions or foreign transaction fees despite us charging in their local currency.

Many credit cards either restrict foreign purchases entirely, or they will fail because they've flagged them as fraudulent, and the CC owner needs to respond and let them know that it's not fraud, and then the next time it will go through.

At small scale, the best solution here is to reach out to those people manually (set a Zapier zap up to let you know when a transaction fails or similar) and ask if you can help. Sometimes a different card will help, sometimes sending a PayPal invoice manages to succeed where Stripe fails.

Larger scale, the best solution is to have subsidiaries in countries where you do most of your business with local banking and credit card processors so that your transactions are no longer considered international, but that's likely a long way off for most of us.

The only issue I have with that in my WBE Space is with clients from India. For some reason, it is not possible to collect money from them monthly. What I normally do is to ask them to pay for one year right away

Hey @yousaiditchewie! 👋

I can give you some insight on how I solved this problem while working at mojo where we had 15 different pricing based on the country.
As a side note, this is a problem that first occurred to us when we reached 5M$ ARR and beyond, and it's often more trouble than worth to support multiple currencies if you don't have product market fit yet 😊

There is no real "automatic way" of handling internationalisation, but you can provide a naive implementation quite easily.
First of all, you need to create at least one price per country on your product page in Stripe (one product, multiple prices). See here if you don't know how to create multiple prices for your existing product.

Once this is done, the tricky part is to display the right price based on the location of the user. The easiest way to do this is to based yourself on the ip address of the user (if server side) or on the geolocalisation API (from the browser or client side) to detect his country. Once it's done, you just have to switch over your existing prices and create a checkout session with the correct one or the default one if the country is not supported yet.

Note that this is not particularly precise and can be easily bypassed, but for 95% of the users, it does the trick.

Regarding the sales page, it kinda depends on the time and effort you wanna put into this. The easiest is probably just to customise the price value with the specific currency based on localisation of the user and apply it at checkout, but leave the rest of the content in English (or whatever language you write your content in).
If you've more time and availability, you can decline the complete page in multiple languages based on the market you wanna target, so you can benefits from local SEO/ASO.

Internationalisation is often a Serie B-C problem for startups (if we talk in terms of funding size), so as I said previously, it's really rare you encounter these kind of problems in your indiehacking journey and you shouldn't put too much time covering this too early 😉