Using SSF_EPAYMENT_TRANS for AAWS Application Fee Payment

This section provides a high level overview of the steps involved when an applicant pays the AAWS application fee through an external user interface.

The setup of the AAWS Application Fee and Waiver Processing group box on the Application Center Table page controls how an online application fee payment or waiver is processed.

The applicant has entered the required information and is ready to submit the application. Based on the Application Center setup, the applicant sees the relevant buttons on the external UI—for example: Request a Waiver, Make a Payment, or Pay at a Later Time.

When the applicant clicks the button to make a payment:

• The AAWS Submit web service (SAD_SUBMITAPPL) calls the Application Fee Calculation API which calculates the fee. The Submit web service returns the amount and currency code to the external UI which displays the fee.

• The Get List Of Values web service is called to determine the payment methods. These values are set up by the institution.

The applicant views the fee amount and selects a payment method. The applicant must make payment in full. Similarly, if the applicant has multiple applications, separate payments must be made for each.

When the applicant clicks the button to make the payment, the external UI calls the SSF_INITIATE_EPAYMENT web service. This web service returns values to the external UI which then redirects the applicant to the third party hosted site. The SF_PAYMENT record is created at this point. The tender rows are created in the AAWS staging records.

The applicant, who is no longer on the external UI site but on the third party hosted site, enters his or her epayment information. For echeck, the shared secret is the date of birth in the staging tables.

The applicant clicks to continue from the third party page and the payment processor redirects to the external UI. The external UI calls the SSF_COMPLETE_EPAYMENT web service. The SSF_COMPLETE_EPAYMENT web service leverages the hosted payment framework to interpret the results of the payment and call the Payment Application adapter to update the session ID and the last 4 digits of the account on the SF Payment. It also calls the SF Payment Transaction Manager to complete the payment. If the transaction is successful, the payment is authorized and posted to the GL. The payment transaction adapter updates the application-related data based on the attributes of the SF Payment.

For information about the AAWS application fee payment process, including the SF web services, see Recruiting and Admissions: Understanding AAWS.

For information about how the Application Data staging page fields are updated when an online application fee or waiver is processed, see Recruiting and Admissions: Understanding Admission Transactions.

For information about the Direct to GL process, see Generating Direct to GL Entries.