| Page Properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Three Possible Models
I. CashNet SmartPay Portal
Requirements: Pay User Fines / Fees API, Export User Blocks, Users API, CashNet "SmartPay"
...
- Removing Blocks/Holds in PeopleSoft remain manual; fine amount owed not available in PeopleSoft (necessarily) - if using Analytics API export, however, this could be available in PeopleSoft, once a day.
- Need more information about CashNet portal setup (Christian Ward (Sacramento) is researching)
- Info from Christian: Requires CashNet add-on called "Smart Pay" used to build a "Storefront" web application. Sacramento's parking services is using this type of integration with a third party parking tickets application that enables guests and campus users to pay citations through CashNet. We may be able to work with CashNet to create an interface that all campuses could use but would need the CO to help with that. It may be more efficient to straight into CashNet without using the unique account page, but that would be worked out with CashNet. See Information re: Parking Fine Payment @ Sac State
- Need to research any differences in approach for campuses using PayPal (e.g., Pomona) OR whether all CSUs using PayPal could move to CashNet for this integration.
...
- Analytics data only available once a day. Ex Libris enhancement request: Retrieve user accounts from Users API via fine amount? See Idea Exchange Entry.
III. Bursar Export
This is the native bursar export provided by Ex Libris. With this option, fines and fees are closed in Alma. This option is best if your library does not intend to restrict library use for balances owed, and does not wish to accept fines in the library. If TOU restrict permissions based on fine balance owed, those restrictions would not take effect, as fine balances are closed out once they are exported to the bursar's office.
III. Ex Libris Designed Solution
...