#storm-guardian_unexpected
hardy lichenBOT
👋 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/1435205980735541390
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
vivid hollow
Event visible in prod webhook, but data can't be accessed
Payment visible in test mode, only when using prod connected account id directly in the url
chilly terrace
👋 Hi there!
Can you share the ID (req_xxx) of the request that you believe should have returned an error?
vivid hollow
Here's one of them : req_PF9ENRsLm3g6jf
hardy lichenBOT
vivid hollow
Creation of the paymentMethod : req_1MVdK0sJFIHhFk
mossy hull
Hi there. So this is actualy the expeced behaviour as the connected account is only connected in live mode to the platform. This doc gives a good overview of how this works and what you can do: https://docs.stripe.com/connect/webhooks#connect-webhooks
vivid hollow
Ah !
This feels weird, even more since the data of the event cannot be seen in the dashboard
and it's really weird to be able to use the ID of production connected account. Which makes it difficult to find the data in the dashboard
mossy hull
Is there something in particular that you would need help finding, or unclear in the docs?
vivid hollow
Thanks for the documentation explaining why the events triggers in prod.
However I still don't understand why I can use an non existing connected account in test mode without any issue
Maybe its also a feature ?
mossy hull
How do you mean non existing?
If you mean the account isn't in test mode, then having a connected account in live mode doesn't prevent interacting with it in test mode
mossy hull
You can't have sandboxes in live mode, so this doesn't really apply there
vivid hollow
I'm thinking about switching from test mode to sandboxes in the developpement process
That's why I'm asking if the behavior would be the same.
mossy hull
The sandbox will be its own isolated environment, so there would've be live/test mode confusion there
vivid hollow
So, with the sandbox, I wouldnt be able to create a paymentMethod on a customer attached to a production connected account ?
Whereas it's possible with test mode
mossy hull
No, it would be treated as a separate account with its own customers
vivid hollow
So the call with the sandbox privateKey would fail ?
mossy hull
A call to a customer on the live production account? Yes
vivid hollow
OK
So, sandbox should be seen as a COMPLETLY ISOLATED environment
BUT the test mode, is more of an overlay of the production environment. We see in the dashboard, only the data created in test mode BUT we can access production accounts (not their data though)
mossy hull
Yes, sandbox is completely isolated, and can be thought of as a completely separate account
vivid hollow
so in prod/test mode. Accounts are somehow shared (even though they do not appear in the dashboard)
Are there any other resources shared ?
I would havec expected products to be "shared" but I just made a test and :
Ressource product inexistante : 'prod_TMQmZuDeroACVb'; a similar object exists in live mode, but a test mode key was used to make this request.
hardy lichenBOT
deep kayak
hey there 👋 taking over for my colleague now - just getting caught up
Are there any other resources shared ?
do you mean across live and test mode? if so then no, other resources are generally limited to the 'mode' they exist in
deep kayak
you can interact with live connected accounts in test mode, but this isn't true for other resources (customers, subscriptions, etc)
vivid hollow
Oki