#nick_code
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/1283345731939336244
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
The entire stacktrace is in elements code.
Hi, let me help you with this.
Do you have a website where I can reproduce the error?
Could you please share the complete frontend code?
the entire frontend code is too complex.
const STRIPE_OPTIONS = {
layout: {
type: 'accordion',
defaultCollapsed: true,
radios: true,
spacedAccordionItems: false,
},
fields: {
billingDetails: {
name: 'never',
email: 'never',
},
},
} as StripePaymentElementOptions;
<Elements
options={{
clientSecret,
appearance: {
variables: {
colorPrimary: organisation?.theme?.button_color_1,
colorBackground: organisation?.theme?.sections ?? 'transparent',
colorText: organisation?.theme?.text_color,
colorDanger: '#df1b41',
borderRadius: '8px',
},
},
}}
stripe={stripe}
>
<PaymentElement
id="payment-element"
onChange={(e) => {
onMethodChange(e?.value?.type);
}}
options={STRIPE_OPTIONS}
/>
<CheckoutButtons />
</Elements>
Ok, I see there's an incident ongoing about iDEAL and Payment Element
What can we do to fix it. Our clients are losing a shit ton of revenue haha
I see there are breaking changes in the docs around ideal payments, but it's weird to me it breaks existing code.
We can of course implement that new flow and push to production, but would take some hours, which is not great
I would say you could disable iDEAL from the Dashboard for now, please write in to Stripe Support to be notified when it's mitigated and you can turn it back on
99% of our rev is ideal
let's not
Or are you guys implementing a fix on the libraries at the CDN and do we just wait?
I see there is no incident on the status page
Can you please share your account Id ?
acct_1M84E7HlWbdNGYe2
Heads up that all our payments go through connect accounts
Thanks for sharing, our team are currently investigating..
A fix is currently deploying...
It would take ~1hour for this one I think...
Looks like everything is up and running again. Can you confirm? @tame oasis
the deploy is in progress yes. If you have a support ticket open they'll send you comms when we consider the issue resolved(we might also do some proactive outreach with direct email)
@still parcel this should now be resolved, let us know if you're still seeing issues