#yerayamenitiz_unexpected
gloomy hatchBOT
đ 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/1272955728566423705
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
chilly sun
Hello! Are you using the Payment Element?
shell pendant
I'm unsure to be honest. We are using this to initialize Stripe(stripe_public_key and then let elements = stripe.elements(); then we create the card element and we end up doing stripe.confirmCardPayment
with the result we send it to the backend and we capture it
Is that Payment Element?
chilly sun
Does it look like the screenshot here? https://docs.stripe.com/co-badged-cards-compliance?type=web-elements&ui=payment-element
shell pendant
The one on the second link
But we have another place in the app where it looks like the first screenshot
because we are revamping the frontend part and we are using the newest docs
so on the nwest part of the app it looks like the first screenshot and on the old one it looks like on the second screenshot
okay I see, the one I'm mentioning it's called "card elements"
and the one in the new version of the frontend it's called "payment element"
just so you know this is how it looks now
chilly sun
Gotcha, that's the Card Element.
shell pendant
and that's how it looks like with a CB card
which is exactly what I'm expecting
however, it does not work in production
I have already done the API request to enable CB on the connected account and it's active according to the stripe dashboard
I know the client must process 50 euros with eligible CB cards but has already done so and now it shows as fully active
so I'm a bit lost here
thanks for your help
chilly sun
Are you using onBehalfOf when initializing Elements?
shell pendant
no I'm not
I'm using onBehalfOf when creating the payment intent
this is how the Elements init looks like in our old frontend const stripe = Stripe(stripe_public_key, { api_version: <%= STRIPE_VERSION.DEFAULT %> });
chilly sun
Ah, that's probably the issue. See here: https://docs.stripe.com/co-badged-cards-compliance?type=web-elements&ui=card-element#connect-platforms
shell pendant
does that param affect anything else?
chilly sun
It lets Elements know that the payment is on behalf of the connected account, and shouldn't cause a problem if you're already using it on the Payment Intent.
shell pendant
it works fine locally
for the Payment Element (not the Card Element) should I also specify this param?
yes according to the docs, but only to confirm
chilly sun