A2P SMS, OTP, and sender ID rules in Germany.
BroadNet delivers A2P SMS and OTP in Germany over direct connections to Telekom Deutschland, Vodafone Germany, and Telefónica O2; sender IDs need no formal pre-registration with BNetzA. Direct termination into Telekom Deutschland, Vodafone Germany, and Telefónica O2 with GDPR-aligned operations from Frankfurt PoP.
From-rates by channel in Germany
- SMSfrom$0.0800per SMSIndicative list rate, reviewed September 24, 2026Volume pricing available
- OTPRequest a quote Channel list rate from $0.0120 per verification (all markets)
- WhatsAppRequest a quote Channel list rate from $0.0135 per template message (all markets)
- RCSRequest a quote Channel list rate from $0.0080 per session (all markets)
- VoiceRequest a quote Channel list rate from $0.0150 per minute (all markets)
Indicative list prices in USD, excluding taxes and sender-ID registration fees. Final per-operator pricing is confirmed in your quote.
The Germany A2P market at a glance.
Germany is EU tier-1 — 108M subscriptions across Telekom Deutschland, Vodafone Germany, and Telefónica O2. BNetzA (Bundesnetzagentur) regulates electronic communications and actively blocks high-fraud senders; the Telekommunikationsgesetz (TKG) sets the wider framework. GDPR governs all recipient PII with double-opt-in the operator-preferred standard for marketing. Numeric senders are preferred for transactional traffic; alphanumeric is allowed but operators prefer the numeric form for PSD2-SCA flows. German is the working language for consumer-facing templates.
Technical facts for Germany
Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).
| Mobile country code (MCC) | 262 |
|---|---|
| Dialling code | +49 |
| Operators (MCC-MNC) |
|
| SMS length, GSM-7 (Latin alphabet) | 160 characters in a single SMS; 153 per part when concatenated |
| SMS length, UCS-2 (Arabic, Cyrillic and other scripts) | 70 characters in a single SMS; 67 per part when concatenated |
| Regulator | BNetzA (Bundesnetzagentur) |
| Sender-ID rules | Alphanumeric sender IDs allowed but numeric preferred for transactional. GDPR opt-in mandatory for marketing. |
| Sender-ID lead time | Free-form (numeric preferred) |
Channels live in Germany.
One contract, one contact model. Fall back between SMS, WhatsApp, and Voice with shared opt-in evidence and a single audit trail.
SMS
Operator-direct A2P to Telekom, Vodafone, and Telefónica O2. Numeric sender preferred for transactional.
OTP
Sub-3-second median; PSD2-SCA-grade reliability across all three operators.
WhatsApp Business API live; growing share for customer-care and re-engagement traffic.
RCS
RCS Business Messaging available via Google MaaP on enabled handsets across all three operators.
Voice
Voice OTP and TTS available; PSD2-grade audit trail.
How do I register a sender ID in Germany?
Filed end-to-end by BroadNet's compliance team — KYC pack, operator approval, and renewal cycles handled on your behalf.
BNetzA / operators · Telekom, Vodafone, Telefónica O2
- Format
- Alphanumeric (up to 11 chars) or numeric long-code. Numeric preferred for transactional.
- Pre-registration
- No formal BNetzA registration; operator white-listing per brand on a continuous basis
- KYC documents
- Handelsregister entry (HRB number), VAT (USt-IdNr.) number, traffic-type declaration, GDPR processing-basis declaration
- Renewal cycle
- Not required — continuous use once white-listed
- Common rejection causes
- Brand-impersonation risk on generic financial / shipping terms, missing GDPR processing-basis on the white-list form, marketing senders without double-opt-in evidence, or alphanumeric senders for PSD2-SCA flows (numeric strongly preferred).
What OTP delivery looks like in Germany.
Latency profile, peak-hour behaviour, recommended fallback chain, and the fraud signals our firewall watches in-market.
Typical latency window
Median 2.3s with p95 inside 5s on Telekom, Vodafone, and Telefónica O2. PSD2-SCA-grade two-shot OTP delivery confirmed via DLR.
Peak-hour behaviour
Throughput holds steady through the working week. Operator firewall is strict on category drift; numeric senders for transactional clear faster than alphanumeric.
Fallback chain
Recommended chain: SMS (primary, numeric for PSD2) → Voice OTP after 25s no-DLR → WhatsApp Business OTP as low-friction alternative. PSD2-SCA audit trail retained for 13 months.
Fraud signals we watch
SIM-swap attempts on PSD2-SCA flows are the dominant signal. Number-rented OTP harvesting and robocall-style voice OTP abuse watched in parallel. BNetzA actively blocks confirmed high-fraud senders.
What you can — and can't — send.
Opt-in, opt-out, quiet hours, content restrictions, and the penalty regime for the Germany market.
Opt-in
GDPR + DSGVO double-opt-in is the operator-preferred standard for marketing. Consent source, timestamp, and channel logged per-recipient; opt-in confirmation link timestamp retained.
Opt-out
STOP keyword honoured network-wide. One-step opt-out, irreversible until re-consent. Required wording in German.
Quiet hours
We have not found a regulator-published time-of-day window for promotional SMS in this market. Agree sending hours with the operator and schedule promotional sends for the recipient's local daytime; transactional traffic runs 24/7.
Content restrictions
Brand-impersonation policed by operator firewall. PSD2-SCA flows must use a dedicated transactional sender ID separate from marketing. Templates flagged against fraud heuristics pre-send.
Regulator penalties
BNetzA can fine for breaches of TKG and the UWG (Gesetz gegen den unlauteren Wettbewerb). GDPR penalties stack on top — up to 4% of global turnover for the underlying data-processing violation.
Termination,
network by network.
The route status column shows how each operator is reached — a direct BroadNet bind or a labelled partner route. No grey-route exposure. Route grades are indicative planning guides, not live measurements.
| Operator | MCC-MNC | Route status | Grade | A2P rate (typ.) |
|---|---|---|---|---|
| Telekom Deutschland | 262-01 | Direct | A+ | EUR 0.0776 |
| Vodafone Germany | 262-02 | Direct | A+ | EUR 0.0756 |
| Telefónica O2 | 262-07 | Direct | A+ | EUR 0.0736 |
Rates shown are typical pay-as-you-go for transactional traffic. Promotional traffic is priced separately, and volume tiers reduce both. See the rate-card section below for the full ladder.
| Tier | Transactional | Promotional | Notes |
|---|---|---|---|
| Pay-as-you-go | EUR 0.074 | EUR 0.085 | List rate up to 100K messages/month |
| Growth · 100K+ | EUR 0.065 | EUR 0.075 | Auto-tier discount |
| Volume · 1M+ | EUR 0.054 | EUR 0.063 | Includes quarterly route review |
| Enterprise | Custom | Custom | Direct operator pricing + signed SLA |
Free-form alphanumeric; numeric preferred for transactional. No formal registration.
Open the Germany rate cardCompliant
by default.
Every send is pre-screened against Bundesnetzagentur (BNetzA) rules, the operator firewalls, and the local privacy framework. Where registration is required, BroadNet files the paperwork on your behalf.
GDPR + TKG enforced. Double opt-in for marketing (DSGVO). BNetzA actively blocks high-fraud senders.
Full regulatory deep-diveGDPR + DSGVO
Double opt-in for marketing. Records retained per German law.
Numeric preferred
Alphanumeric allowed but numeric sender preferred for transactional in DE.
BNetzA blocking
BNetzA actively blocks high-fraud senders.
Programmes that work well in Germany.
Where the BroadNet operator-direct footprint, the local regulator regime, and consumer messaging habits line up.
- 01
B2B SaaS account onboarding, MFA, and operational alerts.
- 02
PSD2-SCA OTP and banking transaction alerts under BaFin guidance.
- 03
E-commerce shipment and click-and-collect notifications (Zalando, Otto, About You-style flows).
- 04
Mobility and ride-hail itinerary updates with multilingual templates (DE + EN).
- 05
Healthcare appointment reminders aligned with TKG telemedicine rules and patient-data confidentiality.
What we run for Germany senders.
The operator relationships, the compliance workflow, the routing position — all on a single contract and a single account team.
Frankfurt PoP with EU-resident data plane — GDPR-aligned operations and PSD2-SCA-grade audit trail retained for 13 months.
Operator-direct binds with Telekom, Vodafone, and Telefónica O2 — numeric senders preferred for transactional applied automatically.
Brand white-listing handled per-operator in 3–5 business days; no formal BNetzA registration step.
Double-opt-in capture and DSGVO-aligned consent-evidence retention built into the contact model.
EUR billing with USD also available; automatic volume tiers from 100K messages a month.
BNetzA fraud-block monitoring with proactive sender-rotation if a brand gets caught in a hard-block sweep.
Buyer questions about Germany.
The questions BroadNet's sales engineers field every week from teams shipping into this market.
Can I send marketing SMS in Germany without prior consent?
No — GDPR requires opt-in and the operator-preferred standard is double-opt-in (the recipient confirms the opt-in via a link or reply). BroadNet's contact model captures and retains the consent source, timestamp, and channel, plus the confirmation timestamp.
Should I use a numeric or alphanumeric sender for OTP?
Numeric is strongly preferred by the German operators for transactional and PSD2-SCA flows — faster clearance, fewer firewall flags. Alphanumeric is allowed but better suited to non-transactional categories. BroadNet's onboarding sets numeric for transactional automatically.
How long does operator white-listing take?
3 business days for a numeric sender, 5 business days for alphanumeric. There's no formal BNetzA registration — white-listing happens at the operator level on a continuous basis.
How long do I need to retain opt-in evidence?
GDPR doesn't set a hard retention floor, but operator-audit and BNetzA enforcement practice favour retention for the life of the marketing relationship plus 3 years. PSD2-SCA audit trail is retained for 13 months separately.
Is RCS Business Messaging available?
Yes — RCS is live on all three operators via Google's MaaP. Verified-sender RCS is recommended for high-trust brands. BroadNet handles the verification onboarding.
What happens if BNetzA blocks my sender?
BNetzA actively blocks high-fraud senders. BroadNet's monitoring catches a hard-block at the operator edge and rotates the sender within the hour, with a notification to your account manager. Root-cause analysis is included in the incident report.
Where does my recipient PII sit?
Inside the EU-resident data plane (Frankfurt PoP). Recipient MSISDNs and message bodies do not leave the EEA without a documented legal basis (e.g. SCCs). The GDPR compliance pack is available on signed-NDA request.
A ready-to-adapt template for Germany.
In the local script alongside English. Copy, swap the brand, and we'll register it as part of your sender-ID onboarding.
- Mobile subscribers
- 108M
- Sender ID lead
- Free-form (numeric preferred)
- Time-to-launch
- Live in 5–15 business days from test-access request to production
- Billed in
- EUR / USD
Your verification code is 471829.
Ihr Verifizierungscode lautet 471829.
Alphanumeric sender IDs allowed but numeric preferred for transactional. GDPR opt-in mandatory for marketing.
Continue across the region.
See how enterprises put these operator-direct routes to work in banking and finance messaging and e-commerce and retail messaging, or weigh the options on the messaging platform comparison hub.
More on Germany
Request current route availability for Germany.
Live in 5–15 business days from test-access request to production. Sender ID filed with BNetzA on your behalf. Billed in EUR from day one.
$ curl -X POST https://api.broadnet.me/sms/sendSms·mno = +49