# Spain registration
The following registrations are available for Spain.
## Sender ID registration
All alphanumeric sender IDs used to send SMS messages to Spanish mobile numbers (\+34) must be registered in the CNMC (Comisión Nacional de los Mercados y la Competencia) National Alias Registry. Unregistered sender IDs cannot deliver messages to Spanish recipients. Your Spain sender ID registrations are case-sensitive at the carrier level. The exact casing that you register with CNMC must match what you submit through the AWS End User Messaging console.
Starting September 15, 2026, unregistered alphanumeric sender IDs will be blocked by Spanish mobile operators and will not deliver messages to Spanish recipients. Generic sender IDs that do not clearly identify your business are not permitted by CNMC and cannot be registered.
Dedicated phone numbers (local long codes or short codes, international toll-free numbers) are not affected by this regulation and do not require registration.
**Important**
New Spain short code provisioning is temporarily on hold. If you need a dedicated number for Spain, request a long code instead. For more information, see [Dedicated phone numbers for Spain](https://docs.aws.amazon.com/sms-voice/latest/userguide/dedicated-number-spain.html).
The CNMC registration portal requires authentication with a valid digital certificate. The following certificate types are accepted:
+ A qualifying digital certificate issued by the Spanish government
+ An eIDAS-compliant qualified digital certificate issued by one of the EU countries listed below
Qualifying EU countries for eIDAS certificates: Austria, Belgium, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, and Sweden.
If you do not have a qualifying digital certificate issued by the Spanish government or by one of the qualifying EU countries listed above, you have two options:
**Option A: Appoint a representative and register your sender IDs**
You must appoint a representative in Spain or a qualifying EU country who holds a valid digital certificate. The representative must also have an apostilled notarized power of attorney authorizing them to act on your behalf. We recommend engaging legal counsel to advise on the process for appointing an authorized representative.
**Option B: Switch to dedicated phone numbers for Spain**
Dedicated phone numbers (local long codes, international toll-free numbers) are not affected by this regulation and do not require CNMC registration. Note that new short code provisioning for Spain is temporarily on hold; request a long code instead. You can request a dedicated phone number for Spain through the [AWS End User Messaging console](https://console.aws.amazon.com/sms-voice/home). For more information, see [Dedicated phone numbers for Spain](https://docs.aws.amazon.com/sms-voice/latest/userguide/dedicated-number-spain.html). For registration processing timelines, see [Registration processing times](https://docs.aws.amazon.com/sms-voice/latest/userguide/registration-eta.html).
After you submit your registration at the CNMC portal, CNMC sends a verification email to the representative email address you provided. You (or your representative) must then log into the portal with the qualifying digital certificate and approve the registration within 10 business days.
If you registered your sender ID with multiple downstream providers, you may receive a separate verification request for each provider.
To complete your Spain sender ID registration, you must:
1. **Create a Spain sender ID registration in the AWS console** – Start the registration process in the [AWS End User Messaging console](https://console.aws.amazon.com/sms-voice/home) by creating a new Spain sender ID registration. This generates the TERCERO (third party) details you will need when registering in the CNMC portal. **Do not submit the AWS registration form yet** – you will complete and submit it in step 3 after your CNMC registration is done.
1. **Register your sender ID in the CNMC National Alias Registry** (directly or through an appointed representative) – Go to [https://tramites.cnmc.gob.es/formulario/213/](https://tramites.cnmc.gob.es/formulario/213/) and authenticate with your valid digital certificate. During registration:
+ Select each of our downstream SMS providers as **PRO** (Registered Provider of Origin) using the details provided in the AWS console in step 1:
CNMC Portal Name
Provider
SINCH COMMUNICATIONS SPAIN, S.L.
Sinch
VONAGE, B.V.
Vonage
Twilio Ireland Limited
Twilio
+ For the **TERCERO** (Third Party) field, enter the details provided in the AWS console.
+ Select the alias relationship type that applies to your sender ID.
**Important**
The TERCERO legal representative information is sensitive and you may not use this information for any other purpose than to register your sender ID for Spain. Do not retain this information after you have submitted your registration in the CNMC portal. Use the AWS console as your reference if you need to access these details again for a new registration.
After submission, approve the CNMC verification notification within 10 business days.
1. **Submit the AWS sender ID registration form** – Return to the registration you created in step 1 in the [AWS End User Messaging console](https://console.aws.amazon.com/sms-voice/home), complete any remaining fields, and submit. This informs our downstream SMS providers of your registration. See the procedure below for step-by-step instructions.
1. Open the AWS End User Messaging console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Registrations**, choose **Create registration**.
**Note**
If you already created a registration when requesting the origination identity, use that existing registration form.
For **Registration form name**, enter a friendly name.
Choose **Next**.
1. In the **Sender ID info** section, enter the following:
+ For **Sender ID**, enter the sender ID to register. The sender ID must be between 3 and 11 alphanumeric characters. The value you enter must use the exact same casing as your CNMC registration. For example, if you registered "MyBrand" with CNMC, you must enter "MyBrand"—not "MYBRAND" or "mybrand." The AWS End User Messaging console displays sender IDs in uppercase. However, the downstream partner stores the exact casing that you entered at submission time.
Choose **Next**.
1. In the **Alias relationship type** section, select the type that matches how you established the right to use this sender ID:
+ **OEPM/EUIPO trademark** – The alias is a registered trademark with the Spanish Patent and Trademark Office (OEPM) or the EU Intellectual Property Office (EUIPO).
+ **OEPM trade name** – The alias is a registered trade name with OEPM.
+ **Commercial Register company name** – The alias matches the company name in the Spanish Commercial Register.
+ **Red.es/ICANN domain** – The alias corresponds to a domain registered with Red.es or an ICANN-accredited registrar.
+ **Other public registry** – The alias is registered in another official public registry.
+ **Legitimate habitual use** – The alias has been in legitimate habitual use by the holder.
Choose **Next**.
1. In the **Alias holder information** section, enter the following:
+ For **Holder type**, select **PF** (natural person) or **PJ** (legal entity).
+ For **Tax ID**, enter the holder's NIF or CIF.
+ For **Legal name**, enter the holder's full legal name or company name.
+ For **Surnames**, enter the holder's surnames. This field is required for natural persons (PF) only.
Choose **Next**.
1. In the **Representative information** section, enter the following:
+ For **Representative type**, select the type of representative.
+ For **Tax ID**, enter the representative's NIF or CIF.
+ For **Name**, enter the representative's name.
+ For **Surnames**, enter the representative's surnames.
+ For **Email**, enter the email address for CNMC verification notifications.
+ For **Phone – optional**, enter a contact phone number.
**Note**
If you do not have a qualifying digital certificate issued by the Spanish government or by one of the qualifying EU countries listed above, the representative must be your appointed representative with a valid digital certificate and apostilled notarized power of attorney.
Choose **Next**.
1. If the representative is a company, complete the **Person acting for company representative** section with the individual's details.
Choose **Next**.
1. In the **Company info** section, enter the following:
+ For **Company Name**, enter the name of your company as officially registered.
+ For **Tax ID**, enter your company's tax identification number.
+ For **DBA (Doing Business As) – optional**, enter any trade name your company uses.
+ For **Company website**, enter the URL for your company's website.
+ For **Area of business**, describe your company's industry or sector.
Choose **Next**.
1. In the **Company address** section, enter your company's registered address.
Choose **Next**.
1. In the **Contact info** section, enter the contact details for the person managing this registration.
Choose **Next**.
1. In **Messaging Use Case**, do the following:
+ For **Use case category**, choose the category that best describes your messaging use case.
+ For **Use case description**, provide additional context about how you will use this sender ID.
+ For **Monthly volume**, enter the estimated number of messages you plan to send per month.
+ For **Opt-in workflow**, describe how recipients consent to receive your messages.
Choose **Next**.
1. In **Message samples**, do the following:
+ For **Message Sample 1**, enter an example SMS message body that will be sent to your end users.
+ For **Message Sample 2 – optional** and **Message Sample 3 – optional**, enter additional example messages if needed.
Choose **Next**.
1. On the **Review and submit** page, verify the information you are about to submit is correct. To make updates, choose **Edit** next to the section.
1.
**Important**
Do not submit this form until you have completed your sender ID registration in the CNMC portal. You must register your sender ID with CNMC before submitting the AWS form.
Choose **Submit registration**.
+ [CNMC Registration Portal](https://tramites.cnmc.gob.es/formulario/213/)
+ [CNMC FAQ – Gestión del Registro de Alias](https://sede.cnmc.gob.es/tramites/telecomunicaciones/gestion-del-registro-de-alias)
+ [AWS End User Messaging console](https://console.aws.amazon.com/sms-voice/home)
+ [Dedicated phone numbers for Spain](https://docs.aws.amazon.com/sms-voice/latest/userguide/dedicated-number-spain.html)
+ [Registration processing times](https://docs.aws.amazon.com/sms-voice/latest/userguide/registration-eta.html)
+ [AWS Support](https://console.aws.amazon.com/support/home)
## Dedicated number registration
Registering a dedicated number is the first step in creating an origination identity.
**Important**
New Spain short code provisioning is temporarily on hold. If you need a dedicated number for Spain, request a long code instead. For more information, see the long code request process.
To request a long code phone number, see the long code request process.
Follow these directions to register your dedicated number in Spain.
**Complete Common Dedicated Number registration form**
1. Open the AWS End User Messaging console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Registrations**, choose the registration number to complete.
**Note**
If you already created a registration when requesting the toll-free number then you can use that registration form.
1. In the **Company info** section, enter the following:
+ For **Company Name**, enter the legal name of your company.
+ For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT).
+ For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company.
+ For **Company website**, enter the full URL of your company website.
Choose **Next**.
1. In the **Company Address** section, enter the following:
+ For **Address 1**, enter the physical street address associated with your company.
+ For **Address 2**, enter the unit number of the physical address, if applicable.
+ For **City** enter city where the physical address is located.
+ For **State / Province (optional)**, enter the state, province, or region where the physical address is located.
+ For **Postal code (optional)**, enter the postal code / ZIP code where the physical address is located.
+ For **Country code**, enter the two-digit ISO country code where the physical address is located.
Choose **Next**.
1. In the ** Service Information and Use Case** section, enter the following:
In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users.
+ For **Service name**, Name of your SMS service or feature.
+ For **Use case category**, select the category which most closely aligns with your use case.
+ For **Use case description**, enter a description of your use case for sending SMS messages with this long code..
+ For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month.
+ For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound).
+ For **Opt-in Method**, enter a how the user will opt-in..
+ For **Opt-in method other**, ff you chose Other, please explain.
+ For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service..
+ For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location.
+ For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service.
+ For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location.
+ For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service.
+ For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location.
Choose **Next**.
1. On the **Review and submit** page verify the information you are about to submit is correct. To make updates choose **Edit** next to the section.
1. Choose **Submit registration**.