{"id":"sr:transport-compliance-and-miscellaneous-ticketing-regulations-2017","name":"Transport (Compliance and Miscellaneous) (Ticketing) Regulations 2017","slug":"transport-compliance-and-miscellaneous-ticketing-regulations-2017","collection":"regulation","jurisdiction":"vic","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":181625,"registerId":"vic-sr:transport-compliance-and-miscellaneous-ticketing-regulations-2017-current","compilationNumber":null,"startDate":"2026-04-05","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Part 1","sectionType":"part","heading":"Preliminary","content":"Part 1—Preliminary\n\n","sortOrder":0},{"sectionNumber":"1","sectionType":"section","heading":"Objectives","content":"\t1 Objectives\n\nThe objectives of these Regulations are—\n\n(a) to require and regulate the use of tickets for Victoria's public transport system; and\n\n(b) to support the collection of revenue for that system and reduce fare evasion and the consequential revenue losses incurred by public transport operators and the State; and\n\n(c) to clarify contractual arrangements in relation to certain tickets; and\n\n(d) to prescribe certain conditions and enforcement powers in relation to tickets; and\n\n(e) to specify the defences applying to ticket‑related offences; and\n\n(f) to prescribe other matters required, permitted or necessary to be prescribed by or under the **Transport (Compliance and Miscellaneous) Act 1983**.\n\n","sortOrder":1},{"sectionNumber":"2","sectionType":"section","heading":"Authorising provisions","content":"\t2 Authorising provisions\n\nThese Regulations are made under sections 56, 221AA and 230AH of the **Transport (Compliance and Miscellaneous) Act 1983**.\n\n","sortOrder":2},{"sectionNumber":"3","sectionType":"section","heading":"Commencement","content":"\t3 Commencement\n\nThese Regulations come into operation on 1 July 2017.\n\n","sortOrder":3},{"sectionNumber":"4","sectionType":"section","heading":"Revocation of Regulations","content":"\t4 Revocation of Regulations\n\nThe following regulations are **revoked**—\n\n(a) the Transport (Ticketing) Regulations 2006[[1]](#endnote-2);\n\n(b) the Transport (Ticketing) Amendment (Mykis and Other Smartcards) Regulations 2009[[2]](#endnote-3);\n\n(c) the Transport (Ticketing) Amendment (Portable Devices) Regulations 2010[[3]](#endnote-4);\n\n(d) the Transport (Compliance and Miscellaneous) (Ticketing) Amendment  \nRegulations 2011[[4]](#endnote-5);\n\n(e) the Transport (Conduct) and (Ticketing) Amendment (Protective Services Officers) Regulations 2011[[5]](#endnote-6);\n\n(f) the Transport (Conduct), (Passenger Vehicles) and (Ticketing) Amendment (Public Transport Development Authority) Regulations 2012[[6]](#endnote-7);\n\n(g) the Transport (Ticketing) Amendment Regulations 2013[[7]](#endnote-8);\n\n(h) the Transport (Ticketing) Amendment (On‑the-Spot Penalty Fares) Regulations 2014[[8]](#endnote-9);\n\n(i) the Transport (Ticketing) Amendment (Bus Drivers' Obligations) Regulations 2015[[9]](#endnote-10);\n\n(j) the Transport (Ticketing) Amendment (Prescribed Devices and Processes) Regulations 2015[[10]](#endnote-11);\n\n(k) the Transport (Ticketing) Amendment (Prescribed Devices and Processes) Regulations 2016[[11]](#endnote-12);\n\n(l) the Transport (Ticketing) Amendment (On‑the-Spot Penalty Fare Amount) Regulations 2016[[12]](#endnote-13);\n\n(m) the Transport (Ticketing) Further Amendment (Prescribed Devices and Processes) Regulations 2016[[13]](#endnote-14);\n\n(n) the Transport (Ticketing) Amendment (On‑the-Spot Penalty Fares Revocation) Regulations 2016[[14]](#endnote-15).\n\n","sortOrder":4},{"sectionNumber":"5","sectionType":"section","heading":"Definitions and reference provisions","content":"\t5 Definitions and reference provisions\n\n(1) In these Regulations—\n\n***authorised officer*** has the same meaning as in section 208 of the Act;\n\ndef. of *authorised person (ticketing)* amended by S.R. Nos 168/2019 reg. 5(a), 14/2026 reg. 5(c).\n\n***authorised person (ticketing)*** means—\n\n(a) an authorised officer; or\n\n(b) a police officer; or\n\n(c) a protective services officer; or\n\n(d) a person employed by a passenger transport company or a bus company who has duties in relation to the issue, inspection, scanning or collection of tickets and tokens for travel in a passenger vehicle or for entry to a compulsory ticket area; or\n\n(e) a person (other than a person referred to in paragraph (a) or (d)) appointed in writing by a passenger transport company or a bus company or the Secretary or the Head, Transport for Victoria for the purposes of these Regulations; or\n\n(f) if a bus company is a natural person, that person;\n\ndef. of *central computer system* amended by S.R. Nos 22/2019 reg. 5(1)(a), 57/2019 reg. 5(a), 168/2019 reg. 5(b), 14/2026 reg. 5(d).\n\n***central computer system*** means the central servers, computers, networks, other electronic data systems and other devices operated and maintained by or on behalf of the Head, Transport for Victoria to—\n\n(a) collect, manage, process, summarise and store information; and\n\n(b) settle financial transactions—\n\nrelating to smartcards, digital tokens and other prescribed devices;\n\ndef. of *compulsory ticket area* amended by S.R. Nos 22/2019 reg. 5(1)(b), 14/2026 reg. 5(e).\n\n***compulsory ticket area*** means—\n\n(a) an area of land or an area within premises owned or occupied by a passenger transport company that is designated by the passenger transport company by means of signs in or near the area as an area for entry to which a ticket valid for that entry is required; or\n\n(b) if a railway station is specified by the Secretary in a notice published in the Government Gazette as a station to which this paragraph applies—\n\n(i) a platform at that station; and\n\n(ii) a waiting room or area adjoining a platform from which the platform can be accessed without the need to pass a smartcard and digital token reader or a ticket barrier; and\n\n(iii) an area between a platform and any smartcard and digital token reader or ticket barrier that it is necessary to pass to gain access to the platform;\n\n***concession ticket*** means a ticket that, in accordance with conditions determined under section 220D of the Act—\n\n(a) authorises free travel, or travel at a price less than the full fare, in a passenger vehicle; or\n\n(b) authorises free entry, or entry at a price less than the full price for entry, to a compulsory ticket area;\n\ndef. of *digital card* inserted by S.R. No. 22/2019 reg. 5(2), amended by S.R. No. 129/2024 reg. 5(a), revoked by S.R. No. 14/2026 reg. 5(a).\n\nReg. 5(1) def. of *digital myki* inserted by S.R. No. 14/2026 reg. 5(b).\n\n***digital myki*** means a digital State token that is capable of—\n\n(a) recording a myki product or myki money; and\n\n(b) in respect of myki money—\n\n(i) recording the value of that myki money; and\n\n(ii) transferring information to other electronic devices so as to effect modifications to that value to reflect payment for travel in a passenger vehicle or entry to a compulsory ticket area; and\n\n(iii) recording that value as so modified—\n\nbut does not include a V/Line digital ticket;\n\nReg. 5(1) def. of *digital token* inserted by S.R. No. 14/2026 reg. 5(b).\n\n***digital token*** means a token that is—\n\n(a) a software application on a personal electronic device; or\n\n(b) another thing processed through a software application on a personal electronic device—\n\nthat may lawfully be used for the purpose of obtaining a ticket or proving the existence of a ticket but does not include a V/Line digital ticket;\n\ndef. of *digital top-up application* inserted by S.R. No. 87/2021 reg. 4, amended by S.R. No. 14/2026 reg. 5(f).\n\n***digital top-up application*** means a software application on a personal electronic device that may lawfully be used for the purpose of recording a myki product or myki money on a myki smartcard;\n\ndef. of *Handheld Retail* substituted by S.R. No. 6/2020 reg. 4.\n\n***Handheld Retail*** means—\n\n(a) a PSION WORKABOUT PRO S Model 7527S-G2; or\n\n(b) a ZEBRA Model TC77—\n\nthat is being used by or on behalf of a retail agent in the course of that retail agent's activities as a retail agent;\n\ndef. of *Handheld V/Line* amended by S.R. Nos 48/2023 reg. 4, 14/2026 reg. 5(g).\n\n***Handheld V/Line*** means an Axium EX8000 3GB or a ZEBRA Model TC77 that is being used by a V/Line conductor in the course of that conductor's duties as a conductor;\n\ndef. of *myki* substituted by S.R. No. 22/2019 reg. 5(3), revoked by S.R. No. 14/2026 reg. 5(a).\n\nReg. 5(1) def. of *myki bus ticketing equipment* amended by S.R. No. 14/2026 reg. 5(h).\n\n***myki bus ticketing equipment*** means equipment installed on a bus that enables a digital token or token that is a smartcard to be used to authorise travel in that bus;\n\nReg. 5(1) def. of *myki money* amended by S.R. Nos 57/2019 reg. 5(b), 168/2019 reg. 5(c), 14/2026 reg. 5(i).\n\n***myki money*** means a dollar amount paid to the Head, Transport for Victoria and recorded as value on a myki smartcard or digital myki;\n\nReg. 5(1) def. of *myki product* amended by S.R. No. 14/2026 reg. 5(j).\n\n***myki product*** means a pre-purchased or free entitlement, recorded on a myki smartcard or digital myki, to travel in a passenger vehicle or to enter a compulsory ticket area in accordance with conditions determined under section 220D of the Act;\n\nReg. 5(1) def. of *myki smartcard* inserted by S.R. No. 14/2026 reg. 5(b).\n\n***myki smartcard*** means a smartcard that is capable of—\n\n(a) recording a myki product or myki money; and\n\n(b) in respect of myki money—\n\n(i) recording the value of that myki money; and\n\n(ii) transferring information to other electronic devices so as to effect modifications to that value to reflect payment for travel in a passenger vehicle or entry to a compulsory ticket area; and\n\n(iii) recording that value as so modified;\n\n***operator access card*** means a plastic card that—\n\n(a) contains an imbedded computer microchip capable of receiving, storing, processing and transferring information; and\n\n(b) is used to identify the holder of the card to another prescribed device and enable the holder to operate the device;\n\n***passenger vehicle*** means any of the following that is operated by or on behalf of a passenger transport company or a bus company—\n\n(a) a passenger train;\n\n(b) a tram;\n\n(c) a bus;\n\ndef. of *personal electronic device* inserted by S.R. No. 22/2019 reg. 5(2), substituted by S.R. Nos 129/2024 reg. 5(b), 14/2026 reg. 5(k).\n\n***personal electronic device*** means an electronic device on which a ticket or token is capable of being stored and that contains one or more imbedded computer microchips capable of receiving, storing, processing and transferring information;\n\n***protective services officer***  has the same meaning as in the **Victoria Police Act 2013**;\n\n***regular passenger service*** has the same meaning as in the **Bus Services Act 1995**;\n\nReg. 5(1) def. of *retail agent* amended by S.R. Nos 57/2019 reg. 5(c), 168/2019 reg. 5(d), 14/2026 reg. 5(l).\n\n***retail agent*** means a person (other than a passenger transport company or a bus company) engaged by the Crown or the Head, Transport for Victoria to act as its agent in relation to the sale of State tokens and payment for travel in a passenger vehicle or entry to a compulsory ticket area;\n\nReg. 5(1) def. of *smartcard* inserted by S.R. No. 14/2026 reg. 5(b).\n\n***smartcard*** means a plastic card that contains an imbedded computer microchip capable of receiving, storing, processing and transferring information;\n\nReg. 5(1) def. of *smartcard and digital card reader* inserted by S.R. No. 129/2024 reg. 5(e), revoked by S.R. No. 14/2026 reg. 5(a).\n\nReg. 5(1) def. of *smartcard and digital token reader* inserted by S.R. No. 14/2026 reg. 5(b).\n\n***smartcard and digital token reader*** means a machine that, when a smartcard or digital token is scanned by the machine as part of the actions necessary for a ticket to be made valid for travel in a passenger vehicle or entry to a compulsory ticket area, regardless of whether or not at any particular time the machine is in working order, is designed and intended—\n\n(a) to electronically record and process information from a digital token or a token that is a smartcard; and\n\n(b) to perform related functions;\n\ndef. of *smartcard reader* amended by S.R. No. 22/2019 reg. 5(1)(c), revoked by S.R. No. 129/2024 reg. 5(c).\n\ndef. of *smartcard security access module* amended by S.R. Nos 22/2019 reg. 5(1)(d), 14/2026 reg. 5(m).\n\n***smartcard security access module*** means a computer microchip that stores security authentication and encryption keys that ensure that a prescribed device, when fitted with the smartcard security access module, is authorised to copy and transfer information between the prescribed device and—\n\n(a) a smartcard or digital token; and\n\n(b) the central computer system;\n\n***the Act*** means the **Transport (Compliance and Miscellaneous) Act 1983**;\n\nReg. 5(1) def. of *ticket* revoked by S.R. No. 14/2026 reg. 5(a).\n\n***ticket barrier*** means a barrier that is intended to be used to regulate access to or egress from a part of a railway station that is a compulsory ticket area;\n\n***train*** includes a single carriage (whether powered or not) that does not form part of a set or series of carriages;\n\n***vehicle control unit*** means a device installed on a bus or a tram that is capable of—\n\n(a) transferring or copying information stored by the device between prescribed devices installed on the bus or tram; and\n\n(b) transferring or copying information stored by the device between a prescribed device installed on the bus or tram and the central computer system; and\n\n(c) receiving information from a global positioning system and generating and storing information relating to the location of the bus or tram and transferring or copying such information to prescribed devices installed on the bus or tram;\n\nReg. 5(1) def. of *V/Line conductor* substituted by S.R. No. 55/2018 reg. 3(1).\n\n***V/Line conductor*** means a person employed by V/Line Corporation to perform duties as a conductor on trains operated by or on behalf of that company;\n\nReg. 5(1) def. of *V/Line Corporation* inserted by S.R. No. 55/2018 reg. 3(2), amended by S.R. No. 129/2024 reg. 5(d).\n\n***V/Line Corporation*** has the same meaning as in section 3 of the **Transport Integration Act 2010**;\n\nReg. 5(1) def. of *V/Line digital ticket* inserted by S.R. No. 129/2024 reg. 5(e), amended by S.R. No. 14/2026 reg. 5(n)(o).\n\n***V/Line digital ticket*** means a token with a barcode that can be displayed on a personal electronic device and which may lawfully be used for the purpose of proving an entitlement to travel in a passenger vehicle or entry to a compulsory ticket area.\n\n(2) For the purposes of these Regulations, the fact that a tramway is not laid entirely in public streets or roads does not prevent a vehicle running on that tramway from being characterised as a tram.\n\n(3) For the purposes of these Regulations, a person's travel in a passenger vehicle—\n\n(a) begins—\n\n(i) in the case of a bus, on the earlier of—\n\n(A) when the person, after boarding the bus, first moves past the driver's seat towards the back of the bus; or\n\n(B) when the bus first starts to move after the person has boarded the bus; or\n\n(ii) in all other cases, when the passenger vehicle first starts to move after the person has boarded the vehicle; and\n\n(b) ends when the person leaves the passenger vehicle.\n\n","sortOrder":5},{"sectionNumber":"6","sectionType":"section","heading":"Validity for travel or entry","content":"\t6 Validity for travel or entry\n\nFor the purposes of these Regulations—\n\n(a) a ticket is valid for the whole of a person's travel in a passenger vehicle if the ticket authorises the whole of that travel; and\n\n(b) a ticket is valid for a person's entry to a compulsory ticket area if the ticket authorises that entry to the compulsory ticket area; and\n\n(c) a ticket is not valid for the whole of a person's travel in a passenger vehicle if any part of that travel is not authorised by the ticket.\n\nExamples to reg. 6 amended by S.R. No. 22/2019 reg. 6, substituted by S.R. No. 14/2026 reg. 6.\n\n**Examples**\n\nFor the purposes of Division 2 of Part 2, examples of reasonable steps that may be available to make a ticket valid for travel include—\n\n- in the case of a digital myki or a token that is a myki smartcard, if required by the conditions determined under section 220D of the Act, to have recorded on the digital myki or myki smartcard a myki product or myki money of sufficient value to pay for the whole of the travel or entry to a compulsory ticket area and have the whole of the travel recorded on the digital myki or myki smartcard; and\n- in the case of a digital token or a token that is a smartcard (other than a digital myki or myki smartcard), if required by the conditions determined under section 220D of the Act, to have the digital token or smartcard scanned by a smartcard and digital token reader and made valid for travel or entry to a compulsory ticket area before commencing travel or, if travelling on a tram or a bus, on commencing travel or entering a compulsory ticket area.\n\nNote to reg. 6 inserted by S.R. No. 14/2026 reg. 6.\n\nSee regulation 7(3) which explains when a person has a ticket in the person's possession.\n\nPart 2—Valid ticket must be held and presented\n\nDivision 1—Obligations\n\n\t7 Obligation to hold valid ticket\n\n(1) A person who is travelling in a passenger vehicle must have in the person's possession a ticket that is valid for the whole of the person's travel in that passenger vehicle.\n\nRegulation 13 sets out the defence that may apply in respect of a charge under this subregulation.\n\n(2) A person who is in a compulsory ticket area must have in the person's possession a ticket that is valid for that entry to the compulsory ticket area.\n\nRegulation 14 sets out the defence that may apply in respect of a charge under this subregulation.\n\nReg. 7(3) substituted by S.R. Nos 22/2019 reg. 7, 129/2024 reg. 6, 14/2026 reg. 7(1).\n\n(3) For the purposes of this regulation, a person has a ticket in the person's possession only if—\n\n(a) the person holds on or about their person—\n\n(i) in the case of a digital token, the personal electronic device on which the token that proves the existence of a ticket is stored; or\n\n(ii) in the case of a V/Line digital ticket, a personal electronic device on which the V/Line digital ticket can be displayed; or\n\n(iii) in any other case, the token that proves the existence of a ticket; or\n\n(b) the person is accompanied by another person and that other person holds on or about their person on behalf of the first‑mentioned person—\n\n(i) in the case of a digital token, the personal electronic device on which the first-mentioned person's token that proves the existence of a ticket is stored; or\n\n(ii) in the case of a V/Line digital ticket, a personal electronic device on which the V/Line digital ticket can be displayed; or\n\n(iii) in any other case, the token that proves the existence of a ticket.\n\nExamples to reg. 7 amended by S.R. No. 14/2026 reg. 7(2).\n\n**Examples**\n\nFor the purposes of subregulation (3)(b), examples of another person holding a token on a person's behalf are—\n\n- a parent, foster carer or person who is granted guardianship of a child holding a token on behalf of a child; and\n- the holder of a token authorising group travel.\n\nSee regulation 6, which explains the meaning of valid for travel or valid for entry to a compulsory ticket area.\n\nReg. 8 (Heading) amended by S.R. No. 14/2026 reg. 8(1).\n\n","sortOrder":6},{"sectionNumber":"8","sectionType":"section","heading":"Obligation to produce a token that proves the existence of a ticket valid for travel","content":"\t8 Obligation to produce a token that proves the existence of a ticket valid for travel\n\nReg. 8(1) amended by S.R. No. 14/2026 reg. 8(2).\n\n(1) An authorised person (ticketing) may ask a person who is travelling in, or has just left, a passenger vehicle to produce for inspection a token that proves the existence of a ticket that is or was (as the case requires) valid for the whole of the person's travel in that passenger vehicle.\n\n(2) A person must without delay comply with a request made under subregulation (1).\n\nRegulation 13 sets out the defence that may apply in respect of a charge under this subregulation.\n\nReg. 9 (Heading) amended by S.R. No. 14/2026 reg. 9(1).\n\n","sortOrder":7},{"sectionNumber":"9","sectionType":"section","heading":"Obligation to produce a token that proves the existence of a ticket valid for entry to a compulsory ticket area","content":"\t9 Obligation to produce a token that proves the existence of a ticket valid for entry to a compulsory ticket area\n\nReg. 9(1) amended by S.R. No. 14/2026 reg. 9(2).\n\n(1) An authorised person (ticketing) may ask a person who is in, or has just left, a compulsory ticket area, to produce for inspection a token that proves the existence of a ticket that is or was (as the case requires) valid for that entry to the compulsory ticket area.\n\n(2) A person must without delay comply with a request made under subregulation (1).\n\nRegulation 14 sets out the defence that may apply in respect of a charge under this subregulation.\n\nReg. 9A (Heading) amended by S.R. Nos 129/2024 reg. 7(1), 14/2026 reg. 10(1).\n\nReg. 9A inserted by S.R. No. 22/2019 reg. 8, amended by S.R. Nos 103/2020 reg. 3, 129/2024 reg. 7(2)(3) (ILA s. 39B(2)).\n\n","sortOrder":8},{"sectionNumber":"9A","sectionType":"section","heading":"Production of digital token or a V/Line digital ticket for inspection","content":"\t9A Production of digital token or a V/Line digital ticket for inspection\n\nReg. 9A(1) substituted by S.R. No. 14/2026 reg. 10(2).\n\n(1) For the purposes of regulations 8 and 9, a person travelling using a digital token that proves the existence of a ticket produces that token for inspection if the person makes the personal electronic device on which the digital token is stored available to an authorised person (ticketing) so that the validity of the ticket can be electronically tested or read using a hand held reader or Handheld V/Line.\n\nReg. 9A(2) inserted by S.R. No. 129/2024 reg. 7(3), amended by S.R. No. 14/2026 reg. 10(3).\n\n(2) For the purposes of regulations 8 and 9, a person travelling using a V/Line digital ticket produces that V/Line digital ticket for inspection if the person displays the V/Line digital ticket on a personal electronic device when requested to do so by an authorised person (ticketing) and allows the authorised person (ticketing) to inspect and electronically read the V/Line digital ticket.\n\n","sortOrder":9},{"sectionNumber":"10","sectionType":"section","heading":"Obligation to produce evidence of entitlement to rely on a concession ticket for travel","content":"\t10 Obligation to produce evidence of entitlement to rely on a concession ticket for travel\n\n(1) If it appears to an authorised person (ticketing) that a person who is travelling in, or has just left, a passenger vehicle relies, or has relied (as the case requires), on a concession ticket for the person's travel, the authorised person (ticketing) may ask the person to produce for inspection evidence of the person's entitlement to rely on the concession ticket for the person's travel in that passenger vehicle.\n\n(2) Subregulation (1) does not apply if the concession ticket itself constitutes or contains evidence of the person's entitlement to rely on the concession ticket.\n\nExample to reg. 10(2) inserted by S.R. No. 14/2026 reg. 11.\n\n**Example**\n\nA police officer or protective services officer may access free travel by producing their Victoria Police identification. No token is required.\n\n(3) A person must without delay comply with a request made under subregulation (1).\n\n","sortOrder":10},{"sectionNumber":"11","sectionType":"section","heading":"Obligation to produce evidence of entitlement to rely on a concession ticket for entry to a compulsory ticket area","content":"\t11 Obligation to produce evidence of entitlement to rely on a concession ticket for entry to a compulsory ticket area\n\n(1) If it appears to an authorised person (ticketing) that a person who is in, or has just left, a compulsory ticket area relies or has relied  \n(as the case requires) on a concession ticket for the person's entry to the compulsory ticket area, the authorised person (ticketing) may ask the person to produce for inspection evidence of the person's entitlement to rely on the concession ticket.\n\n(2) Subregulation (1) does not apply if the concession ticket itself constitutes or contains evidence of the person's entitlement to rely on the concession ticket.\n\nExample to reg. 11(2) inserted by S.R. No. 14/2026 reg. 12.\n\n**Example**\n\nA police officer or protective services officer may enter a compulsory ticket area by producing their Victoria Police identification. No token is required.\n\n(3) A person must without delay comply with a request made under subregulation (1).\n\nReg. 12 (Heading) amended by S.R. No. 14/2026 reg. 13(1).\n\nReg. 12 substituted by S.R. Nos 22/2019 reg. 9, 129/2024 reg. 8, amended by S.R. No. 14/2026 reg. 13(2)(d).\n\n","sortOrder":11},{"sectionNumber":"12","sectionType":"section","heading":"Application of regulations 8 to 11 if a person's token etc. is held by another person","content":"\t12 Application of regulations 8 to 11 if a person's token etc. is held by another person\n\nFor the purposes of regulations 8(2), 9(2), 10(3) and 11(3), a person is taken to have complied with a request made under, respectively, regulation 8(1), 9(1), 10(1) or 11(1) if, at the time the request is made, another person, who is accompanying the person and is holding—\n\nReg. 12(a) amended by S.R. No. 14/2026 reg. 13(2)(a).\n\n(a) the relevant token; or\n\nReg. 12(b) substituted by S.R. No. 14/2026 reg. 13(2)(b).\n\n(b) in the case of a digital token, the personal electronic device on which the digital token is stored; or\n\nReg. 12(c) amended by S.R. No. 14/2026 reg. 13(2)(c).\n\n(c) in the case of a V/Line digital ticket, a personal electronic device on which the V/Line digital ticket can be displayed; or\n\n(d) evidence of entitlement—\n\non behalf of the first person, produces the token, personal electronic device, V/Line digital ticket or evidence for inspection by the authorised person (ticketing).\n\n","sortOrder":12},{"sectionNumber":"Div 2","sectionType":"division","heading":"Defences","content":"Division 2—Defences\n\nReg. 13 substituted by S.R. No. 14/2026 reg. 14.\n\n","sortOrder":13},{"sectionNumber":"13","sectionType":"section","heading":"Defence in relation to travel","content":"\t13 Defence in relation to travel\n\n(1) It is a defence to a charge under regulation 7(1) that the person charged took all reasonable steps that were available to have in the person's possession a ticket that was valid for the whole of the person's travel—\n\n(a) before commencing the travel; and\n\n(b) while undertaking the travel.\n\n(2) It is a defence to a charge under regulation 8(2) that the person charged took all reasonable steps that were available to produce for inspection a token that proves the existence of a ticket that was valid for the whole of the person's travel—\n\n(a) before commencing the travel; and\n\n(b) while undertaking the travel.\n\nReg. 14 substituted by S.R. No. 14/2026 reg. 14.\n\n","sortOrder":14},{"sectionNumber":"14","sectionType":"section","heading":"Defence in relation to entry to a compulsory ticket area","content":"\t14 Defence in relation to entry to a compulsory ticket area\n\n(1) It is a defence to a charge under regulation 7(2) that the person charged took all reasonable steps that were available to have in the person's possession a ticket that was valid for the entry—\n\n(a) before entering the compulsory ticket area; and\n\n(b) while the person was in the compulsory ticket area.\n\n(2) It is a defence to a charge under regulation 9(2) that the person charged took all reasonable steps that were available to produce for inspection a token that proves the existence of a ticket that was valid for the entry—\n\n(a) before entering the compulsory ticket area; and\n\n(b) while the person was in the compulsory ticket area.\n\nReg. 15 substituted by S.R. No. 14/2026 reg. 14.\n\n","sortOrder":15},{"sectionNumber":"15","sectionType":"section","heading":"Insufficient time not a defence","content":"\t15 Insufficient time not a defence\n\n(1) Without limiting the generality of regulations 13(1) and 14(1), for the purposes of those regulations, if the primary reason that the person did not possess a ticket valid for the travel or entry was because there was insufficient time to have such a ticket in the person's possession, the person did not take all reasonable steps that were available.\n\n(2) Without limiting the generality of regulations 13(2) and 14(2), for the purposes of those regulations, if the primary reason that the person did not produce for inspection a token that proves the existence of a ticket valid for the travel or entry was because there was insufficient time to have such a ticket in the person's possession, the person did not take all reasonable steps that were available.\n\nReg. 16 substituted by S.R. No. 14/2026 reg. 14.\n\n","sortOrder":16},{"sectionNumber":"16","sectionType":"section","heading":"Insufficient care not a defence","content":"\t16 Insufficient care not a defence\n\n(1) Without limiting the generality of regulations 13(1) and 14(1), for the purposes of those regulations, if the primary reason that the person did not possess a ticket valid for the travel or entry was because the person took insufficient care to ensure that the person had such a ticket in the person's possession, the person did not take all reasonable steps that were available.\n\n(2) Without limiting the generality of regulations 13(2) and 14(2), for the purposes of those regulations, if the primary reason that the person did not produce for inspection a token that proves the existence of a ticket valid for the travel or entry was because the person took insufficient care to ensure that the person had such a ticket in the person's possession, the person did not take all reasonable steps that were available.\n\nReg. 16A inserted by S.R. No. 22/2019 reg. 10, amended by S.R. No. 129/2024 reg. 9, substituted by S.R. No. 14/2026 reg. 14.\n\n","sortOrder":17},{"sectionNumber":"16A","sectionType":"section","heading":"Personal electronic device inoperable not a defence","content":"\t16A Personal electronic device inoperable not a defence\n\n(1) Without limiting the generality of regulations 13(1) and 14(1), for the purposes of those regulations, if, in the case of a ticket or purported ticket that is a digital token, the primary reason that the person did not possess a ticket valid for the travel or entry was because the personal electronic device on which the digital token is stored was inoperable, the person did not take all reasonable steps that were available.\n\n(2) Without limiting the generality of regulations 13(2) and 14(2), for the purposes of those regulations, if, in the case of a ticket or purported ticket that is a digital token, the primary reason that the person did not produce for inspection a token that proves the existence of a ticket valid for the travel or entry was because the personal electronic device on which the digital token is stored was inoperable, the person did not take all reasonable steps that were available.\n\n(3) Without limiting the generality of regulations 13(1) and 14(1), for the purposes of those regulations, if, in the case of a ticket or purported ticket that is a V/Line digital ticket, the primary reason that the person did not possess a ticket valid for the travel or entry was because a personal electronic device on which the V/Line digital ticket is capable of being displayed was inoperable, the person did not take all reasonable steps that were available.\n\n(4) Without limiting the generality of regulations 13(2) and 14(2), for the purposes of those regulations, if, in the case of a ticket or purported ticket that is a V/Line digital ticket, the primary reason that the person did not produce for inspection a token that proves the existence of a ticket valid for the travel or entry was because a personal electronic device on which the V/Line digital ticket is capable of being displayed was inoperable, the person did not take all reasonable steps that were available.\n\n","sortOrder":18},{"sectionNumber":"Part 3","sectionType":"part","heading":"Ticket contracts and conditions","content":"Part 3—Ticket contracts and conditions\n\n","sortOrder":19},{"sectionNumber":"17","sectionType":"section","heading":"Ticket contracts","content":"\t17 Ticket contracts\n\nReg. 17(1) amended by S.R. Nos 57/2019 reg. 6, 168/2019 reg. 6.\n\n(1) This regulation applies if a passenger transport company or a bus company is obliged under a contract with the Crown, or the Secretary on behalf of the Crown or the Head, Transport for Victoria, to accept for travel in the company's passenger vehicles or entry to the company's compulsory ticket areas a ticket that has not been issued by or on behalf of the company.\n\n(2) If a person enters one of the company's passenger vehicles or compulsory ticket areas in reliance on a ticket referred to in subregulation (1), on that entry there is taken to come into existence a contract between the company and the person for the travel in the passenger vehicle or entry to the compulsory ticket area (as the case requires).\n\n(3) If a person purchases a ticket referred to in subregulation (1) on one of the company's passenger vehicles for use in that vehicle, on that purchase there is taken to come into existence a contract between the company and the person for the travel in the passenger vehicle.\n\n(4) The terms of a contract referred to in subregulation (2) or (3) are taken to be all of the conditions to which the ticket is subject that are relevant to the travel in the passenger vehicle or entry to the compulsory ticket area, as the case may be.\n\n(5) A reference in this regulation—\n\n(a) to the company's passenger vehicles is a reference to any passenger vehicle operated by, or on behalf of, the company; and\n\n(b) to the company's compulsory ticket areas is a reference to any compulsory ticket area that is owned or occupied by the company.\n\n","sortOrder":20},{"sectionNumber":"18","sectionType":"section","heading":"Ticket conditions","content":"\t18 Ticket conditions\n\nA ticket is subject to the condition that the passenger transport company or bus company providing the service to which the ticket relates may alter the service during the currency of the ticket, including for example—\n\n(a) altering the mode of transport used to carry passengers; or\n\n(b) cancelling the service, wholly or in part; or\n\n(c) altering the point at which passengers will be picked up or set down.\n\n","sortOrder":21},{"sectionNumber":"Part 4","sectionType":"part","heading":"General","content":"Part 4—General\n\n","sortOrder":22},{"sectionNumber":"19","sectionType":"section","heading":"Ticket must not be transferred","content":"\t19 Ticket must not be transferred\n\n(1) A person who has begun to use a ticket that has not yet expired must not transfer that ticket to another person unless the conditions under which the ticket is issued permit the transfer.\n\n(2) A ticket is valid for travel in a passenger vehicle, or for entry to a compulsory ticket area, only by the person who has begun to use it or a person to whom it may be transferred in accordance with the conditions under which the ticket is issued.\n\nReg. 19(3) inserted by S.R. No. 22/2019 reg. 11, substituted by S.R. Nos 129/2024 reg. 10, 14/2026 reg. 15.\n\n(3) For the purposes of this regulation, a person does not transfer a V/Line digital ticket or a digital token that proves the existence of a ticket to another person only by giving the personal electronic device on which the V/Line digital ticket is capable of being displayed or the digital token is stored to that person for a purpose other than to authorise travel in a passenger vehicle or entry to a compulsory ticket area.\n\nReg. 20 (Heading) amended by S.R. No. 14/2026 reg. 16(1).\n\nReg. 20 amended by S.R. Nos 150/2018 reg. 3, 14/2026 reg. 16(2).\n\n","sortOrder":23},{"sectionNumber":"20","sectionType":"section","heading":"Testing of token","content":"\t20 Testing of token\n\nIf a token is produced for inspection under regulation 8 or 9, the authorised person (ticketing) may, unless the authorised person (ticketing) is a protective services officer, electronically test or read the token at the place where the inspection is being made.\n\nReg. 21 (Heading) amended by S.R. No. 14/2026 reg. 17(1).\n\n","sortOrder":24},{"sectionNumber":"21","sectionType":"section","heading":"Token must be surrendered","content":"\t21 Token must be surrendered\n\nReg. 21(1) amended by S.R. Nos 22/2019 reg. 12, 129/2024 reg. 11, substituted by S.R. No. 14/2026 reg. 17(2).\n\n(1) An authorised officer, a police officer or a protective services officer may request the holder of a token that proves or purports to prove the existence of a ticket to surrender the token or purported token to the officer if the officer believes on reasonable grounds that the token or purported token may be required as evidence or that its surrender is otherwise necessary for the enforcement of the Act or these Regulations.\n\nReg. 21(1A) inserted by S.R. No. 14/2026 reg. 17(2).\n\n(1A) Subregulation (1) does not apply in relation to a token or purported token that is—\n\n(a) a smartcard that is not a State token; or\n\n(b) a digital token; or\n\n(c) a V/Line digital ticket; or\n\n(d) a software application or another form of token on a personal electronic device.\n\nReg. 21(2) amended by S.R. No. 14/2026 reg. 17(3).\n\n(2) The holder of a token or purported token must without delay comply with a request made under subregulation (1).\n\nReg. 21(3) amended by S.R. No. 14/2026 reg. 17(4).\n\n(3) An authorised officer, a police officer or a protective services officer to whom a token or purported token is surrendered under subregulation (1) must, at the time of the surrender, give to the holder of the token or purported token a receipt for the token or purported token.\n\nReg. 21(4) amended by S.R. No. 14/2026 reg. 17(5).\n\n(4) A request must not be made under subregulation (1) for the surrender of a token unless a condition determined under section 220D of the Act specifies whether, if such a token is surrendered, the token will be replaced or a refund will be made, to the extent of the whole or part of any unused value remaining on the token at the time of surrender.\n\n","sortOrder":25},{"sectionNumber":"22","sectionType":"section","heading":"Additional ticketing requirements for buses","content":"\t22 Additional ticketing requirements for buses\n\n(1) A person must, at the same time as requesting a concession ticket, show the driver evidence of the person's entitlement to rely on a concession ticket for the travel if the person—\n\n(a) boards a bus for travel in respect of which a ticket is required; and\n\n(b) requests from the driver the concession ticket for that travel.\n\n(2) Subregulation (1) does not apply unless a sign stating that evidence of a person's entitlement to rely on a concession ticket must be shown to the driver when a concession ticket is requested from the driver is placed in the bus so that it is clearly visible by a person who requests a ticket from the driver.\n\n","sortOrder":26},{"sectionNumber":"23","sectionType":"section","heading":"Bus drivers' ticketing obligations","content":"\t23 Bus drivers' ticketing obligations\n\n(1) This regulation applies to the driver of a bus operated for the purpose of a regular passenger service if myki bus ticketing equipment is not installed on that bus.\n\n(2) If a person who boards a bus does not hold a ticket that is valid for the whole of that person's travel in the bus, the driver must, unless there is a reasonable excuse for the driver not to do so—\n\n(a) request that the person pay the correct fare for the whole of the person's travel in the bus, unless the person has already paid the correct fare; and\n\n(b) on payment of the correct fare for the whole of the person's travel in the bus, issue the person with a ticket authorising that travel.\n\n(3) If a person referred to in subregulation (2) does not take a ticket issued under subregulation (2)(b), the driver must, unless there is a reasonable excuse for the driver not to do so, immediately tear the ticket in half and ensure that the pieces of the ticket are left in the tray beside the driver that is used for the exchange of cash, tickets and other items between the driver and passengers until the person's travel in the bus ends.\n\nReg. 24 amended by S.R. No. 22/2019 reg. 13, revoked by S.R. No. 103/2020 reg. 4.\n\nReg. 25 revoked by S.R. No. 103/2020 reg. 4.\n\n","sortOrder":27},{"sectionNumber":"26","sectionType":"section","heading":"Convictions or findings of guilt for certain offences","content":"\t26 Convictions or findings of guilt for certain offences\n\n(1) If a person commits an offence against more than one of regulation 7(1), 8(2), 10(3) or 22(1) in respect of the same travel in a passenger vehicle, the person must not be convicted or found guilty of more than one of those offences.\n\n(2) If a person commits an offence against more than one of regulation 7(2), 9(2) or 11(3) in respect of the same entry to a compulsory ticket area, the person must not be convicted or found guilty of more than one of those offences.\n\n","sortOrder":28},{"sectionNumber":"27","sectionType":"section","heading":"Exemptions","content":"\t27 Exemptions\n\nRegulations 7, 8, 9 and 22 do not apply in relation to anything done or omitted to be done by—\n\n(a) a police officer, a protective services officer or an authorised officer acting in the course of their duties; or\n\n(b) a person employed by a passenger transport company or a bus company acting in the course of the person's duties; or\n\n(c) a person (other than a person referred to in paragraph (a) or (b)) who is authorised in writing to do or not do the thing by—\n\n(i) a passenger transport company or a bus company in respect of that company's passenger vehicles or compulsory ticket areas owned or occupied by that company; or\n\nReg. 27(c)(ii) substituted by S.R. No. 168/2019 reg. 7(a).\n\n(ii) the Secretary or the Head, Transport for Victoria; or\n\nReg. 27(d) substituted by S.R. No. 168/2019 reg. 7(b).\n\n(d) a person travelling in a passenger vehicle or in a compulsory ticket area if the passenger transport company, the bus company, the Secretary or the Head, Transport for Victoria has determined that a ticket is not required for that travel or that entry to the compulsory ticket area.\n\n**Examples for paragraph (d)**\n\n• Free travel to a major event.\n\n• The Heritage City Circle Tram Service.\n\nPt 5 (Heading) amended by S.R. No. 14/2026 reg. 20.\n\n","sortOrder":29},{"sectionNumber":"Part 5","sectionType":"part","heading":"Prescribed devices, tokens and processes","content":"Part 5—Prescribed devices, tokens and processes\n\n","sortOrder":30},{"sectionNumber":"28","sectionType":"section","heading":"Prescribed kinds of portable device","content":"\t28 Prescribed kinds of portable device\n\nFor the purposes of the definition of ***hand held reader*** in section 208 of the Act, each of the following is a prescribed kind of portable device—\n\nReg. 28(a) revoked by S.R. No. 22/2018 reg. 4.\n\nReg. 28(ab) inserted by S.R. No. 48/2023 reg. 5.\n\n(ab) the ZEBRA Model TC77;\n\nReg. 28(b) substituted by S.R. No. 14/2026 reg. 18.\n\n(b) the Axium EX8000 3GB.\n\nReg. 28A inserted by S.R. No. 14/2026 reg. 21.\n\n","sortOrder":31},{"sectionNumber":"28A","sectionType":"section","heading":"Prescribed tokens","content":"\t28A Prescribed tokens\n\nFor the purposes of paragraph (b)(i) of the definition of ***token*** in section 208 of the Act, the following things are prescribed—\n\n(a) a credit card or debit card that is a smartcard that—\n\n(ii) is capable of being processed through the Visa or Mastercard payment card network;\n\n(b) a credit card or debit card that is stored in, or accessed through, a digital wallet or mobile payment application  that—\n\n(ii) is capable of being processed through the Visa or Mastercard payment card network;\n\n(c) a prepaid card that is a smartcard that—\n\n(ii) is capable of being processed through the Visa or Mastercard payment card network; and\n\n(iii) is issued—\n\n(A) in the case of Mastercard, in Australia; or\n\n(B) in the case of Visa, in Australia or the Asia Pacific;\n\n(d) a prepaid card that is stored in, or accessed through, a digital wallet or mobile payment application  that—\n\n(ii) is capable of being processed through the Visa or Mastercard payment card network; and\n\n(iii) is issued—\n\n(A) in the case of Mastercard, in Australia; or\n\n(B) in the case of Visa, in Australia or the Asia Pacific.\n\nReg. 29 amended by S.R. No. 22/2019 reg. 14 (ILA s. 39B(2)).\n\n","sortOrder":32},{"sectionNumber":"29","sectionType":"section","heading":"Prescribed devices","content":"\t29 Prescribed devices\n\n(1) The devices set out in the Table in Schedule 1 are prescribed devices for the purposes of sections 230AB, 230AD and 230AE of the  \nAct.\n\nReg. 29(2) inserted by S.R. No. 22/2019 reg. 14, amended by S.R. No. 14/2026 reg. 19.\n\n(2) A computer microchip which enables a digital token to be stored on a personal electronic device is a prescribed device for the purposes of sections 230AD and 230AE of the Act.\n\n","sortOrder":33},{"sectionNumber":"30","sectionType":"section","heading":"Prescribed processes","content":"\t30 Prescribed processes\n\n(1) The processes set out in Schedule 2 are prescribed processes for the purposes of Division 5 of Part VII of the Act.\n\n(2) For the purposes of a process referred to in subregulation (1), the central computer system is a prescribed computer system.\n\nSch. 1 amended by S.R. Nos 22/2018 reg. 5, 6/2020 reg. 5, 22/2025 reg. 4, 14/2026 reg. 22.\n\n","sortOrder":34},{"sectionNumber":"Sch 1","sectionType":"schedule","heading":"Prescribed devices","content":"Schedule 1—Prescribed devices\n\nRegulation 29\n\n**Table**\n\n| *Item* | *Device* |\n| 1 | The device known as a TTA: ACS Expert 900 Melbourne: CVM/AVM-s, also known as a myki machine (stationary), if fitted with an operational smartcard security access module. |\n| 2 | The device known as a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC, also known as a Bus Driver Console, if fitted with an operational smartcard security access module. |\n| 3 | The device known as a Parkeon (Wayfarer) TCON product Melbourne: Depot Card Management Console, also known as a Depot Card Management Console, if fitted with an operational smartcard security access module. |\n| 4 | The device known as a Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC, also known as a Tram Driver Console, if fitted with an operational smartcard security access module. |\n| 5 | The device known as a Parkeon (Wayfarer) ICON Product Melbourne: Secondary Tram Driver Console TDC, if fitted with an operational smartcard security access module. |\n| 6 | The device known as an ACS Product family EVD121 Melbourne: Standalone Enquiry Machine (SEM), if fitted with an operational smartcard security access module. |\n| 7 | The device known as a Melbourne: Ticket Office Machine (Terminal) Fixed (TOM/TOT-F), if fitted with an operational smartcard security access module. |\n| 8 | The device known as a Melbourne: Ticket Office Machine (Terminal) Mobile (TOM/TOT-M), if fitted with an operational smartcard security access module. |\n| 9 | The device known as a Melbourne: Ticket Office Machine (Terminal) Smart Card Management Terminal (TOM SMT), if fitted with an operational smartcard security access module. |\n| 10 | The device known as an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 11 | The device known as an ACS Product family EVD141 Melbourne: Fare Payment Device Stationary, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 12 | The device known as an ACS Product family EVD360 Melbourne: Fare Payment Device Mobile, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 13 | The device known as a PSION WORKABOUT PRO S Model 7527S-G2, if fitted with an operational smartcard security access module. |\n| 14 | The device known as an ACS Electronic Validation Device EVD340, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 15 | An operator access card. |\n| 16 | A vehicle control unit. |\n| 17 | The device known as a Vix Product family iVal CR6000 Fare Payment Device, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 18 | The device known as a Vix Product family iVal CP6500 Fare Payment Device, also known as a myki reader, if fitted with an operational smartcard security access module. |\n| 19 | The device known as a Vix Product family DC6000 Primary Tram Driver Console, also known as a TDC, if fitted with an operational smartcard security access module. |\n| 20 | The device known as a Vix Product family DC6000 Secondary Tram Driver Console, also known as a TDC, if fitted with an operational smartcard security access module. |\n| 21 | The device known as a Vix Product family DC6000 Bus Driver Console, also known as a BDC, if fitted with an operational smartcard security access module. |\n| 22 | The device known as a Vix Product family PCP6200, also known as a Quick Topup and Enquiry Machine (QTEM), also known as a myki machine (stationary), if fitted with an operational smartcard security access module. |\n| 23 | The device known as a ZEBRA Model TC77, if fitted with an operational smartcard security access module. |\n| 24 | The device known as a Conduent Mixed Driver Console 430 (MDC430) Primary Tram Driver Console, also known as a TDC. |\n| 25 | The device known as a Conduent Mixed Driver Console 430 (MDC430) Secondary Tram Driver Console, also known as a TDC. |\n| 26 | The device known as a Conduent Mixed Driver Console 430 (MDC430) Bus Driver Console, also known as a BDC. |\n| 27 | The device known as a Conduent VPE430 Universal Validator, also known as a myki reader or an EMV token reader, if fitted with an operational smartcard security access module or commissioned with Open Payment production keys, or both. |\n| 28 | The device known as a Conduent CAS430 Universal Platform Validator, also known as a myki reader or an EMV token reader, if fitted with an operational smartcard security access module or commissioned with Open Payment production keys, or both. |\n| 29 | The device known as an Axium EX8000 3GB, also known as a hand held reader, if fitted with an operational smartcard security access module, or commissioned with Open Payment production keys, or both. |\n\n","sortOrder":35},{"sectionNumber":"Sch 2","sectionType":"schedule","heading":"Prescribed processes","content":"Schedule 2—Prescribed processes\n\nRegulation 30\n\n**Information transferred etc. to and from myki machines**\n\n1 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 1(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a TTA: ACS Expert 900 Melbourne: CVM/AVM-s and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 1(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 1(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a TTA: ACS Expert 900 Melbourne: CVM/AVM-s information relating to one or a combination of the following—\n\nSch. 2 item 1(a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 1(a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a TTA: ACS Expert 900 Melbourne: CVM/AVM-s;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n2 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 2(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 2(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a TTA: ACS Expert 900 Melbourne: CVM/AVM-s;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\nSch. 2 item 2A inserted by S.R. No. 22/2018 reg. 6.\n\n","sortOrder":36},{"sectionNumber":"2A","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"2A The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 2A(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Vix Product family PCP6200 and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 2A (a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 2A (a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a Vix Product family PCP6200 information relating to one or a combination of the following—\n\nSch. 2 item 2A (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 2A (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(B) the use of myki smartcards;\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Vix Product family PCP6200;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\nSch. 2 item 2B inserted by S.R. No. 22/2018 reg. 6.\n\n","sortOrder":37},{"sectionNumber":"2B","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"2B The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 2B(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 2B(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Vix Product family PCP6200;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n**Information transferred etc. to and from bus driver consoles**\n\n3 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus one or a combination of the following—\n\n(b) storing by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC either or both of the following—\n\n(ii) information generated by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC relating to the location of that bus;\n\n(c) copying information stored as described in paragraph (b) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that bus.\n\n4 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC;\n\n(c) transferring or copying the information stored as described in paragraph (b) to a vehicle control unit installed on that bus;\n\n(d) storing information transferred or copied as described in paragraph (c) by that vehicle control unit;\n\n(e) transferring or copying the information stored as described in paragraph (d) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that bus.\n\n5 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus one or a combination of the following—\n\n(b) storing by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC either or both of the following—\n\n(ii) information generated by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC relating to the location of that bus;\n\n(c) either or both of the following—\n\nSch. 2 item 5(c)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 5(c)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 5(c)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC information relating to one or a combination of the following—\n\nSch. 2 item 5(c)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 5(c)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(d) storing information copied, transferred or loaded as described in paragraph (c) by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC;\n\n(e) transferring or copying information stored as described in paragraph (b) or (d) by means of either or both a wired or wireless network to the central computer system;\n\n6 The process containing the steps set out in the following paragraphs—\n\n(a) one or a combination of the following—\n\n(i) loading onto a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus information relating to one or a combination of the following—\n\n(A) the vehicle identification of that bus;\n\n(B) the route of that bus;\n\n(C) the location of that bus;\n\nSch. 2 item 6(a)(ii) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) copying or transferring, between a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 6(a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 6(a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(iii) loading onto a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC information relating to one or a combination of the following—\n\nSch. 2 item 6(a)(iii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 6(a)(iii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information loaded, copied or transferred as described in paragraph (a) by that Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC;\n\n(c) transferring or copying information stored as described in paragraph (b) to a vehicle control unit installed on that bus;\n\n(e) transferring or copying information stored as described in paragraph (d) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":38},{"sectionNumber":"7","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"7 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 7(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 7(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on a bus;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n8 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 8(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 8(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a vehicle control unit installed on a bus;\n\n(d) storing information copied as described in paragraph (c) by that vehicle control unit;\n\n(e) transferring or copying information stored as described in paragraph (d) to a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on that bus;\n\n(f) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n(g) producing a printed record of information stored as described in paragraph (b) or (f).\n\n9 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Vix Product family DC6000 Bus Driver Console installed on a bus one or a combination of the following—\n\n(b) storing by that Vix Product family DC6000 Bus Driver Console either or both of the following—\n\n(ii) information generated by that Vix Product family DC6000 Bus Driver Console relating to the location of that bus;\n\n(c) copying information stored as described in paragraph (b) to a Vix Product family iVal CP6500 Fare Payment Device installed on that bus.\n\n10 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Vix Product family DC6000 Bus Driver Console installed on a bus one or a combination of the following—\n\n(b) storing by that Vix Product family DC6000 Bus Driver Console either or both of the following—\n\n(ii) information generated by that Vix Product family DC6000 Bus Driver Console relating to the location of that bus;\n\n(c) either or both of the following—\n\nSch. 2 item 10(c)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between that Vix Product family DC6000 Bus Driver Console and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 10(c)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 10(c)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto that Vix Product family DC6000 Bus Driver Console information relating to one or a combination of the following—\n\nSch. 2 item 10 (c)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 10 (c)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(d) storing information copied, transferred or loaded as described in paragraph (c) by that Vix Product family DC6000 Bus Driver Console;\n\n(e) transferring or copying information stored as described in paragraph (b) or (d) by means of either or both a wired or wireless network to the central computer system;\n\n11 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 11(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 11(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Vix Product family DC6000 Bus Driver Console installed on a bus;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\nSch. 2 item 11A inserted by S.R. No. 22/2025 reg. 5(a).\n\n","sortOrder":39},{"sectionNumber":"11A","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"11A The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Conduent Mixed Driver Console 430 Bus Driver Console installed on a bus one or a combination of the following—\n\n(b) storing by that Conduent Mixed Driver Console 430 Bus Driver Console either or both of the following—\n\n(ii) information generated by that Conduent Mixed Driver Console 430 Bus Driver Console relating to the location of that bus;\n\n(c) copying information stored as described in paragraph (b) to a Conduent VPE430 Universal Validator installed on that bus.\n\nSch. 2 item 11B inserted by S.R. No. 22/2025 reg. 5(a).\n\n","sortOrder":40},{"sectionNumber":"11B","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"11B The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Conduent Mixed Driver Console 430 Bus Driver Console installed on a bus one or a combination of the following—\n\n(b) storing by that Conduent Mixed Driver Console 430 Bus Driver Console either or both of the following—\n\n(ii) information generated by that Conduent Mixed Driver Console 430 Bus Driver Console relating to the location of that bus;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n**Information transferred etc. to and from a vehicle control unit installed on a bus**\n\n12 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a vehicle control unit installed on a bus information from a global positioning system relevant to determining the location of that bus;\n\n(b) storing by that vehicle control unit information generated by that vehicle control unit relating to the location of that bus;\n\n(c) transferring or copying the information stored as described in paragraph (b) to a Parkeon (Wayfarer) TCON product Melbourne: Bus Driver Console BDC installed on that bus or to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that bus.\n\n**Information transferred etc. to and from an operator access card**\n\n13 The process containing the steps set out in the following paragraphs—\n\n(a) loading information relating to the unique identifying number assigned to an authorised officer or the driver of a bus or a tram onto a Parkeon (Wayfarer) TCON product Melbourne: Depot Card Management Console;\n\n(b) transferring or copying the information loaded as described in paragraph (a) to an operator access card;\n\n(c) storing the information transferred or copied as described in paragraph (b) by that operator access card;\n\n(d) copying the information stored as described in paragraph (c) between that operator access card and another prescribed device so as to give the authorised officer or driver access to that other prescribed device;\n\n(e) storing the information copied as described in paragraph (d) by the other prescribed device referred to in paragraph (d);\n\n(f) transferring or copying information stored as described in paragraph (e) by means of either or both a wired or wireless network to the central computer system;\n\n(g) storing information transferred or copied as described in paragraph (f) by the central computer system;\n\n(h) producing a printed record of information stored as described in paragraph (g).\n\n**Information transferred etc. to and from primary tram driver consoles**\n\n14 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC installed on a tram one or a combination of the following—\n\n(b) storing by that Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC either or both of the following—\n\n(ii) information generated by that Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC relating to the location of that tram;\n\n(c) copying information stored as described in paragraph (b) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that tram.\n\n15 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC installed on a tram information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC;\n\n(c) transferring or copying information stored as described in paragraph (b) to a vehicle control unit installed on that tram;\n\n(e) transferring or copying the information stored as described in paragraph (d) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that tram.\n\n16 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC installed on a tram information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n17 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC installed on a tram information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Parkeon (Wayfarer) ICON Product Melbourne: Primary Tram Driver Console TDC;\n\n(c) transferring or copying information stored as described in paragraph (b) to a vehicle control unit installed on that tram;\n\n(e) transferring or copying information stored as described in paragraph (d) by means of either or both a wired or wireless network to the central computer system;\n\n18 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Vix Product family DC6000 Primary Tram Driver Console installed on a tram one or a combination of the following—\n\n(b) storing by that Vix Product family DC6000 Primary Tram Driver Console either or both of the following—\n\n(ii) information generated by that Vix Product family DC6000 Primary Tram Driver Console relating to the location of that tram;\n\n(c) copying information stored as described in paragraph (b) to a Vix Product family iVal CP6500 Fare Payment Device installed on that tram.\n\n19 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Vix Product family DC6000 Primary Tram Driver Console installed on a tram information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Vix Product family DC6000 Primary Tram Driver Console;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\nSch. 2 item 19A inserted by S.R. No. 22/2025 reg. 5(b).\n\n","sortOrder":41},{"sectionNumber":"19A","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"19A The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Conduent Mixed Driver Console 430 Primary Tram Driver Console installed on a tram one or a combination of the following—\n\n(b) storing by that Conduent Mixed Driver Console 430 Primary Tram Driver Console either or both of the following—\n\n(ii) information generated by that Conduent Mixed Driver Console 430 Primary Tram Driver Console relating to the location of that tram;\n\n(c) copying information stored as described in paragraph (b) to a Conduent VPE430 Universal Validator installed on that tram.\n\nSch. 2 item 19B inserted by S.R. No. 22/2025 reg. 5(b).\n\n","sortOrder":42},{"sectionNumber":"19B","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"19B The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a Conduent Mixed Driver Console 430 Primary Tram Driver Console installed on a tram information relating to either or both of the following—\n\n(b) storing information loaded as described in paragraph (a) by that Conduent Mixed Driver Console 430 Primary Tram Driver Console;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n**Information transferred etc. to and from a vehicle control unit installed on a tram**\n\n20 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto a vehicle control unit installed on a tram information from a global positioning system relevant to determining the location of that tram;\n\n(b) storing by that vehicle control unit information generated by that vehicle control unit relating to the location of that tram;\n\n(c) transferring or copying the information stored as described in paragraph (b) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on that tram.\n\n**Information transferred etc. to and from ticket office machines**\n\n21 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 21(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Melbourne: Ticket Office Machine (Terminal) Fixed (TOM/TOT-F) and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 21(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 21(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a Melbourne: Ticket Office Machine (Terminal) Fixed (TOM/TOT-F) information relating to one or a combination of the following—\n\nSch. 2 item 21 (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 21 (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Melbourne: Ticket Office Machine (Terminal) Fixed (TOM/TOT-F);\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n22 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 22(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 22(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Melbourne: Ticket Office Machine (Terminal) Fixed (TOM/TOT-F);\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n23 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 23(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Melbourne: Ticket Office Machine (Terminal) Mobile (TOM/TOT-M) and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 23(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 23(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a Melbourne: Ticket Office Machine (Terminal) Mobile (TOM/TOT-M) information relating to one or a combination of the following—\n\nSch. 2 item 23 (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 23 (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Melbourne: Ticket Office Machine (Terminal) Mobile (TOM/TOT-M);\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":43},{"sectionNumber":"24","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"24 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 24(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 24(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Melbourne: Ticket Office Machine (Terminal) Mobile (TOM/TOT-M);\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":44},{"sectionNumber":"25","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"25 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 25(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Melbourne: Ticket Office Machine (Terminal) Smart Card Management Terminal (TOM SMT) and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 25(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 25(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a Melbourne: Ticket Office Machine (Terminal) Smart Card Management Terminal (TOM SMT) information relating to one or a combination of the following—\n\nSch. 2 item 25 (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 25 (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Melbourne: Ticket Office Machine (Terminal) Smart Card Management Terminal (TOM SMT);\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n26 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 26(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 26(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Melbourne: Ticket Office Machine (Terminal) Smart Card Management Terminal (TOM SMT);\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n**Information transferred etc. to and from myki readers**\n\n27 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 27(a) amended by S.R. Nos 22/2019 reg. 15(a)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a bus and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 27(a)(iv) amended by S.R. Nos 22/2019 reg. 15(a)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 27(a)(v) amended by S.R. Nos 22/2019 reg. 15(a)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a bus information relating to one or a combination of the following—\n\nSch. 2 item 27(b)(iv) amended by S.R. Nos 22/2019 reg. 15(a)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 27(b)(v) amended by S.R. Nos 22/2019 reg. 15(a)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n28 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 28(a) amended by S.R. Nos 22/2019 reg. 15(b)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a bus and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 28(a)(iv) amended by S.R. Nos 22/2019 reg. 15(b)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 28(a)(v) amended by S.R. Nos 22/2019 reg. 15(b)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a bus information relating to one or a combination of the following—\n\nSch. 2 item 28(b)(iv) amended by S.R. Nos 22/2019 reg. 15(b)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 28(b)(v) amended by S.R. Nos 22/2019 reg. 15(b)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) to a vehicle control unit installed on that bus;\n\n(e) transferring or copying information stored as described in paragraph (d) by means of either or both a wired or wireless network to the central computer system;\n\n29 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 29(a) amended by S.R. Nos 22/2019 reg. 15(c)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a tram and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 29(a)(iv) amended by S.R. Nos 22/2019 reg. 15(c)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 29(a)(v) amended by S.R. Nos 22/2019 reg. 15(c)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a tram information relating to one or a combination of the following—\n\nSch. 2 item 29(b)(iv) amended by S.R. Nos 22/2019 reg. 15(c)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 29(b)(v) amended by S.R. Nos 22/2019 reg. 15(c)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n30 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 30(a) amended by S.R. Nos 22/2019 reg. 15(d)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a tram and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 30(a)(iv) amended by S.R. Nos 22/2019 reg. 15(d)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 30(a)(v) amended by S.R. Nos 22/2019 reg. 15(d)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on a tram information relating to one or a combination of the following—\n\nSch. 2 item 30(b)(iv) amended by S.R. Nos 22/2019 reg. 15(d)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 30(b)(v) amended by S.R. Nos 22/2019 reg. 15(d)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) to a vehicle control unit installed on that tram;\n\n(e) transferring or copying information stored as described in paragraph (d) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":45},{"sectionNumber":"31","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"31 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 31(a)(i) amended by S.R. Nos 22/2019 reg. 15(e), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 31(a)(ii) amended by S.R. Nos 22/2019 reg. 15(e), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":46},{"sectionNumber":"32","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"32 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 32(a)(i) amended by S.R. Nos 22/2019 reg. 15(f), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 32(a)(ii) amended by S.R. Nos 22/2019 reg. 15(f), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a vehicle control unit installed on a bus or a tram;\n\n(d) storing the information copied as described in paragraph (c) by that vehicle control unit;\n\n(e) transferring the information stored as described in paragraph (d) to an ACS Product family EVD240 Melbourne: Fare Payment Device Mobile installed on the bus or the tram (as the case may be);\n\n(f) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n(g) producing a printed record of information stored as described in paragraph (b) or (f).\n\n","sortOrder":47},{"sectionNumber":"33","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"33 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 33(a) amended by S.R. Nos 22/2019 reg. 15(g)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Vix Product family iVal CP6500 Fare Payment Device installed on a bus and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 33(a)(iv) amended by S.R. Nos 22/2019 reg. 15(g)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 33(a)(v) amended by S.R. Nos 22/2019 reg. 15(g)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by a Vix Product family iVal CP6500 Fare Payment Device installed on a bus information relating to one or a combination of the following—\n\nSch. 2 item 33(b)(iv) amended by S.R. Nos 22/2019 reg. 15(g)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 33(b)(v) amended by S.R. Nos 22/2019 reg. 15(g)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":48},{"sectionNumber":"34","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"34 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 34(a) amended by S.R. Nos 22/2019 reg. 15(h)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Vix Product family iVal CP6500 Fare Payment Device installed on a tram and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 34(a)(iv) amended by S.R. Nos 22/2019 reg. 15(h)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 34(a)(v) amended by S.R. Nos 22/2019 reg. 15(h)(i), 14/2026 reg. 23(1)(3).\n\n(b) storing by a Vix Product family iVal CP6500 Fare Payment Device installed on a tram information relating to one or a combination of the following—\n\nSch. 2 item 34(b)(iv) amended by S.R. Nos 22/2019 reg. 15(h)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 34(b)(v) amended by S.R. Nos 22/2019 reg. 15(h)(ii), 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":49},{"sectionNumber":"35","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"35 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 35(a)(i) amended by S.R. Nos 22/2019 reg. 15(i), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 35(a)(ii) amended by S.R. Nos 22/2019 reg. 15(i), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Vix Product family iVal CP6500 Fare Payment Device;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":50},{"sectionNumber":"36","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"36 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 36(a) amended by S.R. Nos 22/2019 reg. 15(j)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD141 Melbourne: Fare Payment Device Stationary and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 36(a)(i) amended by S.R. Nos 22/2019 reg. 15(j)(i), 14/2026 reg. 23(1)(3).\n\nch. 2 item 36(a)(ii) amended by S.R. Nos 22/2019 reg. 15(j)(i), 14/2026 reg. 23(1)(3).\n\n(iv) the location of that ACS Product family EVD141 Melbourne: Fare Payment Device Stationary;\n\n(b) storing by an ACS Product family EVD141 Melbourne: Fare Payment Device Stationary information relating to one or a combination of the following—\n\nSch. 2 item 36(b)(i) amended by S.R. Nos 22/2019 reg. 15(j)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 36(b)(ii) amended by S.R. Nos 22/2019 reg. 15(j)(ii), 14/2026 reg. 23(2)(4).\n\n(iv) the location of that ACS Product family EVD141 Melbourne: Fare Payment Device Stationary;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":51},{"sectionNumber":"37","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"37 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 37(a)(i) amended by S.R. Nos 22/2019 reg. 15(k), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 37(a)(ii) amended by S.R. Nos 22/2019 reg. 15(k), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to an ACS Product family EVD141 Melbourne: Fare Payment Device Stationary;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":52},{"sectionNumber":"38","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"38 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 38(a) amended by S.R. Nos 22/2019 reg. 15(l)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Product family EVD360 Melbourne: Fare Payment Device Mobile and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 38(a)(i) amended by S.R. Nos 22/2019 reg. 15(l)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 38(a)(ii) amended by S.R. Nos 22/2019 reg. 15(l)(i), 14/2026 reg. 23(1)(3).\n\n(iv) the location of that ACS Product family EVD360 Melbourne: Fare Payment Device Mobile;\n\n(b) storing by an ACS Product family EVD360 Melbourne: Fare Payment Device Mobile information relating to one or a combination of the following—\n\nSch. 2 item 38(b)(i) amended by S.R. Nos 22/2019 reg. 15(l)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 38(b)(ii) amended by S.R. Nos 22/2019 reg. 15(l)(ii), 14/2026 reg. 23(2)(4).\n\n(iv) the location of that ACS Product family EVD360 Melbourne: Fare Payment Device Mobile;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":53},{"sectionNumber":"39","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"39 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 39(a)(i) amended by S.R. Nos 22/2019 reg. 15(m), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 39(a)(ii) amended by S.R. Nos 22/2019 reg. 15(m), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to an ACS Product family EVD360 Melbourne: Fare Payment Device Mobile;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":54},{"sectionNumber":"40","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"40 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 40(a) amended by S.R. Nos 22/2019 reg. 15(n)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between an ACS Electronic Validation Device EVD340 and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 40(a)(i) amended by S.R. Nos 22/2019 reg. 15(n)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 40(a)(ii) amended by S.R. Nos 22/2019 reg. 15(n)(i), 14/2026 reg. 23(1)(3).\n\n(iv) the location of that ACS Electronic Validation Device EVD340;\n\n(b) storing by an ACS Electronic Validation Device EVD340 information relating to one or a combination of the following—\n\nSch. 2 item 40(b)(i) amended by S.R. Nos 22/2019 reg. 15(n)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 40(b)(ii) amended by S.R. Nos 22/2019 reg. 15(n)(ii), 14/2026 reg. 23(2)(4).\n\n(iv) the location of that ACS Electronic Validation Device EVD340;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":55},{"sectionNumber":"41","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"41 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 41(a)(i) amended by S.R. Nos 22/2019 reg. 15(o), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 41(a)(ii) amended by S.R. Nos 22/2019 reg. 15(o), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to an ACS Electronic Validation Device EVD340;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":56},{"sectionNumber":"42","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"42 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 42(a) amended by S.R. Nos 22/2019 reg. 15(p)(i), 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Vix Product family iVal CR6000 Fare Payment Device and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 42(a)(i) amended by S.R. Nos 22/2019 reg. 15(p)(i), 14/2026 reg. 23(1)(3).\n\nSch. 2 item 42(a)(ii) amended by S.R. Nos 22/2019 reg. 15(p)(i), 14/2026 reg. 23(1)(3).\n\n(iv) the location of that Vix Product family iVal CR6000 Fare Payment Device;\n\n(b) storing by a Vix Product family iVal CR6000 Fare Payment Device information relating to one or a combination of the following—\n\nSch. 2 item 42(b)(i) amended by S.R. Nos 22/2019 reg. 15(p)(ii), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 42(b)(ii) amended by S.R. Nos 22/2019 reg. 15(p)(ii), 14/2026 reg. 23(2)(4).\n\n(iv) the location of that Vix Product family iVal CR6000 Fare Payment Device;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":57},{"sectionNumber":"43","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43(a)(i) amended by S.R. Nos 22/2019 reg. 15(q), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43(a)(ii) amended by S.R. Nos 22/2019 reg. 15(q), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Vix Product family iVal CR6000 Fare Payment Device;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\nSch. 2 item 43A inserted by S.R. No. 22/2025 reg. 5(c).\n\n","sortOrder":58},{"sectionNumber":"43A","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43A The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43A(a) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Conduent VPE430 Universal Validator installed on a bus and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 43A(a)(iv) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\nSch. 2 item 43A(a)(v) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(b) storing by a Conduent VPE430 Universal Validator installed on a bus information relating to one or a combination of the following—\n\nSch. 2 item 43A(b)(iv) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43A(b)(v) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\nSch. 2 item 43B inserted by S.R. No. 22/2025 reg. 5(c).\n\n","sortOrder":59},{"sectionNumber":"43B","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43B The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43B(a) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Conduent VPE430 Universal Validator installed on a tram and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 43B(a)(iv) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\nSch. 2 item 43B(a)(v) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(b) storing by a Conduent VPE430 Universal Validator installed on a tram information relating to one or a combination of the following—\n\nSch. 2 item 43B(b)(iv) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43B(b)(v) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\nSch. 2 item 43C inserted by S.R. No. 22/2025 reg. 5(c).\n\n","sortOrder":60},{"sectionNumber":"43C","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43C The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43C(a)(i) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43C(a)(ii) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Conduent VPE430 Universal Validator;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\nSch. 2 item 43D inserted by S.R. No. 22/2025 reg. 5(c).\n\n","sortOrder":61},{"sectionNumber":"43D","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43D The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43D(a) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(a) copying or transferring, between a Conduent CAS430 Universal Platform Validator and a myki smartcard or digital myki, information relating to one or a combination of the following—\n\nSch. 2 item 43D(a)(i) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\nSch. 2 item 43D(a)(ii) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(iv) the location of that Conduent CAS430 Universal Platform Validator;\n\n(b) storing by a Conduent CAS430 Universal Platform Validator information relating to one or a combination of the following—\n\nSch. 2 item 43D(b)(i) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43D(b)(ii) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(iv) the location of that Conduent CAS430 Universal Platform Validator;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\nSch. 2 item 43E inserted by S.R. No. 22/2025 reg. 5(c).\n\n","sortOrder":62},{"sectionNumber":"43E","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"43E The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 43E(a)(i) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\nSch. 2 item 43E(a)(ii) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Conduent CAS430 Universal Platform Validator;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n**Information transferred etc. to and from hand held devices**\n\n","sortOrder":63},{"sectionNumber":"44","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"44 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 44(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Handheld Retail and a myki smartcard, information relating to one or a combination of the following—\n\nSch. 2 item 44(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 44(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a Handheld Retail information relating to one or a combination of the following—\n\nSch. 2 item 44 (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 44 (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Handheld Retail;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":64},{"sectionNumber":"45","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"45 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 45(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 45(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Handheld Retail;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\n","sortOrder":65},{"sectionNumber":"46","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"46 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 46(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a Handheld V/Line and a myki smartcard, information relating to one or a combination of the following—\n\n(A) the vehicle identification of a train;\n\n(B) the route of that train;\n\n(C) the location of that train;\n\nSch. 2 item 46(a)(i)(D) amended by S.R. No. 14/2026 reg. 23(3).\n\n(D) that myki smartcard;\n\nSch. 2 item 46(a)(i)(E) amended by S.R. No. 14/2026 reg. 23(3).\n\n(E) the use of that myki smartcard;\n\n(ii) loading onto a Handheld V/Line information relating to one or a combination of the following—\n\n(A) the vehicle identification of a train;\n\n(B) the route of that train;\n\n(C) the location of that train;\n\nSch. 2 item 46 (a)(ii)(D) amended by S.R. No. 14/2026 reg. 23(4).\n\n(D) myki smartcards;\n\nSch. 2 item 46 (a)(ii)(E) amended by S.R. No. 14/2026 reg. 23(4).\n\n(E) the sale and use of myki smartcards;\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a Handheld V/Line;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":66},{"sectionNumber":"47","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"47 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 47(a)(i) amended by S.R. Nos 22/2019 reg. 15(r), 14/2026 reg. 23(2)(4).\n\nSch. 2 item 47(a)(ii) amended by S.R. Nos 22/2019 reg. 15(r), 14/2026 reg. 23(2)(4).\n\n(c) copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to a Handheld V/Line;\n\n(d) storing by the central computer system information relating to the copying of the information copied as described in paragraph (c);\n\nSch. 2 item 47A inserted by S.R. No. 48/2023 reg. 6\n\n","sortOrder":67},{"sectionNumber":"47A","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"47A The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 47A(a)(i) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(i) copying or transferring, between a ZEBRA Model TC77  and a myki smartcard or a digital myki, information relating to one or a combination of the following—\n\n(A) the vehicle identification of a bus, train or tram;\n\n(B) the route of that bus, train or tram;\n\n(C) the location of that bus, train or tram;\n\nSch. 2 item 47A (a)(i)(D) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(D) that myki smartcard or digital myki;\n\nSch. 2 item 47A (a)(i)(E) amended by S.R. No. 14/2026 reg. 23(1)(3).\n\n(E) the use of that myki smartcard or digital myki;\n\n(ii) loading onto a ZEBRA Model TC77 information relating to one or a combination of the following—\n\n(A) the vehicle identification of a bus, train or tram;\n\n(B) the route of that bus, train or tram;\n\n(C) the location of that bus, train or tram;\n\nSch. 2 item 47A (a)(ii)(D) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(D) myki smartcards or digital myki;\n\nSch. 2 item 47A (a)(ii)(E) amended by S.R. No. 14/2026 reg. 23(2)(4).\n\n(E) the sale and use of myki smartcards or digital myki;\n\n(b) storing information copied, transferred or loaded as described in paragraph (a) by a ZEBRA Model TC77;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":68},{"sectionNumber":"48","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"48 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 48(a) amended by S.R. No. 14/2026 reg. 23(3).\n\n(a) copying from a myki smartcard produced to an authorised officer for inspection to a hand held reader being used by that authorised officer for the purposes of that inspection information relating to one or a combination of the following—\n\nSch. 2 item 48(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) that myki smartcard;\n\nSch. 2 item 48(a)(ii) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) the use of that myki smartcard;\n\n(iv) the vehicle identification of a train, tram or bus;\n\n(v) the route of a train, tram or bus;\n\n(vi) the location of a train, tram or bus;\n\nSch. 2 item 48(a)(vii) amended by S.R. No. 14/2026 reg. 23(3).\n\n(vii) the location of a prescribed device (other than that myki smartcard or that hand held reader);\n\n(b) storing information copied as described in paragraph (a) by that hand held reader;\n\n(c) transferring or copying information stored as described in paragraph (b) by means of either or both a wired or wireless network to the central computer system;\n\n","sortOrder":69},{"sectionNumber":"49","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"49 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 49(a) amended by S.R. No. 14/2026 reg. 23(3).\n\n(a) copying from a myki smartcard produced to an authorised officer for inspection to a hand held reader being used by that authorised officer for the purposes of that inspection information relating to one or a combination of the following—\n\nSch. 2 item 49(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) that myki smartcard;\n\nSch. 2 item 49(a)(ii) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) the use of that myki smartcard;\n\n(iv) the vehicle identification of a train, tram or bus;\n\n(v) the route of a train, tram or bus;\n\n(vi) the location of a train, tram or bus;\n\nSch. 2 item 49(a)(vii) amended by S.R. No. 14/2026 reg. 23(3).\n\n(vii) the location of a prescribed device (other than that myki smartcard or that hand held reader);\n\n(b) storing information copied as described in paragraph (a) by that hand held reader;\n\n(c) producing a printed record of information stored as described in paragraph (b).\n\n**Transfer etc. of information relating to the operation of prescribed devices**\n\n","sortOrder":70},{"sectionNumber":"50","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"50 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 50(a) amended by S.R. No. 14/2026 reg. 23(3).\n\n(a) transferring information relating to the operation of a prescribed device (other than a myki smartcard) from that prescribed device by means of either or both a wired or wireless network to the central computer system;\n\n(b) storing information transferred as described in paragraph (a) by the central computer system;\n\n(c) producing a printed record of information stored as described in paragraph (b).\n\n","sortOrder":71},{"sectionNumber":"51","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"51 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 51(a) amended by S.R. No. 14/2026 reg. 23(3).\n\n(a) storing by the central computer system information generated by the central computer system relating to the operation of a prescribed device (other than a myki smartcard);\n\n(b) producing a printed record of information stored as described in paragraph (a).\n\nSch. 2 Heading preceding item 52 inserted by S.R. No. 87/2021 reg. 5.\n\n**Information transferred etc. to and from digital top-up application and central computer system**\n\nSch. 2 item 52 inserted by S.R. No. 87/2021 reg. 5.\n\n","sortOrder":72},{"sectionNumber":"52","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"\t52 The process containing the steps set out in the following paragraphs—\n\nSch. 2 item 52(a)(i) amended by S.R. No. 14/2026 reg. 23(3).\n\n(i) copying or transferring, between a digital top-up application  and a myki smartcard, information relating to one or more of the following—\n\nSch. 2 item 52(a)(i)(A) amended by S.R. No. 14/2026 reg. 23(3).\n\nSch. 2 item 52(a)(i)(B) amended by S.R. No. 14/2026 reg. 23(3).\n\n(ii) loading onto a digital top-up application  information relating to one or more of the following—\n\nSch. 2 item 52 (a)(ii)(A) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 52 (a)(ii)(B) amended by S.R. No. 14/2026 reg. 23(4).\n\n(B) the use of myki smartcards;\n\n(b) storing information referred to in paragraph (a) by a digital top-up application;\n\n(c) transferring or copying information referred to in paragraph (b) by means of either, or both, a wired or wireless network to the central computer system;\n\n(d) storing information referred to in paragraph (c) by the central computer system;\n\n(e) producing a printed record of information referred to in paragraph (d).\n\nSch. 2 item 53 inserted by S.R. No. 87/2021 reg. 5.\n\n","sortOrder":73},{"sectionNumber":"53","sectionType":"section","heading":"The process containing the steps set out in the following paragraphs—","content":"\t53 The process containing the steps set out in the following paragraphs—\n\n(a) loading onto the central computer system information relating to one or more of the following—\n\nSch. 2 item 53(a)(i) amended by S.R. No. 14/2026 reg. 23(4).\n\nSch. 2 item 53(a)(ii) amended by S.R. No. 14/2026 reg. 23(4).\n\n(b) storing information referred to in paragraph (a) by the central computer system;\n\n(c) copying information referred to in paragraph (b) by means of either, or both, a wired or wireless network to a digital top-up application;\n\n(d) storing information referred to in paragraph (c) by the central computer system;\n\n(e) producing a printed record of information referred to in paragraph (b) or (d).\n\n═════════════\n\nEndnotes\n\n1 General information\n\nSee [www.legislation.vic.gov.au](http://www.legislation.vic.gov.au) for Victorian Bills, Acts and current Versions of legislation and up-to-date legislative information.\n\nThe Transport (Compliance and Miscellaneous) (Ticketing) Regulations 2017, S.R. No. 48/2017 were made on 14 June 2017 by the Governor in Council under sections 56, 221AA and 230AH of the **Transport (Compliance and Miscellaneous) Act 1983**, No. 9921/1983 and came into operation on 1 July 2017: regulation 3.\n\nThe Transport (Compliance and Miscellaneous) (Ticketing) Regulations 2017 will sunset 10 years after the day of making on 14 June 2027 (see section 5 of the **Subordinate Legislation Act 1994**).\n\nINTERPRETATION OF LEGISLATION ACT 1984 (ILA)\n\nStyle changes\n\nSection 54A of the ILA authorises the making of the style changes set out in Schedule 1 to that Act.\n\nReferences to ILA s. 39B\n\nSidenotes which cite ILA s. 39B refer to section 39B of the ILA which provides that where an undivided regulation, rule or clause of a Schedule is amended by the insertion of one or more subregulations, subrules or subclauses the original regulation, rule or clause becomes subregulation, subrule or subclause (1) and is amended by the insertion of the expression \"(1)\" at the beginning of the original regulation, rule or clause.\n\nInterpretation\n\nAs from 1 January 2001, amendments to section 36 of the ILA have the following effects:\n\n• Headings\n\nAll headings included in a Statutory Rule which is made on or after  \n1 January 2001 form part of that Statutory Rule. Any heading inserted in a Statutory Rule which was made before 1 January 2001, by a Statutory Rule made on or after 1 January 2001, forms part of that Statutory Rule.  \nThis includes headings to Parts, Divisions or Subdivisions in a Schedule; Orders; Parts into which an Order is divided; clauses; regulations; rules; items; tables; columns; examples; diagrams; notes or forms.  \nSee section 36(1A)(2A)(2B).\n\n• Examples, diagrams or notes\n\nAll examples, diagrams or notes included in a Statutory Rule which is made on or after 1 January 2001 form part of that Statutory Rule. Any examples, diagrams or notes inserted in a Statutory Rule which was made before 1 January 2001, by a Statutory Rule made on or after 1 January 2001, form part of that Statutory Rule. See section 36(3A).\n\n• Punctuation\n\nAll punctuation included in a Statutory Rule which is made on or after  \n1 January 2001 forms part of that Statutory Rule. Any punctuation inserted in a Statutory Rule which was made before 1 January 2001, by a Statutory Rule made on or after 1 January 2001, forms part of that Statutory Rule.  \nSee section 36(3B).\n\n• Provision numbers\n\nAll provision numbers included in a Statutory Rule form part of that Statutory Rule, whether inserted in the Statutory Rule before, on or after  \n1 January 2001. Provision numbers include regulation numbers, rule numbers, subregulation numbers, subrule numbers, paragraphs and subparagraphs. See section 36(3C).\n\n• Location of \"legislative items\"\n\nA \"legislative item\" is a penalty, an example or a note. As from 13 October 2004, a legislative item relating to a provision of a Statutory Rule is taken to be at the foot of that provision even if it is preceded or followed by another legislative item that relates to that provision. For example, if a penalty at the foot of a provision is followed by a note, both of these legislative items will be regarded as being at the foot of that provision. See section 36B.\n\n• Other material\n\nAny explanatory memorandum, table of provisions, endnotes, index and other material printed after the Endnotes does not form part of a Statutory Rule. See section 36(3)(3D)(3E).\n\n2 Table of Amendments\n\nThis publication incorporates amendments made to the Transport (Compliance and Miscellaneous) (Ticketing) Regulations 2017 by statutory rules, subordinate instruments and Acts.\n\n–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment (Prescribed Devices and Processes) Regulations 2018, S.R. No. 22/2018\n\n| *Date of Making:* | 27.2.18 |\n| *Date of Commencement:* | 15.3.18: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Further Amendment Regulations 2018, S.R. No. 55/2018\n\n| *Date of Making:* | 15.5.18 |\n| *Date of Commencement:* | 15.5.18 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment (Electronic Testing of Tickets) Regulations 2018, S.R. No. 150/2018\n\n| *Date of Making:* | 2.10.18 |\n| *Date of Commencement:* | 2.10.18 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment Regulations 2019, S.R. No. 22/2019\n\n| *Date of Making:* | 26.3.19 |\n| *Date of Commencement:* | 28.3.19: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Conduct on Public Transport) and (Ticketing) Amendment Regulations 2019, S.R. No. 57/2019\n\n| *Date of Making:* | 25.6.19 |\n| *Date of Commencement:* | Regs 5, 6 on 1.7.19: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Conduct on Public Transport) and (Ticketing) Further Amendment Regulations 2019, S.R. No. 168/2019\n\n| *Date of Making:* | 23.12.19 |\n| *Date of Commencement:* | Regs 5–7 on 1.1.20: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment Regulations 2020, S.R. No. 6/2020\n\n| *Date of Making:* | 11.2.20 |\n| *Date of Commencement:* | 11.2.20 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Further Amendment Regulations 2020, S.R. No. 103/2020\n\n| *Date of Making:* | 29.9.20 |\n| *Date of Commencement:* | 29.9.20 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment (Prescribed Processes) Regulations 2021, S.R. No. 87/2021\n\n| *Date of Making:* | 20.7.21 |\n| *Date of Commencement:* | 21.7.21: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Conduct on Public Transport) and (Ticketing) Amendment (Prescribed Equipment and Processes) Regulations 2023, S.R. No. 48/2023\n\n| *Date of Making:* | 6.6.23 |\n| *Date of Commencement:* | Regs 4–6 on 6.6.23 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment Regulations 2024, S.R. No. 129/2024\n\n| *Date of Making:* | 19.11.24 |\n| *Date of Commencement:* | 19.11.24: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment (Prescribed Devices and Processes) Regulations 2025, S.R. No. 22/2025\n\n| *Date of Making:* | 29.4.25 |\n| *Date of Commencement:* | 29.4.25: reg. 3 |\n\nTransport (Compliance and Miscellaneous) (Ticketing) Amendment Regulations 2026, S.R. No. 14/2026\n\n| *Date of Making:* | 11.3.26 |\n| *Date of Commencement:* | 16.3.26: reg. 3 |\n\n–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––\n\n3 Explanatory details\n\n1. Reg. 4(a): S.R. No. 86/2006. Reprint No. 1 as at 7 August 2013. Reprinted to S.R. No. 95/2013. Subsequently amended by  \nS.R. Nos 66/2014, 74/2015, 75/2015, 35/2016, 69/2016, 149/2016 and 155/2016. [↑](#endnote-ref-2)\n\n2. Reg. 4(b): S.R. No. 84/2009. [↑](#endnote-ref-3)\n\n3. Reg. 4(c): S.R. No. 95/2010. [↑](#endnote-ref-4)\n\n4. Reg. 4(d): S.R. No. 114/2011. [↑](#endnote-ref-5)\n\n5. Reg. 4(e): S.R. No. 131/2011. [↑](#endnote-ref-6)\n\n6. Reg. 4(f): S.R. No. 22/2012. [↑](#endnote-ref-7)\n\n7. Reg. 4(g): S.R. No. 95/2013. [↑](#endnote-ref-8)\n\n8. Reg. 4(h): S.R. No. 66/2014. [↑](#endnote-ref-9)\n\n9. Reg. 4(i): S.R. No. 74/2015. [↑](#endnote-ref-10)\n\n10. Reg. 4(j): S.R. No. 75/2015. [↑](#endnote-ref-11)\n\n11. Reg. 4(k): S.R. No. 35/2016. [↑](#endnote-ref-12)\n\n12. Reg. 4(l): S.R. No. 69/2016. [↑](#endnote-ref-13)\n\n13. Reg. 4(m): S.R. No. 149/2016. [↑](#endnote-ref-14)\n\n14. Reg. 4(n): S.R. No. 155/2016.\n\n  ——\n\n  **Penalty Units**\n\n  These Regulations provide for penalties by reference to penalty units within the meaning of section 110 of the **Sentencing Act 1991**. The amount of the penalty is to be calculated, in accordance with section 7 of the **Monetary Units Act 2004**, by multiplying the number of penalty units applicable by the value of a penalty unit.\n\n  The value of a penalty unit for the financial year commencing 1 July 2025 is $203.51. The amount of the calculated penalty may be rounded to the nearest dollar.\n\n  The value of a penalty unit for future financial years is to be fixed by the Treasurer under section 5 of the **Monetary Units Act 2004**. The value of a penalty unit for a financial year must be published in the Government Gazette and a Victorian newspaper before 1 June in the preceding financial year. [↑](#endnote-ref-15)","sortOrder":74}],"analysis":{"flash_summary_failed":{"failed":true,"reason":"A positive credit balance is required for all requests, including BYOK, so fallback providers remain available. Add credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up to continue.","source":"analysis-cron"},"kimi_summary":{"_metrics":{"provider":"moonshot","completionTokens":2772},"content_quality":"ok","complexity_score":7,"scope_assessment":{"changed":true,"description":"The legislation has expanded significantly beyond its original 2017 scope. Initially focused on the myki smartcard system (physical cards), successive amendments have transformed it into a multi-technology framework. It now regulates digital myki (phone-based tickets), V/Line digital tickets (barcodes), digital top-up applications, and 'open payment' systems allowing direct use of contactless credit/debit cards and digital wallets (Visa/Mastercard). The technical schedules have grown from basic smartcard readers to include complex prescribed processes for mobile device integration and contactless payment networks."},"complexity_factors":["29 specific hardware devices prescribed in Schedule 1 by manufacturer and model number (e.g., 'ZEBRA Model TC77', 'Conduent CAS430 Universal Platform Validator')","53 detailed data transfer processes in Schedule 2 governing information flow between devices and the central computer system","25+ defined terms in Regulation 5, many of which are technical (e.g., 'smartcard security access module', 'digital myki', 'vehicle control unit')","Nested conditional logic distinguishing between transport modes (bus vs tram vs train) and ticket technologies (physical smartcard vs digital token vs V/Line barcode)","Multiple overlapping amendments layering new technologies (digital tickets 2019, contactless payments 2026) onto the original 2017 physical myki framework","Cross-references to the parent Transport (Compliance and Miscellaneous) Act 1983 for key concepts like 'authorised officer' and 'compulsory ticket area'"],"plain_english_summary":"These regulations are the rulebook for catching a ride on Victoria's trains, trams, and buses. They set out what you need to flash to prove you've paid your way, what transport staff can do to check up on you, and the technical nuts and bolts of the ticketing system.\n\n**The basics for passengers:**\n*   **Hold a valid ticket:** You must possess a ticket covering your whole journey before you board (or enter a \"compulsory ticket area\" like a train platform). A ticket is only \"valid\" if it authorises the entire trip.\n*   **Show it when asked:** Authorised officers, police, protective services officers, or transport staff can demand to see your \"token\" (the physical or digital proof of your ticket). You must comply immediately. This could be a physical myki card, a digital myki on your phone, a V/Line digital ticket (barcode), or even a contactless credit/debit card or digital wallet.\n*   **Prove your concession:** If you're riding on a concession fare, you must also show evidence you qualify for it (e.g., a concession card), unless the ticket itself proves it.\n*   **Kids and groups:** Someone else (like a parent) can hold the token on your behalf if you're travelling together.\n\n**The \"don't even try it\" defences:**\nThe regulations specifically shut down common excuses. It is **not** a defence to say:\n*   You didn't have time to buy a ticket (Regulation 15);\n*   You weren't paying attention or forgot (Regulation 16); or\n*   Your phone battery died or the device failed (if using a digital ticket) (Regulation 16A).\n\nThe only real defence is proving you took \"all reasonable steps\" to have a valid ticket before and during your travel.\n\n**Enforcement powers:**\nStaff can electronically test your token (except protective services officers, who can only visually inspect). They can demand you hand over a physical token or card as evidence (but crucially, they **cannot** demand you surrender your phone, smartcard, or digital wallet itself if it's a digital token).\n\n**The techy stuff:**\nThe regulations prescribe the exact machinery used — from \"ZEBRA Model TC77\" handheld readers to \"Conduent VPE430 Universal Validator\" machines — and the data flows between them. They also now cover modern \"open payment\" systems, allowing you to tap on with a Visa/Mastercard or phone wallet instead of a myki."},"flash_summary":{"complexity_score":8,"scope_assessment":{"changed":true,"description":"Since the Regulations were first made, their operational scope has been extended to explicitly cover electronic and contactless payment forms, digital tickets and a broader set of prescribed devices and data processes. The text now: (a) recognises and defines digital myki and digital tokens and sets out how they must be produced and electronically tested (Reg. 5 definitions; Reg. 9A); (b) prescribes EMV/\"open payment\" style tokens and payment cards (Visa/Mastercard and cards stored in digital wallets) as accepted tokens for ticketing purposes (Reg. 28A); (c) lists additional hand‑held, validator and validator‑platform devices and imposes configuration/commissioning requirements (Schedule 1; Reg. 29); and (d) adds a detailed catalogue of processes that transmit, store and print information between devices and the central computer system (Schedule 2). The Regulations also make it explicit that an inoperable personal electronic device is not a defence for failure to hold/produce a digital ticket (Reg. 16A) and that certain digital tokens or personal electronic devices cannot be demanded to be surrendered (Reg. 21(1A)). These changes broaden the regulatory coverage from primarily physical smartcard and token systems to a defined digital payment and device ecosystem, shifting technical, operational and compliance responsibilities onto operators, device suppliers and the central computer system (Reg. 5; Reg. 29; Schedule 2)."},"complexity_factors":["Extensive cross‑referencing to the Transport (Compliance and Miscellaneous) Act 1983 (definitions and delegated powers) (Reg. 2; Reg. 5)","Large number of technical and operational definitions (digital token, digital myki, myki smartcard, central computer system, smartcard security access module) (Reg. 5)","Detailed, model‑specific list of prescribed hardware in Schedule 1 with conditions (e.g. fitted with operational smartcard security access module or commissioned with production keys)","Long catalogue of prescribed data processes between heterogeneous devices and the central computer system in Schedule 2","Multiple offence provisions with different penalties and a layered set of procedural defences and exclusions (Reg. 7–16A)","Specific rules for digital tokens and V/Line digital tickets (production, testing, and non‑surrenderability) that interact with possession and defence rules (Reg. 9A; Reg. 21(1A); Reg. 16A)","Delegation of detailed administrative policy (refunds/replacement) to conditions under section 220D of the Act, creating operational dependency on external instruments (Reg. 21(4))","Frequent amendments and versioning noted in the text, indicating evolving scope and multiple interaction points (Table of Amendments; Endnotes)"],"plain_english_summary":"What these Regulations do, in simple terms\n\n- Mechanically, the Regulations require people using Victoria's public transport system to hold and, on request, show proof of a valid ticket for the whole of their trip or for entry to a designated (\"compulsory\") ticket area (Reg. 7–9). Proof can be a physical token, a smartcard or an approved digital token displayed or made available on a personal electronic device (Reg. 7(3), Reg. 9A).\n\n- They give authorised persons (ticketing) — authorised officers, police, protective services officers and certain employees or appointees of transport companies — the power to ask for tokens or concession evidence, to test tokens electronically at the point of inspection (unless the inspector is a protective services officer) and, in some cases, to require surrender of tokens when they are reasonably believed to be needed as evidence (Reg. 5 definitions; Reg. 8–11; Reg. 20; Reg. 21(1)).\n\n- The Regulations define a range of ticketing concepts and the technical systems that support ticketing: smartcards, digital myki, digital tokens, the central computer system, hand‑held and fixed readers, vehicle control units and a specified list of authorised devices (Reg. 5; Reg. 29; Schedule 1). They also prescribe the permitted data‑transfer and storage processes between those devices and the central computer system (Reg. 30; Schedule 2).\n\n- Penalties are set for not holding a valid ticket or failing to produce it on request (Reg. 7–11). The Regulations set out statutory defences where a person has taken \"all reasonable steps\" to have or produce a valid ticket, and they specify when common excuses are not accepted — for example, a primary reason of insufficient time or insufficient care is not a defence, and an inoperable personal electronic device is not a defence for a digital token or V/Line digital ticket (Reg. 13–16A).\n\n- The Regulations treat certain tickets (including some tickets issued by other companies under contract) as creating a contract of carriage and make those tickets subject to conditions that can include changes to the service (Reg. 17–18). They also limit ticket transferability and set extra rules for bus drivers when particular on‑board ticketing equipment is not fitted (Reg. 19; Reg. 22–23).\n\nWhy this matters (official purpose and how that maps to costs and incentives)\n\n- The stated objectives are: to require and regulate ticket use; support revenue collection; reduce fare evasion; clarify ticket‑related contracting; set ticket conditions and enforcement powers; and prescribe matters required by the parent Act (Reg. 1). Those objectives are achieved by creating rules that make possession and production of valid tickets a legal obligation (Reg. 7–9), by empowering inspections and electronic testing (Reg. 8–9; Reg. 20), and by defining the technical and contractual ecosystem that makes electronic ticketing operate (Reg. 5; Reg. 29; Schedule 2).\n\n- Who pays: on a direct level, travellers who fail to hold or show valid tickets risk monetary penalties (Reg. 7–11 set penalties). Indirect costs fall on transport operators, retail agents and the Head, Transport for Victoria to install and maintain the prescribed devices, to operate the central computer system, and to support prescribed processes (Reg. 29; Schedule 1; Schedule 2). Ongoing operational and upgrade costs follow from the device and process lists and the technical requirements in Schedule 1 and Schedule 2.\n\n- Who decides: the Secretary or the Head, Transport for Victoria determines conditions under section 220D of the Act that apply to some ticket products and refunds/replacements (Reg. 5 definitions; Reg. 21(4) cross‑refers to conditions under s.220D). Passenger transport companies can designate compulsory ticket areas by signage (Reg. 5 definition of compulsory ticket area). Authorised persons (ticketing) decide when to request inspection, test tokens (Reg. 8–9; Reg. 20) and, on reasonable grounds, to request surrender of tokens that may be needed as evidence (Reg. 21(1)).\n\n- Behaviour changes required: passengers must carry whatever form of token the system recognises for the trip (physical token, myki smartcard, digital myki, V/Line digital ticket or an approved payment token) and must present it or make the device available for electronic testing (Reg. 7(3); Reg. 9A). Passengers relying on concession fares must carry entitlement evidence and, when requesting a concession from a bus driver, show that evidence if signage requires it (Reg. 10–11; Reg. 22). Passengers using digital tokens must ensure their device and token are operable because device inoperability is not an accepted defence (Reg. 16A).\n\nImplementation risks, discretion and compliance burden\n\n- Discretion and enforcement: authorised persons have on‑the‑spot discretion to request production, to test tokens electronically (Reg. 20) and to determine reasonable grounds for surrender (Reg. 21(1)). The Regulations require receipts when surrender occurs (Reg. 21(3)) and require pre‑set ticket‑condition rules about replacement or refund when surrender is requested (Reg. 21(4)), which leaves administrative and policy detail to the conditions determined under section 220D of the Act.\n\n- Technical and operational risk: the Regulations prescribe a detailed set of approved devices and explicit processes for copying, transferring and storing information between devices and the central computer system (Reg. 29; Schedule 1 and Schedule 2). That creates ongoing technology and data‑management obligations (security, commissioning with production keys, device configuration such as operational smartcard security access modules) for operators and suppliers.\n\n- Compliance burden: for passengers — ensuring a valid ticket/product is on the device and that devices are operable (Reg. 6 example; Reg. 16A). For operators/agents — maintaining, commissioning and linking a narrow set of prescribed devices and processes to the central computer system, and administering refunds/replacements where conditions require (Schedule 1; Schedule 2; Reg. 21(4)). For authorised persons — following the inspection, testing and surrender procedures and providing receipts (Reg. 20; Reg. 21(1)–(3)).\n\nConcrete mechanisms that concentrate effects or constrain choices\n\n- The Regulations explicitly prescribe which devices and data processes are authorised for ticketing (Schedule 1; Schedule 2; Reg. 29). Prescribing particular hardware models, security module requirements and commissioning states (e.g. Open Payment production keys) means only devices meeting those technical specifications may be used for the regulated ticketing functions; that creates a defined supplier/technology boundary for operators and retail agents (Schedule 1; Sch. 1 Table).\n\n- The Regulations define certain payment tokens as acceptable State tokens (Reg. 28A), including Visa and Mastercard smartcards, prepaid cards and payment cards in digital wallets that can be processed through those branded payment networks and meet regional issuance constraints. That makes those payment networks and token types part of the authorised payment ecosystem and determines which payment instruments can be processed as tokens (Reg. 28A).\n\n- The definition of \"central computer system\" and the many prescribed processes that move information between devices and that system make the central computer system the hub for ticket validity, settlement and records (Reg. 5 central computer system; Schedule 2). The Regulations therefore allocate to that system the role of collecting, storing and settling transactions relating to digital myki, smartcards and other prescribed devices.\n\nKey exceptions and procedural details to note\n\n- Digital tokens and V/Line digital tickets must be made available for electronic testing or display (Reg. 9A). However, an authorised officer generally cannot require surrender of a personal electronic device or certain digital tokens and V/Line digital tickets (Reg. 21(1A)).\n\n- The defence framework requires that an accused took \"all reasonable steps\" to possess or produce a valid ticket; the Regulations are explicit that \"insufficient time\" or \"insufficient care\" are not, in themselves, defences, nor is an inoperable personal electronic device (Reg. 13–16A).\n\nRelevant provisions cited: Reg. 1 (objectives), Reg. 5 (definitions and central computer system), Reg. 6 (what is valid), Reg. 7–12 (possession/production obligations), Reg. 9A (digital token display/testing), Reg. 13–16A (defences), Reg. 17–18 (ticket contracts/conditions), Reg. 19–23 (transfer, testing, surrender, bus rules), Reg. 21(1A) (surrender exclusions), Reg. 27 (exemptions), Reg. 28A (prescribed tokens), Reg. 29 and Schedule 1 (prescribed devices), Reg. 30 and Schedule 2 (prescribed processes)."},"summary":{"complexity_score":4,"scope_assessment":{"changed":false,"description":"Based on the available text (which is primarily version history metadata), there is insufficient substantive content to determine whether the scope changed from the original intent. The regulations appear to remain focused on their stated purpose of ticketing compliance within the Victorian public transport system, consistent with their enabling Act."},"complexity_factors":["Subordinate legislation requiring cross-reference to the parent Act (Transport (Compliance and Miscellaneous) Act 2007) to be fully understood","Technical ticketing system rules (e.g. Myki touch on/off requirements) that may be unfamiliar to general public","Multiple amended versions requiring readers to track which version applies at a given time","Interaction with other transport regulations and ticketing schemes adds layering","Score limited by the fact the provided text is largely metadata/version history rather than substantive provisions, preventing assessment of deeper complexity"],"plain_english_summary":"## Transport (Compliance and Miscellaneous) (Ticketing) Regulations 2017\n\nThis is a Victorian statutory rule (a type of subordinate legislation made under a parent Act) dealing with **ticketing compliance** on public transport.\n\n### What does it cover?\nThese regulations set out rules around **ticketing on public transport** — things like valid tickets, proof of purchase, and the obligations of passengers and transport operators in Victoria.\n\n### Who does it affect?\n- **Everyday public transport users** in Victoria (trains, trams, buses)\n- **Transport operators and their staff** (including authorised officers who can check tickets)\n- **Myki cardholders** and anyone using Victoria's public transport ticketing system\n\n### Why does it matter?\nThese regulations define what counts as a valid ticket, what passengers must do (e.g. touch on/off), and what powers authorised officers (inspectors) have to check compliance. Breaching these rules can result in **fines or infringement notices**.\n\n### Key limitation\n⚠️ *The document provided appears to be an incomplete extract — mainly version history metadata — so a full detailed analysis of specific provisions is not possible from this text alone.*"}},"importantCases":[],"_links":{"self":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017","history":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017/history","analysis":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017/analysis","conflicts":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017/conflicts","importantCases":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017/important-cases","documents":"/api/acts/transport-compliance-and-miscellaneous-ticketing-regulations-2017/documents"}}