Overview of CASHNet interfaces

CASHNet supports a wide variety of interfaces to other systems. There are two primary types of interfaces:

• Imports are used to retrieve information from other systems and load them into CASHNet. The data imported is typically information about who the customers are, what their balances are, and any notes or restrictions on their accounts.
• Extracts are used to send information about activity which occurs in CASHNet to other systems. Transaction extracts provide information about payments which were receipted in CASHNet. Status extracts provide information about non-financial activities such as students signing up for eRefund or MyPaymentPlan.

CASHNet interfaces with a campus’s student account system or student information system. In many cases CASHNet also interfaces with the campus’s financial system to post general ledger transactions. It is also often useful to establish interfaces between departmental systems such as parking, telecommunications and library so that information about debts students owe in these areas can be imported into CASHNet and payments received in CASHNet can be extracted to those systems.

There are two methods of interfacing:

• Batch interfaces function by exchanging text files between CASHNet and the other system once per day (or in some cases less frequently).
• Real-time interfaces perform imports for a customer whenever the customer access CASHNet and perform extracts whenever new transaction or status data is available.

The choice of batch or real-time interfaces depends both on the capabilities of the other system and the business requirements. For example, it is often valuable to interface with a student system in real time so that students making payments online see their most current balances and so that payments are posted immediately to enable students to register right after paying. However there is little benefit to interfacing in real time to a general ledger system, since most people only view general ledger reports following a month-end close. Thus, so batch interfaces are often more appropriate for general ledger systems.

CASHNet Jenzabar Connector

Architecture

As shown in the picture below for real-time import and extract, CASHNet connects to Jenzabar through a HTTPS listener installed on the Web Server on the school end. The listener can be installed on web server like JICS or Ex Web or CX Web.

The real-time listener can also retrieve data needed for CASHNet My payment plan (MPP) .

The connector can also produce data file are required for

• CASHNet eBill module
• Customer batch import
• CASHNet eRefund module

Features

• Real-time student demography import
• Real-time student balance import
• Real-time transaction posting
• Seamless integration with Jenzabar Online Gift modile
• Seamless integration with Jenzabar online payment JICS portlets
• Support for Single sign-on from JICS, EX web and CX web

Security

The CASHNet solution complies with PCI and other security regulations related to handling of credit card and bank account data. CASHNet Jenzabar connector transfer data through industry proven secure HTTPS protocol.

Installation and Setup

CASHNet Connector comes with an easy to install and wizard driven setup package which install listener, necessary portlet changes and other Jenzabar objects on the JICS and EX/CX platforms.