...

1. Marketplace - uPay Site Manager
   1. Manage 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 future
2. Marketplace - uPay Payment Clerk
   1. Issue reversals
   2. 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 uPay reports
   2. View and update Posting Status report
   3. In addition to functional office, developer may also need access for the Posting Status report

uPay TEST

uPay TEST URL information found here.

uPay TEST Setup

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

         Warning
         Must also 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

...