Instant Phone Verification
The mobile operator issues a signed credential confirming phone number ownership into the subscriber's wallet — replacing SMS one-time codes with a reusable, cryptographic proof that any service can verify.
Today
Enter Number Again
The user re-types a phone number each time a service needs a phone-number control check or step-up verification.
30–90 secWait for SMS OTP
A one-time code is sent over SMS and may be delayed, blocked, or mistyped.
15–60 secRepeat Per Service
Each relying party runs the same verification loop again instead of reusing a prior cryptographic assertion.
1–3 minWith Wallet-Based Credentials
Operator Issues Credential
After operator-side checks and enrolment, the customer receives a signed credential for phone-number control in the wallet.
Present Proof from Wallet
The user presents a verifiable proof of phone-number control without waiting for a fresh OTP each time.
Verify Reusable Assertion
The service verifies issuer trust, validity, and proof integrity, then continues the journey with fewer repeat phone-number control checks.
Today
- 1
Enter Number Again
The user re-types a phone number each time a service needs a phone-number control check or step-up verification.
30–90 sec - 2
Wait for SMS OTP
A one-time code is sent over SMS and may be delayed, blocked, or mistyped.
15–60 sec - 3
Repeat Per Service
Each relying party runs the same verification loop again instead of reusing a prior cryptographic assertion.
1–3 min
With Wallet-Based Credentials
Operator Issues Credential
After operator-side checks and enrolment, the customer receives a signed credential for phone-number control in the wallet.
Present Proof from Wallet
The user presents a verifiable proof of phone-number control without waiting for a fresh OTP each time.
Verify Reusable Assertion
The service verifies issuer trust, validity, and proof integrity, then continues the journey with fewer repeat phone-number control checks.
What changes
Fewer details shared · More verified directly · Less manual checking
Why It Matters
Operators and digital services are looking for stronger, lower-friction ways to verify phone-number control. GSMA Open Gateway signals market demand around number verification APIs, while wallet-based credentials suggest a plausible future path toward reusable proofs in selected journeys.
GSMA Open Gateway — Number Verification APIWhat to Think About First
Lower OTP Dependence
Reusable cryptographic proof can reduce reliance on repeated SMS challenges in flows where wallet acceptance is available.
Minimal Attribute Sharing
The verifier can receive proof of phone-number control without needing broader subscriber or account data.
Operational Readiness Matters
Issuance, trust onboarding, revocation, and verifier acceptance all need implementation work before the model can run at scale.
Want to explore how this applies to your context?
Whether you are evaluating, piloting, or scaling wallet-based identity — let's discuss what makes sense for your organisation.
Prefer LinkedIn? Message me there .