Page Comparison

1. KSAMS Access
   1. Ecommerce
      1. Request routed to Department Security Administrator (DSA)
   2. Marketplace
      1. Request routed to Payment Card Services (Central Office)
      2. Approved after Ecommerce program profile is approved (e.g. might take time)
2. Ecommerce
   1. Create program profile with Chart of Account (COA) distribution
      1. Indicate uStore or uPay in description
      2. For uPay - name is used in customer receipt email signature. Plan accordingly.
   2. Submit for approval
   3. Central Office will create uStore/uPay skeleton before approving program
   4. Business rules:
      
      1. 1-1 mapping between Ecommerce program and uStore or uPay site
         1. Name is used to map for ledger processing
         2. uStore products will share same COA distribution
         3. uPay transactions will share same COA distribution
      2. If COA distribution is different (chart, account, sub-account, object, sub-object, project, org doc no, org ref ID, or distribution percentage), department must create different programs and have separate uStore/uPay sites
3. Marketplace Authorization
   1. Central Office will setup users and send out login information
   2. Central Office will assign appropriate access to uStores/uPay sites
4. Marketplace
   1. Authorized department users can configure uStore/uPay
      1. uStore products must have "Auto Fulfill" set to Yes
   2. Verify uStore/uPay with personal card (e.g. Marketplace does not have test credit card numbers in PRODUCTION)
      1. Can void before midnight cutoff, or issue a refund after
   3. Bring uStore/uPay live accordingly

...