March Status Update #2
- Lauren Magnuson (Unlicensed)
| Date | Â |
|---|---|
| Working Group | Systems |
| Task Force | Alma Bursar / Fines and Fees Integration |
| Report Summary | Lauren Magnuson (Unlicensed) had call with with the CSU’s CashNet rep Juliette. The key point here is that any custom integration we would want to create *requires* an e-market license. It is possible to have a single eMarket license be used so that transactions from multiple campuses go through a single campus’ eMarket license. Conceivably, it would be possible to have a single eMarket license at a campus, (or the Chancellor’s Office) process transactions for all campuses. There are some outstanding questions about how funds would be reconcilable and whether it’s possible to configure a retail terminal to post funds to multiple bank accounts depending on the type/origination of the charge. Lauren Magnuson (Unlicensed) had phone call with Delfin Guillory @ Stanislaus to find out how they’ve built a parking payment portal that accepts transactions from multiple campuses through a single CashNet eMarket database. Read the Q&A here. Lauren Magnuson (Unlicensed) following up w/CashNet about the retail terminal configuration. Lauren Magnuson (Unlicensed) distributed CashNet integration guide to Fines/Fees TF  Lauren Magnuson (Unlicensed) distributed results of our survey. a.      Based on these results, I propose we designate leaders of three subgroups to investigate, document, and assist campuses with their chosen integrations:                                                               i.      1 person to lead a subgroup interested in the bursar integration,                                                             ii.      1 person to lead a subgroup for the PeopleSoft Integration (San Marcos model – Ian)                                                           iii.      1 to lead eMarket integrations. The developments of the eMarket subgroup can lead into developing a CSU-wide solution using a single eMarket license, if there is still interest in working out the details of that given the information above.   Lauren  Q&A w/CashNet rep Q. We would like to create an integration where a user can click a payment link within Primo and be sent to a CashNet payment screen. Is an eMarket required to create such an integration? A. Yes, an eMarket license is required to create an integration as described.  You can build your own checkout with eMarket.  The way that this would work is when the user clicks the link in Primo, a URL is sent containing a string of data including the charge, the "item code" (charge code, e.g., replacement vs. fine, etc.)., and the employee ID, and the user can pay the amount.  The amount paid is then reported as a "postback" HTTPS notification which can go to wherever you specify.  The Postback message can include employee ID (provided that was sent from Primo when the user navigated to CashNet), business unit (campus), item code (charge code). It is likely that the Sacramento custom parking portal uses an eMarket license. Q.  Is it possible to run transactions from multiple campuses through a single eMarket license? A.  Yes.  All payments would go to a single bank account, but the postback messages could be sent to server/script that would parse out transactions by campus, and then checks would have to be cut to each campus.  Stanislaus did this for parking fees with other CSUs, where payments from other CSUs went through their single CashNet database.  Conceivably, the Chancellor's Office could be used as the single eMarket license and CashNet database. Q.  Are there other considerations we would need to know for building an integration of this type? A.  Dominguez HIlls currently doesn't use ePayment/CashNet.  Each eMarket license is $3500, but there are also deployment fees (one-time deployment fee: $1,795). You also need to decide if you will accept ACH (electronic checks). |
| Description | |
| Action Items |
|