CHARGE IT! A Case Study of Implementing Web Credit Card Service

1. CHARGE IT! A Case Study of Implementing Web Credit Card Service Presented By: Marilyn Shipp Roger Lurie Mickey Bryant CUMREC 2001

2. Agenda • Background • Demo • Web Application Architecture • Supporting Batch Architecture • Summary • Q & A CUMREC 2001

3. Arizona State University • 50,000 Students • Students representing every state and 120 foreign countries • Research I University • 3 Campuses • Competition for best students CUMREC 2001

4. Motivation Student demand for transacting business via the web including paying their financial obligations  Accounts Receivable CUMREC 2001

5. Critical Decisions • Vendor for Credit Card Validation and Posting - contracted with Cybercash • Security - dedicatedcredit card server - central credit card process - credit card numbers not stored CUMREC 2001

6. Multiple Teams Concurrent Efforts • Accounts Receivable Application • Credit Card Application • Cybercash Implementation • Reconciliation Reporting CUMREC 2001

7. Hurdles • New development tool • New terminology to master • Many departments involved • Complex environment: Unix systems, gateways, firewalls, mainframe system, three database types, … • New work flows to implement CUMREC 2001

8. Results • Timeline • Accounts Receivable received $1.8 million to date • Currently, switching our Interactive Voice systems to use Cybercash • Manyrequests in queue CUMREC 2001

9. Demonstration

10. University Challenge Distributed, Autonomous Department Computing! CUMREC 2001

12. Accounts Receivable • Inserts entry in Sybase table for access tracking • Retrieves DB2 legacy mainframe data • Creates a unique Cybercash order id • Inserts record in DB2 UDB State DB • Sets a cookie with order id CUMREC 2001

14. Credit Card Application • Retrieves order id from cookie • Selects/Deletes data from State DB • Inserts record in Transaction DB • Updates record in Transaction DB • Resets cookie with order id CUMREC 2001

16. Control Returns to A/R • Retrieves order id from cookie • Selects data from Transaction DB • Display Pending Payment • Displays appropriate messages CUMREC 2001

17. Legend R/W - Read/Write R/O - Read/Only W/O – Write/Only Firewall Workstation with IE or Netscape Dept Transaction Log Departmental Web/App (requires dept. firewall) Web Server Farm With SSL R/O W/O Firewall Sapphire Load Balancing Broker Credit Card Transaction DB (UDB) R/O R/W A/R DB2 Database Sapphire Credit Card App CyberCash Server Sapphire A/R Application R/W Credit Card State DB (UDB) W/O

18. Credit Card State CC_STATE ORDER_ID char(25) AMOUNT decimal (12,2) APPLICATION_ID char(8) CUSTOMER_ID varchar(20) CUSTOMER_NAME varchar(35) RETURN_URL varchar(255) USER_FIELD_1 varchar(30) USER_FIELD_2 varchar(30) timestamp TRANS_ORIG_DT

19. Credit Card Transactions CC_TRANSACTIONS ORDER_ID char(25) APPLICATION_ID char(8) AMOUNT DECIMAL(12,2) CUSTOMER_ID varchar(20) CUSTOMER_NAME varchar(35) RETURN_URL varchar(255) varchar(30) USER_FIELD_1 USER_FIELD_2 varchar(30) TRANS_ORIG_DT TIMESTAMP ASU_STATUS char(1) ASU_STATUS_DT TIMESTAMP M_STATUS varchar(30) M_ERR_MSG varchar(255) M_ERR_CODE varchar(10) MERCH_TXN varchar(20) AUTH_CODE varchar(20) ACTION_CODE char(3) REF_CODE varchar(20) char(1) PROCESSED_FLAG

20. Crediting the Accounts CUMREC 2001

21. CUMREC 2001

22. Legacy Process • Mainframe process • Batch Jobs • Accounts Receivable Posting • Reconciliation • Scheduled Monday thru Friday evening CUMREC 2001

23. Web Process • Cybercash Settlement • Push Payments to Mainframe • Reconciliation CUMREC 2001

24. Cybercash Settlement • Cybercash batches and processes the debiting of the student’s credit card • 2 Settlement options available: Auto Settle Manual Settle CUMREC 2001

25. Cybercash SettlementAuto Settle • Automatically controlled by Cybercash • Based on Eastern Standard Time/Eastern Daylight Time CUMREC 2001

26. Cybercash SettlementManual Settle Decisions • Java vs Perl • Java – How?? • Java.sun.com/products/jdk1.1/docs/guide/ jdbc/getstart/introTOC.doc.html Sample Code CUMREC 2001

27. Cybercash SettlementManual Settle Settlement Process CC_RECONCILIATION ORDER_ID char(25) MERCH_TXN varchar(20) Cybercash ASU Payments ORIGIN char(1) STATUS varchar(30) CARD_TYPE varchar(20) CARD_NUMBER varchar(20) varchar(10) CARD_EXP AMOUNT MN AUTH_CODE varchar(20) BATCH_ID varchar(20) CUMREC 2001

28. Credit Card Transactions CC_TRANSACTIONS ORDER_ID char(25) APPLICATION_ID char(8) CC_RECONCILIATION AMOUNT DECIMAL(12,2) CUSTOMER_ID varchar(20) CUSTOMER_NAME varchar(35) ORDER_ID char(25) RETURN_URL varchar(255) MERCH_TXN varchar(20) varchar(30) USER_FIELD_1 ORIGIN char(1) USER_FIELD_2 varchar(30) STATUS varchar(30) TRANS_ORIG_DT TIMESTAMP REF_CODE varchar(25) char(1) S ASU_STATUS varchar(20) CARD_TYPE ASU_STATUS_DT TIMESTAMP CARD_NUMBER varchar(20) M_STATUS varchar(30) varchar (10) CARD_EXP M_ERR_MSG varchar(255) AMOUNT MN M_ERR_CODE varchar(10) AUTH_CODE varchar(20) MERCH_TXN varchar(20) BATCH_ID AUTH_CODE varchar(20) varchar (20) ACTION_CODE char(3) REF_CODE varchar(20) char(1) N PROCESSED_FLAG

29. Push Charges to Mainframe Send Transactions To MF MF DB2 Gateway CC Transaction CC Reconciliation Credit Card Payments (DB2) CUMREC 2001

30. A/R Posting A/R Legacy Nightly Processing Legacy Payments DB2 Credit Card Payments Student Accounts CUMREC 2001

31. Reconciliation Cybercash ASU Payments A/R Nightly Processing FTP A/R Transactions Department Reconciliation Process CUMREC 2001

32. Success! • Provided a new student service • Have a reusable credit card service • Learned new skills • Truly a team effort CUMREC 2001

33. Future? • Admissions apps, class registration, event registration, instructional material ordering CUMREC 2001

34. Questions CUMREC 2001