A recent SIM change is context worth checking.

Where a SIM-swap signal can help

Consider the question when an existing customer starts an account-recovery flow, changes a sensitive account setting, or is about to rely on an SMS code. A recent SIM change may be a reason to add another verification step under your own risk policy. It is one signal, not a complete identity or fraud decision.

What QuietPass supports today

sim_swap is an optional check in QuietPass’s API contract. Network supply is not connected, so requests currently receive an unavailable result rather than a SIM-change finding. No paid SIM-swap check is executed in this release.

{
  "phone": "YOUR_VERIFIED_NUMBER",
  "checks": ["sim_swap"]
}

Check status and reason before applying any decision rule. A successful HTTP response can still contain an unavailable check.

Coverage and approval come before live access

SIM-swap availability is specific to the country, carrier, supplier, and approved use case. QuietPass requires business and use-case review before a live-service trial. Trial scope and terms will be presented before it starts; paid access requires explicit activation.

Our coverage page and New Zealand coverage response show the current connected state. They do not promise future carrier availability.

How it differs from other phone checks

Validation checks numbering rules. Line type classifies a number. Carrier lookup resolves the serving network. A SIM-swap signal addresses a different event and should retain its own availability, freshness, and interpretation.

Background: CAMARA SIM Swap API project. This explains the general signal; it does not certify QuietPass coverage or supplier connectivity.