#gabriele-frattini_webhooks

1 messages ยท Page 1 of 1 (latest)

night solsticeBOT
#

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

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

hard vigil
#

Could the reason our webhook does not work in test mode be because we created the connected account in live mode first?
But then its weird that the payment pi_3SX0sTIVVMDlU7tY0qxTmqbx in test mode was sucessful? the only problem we have is that no event was delivered to our webhook in test mode

gaunt solstice
#

๐Ÿ‘‹ Hi there, just taking a look now

hard vigil
#

hello! thank you

gaunt solstice
#

I think this note from our documentation at https://docs.stripe.com/connect/webhooks might be relevant, but I'm just checking if that applies to your specific scenario: For Connect webhooks, your development webhook URLs receive only test webhooks, but your production webhook URLs receive both live and test webhooks. This is because you can perform both live and test transactions under a production application.

hard vigil
#

interesting

#

our development webhook should have recieved a test webhook

#

Let me know if you need any more information from me but there is no stress

gaunt solstice
#

Strange, as far as I can see your pi_3SX0sTIVVMDlU7tY0qxTmqbx in test mode did actually deliver event evt_1SX0sVIVVMDlU7tYnxXMCeA5 to your webhook

night solsticeBOT
hard vigil
#

oh okay, weird. I dont see it in the workbench or our own logs

haughty mauve
#

I'll be sending a consent link shortly, so that we can access your Dashboard to check why you don't see the event delivery. Could you please confirm the access?

night solsticeBOT
#

Hello @hard vigil, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442880938303553668

  • ๐Ÿ”— The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
haughty mauve
#

If you search the event ID directly, will you be able to find the event delivery attempt?

hard vigil
#

one sec

#

I just gave you access to the dashboard

haughty mauve
#

This is the link for connected account Dashboard. Let me double check viewing from the platform

#

Sorry, I'll need the consent again for your platform account. Could you help me to approve the access to your platform account as well?

night solsticeBOT
#

Hello @hard vigil, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442880938303553668

  • ๐Ÿ”— The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
hard vigil
#

yes!

#

approved

haughty mauve
#

Thanks! Checking it now

#

The delivery attempt shown in our records showed evt_1SX0sVIVVMDlU7tYnxXMCeA5 was delivered to live mode Webhook endpoint. Indeed that the event wasn't sent to we_1IyITTILgSZ3iaDE7dXeuHJM in test mode. I could see other checkout.session.completed events being delivered to we_1IyITTILgSZ3iaDE7dXeuHJM. Did you observe this issue only specifically to pi_3SX0sTIVVMDlU7tY0qxTmqbx, or are there similar situation like this?

#

Ah! I found the issue

hard vigil
#

there are similar situations, we have three payments in total and the other two are: pi_3SXH1KIVVMDlU7tY2Ck1G0g6 & pi_3SXHQlIVVMDlU7tY2nFozDoA

haughty mauve
#

acct_1SVq8oIVVMDlU7tY was only connected in live mode, so the event will only be sent to the live mode Webhook endpoint. This means that events of test mode object will not be sent to test mode endpoint.

Other successful event delivery from acct_1KddClHiBurE4sHW was connected in both test and live mode, so the events can be delivered to test mode Webhook endpoints

hard vigil
#

Ahaa that is very interesting. Thank you for the explanation.

#

Is it in any way possible for you to connect acct_1SVq8oIVVMDlU7tY to our platform account in test mode as well please?

#

or if we can do it

haughty mauve
#

We generally recommend to use different accounts for testing purpose to avoid the situation mentioned https://docs.stripe.com/connect/webhooks:

For Connect webhooks, your development webhook URLs receive only test webhooks, but your production webhook URLs receive both live and test webhooks. This is because you can perform both live and test transactions under a production application.

If you really want to have the account connected to test mode as well, I'd recommend checking with Support https://support.stripe.com/contact whether this is possible and how it can be done. This channel is for technical integration questions, and we don't have necessary expertise in this matter.

hard vigil
#

Okay I understand! Thank you so much for all the help.
What is the best way for me to use this conversation as context to support when I contact them? Just a screenshot of your explanation of what has happend?

#

Need to log off now, thanks for the help!

haughty mauve
#

You can save the link of this Discord and include it in your conversation to the Support