What to do after a bank referral or police contact

Preserve the original communication with the financial institution. Save call recordings if available, secure messages, online forms, emails, chat transcripts, branch notes, claim confirmations, card-cancellation notices, replacement-card records, and the exact date and time of every report.

Do not edit an earlier message or create a new explanation without preserving the original. A correction can be helpful, but silent alteration can make a routine misunderstanding appear deliberate.

Collect the item history. For checks, preserve the check register, check numbers, order and delivery records, images, carbon copies, stop-payment requests, and any recovered checkbook. For a debit card, preserve card numbers, activation records, mobile-wallet tokens, replacement history, location data, receipts, and transaction alerts.

Write a timeline of when the item was last seen, who had access, when it was reported, when it was found or used, when the bank contacted the customer, and when the customer learned any new fact. Knowledge is assessed at the time of the report.

Do not accuse a family member, employee, merchant, or stranger without a factual basis. False follow-up statements can create additional problems and distract from a defensible original report.

A person contacted by a bank investigator or law enforcement should not guess about dates, transactions, or card possession. It is lawful to obtain counsel before a voluntary criminal interview. Bank account duties and criminal interview rights are separate questions.

Section 609.508 is not a general bank-fraud statute

The statute identifies two covered categories: the person’s blank checks and the person’s debit cards. It identifies two claimed conditions: lost or stolen. And it identifies one recipient category: a financial institution.

The law does not say credit cards, completed checks, cash, account passwords, account numbers, certificates of deposit, wire transfers, loan applications, or every electronic-payment credential. Other laws may govern those subjects, but section 609.508 should not be expanded simply because the conduct involves a bank.

The statute applies whether the customer speaks or writes. A telephone call, branch conversation, online lost-card form, secure message, signed affidavit, email, or chat can supply the communication if it conveys the covered representation.

No bank loss is an express element. The report itself completes the offense if the remaining elements and mental state exist. A bank’s decision to deny the claim or cancel the card before any loss does not necessarily prevent a charge.

No intent to obtain money or defraud appears in the text. Prosecutors may offer motive evidence, but jury instructions should not replace the enacted mental state—knowing or having reason to know the information is false—with a different standard.

What prosecutors must prove beyond a reasonable doubt

A useful element formulation is: the defendant informed a financial institution; the information was that one or more of the defendant’s blank checks or debit cards had been lost or stolen; that information was false; the defendant knew or had reason to know it was false; and the communication occurred at the charged time and place.

The State must identify the item. A vague allegation that someone made a false “fraud claim” does not establish whether the communication concerned a blank check, debit card, credit card, completed check, or unauthorized transaction.

The State must prove what was said. A customer may report a card as compromised and request cancellation without saying the physical card was lost or stolen. A bank employee’s shorthand code should not substitute for the customer’s actual words.

Falsity and mental state are separate. The fact that a card was later found can establish that the original report was inaccurate, but it does not automatically prove the person then knew or had reason to know the report was false.

Identity and authorship can be disputed. Joint accounts, family telephone access, business bookkeepers, online credentials, voice authentication, and branch visits can create proof questions about who made the report.

The communication must be made to a financial institution

Section 609.508 does not supply a special definition within its text. Banks and credit unions are the clearest examples under the phrase’s ordinary meaning. The particular entity’s charter, services, and role should be established when status is genuinely disputed.

A report to a merchant, payment app, police officer, credit bureau, employer, check-verification company, insurance carrier, or card network is not necessarily a report to a financial institution under this statute. Another law may apply, and the communication may later reach a bank, but recipient proof remains required.

Third-party customer-service vendors can complicate the issue. Many banks outsource card support or fraud intake. The defense should identify whether the recipient acted for the institution, what system received the report, and what the customer reasonably understood.

A communication routed through a mobile banking application ordinarily reaches the institution’s process, but native records should show the account, time, content, and recipient. A screenshot alone may omit important fields.

The State should not rely only on the institution’s name. A witness or business record should connect the report to the entity and explain the intake system accurately.

Oral and written statements are both covered

The Legislature expressly included oral and written reports. Telephone calls and branch conversations can therefore be charged even without a signed affidavit.

Oral cases turn on reliable proof. Recorded calls, contemporaneous notes, call disposition codes, voice authentication, employee testimony, and follow-up messages may show what occurred. A summary written later can omit qualifications such as “I may have lost it” or “I cannot find it.”

Written reports include paper forms, email, secure chat, mobile-app submissions, online questionnaires, and perhaps text communications sent through an authorized bank channel. Authorship and completeness must be established.

Preselected form language deserves close review. A customer might click “card unavailable,” while the bank system converts that selection to “lost.” The customer’s input, screen displayed at the time, system mapping, and confirmation page can differ.

Silence is not ordinarily “informing” the institution that an item was lost or stolen. Failure to correct a bank’s assumption may raise other issues, but the State should identify the affirmative communication charged under this section.

The statute refers to the person’s checks or debit cards

The possessive language matters. The report must concern one or more of “the person’s” blank checks or debit cards. The ordinary case involves the defendant’s account and item issued to or owned by that customer.

A parent reporting a child’s card, an employer reporting a company card, an authorized signer reporting a business checkbook, or a spouse reporting a joint-account item can raise whether the item is legally or practically the reporter’s within the statute. Account agreements and issuance records matter.

The State should not assume that access equals ownership. An employee may be entrusted with a corporate debit card but not be the account owner. Conversely, a joint account holder may have a legal interest even if another person’s name appears on a particular card.

Agency principles can matter to the institution’s operations, but penal statutes are applied to enacted language. When a case falls outside the obvious individual-account setting, counsel should preserve a statutory-construction argument.

The possessive requirement also distinguishes reporting someone else’s stolen checks to help that person. A good-faith third-party report is not the conduct the statute describes.

What “blank checks” means in this statute

A blank check is generally an unused check not yet completed for payment. A missing checkbook, unissued check stock, or a group of numbered checks can fit the ordinary meaning.

A completed and delivered check is different. Reporting that a payee altered an amount, a signature was forged, or a deposited check was unauthorized may involve other law, but it is not necessarily a report that the customer’s blank check was lost or stolen.

A partially completed check requires attention to what remained blank and what the customer told the bank. The statutory text should be applied to the actual item, not a generic “check fraud” label.

Business checks create custody questions. Owners, bookkeepers, payroll vendors, and authorized signers may all handle blank stock. Inventory logs, check sequences, printer systems, approval controls, and office access can show whether a report was reasonable.

A check later negotiated does not by itself prove the initial report was false. A truly lost or stolen blank check can later be completed and used. The State must prove that the lost-or-stolen information was false when given.

Debit cards are not the same as every payment card

A debit card ordinarily accesses funds in a deposit account. A credit card extends credit. Section 609.508 names debit cards but not credit cards, and the difference should not be ignored.

Some cards have multiple functions, network branding, or prepaid features. Account agreements, cardholder disclosures, issuing records, and transaction settlement can establish whether the item was a debit card.

A mobile-wallet token can permit debit transactions without the physical card. Reporting a phone lost, token compromised, or account credential exposed is not necessarily the same as stating that the debit card itself was lost or stolen. The exact words control.

Possession of the physical card after a report can be important but not conclusive. The customer may find it later, receive a replacement with similar appearance, possess an expired duplicate, or recover it from someone who took it.

Card-number continuity can cause confusion. Banks may reissue a card with a new number, retain the underlying account, or automatically update merchants. Records should distinguish the reported card from earlier and replacement cards.

“Lost” and “stolen” describe different factual claims

A lost item is missing without a known taking. A stolen item is claimed to have been taken. A customer uncertain which occurred may use both terms or select a bank category that groups them together.

Temporary inability to locate a card can honestly support a lost-card report. Customers are often told to freeze or replace a card immediately. Finding it later in a coat, vehicle, or home does not prove the initial concern was dishonest.

A stolen-card report can be false if the customer voluntarily gave the card to someone and later described that authorized transfer as theft. But permission can be limited, revoked, or disputed. The scope and timing of consent matter.

A bank may code a card “lost/stolen” for operational reasons even when the customer reported compromise, damage, retention by an ATM, or suspected copying. Internal code language should not be attributed automatically to the customer.

The defense should obtain the full intake script. Questions may be leading or binary: “Was it lost or stolen?” A hesitant answer or employee selection may carry less proof than a deliberate narrative.

The State must prove the report was false

Falsity concerns the representation that the covered item was lost or stolen. The prosecution should identify where the item actually was and why that fact defeats the reported condition.

Continued card use after the report can support falsity if reliable evidence connects the defendant to the transaction and the same card. Chip data, PIN entry, device token, surveillance, receipts, location, and merchant testimony can matter.

A transaction attributed to the account does not always establish physical possession. Recurring merchants, digital wallets, stored credentials, offline transactions, and account-updater services may process after the card is reported.

Checks require similar care. A reported check number may later clear because it had been issued earlier, duplicated, forged, or miscoded. Obtain the image and compare signatures, ink, handwriting, endorsement, deposit channel, and chronology.

A genuine factual dispute about consent or possession is not resolved by the bank’s reimbursement decision. Civil account rules and criminal proof beyond a reasonable doubt are different standards.

Knowing or having reason to know the report was false

The statute reaches actual knowledge and the alternative “having reason to know.” It is not written as pure strict liability. The State must connect the accused’s information and circumstances to awareness or reason to know the lost-or-stolen claim was false.

Actual knowledge can be inferred when a customer possesses and uses the card immediately before and after the report, directs another person to use it, fabricates a theft story, or admits the report was designed to reverse a transaction.

Reason to know is broader than a confession of actual knowledge, but it should not be reduced to any mistake. The evidence must show circumstances that gave the person reason to know the particular information was false.

Confusion about card numbers, household access, memory, medication, cognitive limitations, mobile wallets, replacement cards, and bank terminology can rebut the inference. The defense should explain facts, not merely assert good faith.

The mental state applies at the time of informing. A customer who honestly reports a card missing and finds it an hour later did not necessarily have reason to know the original report was false. What the person does after finding it can still become relevant.

Timing often separates mistake from crime

Build the timeline to the minute when possible: last confirmed possession, disputed transaction, account alert, report, cancellation, replacement order, later transaction, recovery, correction, reimbursement, and police referral.

A report made before suspicious activity may look different from a report made after a merchant dispute is denied. Neither timing proves guilt by itself, but it can support or weaken competing inferences.

A prompt follow-up that the card was found supports good faith, especially if the customer did not seek reimbursement. A delayed correction may still be innocent if the customer believed the old card had been disabled or did not understand a duty to update.

Bank records may use several time zones or posting dates. Authorization time, settlement date, statement date, and employee-entry time are different. An apparent sequence can be wrong if those fields are compared carelessly.

Video and location evidence also require precise synchronization. Camera clocks drift. Phone location may identify a device, not a person or physical card. The defense should test the foundation before accepting a timeline.

Joint accounts, families, employees, and authorized users

Shared access complicates possession and knowledge. A spouse may move a card, a teenager may have permission for one purchase, an employee may hold a company checkbook, or a bookkeeper may order and secure blank stock.

Account agreements can show who owns the funds, who is authorized to transact, who may report an item, and what notice is required. They do not automatically decide criminal intent, but they provide necessary context.

Consent can be disputed. A customer may authorize possession but not a later transaction, or revoke authority before use. Calling the item stolen may be imprecise yet based on an honest understanding of revoked permission.

Another person may make the report using the account holder’s credentials. Voice recordings, device data, branch video, authentication questions, secure-message metadata, and testimony can establish identity.

In business cases, policies and division of duties matter. An owner may rely on staff inventory and reasonably report missing checks that were later found in another office. Title alone does not prove knowledge.

A transaction dispute is not automatically a lost-card report

Customers dispute charges for many reasons: merchant error, duplicate posting, nondelivery, canceled service, wrong amount, unauthorized use, compromised credentials, or a truly lost card. Section 609.508 covers only its stated lost-or-stolen item representation.

Bank forms may combine questions. One screen can ask whether the transaction was authorized and another whether the card remains in the customer’s possession. The full set of answers must be read together.

A customer can possess the card while denying an online transaction made with copied credentials. Describing the transaction as unauthorized is not the same as falsely saying the physical card was lost or stolen.

Conversely, a person may falsely report the card stolen to obtain chargebacks after personally making purchases. That conduct can support section 609.508 and potentially other charges, but the State must prove who made the purchases and what was reported.

Chargeback rules, zero-liability policies, and federal electronic-funds rules govern bank-customer obligations. They do not alter the criminal elements or burden of proof.

Evidence that often decides the charge

The best evidence of the statement is the bank’s native record: recorded call, chat transcript, secure message, form fields, screen flow, confirmation, employee notes, and disposition codes. Counsel should request system documentation explaining how customer input becomes bank coding.

Card evidence includes issuance and activation, chip and magnetic-stripe data, PIN use, mobile-wallet tokens, ATM video, merchant surveillance, receipts, device information, transaction timing, card-present indicators, and replacement history.

Check evidence includes order and delivery records, serial numbers, check images, signature specimens, endorsements, deposit records, ink and handwriting, stop-payment entries, and custody of blank stock.

Communications with family, employees, merchants, and bank staff can show possession, uncertainty, discovery, permission, correction, or motive. Complete threads matter more than selected messages.

Investigators may rely on a bank loss-prevention narrative. The underlying data should be obtained. A conclusion that a claim was “fraudulent” under bank policy does not prove a criminal statute.

Exculpatory evidence can include failed transaction attempts, a later card recovery report, inconsistent camera time, a second cardholder, prior card compromise, merchant data breach, delivery error, or notes documenting uncertainty.

Related Minnesota offenses require different proof

Theft by false representation under Minn. Stat. § 609.52 (2026) generally requires obtaining possession, title, custody, or performance through an intentionally false representation and additional statutory conditions. A false bank report can be evidence, but section 609.508 does not itself require obtaining money.

Check forgery under Minn. Stat. § 609.631 (2026) addresses falsely making, altering, possessing, or using checks under specified circumstances. Reporting blank checks stolen is a different act.

Identity theft under section 609.527 involves another person’s identity and intent to commit, aid, or abet unlawful activity. A dispute using another account holder’s information may raise that issue, but it must be proved independently.

Dishonored-check law, unauthorized computer access, false police reports, insurance fraud, and federal bank statutes may be considered when facts extend beyond section 609.508. None should be treated as interchangeable.

Minnesota’s rule limiting multiple punishment for one behavioral incident can matter if several charges arise from a single objective, but liability and punishment questions depend on the acts, elements, time, place, and final convictions.

Penalty and practical consequences

Section 609.508 is a misdemeanor. Under Minn. Stat. § 609.02, subd. 3 (2026), the maximum is 90 days in jail, a $1,000 fine, or both.

The maximum is not mandatory. A court may impose a fine, stayed jail, probation, community work, restitution where legally supported, or other lawful conditions. Ordinary misdemeanor probation is generally limited to one year under section 609.135.

Restitution must be based on actual compensable loss caused by the offense and supported through the required process. A bank’s internal loss figure, investigation expense, provisional credit, merchant adjustment, and final net loss may differ.

Collateral consequences can include account closure, loss of banking privileges, employment discipline in financial or fiduciary work, professional licensing review, and difficulty opening future accounts. Bank databases and private risk systems have their own procedures.

A misdemeanor is not assigned a felony severity level under the Minnesota Sentencing Guidelines. Any page describing section 609.508 as a guideline-ranked felony is inaccurate.

What Minnesota appellate law does—and does not—establish

No reported Minnesota Supreme Court or precedential Court of Appeals decision presently gives section 609.508 a detailed construction. The statute was enacted in 2000, but the absence of an appellate interpretation does not authorize assumptions about items or elements omitted from its text.

In State v. Colvin, 645 N.W.2d 449, 452 (Minn. 2002), a case about burglary and an order for protection, the Minnesota Supreme Court stated the general rule that penal statutes are strictly construed and reasonable doubt about legislative intent is resolved for the defendant. That principle supports careful attention to “blank checks,” “debit cards,” “the person’s,” and “lost or stolen.”

Colvin did not interpret section 609.508. It should not be cited as authority for what a financial institution is or what “having reason to know” means in this offense.

In State v. Al-Naseer, 788 N.W.2d 469, 480 (Minn. 2010), the court reiterated in a different statutory setting that knowledge may be proved by circumstantial evidence. Section 609.508 expressly includes “having reason to know,” so its mental-state text must still be applied rather than replaced with Al-Naseer’s actual-knowledge analysis.

When no controlling case answers a section 609.508 question, courts begin with statutory text, ordinary meaning, related provisions, constitutional requirements, and the State’s burden to prove every element beyond a reasonable doubt.

How a Minnesota defense lawyer evaluates the charge

No covered item. The report may concern a credit card, completed check, phone, credential, account number, or transaction rather than a blank check or debit card.

No lost-or-stolen representation. The customer may have reported compromise, damage, unauthorized use, or uncertainty without saying the item was lost or stolen.

Truthful report. The item may actually have been missing or taken when reported, even if later recovered or used.

No knowledge or reason to know. A customer can honestly misplace a card, rely on an employee’s check inventory, misunderstand a family member’s possession, or confuse replacement cards.

Wrong speaker. Another account holder, employee, family member, or unauthorized user may have made the report.

Wrong recipient. The communication may have gone to a merchant, app provider, insurer, police department, or other entity not proved to be the covered financial institution.

Bank coding is not customer language. An employee or automated system may have converted a nuanced report into “lost/stolen.”

Transaction proof is incomplete. Account activity can result from stored credentials, recurring billing, mobile tokens, another authorized user, or merchant processing without physical possession.

Statutory construction. An ambiguous edge case involving a business card, joint ownership, prepaid product, or electronic token should be analyzed under the text rather than a general fraud label.

The defense should build a document-supported chronology and compare it with the institution’s native data. The central question is not whether the bank ultimately denied the claim. It is whether the State can prove the exact covered statement was false and that the defendant knew or had reason to know so when it was made.

Frequently asked questions