We need answer legal analysis. Need think thoroughly. User asks analyze specific issues and filing sequence. Need likely provide structured memo. Need not overstate missing files. Need apply assumed rules. Need maybe recommend combined: oppose now but move to defer/compel targeted discovery before merits briefing? Need decide. Let's parse.

Question 57: Subscription Fee Class Before Files Arrive. We represent StreamLedger. Oppose proposed consumer class re $7.95 priority-processing fee. Plaintiffs moved cert before producing named plaintiffs' account files. Need decide what to file now and whether seek discovery order before briefing merits.

Governing law given 10 rules. Need answer analysis:
- standing typicality adequacy each rep present record
- common liability vs enrollment path
- predominance consumer-statute and contract claims
- effect of 4 disclosure paths, 6 call scripts, weekday/weekend performance, differing assent
- refunds, chargebacks, employer payments, damages model
- issue class/subclasses cure
- exact named-plaintiff materials that matter and why
- whether StreamLedger should move to defer and compel targeted production, oppose certification now, request broad discovery, or combine
- concrete filing sequence next 21 days without overstating missing files will prove.

Need produce detailed legal memo. Let's analyze facts.

Class: every person charged 62,400 fee. Claims: consumer-statute deception/omission and contract. Need common elements: deceptive representation or omission, causation to payment, unreimbursed loss. Reliance inferred only from materially uniform representation. Contract: terms presented and assented to; no recovery for knowingly separately selected enforceable disclosed term.

StreamLedger records: 4 enrollment paths:
Desktop 14,800 separate unchecked box: "Add priority verification for $7.95; ordinary verification remains available at no charge." Likely explicit opt-in, clear disclosure. Contract: if checked, knowingly selected. Consumer: maybe no deception? At least not uniform hidden.
Mobile 21,300 preselected box: "Priority processing, $7.95," link explaining free ordinary option. Could be dark pattern? Preselected, maybe deception/omission if not unselected. But need know each saw and did not uncheck. Common? Uniform interface maybe common representation, but individual choice to leave selected. Reliance? Preselection could be misleading if free option not salient. But common maybe if all saw same? Need account-level records for preselected state and unselected actions. Contract: enforceable disclosed term? If preselected but disclosed, customer may have knowingly separately selected? They didn't unselect; maybe deemed selected? Contract claim may fail if terms presented and assented, but consumer claim maybe. Need individualized proof if some disabled/unselected? Actually charged fee means box selected at checkout. Need screenshots/confirmation emails.
Legacy 17,100 email link landing page disclosed fee only in linked service terms. More weak disclosure; fee in terms only. Could support deception/omission for those if no clear notice. But individualized? Uniform landing page maybe common. Need original emails and landing page version.
Call 9,200 six scripts, retained only sample recordings. Highly variable; likely need subclasses or individualized. Call reps statements maybe not uniform. Tara alleges mandatory but no date/rep. Need recordings, call metadata, agent IDs. Six scripts. Could not infer uniform. Predominance problem unless scripts common enough? Need discovery to identify scripts and records.

Backend: priority processing reduced avg verification time by 18 hours weekdays, no average improvement weekends. Complaint alleges no benefit. Benefit element maybe for damages? Consumer statute may require economic loss; if benefit conferred, offset? Need damages model. Out-of-pocket $7.95 less benefit? Maybe if paid for service with no benefit. Weekend no benefit, weekdays 18h benefit. Need identify when charged/verification occurred? If benefit, damages less than full fee? Need date/transaction data.

Refunds/chargebacks: 5,400 full refunds, 1,180 chargebacks. Must deduct from damages. Employer cards 7,900; field doesn't establish reimbursement or personal expense. Economic loss must be unreimbursed; need individual proof for employer payments and refund/chargeback status. Could exclude refunded/chargeback/employer-reimbursed? Need discovery.

Named plaintiffs:
Milo Chen: mobile, doesn't remember if box preselected or opened link. Standing? Need show was charged, loss, deception/contract? Alleges mobile, likely charged. But uncertainty enrollment path details and assent may defeat typicality/adequacy? Under rule 7: standing and typicality must be established from evidence, not allegations. Material uncertainty about enrollment path, assent, refund status, personal loss may defeat/postpone. Milo has no memory whether fee box already selected or opened explanation. But he is mobile, charged. Does not remember means cannot prove he was exposed to same representation? Maybe his account file can show. On present record, insufficient to establish typicality/adequacy for mobile class if cannot establish representation or assent. Standing maybe still if he paid and no refund? Not clear. Need file.
Tara Vale: call-center said fee mandatory. Does not remember date or representative. Cannot identify script/recording. Need evidence of call, statement, causation, loss. On present record, insufficient standing/typicality; can't prove deceptive representation or that she was in class. Also if fee was not mandatory? Need call logs.
Jae Morgan: alleges no refund received. Ledger ambiguous CB-R could mean completed chargeback or rejected request. If completed chargeback, no unreimbursed loss (deduct). If rejected, loss. On present record uncertainty about refund/chargeback status defeats typicality/standing? Need ledger clarification, bank statements, refund records. Ambiguous code means material uncertainty. Need file.

Need analyze exact named-plaintiff materials:
- Original confirmation emails at enrollment (show path, representation, fee disclosure, assent, date)
- Screenshots/transaction records of enrollment (desktop unchecked box; mobile preselected/unselected; legacy landing page/terms; call confirmation maybe)
- Account logs showing enrollment path, UI version, checkbox state, link clicks, call metadata/agent/script/recording if retained
- Bank/card statements showing charge date, card type, employer/personal
- Refund/chargeback records: StreamLedger ledger entries, payment processor records, CB-R meaning, bank statements showing reversal/reimbursement
- Employer reimbursement records (expense reports, payroll, reimbursement statements)
- Communications: call recordings, call notes, emails/chat about mandatory/benefit/refund
- For damages: verification timestamps before/after, weekday/weekend, performance data, any benefit received
- For standing: proof of no refund or loss after deductions.
Need why each matters: path/assent, deception, causation, loss, damages, typicality.

Need common questions:
Likely common: fee existed, class definition, maybe backend queue and average performance? But liability varies.
Consumer statute: deceptive representation or omission, causation, loss. Common: overall fee charged, maybe uniform backend queue? But not enough. Materially different disclosures by path defeat common proof. Reliance inferred only from materially uniform rep. There are four paths; desktop clear unchecked, mobile preselected link, legacy terms only, calls variable. No materially uniform representation. So common proof not available for all. Maybe within each path common if uniform? But calls six scripts not uniform. Could subclass: desktop, mobile, legacy, calls maybe script subclasses. But each subclass has individual issues: assent, refund, employer, weekend/weekday benefit, damages. Need predominance? For consumer statute, maybe within mobile/legacy if uniform disclosure and backend queue common? But still individualized causation? Reliance inferred if uniform; but each must have been charged (common), no refund (individual), loss (individual). If full damages are $7.95 less refunds, individual deductions. Could use common damages model? Need account data.
Contract: depends on terms presented and assented. Different terms. Desktop: clear opt-in. Mobile: preselected but disclosed. Legacy: terms only. Calls: scripts. Contract claim likely requires individualized terms and assent. Maybe common within same disclosure if same terms and assent method? But still individual selection. Rule 5: cannot recover fee customer knowingly separately selected under enforceable disclosed term. Desktop likely fails common. Mobile maybe some argue not knowing? But preselected disclosed; contract maybe depends on terms of service. Contract predominance poor.

Predominance:
- Consumer statute: for all class, individualized proof likely predominate due to four paths, call scripts, assent, refunds, employer, benefit/weekend. Deny. For narrower subclasses? Need assess. If define mobile subclass (preselected uniform) and legacy subclass? Common questions may predominate? Need still individualized damages and loss. But can use common damages model if out-of-pocket full $7.95, but need deduct refunds/chargebacks/employer reimbursements. Those are account-level; can be common? Maybe individualized but discoverable. If no refund data, need discovery. If subclass excludes refunded/chargeback/reimbursed? Can define class as persons not refunded/reimbursed. But need know who. Predominance may be manageable with account data. However named plaintiff uncertainty. Also benefit: if priority processing provided 18h weekday, damages not simply full fee? Consumer statute economic loss maybe unreimbursed loss from fee, but if benefit conferred, offset? Need model. If benefit not uniform, weekend vs weekday. Could use average? Need match certified theory. If theory is no benefit? Backend contradicts weekdays. If deception re hidden fee but benefit? Could still be deceptive if fee not clearly disclosed? But if customer received benefit, maybe loss less? Need individualized by date. Maybe common proof of weekend no benefit, weekday 18h benefit; damages model could be full fee for weekend, reduced for weekday? Need match. But if claim is deceptive fee, benefit may not reduce statutory damages? The rule says damages model must match theory, full refunds etc deducted from out-of-pocket model. It doesn't explicitly require offset for benefit, but economic loss maybe unreimbursed; if service provided benefit, maybe not full loss? It says unreimbursed economic loss; benefit may reduce. Need discuss.
- Contract: individual terms/assent predominate. Deny unless maybe desktop subclass? Desktop clear disclosure, likely no claim. Mobile preselected but disclosed, contract maybe assent by proceeding; individualized? Hard.

Issue class/subclasses:
Could issue class on liability for mobile preselected or legacy? Maybe separate issues: liability (deception/omission) and damages. But predominance? If issue class for liability, still individualized loss? Issue classes usually narrow common issue. Could certify issue class on whether preselected box was deceptive/omission for mobile customers, then individual damages. But rule 2: damages class common questions must predominate and superiority. For issue class maybe not damages. Could cure some variations? Subclasses: desktop opt-in (probably no class or issue?), mobile preselected, legacy terms-only, call scripts (maybe individual). But call scripts too varied, recordings missing. Weekend/weekday? Could subclass by verification date/weekend? But performance varies by day; benefit damages. Could issue class for each disclosure path. But named reps? Need reps for each subclass with evidence. Current reps: Milo mobile (uncertain), Tara call (insufficient), Jae refund ambiguity. No desktop, legacy, call script reps? Need additional reps or cure via discovery.

Filing strategy:
Options: immediate denial, broad 6-month stay, full merits now, move to defer and compel targeted production, combine. Need decide. Under rule 8: court may defer certification briefing and compel targeted discovery when movant controls specific previously requested info essential to standing, typicality, predominance. Requesting party identify documents and explain decisional significance; broad delay not permitted. We requested 4 months ago; plaintiffs promised by June 1, produced none, filed June 3. This fits targeted. Should move to defer and compel targeted production before merits? But opposition brief due in 21 days. Need concrete filing sequence. We can file opposition? Maybe simultaneously file limited motion to defer certification hearing/briefing pending targeted production, with proposed discovery order, and serve specific requests; not request broad six-month stay. We should also preserve opposition on present record: standing/typicality/predominance fail. Could file opposition now? If brief due 21 days, need file opposition or maybe notice of appearance and statement? We need decide what to file now. Could file: (1) notice of intent to oppose or opposition? (2) motion to defer and compel targeted production; (3) if court denies deferral, file merits opposition within deadline; or file opposition concurrently with motion? The question: "what to file now and whether to seek a discovery order before briefing the merits." Need recommend. Since opposition due 21 days, if we seek deferral, we may need file motion promptly. Could combine: file (a) a limited motion to defer certification briefing/hearing and compel targeted production of named plaintiffs' account files, with proposed order; (b) a short preliminary opposition/statement of opposition identifying present-record deficiencies (standing/typicality/predominance) without full merits? Or file full opposition within deadline while moving to hold in abeyance? Need not request broad discovery. The concrete sequence next 21 days: Day 1-2 meet and confer? Already requested 4 months ago but maybe formal meet and confer? Need maybe send letter and file motion with certification of conference. Day 3-5 file motion to defer and compel targeted production; include document schedule, decisional significance, proposed order, no broad stay. Day 7 request status conference? Day 10 if court grants, produce/serve? If denies, proceed with opposition. Need file opposition by day 21? If motion defers briefing, maybe no opposition due until production. But if court requires opposition to motion, file response? Need sequence: file motion before opposition due; if court doesn't resolve before deadline, file timely opposition preserving arguments and stating deferral pending. Could also file "opposition brief" if no deferral. Need avoid overstating missing files will prove: say files may establish or negate standing/typicality; we seek only to test, not assume they will defeat. Need specific materials.

Need think about legal standards and possible outcomes.

Detailed analysis:

1. Standing/Typicality/Adequacy:
Rule 7: evidence not allegations; material uncertainty about enrollment path, assent, refund status, personal loss may defeat/postpone certification.
Need for each:
- Milo Chen (mobile): He alleges mobile. But mobile path includes preselected box and link. His uncertainty whether box already selected or opened link is core to whether he was exposed to preselected representation and whether he assented. He cannot testify from personal knowledge? If charged, maybe his account shows. Standing: to bring class, must have personal standing: injury in fact, traceable, redressable. If he paid $7.95 and no refund, maybe standing. But typicality: claims same as class? For mobile subclass, if he can't establish the representation or his assent, may not be typical. Adequacy: inability to recall may make him less adequate? But not necessarily; counsel can prove with documents. On present record, material uncertainty about enrollment path/assent; postpone. Need original confirmation, UI logs, screenshots, link click records.
- Tara Vale (call): Cannot remember date/rep. Call path has six scripts and only sample recordings. Need identify call to prove representation "mandatory". Without date/rep, cannot locate recording or script version. Standing: if she was charged and loss, maybe. Typicality: cannot establish common call script or that she heard misleading statement. On present record, fails; may be inadequate to represent call class. Need call logs, recording, agent/script records, confirmation email.
- Jae Morgan: no refund alleged but ledger ambiguous CB-R. If completed chargeback, no unreimbursed loss; if rejected, loss. Material uncertainty about personal loss/refund status. On present record, cannot establish unreimbursed loss typical. Need ledger explanation, payment processor records, bank/card statement, refund/chargeback docs.
Adequacy overall: three reps span different paths, no one can represent all. None can establish class-wide common facts. Inconsistent paths and uncertainties. Need adequate reps who can protect varied interests? Maybe if subclasses, need reps per subclass. Current three insufficient. Also conflicts? Maybe refunded vs unreimbursed. Need mention.

2. Common liability questions vs individual:
Common possible:
- Fee charged and amount; class membership (charged $7.95).
- Existence of fee, backend queue? But complaint's no benefit false? Backend average shows 18h weekday, none weekend. Not common no benefit. Maybe common average benefit by weekday/weekend? Could be common for damages if date known.
- For each enrollment path, if uniformly same disclosure, whether that disclosure was materially deceptive/omission or enforceable term. But across class, no.
- For mobile: whether preselected box with link was materially deceptive/omission (common legal question) if all saw same. For legacy: whether fee only in linked terms was materially deceptive/omission. Desktop: clear opt-in likely no. Call: script-by-script if scripts uniform; but six scripts.
- For contract: whether terms presented and assented. Individual assent and path.
Requires enrollment path:
- deceptive representation/omission content (desktop vs mobile vs legacy vs call)
- reliance inference (only materially uniform; paths differ)
- causation (did path/representation cause payment; for calls specific statement; for mobile whether unselected; for desktop checked)
- contract terms and assent (checkbox state, terms version, call script)
- benefit/performance maybe transaction date weekday/weekend; but backend average maybe common? Need individual date.
- damages: refunds/chargebacks/employer reimbursements, individual loss.

3. Predominance:
Consumer statute:
All class: individualized questions predominate. Four materially different disclosures, six scripts, assent records, refunds, employer, benefit/weekend. Reliance cannot be inferred class-wide. Even if liability within subclasses common, damages individual. Need account-level proof. Deny full class.
Possible subclass/issue: mobile preselected and legacy terms-only? Need evaluate. For mobile, if UI uniform and backend records show preselected, common liability (deception/omission) maybe predominates; damages still individual but manageable via records? Need named rep. For legacy, if landing page uniform, common liability. But legacy disclosed fee in terms; maybe individualized if versions differ. For calls, six scripts; maybe subclasses per script if records identify; but missing recordings and Tara can't identify. Predominance likely fails for call class due to individualized statements, script, causation. Desktop: clear opt-in; individualized and likely no claim; no class.
Weekend/weekday: If damages model requires benefit offset, individual date. Could maybe common: all weekday claims reduced by value of 18h? But value of time? Not straightforward. If theory is fee deceptive regardless of benefit, maybe no offset? But economic loss? Need match. Could separate issue class for weekend no-benefit? But weekend customers may have no benefit; weekday maybe got benefit. But if deception is nondisclosure, benefit may not negate loss? Need careful. Consumer statute requires economic loss; if paid for service that provided benefit, loss may be less. If no benefit weekend, full out-of-pocket. Weekday, if priority delivered 18h speed, perhaps partial benefit; need valuation. That is individualized (when charged, whether priority actually delivered). Could use common model: full refund for weekend, zero or reduced for weekday? But if class theory is fee was deceptive because hidden, not necessarily no benefit. Complaint alleges no benefit, but records show weekday benefit; that may defeat "no benefit" theory or require narrower class (weekend only). Need mention: if plaintiffs rely on no-benefit, backend contradicts for weekdays; either narrow to weekend or prove benefit immaterial. If narrow to weekend, common benefit/no-benefit maybe. But disclosure still varies.
Contract:
All class fails. Desktop: knowingly selected under clear disclosed term; no recovery. Mobile: preselected disclosed; contract depends on terms and assent; likely individualized. Legacy: terms only; maybe contract not knowingly selected? But assent to terms? Individualized. Calls: scripts variable. Need no class.

4. Effect of disclosure paths, scripts, performance, assent:
- Four paths break material uniformity. Rule 3: materially different disclosures may require individualized proof/subclasses.
- Desktop unchecked separate box: strong disclosure and affirmative selection; defeats deception and contract for those; cannot support class with others.
- Mobile preselected box: common dark-pattern issue; could support subclass if records uniform; but need evidence of preselected state and whether user unselected? Actually charged means selected. Need proof they saw and link? Common UI. But assent records differ.
- Legacy fee only in linked service terms: weaker disclosure; maybe common omission if all same; but need landing page versions.
- Call six scripts: not uniform; oral communications vary; only samples; likely individualized; need recordings.
- Weekday/weekend performance: common no-benefit only for weekends; weekdays show benefit. Affects damages and maybe liability if complaint alleges no benefit. Requires date/transaction data.
- Differing assent records: checkbox unchecked vs preselected, call consent, terms assent. Contract claim inherently individualized.

5. Refunds/chargebacks/employer payments/damages model:
- 5,400 full refunds and 1,180 chargebacks must be deducted; those members may have no unreimbursed loss, unless refunded elsewhere? Need exclude or damages zero. Need identify each member. StreamLedger ledger and processor records, bank statements. Ambiguous CB-R for Jae.
- Employer cards 7,900: field not enough to establish personal loss. Need reimbursement records/expense reports; if employer paid and not reimbursed, customer may not have personal economic loss. If customer reimbursed employer, loss. Need individual proof. Could maybe exclude business-account payments from consumer class or require certification by business? But consumer statute? Need individual.
- Damages model must match theory. If out-of-pocket fee, model = $7.95 - full refunds - chargebacks - employer reimbursements/benefit offsets? If benefit offset, need valuation. If statutory damages maybe different? Assume out-of-pocket. Need account-level database with date, amount, refund status, card type, reimbursement, verification weekday/weekend, priority benefit. Need class action notice maybe.
- For certified class, cannot use full $7.95 if many refunded/employer. Need deductions. If missing named files, can't calibrate.

6. Issue class/subclasses:
- Could certify narrower issue class on liability for specific disclosure (mobile preselected; legacy terms-only) if uniform and named rep with evidence. But still need damages individual. Maybe issue class for "whether mobile preselected presentation was materially deceptive" and then individual damages. But if damages not common, may not satisfy superiority? Issue classes useful if individual damages manageable. Could use common liability + individual damages. Rule 10: certify narrower issue class or subclasses when common issues separable without unmanageable. Could cure disclosure variations: separate subclasses by path; maybe call scripts. But does not cure refunds/employer/benefit unless account data. Could define subclass excluding refunded/chargeback/reimbursed? But need data. Could issue class for weekend no-benefit? Maybe.
- Proposed subclasses:
  1. Mobile preselected: common liability; individual damages; need rep.
  2. Legacy terms-only: common liability; individual damages; need rep.
  3. Call scripts: perhaps multiple script subclasses if scripts materially similar and records; but Tara can't identify; need discovery.
  4. Desktop: likely no class; maybe issue that no deception? Or exclude.
  5. Weekend vs weekday damages subclass/issue: common benefit/no benefit and damages model? But still refunds etc.
- Issue class could separate liability and damages. But current motion asks full class, so deny and invite narrowed motion after discovery.

7. Exact named plaintiff materials and why:
Need list with purpose:
- Account enrollment records: path, date, IP/device, UI version, checkbox state, link click, terms version, call metadata. Essential to standing/typicality/predominance.
- Original confirmation emails: show disclosure and fee, terms, date, assent; maybe call confirmation.
- Screenshots or device logs: show what rep saw; Milo mobile box; legacy landing page; desktop box.
- Call recordings/notes: Tara's statement mandatory, script, date, agent; causation.
- Payment records: bank/card statements, transaction dates, card type (employer/personal), amount. Standing and damages.
- Refund/chargeback records: ledger entries, processor records, CB-R definition, reversal dates, bank statements. Jae's loss.
- Employer reimbursement records: expense reports, reimbursements, payroll; personal loss.
- Performance data: verification timestamps, priority delivery, weekday/weekend; benefit/damages.
- Communications: emails/chat about refund, fee, benefit; possible estoppels.
Need note: We don't need all merits; only targeted for standing/typicality/predominance.

8. Strategy:
Should StreamLedger move to defer and compel targeted production, oppose now, broad discovery, combine? Need recommend.
Given rule 8: targeted discovery appropriate. Plaintiffs promised files and didn't produce; filed certification. We should file a limited motion to defer certification briefing/hearing and compel targeted production of named plaintiffs' account files before merits briefing. We should not request broad six-month stay; overbroad, not permitted. We should also preserve opposition: either file a preliminary opposition or file full opposition if court denies deferral. Since opposition due 21 days, we can file: (a) immediate notice of intent to move; (b) targeted discovery motion with proposed order; (c) if necessary, a brief "opposition to class certification on present record" or "conditional opposition" to preserve. But perhaps better: file a concise opposition now identifying record deficiencies and arguing that if no deferral, certification should be denied; simultaneously move to defer for limited production. Need not delay opposition. But if we move to defer, the court may set hearing; if opposition due in 21 days, we may need to file opposition to avoid waiver. Could file "Preliminary Opposition and Motion for Limited Deferral and Compelled Production". Need concrete sequence.

Need be careful: The plaintiffs' missing files are named plaintiffs' own files; defendant requested. Could court compel named plaintiffs to produce? Yes if movant? Rule 8: court may compel targeted discovery when movant controls specific previously requested info essential. But named plaintiffs control their files. We are defendant. We can move court to order plaintiffs to produce. Need identify documents. The court can defer certification briefing. Need no broad delay.

Potential issue: Should we seek immediate denial instead? On present record, standing/typicality may fail; could deny. But if files might cure, deferral with production is better. However if we only move for deferral, plaintiffs may still not produce; need sanctions? We can seek order with short deadline and consequences (deemed admitted? denial). Need propose 14-21 day production? They promised June 1; now June 3. Need maybe order produce within 14 days, then supplemental briefing. Not six months. Need targeted.

Need maybe request "limited discovery stay" only pending production, not broad. And "oppose certification now" on present record. Combine: file opposition preserving denial; move for limited deferral and production; if court denies deferral, proceed with merits opposition. We should not file full merits opposition before production if deferral likely? But deadline. Could file short "present-record opposition" and request deferral. The prompt asks "what to file now and whether to seek a discovery order before briefing the merits." Answer: File a targeted motion to defer and compel plus a present-record opposition/conditional opposition. Seek discovery order before merits briefing, but not broad. Maybe if court grants, merits briefing after production; if denies, full opposition due.

Need concrete filing sequence next 21 days without overstating what missing files will prove.
Let's craft timeline:
- Day 1 (immediately): Serve detailed written request/letter to plaintiffs' counsel: reassert specific document requests (list) and demand production by e.g., 10 days; state they already promised June 1; ask meet and confer; note certification motion premature. Preserve request under discovery rules. If they refuse, file certification of conference.
- Day 2-3: If no production, file "Defendant's Motion to Defer Certification Briefing and Compel Targeted Production of Named Plaintiffs' Account Files". Include:
  * proposed order: plaintiffs produce specified documents for Chen, Vale, Morgan within 14 days (or by date); produce StreamLedger's own records? They have their own? They control some; maybe also defendant's records already? We may request court order plaintiffs to produce and defendant to produce its records? Need targeted. Since defendant controls some records, maybe include defendant's production? The missing files are plaintiffs' account files. We can also produce StreamLedger ledger extracts? We have backend. But named plaintiffs' original confirmation emails, bank statements, employer records are plaintiffs' control.
  * specify each document and decisional significance (standing, typicality, predominance).
  * ask court to suspend certification briefing/hearing only until 21 days after production (or 30 days total), not six months.
  * propose if failure, certification denied or documents excluded, no adverse inference? Need careful. Could seek default? Maybe "if not produced, certification denied" or "plaintiffs' testimony excluded"? Need not overstate. Could seek consequences for noncompliance.
  * no request for broad merits discovery.
- Day 4-7: Request status conference or set briefing schedule. If court asks, provide proposed production order. Maybe file reply if needed.
- Day 5-10: Continue meet and confer; perhaps send follow-up. If plaintiffs produce, review and file status report; maybe file supplemental opposition based on produced files? But 21 days. Need if produce by day 10, we need respond. Could request short extension or schedule. But opposition due 21; maybe if court defers, no issue. If not, we can file opposition by 21 using present record.
- Day 10-14: If court denies deferral or no production, prepare and file opposition to class certification (or complete opposition) by Day 21. Include present-record deficiencies: named plaintiffs' standing/typicality uncertain; no material uniformity; predominance; damages. If some documents produced, incorporate. If not, rely on present record and note court's order.
- Day 15-20: If deferral granted and production occurs, file status report and request short supplemental briefing (e.g., 14 days after production). If court requires, file response to plaintiffs' opposition? Need sequence.
- Day 21: Ensure opposition or conditional opposition filed; no waiver. If motion pending, file short status note that merits opposition deferred per court but if not, filed.

Need maybe include "Do not request broad six-month stay". Reason: rule 8 prohibits unfocused discovery; targeted only.

Need maybe discuss immediate denial: On present record, could deny because named plaintiffs fail standing/typicality and class fails predominance. But better to seek limited deferral because court can require specific files; if not, denial. However if plaintiffs' files might cure, deferral may be favored. Need recommend combined. Need perhaps say if court wants merits now, file opposition arguing denial. Do not stipulate to broad discovery.

Need maybe mention "StreamLedger's own database should be enough" counter: defendant's database shows aggregate paths and performance but not named plaintiffs' individual enrollment, assent, refund, employer reimbursement. Rule 7 requires evidence for named plaintiffs. StreamLedger's database may identify path and charge, but not original representations, user's screen, link clicks, call statement, bank/card reimbursement. Need individualized proof. For Milo, database may show mobile path but not whether box preselected? Actually mobile path is preselected box by design; if charged, maybe selected. But he doesn't remember whether it was already selected; the design says preselected, so maybe account record can show. But he also didn't remember opening link; link click logs may show. For typicality, if all mobile preselected, his memory less critical? But rule says material uncertainty on present record. Need not overstate.

Need consider standing: To bring consumer-statute claim, named plaintiff must have paid fee and suffered unreimbursed loss. Do we know each was charged? Proposed class every person charged; presumably they are charged. But maybe refunds? Jae ambiguous. Milo and Tara maybe no refund info. Standing requires injury in fact: payment. If they paid and no refund, yes. But they haven't produced refund records. On present record, allegations of being charged may be enough for standing? Rule 7 says standing and typicality must be established from evidence, not allegations alone. So we need argue insufficient. But if class certification record includes their declarations? They allege. Need maybe state: unless they submit affidavits with documents, allegations alone insufficient. For standing, if they can show payment by transaction records, maybe. But missing files. So postpone.

Typicality:
- Milo: If mobile, typical of mobile subclass but not class. His uncertainty about whether box selected/opened link might be same as other mobile? Many may not remember. But typicality requires common legal theory; if he can't prove he was exposed to representation, not adequate. Maybe if account record shows, okay. Present record insufficient.
- Tara: call; typical of call claims only if she heard mandatory statement. But six scripts; if no date/rep, cannot identify. Not typical of all calls. Maybe not adequate.
- Jae: refund ambiguity; if no loss, not typical of unreimbursed class. If chargeback completed, not injured. Present record insufficient.
Adequacy:
- Reps from different paths cannot adequately represent all. Inadequate to manage common issues. Need separate reps for subclasses. Current three have memory gaps. No rep for desktop/legacy. Also conflict between refunded and unreimbursed? Need class management.

Need maybe discuss commonality: There are common questions: whether fee was charged, whether any representation was materially deceptive by path, whether backend performance supports no-benefit. But commonality alone not enough. Predominance.

Need maybe discuss "uniform material misrepresentation may support common proof." The only uniform things: $7.95 fee, backend queue? But representations differ. One marketing page? Plaintiffs rely on one marketing page and common backend queue. But actual enrollment paths differ. One marketing page may not be the representation each saw. Backend queue not a representation. No uniform misrepresentation. Reliance cannot be inferred.

Need maybe discuss "contract claim depends on terms presented and assented to." For desktop, clear separate unchecked box. If customer checked, knowingly selected. For mobile, preselected but link; if customer proceeded without unchecking, did they knowingly select? Could argue they didn't affirmatively select, but terms disclosed. Contract claim may still fail because fee was disclosed in terms and UI; enforceable. But consumer statute maybe. For legacy, fee only in terms; maybe if not clearly presented, contract maybe not knowing? But terms enforceable? Need individualized. Calls: scripts; if told mandatory, maybe misrepresentation; if disclosed, assent.

Need maybe discuss "full refunds, chargebacks, employer reimbursements must be deducted from out-of-pocket model." Need propose damages model:
- Universe: 62,400 charged.
- Deduct 5,400 full refunds (no loss unless refunded elsewhere? full fee refund = zero) and 1,180 chargebacks (zero, unless chargeback not final? Need final).
- For 7,900 employer card payments, do not automatically exclude; need evidence whether customer personally bore cost. If employer reimbursement not personally reimbursed, no personal loss; if personally reimbursed, loss. Need individual records.
- For remaining, if benefit offset required: identify verification date and weekday/weekend; if weekend no average improvement, full $7.95; if weekday average 18h improvement, need determine if any economic value and deduct. But if consumer statute's loss is the fee for deceptive practice, maybe full fee regardless of benefit? Need be careful. Rule 6 says damages model must match certified theory and deduct refunds etc. It doesn't say benefit offset, but economic loss may be reduced by benefit. Could say if certified theory includes "no benefit," then backend weekdays defeat or require narrower weekend class; if not, damages model may still require valuation of benefit or statutory measure. Need avoid overclaim. We can say "depending on the certified theory, a benefit offset or narrowed no-benefit class may be required; at minimum, weekday performance prevents a class-wide no-benefit damages model." Good.
- Need account-level data to compute. Could use database and notice.

Need maybe discuss "materially different disclosures may require separately defined subclasses." So four subclasses. But if subclass too small? 14,800, 21,300, 17,100, 9,200 all large. Numerosity okay. But typicality reps.

Need maybe discuss "defendant opposing certification must connect variations to elements or remedies. Merely asserting every customer different doesn't defeat." We need connect: variations in disclosure tie to deception/reliance; call scripts tie to representation/causation; assent ties to contract; refunds/employer tie to loss; weekday/weekend ties to damages/no-benefit. Good.

Need maybe include a "decisional significance" table for documents.

Potential final answer structure:
- Executive recommendation: Do not file only broad stay. File combined limited motion + present-record opposition. Seek targeted discovery before merits. Immediate denial preserved.
- I. Record posture and standard
- II. Named plaintiffs: standing, typicality, adequacy (table)
- III. Commonality and predominance: consumer statute and contract, by path
- IV. Effect of four paths, scripts, performance, assent
- V. Damages: refunds/chargebacks/employer, model
- VI. Subclasses/issue classes
- VII. Exact named plaintiff materials needed and why (table)
- VIII. Strategic choices: denial vs deferral vs broad discovery
- IX. Filing sequence next 21 days (timeline and proposed order language)
- X. Conclusion

Need ensure answer not legal advice? It's hypothetical. Fine.

Need maybe include proposed order terms:
1. Plaintiffs shall produce for each named plaintiff within 14 days:
   a. All account enrollment records maintained by StreamLedger? Actually defendant controls. Could order defendant to produce extracts? But plaintiffs requested? We can produce. Maybe order both:
   - Plaintiffs produce: original confirmation emails, screenshots/device logs in their possession, bank/card statements, refund/chargeback records not in defendant's possession, employer reimbursement records, communications, call logs? Call recordings maybe defendant controls. Need identify.
   - Defendant produce: account ledger entries, UI/transaction logs, call metadata and any retained recordings, refund/chargeback ledger, CB-R definitions, backend performance records for named plaintiffs. But the missing files are plaintiffs. The motion to compel could target plaintiffs' files; we can also stipulate to produce our records.
2. Certification briefing stayed only until 21 days after production (or 30 days from order) to allow supplemental briefing; not six months.
3. If plaintiffs fail to produce, court may deny certification or exclude their testimony; no broad stay.
4. Scope limited to standing/typicality/predominance, not full merits.

Need maybe include "without overstating missing files will prove": language: "We do not ask the court to assume the files will establish a defense; we ask only that the named plaintiffs, who moved for certification, produce the specific records necessary to show they have standing and typicality. If the records show they are typical, the court may proceed; if not, denial is appropriate." Good.

Need consider if motion to defer before merits is proper if opposition due in 21 days. Maybe file "Motion for Order Deferring Opposition Briefing"? Could be seen as delay. But rule 8 permits. Need emphasize targeted, previously requested, promised, none produced.

Need maybe discuss "Plaintiffs argue missing docs are merits details and defendant's database enough." Rebut: not merits; standing/typicality essential. Rule 7. Database lacks personal control files. For named plaintiffs, allegations alone insufficient.

Need maybe discuss "full merits briefing now" option: If court denies deferral, we must file opposition. We should be prepared. We can file a "preliminary opposition" now, not full? Need concrete.

Let's think of possible court outcomes:
- Court grants deferral and production: Then after files, we file supplemental opposition. If files show named plaintiffs lack standing/typicality, deny. If show typical, maybe still deny full class but invite subclasses.
- Court denies deferral: We file merits opposition; argue denial based on present record. Need not produce plaintiffs' files. But can seek discovery later if subclasses.
- Court orders immediate denial: Great.
- Court orders broad discovery: We should not accept; object as overbroad.

Need maybe include "Do not request six-month stay". Reasons: Rule 8: broad delay for unfocused discovery not permitted; plaintiffs already agreed June 1; certification schedule can be managed with 30-45 days.

Need maybe include "Should StreamLedger move to compel targeted production even though plaintiffs are the movants?" Yes, because they control files. We requested. Need identify specific docs.

Need maybe include "targeted production from StreamLedger"? We can offer to produce defendant's records to narrow: e.g., ledger, UI logs, call metadata, refund ledger. That strengthens. But the missing named plaintiff files are in plaintiffs' possession. We can propose joint production.

Need maybe include "If call recordings only samples, we can produce any retained for named plaintiff? Tara no date; maybe cannot. We can produce call logs for Vale? She may not know date. Need her bank statement to identify charge date, then call log around date. That's why bank/card statements matter. Good point: For Tara, if she provides bank statement with charge date, we can identify call date/agent/script/recording. If not, cannot. For Milo, confirmation email date helps. For Jae, bank statement helps identify chargeback/reversal.

Need maybe include "CB-R code ambiguous": Need definition and transaction-level records; bank statement showing whether money returned. If chargeback completed, no loss. If rejected, maybe loss. Need not assume.

Need maybe include "employer card field": For named plaintiffs, if any employer card, need reimbursement records. But not specified which named. Maybe class-wide. For named reps, need personal loss. If one used employer card and not reimbursed, no standing. We need their bank/employer records.

Need maybe discuss "adequacy" with different paths: A representative with call claim may not adequately represent mobile/desktop/legacy because interests differ (e.g., call reps may seek proof of oral misrepresentation, mobile may seek UI). Also refunded vs unreimbursed. Need separate reps.

Need maybe include "typicality" legal: claims arise from same course of conduct and same legal theory; if reps cannot prove the theory, not typical. For Milo: cannot prove preselected box representation? But if all mobile preselected, maybe his claim typical if he was charged. However his uncertainty about whether box already selected is actually a fact that the system design can prove; if account logs show preselected, maybe okay. But present record lacks. Need say "may be cured by account logs; until then postpone." For Tara: need call logs; may be cured. For Jae: need ledger/bank; may be cured. But if not, deny.

Need maybe be nuanced: We are opposing, but cannot overstate. We should say "on present record, certification should be denied or deferred; if files establish standing/typicality, still class fails predominance." That's safe.

Need maybe include "standing: named plaintiffs must have paid and not been reimbursed. Allegations of charge may be sufficient if defendant does not challenge? But rule 7 says evidence. We can argue declarations alone not enough if material facts contested by ambiguous ledger. For Milo/Tara, no refund records; we can request. For Jae, ambiguous code creates genuine dispute.

Need maybe discuss "consumer statute reliance inferred only from materially uniform representation." Since no uniform, individualized reliance/causation. For mobile, preselection may be common but reliance inference maybe if materially uniform; for each mobile customer who saw same preselected box, reliance could be inferred? But if they unchecked? Charged means didn't uncheck. Maybe common. But still individual path. Need not overstate. Could say "material uniformity exists only within a sufficiently narrow path, not across the proposed class."

Need maybe discuss "backend queue common": It shows fee charged and maybe performance, but not deception. It can support common proof of fee amount and average performance, but not liability. It may help damages if date known.

Need maybe discuss "one marketing page": Plaintiffs rely on one marketing page but actual enrollment paths differ. Marketing page may not be the representation at enrollment. For consumer statute, each claimant exposed to deceptive representation or omission. Need show exposure. One page not enough.

Need maybe discuss "contract claim: customer cannot recover fee knowingly and separately selected under enforceable disclosed term." Desktop likely barred. Mobile preselected: if disclosed and terms enforceable, perhaps not knowingly separately selected? But proceeding with preselected box may be assent; individualized. Legacy: fee in terms; if enforceable, no recovery; if not conspicuous, maybe consumer. Call: script. So contract predominance poor.

Need maybe include "If certify subclass for mobile, contract claim may still fail because fee disclosed and preselected; but consumer claim maybe." Good.

Need maybe include "issue class vs subclass": A subclass by enrollment path can handle disclosure/assent; an issue class can handle liability while damages individual. But current named reps inadequate. Need perhaps propose:
- Mobile issue class: liability whether preselected presentation was materially deceptive/omission; damages individual.
- Legacy issue class: liability whether fee-only-in-terms was materially deceptive/omission.
- Call script issue classes only if script records show common statements; otherwise individual.
- Weekend damages issue: no benefit, full out-of-pocket, maybe subclass.
But caution: issue class for liability may not be superior if individual damages numerous; but can be.

Need maybe include "defendant must connect variations to elements/remedies" with a table:
Variation | Element/Remedy affected | Consequence
Disclosure path | deception/omission, reliance, contract term | no common proof; subclasses
Call script | representation, causation | individual proof; recordings
Weekend/weekday | no-benefit theory, damages offset | no class-wide damages model
Assent records | contract assent | individual
Refund/chargeback | economic loss | deductions/exclusions
Employer card | personal loss | individual proof

Need maybe include "exact named plaintiff materials" table with columns: Document, why necessary, if absent consequence.
List:
1. Enrollment confirmation emails (Milo, Tara, Jae): date, path, representation, fee disclosure, assent.
2. UI transaction logs/screenshots: checkbox state, link click, terms version.
3. Account logs: path, date, device, IP, account type.
4. Call logs/metadata/recordings/notes: Tara's call date, agent, script, statement.
5. Bank/card statements: charge date, card type, employer/personal, refunds/chargebacks.
6. Refund/chargeback records: ledger, processor, CB-R meaning, reversal status.
7. Employer reimbursement records: expense reports, reimbursements, personal bearing.
8. Verification performance records: timestamps, weekday/weekend, priority benefit.
9. Communications: emails/chats/call notes about fee, benefit, refund.
Need maybe specify for each named plaintiff:
- Milo: mobile UI logs, confirmation email, link click logs, bank statement, refund records.
- Tara: bank statement to date call, call logs/recordings, confirmation email, refund records.
- Jae: ledger CB-R explanation, processor/bank statement, refund/chargeback records, employer records if applicable.

Need maybe include "Do not request broad discovery": only documents for three named plaintiffs and maybe class-wide records to define subclasses? We can request class-wide records we already control? Need targeted. Could request StreamLedger's records to map enrollment path and refund status for class? But we have them. For certification, we may need class-wide refund/employer data? We can produce. But named files are essential. Maybe also request court to order plaintiffs to identify any refunds/chargebacks? But class-wide. For predominance, need know refund status. We have 5,400 refunds, 1,180 chargebacks, but need individual. We can produce ledger. For employer 7,900, we can't establish reimbursement; need plaintiffs' records. For class-wide, maybe cannot get all employer reimbursement records before certification? But can propose damages model with individualized deductions post-certification. For named, need.

Need maybe include "If plaintiffs fail to produce, what relief?" Could seek: deny certification, preclude their testimony, adverse inference? But under rule 8, maybe "postpone or defeat". Need not overstate. Propose: if not produced, court may deny certification or, if certification proceeds, preclude reliance on their accounts; no assumption.

Need maybe include "21 days plan" with actual dates? Could use Day 1 etc. Maybe include sample deadlines: Order production by Day 14, briefing by Day 35? But question next 21 days. Need concrete within 21: file motion, meet confer, status conference, file opposition/conditional. Need maybe include if deferral granted, no merits opposition until production; but to avoid missing deadline, file short opposition or stipulate to extension? Let's think.

If opposition brief due in 21 days. If we file motion to defer briefing, court may grant and extend deadline. But until granted, deadline remains. To be safe, we should file a "Preliminary Opposition to Class Certification" or "Notice of Intent to Oppose and Motion for Deferral" before deadline. But maybe filing a motion to defer with a proposed order is enough? If court doesn't act, we could be in default. Better: File a concise opposition by day 21 that says (1) on present record, certification should be denied; (2) defendant moves to defer and compel targeted production; (3) if court grants deferral, this opposition is without prejudice and merits briefing should be stayed; (4) if court denies deferral, defendant submits this opposition (possibly supplemented) as its merits opposition. Need not full 50 pages; enough to preserve. But question asks "concrete filing sequence for next 21 days". We can recommend:
- By Day 2: Serve letter and file motion to defer/compel (with proposed order and exhibit list).
- By Day 5: Request status conference; if court sets hearing, brief.
- By Day 10: If no production, send follow-up; if production, review and prepare.
- By Day 20: File "Defendant's Opposition to Class Certification and Motion for Deferral/Compelled Production" (combined) if not yet filed. Or if motion already filed, file short opposition to class cert on present record.
- Day 21: File any required reply/status; ensure opposition on time.
But maybe filing motion first and opposition later is okay. Need maybe include "if court grants deferral, do not file full merits opposition; file status report."

Could we file only motion to defer and not opposition? If court denies before deadline, need opposition. Better combined.

Need maybe include "Do not request broad six-month stay; instead ask for a limited stay of certification briefing for 30-45 days pending targeted production." Good.

Need maybe include "immediate denial" argument: If court does not want discovery, deny now because named plaintiffs' claims are uncertain and class not predominance. But we can ask for deferral first, with denial alternative.

Need maybe include "full merits briefing now" not preferred because missing files essential; but we must be prepared. We can file present-record opposition.

Need maybe include "broad discovery" not preferred because overbroad, may be denied, and could delay. Targeted only.

Need maybe include "combine approaches" yes: limited deferral + targeted production + preserve denial + oppose now.

Need maybe include "what to file now" maybe:
1. Motion for Order (a) deferring certification briefing/hearing for limited period, (b) compelling production of specified named-plaintiff documents, (c) setting schedule, (d) preserving objection to full class.
2. A short "present-record opposition" or "notice of opposition" within deadline.
3. If court asks, a joint status report after production.

Need maybe include "proposed order language". Good.

Need maybe include "exhibit list" with document requests. Could be detailed.

Let's develop legal arguments in detail.

Governing law:
1. Certification requires standing, numerosity, commonality, typicality, adequacy.
2. Damages class: predominance and superiority.
3. Uniform material misrepresentation supports common proof; materially different disclosures etc require individualized proof/subclasses.
4. Consumer statute elements: exposure, causation, unreimbursed loss; reliance inferred only from materially uniform representation.
5. Contract: terms and assent; no recovery for knowingly separately selected enforceable disclosed term.
6. Damages model match theory; deduct refunds, chargebacks, employer reimbursements.
7. Named standing/typicality from evidence; material uncertainty may defeat/postpone.
8. Court may defer and compel targeted discovery if specific previously requested info essential; identify documents and significance; no broad delay.
9. Defendant must connect variations to elements/remedies.
10. Court may certify narrower issue class/subclasses.

Apply.

Standing/Typicality/Adequacy:
Need maybe separate each named:
Milo Chen:
- Standing: alleges mobile enrollment and charge. If he paid $7.95 and not refunded, injury. But no bank statement/refund record. On present record, payment may be in StreamLedger ledger; maybe enough? Rule 7 says evidence. We have ledger? It identifies 21,300 mobile customers charged; if Milo in it, that is evidence of charge. But refund status? Not known. Need bank/refund. If no refund, standing. But typicality/adequacy: mobile path; his uncertainty about preselected box and link means he cannot personally demonstrate the representation or assent. However if system records show mobile UI preselected and he didn't uncheck, typicality may be established. But present record lacks. Material uncertainty about enrollment path? He says mobile but not whether box selected; but mobile path is preselected. Maybe the fact he was charged implies selected. But his memory of link click relevant to whether he saw free option. For consumer statute, reliance may be inferred from materially uniform preselected presentation; individual link click maybe not needed. But typicality: if his claim is based on preselected box, he must show he was charged through that path. Account logs can. So maybe not fatal if records produced. On present record, postpone.
- Adequacy: If he cannot recall, can still be adequate if counsel proves with records. But memory gaps may suggest he cannot protect class? Not necessarily. Need say uncertainty about assent may make him less adequate; if records cure, okay.

Tara Vale:
- Standing: call-center, fee mandatory. Need show charge, no refund. Missing. Typicality: Cannot identify call/date/rep; six scripts. Without date, cannot show which script or if statement made. Her claim may be atypical if her call differs. She may be typical of a "call subclass" only if her call can be tied to a script. On present record, material uncertainty about enrollment path (which script) and representation. Adequacy: inability to identify call may impede proving common script; inadequate for call class.

Jae Morgan:
- Standing: alleges no refund, but ambiguous CB-R. If completed chargeback, no loss; if rejected, loss. Material uncertainty about personal loss. On present record, standing/typicality uncertain. Need ledger definition, bank statement, processor records. If completed chargeback, not injured. If rejected, injured. Adequacy: cannot represent unreimbursed loss class if his own loss disputed.

Overall adequacy: three reps from different paths; no representative for all. If full class, inadequate. If subclasses, need reps per subclass. Current set lacks desktop and legacy reps; Milo mobile (uncertain), Tara call (uncertain), Jae unclear path? Actually Jae no path specified? He alleges no refund; maybe could be any path. Need know. So inadequate.

Common questions:
Let's define:
Common across all class:
- Did StreamLedger charge $7.95 priority-processing fee? Yes, records.
- Were class members charged? Can identify.
- Did priority processing provide no benefit? Not common; backend shows weekdays 18h, weekends none. So no.
- Was one marketing page deceptive? Not common if enrollment varied.
- Average backend queue? Common performance data but not liability.
- Legal standards? Common.
But for certification, common factual questions must predominate. Here not.

Consumer statute by path:
Desktop: representation: separate unchecked box with clear statement. Materially deceptive? Likely no. Causation: customer checked; no inference. Contract: knowingly selected. Likely no class claims. If some argue box was misleading? But clear. Individualized.
Mobile: preselected box with link. Could be materially deceptive/omission if free option not salient. Common if all saw same. Causation: did preselection cause payment? Individual? Reliance inferred maybe if uniform. Need know if user unselected? Charged means selected. Need account logs. Damages individual. Subclass possible.
Legacy: fee only in linked service terms. Could be omission. Common if landing page uniform. Need original emails/landing page. Subclass possible.
Calls: six scripts, oral statements. Material uniformity unlikely. Need recordings/agent. Individualized. Maybe script subclasses if scripts common and records. Tara cannot identify.

Contract by path:
Desktop: terms presented and assented via check. No recovery if knowingly selected. Individual.
Mobile: preselected box disclosed; if enforceable term, customer proceeded; may be assent. But if preselection dark pattern, contract maybe still enforceable? Consumer claim. Individualized.
Legacy: terms linked; assent by using? Individualized.
Calls: oral terms; assent; individualized.

Predominance:
For all class, consumer: variations in disclosure, reliance, causation, contract, damages. Individualized predominate. Contract: terms/assent individual. Deny.
Narrowed: Mobile and legacy may have common liability; but damages still individual. Could issue class. Weekend no-benefit subclass maybe common damages? But disclosure still varies. Could combine: mobile weekend subclass? Too narrow? Maybe.

Effect of paths/scripts/performance/assent:
- Breaks common proof. Need connect to elements.

Refunds/chargebacks/employer/damages:
- Deduct. Need model.
- If class defined as all charged, damages not common due to 6,580 refunded/chargeback and 7,900 employer. Need individual.
- Could exclude refunded/chargeback and employer-reimbursed from class; but need data. Could define class as those with unreimbursed loss; but must identify. Need discovery.
- For weekday benefit, if theory no benefit, narrow to weekend or offset. Need date.
- Damages model: $7.95 less refunds/chargebacks/reimbursements/benefit offsets. Need class-wide data and notice.

Subclasses/issue classes:
- Path subclasses: desktop (probably exclude/no claim), mobile, legacy, call (maybe scripts). Each has common disclosure/assent issues. But named reps? Need.
- Issue class: liability for mobile/legacy; damages individual. Could cure disclosure variations. Call scripts maybe issue per script.
- Weekend/weekday damages issue: common no-benefit or benefit offset. Could cure performance variation.
- But cannot cure named plaintiff uncertainty without production.
- If issue class certified, need manage individual damages via records, sample, class notice.

Exact materials: as above.

Strategy:
- Immediate denial: viable if court refuses discovery; but limited deferral better because rule 8 and facts (promised files). We should not rely solely on denial because named uncertainty may be curable. But preserve denial.
- Broad six-month stay: not. Overbroad; rule 8. Could be denied and signal overreach.
- Full merits now: if court denies deferral; but better to avoid before targeted production.
- Combine: file limited motion to defer and compel; file present-record opposition; if production occurs, supplement.
Need maybe say "Move to defer certification briefing, not the whole case." "Compel production within 14-21 days." "No broad merits discovery." "If plaintiffs fail, seek denial."

Filing sequence:
Need concrete. Let's draft timeline:
Day 0/1:
- Send written meet-and-confer/production demand: specify documents (Exhibit A) and deadlines; note prior request 4 months ago and June 1 promise; ask produce by Day 10; state certification motion premature.
Day 2-3:
- File Defendant’s Motion for (1) Limited Deferral of Certification Briefing/Hearing, (2) Order Compelling Targeted Production, (3) Scheduling. Include proposed order and exhibit. Ask court to suspend opposition deadline until 21 days after production or Day 35/45. No broad stay.
Day 4-7:
- Request status conference; submit status letter with plaintiff’s response; if court asks, provide proposed schedule.
Day 5-10:
- Continue meet and confer; if plaintiffs produce, log receipt; if not, send letter preserving.
Day 10-14:
- If court grants deferral and no production, move for order to show cause? Maybe not. If production, review. If no production and no deferral, prepare opposition.
Day 15-20:
- File Defendant’s Opposition to Class Certification (or supplement) if required by deadline. It should: (a) on present record, deny certification due to standing/typicality/predominance; (b) state motion to defer pending; (c) if court denies deferral, defendant submits opposition; (d) if granted, opposition is preliminary and without prejudice.
Day 21:
- File any reply to plaintiff’s opposition to motion; status report; ensure compliance with court schedule.
Alternative: If court grants deferral immediately, no full merits opposition; file status report after production.

Need maybe include "If plaintiffs produce by Day 14, file a short status report and request 14-day supplemental briefing; if not, seek denial or preclusion."

Need maybe include "proposed targeted production list" in sequence.

Need maybe include "proposed order text":
"IT IS ORDERED:
1. Within 14 days, Plaintiffs shall produce, for each named plaintiff: [list].
2. Within 14 days, Defendant shall produce corresponding account and ledger extracts, call metadata/any retained recordings, refund/chargeback records, and performance timestamps for the named plaintiffs.
3. Certification briefing and hearing are stayed only until 21 days after substantial compliance (or [date]), not to exceed 30 days from this order.
4. If Plaintiffs fail to produce, the Court may deny certification or preclude reliance on the named plaintiffs’ accounts.
5. No broad merits discovery is authorized."
Need be careful: compelling defendant to produce? We can offer. The motion can ask court to order both parties? Since we control some. But targeted discovery from plaintiffs. We can also produce without order.

Need maybe include "Decisional significance" for each doc:
- Confirmation emails: establish representation/omission and fee disclosure (consumer statute exposure; contract terms).
- UI logs/screenshots: establish preselected/unchecked state, link clicks (mobile/desktop; contract assent; deception).
- Call logs/recordings: establish Tara's enrollment representation, script, causation.
- Bank/card statements: establish charge, date, card type, refund/chargeback (standing, loss, damages).
- Refund/chargeback records: establish unreimbursed loss; CB-R (Jae).
- Employer reimbursement: establish personal loss (consumer statute economic loss).
- Verification timestamps: establish benefit/no benefit and damages (weekday/weekend).
- Communications: establish reliance, refund requests, admissions.

Need maybe include "Without these, court cannot assess whether named plaintiffs are typical and whether common questions predominate." Good.

Potential nuance: Named plaintiffs' bank statements may be personal financial info; can they be compelled? For standing/damages, yes, with protective order. Need propose protective order and in camera if necessary. Could include "subject to protective order; redacted card numbers." Good.

Need maybe include "employer reimbursement records may be business records; protective order." Good.

Need maybe include "call recordings: if retained, produce; if not, produce logs and script versions." Good.

Need maybe include "StreamLedger's database should be enough" rebuttal: It shows aggregate and path counts but not the specific representation as presented to each named plaintiff (e.g., link click, exact call statement, refund status, employer reimbursement). Rule 7 requires evidence. Also for class-wide predominance, defendant's database can help but not replace named plaintiffs' proof of standing.

Need maybe include "Plaintiffs' argument missing docs are merits details" rebuttal: standing and typicality are class prerequisites, not merits; documents go to whether reps are proper and whether common proof possible. Rule 8.

Need maybe include "Do not overstate missing files will prove": We should phrase as "may establish or negate"; "We do not ask the court to infer nonproduction; we ask for targeted production so the court can decide." Good.

Need maybe include "If files show named plaintiffs are typical, what then?" We still argue full class fails due to predominance; invite narrowed subclass/issue class. This shows reasonableness.

Need maybe include "If files show no standing, immediate denial." Good.

Let's think of possible objections to motion to defer:
- Plaintiffs may say certification can proceed without documents; defendant should take depositions later. But rule 7 and 8 support. We can say limited, previously requested, promised, essential.
- Court may worry about delay. We propose short 14-21 day production and 21-day supplemental briefing, not six months.
- Court may say broad. We limit to three named plaintiffs and specific docs.
- Court may say defendant can produce its own database. We say database lacks personal control files and employer reimbursement; also named plaintiffs' files needed for standing.

Need maybe include "If court denies deferral, should we seek broad discovery?" No. We should proceed to merits opposition and if certification granted, seek post-certification discovery. But for now, targeted motion denied, so argue denial.

Need maybe include "Should StreamLedger move for immediate denial?" As alternative, yes in opposition: if court declines deferral, deny. But not as primary if deferral available.

Need maybe include "Should StreamLedger request broad six-month stay?" No.

Need maybe include "Should StreamLedger file full merits briefing now?" Only if court denies deferral or as conditional. Better to file present-record opposition.

Need maybe include "What if plaintiffs produce nothing after order?" Seek sanctions: denial, preclusion, adverse inference? Rule 8 says may defeat/postpone. Could propose denial. But not overstate. Need maybe "seek an order that failure to produce results in denial of certification or preclusion of the named plaintiffs' accounts; leave court to determine appropriate sanction." Good.

Need maybe include "Specific class definitions" maybe:
- Full proposed class fails.
- Possible viable: "all mobile customers who were presented with the preselected box during period and paid fee but were not refunded/chargeback and personally bore expense" maybe too complex. But for certification, subclass by path.
- "Weekend verification" subclass for no benefit? But if disclosure varies, combine with path: mobile/legacy weekend.
- Desktop likely no class.
- Call: maybe individual actions unless script subclass.

Need maybe include "Numerosity" each subclass large enough. But typicality reps lacking.

Need maybe include "Adequacy" for issue class: If issue class liability, reps need protect interest in liability; current reps may be okay for mobile if cured. But damages individual may create conflict? Not necessarily.

Need maybe include "Superiority" for subclass: If individual damages manageable via records, class superior. But for full class, not.

Need maybe include "common backend queue" significance: It may show fee processed through same system and average performance, but not that each saw deceptive representation. It can support common damages model for benefit if date known. But not enough.

Need maybe include "marketing page" significance: Not enrollment representation; may be common but not sufficient. If plaintiffs rely on marketing page, need show exposure. Not all customers saw it. So no common proof.

Need maybe include "uniform fee amount" common but not enough.

Need maybe include "deception caused payment" for preselected: If customer could unselect, did preselection cause? Individualized? Maybe common if many didn't unselect. Need account data. For calls, individual.

Need maybe include "relief" for consumer statute: full fee? Need deduct.

Need maybe include "contract claim: enforceable disclosed term" for mobile: preselected box plus link; if term enforceable, customer may not recover under contract. But consumer statute maybe separate. Need discuss.

Need maybe include "If customer knowingly and separately selected" desktop definitely. Mobile: not separately selected? Preselected; but they had opportunity to unselect. Could argue they didn't knowingly select because they didn't realize; but contract claim depends on terms presented and assented. If they assented by proceeding, maybe no. Individualized.

Need maybe include "oral communications" for calls: six scripts, sample recordings; individual. If some script said mandatory, deceptive; if others disclosed, not. Cannot infer uniform.

Need maybe include "assent records": Desktop checkbox, mobile preselected, legacy terms, call consent. Differ. Contract predominance poor.

Need maybe include "materially different disclosures may require subclasses" but "not cure all" because damages/loss individual.

Need maybe include "exact materials that matter" maybe in bullet with named-specific:
Milo: mobile transaction log showing preselected state and whether link opened; confirmation email; bank statement; refund records. Why: establish he was exposed to mobile representation, paid, not refunded; typicality.
Tara: bank statement date; call log/recording/agent/script; confirmation; refund records. Why: establish call representation mandatory, date/script, loss.
Jae: ledger CB-R definition; processor/bank statement; refund/chargeback record; employer records. Why: establish whether loss unreimbursed.
Class-wide: path counts, refund ledger, employer card list, performance timestamps. But named first.

Need maybe include "bank or card statements" can identify charge date for Tara, refund for Jae, employer card for all. Good.

Need maybe include "original confirmation emails" may be in plaintiffs' control; if not, defendant may have copies? But original.

Need maybe include "screenshots" if plaintiffs took; if not, UI logs.

Need maybe include "employer-reimbursement records" for named plaintiffs if employer card. We don't know which. But request all.

Need maybe include "communications concerning enrollment" e.g., call notes, emails.

Need maybe include "Do not request all customers' files now" to avoid broad. Only named plaintiffs. Maybe also class-wide summary records we control.

Need maybe include "If court orders production, plaintiffs should produce under oath certification of completeness." Good.

Need maybe include "Protective order" for bank/employer info.

Need maybe include "In camera review" for bank statements if privacy.

Need maybe include "If documents show the named plaintiffs were refunded/employer-paid, they lack standing; if show they were not typical, deny." Good.

Need maybe include "If documents show they are typical, still full class fails due to predominance; but subclass possible." Good.

Need maybe include "Filing sequence" with specific documents to file:
1. Motion (with proposed order) and exhibit: document request letter, prior request, certification motion, proposed order.
2. Memorandum in support.
3. Opposition? Could be combined or separate. Maybe "Defendant’s Preliminary Opposition to Class Certification" if not combined.
4. Status letter.
5. Supplemental opposition after production.

Need maybe include "If the court requires a reply to the plaintiffs’ opposition to certification, file by day 21." But plaintiffs filed certification motion; opposition due in 21 days. There may be reply to opposition later. We need file opposition now.

Need maybe include "Do not file a general motion for discovery." Good.

Need maybe include "Do not file for default or sanctions immediately; first order." Good.

Need maybe include "If plaintiffs already promised June 1, we can argue bad faith but avoid overstatement." Maybe mention "their June 1 promise makes targeted production feasible and short deferral appropriate." Not bad faith unless evidence.

Need maybe include "The missing files will not prove the merits" but they prove prerequisites. Good.

Let's draft final answer in a polished memo.

Potential final answer:

**Recommendation**: File a limited motion to defer certification briefing and compel targeted production, plus a present-record opposition. Do not seek six-month stay. Do not wait for full merits without preserving denial. Seek production within 14 days and supplemental briefing within 21 days after production.

Then detailed analysis.

Need ensure answer covers all bullets. Use headings.

Let's produce final with high detail.

Need maybe include "Assumptions" not necessary.

Let's think of possible subtlety: The consumer statute requires each claimant exposed to deceptive representation or omission, deception caused payment, unreimbursed economic loss. For class certification, common questions must predominate. If plaintiffs rely on one marketing page, but actual enrollment paths differ, maybe some customers not exposed to that page. Need show exposure individually. This is individualized. Good.

For mobile preselected, if all mobile saw same preselected box, that is materially uniform. Reliance may be inferred? Rule 4: reliance may be inferred only from materially uniform representation. If mobile UI uniform, yes. But causation? Preselected box may be representation; payment caused by not unchecking. Could be common. But still need individual proof that they were in mobile path and not refunded. That's manageable. So maybe mobile subclass could be certified after named files. We should not say impossible. Say possible but not current full class.

For legacy, fee only in linked terms. If uniform, materially uniform representation/omission. Reliance inferred? Maybe. But contract? Terms disclosed. Consumer maybe. Subclass possible.

For calls, six scripts: if some scripts materially similar, maybe subclass by script. But only sample recordings; need produce logs and scripts. Tara can't identify. So not current.

For desktop, clear unchecked: no deception; contract knowingly selected. Likely no class. But maybe if box was preselected? No, separate unchecked. So exclude.

Weekend/weekday: If claim is "no benefit", backend average contradicts weekdays. Could narrow to weekend verifications or allege benefit immaterial. If not, damages model must account. If benefit has no monetary value, maybe no offset? But economic loss? Need not decide. Say court should require plaintiffs to specify theory; if no-benefit, narrow; if fee deceptive regardless, damages still out-of-pocket less refunds. But backend may affect credibility/damages. Rule 6: damages model must match theory. If full refunds out-of-pocket, need deduct. If benefit offset, need model. Good.

Refunds: 5,400 full fee refunds and 1,180 chargebacks. If chargeback completed, customer got money back; no loss. If chargeback rejected, not. Ambiguous CB-R. Need definition. Employer cards: 7,900; field doesn't establish personal loss. Need individual. Could exclude business cards? But consumer statute for consumers? If paid on employer card and employer didn't reimburse, personal loss? Actually if employer card paid and employer absorbs cost, customer no personal loss. If customer reimburses employer, loss. Need records. Could maybe define class excluding employer card payments? But some employer card payments may be personal? The field identifies business-account; maybe business accounts? If business accounts, consumer class may not include. But fact: business-account field identifies payments made on employer cards; does not establish whether customer later reimbursed employer or personally bore expense. So need individual. Could exclude business-account payments from consumer class or require individual proof. Good.

Damages model: Need maybe propose:
- Step 1: Identify charged customers.
- Step 2: Deduct full refunds and completed chargebacks.
- Step 3: For employer-card customers, determine personal bearing via reimbursement records; exclude or offset.
- Step 4: Determine verification date and benefit; if no-benefit theory, restrict to weekend or deduct benefit.
- Step 5: Compute $7.95 per qualifying customer (or statutory measure). Need class notice.
This is individualized but can be done with records. For certification, need show manageable. But current missing named files.

Issue class: Could certify "liability issue" for mobile/legacy; then individual damages. But if damages not common, class action superiority? Issue class can be superior if individual damages are routine. Need mention.

Subclass cures: Path subclasses cure disclosure/assent; issue class cures liability vs damages; weekend subclass cures benefit. But cannot cure named plaintiff uncertainty or refunds/employer without data.

Filing sequence more concrete:
Maybe propose dates relative to June 3? Opposition due June 24? 21 days from June 3 is June 24. Could use "Day 1 = filing of certification motion" or actual dates. The facts: produced none and filed for certification on June 3. Opposition due in 21 days. So today likely June 3? We can use June 3-24. Need concrete: 
- June 3-4: Serve production demand/meet and confer.
- June 4-5: File limited motion with proposed order.
- June 5: Request status conference.
- June 10: If no production, follow-up letter; if court sets hearing, brief.
- June 12: If court grants, request production deadline June 17/19.
- June 17-19: Production deadline.
- June 20-23: Review; if no deferral, file opposition by June 24.
- June 24: File opposition or status.
But if court grants deferral, maybe no opposition. Need flexible.

Maybe better: "Within 21 days: file motion by day 3; file a short present-record opposition by day 20; if court grants deferral, treat opposition as conditional and file status after production." This is safe.

Need maybe include "proposed production deadline 10 days from order, supplemental briefing 14 days after production; total 30-40 days." Good.

Need maybe include "if court denies deferral, file full opposition by day 21." Good.

Need maybe include "if court orders production but not deferral, still produce and file opposition with any responsive facts." Good.

Need maybe include "Do not request immediate denial as sole relief; ask court to deny only if deferral/production denied or not complied." Good.

Need maybe include "Do not request broad six-month stay; request only stay of certification briefing, not all case." Good.

Need maybe include "Do not file motion for class discovery; that's post-certification." Good.

Need maybe include "If plaintiffs claim missing docs are merits, cite rule 7/8." Good.

Let's think if there is any issue with compelling named plaintiffs to produce account files before certification. Usually class representative's relevant documents can be discovery if relevant. But here court can defer. We can ask. Need identify documents. Good.

Need maybe include "targeted discovery from StreamLedger's own records"? We can produce voluntarily. But motion to compel named plaintiffs. Could also ask court to order StreamLedger to produce ledger extracts to avoid disputes. But not necessary. We can include as part of proposed schedule.

Need maybe include "CB-R code" specific: Need data dictionary, transaction ledger, processor statements. If code means completed chargeback, Jae no loss; if rejected, loss. Need bank statement showing credit/reversal. Good.

Need maybe include "Tara does not remember date or representative": Bank statement charge date can identify call date; call logs can identify agent; recordings if retained. If not, script version and agent notes. Without, cannot prove. Good.

Need maybe include "Milo does not remember whether box already selected or opened link": Mobile transaction log can show preselected state (by design) and link click; confirmation email. If he was charged, likely box selected. But need link? For deception, if he didn't open link, maybe reliance; if opened, maybe actual knowledge. Could affect contract? Need. Good.

Need maybe include "Jae alleges no refund": Ambiguous ledger; need payment processor and bank. Good.

Need maybe include "adequacy: named plaintiffs may have inconsistent interests: e.g., refunded members vs unreimbursed; call reps seeking oral proof vs UI reps; employer-paid vs personal." Good.

Need maybe include "If class includes every person charged, those refunded/chargeback/employer-paid have no loss; class definition overbroad. Need narrow to unreimbursed personal loss." But to define, need data. Could propose class definition: "customers who paid $7.95, were not refunded/completed chargeback, and personally bore cost." But need identify. For certification, maybe can define with records. But current missing. Good.

Need maybe include "The 7,900 employer-card payments may be business accounts, not consumers; if so, consumer class should exclude." Good.

Need maybe include "The 5,400 refunds and 1,180 chargebacks are about 10.5% of class; not trivial. Employer 12.7%. Combined >23% may lack loss. This affects predominance/damages." Could compute: 5,400+1,180=6,580 (10.5%); employer 7,900 (12.7%); overlaps possible. Could mention.

Need maybe include "Numerosity" each path > 9,000, so subclasses viable. Good.

Need maybe include "Commonality" maybe one common question: whether fee was disclosed materially? But path-specific. Not enough.

Need maybe include "Predominance for consumer statute if full class: individualized questions include: (1) which representation; (2) whether materially deceptive; (3) reliance; (4) causation; (5) whether refund/chargeback/employer; (6) whether benefit; (7) amount of loss." Good.

Need maybe include "Predominance for contract: (1) terms presented; (2) assent; (3) enforceability; (4) knowing selection; (5) damages." Good.

Need maybe include "Defendant's variations are not mere 'everyone different'; they tie to elements." Good.

Need maybe include "If court certifies issue class, ensure damages model matches and individual damages do not predominate." Good.

Need maybe include "Superiority": Full class not superior due to manageability; subclasses maybe. Broad discovery not superior. Targeted discovery superior.

Need maybe include "Filing sequence" maybe as a table.

Let's draft final answer with headings and tables. Need be thorough but not insanely long? Desired oververbosity 9, so detailed. We can produce long memo.

Potential final:

**Bottom line**:
- On present record, certification of all 62,400 should be denied or held for limited production.
- Do not seek six-month broad stay.
- File now: (1) targeted motion to defer and compel; (2) present-record opposition/conditional opposition.
- Seek production of specific named plaintiff files; after production, file supplemental opposition. If failure, seek denial.

Then analysis.

Let's ensure no missing bullet:
* Standing, typicality, adequacy each rep on present record. Covered.
* Which liability questions common and which enrollment path. Covered.
* Predominance consumer/contract. Covered.
* Effect of paths, scripts, weekday/weekend, assent. Covered.
* Refunds, chargebacks, employer, damages model. Covered.
* Issue class/subclasses cure. Covered.
* Exact named plaintiff materials and why. Covered.
* Whether move to defer/compel, oppose now, broad discovery, combine. Covered.
* Concrete filing sequence next 21 days without overstating. Covered.

Need maybe include "without overstating what missing files will prove" in strategy and filing: use language "may establish", "if", "court should not infer".

Let's write final.

Need maybe include citations to assumed rules (Rule 7, 8, etc.) not real cases. Good.

Let's produce final answer. Ensure no analysis in final. Use professional tone.

Double-check legal nuances:
- Standing: If named plaintiff was refunded, no injury. Jae ambiguous. Milo/Tara unknown. We can say if StreamLedger's ledger shows charge, standing as to payment may be established, but unreimbursed loss not. Rule 7 says evidence. Good.
- Typicality: For class, typical if claims arise from same conduct. If reps from different paths, not typical of all. Good.
- Adequacy: If reps cannot prove common facts, inadequate. Good.

Could there be an argument that named plaintiffs' lack of memory does not defeat standing because documents can prove; but rule 7 says material uncertainty may postpone. We should present as "postpone" rather than automatic fail. Good.

Need maybe mention "if the court is unwilling to defer, it should deny certification now, not certify on allegations." Good.

Need maybe mention "if documents show named plaintiffs are typical, the court should still not certify full class; should consider subclasses." Good.

Need maybe include "The complaint's allegation fee uniformly hidden is contradicted by desktop unchecked box and mobile link." Good.

Need maybe include "One marketing page and common backend queue are insufficient." Good.

Need maybe include "For contract claim, the fee was disclosed in all paths? Desktop explicit, mobile box/link, legacy terms, calls scripts maybe. So enforceable disclosed term may bar contract claim, especially desktop/mobile." Good.

Need maybe include "Consumer statute claim may survive for mobile/legacy/call misrepresentations but not uniform." Good.

Need maybe include "If call scripts materially vary, common proof of oral misrepresentation unavailable." Good.

Need maybe include "Weekend/weekday: complaint alleges no benefit; backend shows weekdays 18h. A class-wide no-benefit damages model is untenable. Either narrow to weekend or prove benefit immaterial/offset." Good.

Need maybe include "Refund/chargeback: 6,580 members likely no loss; cannot include in damages class without deduction." Good.

Need maybe include "Employer: 7,900 field not enough; need reimbursement. Could exclude business accounts or require individual proof." Good.

Need maybe include "Damages model: account-level calculation, not one-size." Good.

Need maybe include "Subclasses by path: desktop likely no; mobile, legacy, call scripts. Weekend/weekday issue. Refund/employer exclusion." Good.

Need maybe include "Issue class: liability for mobile/legacy; damages individual. Call script liability maybe." Good.

Need maybe include "Targeted production list" with exact documents. Good.

Need maybe include "Filing sequence" with day numbers. Good.

Let's write final now.