#megio_error

1 messages ยท Page 1 of 1 (latest)

calm pikeBOT
inland veldtBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

calm pikeBOT
#

๐Ÿ‘‹ 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/1239483184786444330

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

long creek
#

It looks like you don't have access to this beta, have you asked support about it? https://support.stripe.com/contact/email

#

There's a form at the bottom of this page to register for this beta.

opal sedge
#

if yes, I should have already registered my account

long creek
#

And did you receive any confirmation that your account is ready to use this beta?

opal sedge
#

just the form's feedback on the docs page:

long creek
#

Ok, if you didn't receive any confirmation your account isn't ready for this beta

opal sedge
#

how long does it usually take? Cause I submitted that form also last Friday but didn't receive any confirmation's email yet

long creek
#

I don't know, but you can follow up with support

opal sedge
#

got it. The weird thing is that last Friday, I wrote here about the same problem. One of your team members check on my account and told me that my account was enabled for this beta, and I was able to fix this error. Today, I've started my working day and the error was back ๐Ÿ˜ฆ

#

anyway: thanks, I can definitely ask the support