#darrenbot_unexpected

1 messages · Page 1 of 1 (latest)

wary sluiceBOT
#

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

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

final crypt
#

hi! can you clarify, maybe some code and screenshots?

jaunty dune
#

sure!

#

This is the front end using the payments element:

image.png
#

Fromt he Stripe deashboard and in settings the payment methods are not "turned on"

#

These are the only selected payment methods so I'm unsure why this isn't reflected on the website

image.png
final crypt
#

are you using Connect?

jaunty dune
#

🤔 It's a bit odd... It's a implementation that I've used on several sites before, but I've not run into this problem

final crypt
#

so it's using Connect? because then the settings can be controlled by the platform (I don't know if your screenshot is the connected account or the platform's Dashboard).
https://docs.stripe.com/connect/dynamic-payment-methods
You might also be explicitly passing payment_method_types in your code , which overrides Dashboard settings.

jaunty dune
#

Screenshots are from the the connected account's Stripe dashboard settings. The options passed are layout based things and don't override the payment_method_types. To be clear though the implementation is adding a payment source, the source can then be used to subscribe to a product... Not sure if that effects what payment methods can be used but I figured it aught to, perhaps I'm mistaken?

warm whale
#

hi! I'm taking over this thread.

#

can you share a PaymentIntent ID (pi_xxx) with this issue?

jaunty dune
#

Hi Soma

#

I'm not sure if I have a PaymentIntent ID yet - the form is to add a payment source (add a card), would that create a PaymentIntent ID? 🤔

warm whale
#

it depends. there are two ways to use the Payment Element:

  • by first creating a PaymentIntent and sending the client_secret to the frontend to load the Payment Element
  • or by first creating the Payment Element and then create the PaymentIntent later
    which option are you using?
jaunty dune
warm whale
#

got it. but you still have to create a PaymentIntent later. can you share one? pi_xxx

jaunty dune
#

I could grab one from the dev environment, it would have come through via test mode but seems to have the same problem, will that help?

warm whale
#

yep!

jaunty dune
#

2 ticks!

#

ah ha! interesting! I can see in our POST body we're sending those payment method types in a setup_intents

#

The response body obviously then includes those methods in response... Oh dear...

#

Thanks Soma for your help - I'm afraid I'll need to do some further digging into the implementation

#

Thanks for your time and hepl

warm whale
#

happy to help 🙂