Fees and Payment

An application template can charge the applicant before they submit. There are two ways to do it: a one-off application fee, or the fees of the payment plan attached to the class the applicant chose. Either way, the application moves to pending_payment while the applicant pays, and cannot be submitted until the payment requirement is met.

Payment Types

Payment is set up on the template's Payment tab. Enable payment turns it on (off by default), and What is the fee requirement for an applicant to submit their application? picks the type:

Option What the applicant pays Submission requires
Application fee A fixed fee, optionally different per programme The fee is paid or waived
Required fee(s) from Payment Plan The fees of the payment plan of the chosen class The plan's fees due on application are paid, or a flexible plan is set up correctly

A template set to payment plan fees falls back to no payment if payment plans are turned off for it. The template list shows the setup in its Payment column (for example Disabled, No fee or Payment plan fee(s)).

Application Fee

Setting Description
Gateway Where the applicant pays: one of the institution's payment portals (such as Stripe, PayPal, Flywire, Adumo or an external portal), set up in Finance.
Application fee and Application fee currency The fee. A currency is required when payment is on.
Button text and Button link For an external gateway: a button that sends the applicant to pay outside Full Fabric.
Tab name and Instructions The payment tab's name and the text shown on it, per language.

The Details, Discounts and Payment form sub-tabs hold these settings, the template's discounts and the fields of the payment tab.

Fee per Programme

On an institution-wide template, Define fee depending on the applicant's primary programme choice lets you set a fee, currency and gateway per class and campus, in a table with Name, Currency, Application Fee and Gateway columns. The applicant then pays:

  • The sum of the fees of every class they chose as their primary choice.
  • The template's fee for any chosen class with no fee of its own.
  • The template's fee and currency if the chosen classes use different currencies.

The payment description sent to the portal names the template and the chosen classes.

Discounts

Discounts set on the payment tab's Discounts sub-tab reduce the application fee. The applicant pays the fee minus every valid discount.

Paying

  1. The applicant completes every other part of the form. Moving to payment is blocked until the form is valid apart from the payment.
  2. The application moves to pending_payment, which publishes an automation event (useful for reminder workflows).
  3. The applicant pays through the payment portal. To change an answer, they restart, which returns the application to started.
  4. Once the payment requirement is met, the applicant submits.

When the fee is due and unpaid, submission fails with "Application fee needs to be paid before applying". A fee of 0, or a template with an external payment portal, does not block submission.

Payment States

The application fee payment has its own state: not_paid, in_process, partially_paid, paid or waived. Only paid and waived let the applicant submit.

Staff Actions on the Fee

Staff with applics.applications_payments can set the fee's status on the application's Financials panel:

Status Effect
Paid Sets the fee to paid and records who and when.
Waived Sets the fee to waived and records who and when. The applicant can then submit without paying.
Not paid Returns the fee to not_paid, clearing the paid and waived records.

The panel also offers Manage discounts.

Payment Plan Fees

When payment plans are enabled on the template and the applicant's chosen class has a payment plan, the applicant picks a payment plan on the application. The template's Payment plan tab holds these settings. They pick either one of the plan options of the class or a plan that staff created for them in that class.

Setting Description
Required fee(s) from Payment Plan (Payment tab) Requires the plan's fees due on application to be paid before submitting.
Automatically publish the payment plan on application submission? Publishes the applicant's plan when the application is submitted.
Applicant discount codes Allowed lets the applicant enter discount codes against their plan. Not allowed by default.
Instructions Text shown on the payment plan step, per language.

Submission checks for payment plans:

Check Error the applicant sees
No plan selected "A payment plan must be selected"
Fees due on application unpaid "Payment plan fees must be paid before applying"
Flexible plan incomplete "The payment plan must be correctly set up"

On submission the applicant's plan is saved against their profile, so later changes to the plan options do not change what they signed up to.

Note: Restarting from pending_payment clears the applicant's plan choice, so they choose again before paying.

See Finance for payment plans, discounts and payment portals.