Skip to main content

​
Finland Number & Sender Rules (Traficom, formerly FICORA)

Finland (FI) sits in Orbit’s regulated number-purchase set, so a Finnish DID order opens only after an approved compliance profile is attached. Traffic into Finland sits under the Information Society Code (laki sähköisestä viestinnästä 917/2014), which carries the country’s ePrivacy and marketing-consent rules, overseen by Traficom, the Finnish Transport and Communications Agency, the regulator formerly known as FICORA. This page expands the FI row of the country-requirements matrix so you can assemble the profile before your first Finnish order. Finland is a tenant-owned burden. Orbit keeps the country-rules reference and the purchase gate; the legal posture is yours.
This page is documentation, not legal advice. The Information Society Code’s direct-marketing provisions are enforced against the sender. Have counsel review your consent practice for Finnish recipients; Orbit supplies the surfaces.

​
Where Orbit gates Finnish number purchases

FI is a member of the platform’s phone_number_purchase regulated set (DE, GB, FR, BR, MX, IN, JP, FI, NL, SE) — the same registry that drives the compliance-profile wizard. For a Finnish order the gate works like this:
1

Create the profile

POST /api/v1/compliance/compliance-profiles with country_code: "FI" and use_case: "phone_number_purchase". The wizard surfaces the Finnish packet: a required business registration certificate (business_doc) and proof of address (address_proof), plus an optional government-issued ID (id_proof). The ID is optional because the carrier’s compound requirement accepts either an identity document or the company registration. The data fields are the business identity block (registered name, registration number, address, contact person, email, phone) plus website and the use-case description with sub-allocation disclosure.
2

Submit and wait for carrier review

Submission fans the bundle to the carrier for review, typically a few business days. The gate opens only on approved. See the KYC Profile Submission Runbook.
3

Order the number

Place the Finnish order with the approved profile attached (compliance_profile_id). Without an approved profile the order gate answers the same 422 as a missing profile (COMPLIANCE_PROFILE_REQUIRED / COMPLIANCE_PROFILE_NOT_APPROVED), and a number bought ahead of approval lands at pending_compliance and cannot originate traffic until the profile is attached and the carrier confirms.

​
Sender registration behavior under Traficom (the FICORA regime)

Finland has never operated a statutory alphanumeric sender-ID registry. The FICORA-era regime, continued by Traficom, concentrates on the confidentiality of communications and on direct-marketing consent in the Information Society Code, not on pre-registering sender strings. Expect the live FI country-rules row to read registration: none:
With no statutory register, the operative layer is carrier deliverability: an unregistered alphanumeric sender can be relabeled in transit, so register the sender identity where stable branding matters, and treat that as posture rather than law. The consent rule: electronic direct marketing to individuals requires prior consent; the B2B exception is narrow. Record consent with sms scope before dispatch, and honor revocations on every channel:

​
Worked phone_number_purchase profile for FI

Attach the trade-register extract as business_doc and a recent address document as address_proof; add the optional id_proof if the carrier asks for the identity branch of its compound requirement.