A Minor Signed Your Lease: The Infancy Defence, Why a Remote Lock Cannot Cure It, and Four Onboarding Gates

Conclusion first: in the United States a lease or subscription signed by a minor is not void, it is voidable at the minor's election - and that distinction changes the operator's exposure completely. A remote lock will still reach the handset, but the lock's legal authority comes from the contract, not from the technology. If the minor disaffirms, the authorisation clause disaffirms with it, and the operator is left with a self-help remedy that has no contractual footing and a set of claims - conversion, trespass to chattels, unfair-practice exposure - that it would not otherwise face.

This is the one onboarding red line that no amount of device management can repair. It is a capacity defence, not a risk score. One sentence to carry away: the contract is the source of the authority, the handset is only the object it acts upon.

Where the line sits: the infancy rule and the three state exceptions

The Restatement (Second) of Contracts § 14 states the baseline: unless a statute provides otherwise, a natural person has the capacity to incur only voidable contractual duties until the beginning of the day before the person's eighteenth birthday. Restatement § 12 frames capacity as potentially partial and dependent on the nature of the transaction.

Three states depart from the 18-year baseline, and an operator underwriting nationally has to price that in:

Jurisdiction	Age of majority	Practical effect on onboarding
Most states	18	Standard threshold; date-of-birth gate set at 18
Alabama, Nebraska	19	A 18-year-old applicant is still a minor; the gate must be configurable by state
Mississippi	21	College-age applicants up to 20 remain minors; the gate must be configurable by state

A single hard-coded threshold of 18 is therefore wrong in at least three states. Confirm the rule for each state in which you write business, because the statute displaces the Restatement baseline where it speaks.

Why voidable is worse than void for an operator

A void contract is a nullity from the start and neither side can enforce it, which at least tells everyone where they stand. A voidable contract is alive and fully enforceable against the adult party until the protected party pulls the plug. Three consequences follow that operators routinely underestimate.

• Asymmetry during the minority. The operator is bound from signature; the minor is not. The minor can sue to enforce delivery, the operator cannot sue to enforce payment while the contract is on foot and unratified.
• Disaffirmance is a unilateral act. The minor may disaffirm during minority or within a reasonable time after reaching majority, expressly or by conduct. No court order is required and no reason needs to be given.
• Restitution runs in a direction operators do not expect. Under the traditional rule, illustrated by Halbman v. Lemke, 298 N.W.2d 562 (Wis. 1980), a minor who disaffirmed a used-car purchase recovered the money already paid even though the vehicle had been wrecked. Some jurisdictions have since allowed the seller an offset for depreciation or benefit received, so the recovery figure is jurisdiction-specific - but the direction of the default rule is worth internalising.

Whether a handset is a "necessary"

The necessaries exception is the one carve-out that survives disaffirmance: a minor is liable for the reasonable value of necessaries even where the contract itself is avoided. The classic categories are food, shelter, clothing and medical care, and the determination is made on the minor's circumstances rather than on the label the contract puts on the goods.

A smartphone in a commercial leasing programme is a weak candidate. Three reasons: the device is supplied under a recurring-payment structure rather than as a single purchase of essentials; the operator's pricing embeds a financing and service component well above the bare value of the handset; and the programme bundles charges, fees and buyout options that a court is unlikely to characterise as necessaries. Operators should underwrite on the assumption that the exception will not be available, and treat any jurisdiction where it is as an upside rather than a plan.

Three layers: what you can do, what it rests on, what fails

Layer	What it actually does	What it depends on	What happens when the dependency fails
Technical (MDM lock, restrictions, remote wipe)	Applies restrictions, locks, displays a message, issues policies	Device enrolled, push channel healthy, valid provider certificate	Commands stop arriving - a channel failure, unrelated to capacity
Monetary (deposit, rent, fees, deficiency)	Supports a claim for money	A valid and enforceable contract with terms that survive scrutiny	Disaffirmance removes the basis for the claim
Authorisation (right to lock, repossess, dispose)	Grants permission to act against the device	Capacity of the person who granted it	Voidable grant means the permission is voidable with it

The table is the core of this page. Only the technical layer is wholly within the operator's control, and it is the only layer that cannot stand on its own. A management command is lawful to issue because the lessee authorised it in the agreement; the agreement's enforceability traces back to capacity.

That is also why "lock first and ask questions later" is the most dangerous available response. Taking a restrictive measure against a minor under a contract the minor can disaffirm converts a contractual remedy into an unauthorised interference with property, and it does so in a fact pattern that regulators and plaintiffs' lawyers find attractive.

Four onboarding gates

1. Date of birth as a first-class required field. Not optional, and not derived by a human reading an ID number. Compute age in whole years as of the application date, and route anything below the state threshold to manual review instead of instant approval.
2. Identity resolution, not identity capture. Name, government ID number, and a biometric or knowledge-based match against an authoritative source. A captured ID proves the document exists, not that the applicant is the document holder.
3. Three observable student signals. Delivery address resolving to a campus or campus-adjacent location; an emergency contact recorded as a peer or academic adviser; age in the 17-to-22 band with employment left blank. Two of three should trigger manual review, not automatic decline - an adult student is an ordinary customer, a minor student is not.
4. Under-threshold applications: decline or documented parental involvement. Declining is cheaper. If you take the second path, the parent or guardian should be the contracting party, the relationship evidence should be retained, and the consent should be a signed document rather than a phone call.

Log the check. Four fields: timestamp, method, result, and the artefact - the verification response, the scan, or the screenshot. Missing any one of them, the operator cannot later show that it exercised diligence, and diligence is what decides how fault is apportioned when the contract is unwound.

Where the regulator's lens is different: under-13 and student marketing

Two adjacent regimes matter even where capacity is not in play.

• COPPA, 15 U.S.C. §§ 6501-6506. Where an operator collects personal information from a child under 13, verifiable parental consent is required before collection, with notice and data-minimisation duties attached. A device programme that collects location, device identifiers and usage telemetry runs straight into this.
• UDAAP and unfairness exposure. Marketing a recurring-payment device programme to a student population, or structuring it so that total payments sit far above the cash price of the handset, invites scrutiny under the Consumer Financial Protection Act's prohibition of unfair, deceptive or abusive acts and practices, and under state analogues. The structural self-test is simple: divide total payments by the retail price of the device. A programme that requires 24 payments of USD 49 on a USD 1,399 handset totals USD 1,176, or about 84 percent of retail - a shape that reads as a lease. At 24 payments of USD 64 plus a USD 1 buyout, the total reaches USD 1,537, or about 110 percent, which reads much more like a financed sale.

Already shipped and the applicant turns out to be a minor: four steps

1. Pause. Stop locks, stop collection activity. Actions taken before the capacity question is resolved tend to enlarge the exposure rather than reduce it.
2. Preserve. Secure the onboarding record, the age verification, the signature flow, the communications, and the device delivery and activation record. This file determines what an offset for depreciation or benefit the operator can argue for.
3. Contact the parent or guardian. In writing, with a clear statement of what is being asked and a defined response window, and retain proof of delivery.
4. Unwind as restitution, not as a deficiency claim. The traditional remedy on disaffirmance is return of the device and restoration of money paid, with the jurisdiction-specific question being whether the operator receives an offset for use, wear or depreciation. Claiming contractual fees in this posture is unlikely to succeed and tends to harden the other side's position.

Three common mistakes

• "They produced a government ID, so they are an adult." An ID establishes that a record exists. It does not establish that the person in front of the camera is the record holder, and in three states it does not establish majority at 18.
• "A parent knew about it." Knowledge is not ratification. Ratification is a manifestation of assent by the former minor after reaching majority, and a parent's passive awareness, unrecorded, is not evidence of anything an operator can put in front of a decision-maker.
• "The device is locked, so the exposure is contained." This inverts the dependency. The lock is a technical act whose lawfulness comes from an authorisation clause that is itself voidable. Containing the device does not contain the claim.

Two boundaries

• Emancipation and similar statuses change the threshold. Emancipated minors, married minors, and minors on active military duty are treated as having capacity in a number of states. These turn on a documented status, not on an assertion, and the evidence should be retained like any other exception.
• Misrepresentation of age does not reliably save the contract. The majority rule is that a minor's false statement of age does not estop disaffirmance, although some states allow a tort claim for the misrepresentation. Underwrite on the majority rule.

FAQ

Is the contract void or voidable?

Voidable at the minor's election. That means it is enforceable against the operator from signature and remains enforceable unless and until the minor disaffirms. Restatement (Second) of Contracts § 14 states the rule in terms of capacity to incur voidable duties.

Can we keep the payments already made?

Not on the traditional rule. On disaffirmance the minor is generally entitled to the return of money paid, and the operator is entitled to the device back. Whether the operator can also recover an offset for depreciation or for the benefit of use varies by jurisdiction, and this is the single most important question to ask counsel about in your states.

What if the parent co-signs?

That works if it is done properly: the adult with capacity is the contracting party and the young person is the user. The authorisation to manage the device is then granted by someone who can grant it. Keep the relationship evidence on file and make sure the ledger's registered user matches the person who actually holds the unit.

Does an age checkbox in the flow help?

It helps as evidence of notice and of a representation, but it is not verification. A self-declaration, standing alone, does not establish age. The workable combination is a date-of-birth field with automatic age computation, an identity check against an authoritative source, the declaration, and full retention of all four artefacts.

Does this apply to 19- and 20-year-old students?

Only in the states with a higher age of majority. A 20-year-old is an adult in most states, and a student's status does not by itself affect capacity. It can, however, affect how a regulator or a court looks at the marketing and the pricing structure, which is a separate question.

Criteria checklist

• Date of birth is a required field, age is computed automatically, and the threshold is configurable by state rather than hard-coded at 18.
• Identity is resolved against an authoritative source, not merely captured from a document.
• Two of three student signals route the application to manual review.
• Every check is logged with timestamp, method, result and artefact, retained for as long as the contract file.
• Total payments divided by retail price is run as a structural self-test before a programme goes live.

LuckyMDM (Sichuan Starlight Network LLC) treats this as a data-model problem rather than a policy document. LuckyMDM requires date of birth as a first-class field at onboarding, computes age in whole years as of the application date against a per-state threshold, routes any under-threshold applicant to manual review instead of instant approval, and stores the verification timestamp, method, result and artefact alongside the contract record.

In short: capacity is a gate at the front door, not a defence you argue at the back end. Compute age, resolve identity, log the artefacts, and never let a lock stand in for a signature that a court will honour.

All Articles