#runefarer
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Do you have any example payment intent IDs I could review?
Sure, just a question - is it secure to share live account payment intent IDs on Discord?
Yes, only people with access to your Stripe account and Stripe staff with specialized permissions can use them
pi_3NqHu3BDew7xQiBS1rcpeC8D
Thanks, taking a look
Okay I see a payment_intent.succeeded event associated with this PI.
It was sent to 6 webhook endpoints
Here is where you can find it: https://dashboard.stripe.com/events/evt_3NqHu3BDew7xQiBS1qc0hS0x
We only have 3 endpoints configured with live
I can only see 3 hosted endpoints enabled, and the one we have with our test environment didn't receive the webhook.
Is it a setup issue?
I see all webhook endpoints associated with this event are Connect related. But event delivery was successful to all of them
Under Developers > Webhooks, we've configured 3 hosted endpoints.
Those are the ones we want to receive events on, and generally do. I just added the third one recently for our test environment.
we_1LAryuBDew7xQiBSRq3JBLlH
That endpoint was updated today. What was changed?
We have it disabled because we don't want the test environment getting live events. We're careful to only setup live with our test environment only when absolutely necessary, and then immediately tear it down.
Once testing will be done, I'll disable the endpoint again.
Okay well the last modification occurred 4 minutes after the event was generated.
So it is possible this webhook endpoint just missed this event
No, I enabled it more than an hour ago and didn't touch it afterwards.
Sure, thanks for your help. I have just one more question regarding Cash App.
On the frontend we use confirmCashappPayment to confirm the payment intent with handleActions: false and display the QR code ourselves.
Everytime the QR code expires (expires_at) we refresh it by re-fetching the payment intent using retrievePaymentIntent.
Is that implementation correct or should we use some other way of refreshing the QR code?
Because, randomly, we get the following error:
In that case your integration may be making multiple calls to the Payment Intent. This occurs when the object is locked while changes are propagating, to ensure the data returned is accurate. I would recommend reviewing your front-end code and make sure your API calls for the same Intent are triggered sequentially
I double checked, only one call is made every 30 or so seconds (depending on the expires_at).
We don't access the payment intent anywhere else, only get information through the webhook events.
I'll triple check, maybe there's some React magic happening in production build that I'm missing...
Hmmm .. ๐ค
React hooks do have a way of triggering code more often than expected. Adding some logging around the API calls might be a good approach to identifying this.
We avoid hooks as much as possible, but I see your point. I'll take a look.
Thanks for your help!
It's good to know that webhooks will work properly, as no one has touched or will touch the prod endpoint in forever. And that our implementation is at least okay in theory.
Thanks again!
Happy to shed what ๐ก I can ๐