#alex_error

1 messages ¡ Page 1 of 1 (latest)

bitter galeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247694508548820993

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

vernal vapor
#

Hi there!

tulip sorrel
vernal vapor
#

Did anything change in the way you've configured Stripe within Memberpress?

tulip sorrel
#

do, we simply disconnected and re-connected earlier

#

no*

#

although i will say stripe has seen people sign up today but has reported $0 on all the invoices

vernal vapor
#

I see the IDs you shared do in fact exist on Stripe. Give me a few mins to keep digging

tulip sorrel
#

thank you!

vernal vapor
#

This error comes up if a request is made to Stripe using the API key of an account that doesn't actually have access to a particular object. I usually see this if someone has access to more than one merchant account and accidentally authenticates with the wrong account

#

That said, I see you only have access to a single account. Please do not share any API keys with me here

#

Do you happen to have a link where I can see this error in action?

tulip sorrel
#

yes

#

let me enable test mode then you can test it

#

test mode enabled

vernal vapor
#

Thanks!

#

Yep, that's exactly it. So the publishable key and secret keys that are being used to render the PaymentElement and to attempt to create a Subscription (respectively) belong to a different merchant account

tulip sorrel
#

okay, so i either need to change accounts or change the api key to the correct account?

vernal vapor
#

The disconnect/reconnect is likely what triggered this since I see the Memberpress platform was connected to this different merchant account earlier today

tulip sorrel
#

yes

vernal vapor
#

That's correct. Currently, Memberpress is trying to create subscriptions with a plan ID that only exists in the other account

tulip sorrel
#

everything was working earlier today as well but we had been fighting the issue of the payments not coming through on strip and it looked more like a memberpress issue at that point

vernal vapor
#

I can't share much about this second account other than it has the same business name

tulip sorrel
#

i'm one of the owners and have access to all the email account and confirm any information that would help point me to the problem

#

i've spent all day trying to put out each fire as it happens and it's mainly involved issues with the payments not showing up and this issue with the api keys

vernal vapor
#

The only other thing I can share is that the account that is currently configured with Memberpress is owned by an "admin" email address. I hope that helps you narrow it down

tulip sorrel
#

yes thank you so much, so i just need to log back into the other account and it should work fine?

vernal vapor
#

Not exactly. If your goal is to use Memberpress with the account that uses plan_QCfJuxpPs6s0V4, you'll need to log into Memberpress and update your settings to use the API keys that correspond with the account where plan_QCfJuxpPs6s0V4 lives

#

Does that make sense?

tulip sorrel
#

as a point of reference, if i switched to my other account what would the steps be to swap the api keys to the correct key?

#

kind of, i looked for that option in memberpress and didnt see it

vernal vapor
#

I can't really speak to specific steps since those settings are owned by Memberpress. You essentially need to undo/revert the changes made this morning.

tulip sorrel
#

can i ask why when i try to log into the stripe accont it asks me to make a new one?

bitter galeBOT
tulip sorrel
#

account*

vernal vapor
#

I recommend working with Memberpress on next steps so they can help you revert the changes made earlier today. Since you seem to have Stripe Dashboard access to multiple merchant accounts, I recommend searching for plan_QCfJuxpPs6s0V4 in the Dashboard to confirm which account has access to this Plan. This is the account you want to use within Memberpress

tulip sorrel
#

noted, so i logged back into the stripe account i believe i was logged into before through memberpress

#

looks like it's still having that issue

quiet timber
#

unfortunately, it still looks like you're using the wrong account

tulip sorrel
#

so at this point i've tested all the admin emails including the stripe account that the transactions were reporting on and im still having that issue

#

i'm sorry for bugging you with this issue but i've been at this all day and you've been the most help so far

#

i'm looking at the api events in the dev center under the email i'm currently logged into stripe in memberpress with

quiet timber
#

i think lets take a step back, have you found the Stripe account which has plan_QCfJuxpPs6s0V4 like what roadrunner mentioned previously?

tulip sorrel
#

yes and none of them worked

#

or would just signing into my preferred account and swapping the key mentioned earlier be a better solution?

quiet timber
#

i assume that yes and none of them worked means you couldn't find plan_QCfJuxpPs6s0V4 in the accounts you looked in. Maybe the best solution now is to just create a new plan/product on the account that you have connected to and use the newly created one (instead of using the previous one)

tulip sorrel
#

but i'd still run into that error on checkout

#

and on top of that strip didnt capture any payments from the 2 sign ups earlier today

#

stripe didn't capture*

quiet timber
#

i can't confirm that here on this channel as this is a public channel and there is no way for me to perform authentication. you'll need to reach out to Stripe Support and they'll likely be able help you with that - https://support.stripe.com/contact

#

also, i'll recommend you edit your replies to remove all emails since this is a public channel and anyone can see those emails

tulip sorrel
#

noted

#

can you explain to me how the newly created product would solve that problem?

#

and why stripe didn't capture the previous payments?

quiet timber
#

Right now the problem is that your Checkout Session (from Stripe account A) is trying to access a product that exists on a different account (Stripe Account B). If you created a new product (on Stripe account A too), then the Checkout Session (from Stripe account A) will have no problems using it

#

i wasn't aware you potentially already had payments collected already though

tulip sorrel
#

that's fine, the main guy who owns the MGA rushed this out the door without proper testing time

quiet timber
#

again, I can't say if Stripe did or did not capture the previous payments - I don't quite understand the $0 for all invoices bit and where you are seeing that

tulip sorrel
#

so as long as i create a new product in the new account it should work? what about the code itself? will everything automatically

#

i wouldn't need to swap api information? memberpress doesn't ask for api's just to sign into the stripe account

quiet timber
#

I can't say with any certainty. You're using memberpress which is a third party plugin and we don't know how their setup works - for example, I'm not sure where you key in the product / plan id in memberpress. You can try it out and/or also check in with memberpress

tulip sorrel
#

i have checked with memberpress and they're not being very helpful but i understand, on the stripe end of things would the info automatically fix itself if i created a new product/subscription and then connected that stripe account to memberpress?

#

im making the new subscription item in stripe right now

quiet timber
#

so from the Stripe's end of things, if you use a product id #1 that exists on Stripe account A, and if you are also using Stripe account A to create the Checkout Session (and are using that product id #1), it should work

tulip sorrel
#

so all i need to do now is just sign back into stripe on memberpres and it should work correct?

quiet timber
#

again, sorry but I have no idea, all I can say is that you can try it out

tulip sorrel
#

it did not work

quiet timber
#

what didn't work specifically? is it using the new plan/product id?

tulip sorrel
#

i created the new plan and signed into stripe through memberpress but i dont know where i would swap the product id at