Present Fee Options

If the Get Fee Configuration step determines that there is a fee payable at submission time, then this page flow must be presented to the applicant. Fees are calculated by Student Financials according to the Fee Code attached to the application center. This page flow needs to present the applicant with his or her payment options based on the values returned in the earlier Get Fee Configuration step. The options here will include the ability to specify the tender category (for example, CC and check) and optionally the ability to request a waiver if that is allowed. Partial payments are not allowed. Therefore, the self service online application must not allow the applicant to change amount presented for payment.

A typical self-service, online-application user interface might perform the following actions:

• Present a page showing the:

  1. Amount payable.

  2. Currency code of the fee amount.

  3. Optionally, the ability to request a waiver.

  4. Optionally, the ability to specify a Waiver Basis code to be associated with the waiver request.

  5. Optionally, the ability for the applicant to attach one or more attachments to be used as supporting documentation for the waiver request.

• Formulate a request message based on the choice of the applicant:

  1. If the applicant requests a waiver then:

     - Add waiver details to the request.

     - Submit the request to the SAD_SUBMITAPPL service operation.

     - Process the response as in the Submit Application flow.

  2. If the applicant chooses to proceed with payment:

     -Submit the request message to the SSF_INITIATE_EPAYMENT web service operation.

     -Receive and process the response from the payment service operation.

     -The response may be either a HTTP redirect or a HTML string (this is determined by the hosted payment configuration).

     -In the case of a redirect, the user interface needs to respect the HTTP redirect and it will also need to store state of the current logged on userid/password in persistent client storage (for example, a database table).

     -In the case of a HTML string response, the user interface can handle this in a number of ways. Some examples are:

     — Spawn a new child window to display the HTML string response.

     — Incorporate the HTML response into a parent window frame.

  3. The response style is configurable and customizable by use of dynamic HTML. There is sufficient flexibility for the user interface to initiate the Payment Processing flow in either a new or an existing browser window. The decision will hinge entirely on the desired user experience and the technical capabilities of the user interface technology being employed.

• The end result of this activity is that the user will be presented with a browser page provided by the third party hosted payment processor from where the applicant can proceed with payment as given in the Payment Processing flow.