The code wasn't detected

When an SMS arrives, we pull the verification code out of it and show it front and centre. Usually that's exactly right. When we're not confident, we'd rather show nothing than guess — and the full message is always there.

Read the full message#

Open the order and read the SMS itself. Every message the order receives is kept, newest first, exactly as it arrived.

Why a code might not be picked out#

The detector looks for a 4–8 digit code next to words like "code", "verification", "OTP", "PIN" or "passcode", and understands formats like 123-456, 123 456 and G-123456. It deliberately skips things that look like phone numbers, prices, dates and years. It may come up empty when:

• the message contains a link to tap instead of a code;
• the code contains letters and the message doesn't clearly label it as a code;
• the message has several numbers and none is clearly the code.

If the highlighted code looks wrong#

Trust the message text. If the service sent more than one code — after a resend, say — the most recent message is usually the one that counts, and that's the code the console highlights.

In the API#

An order's code is null when nothing was detected. The messages array always includes each message's full body, so you can apply your own parsing if you need to.