Using Marketplace for Online Credit Card Transactions

1
Using Marketplace for Online Credit Card
Transactions

• Jonathan Keller
• UC Davis
• Accounting Financial Services

2
Why a Centralized Solution?

• PCI Data Security Standards
• Certification Process
• Network Scans
• Infractions affect rates for entire campus
• AFS Offers it as a free service

3
TouchNet Payment Gateway

• TouchNet Payment Gateway
• Stores Credit Card Information
• Communicates With Bank
• Encrypted Data Storage
• Automatic Settling

4
TouchNet Marketplace

• uStores
• uPay
• Administration Console
• Credit/Refund Tool
• Transaction Reports
• Revenue Reports

5
uPay

• Centrally hosted web UI to gather payment
  information
• Can be slightly customized
• Sends results back to your server
• Multiple Sites per Department

6
UCD Added Functionality

• Automatic posting to the General Ledger
• Ability to specify the FAU
• Integration with the on-line gift processing form
• Additional reporting through Decision Support

7
How it Works

• 4 Components
• Your Web/Application Server
• Marketplace (uPay) Server
• Payment Gateway
• Data Extraction Process

8
Process Diagram
9
Departmental Web Server

• Gather non-payment information
• Store the transaction information
• Flag as incomplete
• Have user submit a form which will post to the
  uPay server
• Form contains site ID and transaction information
• Accept a post from the uPay Server

10
uPay Server

• Gathers payment information
• Credit card number
• CVV
• Billing Address
• Communicates with Payment Gateway
• Provides feedback to user
• Sends success or failure information to
  department server

11
uPay Site Pages
12
uPay Site Pages
13
Form Post Details

• UPAY_SITE_ID merchant identifier
• EXT_TRANS_ID local unique transaction ID
• Also 1st 40 characters go to the general ledger
• AMT amount to be charged
• VALIDATION_KEY (optional) special string that
  prevents altering of the above parameters

14
Post-back Details

• Server-to-Server communication
• UPAY_SITE_ID
• EXT_TRANS_ID
• POSTING_KEY
• Secret key set up on the server to ensure that
  this post actually came from the uPay server.
• TPG_TRANS_ID
• Unique transaction identifier assigned by the
  payment gateway. Also, sent to the bank.
• PMT_STATUS
• Should be success
• PMT_AMT
• And others

15
Handling the Post-Back

• Verify the POSTING_KEY
• Verify the UPAY_SITE_ID
• Retrieve the transaction using the EXT_TRANS_ID
• Check that the PMT_STATUS is "success
• Verify that the PMT_AMT matches the transaction
  amount
• Save any of the returned information that you
  want to keep (especially TPG_TRANS_ID)
• Mark the transaction as "paid and perform any
  post-payment processing

16
Data Extraction Process

• Pulls settled transactions from the Payment
  Gateway
• Extracts FAU information from the information
• Posts revenue to ledgers
• Creates on-line gift documents (when appropriate)

17
Specifying a FAU

• If you need more than the default
• Two options
• FID123
• FAU36620110KUALITRAINDEVLP (CAAAAAAASSSSSPPPPPPPP
  PP)
• Append either to the EXT_TRANS_ID

18
DaFIS GL Feed

• No more SCCZ documents!
• EXT_TRANS_ID goes into description
• Without any FAU/FID information

19
Reporting

• Merchant Revenue Report
• Site Revenue Report
• Payment Lookup
• DS Report 302

20
Getting Started

• Contact Internal Control
• Maureen Pigozzo
• Email mdpigozzo_at_ucdavis.edu
• Phone [phone]
• Provide merchant information
• Experiment with the test uPay site
• Determine default FAU for GL posting

21
Questions?

• Functional/Policy Questions
• Maureen Pigozzo, Internal Control
  (mdpigozzo_at_ucdavis.edu)
• Technical Questions
• Suzanne Sparrevohn, AFS Systems Operations
  (shsparrevohn_at_ucdavis.edu)
• Jonathan Keller, AFS Systems Development
  (jhkeller_at_ucdavis.edu)