Laserfiche WebLink
REV: 01-05-26 LR <br />required validation support will be for the Century 20 theaters located above the <br />Jefferson Garage. The MMS must provide at least the following options and <br />features regarding such validations: <br />1. Provide the ability to do validation using unique, single-use, pre-issued <br />coupon codes (e.g., purchased online along with a movie ticket or handed <br />out by the theater) which are presented on paper or the screen of a mobile <br />device. Such coupon codes are to be used when the parker initially arrives <br />in a garage and pre-pays for parking. The parker may purchase as many <br />hours of parking as they desire, and the coupon code would reduce the <br />parking fees based on the value of the validation. For example, if the parker <br />purchases 5 hours of parking and has a coupon code good for 3 hours of <br />validated parking, the parker will be charged for 2 hours of paid parking. <br />2. Provide the ability for the payee to initially pay for validated parking at a <br />designated MSM located inside a validating business and automatically <br />receive credit for that business’s validation amount. For example, the <br />Century Theaters could place one or more special purpose “validated <br />parking” MSMs or similar kiosk devices inside the theater which is pre- <br />programmed with a rate table that always provides an identified number of <br />validated hours of parking without entry of any coupon code. <br />3. Provide the ability for any validated parking session to be extended by <br />purchasing additional hours of parking, same as for non-validated parking <br />sessions. For example, a parker who purchased 3 hours of parking at $0 <br />fee based on using a 3 hour validation coupon code, but then decides to <br />stay parked longer than 3 hours may add on as many additional hours as <br />needed using either an MSM or a mobile payment app or text-to-pay <br />function. <br />4. Allow setting of multiple and variable validation values for each named retail <br />business. <br />5. Track and report on validation issuance and usage. <br />6. Validated transactions in all cases will still require the parker to input their <br />LPN to identify their vehicle. <br />K. Pay-by-Cell (PbC) Integration: <br />1. MMS is to support and integrate with, at minimum, the PaybyPhone PbC <br />mobile application which is currently used by Owner. <br />2. Contractor is required to identify in their proposal all PbC vendors for whom <br />they currently offer integrations. <br />3. MSM/MMS is to also offer a text-to-pay capability that allows parkers to pay <br />for parking (including validation support) without using a mobile application <br />by texting a message to an identified mobile number, which returns a web <br />URL that when selected opens a secure, mobile browser-compatible <br />payment page. <br />ATTY/AGR.2026.001/EnSight Technologies (Parking Access and Revenue Control System (PARCS)) (Page 48 of 167)