1 / 17

CREDIT CARDS AT UVA

CREDIT CARDS AT UVA. Tim Sigmon Sandy Bryant Deborah Mills January 11, 2001. BACKGROUND. Needed to accept credit cards for a variety of services Donations Admissions fees Continuing Education Conference & event fees many others. BACKGROUND. Partnered with the University Comptroller

devin-freeman
Télécharger la présentation

CREDIT CARDS AT UVA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CREDIT CARDS AT UVA Tim Sigmon Sandy Bryant Deborah Mills January 11, 2001

  2. BACKGROUND • Needed to accept credit cards for a variety of services • Donations • Admissions fees • Continuing Education • Conference & event fees • many others

  3. BACKGROUND • Partnered with the University Comptroller • Accounting issues • Credit card balancing issues • Procedures for approving credit card usage for the service

  4. BACKGROUND • Decisions for Phase I • Credit cards for services only; no goods • Did not want to store credit card numbers on university machines • ITC would provide the credit card infrastructure • Departments would develop or would contract for development of the “storefront” and the backend processing

  5. PILOT • Examined options for the acquiring financial institution (Cybercash, Signio, SurePay, ...) • Selected SurePay • ITC developed the infrastructure • ITC developed the “storefront” and the backend processing for the pilot • Long-term the ITC Business Services group will customize a template for the “storefront” & backend for a fee

  6. PILOT • Architecture • Java servlets & JSPs • SurePay Java SDK, transactions in XML • Tomcat – v.3.1 • Apache – v.1.3.12 with SSL • Locally written software – straightforward & available • Hardware – Sun Ultra 10, 440 MHz, 512 MB, mirrored 9GB drives • Identical warm spare – moveable disk array

  7. Departmental Web Server Departmental Web Server HTTP Name: John Doe Item Cost Quantity 1 $10.00 2 $15.00 10 3 Calculate Total • The department gather the contact and purchasing data…

  8. Departmental Web Server Credit Card Gateway Name Total John Doe $145.00 HTTP Page Source Please Confirm! <form = ccgatewayURL> <sender = department> <total = 145.00> $100.00 $45.00 Total: $145.00 Yes • Computes the total and returns a confirmation screen with hidden fields specifying the Credit Card Gateway

  9. Credit Card Gateway SSL HTTP VISA Credit Card Type CC Number: Total: $145.00 ******** Submit • The Credit Card Gateway returns a form requesting Credit Card number…

  10. SurePay Server Credit Card Gateway SSL HTTP Thanks! Your submission has been received. Return to Department • The Credit Card Gateway returns a screen confirming the request was received and simultaneously passes the information to the Credit Card Authorizer

  11. SurePay Server Departmental Web Server Credit Card Gateway HTTP or email SSL Authorize or Decline • The Credit Card Authorizer sends authorization status to Gateway. Gateway passes status (via email, http, etc.) to department

  12. Departmental Web Server Name Total Status John Doe $145.00 Authorized email Johndoe@virginia.edu Your VISA card has been authorized for $145.00. You are now enrolled in … Thank you • Department contacts individual (via email, phone, etc.) with status of credit card transaction.

  13. SurePay Server Web Manager John Doe $145.00 Authorized Monies moved into account = • Department then uses the Credit Card Authorizer’s web management system to record business activity to later compare with bank’s account statements.

  14. PILOT • Areas using the credit card gateway or interested in using it • Continuing Education • International Health • Casenex • Development site • Cavalier Advantage Card • Parking and Transportation • Transcripts • Box Office type transactions

  15. ISSUES TO CONSIDER • Understand the fee structure of the acquiring financial institution and negotiate • Work with your finance area on procedures for setting up merchant IDs and institutional procedures • Audit approval • Understand address verification and how and where you will/will not use this

  16. ISSUES TO CONSIDER • Fraud prevention capabilities don’t make a lot of sense for long term services • Work with the finance area on the web interface for transactions and settling • Tomcat – not in the standard build for web servers • Learning curve for departments – setting up their site and processing credit cards

  17. ISSUES TO CONSIDER • Asynchronous confirmation for customers on the results of the charge • Big sites do this • Accepting/rejecting the transactions dealt with differently by departments

More Related