#_webhooks

1 messages ¡ Page 1 of 1 (latest)

exotic pebbleBOT
#

👋 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/1283423866038780041

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

  • _api, 7 hours ago, 5 messages
vast glacier
#

1/ Yes, you should listen to webhook events to receive real-time updates on what's going on with the payment

2/ Not sure what you mean by that.. Can you elaborate?

3/ There are no guarantees about when the webhook event will arrive. It is delivered as soon as possible but there is no specific time we commit. This is because webhook events are delivered asynchronously.

halcyon meadow
#

  1. Further clarification on #2.
    Is it supported behavior to have both return_url and webhook enabled?

  2. Further clarification on the intent of my question #3

If I have both webhooks and return_url enabled, I was wondering if it is possible to set them to be staggered so that the order fulfillment doesn't happen overlapping, or if there is a guide in case they happen at the same time.

vast glacier
#

2/ both are independent of each other. Return URL is used on the client-side (after the payment is completed). Webhook event is delivered server-side. Ideally, both will be triggered for a payment assuming you're listening to webhook events

#

I don't believe we have any guides for it. Essentially, you can choose to prioritize whatever is delivered first.. You can have a column in your DB that tells you if the order has been fulfilled or not.

So you can check your database when you receive a callback on return URL or webhook endpoint to see if the orders have been fulfilled or not.

exotic pebbleBOT
halcyon meadow
#

In your example, are you saying that the way to add a DB column is to record information like payment_intent_id and design it so that if a duplicate request occurs, it will skip the later request if the already processed information is recorded in the DB?

timid cipher
#

Exactly, that kind of thing could help prevent duplicate orders