INFOSEND, INC. 1 - 2007 - Laserfiche WebLink

Home Browse Search

InfoSend Response — 12/29/2006 c. Not Applicable - InfoSend is able to process recurring payments based on the requirements above. D. Requirements: Future phases of Web Services Implementation Allow customers to request services or programs interactively on the website. The functionality should ensure that required information /fields are populated, editable, and secure. Examples of online interaction are as follows: a. Account Changes: much of this is already provided in InfoSend's standard EBPP implementation. Customers can choose to change any of the following data elements that are stored in the EBPP database: i. Account Password ii. Email Address iii. Phone Number iv. Physical Address v. Turn Paper Statement Delivery On or Off (unless the City chooses to force all EBPP customers to forego paper statements). vi. Which Accounts are Enrolled — Customers can add additional accounts to one user ID in the EBPP system. The standard method of allowing customers to change account settings is to design web forms that the customer can submit to make changes. The City can choose to have InfoSend pre - populate the customer's current data into some of the text fields so that the customer can see what he or she the current data before making a change. InfoSend can report the changes to the City in an emailed report or by posting the data to a secure website for download. InfoSend can format the report to match the delimiter type and column layout used by its CIS system so that the data can be automatically uploaded to the system. InfoSend will not charge the City to develop or maintain these forms. If the future phase website features require that an HTML formatted document be created and stored in the EBPP system archive then a transaction fee will be charged for each document created, that is equal to the normal bill presentment fee. An example of a web form is provided on the next page: