Laserfiche WebLink
City of Everett <br />Parking Access and Revenue Control System <br />Integration with Street Pay Stations and Mobile Parking Applications <br />E. Describe the integration with future potential on street pay stations and mobile parking <br />availability application. <br />Orbility's Multipark software management system is built using modern software tools and <br />technologies. Today, it already supports multiple third -parties (both hardware and software) via <br />APIs (Application Programming Interfaces). As the City's future needs expand, Multipark can <br />support these new, additional requirements in a timely manner and with ease. <br />Steps of Credit Card Processing <br />F. Provide a diagram explaining in detail what the steps of credit card processing entails. All <br />involved entities must be included in the diagram. <br />Figure 3 below is a detailed diagram showing the steps involved in the credit card processing <br />flow. <br />Figure 3. Credit Card Processing <br />ADVAM's Card Processing — Terminal to Acquirer a High -Level Architecture <br />TERMINAL <br />PIPE <br />ADVAM Ingenico <br />Terminal <br />Encrypt request <br />with HSM key <br />8 (tQUESI <br />Decrypt response <br />with HSM key <br />Ii1Sh ONSE <br />• <br />ADVAM GATEWAY <br />Payment <br />Request <br />AS2B05 <br />Shared <br />terminal key <br />stored in HSM <br />5eiu - TL5 <br />Payment <br />Response <br />AS2B05 <br />ADVAM Dine Centre Melbourne <br />ADVAM Gateway <br />Dotrypt message with <br />HSM key ri RECJL:1 B <br />rsPDNsr a Encrypt response with <br />HStllt key <br />ADVAM Data Centre Adelaide <br />ACQUIRERS <br />Payment <br />Request/Respcnso <br />eaturely exchanged <br />with Acquirer <br />Message format and <br />channel dependent on <br />Acquirer <br />• Contact or <br />Cordacttess <br />payment <br />• Also support OR ' <br />and RHD <br />reading <br />Terminal access to • <br />ADVAM Gateway via the <br />host's network <br />Integration via Serial APIs <br />Symmetrical shared key <br />stored in HSM <br />Secure TLS 1.2 <br />transmission of <br />payment message <br />• HSM symmetrical key data <br />encryption for message <br />exchange(P2PE) <br />• ADVAM Gateway responsible <br />for Message Enriching and <br />Switching to Acquirer <br />network <br />Sample Credit Card Report <br />G. Provide sample credit card or batch reports. <br />Figure 4 is a sample credit card payment report. <br />ADVAM has a rich set of Payment <br />APIs supporting Card Present and <br />Card not Present transactions <br />• Highly available and fault tolerant <br />Infrastructure balanced across <br />Two Data Centres <br />• Dedicated fibre. TLS <br />or VPN connection to <br />acquirers (depending <br />on acquirer) <br />• 31 Acquirers <br />integrated globally <br />-� orbility <br />Page 12 <br />