...

Introduction

Preparation / Setup

uPay

...

1. Submit TEST and PROD department postback IP/port information to sfinsvcsdev@uci.edu 
   1. TouchNet needs to be notified to add firewall exception to allow postback transmission through
   2. Port needs to be an SSL port (i.e. 443, 8443)

uPay

1. Email Address - Initiate the request for the email address to be entered on the production uPay sites; this address is the “From” address on the email receipt for users that enter their email address on the credit card payment form, as well as receive alerts for failed transactions, etc.
   1. Your own email address can be used for testing, but the production site needs the official functional office email address that will be monitored.
2. Graphics - Initiate the request for images for the header, sidebar (optional), and footer of the uPay screens
   1. These are not needed for testing, but must be ready for production
3. Style Sheet - The look of the uPay site can be modified by uploading customized style sheets. This is optional. If you want to use them, initiate the process to develop and approve the design of your production uPay site.

uPay Postback Setup

1. Submit TEST and PROD department postback IP/port information to sfinsvcsdev@uci.edu 
   1. TouchNet needs to be notified to add firewall exception to allow postback transmission through
   2. Port needs to be an SSL port (i.e. 443, 8443)

Access

KSAMS Roles - Test accounts are provisioned for development purposes; however, production accounts need to be requested and in place before you can set up your uPay site in production. The following KSAMS requests must be submitted:

Ecommerce

1. Ecommerce - Department Profile Creator
   1. The individual that will set up the credit and expense profiles for the uPay Site transactions
   2. Note that the uPay Site name MUST be identical to the Program Name
   3. This person may or may not be the developer for this project
2. Ecommerce - Department Head
   1. The individual that will approve the profile

...