One University payment gateway for University of Waikato
•Download as PPTX, PDF•
0 likes•496 views
A presentation given at Tertiary ICT conference in 2014 for the Microsoft Tertiary ICT Excellence Awards - technology delivery. University of Waikato implemented a pan-university payment gateway in November 2013. The aim of the project was to develop a generic online payment system which can be used by any operational area of the university. The benefits of this project were: 1. Progressing the University on the path toward a cashless campus. 2. Providing students with an alternative payment method other than credit cards. 3. Reconciliation – introducing a central point from which payment information is sent to Oracle Financials for auto-reconciliation. 4. Providing a central payment gateway for all University services. Technically the solution utilises the Oracle SOA technology stack, exposing a web service which can be called to open the online payment system for the credit card and bank transfer service providers. Web components were developed with WebLogic BPEL. Mid-2014 the benefits are starting to be realised, with 8674 transactions this year and more than ten different developments using our gateway from different areas of the University and external parties on behalf of University parties, all using vastly different technologies. This presentation will outline this project; the drivers, the lessons learnt, the successes, the failures and what our future plans are for our online payment gateway.
Recommended
Recommended
More Related Content
Similar to One University payment gateway for University of Waikato
Similar to One University payment gateway for University of Waikato (20)
More from Claire moava Sherrington
Recently uploaded
Recently uploaded (20)
One University payment gateway for University of Waikato
- 1. One University Payment Gateway By Claire Sherrington and Ian Drever
- 2. Payment Gateway Buying online Integrates with Oracle Financials 10 months old 9,000 plus transactions 10 plus usages 2
- 3. What are the Drivers? 1. Limited internal resources to build specific payment solutions 2. Limited budget to purchase 3rd party solutions 3. Demand to pay anytime from students 4. It was hard to sell stuff ….. 3
- 4. Overview of Payment Process Jdeveloper and SOA BPEL processor Credit Card Select REST Payment Gateway WSDL Library Onenote Student Browser 4 Receipt Oracle AR Receipt
- 5. What are the Benefits? 5 Cashless campus
- 6. What are the Benefits? 6
- 7. What are the Benefits? 7
- 8. What are the Benefits? 8
- 9. What are the Benefits? 9
- 10. What are the Benefits? 10
- 11. Challenges 11 Communications Demand Assurance Governance
- 12. Challenge - Communication 1. Internal technical groups 2. External development suppliers 3. Payment service providers 12
- 13. Challenge - Demand 13
- 14. Challenge – Demand 14 Demand for new supporting tools
- 15. Challenge - Assurance Peer reviewing 3rd parties work 15
- 16. Challenge – Assurance 16
- 17. Challenge – Assurance Business group approval and decisions 17
- 18. Challenge - Governance 1. Technical oversight level? 2. Is it governance or ownership? Final sign off by the Finance Division Ownership of the monitoring? 18
- 19. What is the future? From the business • Mandating one payment gateway • Improved assurance processes • Add more credit cards types and refunds From IT • Error management framework • Improving the communication framework • Peer review processes 19
- 20. Questions 20
Editor's Notes
- IS revenue is important? Therefore the way we collect revenue is essential. My name is Claire Sherrington, I am the IS group manager and this Ian Drever EA from UoW. Today we are speaking about University of Waikato implemented a pan-university payment gateway in November 2013. I was project manager and Ian was the Technical lead.
- The aim of the project was to develop a generic online payment system for credit cards and online banking that seemingly integrates with Oracle Financials which can be used by any operational area of the University. Using technologies were - Oracle SOA BPEL, Oracle AR, Jdeveloper connecting to payment services providers. 10 months old 9,000 plus transactions 10 plus applications of use. Paying for library fees, academic records, conference fees, buying course & teaching resources, enrolment, conference fees, donations, coming soon is purchasing student accom
- There 3 key drivers to do this a different way. 1, My team of 14, supplies all corporate application and data services – we have limited internal resources, we want to build something once and reuse to make best use of our time Our budget is limited Students wanted to pay online … It was hard to paid and get in the “right place” in the OF A project was born …
- 1. Progressing the University on the path toward a cashless campus. Safer has there is less need to move money/cash around
- 2. It’s easier to buy and sell stuff …. Making Revenue. Providing students with an alternative payment method other than credit cards. We had opportunity to allow payment by online banking.
- 3. Reconciliation – introducing a central point from which payment information is sent to Oracle Financials for auto-reconciliation. Seeing an increase in efficiencies for Financial department
- 4. It’s bought together IT resources around the University. UoW has Decentralised IT teams This project bought us together
- Supportability is predictable for internal IT We have support SOA services since 2010, therefore we tools/knowledge for my team to support this service
- 6. It’s technology independent solution…. Any technology can use the payment gateway, for example we have uses in .NET , PHP and Perl
- Theme …….a lot of more stakeholders…………. We have three groups ….. All need different communications needs – types of messages, methods with different times
- A victim of our success ? Bad or a good thing ?? An increasing demand from the different/new business groups to use the payment service. These new groups of the business want to use our service that we have not worked with recently or at all.
- A victim of our success ? Bad or a good thing ?? 1. Demand for supporting tools for the payment gateway, e.g providing transaction monitoring
- Difficulties with peer reviewing third party developments Trusting? Right to audit ? Giving feedback ?
- Importance is testing…. Testing standards….. How much should do? Is it my job? Your gateway should catch this? Common language problem ?
- When completing application and getting an approval to proceed or seeking direction of an review issue from business group
- A simple governance process has been developed with the Finance Division to provide an oversight on business and technical processes for any business groups wishing to connect to the payment service. Technical oversight level – balance of technical knowledge. Does the business group have the ability to develop a robust interface? Governance or ownership Final testing and sign off is given by the Finance Division The different systems are closely monitored when they move into production for any issues.
- From the business Mandating one payment gateway solution support improved assurance processes adding more credit cards types , adding refunds From the IT side redeveloping of the error mngt framework relook at peer review processes improving the communication framework