THE LINUX FOUNDATION PROJECTS

Number Recycling

API Description
Use Cases
  • Secure Authentication and OTP Delivery: Helps prevent OTPs, verification codes, or login links from being sent to a new holder of a recycled number. Before using a stored phone number for authentication, the application can check whether the number has changed subscriber since it was linked to the account.
  • Account Recovery and Password Reset: Reduces the risk of account takeover when phone numbers are used as a recovery channel. If the number has been recycled since the user registered or last verified it, the service can trigger step-up verification or request an alternative recovery method.
  • Sensitive Customer Communications: Helps ensure that alerts, notifications, appointment reminders, transaction messages, or personal information are not sent to the wrong recipient after a number has been reassigned. This is relevant for sectors such as banking, healthcare, insurance, eCommerce, utilities, and public services.
  • Customer Data Accuracy and Compliance: Supports organizations in keeping customer records up to date by identifying phone numbers that may no longer belong to the intended user. This helps reduce privacy risks, misdirected communications, failed delivery, and potential regulatory exposure.

See also at GSMA:

Benefits
  • Enhanced Account Security: Reduces the risk of account takeover by detecting when a stored phone number may no longer belong to the original user.
  • Reduced Misdelivery of sensitive Information: Helps prevent OTPs, recovery links, alerts, and personal messages from reaching the new holder of a recycled number.
  • Improved Customer Data Quality: Enables businesses to identify outdated or risky phone numbers before relying on them for authentication or communication.
  • Lower Operational and Support Costs: Reduces failed communications, customer complaints, manual investigations, and remediation work caused by outdated contact data.
  • Privacy and Compliance Support: Helps businesses follow data accuracy and privacy-by-design principles by reducing the likelihood of contacting the wrong recipient.

API Portfolio: Authentication and Fraud Prevention

Sub Project Wiki: Know Your Customer
(incl. how to meet the team)

API Wiki: Number Recycling

API Repository: Number Recycling

API Repository Status: Sandbox

API Status: In progress

API Version(s) and Release Date(s):

  • v0.1.1 (06.05.2025), Spring25 meta-release
  • v0.2.0 (11.09.2025), Fall25 meta-release

API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today