#hendr1x_api

1 messages ¡ Page 1 of 1 (latest)

pallid shoreBOT
open canopyBOT
#

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.

pallid shoreBOT
#

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

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

radiant cradle
#

Hello, is this after you confirm the intent client-side?

broken scaffold
#

yes

radiant cradle
#

In that scenario typically the webpage will try to tell the server that the payment succeeded and the server will retrieve the intent to confirm that. It is also important to listen to the payment_intent.succeeded webhoook event as it is possible for a payment to succeed but for the user's connection to cut out before it can reach the server, so the event provides redundancy and can prevent scenarios where you charge the user without knowing

broken scaffold
#

I'm not clear what webpage vs server means in your description.

pallid shoreBOT
radiant cradle
#

Are you more familiar with the term "backend" for server here? Or is this a general confusion on the concept of client-server?

#

Happy to explain either way, I just want to make sure I understand what you need clarification on

broken scaffold
#

I am familar

#

I can't tell if you are are talking about my servers or yours

radiant cradle
#

I am talking about your server, how to make sure your server knows that a payment has succeeded

broken scaffold
#

ok

#

so you are saying accept the status response from your server and also listen to webhooks

#

Can I please have more information about how to listen to webhooks

radiant cradle
broken scaffold
#

These are data feeds that are pushed from your server correct?

#

I'm not seeing anything about how to register a url with your system

#

ok...I see it

#

Is there a difference between the webhook approach and me doing a retrieve from my side?

radiant cradle
#

Data-wise no, the main difference is that your server might not know to do a retrieve at all under certain circumstances. An classic example is if the customer is on a train and they hit the pay button on your site, the payment goes through but then right before your webpage can reach our to your server the train goes through a tunnel and their connection drops. In that scenario the payment happened successfully but your server doesn't know because it didn't receive a signal from the client. If the server is also listening to webhook events, we will send an event about the successful payment and your server can process the successful payment when it receives that

broken scaffold
#

got

#

got it

#

Ok. Thank you for explaining