Forced action · Australia

Gamified or paid access coercion

Gamified or paid access coercion is a working label for this design mechanism: Desired functionality is practically conditioned on repetitive engagement or an additional payment not sufficiently clear at acquisition. This is editorial implementation guidance for Australian journeys, not a finding of unlawfulness. From 1 July 2027, a similar interface is relevant to ACL section 28B only if the complete consumer-connection, manipulation or unreasonable-distortion and actual-or-likely-detriment test is met. Current ACL rules require a separate assessment.

Editorial implementation guidance
Also known as
  • gamification
  • grinding
  • pay-to-play
  • repetitive grinding
  • paid bypass
  • function withheld after acquisition
  • daily-streak access
Journey stages

Definition

What is this pattern?

Desired functionality is practically conditioned on repetitive engagement or an additional payment not sufficiently clear at acquisition. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.

How it works

Desired functionality is practically conditioned on repetitive engagement or an additional payment not sufficiently clear at acquisition. A purchased or expected function is placed behind extra play, streak, points or payment mechanics that were not part of the user’s original access decision.

Warning signs

  • A concrete function is withheld or made impractical.
  • Repeated labour or additional payment is the effective unlock route.
  • The condition was unexpected, disproportionate or insufficiently disclosed.

Potential harms

  • Players may pay twice or spend unplanned time to reach content they reasonably understood was included.
  • Learners may be forced into additional engagement or lose a completion record they already earned.

Learn by comparison

What does this look like?

These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.

Illustrative example 1 · Energy gate before a purchased level

A fictional game sells a chapter pass but requires hours of repetitive daily tasks or another payment before the purchased final level becomes playable.

Potential consumer harm: Players may pay twice or spend unplanned time to reach content they reasonably understood was included.

Illustrative example 2 · Reward loop required for document export

A fictional study service makes certificate export depend on completing seven daily streak tasks that were not disclosed when the course was bought.

Potential consumer harm: Learners may be forced into additional engagement or lose a completion record they already earned.

What is a fairer alternative?

Disclose access conditions before acquisition and avoid making disproportionate repetition or surprise payment the practical path to expected functionality.

Context matters

Context and boundary cases

  • A concrete function is withheld or made impractical.
  • Repeated labour or additional payment is the effective unlock route.
  • The condition was unexpected, disproportionate or insufficiently disclosed.
  • Boundary to test: Ordinary progression intrinsic to a game and transparently described
  • Boundary to test: clearly disclosed optional cosmetic purchases

When a similar design can serve a legitimate purpose

  • Ordinary progression intrinsic to a game and transparently described
  • clearly disclosed optional cosmetic purchases

Operational review

What teams should review

Teams
  • Product
  • Design
  • Engineering
  • Legal
  • Compliance
  1. What functional need makes “Unlock boost $6” necessary for the mobile game goal, and can that need be met with less disclosure or commitment?
  2. Place the compared prices, billing periods and material terms on one evidence sheet; where does it support “A concrete function is withheld or made impractical”?
  3. Could the stated purpose make this dependency genuinely necessary under the boundary “Ordinary progression intrinsic to a game and transparently described”, and what product evidence would demonstrate that necessity?
  4. What functional need makes “Return tomorrow” necessary for the learning platform goal, and can that need be met with less disclosure or commitment?
  5. Test the control across refresh, device and account states; is “Repeated labour or additional payment is the effective unlock route” still observable after persistence is considered?
  6. Could the stated purpose make this dependency genuinely necessary under the boundary “clearly disclosed optional cosmetic purchases”, and what product evidence would demonstrate that necessity?

Evidence to retain

  • Annotated account management screenshots at each responsive breakpoint
  • The complete state sequence before, during and after the consumer decision
  • Design-system component, content, default and configuration records for the reviewed release
  • Operational records substantiating price, availability, timing and eligibility claims
  • Usability, accessibility, reversal, complaint and support evidence relevant to consumer impact
  • A dated product and legal review record identifying evidence, uncertainties and release decisions

Legal map and implementation tools

Evidence base

Sources

  1. Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
  2. Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064
  3. Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
  4. Unfair trading tricks and traps to be bannedTreasury Ministers · Primary · checked 2026-09-14
  5. Inquiry into the Competition and Consumer Amendment (Unfair Trading Practices) Bill 2026Senate Economics Legislation Committee · Primary · checked 2026-08-09