We've observed that Clover takes close to 10mins to update us if Payment for an Order has been completed. We get the Order message ASAP, but Payment takes a long time. Any fix to this?
Clover takes a long time to send an update between Order(O:123455) and Payment (P:12345678) to our Webhook
There is so much spam on this forum that I probably won't see your response.
You haven't provided a lot of details. There can be a lot of time between the creation of an order and payment of that order.
Is this an order you are creating?
"We get the Order message ASAP"
What order message? Order CREATED?
"Payment takes a long time. Any fix to this?"
Are you determining this based on another webhook? As I said above, an order can be created ane not be paid for for quite sometime depending on the scenario. So unless you are creating the order and paying for it immediately there probably is not a problem.
Is this an order you are creating? - No, it's an order users are making through our merchants (store). The events are sent to use through our webhook.
What order message? Order CREATED? - yes ORDER CREATED. The structure of order created event is like this -> (O:12345678) with the "O" standing for "Order created" followed by the order ID. We are only processing orders with payment successfully status, which is a different ID event structure, this time it's -> (P:12345678) with the P standing for Payment, followed by the payment ID.
So the issue is, through our webhook, we get the Order Created event immediately after a transaction has been made to our merchant, so we get "O:12345678" event type of order immediately. But sometimes Clover takes a long time, roughly 10-12 minutes to process the payment perhaps and send us through our webhook a Payment successful event - "P:12345678". Sometimes, it drops immediately but at times it takes 10-12 minutes or even more.
We have checked if it is a problem with how we process the payment in our webhook, but we have confirmed and 100% seen that it is indeed a Clover problem.
Is it that clover's infrastructure doesn't cater to this on their webhook or handle high traffic spikes? How do we address this.
Welcome to the
Clover Developer Community
10 People are following this question.
