OTP was entered correctly but rejected
In a small number of cases, a customer insists they entered the correct code but Cartsaver rejected it. The possible reasons are finite and each is quick to test.
Other verification problems are covered in the COD OTP and WhatsApp troubleshooting guide.
1. Has the code expired?
Section titled “1. Has the code expired?”A Cartsaver verification code is valid for 10 minutes from when it’s sent, and that limit can’t be changed. In Cartsaver Logs, compare the time the code was sent with the time of the customer’s attempt. If more than 10 minutes passed, the code has expired and the customer needs a fresh one.
The Sent At column on the OTP Verification tab of Logs shows when each code went out:

Fix: ask the customer to tap “Resend” for a fresh code. See Code limits for the built-in limits.
2. Too many tries in one minute
Section titled “2. Too many tries in one minute”- Cartsaver checks up to 5 code entries per minute for the same phone number or email. Further tries in that minute get a “Please wait” message.
- A wrong entry doesn’t lock the code. After the wait, the same code still works until it expires.
Fix: ask the customer to wait a minute and enter the code again, or request a new one. This limit is built in and can’t be changed (see OTP channels).
3. Did the customer use a different number?
Section titled “3. Did the customer use a different number?”Cartsaver matches the code to the phone number on the order, not to the device the customer types on. Some customers use more than one WhatsApp number and may read the message on one device while entering the code on another. The code then belongs to a different number and is rejected.
Fix: confirm with the customer that they’re using the same number they entered at checkout.
4. Accidental whitespace
Section titled “4. Accidental whitespace”- A copy from WhatsApp sometimes includes a leading or trailing space, which can register as a different value.
- Cartsaver trims input automatically in recent versions; if a customer reports this after a browser or keyboard update, ask them to type the code manually.
5. Relying on auto-verify
Section titled “5. Relying on auto-verify”- If Auto-verify is enabled but the customer tapped the link in a different browser session (with another account logged in), the automatic verification can silently fail.
- Manual code entry should still work as a fallback.
6. Transient network issue
Section titled “6. Transient network issue”Bad network on the customer’s side can cause a successful submission to look like a failure.
Fix: ask them to retry on a different network, or after a few seconds.
What if many customers report it at once?
Section titled “What if many customers report it at once?”When several customers report rejected codes in a short window, the cause is probably not on their side. Look in Cartsaver Logs for a pattern, such as the same country, provider or template, and tell the support team right away, because it may be an incident at Cartsaver or at a message provider.
See Contact support.
