eMarket
Overview
Student Financial Solutions has partnered with Transact Payments (a third-party vendor solution) to offer e-commerce services to the campus community. Campus departments can establish themselves as merchants to sell approved products or services via customizable online storefronts and accept credit card payments
Resources
- Increases visibility of departmental services and offerings to campus customers, alumni, and the community
- Reduces administrative burden related to PCI compliance
- SFS will complete one SAQ A report on behalf of departments using Transact E-Market storefronts (does not include e-market checkout integrations)
Category | eMarket Storefront | eMarket Checkout |
---|---|---|
Purpose & Use Case | Designed to let users browse, select, and pay for items entirely within a hosted site. Ideal for donations, event sales, and departmental storefronts. | Used when item selection happens on the institution’s website, but payment is processed via Transact. Good for applications needing custom workflows. |
Start Point | Customer starts directly on a Transact (CashNet)-hosted eMarket site (Storefront URL). | Customer starts on the institution’s own website. |
Item Selection | Happens within the Storefront—user browses by category or item. | Happens on the institutional site—items are selected before being sent to Checkout. |
Checkout Process | Seamless within the same site; user moves from selection to payment on one site. | User is redirected to Transact (CashNet) to complete payment after selecting items. |
Payment Methods | Credit card, ACH (if allowed), SmartPay compatible. | Same as Storefront – fully compatible with major methods. |
Receipt & Confirmation | Built-in confirmation screen and optional email receipt. | Same – confirmation via Transact (CashNet), then redirected to institutional URL. |
Best for... | Departments that want a ready-to-use online storefront for simple transactions. | Use cases where the institution wants to control item selection and checkout logic. |
New e-market requests may require 8 - 12 weeks to configure and implement, depending on the complexity and current demand for other e-market sites. This includes information gathering and obtaining a merchant ID (MID) for accepting credit card payments and a bank account.
Description |
Cost |
---|---|
Configuration/Deployment |
TBD |
Terminal ID Fee |
TBD |
Annual Subscription |
TBD |
Merchant Credit Card Fees |
2.65% |
ACH Fees |
0.25 per Transaction |