Section 609.893 creates a service-fraud offense and a facilitation felony

Subdivision 1 covers obtaining service. The State must prove that the accused obtained telecommunications service for personal use, did so through fraudulent means, and intended to evade a lawful charge.

Subdivision 2 covers facilitation. Clause (1) applies when a person makes information or a telecommunications device available—or offers or advertises to do so—in order to help another person violate subdivision 1.

Facilitation clause (2) applies when a person makes, assembles, or possesses a telecommunications device designed or adapted to violate subdivision 1 or to conceal from a service provider or lawful authority the existence, place of origin, or destination of telecommunications service.

The distinctions are important. Subdivision 1 requires service for the accused’s own use and value controls the offense level. Subdivision 2 focuses on assistance or a specialized device and is always a felony with a five-year maximum.

A person who shares account information may be investigated under the facilitation clause even without personally using the service. A person who uses a service may face subdivision 1 without manufacturing a device.

The complaint should identify the subdivision, device or information, service, provider, user, alleged fraud, intent, dates, and value. Generic terms such as “phone hacking” or “service theft” do not substitute for statutory elements.

The statute dates to 1990 and uses broad but defined communications terminology. Modern applications must still fit the enacted definitions rather than assume every internet-related activity qualifies.

What counts as telecommunications service

Minn. Stat. § 609.892 (2026) supplies the controlling definitions for sections 609.892 and 609.893.

Telecommunications service is a service offered for money that transmits messages, signals, facsimiles, or other communications between physically separated persons by telephone, telegraph, cable, wire, fiber-optic cable, or projected energy without a physical connection.

The definition can cover voice calls, certain data transmission, messaging, facsimile, wireless communications, fiber service, and other paid transmission. It does not automatically cover every information product, locally stored file, device function, or free internet service.

The service must be exchanged for pecuniary consideration. A free public service, promotional access, open network, or service included without a separate charge raises different questions, though a paid account or provider loss may still exist.

Transmission must be between physically separated persons. A local device function without communication may fall outside the definition. Automated systems and machine communications require analysis of the service actually provided.

The term applies when the service originates in Minnesota, ends in Minnesota, or both. Provider location alone is not the test. Call-detail records, network logs, account information, and endpoint evidence can establish the connection.

“Information services” appears in the title, but the operative subdivision uses the defined term telecommunications service. A charging theory should be based on the statutory text, not the caption alone.

Providers, Minnesota connection, and a lawful charge

A telecommunications provider is a person, firm, association, or private or municipal corporation owning, operating, or managing facilities used to provide telecommunications service.

Traditional telephone companies fit, but the definition is not limited to them. Wireless carriers, municipal systems, fiber providers, and other entities may qualify if they operate or manage covered transmission facilities.

The service-fraud charge requires intent to evade a “lawful charge.” That phrase matters. The State should identify the tariff, contract, rate, fee, usage charge, or other legally enforceable amount allegedly avoided.

Billing error, unauthorized add-on fees, mistaken roaming, unclear contract terms, service credits, promotional periods, and consumer disputes can undermine the claim that the charge was lawful and intentionally evaded.

Nonpayment after receiving an accurate bill is not automatically fraud in obtaining service. The State must prove fraudulent means used to obtain the service and intent to evade the lawful charge.

A provider may adjust, waive, reverse, or compromise charges. That can affect value and evidence but does not automatically erase or establish criminal intent at the time of use.

Provider records should establish the customer, service plan, charge method, usage, endpoint, fraud flag, and calculation. A collections balance may include taxes, penalties, equipment costs, or unrelated charges that do not equal the statutory service value.

Obtaining telecommunications service for one’s own use

Subdivision 1 expressly says “for the person’s own use.” The prosecution must connect the accused to the obtained service, not merely to a device or account associated with someone else.

Own use can include personal calls, messages, data transmission, or communications undertaken for the accused’s purposes. Whether business use through a personally controlled scheme qualifies depends on facts and ordinary meaning.

Account ownership does not always identify the user. Family plans, employer accounts, shared devices, guest access, forwarded calls, hotspots, and compromised credentials can attribute usage to the wrong person.

Device possession also is not conclusive. A phone, modem, router, server, or software account may be used remotely, loaned, sold, or controlled by multiple people.

The State should prove when service was obtained. An unsuccessful attempt, blocked connection, configuration test, or intercepted request may not establish completed service, though attempt law can be considered.

The service must be obtained by fraudulent means. A customer who lawfully receives service and later disputes payment presents a different case from a person who uses false credentials or manipulates billing at the outset.

Usage records require technical interpretation. A session record may reflect background traffic, automatic updates, failed attempts, network registration, or another linked device rather than conscious communication by the accused.

What “by any fraudulent means” requires

The statute does not list every fraudulent method. Common allegations can involve false identity, stolen account numbers, deceptive activation, manipulated billing, unauthorized access devices, cloned credentials, altered equipment, or misrepresentation to provider systems.

Fraud implies deception or dishonest evasion, not simply breach of contract. The State should identify the act, statement, code, device, or concealment that caused service to be provided without the lawful charge.

An access device is a card, plate, code, account number, or other means of account access usable alone or with another device to obtain telecommunications service.

A credit-card number has a specialized definition involving a card or plate issued by a telecommunications supplier that permits service on credit. It is not necessarily the same as an ordinary bank-payment-card number in every provision.

Use of another person’s account can be fraudulent when unauthorized. Permission, household practice, employer policy, delegation, and reasonable belief matter. A billing-account dispute should not be converted into fraud without proof.

Technical circumvention can be evidence, but modification alone is not enough. Diagnostic tools, privacy configurations, open-source telephony software, testing environments, network-address translation, and ordinary security features have lawful uses.

The complete transaction should show how the provider was deceived, what service resulted, and what charge was avoided. A suspicious device without a service event may support a facilitation theory but not necessarily completed subdivision 1 fraud.

Intent to evade a lawful charge

Subdivision 1 requires a specific purpose: evading a lawful charge. Mistake, inability to pay, confusion over a plan, or accidental connection does not automatically satisfy that element.

Intent may be inferred from concealment, repeated credential changes, false account information, altered identifiers, instructions, avoidance of billing controls, admissions, or continued use after a clear warning.

Other facts can support good faith: provider authorization, a trial period, promotional terms, support guidance, unclear billing, shared-account permission, immediate correction, or a reasonable belief that service was included.

A device’s capability does not prove the user’s intent. Software can mask location or encrypt traffic for privacy and security. Dual-use tools require evidence of actual purpose and context.

Financial motive is not the same as intent. Wanting cheaper service, searching for discounts, or facing debt does not prove fraudulent evasion.

Statements to provider investigators or police can become central evidence. An attempt to explain technical conduct without records may produce inaccurate admissions about configuration, knowledge, or use.

The timing of intent matters. A customer can form an intent to evade after initially lawful activation, but the State must connect that intent and fraudulent means to service actually obtained.

Making devices or information available to help another

Subdivision 2(1) applies when a person makes a telecommunications device or information available to another, or offers or advertises to do so, in order to facilitate the other person’s subdivision 1 offense.

Because an offer or advertisement is enough, a completed transfer or completed service fraud may not be required. The State must still prove the purpose to facilitate another’s intentional evasion of lawful charges.

“Information” can include codes, account details, configuration instructions, methods, credentials, or technical directions. Ordinary public information is not automatically criminal; purpose and connection to service fraud matter.

Online posts, marketplace listings, chat messages, videos, and private groups can be evidence. Context should distinguish technical education, security research, repair, interoperability, or legitimate resale from an offer to facilitate fraud.

Making available can occur without payment. The statute does not require profit. Compensation, volume, secrecy, customer instructions, and after-sale support may strengthen the State’s inference.

A person who unknowingly forwards bad information or sells an ordinary device does not necessarily have the facilitation purpose. Knowledge of the buyer’s intentions and the seller’s instructions matter.

Accomplice liability and facilitation are not identical. Subdivision 2 directly criminalizes specified conduct and provides its own felony penalty.

Devices designed or adapted for telecommunications fraud

The statutory “telecommunications device” definition is unusually broad. It includes an instrument, apparatus, equipment mechanism, operating procedure, or code designed or adapted for a particular use that is intended or can be used to violate section 609.893.

Examples listed in the definition include computer hardware, software, programs, email systems, voicemail systems, identification-validation systems, private branch exchanges, and other means of facilitating service.

Subdivision 2(2) covers making, assembling, or possessing a device designed or adapted to violate subdivision 1 or conceal service from a provider or lawful authority.

Dual-use technology creates hard questions. Routers, servers, PBX systems, caller-identification tools, VPNs, diagnostic software, emulators, test equipment, and code can serve legitimate purposes.

The State should prove design or adaptation, not merely capability. Configuration, modifications, documentation, file names, instructions, sales descriptions, communications, test results, and actual use can be relevant.

Possession can be actual or constructive. A device in a shared office, cloud repository, vehicle, or home requires evidence of knowing dominion and control.

Making or assembling can occur through code development, configuration, combining components, or modifying equipment. Ordinary repair or research is not automatically criminal without the statutory connection.

Concealing service, origin, or destination

Subdivision 2(2) also reaches a device designed or adapted to conceal from a provider or lawful authority the existence or place of origin or destination of telecommunications service.

This language is not a general ban on privacy or anonymous communications. The device must fit the statutory definition and the facilitation provision’s connection to telecommunications fraud.

Caller-identification management, encryption, VPN use, proxies, forwarding, private exchanges, and number masking all have lawful uses. Context, design, adaptation, accompanying instructions, and service billing matter.

A provider may itself offer privacy features or permit network configurations that obscure internal endpoints. Authorized use cannot be treated as concealment from that provider without further proof.

Origin and destination can refer to technical routing, calling numbers, endpoints, accounts, or locations. Expert testimony should explain what the device actually changes and what records remain.

Lawful authority includes government actors acting with legal power, but the statute should not be read to criminalize every privacy measure that makes surveillance harder. The charged device must be designed or adapted as the clause requires.

Overstatement is a risk. Marketing language such as “anonymous,” “private,” or “untraceable” can be evidence, but technical examination should verify function rather than rely on slogans.

Provider records, devices, code, and digital attribution

Evidence can include subscriber records, service agreements, billing, call-detail records, session logs, authentication events, device identifiers, network routing, fraud alerts, support tickets, payments, and account changes.

Provider records often identify an account or device, not the human user. Family sharing, employer systems, resold equipment, compromised credentials, remote access, and spoofed identifiers require investigation.

Devices and software should be collected and examined forensically. Hash values, imaging notes, configuration files, source code, compiled versions, timestamps, and test conditions help establish integrity and function.

Code is not self-explanatory. A function capable of bypassing billing may be dormant, a research tool, a compatibility feature, or part of provider-approved testing. Experts should examine actual execution and context.

Modern voice-over-internet-protocol systems create another attribution problem. A call may pass through a private branch exchange, session-border controller, cloud platform, reseller, or forwarding service before reaching the recipient. The displayed calling number, source internet address, account owner, and person who initiated the communication may therefore be four different things. A technically sound investigation should identify which record was created at each stage and whether the provider can reliably connect it to a particular device and user.

Session Initiation Protocol records also require care. Registration can show that a credential or endpoint contacted a server, but it does not necessarily prove that the accused placed a completed call, received paid service, or intended to avoid a charge. Network-address translation can cause many devices to share an external address. Dynamic addresses change. Virtual machines and remotely administered systems may operate far from the subscriber. Clock settings, time zones, retention practices, and provider-side normalization can materially affect any timeline.

Provider fraud scores and automated alerts are investigative leads, not substitutes for proof. Their underlying rules may be proprietary, may change over time, and may flag legitimate travel, unusual calling volume, newly activated equipment, or privacy settings. The defense should seek the alert criteria, raw events, later account notes, and evidence of false positives rather than accepting the provider’s conclusion at face value.

Advertisements and messages should be preserved completely. Selected phrases can misrepresent sarcasm, technical support, warnings, or permitted uses.

Value evidence should separate telecommunications service from devices, taxes, equipment financing, penalties, and unrelated account charges.

Search warrants for devices, cloud accounts, and communications must satisfy probable cause and particularity. Technical investigations can expose privileged and unrelated data requiring careful review.

Service value, aggregation, and penalties

For subdivision 1 service fraud, value above $2,500 carries up to ten years in prison and a $20,000 fine. Value above $500 through $2,500 carries up to five years and $10,000. All other cases are misdemeanors carrying up to 90 days and $1,000.

The value should reflect services fraudulently obtained, not every balance on the account. Provider testimony and billing data should explain units, rates, discounts, credits, and the charged period.

Amounts under one scheme or course of conduct may be aggregated, whether they involve one credit-card number or several. The State must identify the common scheme and prove each included transaction.

Aggregation can transform misdemeanor allegations into a felony. Transactions outside the alleged scheme, lawful service, duplicate records, failed attempts, equipment costs, and recovered charges should not be added automatically.

Facilitation under subdivision 2 is separately punishable by up to five years and $10,000. Its penalty does not depend on proving more than $500 in service value.

The current Minnesota Sentencing Guidelines severity table ranks subdivision 1 at level 2 for $2,500 or less and level 3 above $2,500. Facilitation is level 2.

Restitution under Minn. Stat. § 611A.04 (2026) requires proof of qualifying loss caused by the offense. Offense value and restitution can differ.

Minnesota appellate proof principles

There is little modern published Minnesota appellate authority construing each phrase of section 609.893. The current statutory text and definitions therefore deserve close attention.

Intent, user identity, and device purpose are often circumstantial. In State v. Al-Naseer, 788 N.W.2d 469, 474–80 (Minn. 2010), the Minnesota Supreme Court explained that a circumstantial-evidence conviction “warrants heightened scrutiny.”

In State v. Andersen, 784 N.W.2d 320, 329–31 (Minn. 2010), the court stated that the circumstances proved must be consistent with guilt and “inconsistent with any rational hypothesis except that of guilt.” These cases did not involve section 609.893 but govern Minnesota circumstantial-evidence review.

A rational innocent explanation may include account permission, provider error, automatic traffic, shared credentials, legitimate testing, ordinary privacy use, or a dual-use device. It must be grounded in the record.

Federal telecommunications cases may use different statutes and definitions. They should not displace Minnesota’s own “telecommunications service,” “device,” and intent language.

A technical fact is not a legal conclusion. Experts can explain routing and device function; the factfinder must decide the statutory elements.

Related criminal and civil provisions

Financial-transaction-card fraud under Minn. Stat. § 609.821 (2026) may apply to unauthorized card or account conduct.

Computer theft, unauthorized computer access, identity theft, ordinary theft of services, cellular telephone counterfeiting, and facilitating access to a security system can overlap depending on the facts.

Minn. Stat. § 237.73 (2026) permits a provider representative or harmed person to seek an injunction and discontinuance of telephone service when a section 609.893 violation is occurring or threatened.

Civil termination of service is not a criminal conviction. Provider contracts, collections, regulatory remedies, and criminal prosecution use different standards.

Federal charges can include wire fraud, access-device fraud, computer offenses, and identity theft. Jurisdiction and elements differ.

Multiple Minnesota counts arising from one behavioral incident may implicate Minn. Stat. § 609.035 (2026) at sentencing.

Defense issues in telecommunications-fraud cases

No covered service. The product may not be paid transmission between physically separated persons or may lack a Minnesota origin or endpoint.

No lawful charge. The amount may be unauthorized, waived, disputed, miscalculated, or outside the agreement.

No fraudulent means. Nonpayment, billing error, or contract breach alone is not the deception the statute requires.

No intent to evade. Permission, a promotion, misunderstanding, provider guidance, automatic connection, or good-faith dispute can create reasonable doubt.

Not the user. Account, subscriber, IP, or device evidence may not identify the person who obtained service.

No facilitation purpose. Information or equipment may have been provided for repair, research, privacy, education, interoperability, or another lawful use.

Dual-use device. Capability is not necessarily proof that a device was designed or adapted for fraud or concealment.

No knowing possession or control. Shared systems, cloud repositories, and workplaces complicate constructive possession.

Inflated value or improper aggregation. The State may count equipment, duplicate sessions, lawful use, taxes, or unrelated accounts.

Unlawful search. Device and account searches may exceed a warrant or lack particularity.

What to do after an accusation or provider referral

Stop disputed use and do not test the device or account. Further activity can change logs and create new allegations.

Preserve devices, code, configurations, bills, provider messages, support tickets, service agreements, payment records, and complete communications.

Do not wipe, factory-reset, reprogram, disassemble, sell, or discard equipment. Do not alter source code or compile a new version over the old one.

Prepare a privileged chronology for counsel identifying users, permissions, provider contacts, configurations, service events, charges, payments, advertisements, and transfers.

Do not ask customers, coworkers, or account holders to delete messages or give a common explanation. Do not access provider systems to gather evidence.

You may decline a voluntary interview and request counsel. Technical explanations should be based on preserved records, not stressful memory.

Early counsel can secure provider logs, arrange a forensic image, test equipment under controlled conditions, challenge value, and identify the exact subdivision at issue.

Frequently asked questions about Minnesota telecommunications fraud