#ks_api

1 messages · Page 1 of 1 (latest)

finite vesselBOT
#

👋 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/1425693133177356391

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

#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

still basin
#

Hi! Looking into your question!

nova jay
#

Since the parent ids are the same for the child configs in both accounts, is it correct to assume that it is a config in the platform account instead of the connected account? Is this why it does not exist in the list of configurations for the connected accounts?

still basin
#

Thanks for waiting! As per the request you are attempting to retrieve pmc_1RO0RJJwYUP6g6g2IOaB5x0r on the connected account acct_1S3WbGLcwiQgMjz4. But this PMC belongs to the platform acct_187cFEJwYUP6g6g2. Which is why you're getting the error: No such paymentsconfig. You need to retrieve the PMC without the Stripe-account header.

nova jay
#

Hi @still basin . Thanks for the info. I tried retrieving the PMC without the Stripe-account header, but it returned this error

  "error": {
    "message": "Platform parent configurations can only be managed via the dashboard.",
    "request_log_url": "https://dashboard.stripe.com/logs/req_nUx7Ltfa8od3iC?t=1759983711",
    "type": "invalid_request_error"
  }
}

For more context, we are checking for whether paynow payment method can be used when creating a checkout session. I'm able to ask my colleague to check the PMC in the dashboard, and it shows that paynow is off in the parent PMC. However, the child PMC also has paynow off. This makes me confused because I tested creating a checkout session with paynow for this account and it worked without any errors. Is there something wrong with how I'm checking for the availablility of thepaynow payment method?

Screenshot_2025-10-09_at_12.20.30_PM.png 📎 message.txt
still basin
#

For the first part, yes I do apologise, you can only inspect and update the parent PMC from the dashboard.

#

I tested creating a checkout session with paynow for this account and it worked without any errors.
Can I have the Checkout Session ID please?

nova jay
#

Checkout Session ID : cs_live_a1vfcUmeqbY3jBtaUXK47LnpKZeea8b0xzxY67kWjH40NuGKegmWB8QFR1

still basin
#

So the payment method configuration is there for dynamic payment method. But since you explicitly passed card and paynow for payment_method_types when creating the checkout session, it used those instead. Also the connected account has the paynnow capability. So due to both of these, PayNow appears as a payment method.

nova jay
#

So does this mean that if I always pass card and paynow to payment_method_types when creating checkout sessions, it will always work regardless of which connected stripe account we are using and which configurations they have? I was previously under the impression that if e.g. paynow is somehow unavailable for an account, passing it into payment_method_types will cause an error. That's why I'm trying to inspect the payment method configurations before pass it in

#

I received this error when trying to create checkout sessions with paynow in another account:

  "error": {
    "message": "The payment method type provided: paynow is invalid. Please ensure the provided type is activated in your dashboard (https://dashboard.stripe.com/account/payments/settings) and your account is enabled for any preview features that you are trying to use. See https://stripe.com/docs/payments/payment-methods/integration-options for supported payment method, currency, and country combinations.",
    "param": "payment_method_types",
    "request_log_url": "https://dashboard.stripe.com/acct_1IGmgXIBDX95QOQY/logs/req_cq4DJrcGgnYSBJ?t=1759987253",
    "type": "invalid_request_error"
  }
}
still basin
#

So does this mean that if I always pass card and paynow to payment_method_types when creating checkout sessions, it will always work regardless of which connected stripe account we are using and which configurations they have?

  • When you pass payment method types, it overrides the payment method cofiguration.
  • If the connected account has the capability for the that particular payment method type, then yes it will always work.
  • But if they don't you will see an error
#

I am looking at req_cq4DJrcGgnYSBJ now.

nova jay
#

Thank you. Regarding point 2, is there a way I can double check the capacity of the connected account to avoid the error?

still basin