#Min.K
balmy hearthBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
radiant dome
Question 1. I want to offer each customer the ability to checkout for a subscription in their local payment currency. I was wondering which method you recommend? I think there are two ways to do this: first, create multiple prices for each currency and let the integration decide which user sees which price. Second, when calling the Price Create API, register the currency-specific prices in currency_options. Which of these two methods does Stripe recommend?
It'll be up do your business decision and prices management which approach will better suit your business. Both will work.
Question 2. Looking at the Price API, it doesn't seem to show currency_options by default. How can I expose it? Is the reason for hiding it because it's not recommended to use it? I'm curious about Stripe's recommended method of supporting multiple currencies.
You may useexpandfield to expandcurrency_options: https://stripe.com/docs/api/expanding_objects
Since Checkout Session will show the local currency based on customer's IP address, it's unlikely user will need currency_options field in their customer face integration.
Question 3. If I register the currency_options through the Price API, it doesn't seem to reflect the currency-adjusted amount to the customer in real-time, so I'll have to continue to utilize the Price Update API to update it when the exchange rate changes. Is there any way to automatically manage the currency-adjusted amount to integrate with the Subscription Checkout Session API?
currency_optionsisn't automatic currency conversion, but the fix amount and currency that your set. Stripe will not change the amount for any FX changes. An update in the amount will be required
cloud vapor
Since Checkout Session will show the local currency based on customer's IP address, it's unlikely user will need currency_options field in their customer face integration.
=> I have additional questions regarding the answers above.
Doesn't Checkout Session need to set currency_options to automatically show the local currency for each IP?
However, I am curious as to why you responded as follows.
it's unlikely user will need currency_options field in their customer face integration.
Doesn't Checkout Session need to set currency_options to automatically show the local currency for each IP?
Yes! You will be able to setcurrency_optionsin the request, but it will be hidden in response by default. What I meant is thatcurrency_optionsis rarely used in retrieval calls.
cloud vapor
To summarize, there seem to be two main ways to offer the same product to a customer in multiple currencies using the Subscription Checkout Session API. Can you recommend which is the better way?
First, you can have one product with multiple prices for each currency and choose which customers pay in which currency.
Second, have 1 Product with 1 Price and set currency-specific prices in currency_options. Which currency to display is automatically selected based on the IP that opens the Stripe checkout window.
radiant dome
Either will work. First option will require your system to manage which currency of the price to use. The second one is handled by Stripe automatically by determining customer's IP address.
If you have other data points such as knowing customer's address or their locations other than IP address, first option might be better. If you don't have any, then second option will be easier.
cloud vapor
Thank you river!