You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the provided $returnURL is accessed, the booking is marked as "Paid" and a confirmation email is sent.
However, it seems that sometimes SumUp will access this URL twice, at basically the same time, resulting in the customer receiving two confirmation emails (despite a check on if it's already been marked as paid).
Is this an issue on SumUp's side that is causing this duplicate callback to the $returnURL?
The text was updated successfully, but these errors were encountered:
Did you find a way to avoid that double call? I exactly have the same problem right now. That return_url webhook is called twice instantly, making it complicated to handle with asynchronous functions.
I may be wrong, but I think I did implement a workaround by calling the SumUp API when the confirmation page loaded, to instantly get the payment status meaning the payment got logged as paid at my end, before SumUp even made the double webhook call. I've since switched to Stripe.
I use the following to perform a checkout on my site:
When the provided
$returnURL
is accessed, the booking is marked as "Paid" and a confirmation email is sent.However, it seems that sometimes SumUp will access this URL twice, at basically the same time, resulting in the customer receiving two confirmation emails (despite a check on if it's already been marked as paid).
Is this an issue on SumUp's side that is causing this duplicate callback to the
$returnURL
?The text was updated successfully, but these errors were encountered: