27th June 20051

2 e-Sales Project Web Liaison Group Meeting 27th June 2005 Chris Sendall and Nick Mattin

27th June ¥€-$a£es¥€-$a£es Currencies are sterling, US dollars and euro If we add the yen

27th June Purpose the project will deliver the functionality for online sale of goods & services from the University.

27th June Project Goals In connection with online services offered by the University, to: –Streamline financial procedures –Meet public expectations –Meet institutional expectations

27th June Streamline financial procedures To negotiate a satisfactory charging structure with a selected bank and a selected card processor (which may be different) To establish revised accounting & banking procedures to efficiently handle online payments securely To amend the University’s financial regulations accordingly

27th June Meet public expectations To identify & implement centralised services which allow institutions to efficiently offer online facilities that include payments

27th June Meet institutional expectations To identify current demand from within the University for support in offering such facilities Provide a platform that can be extended to achieve 90% of what is required To offer clear institutional guidance on available options & services

27th June Project Scope The project will identify institutional demand, but will limit support in meeting that demand to providing centralised services. This will amount to ensuring efficient accounting & banking procedures are established; required interfaces are built and made available for institutional access; and example web sites made available, either for direct use (through configuration) or local adaptation. Further support will be limited to offering guidance and quality assuring new facilities

27th June Application Areas Online Course/Conference Booking Online Shopping Online Donations Bespoke Applications

27th June Pilot Projects Development Office - Donations Computing Service - Printer Credits

27th June Hub Overview hub manages e-Payment request from user and application. passes the request to the card processor returns result to the user and the application

27th June Hub interfaces application to and from hub html or xml card details input hub or application page result - success or failure

27th June Hub Overview Diagram

27th June Hub dataflow diagram Shows flow of data from user through web browser sending html to application or the hub. hub uses xml to communicate with the card processor (ePDQ) hub redirects back to URL supplied by the original e-Payment request.

27th June

27th June html interface hub split into two layers, top layer which communicates with the application using html bottom layer which communicates with top layer using xml and card processor using xml.

27th June

27th June Card details input in application card details are input in the application running on a secure server. communicate with hub using html hub will generate form for user depending on information provided in original e- Payment request

27th June

27th June xml interface xml between application and hub card details input in application e-shop - Interchange - open source

27th June

27th June Real Projects Printer credits - October Donations - November Course booking e-Shop other bespoke applications

27th June Last Slide Any questions?