All articles

Treat SMS content as text: leading zeros, spaces, and lookalike characters

The code “004821” becomes “4821” because a developer stored it as a number. That client-side defect can be tested without a real purchase. In an application using SimAggregator, define how message text and the value intended for entry are handled.

Do not extract the first digit sequence merely because it appears first; a message may contain a date, amount, or another number. If parsing is necessary, define supported formats and handling for ambiguity. Retain the original representation in a restricted context only as needed for the task.

Test regular and nonbreaking spaces, line breaks, leading zeros, and visually similar characters. Normalization may help input, but it must not silently change meaning. Users should understand which value they copy, especially if the interface transforms the source.

Synthetic messages let you repeat checks after changes. Distinguish a displayed message, an extracted value, and acceptance by the tested product. Parser behavior alone cannot prove the last outcome. For an unknown format, a clear manual step is better than confidently displaying the wrong code.

Your first number in a minute

Signing up takes a minute, topping up a couple more, and the code arrives in 20 seconds.

Buy a number
No subscription feeCancel with a refund in the first hour