All updates
Breaking

MNP Netherlands & Spain – Porting Support and Contract Enhancements and Removal of unsupported fields

·By ksanchez

MNP Netherlands & Spain

Mobile Number Portability (MNP) has been introduced for both the Netherlands and Spain, enabling users to seamlessly port their MSISDN both into and out of the network. With this release, customers in these markets can now migrate existing mobile numbers from other operators (port-in) as well as transfer their numbers to external providers (port-out), ensuring full number portability support.


MNP Netherlands

Breaking changes ⚠️

  • Portings: Additional fields have been added to porting-related contracts to ensure clearer separation and prevent specification mappings from being incorrectly associated with other objects during end-to-end (E2E) flows. Introduced timestamp fields for lifecycle states applicable to both port-in and port-out:

    • pending_at for the Pending status
    • processing_at for the Processing status

Non-Breaking changes

  • New Webhooks for Porting:
    To support the agreed status for port-out requests in the Netherlands, a new webhook has been introduced to notify downstream systems when a port-out reaches the agreed state.

MNP Spain

Non-Breaking changes

  • Subscribers:
    Adds an identifications object to support richer subscriber identity data. This is primarily used for KYC and portability requirements.

    • Identification types for Spain:
      • NIE (Número de Identificación de Extranjero)
      • Tax Id (Número de Identificación Fiscal)
      • Passport (existing identification; optional nationality field added)

Removal of unsupported fields from Phone Number schema

Non-Breaking Changes

Removed the port_out_expires_at field from the Phone Number schema when the status is terminated, as this field was not part of the contract definition.