...

1. Submit TEST and PROD department postback IP/port information to sfinsvcsdev (AT) uci (DOT) edu. 

   1. TouchNet needs to be notified to add firewall exception to allow postback transmission through. Otherwise department storefront will not receive data.

   2. 
      

      Code Block
      title Request Format
      Environment: (Test, Production, or both) Host: IP: Port:

      
      

uPay Setup Preparation

Departments may want to determine/request these in advance:

1. Email Address
   1. Initiate request for email address on production uPay site
   2. 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 customer inquiries, alerts for failed transactions, etc.
   3. Can use own email address for testing, but production needs the official functional office email address that will be properly monitored
2. Graphics
   1. Initiate request for header, sidebar (optional), and footer images of uPay screens
   2. Not needed for testing, but must be ready for production
3. Style Sheet
   1. Optional. Modify look of uPay site by uploading customized style sheets
   2. If using style sheets, initiate process to develop and approve design of production uPay site

...

Test accounts are provisioned for development purposes; however. However, production accounts need to access must be requested and in place before you can set up your uPay site in production.

Ecommerce & Marketplace KSAMS Roles

approved in KSAMS to gain access to PRODUCTION TouchNet Marketplace.

Ecommerce Roles

1. Ecommerce - Department Profile Creator
   1. Set up credit Sets up program profile with KFS income/revenue and expense program profiles accounts for the uPay incoming transactions
   2. May or may not Typically fiscal officer; may be developer
2. Ecommerce - Department Head
   1. Approve Approves submitted program profiles for department

Marketplace Roles

1. Marketplace - uPay Site Manager
   1. Manage Manages uPay site settings
   2. Note that in TEST, you will be creating your own from scratch. In PRODUCTION, a skeleton uPay site is created.
   3. This is minimally the developer for this project, additional functional staff may be added in the futureTypically IT; may add functional staff as needed
2. Marketplace - uPay Payment Clerk
   1. Issue reversalsIssues transaction refunds
   2. Functional staff
   3. As a developer, when it’s time to test the PRODUCTION uPay site, you will need a real credit card and perform a live transaction. You will want to be able to refund this charge immediately after; in production this is a FUNCTIONAL USER role, developers only use this feature for testing
3. Marketplace - uPay Accountant
   1. View Views uPay reports
   2. View Views and update updates Posting Status reportIn addition
   3. to functional office, developer may also need access for the Posting Status reportFunctional staff and IT (especially for Posting Status report)

Further details here: Ecommerce & Marketplace KSAMS Roles

uPay TEST

uPay TEST URL information

uPay TEST Setup Tips

1. Sending Web Application - application that redirects customer to payment page
   1. UPAY_SITE_ID
      1. Required; upon uPay Site creation, a Site ID value is generated
      2. Value must be sent with the customer to Marketplace
   2. EXT_TRANS_ID
      1. Strongly recommended; must send this key/value to get a reference value in the postback to know what/who payment is for, which invoice number this payment applies to
   3. EXT_TRANS_ID_LABEL
      1. Optional; allows you to label this value for the customer in a way that is relevant

      Code Block
      <input type="hidden" name="UPAY_SITE_ID" value="$upay_site_id"> <input type="hidden" name="EXT_TRANS_ID_LABEL" value="$ext_trans_id_label"> <input type="hidden" name="EXT_TRANS_ID" value="$ext_trans_id">

      
      

2. Postback Web Application - decide if using a separate web application to process postback results of the payment transaction; need to verify postback functionality of the payments submitted

3. Create uPay site in the TEST environment; fill in the following sections:

   Specific fields mentioned are not inclusive of all the fields you need to enter, just those with hints to help your

   Tip
   Info
   In TEST, you will be creating your uPay from scratch. In PRODUCTION, a skeleton uPay site is created.

   
   

   Tip
   Not exhaustive. For reference with tips to assist with development.

   1. Miscellaneous
      1. Posting URL - Is the web application that Marketplace will send the postback payment results to; it does not have to be the same URL as your original web application used for sending the client to Marketplace; make sure any necessary firewalls rules are in place to allow TouchNet to access this web application
      2. Additional Posting Value - Not viewed by anyone but your postback application and is meant to allow you to validate the source of the postback HTTP POST
      3. Success Link URL - Button; where customers go after their payment has completed
      4. Error Link URL - Only used for system errors
      5. Cancel Link URL - Button; where customers go when they click the cancel button
   2. Email Messages
      1. Payment Notification Signature Text - Shows in signature block of the notification of payment email the user receives
         1. If empty, defaults to Site Name (which may not be good choice for signature)
   3. Messages & Titles
   4. Payment Settings
      1. Required encoded validation key for amount - If using a default payment amount, you do not need to enable this
      2. Passed Amount Validation Key - If using a default payment amount, you do not need to populate this
      3. Default Payment Amount - If using a default payment amount, you MUST enter a value here (no dollar signs, e.g. 100.00)
      4. Payment Amount Prompt - If using default payment amount, this prompt is not displayed anywhere
   5. Images - Upload your header, footer, and sidebar (optional) images here; you can test your payments without this at the beginning
   6. Style Sheets - Optional; upload your style sheets here if you’re using them
   7. Users - Do not edit anything here
4. Change the status of your new uPay site to "Enabled" - this is changed in the Miscellaneous section

uPay TEST Verification

1. Use the "uPay test page" (uPay TEST URL information) to verify your uPay setup
2. Test credit card numbers
   
   1. Review the posted payments in Marketplace reports
      1. Navigate to the Payment Search
         1. Search for your payment, usually by "Order Date" range
         2. Verify results
      2. Navigate to Marketplace Reports » uPay Sites » <uPay Site Name>
         1. Revenue
         2. By Product
         3. Verify results
3. Test your sending web application - set the form action value to the "uPay posting URL"
4. Test your postback processing - you will get back an assortment of key/value pairs depending upon your uPay site configuration
5. Once your end-to-end testing is successful, you are ready to move to setting up the production environment

...