#loaderchips_code
1 messages ยท Page 1 of 1 (latest)
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.
- loaderchips_code, 1 hour ago, 7 messages
- loaderchips_best-practices, 4 days ago, 46 messages
- loaderchips_code, 5 days ago, 47 messages
๐ 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/1269943946214248481
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hey @prisma sable
๐ happy to help
this is the network log -- Request URL:
https://api.stripe.com/v1/payment_pages/cs_test_a1CQcIe5XhpB91qTyNQ4impx7XG1Z3Sd7d7a08LFXA7AmWYDGPCTHspx6x/init
Request Method:
POST
Status Code:
404 Not Found
Remote Address:
52.76.14.176:443
Referrer Policy:
strict-origin-when-cross-origin
taking a look
this is the stripe request id -- req_NbqhZTSl2zblNv
these are the library verions on client side -- "@stripe/react-stripe-js": "^2.7.3",
"@stripe/stripe-js": "4.1.0",
on the server we are creating the session like this. not sure if stripe_account param is affecting this somehow -- session = Stripe::Checkout::Session.create(session_params, { api_key: ApiKeySelector.standard_connect_api_key, stripe_account: @nonprofit.connected_account.account_id })
how are you initiating your Stripe.js instance?
are you passing the connected account ID?
no. this is how we initiate it -- const stripe = loadStripe(
'pk_test_51KmI8jAY9OACmYiwv6QXagmlPqJQtIq1i0EmJfrWdjmputVRqT5bfND1dvDvCjIU8Cagg68IHGoVmafeaN0nKGrm00b4xWkH8F'
);
that's the issue
when you created the CheckoutSession, you created on behalf of your connected account
but when you're trying to display it on your frontend
makes total sense
you're searching in your platform's resources
is there a way to provide the stripe_account in loadStripe?