Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Introduction

Preparation

uPay

  1. Email Address
    1. 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.
    2. 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
    1. Initiate the request for images for the header, sidebar (optional), and footer of the uPay screens
    2. These are not needed for testing, but must be ready for production
  3. Style Sheet
    1. 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.

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

Marketplace

  1. Marketplace - uPay Site Manager
    1. This allows you to modify the uPay Site that will be initialized for you in PRODUCTION
    2. Note that in TEST, you will be creating your own from scratch
    3. This is minimally the developer for this project, additional functional staff may be added to this role in the future
  2. Marketplace - uPay Payment Clerk
    1. 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. This is solely a functional user role

uPay Setup

  1. Department Storefront / Sending Web Application
    1. UPAY_SITE_ID
      1. Required; when you create your uPay Site, it will generate a Site ID value that you must send with the customer to TouchNet
    2. EXT_TRANS_ID
      1. Strongly recommended; you must send this key/value to get a reference value in the postback to know what/who this payment is for, like 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
      <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 - you must decide if you will use a separate web application to process the postback results of the payment transaction; you will need to test the postback functionality of the payments submitted
  3. Create your TouchNet uPay Site in the TEST version; fill in the information for the following sections; specific fields mentioned are not inclusive of all the fields you need to enter, just those with hints to help your development:
    1. Miscellaneous
      1. Site Name - Make it reader friendly; this will show in the signature block of the notification of payment email the user receives; must also be identical to the Program Name in the Ecommerce profile
      2. Posting URL - Is the web application that TouchNet 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 TouchNet; make sure any necessary firewalls rules are in place to allow TouchNet to access this web application
      3. 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
      4. Success Link URL - Button; where customers go after their payment has completed
      5. Error Link URL - Only used for system errors
      6. Cancel Link URL - Button; where customers go when they click the cancel button
    2. Messages & Titles
    3. Payment Settings
      1. Required encoded validation key for amount - If you are using a default payment amount, you do not need to enable this
      2. Passed Amount Validation Key - If you are using a default payment amount, you do not need to populate this
      3. Default Payment Amount - If you are using a default payment amount, you MUST enter a value here (no dollar signs, e.g., 100.00)
      4. Payment Amount Prompt - If you are using default payment amount, this prompt is not displayed anywhere
    4. Images - Upload your header, footer, and sidebar (optional) images here; you can test your payments without this at the beginning
    5. Style Sheets - Optional, upload your style sheets here if you’re using them
    6. 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

  1. Use the "uPay Test URL" to test your uPay set up
  2. Test credit card number
    1. Review the posted payments in TouchNet
      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

uPay PRODUCTION Setup

  1. Submit your Ecommerce program for your uPay Site; if you have multiple uPay sites, you will need a separate program for each site
    1. IMPORTANT: The "Program Name" must be identical to the "uPay Site Name"
    2. IMPORTANT: The uPay Site Name is used in the payment notification email in the signature block, e.g., "Sincerely, (uPay site name)" so consider how a cryptic name will look in the signature block
  2. Your production uPay sites will be initialized for you with the Site Name and some minimal settings; enter additional customized settings as needed (Site Email Address, images, style sheets, verbiage for messages and emails, etc.)
    1. Follow Marketplace Department: Configuring uPay Site
  3. Change your site status to "Enabled"
  4. You can continue to use your web applications in test mode while accessing the production uPay Site but any payments submitted require a real credit card creating real charges; be sure you have the ability to reverse your transactions
  5. Change all settings to production and run final end-to-end testing in the production environment
  6. Remind the functional unit to set up their staff with individuals that can process refunds and access the accounting features in TouchNet
  7. Submit SAQ-A and Terms and Conditions forms to the functional department head for signature and submission to Payment Card Services at pcsgroup@uci.edu 

 

  • No labels