Startup

0)

Student Groups Only

- ASA-recognized student groups should first consult the Student Activities Finances Office http://web.mit.edu/slp/finances/ for guidance. They will help you register for this service.

- Other student groups should contact their financial administrators for guidance.

ASA Groups:

laurie@mit.edu

GSA

Sloan

1)       

Startup Assistance for new Merchants

- Merchant reviews the guidelines

http://web.mit.edu/ecommerce/www/guidelines.html

- ChargeMIT team member has a brief discussion with the merchant while reviewing the ecommerce web page.

- Informal discussions to help define merchant process prior to formal meeting. Merchant provides a description of business process.

X

ChargeMIT-Startup@mit.edu

2)       

Merchant Registration

- Merchant fills out the registration form with or without assistance from ChargeMIT team. Registration form: http://mit.edu/ecommerce/www/registration.html

X

ChargeMIT-Startup@mit.edu

3)       

Acknowledge registration

-The cashierís office sends the merchant a confirmation of receipt of the registration.

- Setup a needs analysis meeting between CAO and the merchant to discuss the merchantís business requirements, the ChargeMIT process and pricing.

X

ChargeMIT-Startup@mit.edu

4)       

Needs Analysis Meeting

- Categorize need (back office vs. back office/retail swipe vs. electronic vs. combination). 

- Discuss services and configuration details, set up follow up meeting with merchant as needed.

X

X

ChargeMIT-Startup@mit.edu

5)       

Cashierís Office requests a new merchant accounts from credit card processing companies.

- Note: It takes 2 weeks to get a merchant account from the bank

X

ChargeMIT-Startup@mit.edu

New Store Implementation

6)       

Finalize store configuration

-CAO assists merchant in completing OMARS questionnaire.

- http://web.mit.edu/ecommerce/www/new-omars-setup.shtml?page=new

X

X

ChargeMIT-Startup@mit.edu

7)       

ChargeMIT team begins store configuration based on Merchant inputs

- Configuration of OMARS

- Shopsite users only: Assign a store to department (for ASA Student Groups ñ Contact Laurie Ward )

- Give store URLs to merchant

X

ChargeMIT-Startup@mit.edu

8)       

Develop Storefront ñ ecommerce only

- Merchant configures Shopsite if applicable

- Merchant develops web form and links to OMARS

X

ChargeMIT-Startup@mit.edu

9)       

Merchant Functional Testing

- Connectivity, Order Entry and Reporting

X

ChargeMIT-Startup@mit.edu

10)    

Merchant / ChargeMIT Acceptance Testing

- Merchant completes testing and notifies ChargeMIT team that they are ready to move to production

X

ChargeMIT-Startup@mit.edu

11)    

CAO verifies that merchant has fulfilled all obligations (e.g., privacy statement)

X

ChargeMIT-Startup@mit.edu

12)    

Move store to production mode

X

ChargeMIT-Startup@mit.edu

13)    

Live Testing:

               - Merchant processes first live transaction

X

ChargeMIT-Startup@mit.edu

14)    

Cashierís Office makes sure that the first settlement occurs properly.

X

ChargeMIT-Startup@mit.edu

Ongoing Operation / Support

15)    

Revenue Reconciliations

- Departments must comply to the following reconciliation process.

<insert link for recon process>

- Student groups must comply with any other reporting requirements imposed by their financial administrator

X

Cashiers-Office@mit.edu

16)    

Merchant daily operations questions

X

Cashiers-Office@mit.edu

17)    

All other inquires

X

ChargeMIT-Help@mit.edu

18)    

System Notifications, Service Changes, Service Interruptions, Software Releases

X

Termination of Operations of Online Stores

19)    

Notify ChargeMIT team upon completion of the store

X

ChargeMIT-Startup@mit.edu