...
- Submit your Ecommerce program for your uPay Site; Ecommerce program corresponds to exactly one uPay site (or uStore)
- 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.
- 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
- 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.)
- Follow guide: Marketplace Department: Configuring uPay Site
- Change your site status to "Enabled"
- Marketplace Department: Verifying uPay Site
- 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
- Change all settings to production and run final end-to-end testing in the production environment
- Remind the functional unit to set up their staff with individuals that can process refunds and access the accounting features in Marketplace
- Submit SAQ-A and Terms and Conditions forms to the functional department head for signature and submit to Payment Card Services at pcsgroup@uci.edu at pcsgroup (AT) uci (DOT) edu