#hammad-shahzad_webhooks

1 messages · Page 1 of 1 (latest)

hollow stirrupBOT
#

đź‘‹ 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/1231798166387429416

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

silver runeBOT
scenic isle
#

What do you mean by "cancelled"? Are you still receiving Webhook events?

smoky jasper
#

Hi there,

We’re still having trouble sending requests in live mode to a webhook endpoint associated with your Draft SC account. Stripe sends webhook events to your server to notify you of activity in your Stripe account, such as a completed payout or a newly-created invoice.

The URL of the failing webhook endpoint is: https://pipelinevolleyball.com/?wc-api=wc_stripe

You (or someone on your team) configured your Stripe account to send events to that URL. You can change your account’s webhook endpoints from the Dashboard.

In most cases, a failing webhook does not impact your payments or payouts. However:

If you use subscriptions we rely on your webhook endpoint to notify you of new invoices. These invoices may be delayed for up to three days if your endpoint is unable to successfully receive them.

If you use Checkout and rely on the checkout.session.completed event as part of your purchase fulfillment process, you should review your completed payments to ensure you have fulfilled all recent purchases.

We’ve attempted to send event notifications to this endpoint 2,132 times since the first failure on April 15, 2024 at 4:42:09 AM UTC. If this endpoint is important to your application, please try and fix the issue. If you do not need this webhook endpoint, you can remove it from your Stripe webhook settings. We will stop sending event notifications to this webhook endpoint by April 24, 2024 at 4:42:09 AM UTC.

Here is the summary of errors we received while attempting to send webhook events:

2,113 requests had other errors while sending the webhook event.

#

19 requests timed out. Make sure your server quickly responds to acknowledge receipt of the webhook event. Whenever possible, use asynchronous patterns and defer processing the event until after responding to Stripe with a successful HTTP status code.

You need to return any status code between HTTP 200 to 299 for Stripe to consider the webhook event successfully delivered.

For more details on these errors and to review your account’s recent activity, you can find the full set of events and request logs on the Dashboard.

This email is the last time we’ll reach out to you before disabling the webhook.

For more in-depth information on how to use webhooks, we recommend reviewing our documentation.

Yours,

The Stripe team

scenic isle
smoky jasper
#

Sure

#

Thanks for coming

#

acct_1MscHyGkvYWAILZY

#

is this?

scenic isle
#

Yes! Looking into it now

smoky jasper
#

Main issue is my client have subscription auto renews on nights of 15,16 and 17 but they go in draft

#

Instead of auto renews

#

And getting these emails

#

In starting their subcription was coming from website like they fill form they pay and their subscroption started but later my client deleted them and made new subscription so i think there is nothing to do with website

#

But getting these issues

scenic isle
#

With reference to https://dashboard.stripe.com/webhooks/we_1OCeHeGkvYWAILZYgF903Jag, your Webhook server responded error 400 to Stripe.

When your server don't respond to 200 status code for multiple days in a row, the Webhook endpoint will be disabled: https://docs.stripe.com/webhooks#disable

I'd recommend checking why your server returned error 400 to Stripe

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

Receive Stripe events in your webhook endpoint

Listen to events in your Stripe account on your webhook endpoint so your integration can automatically trigger reactions.

smoky jasper
#

Even we made fresh subscription is it still connected with form ?

#

As we did make the subscription directly from stripe

#

not from wordpress

#

if website not involved why webhook making issues

scenic isle
#

Who is handling the code of Webhook server? Is it your own server or wordpress?

#

Webhook server is independent from website or API

smoky jasper
#

May i know exactly webhooks work?

#

I think we only need them when we are connecting with website

#

But if we are making subscriptions from stripe

#

without using any website or anything

#

Why it's giving error and invoices are going in draft on 15,16,17 which we set the subscripton auto renews direcly from stripe

#

You can see these two entries

scenic isle
#

Checking this in_1P66w9GkvYWAILZYFGaC5Y2e

smoky jasper
#

Please use the correct webhook signing secret, which should start with "whsec_".

When i am adding this getting this error

image.png
#

In gravity form

#

Do you know why?

#

and whsec what kinda webhooks are these?

scenic isle
#

whsec_ is a Webhook Secret. It can be found by clicking "Reveal" under "Signing scret" in the Webhook page

image.png
smoky jasper
#

I have updated how can i test it?

#

Are they working now?

scenic isle
#

As of now, I don't see successful delivery yet. However, I don't know the timestamp when the changes have been made to your config. I'd recommend monitoring this page

smoky jasper
#

ok thanks i will keep checking to it