Page Comparison

...

Ecommerce & Marketplace KSAMS Roles

Ecommerce

1. Ecommerce - Department Profile Creator
   1. Set up credit and expense program profiles for the uPay transactions
   2. May or may not be developer
2. Ecommerce - Department Head
   1. Approve program profiles

...

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:

   Tip
   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 Show by default in the signature block of the notification of payment email the user receives

         Warning
         Must be identical to the Program Name in the Ecommerce profile

      2. 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
      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 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
   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

...

1. Submit your Ecommerce program for your uPay Site; Ecommerce program corresponds to exactly one uPay site (or uStore)
   1. An Ecommerce program has one Chart of Account (COA) distribution. If you have one COA distribution, you can use the same Ecommerce program. If you have different COA distribution, you will need multiple Ecommerce programs, such that each program has a unique COA distribution.
   2. IMPORTANT: The "Program Name" must be identical to the "uPay Site Name"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 guide: Marketplace Department: Configuring uPay Site
3. Change your site status to "Enabled"
4. Marketplace Department: Verifying uPay Site
5. 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
6. Change all settings to production and run final end-to-end testing in the production environment
7. Remind the functional unit to set up their staff with individuals that can process refunds and access the accounting features in Marketplace
8. Submit SAQ-A and Terms and Conditions forms to the functional department head for signature and submit to Payment Card Services at pcsgroup (AT) uci (DOT) edu 

...