robotlos_api

[uncut token]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1426294293613510767

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[tawny wasp]

It'll only show to users in supported regions

And yes you can customize those in your payment method settings

[slow latch]

Got it so we need to do this from the stripe dashboard and not in code

[tawny wasp]

Correct

[slow latch]

A followup question. When specifying alipay or wechat as a payment method type, why do we need to specify the client on the payment method options ?

e.g.

payment_method_options: {
        wechat_pay: {
          client: 'web',
        },
      },

[shell lion]

Hi there, taking over for @tawny wasp as they had to step away

I'm looking into this for an exact answer. Out of curiousity, is this configuration preventing you from implementing something in your integration?

[sinful dawn]

Also, we are not using the configs from the dashboard. We are specifying from code when we call create session what payment methids are supported. Will this config per country work for that?

Out of curiousity, is this configuration preventing you from implementing something in your integration?
Yes, we did not add that. And now it does not create a checkout session

[slow latch]

Yes @shell lion thats correct we are blocked. Here is the error I am seeing in the checkout session creation

error: WeChat Pay requires `payment_method_options[wechat_pay][client]` to be set to `web`.

[shell lion]

And did you try adding that configuration in your code?

[sinful dawn]

Yes we did and the code does not build

[shell lion]

Can you share the request ID associated with the error so I can take a look?

[sinful dawn]

Can you please explain why do we need to set this?

And do we have to pass it differently for our mobile app? We are using hosted checkout web views in our app

[shell lion]

WeChat Pay specifically has different requirements depending on the client. For example, you need to send payment_method_options.wechat_pay.app_id, but only for iOS or Android
https://docs.stripe.com/api/checkout/sessions/create?api-version=2025-09-30.preview&rds=1#create_checkout_session-payment_method_options-wechat_pay-app_id

The idea is that by sending the client specifically, Stripe can provide the different flows required for each client

It does seem like a sub-optimal experience though, I can flag this as a request for improvement