WPIntell

Source evidence

different orders using the same Kustom session

Kustom Checkout for WooCommerce · support · 2026-03-13T13:47:00+00:00

complaintsentiment
highseverity
0.82relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 28 rows with source links

7.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
hungpham unresolved
If a customer places an order with a slow network, it might take a little time for completing payment. Then if the customer clicks to the payment button again, another new order will be created, but because Kustom is holding one session for a while, the new order will be created with the same Kustom session. Then Kustom doesn’t know which order needs to be finalized. It ends up to fail both. Should the plugin detect and allow only one order in one Kustom working session? Hi, To clarify, do you mean the customer hits “Pay order”-button again before the Kustom modal even appears, or does it happen later in the process? It would also be helpful to know if you’ve identified why the server is responding slowly in those instancesis it a hosting issue or perhaps a delay in the Kustom response? Could you please verify if there are any error messages in the log? Ensure that no user IDs or credentials are shared publicly.

Comments

1 shown
robinkrokedil 2026-03-16T10:58:00+00:00

Hi, To clarify, do you mean the customer hits “Pay order”-button again before the Kustom modal even appears, or does it happen later in the process? It would also be helpful to know if you’ve identified why the server is responding slowly in those instancesis it a hosting issue or perhaps a delay in the Kustom response? Could you please verify if there are any error messages in the log? Ensure that no user IDs or credentials are shared publicly.