#Harrison - customer default currency
1 messages ยท Page 1 of 1 (latest)
Hi ๐
The most direct way around this would be to collect the Customer's preferred currency and use a $0 price that corresponds to that currency.
Harrison - customer default currency
Thanks for the response!
That was my first thought, but we're inevitably going to end up with customers complaining who assumed they could change it later, or customers who had signed up with our original USD pricing and now wish to pay in their local currencies.
For the record, we currently only offer USD and have a fairly large subscriber base on that pricing. We're in the process of implementing this, but have been really surprised at the lack of support outside of Checkout for working with new currencies.
Is there something we're missing? How are other SAAS sites handling multi-currency setups on Stripe?
I suspect many large SAAS platforms are simply creating multiple customers and including metadata to allow them to link the records together in their own system.
That is how I would try to square that circle
Interesting. Assuming we did something like this, how would our Stripe payment methods work? IRRC, these are associated to individual Stripe Customers, so we would be unable to save and re-use these methods across different currency purchases, correct?
I really appreciate the advice by the way. It's really unfortunate that this is even a limitation, as we're otherwise very happy with Stripe. The way that currency is handled right now though is pretty frustrating.
You are correct you would need to use the specific PM for a given currency.
Yikes. I don't think I'll be able to sell that to our product manager.
Well thank you so much for your input. I think we may just need to put freemium on hold until we can figure out some workarounds that make sense for us.
Have a good one!
You too! We do have multiple currency prices available currently https://stripe.com/docs/api/prices/create#create_price-currency_options but I haven't tested to check the impact on Customer default currency.
Thanks, I'll definitely take a look at that. I had noticed the dashboard supports something similar to this (could even be the same feature), but I wasn't sure if this was a Stripe Checkout exclusive feature or not
Yeah, it looks like you're able to add those via the API but they aren't returned in any of the responses.
I think that option is probably to do with this: https://stripe.com/docs/payments/checkout/present-local-currencies#:~:text=To present currencies in Checkout,the API or the Dashboard.&text=From the Product details page,to create a new price.
That may be a viable option you can test out. I hope that will work for you
AFAICS this is Stripe Checkout only. If the decision was up to me I'd be suggesting we use Stripe Checkout for the currency features, but we really want to keep our in-app checkout with Elements. We've compared and found the in-app converts much better, especially when presented as a modal
I suppose a middle ground for us may be to run a customers regular charges in-app, and if they're trying to use a new currency send them out to Stripe Checkout.
Wait a sec, when you said the multi currency prices aren't returned, are you expanding thecurrency_options hash?
Ah probably not, 1 sec
Sorry for not catching that earlier. It was oddly crazy for a bit there
Hey no worries! So yes, I can see the currencies being returned now, but I'm not sure that I'm able to do anything with them as they don't have ID's.
๐ค So perhaps not a panacea here.
Unfortunately not. I think this gives me enough to make a decision about how we can proceed though. I know I read somewhere that Stripe was working on better support for non-checkout and currencies, but I haven't been able to dig anything up yet.
So I think we may experiment with conditionally using Stripe Checkout depending on what the customer is trying to do.
Thanks for all the insight and help