| Table of Contents |
|---|
Background
TouchNet Marketplace enables departments to build and operate secure, web-based shopping cart applications and online payment pages. Marketplace includes three web-based applications:
- Marketplace Universal Stores (uStores) shopping site
- Marketplace Universal Payment (uPay) site
- Marketplace Operations Center administrative site
This document will focus on uPay.
uPay Intro
The uPay features of Marketplace allow departments to configure online payment pages that connect to existing campus department storefronts/web applications. uPay focuses only on the payment pages, and the department builds the storefront/product pages in the department system external to uPay. This web application then calls the uPay site when it’s time for a payment to be accepted. uPay allows site layout choices and images to maintain a consistent look and feel.
...
.
uPay can optionally pass information about the transaction back to the department web application via a postback. This allows the department system to update its record of the payment status to completed or cancelled.
Requirements
Department IT Staff
| Warning |
|---|
This project will require IT staff on the department end to requires department IT staff to create, configure, and integrate the local storefront/web application with uPay. |
Annual PCI-DSS Validation
The Payment Card Industry Data Security Standard (PCI DSS) is a proprietary information security standard for organizations that handle branded credit cards from the major card schemes including Visa, MasterCard, American Express, Discover, and JCB.
Although We have two separate environments for TouchNet: TEST and PROD. Department is recommended to create and verify connectivity with the TEST environment before going live.
Project Schedule
Marketplace environment is ready for department connectivity. Schedule and timeline will be up to department resources and allocation.
Annual PCI Validation
| Warning |
|---|
uPay departments are required to perform annual PCI (Payment Card Industry) compliance validation, since the department storefront/web application |
...
is in scope for PCI |
...
| Warning |
|---|
The department is required to complete annual PCI-DSS validation, which includes but is not limited to:
|
. |
Per the UCI Ecommerce/Marketplace Terms & Conditions on PCI DSS (Data Security Standard) Compliance Validation:
Undergraduate SIR Fees Example
Process
...
Use Case Scenario
From UCI's MyAdmission site, applicants can access the SIR Submission web application, a local system developed by Undergrad Admissions. The applicant process use case is:
- Accept offer
- Agree to terms and conditions
- Confirm personal data
- Proceed to Initiate payment gateway initiation for SIR collectionconnection for SIR payment
- System passes parameters that describe the transaction to TouchNet
- Land on TouchNet Marketplace uPay payment pages
- Submit payment
- TouchNet Marketplace transmits a postback of transaction results to the Admission Admissions system, which captures and processes the data
- If successful, applicant's admission record is stamped as SIR received
- Is redirected back to the Admissions web application;
- View transaction report is displayed
uPay Screenshots
Payment
...
Page
Confirmation Page
Receipt Page
Resources
Marketplace uPay Resources
| Info |
|---|
TouchNet documentation requires a UCI account. |
Video eTraining: uPay Training
Credit Card Decline Codes (section "Exception Codes for Hosted Solutions")
UCI Resources
| Tip |
|---|
Department is encouraged to verify connectivity against TEST environment before PRODUCTION. |
TouchNet Marketplace Info & FAQs (contains test credit card numbers)
Ecommerce & Marketplace KSAMS Roles
Ecommerce & Marketplace Production Implementation Checklist
Contacts
For questions/issues with your uPay site, you can send email to Payment Card Services and the OIT Student Financials groups: pcsgroup (AT) uci (DOT) edu, sfinsvcsdev (AT) uci (DOT) edu.