If your department is ready to request a consultation for an eMarket, follow the steps below to get started.
What do I need to know?
As you consider launching an eMarket, brainstorm on the following items:
- What products or services does your department want to sell?
- Is there a quantity limit?
- Are the goods tangible or intangible?
- Does the customer need to receive a ticket or similar voucher to procure the service?
- What sort of information do you need to collect from your customer? (i.e. shirt size, color preferences, etc.)
- What are the costs or cost savings for your department in moving to an eMarket?
- If you are integrating with a third party system, what is the system's function and how will it relate to an eMarket?
- Who are the contacts at your third party system that you may need to engage?
- What sorts of images, text, and logos would you like to include on your site?
What are eMarkets good for?
eMarkets are great for quick, scalable, payment solutions, but are not an answer for every need. eMarkets are great for:
- Collecting membership dues
- Selling event tickets where the events do NOT require assigned seating (see below)
- Application fees or deposits
- Subscription services
- Tangible products and services
eMarkets are not a good fit for:
- Payments for fees and charges defined under Florida Statute 1009.24
- Point of sale systems
- Donations (these should be coordinated with the Florida State University Foundation)
- Events that require assigned seating, unless integrating with an existing solution as an eMarket Checkout
How much does it cost to build an eMarket?
The Transact team and Controller's Office do not charge departments for the setup of an eMarket at this time. Service charges for online payments may be passed to customers at a rate of 2.75% for domestic credit card payments and 4.25% for international credit card payments. Departments who choose to absorb service charges on behalf of customers will be billed monthly by the Controller's Office.
How long does it take to build an eMarket?
The timeline for the development of an eMarket varies depending upon complexity, number of products, and other factors, but generally follow a 30 day implementation timeline. Changes to existing storefronts are generally completed within 5 business days depending upon complexity. eMarkets that integrate with a third party system as a Checkout may take more time depending on the integration and testing constraints of the third party.
Departmental Responsibilities / Next Steps
- Complete the eMarket request form
- Incomplete forms will be returned and will delay the implementation of the eMarket.
- Email ctl-transact@fsu.edu with any questions about the form.
- Compile images, logos, and text
- The Financial Systems team will not reformat images. Images should be formatted to fit the specific needs of your eMarket.
- Images for eMarkets must adhere to the following guidelines:
- GIF, JPG, or PNG Format
- Store logos must be 965 x 225 pixels or less and must not be more than 1 MB
- Store purchase items must be 500 x 500 pixels and must not be more than 1 MB
- Email ctl-transact@fsu.edu with any questions about image dimensions.
- Review your site prior to launch
- Departments must authorize the final eMarket format and design before the site will be deployed.
- Reporting and reconciliation
- Departments are responsible for regularly reconciling their eMarket activity and will be provided with reports to assist with reconciliation.
- Refunds of payments can be requested by the department through Cash Management, Banking, and Revenue Accounting using the Refund Request Form. Refunds are processed within 3-5 business days. Once a refund is processed, an email notification is sent to the purchaser.
- eMarket transactions are to be initiated by the customer only. Departments are prohibited from entering transactions for customers or collecting credit card information from customers for the purpose of initiating an eMarket transaction.
