A point release, not a reset
The GSMA has published SGP.32 v1.3, the latest version of the remote SIM provisioning standard built for IoT. It landed on 28 May 2026 alongside a matching SGP.31 v1.3 architecture update, and a day after a refreshed eUICC PKI Certificate Policy v2.3. For anyone deploying connected fleets, the headline is reassuringly dull: this is a refinement of the standard, not a reset, and it does not change what you should be specifying today.
The clearest structural move in v1.3 is alignment. The specification now references SGP.31 v1.3 for architecture and pulls its consumer baseline up to SGP.22 v2.7, keeping the IoT standard in step with the wider eSIM ecosystem it borrows from rather than drifting away from it. There are functional refinements too. One concrete example: v1.3 formalises the handling of Emergency Profiles, the profiles tied to eCall and emergency connectivity, which earlier implementations could reject outright. Academic for most telemetry deployments, but exactly the kind of gap that matters for automotive and safety-critical kit.
Why the version number should not change your order
Here is the part worth being blunt about. Formal GSMA certification for eUICC chips, eIM platforms and SM-DP+ servers is still issued against v1.2. That makes v1.2, not v1.3, the version that guarantees interoperability between certified components today. A hardware design or platform choice made against v1.2 is production-grade; one made against an uncertified reading of v1.3 is not. The sensible posture is to keep specifying v1.2-certified kit, ask vendors which version they are certified against rather than merely compatible with, and treat v1.3 as the roadmap. The moment to watch is not the publication date but the point where test specifications and certification catch up to v1.3.
We have covered the standard itself before, in our profile of the British engine behind SGP.32, Kigen. For readers who want the technical detail, the reference site SGP32.co.uk has published a full breakdown of what changed in v1.3, and, if you are new to the standard, a clear explainer on what SGP.32 is and why it matters.
In one line: SGP.32 v1.3 is out, it tidies and realigns the standard rather than overturning it, and until certification moves with it, v1.2 remains the version to build and buy against.
