#elio-payment-webhook

1 messages ยท Page 1 of 1 (latest)

mild cliff
#

hello! do you mean payment_intent.created event?

past schooner
#

No, payment.created. It is a connected account webhook.

mild cliff
#

ah thanks for clarifying, are you creating a Destination Charge? that is when that would happen

#

payment.created is the movement of funds from the Platform to Connect account

#

from the Connect account's perspective

past schooner
#

Yes, the destination charge is being created. I want the webhook to be sent to our host.

#

But it is not being sent. The event is shown in the dashboard.

#

This is an example of what we want to receive as a webhook.

mild cliff
#

looking, thanks for sharing Event ID

#

is there a typo in the Event ID? I can't view it

#

or is it an old Event iD?

past schooner
#

No typo. I can view it by clicking the link.

#

Date on page for event: 10/1/21, 5:18:04 PM

mild cliff
#

do you have a newer event? that is way too old of an event so past certain retention things that I can't easily view where the events were sent etc

past schooner
#

I will find one shortly.

tired pewter
#

๐Ÿ‘‹ I'm just hopping in since @mild cliff had to step away - give me a few minutes to take a look

past schooner
#

Thanks

tired pewter
#

How are you trying to listen for this webhook event? Are you listening for it through the CLI, or are you expecting your Connect webhook endpoint to be receiving it?

past schooner
#

Connect webhook endpoint.

tired pewter
#

Gotcha, so your connect webhook endpoint is not currently listening for that specific event type - you'll need to update it through the API and add payment.created as an event type it's listening for (see https://stripe.com/docs/api/webhook_endpoints/update#update_webhook_endpoint-enabled_events)

past schooner
#

Can this be done in the UI?

tired pewter
#

No, unfortunately this webhook event is not available in the UI

past schooner
#

Thank you ๐Ÿ™‚

#

Your documentation doesn't list payment.created as a webhook to listen to.

tired pewter
#

It's not listed, but you should still be able to listen for it if you update your webhook endpoint through the API. I also just want to check - is there a specific reason you need this? We have it unlisted because we expect most integrations to not need it

past schooner
#

Thank you. Yes, I can understand that it really depends on integration. I was more curious to know why I wasn't receiving it. Thank you again.