#creedsnow
1 messages · Page 1 of 1 (latest)
Do you have any more details than that? Like a request ID?
That error message is pretty generic, so it'll be hard for us to know what's going on without looking at the request
On a client site they sell tickets and today when they were trying to purchase tickets that was the error they kept recieving.
Are you a developer helping them with their Stripe integration?
Im a developer, I didn't set up the stripe integration but I do have access to the ticket plugin on the wordpress site the tickets are being bought on. I can't get ahold of the person who set it up as its 2am where he is, so Im trying to check this off this list if possible. I apologize for the incompetence.
No worries at all - I'm just trying to narrow down if you have access to the information needed to dig into what's going on
Do you happen to have the stripe account ID for you client?
I did some googling as we always do when we dont know lol And it said it could be a caching issue. When I look at the stripe panel, everything seems to be checked off as right as my knowledge can verify. It says, "connect as: acct_1Eni3Elk9bdaiJuN.
I'm not sure if that is the ID
Can you log into the stripe dashboard?
Not at this time, its 2factored and their reach out person doesn't have access. Its one of those typical clients can't be bothered but expect magic deals. If its not possible to narrow down, the only other option is to wait for the person who has the overal access to wake up in a few hours.
Yeah, if you don't have access to the dashboard then your best option is to wait for the person who does have access - especially because the account ID you gave doesn't appear to be correct
Thank you anyway, I appreciate the fast response time