Merchant Credit Card Services

The vendor is required to provide a PCI-compliant gateway and merchant account for credit card processing for visa, master card, American express, and discover cards at various university offices.
- Virtual card processing through desktop computers is desired, along with other remote processing options that the vendor may have to offer.
- Credit card terminals may be needed for some of the locations to facilitate payment and provide receipts.
- University requires a daily batch report from the vendor in order to reconcile cashier activity and bank account.
- Equipment and system shall integrate with PayPal to complete credit card transactions.
- Currently accepts credit card payments using ellucian colleague, ellucian self-service, ellucian CRM recruit, and ellucian elevate, county parking administrator, and housing director software programs.
- Credit card numbers shall not be stored on any university equipment and reside solely on vendor terminals. 
- Signature storage is strongly recommended in order to refute chargebacks.
- Students at university currently have the option to pay for services billed on their student accounts using credit cards, visa, MasterCard, American express, and discover.
- students and employees at university with a university bursar account can pay for services online, and all those transactions flow through the university’s sis system, ellucian, and go through the PayPal pay flow system that is directly supported by ellucian software products.
- As the university continues to grow and students and online transactions increase, university wants to ensure that all transactions are conducted in a safe and encrypted environment, expeditiously, at the lowest cost to the university while providing all the reporting required for reconciliations, audits, and compliance with internal policies.
- Services include:
1. Ease of extraction:
• The system should provide the ability to easily extract information and data for both regular reporting and ad hoc requests.
2. End-user queries:
• The software should accommodate access via end-user query tools, for example, crystal reports, which should be provided by the vendor.
3. Historical reporting:
• The software should allow us to compare data extracted and other elements at any two or more points in time, regardless of reporting cycles. 
• The length of time for which data will be stored should be at the discretion of the university.
4. Type of reporting
• The ability to report by cashier, location, and period.
5. Longitudinal views:
• The software should provide the ability to perform longitudinal comparisons for reporting and analysis purposes.
6. Reporting cycles:
• The software should provide the ability to define and manage differing reporting cycles, for example, one-day, one-week, one-month, year-to-date, annual, etc.
- Contract Period/Term: 1 year
- Questions/Inquires Deadline: July 15, 2025