#neatanderthal_ideal-bank
1 messages · Page 1 of 1 (latest)
👋 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/1286329921827901501
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
What do you see now?
In the JS Elements window is since today the bank dropdown missing. Before there was a dropdown with the option to choose your bank.
Last week we experienced the same issue, but at that time it gave a javascript error. And the whole code was crashing. Now it does work, but the bank selection is a redirect to a new page. Not the desired behaviour. Is there an option to get the bank dropdown back in the iDeal option?
The issue from last week:
#dev-help message
Sorry in many threads right now. Can you summarize the issue from last week and what resolved it?
Also did anything change in your integration?
No the problem was escalated to the developer team of stripe and fixed with a new deploy (please check the linked issue in my last message)
But long story short;
We are missing a dropdown that has always been available in the screenshot that I added to the last message above. Without changelogs or any notice it is missing since today.
We need it back in terms of user experience. It is now redirecting to a bank selection page, inconvient for our users.
https://www.bistroo.nl/eindhoven/restaurants/two-b-eindhoven
Please select a random product, click view order, click complete order, click next step, fill in random credentials, click next step. And then you get the result from the screenshot above.
Regarding our code, our implementation is already working for 2 years. Nothing has changed to our code. The behaviour has changed because the stripe team deployed a new version today.
Code:
function createForm(el, clientSecret) {
elements = stripe.elements({
clientSecret,
})
const payment = elements.create('payment', {
paymentMethodOrder: ['ideal'],
fields: {
billingDetails: {
name: 'never',
email: 'never',
},
},
})
payment.on('loaderror', (event) => {
if (event.error !== undefined) {
sentry?.captureException(new Error(event.error.message))
}
})
payment.on('change', event => {
paymentMethod.value = event.value.type
paymentIssuer.value = ''
state.completed = event.complete
})
payment.mount(el)
}
async function makeStripePayment() {
const {
name,
email,
} = store.getters['user/user']
await store.dispatch('session/rememberCurrentLocation')
await store.dispatch('session/storeInstructions', '')
const { path } = router.resolve(localizedRoute({
name: 'thanks',
params: { orderUuid: state.orderId },
}))
const callbackUrl = `${import.meta.env.VITE_FRONTEND_URL}${path}`
await stripe.confirmPayment({
elements,
confirmParams: {
return_url: callbackUrl,
payment_method_data: {
billing_details: {
name,
email,
},
},
},
redirect: 'always',
})
}
Ok thanks
Still looking in to this. I am seeing the same behavior with iDEAL on our other surfaces and I am not immediately seeing a way to get the select field back. Trying to figure out what may have changed
Can you tell me a bit more about how this is impacting your integration? Are payments still able to go through, but with the redirect happening earlier than expected? Or does this break your integration in some way?
It is impacting the user experience with a extra step in the proces. Before it was selecting iDeal and a bank in the same window. After that the user was redirected to their bank app directly. Now you need to select the bank in a extra stripe page outside of our environment. Especially with a native app there is an unnessecary browser redirect to a stripe bank select page.
Due to this we’re experiencing a conversion drop because users don’t expect this behaviour.
Gotcha, thank you for the detail, passed that along. Will let you know what I hear back from my colleagues
Thank you for the quick response 🙂
My colleagues got back to me, this was an intentional change but it was required by the scheme. If you are already seeing a conversion impact you can write in to our support team and they can look in to/escalate that https://support.stripe.com/?contact=true