MNP in Spain

Under EU law, all Mobile Virtual Network Operators (MVNOs) are required to support mobile number portability, enabling users to retain their phone number when switching service providers. In Spain, the mobile number portability process is regulated by the Administración de Operadores de Portabilidad Móvil (AOPM), which defines a standardized and regulator-approved workflow for all participating operators.

The primary objective of Mobile Number Portability (MNP) is to reduce friction for consumers and businesses when changing providers, removing the need to notify contacts of a new phone number. This framework promotes healthy competition among telecom operators while ensuring continuity of service. For businesses, retaining an established number is critical for maintaining customer relationships and brand identity, while individuals benefit from uninterrupted personal communication.

Port-Out Rules and Cancellation Policy

In Spain, port-out cancellations can only be initiated by the Recipient operator. The Donor operator is not permitted to cancel a port-out directly. However, the MNP workflow includes a scenario known as “Cancellations started by donor network”. This applies when the Donor is unable to perform the port-out, in which case the Donor may contact the Recipient and request that the Recipient initiates the cancellation.

Once a port request is confirmed, it becomes locked at 2:00 p.m. on the business day prior to the scheduled porting date. After this lock time, cancellation is no longer possible.

Following a cancellation, users have 30 days to submit a new port-out request. By default, port-out requests should be scheduled for the earliest possible available date, unless explicitly specified otherwise.

Processing Time Windows and Responses

The Spanish MNP process operates within two daily processing windows:

• 08:00 a.m. – 02:00 p.m.
• 02:00 p.m. – 08:00 p.m.

If a port request is submitted before 02:00 p.m., the Donor operator may send a response during the next processing window (02:00 p.m. – 08:00 p.m.).

While port requests can technically be submitted at any time (Spanish local time), correct handling and enforcement of these timeframes is managed by the AOPM system.

If the Donor does not send a response within the allowed timeframe, the port request is automatically rejected by AOPM with the status AREC and the status cause RECH_NORES (No Response).

Confirmed ports are locked at 02:00 p.m. on the business day prior to the scheduled porting date, after which no further cancellations or modifications are permitted.

MNP Lifecycles

MNP-IN

Porting Lifecycle

Draft : The porting request is initially created in this status. All required information can be added or updated before the request is submitted for further processing.

Pending : The request moves to Pending once validations are completed. At this stage, the request is sent to the donor service provider for acceptance.

Scheduled : The request enters the Scheduled status once it is accepted by the other service provider and a porting date/time is scheduled. The scheduled date represents when the actual porting activity is planned to occur.

While in this status, cancelation requests can be raised. All cancelation requests must comply with the defined deadline rules.

Processing : The request moves to Processing when the scheduled porting date/time is reached. Active provisioning and technical porting activities are executed during this phase, and changes or cancelations are no longer allowed once Processing has started.

Completed : The porting request is marked as Completed once the process has been successfully finalized by both the recipient and donor service providers.

Cancelation Requested : The customer may request cancelation while the request is in Draft or Scheduled.

• If the request is received before it is sent to the donor service provider during Draft or before provisioning begins while Scheduled, the porting request will be canceled.

Rejected : If validation fails or the donor service provider rejects the request while in Pending status, the porting request transitions to Rejected.

Canceled
The porting request has been canceled by the recipient.

MNP-OUT

Porting Lifecycle

Pending : The MNP-Out (Port-Out) process begins when the donor receives the Port-Out request from the regulator in the Pending state. During this state 1GLOBAL will perform typical validations and requests from the partner to accept or reject (typically, the partner shall accept by default for prepaid cases). If all validations pass, the request will transition to a Agreed state or become Rejected due to a data mismatch.

Scheduled : Request was accepted and is waiting for the recipient service operator to start the portability process. Recipient service operator can cancel the request at any time AND the request will be Canceled status.

Processing : The recipient service operator will start the portability process on the agreed date.

Completed : The porting request is marked as Completed after successful de-provisioning.

Canceled : The portability request was canceled by the recipient service operator.

Rejected : If validation fails, porting request transitions to Rejected status.

Rejection Reasons

During the Mobile Number Portability (MNP-ES) process, a porting request may be rejected if certain validations fail or if specific business rules are not met. Each rejection is associated with a reason and a descriptive message (if available), which helps partners understand the reason for the rejection and take corrective action if applicable.

The rejection reasons are summarized in the table below:

Required Customer Data

Personal Account

• First Name
• Last Name
• Address
• Email
• Service Provider
• Contract Type (Prepaid/Postpaid)
• Contract Number
• Identity document (Passport/NIE/NIF)
• MSISDN
• Porting Date
• ICCID (Required for Prepaid contract type)

Business Account

• Company Name
• Business Address
• Billing Address ( if different from Business Address)
• Service Provider
• Contract Number
• Identity document (CIF)
• MSISDN
• Porting Date
• ICCID (Required for Prepaid contract type)

API endpoints

Endpoints were added as Mandatory and Optional. The reasoning for this clustering is explained as follows:

• Mandatory means they are part of the MNP core process and without them, it is not possible to go through the process from the start until the end.
• Optional means they are available to be considered by the Partner to enable specific business, customer service processes supporting the MNP process.