#zelfrost_webhooks
gusty fossilBOT
👋 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/1471077303365799937
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
charred chasm
Can you share the pi_xxx ID for a payment where the .succeeded event should have been fired/sent?
echo pilot
Hello, I’m a developper at Resamania2, and we think we have some issues on receiving webhooks and how to check that in your dashboard. When I access the workbench on the webhooks part, it looks like the last event we received for any of our test environment (dev, rc0x, etc) is yesterday at 10:43 am.
But we sent transactions today, which went fine, and we received no events
Yes
pi_3SzZaXGZjKOKD6M71INgbWsl
charred chasm
I'm guessing you're the Connect platform in both those payments? acct_1JX5Z4LanmA9Pcv3
echo pilot
Yes
charred chasm
pi_3SzZaXGZjKOKD6M71INgbWsl
evt_3SzZaXGZjKOKD6M71MH63Xvr is the payment_intent.succeeded event for this PI. We sent it to a number of Connect webhooks
But they're all different URLs/endpoints to the other event
So this looks like some kind of account configuration issue?
charred chasm
`evt_3SzZaXGZjKOKD6M71MH63Xvr` is the `payment_intent.succeeded` event for this ...
Was sent to various fitnesspark.app and resamania.com endoints – all different to the stadline.tech endpoints for the other one
echo pilot
What sort of url? This is a test transaction on a development platform, so the events should be send to platforms like api.dev.resa2.stadline.tech, api.rc02.resa2.stadline.tech, et
Oh
These are production environments
charred chasm
What sort of url? This is a test transaction on a development platform, so the e...
I think you need to look at the webhook endpoints you have configured on the account then
echo pilot
But this transaction is supposed to be on our test environment
charred chasm
But this transaction is supposed to be on our test environment
Yep, can happen:
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. We recommend that you check the livemode value when receiving an event webhook to determine whether users need to take action.
echo pilot
When I look at the workbench, I can’t find the event id you send, neither in live or in test mode, do you have any idea why?
charred chasm
Trying to understand why we didn't send the event to both though 🤔
charred chasm
When I look at the workbench, I can’t find the event id you send, neither in liv...
Because the event exists on the connected account, not your platform. That is how direct charges work
echo pilot
I don’t understand, so I’m able to access this connected account (ends in KD6M7), see the transaction (the id I sent above), but I can’t see the related events and where they have been sent? Or am I missing something?
Sorry I’m just trying to understand why our transactions from the last 2 days received no webhooks on our test platform. Does this mean we are using an invalid account or something?
charred chasm
Trying to understand why we didn't send the event to both though 🤔
As stated, I'm looking into it. Patience please
charred chasm
I don’t understand, so I’m able to access this connected account (ends in KD6M7)...
Not sure why that is. I suspect because although it's a test mode payment/object, the event was only sent the live mode endpints for reasons I explained above. But I'd expect the event to still be sent to test mode endpoints, which is what I'm trying to figure out
OK, that explains it. acct_1NmvYUGZjKOKD6M7 is only connected to your platform in live mode, so we send all events (live and test) to the live mode endpoints only. The other account, which the desired/expected behaviour (acct_1KA9qKPtiR5KEdep) is only connected in test mode. This diagram explains it:
@echo pilot does that clear things up? You need to establish a connection between that account (and others?) with your platform in test mode