Post setup data for payment plans

post

/fscmRestApi/resources/11.13.18.05/paymentPlanSetups

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Additional Texts
Type: array
Title: Additional Texts
Rich text fields presented to the payer during enrollment that allow the school to describe the details of the plan and the terms and conditions associated with enrollment in the plan.
Show Source
Nested Schema : Eligibility Data
Type: array
Title: Eligibility Data
Eligibility is the criteria that the application uses to determine if a payer is eligible for a particular payment plan.
Show Source
Nested Schema : Payment Schedules
Type: array
Title: Payment Schedules
The schedules that are applied to a payer's account when they complete enrollment in a payment plan.
Show Source
Nested Schema : Tag Assignments
Type: array
Title: Tag Assignments
Tags assigned to a plan.
Show Source
Nested Schema : paymentPlanSetups-additionalTexts-item-post-request
Type: object
Show Source
Nested Schema : paymentPlanSetups-eligibilities-item-post-request
Type: object
Show Source
Nested Schema : Eligible Programs
Type: array
Title: Eligible Programs
Program requirements for payment plan eligibility.
Show Source
Nested Schema : paymentPlanSetups-eligibilities-eligiblePrograms-item-post-request
Type: object
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : paymentPlanSetups-tagAssignments-item-post-request
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : paymentPlanSetups-item-response
Type: object
Show Source
  • Additional Texts
    Title: Additional Texts
    Rich text fields presented to the payer during enrollment that allow the school to describe the details of the plan and the terms and conditions associated with enrollment in the plan.
  • Title: Charge Fee Code
    Maximum Length: 30
    Code that identifies the fee that's charged to payers who enroll in the payment plan.
  • Title: Charge Fee Due Code
    Maximum Length: 30
    Code for the fee due date setting.
  • Title: Charge Fee Due
    Read Only: true
    Maximum Length: 80
    Description of the fee due date setting. Fees can be due entirely with the first payment, or the fee can be due with each payment and evenly distributed.
  • Title: Charge Fee Flag
    Maximum Length: 1
    Default Value: false
    Flag that determines if a fee will be charged to payers who enroll in the payment plan.
  • Title: Charge Fee ID
    Unique identifier of the fee that's charged to payers who enroll in the payment plan.
  • Title: Fee Name
    Read Only: true
    Maximum Length: 50
    Name of the fee charged to payers who enroll in the payment plan.
  • Title: Collect E-signature
    Maximum Length: 1
    Default Value: false
    Flag that determines if an e-signature is required during the payment plan enrollment process.
  • Eligibility Data
    Title: Eligibility Data
    Eligibility is the criteria that the application uses to determine if a payer is eligible for a particular payment plan.
  • Title: End Date
    The end of the availability date range for a fixed availability plan.
  • Title: End Pivot Code
    Maximum Length: 30
    The code for the academic period attribute used as the pivot for the end of the payment plan availability date range.
  • Title: End Pivot Direction Code
    Maximum Length: 30
    The code for the direction used in calculating the payment plan availability end date.
  • Title: End Pivot Direction
    Read Only: true
    Maximum Length: 80
    Determines if the payment plan end date is before or after the selected academic period attribute.
  • Title: End Pivot
    Read Only: true
    Maximum Length: 80
    The name of the academic period attribute used when the application calculates the end of the payment plan availability date range.
  • Title: End Pivot Unit Code
    Maximum Length: 30
    The code for the time unit used in calculating the plan availability end date.
  • Title: End Pivot Unit
    Read Only: true
    Maximum Length: 80
    The time unit used in calculating the plan availability end date. The calculation can be based on days, weeks, or months.
  • Title: Increment
    The number of days weeks or months between the academic period attribute and the calculated plan availability end date.
  • Title: Last Updated
    Read Only: true
    Date the plan was last updated.
  • Links
  • Title: Payment Plan Name
    Maximum Length: 50
    Name of the plan.
  • Title: Notes
    Maximum Length: 1000
    Notes displayed about the payment setup. Notes aren't displayed to payers.
  • Title: Organization ID
    Unique identifier of the business unit.
  • Title: Academic Business Unit
    Maximum Length: 240
    Name of the business unit.
  • Title: Payment Plan Code
    Maximum Length: 30
    Code for the payment plan artifact group. Used in versioning.
  • Title: Payment Plan ID
    Read Only: true
    Unique identifier of the payment plan.
  • Payment Schedules
    Title: Payment Schedules
    The schedules that are applied to a payer's account when they complete enrollment in a payment plan.
  • Title: Plan Availability Code
    Maximum Length: 30
    Code for the plan availability setting.
  • Title: Plan Availability
    Read Only: true
    Maximum Length: 80
    Payment plan availability setting. Plans can be available for a fixed date range, or the application can calculate availability for each defined academic period based on a pivot date.
  • Title: Schedule Due Frequency Code
    Maximum Length: 30
    The code for frequency of plan due dates for a calculated plan.
  • Title: Schedule Due Frequency Days
    Maximum Length: 100
    The days of the week that weekly payments are due. Days are represented as integers. Monday is 1.
  • Title: Schedule Due Frequency
    Read Only: true
    Maximum Length: 80
    The frequency of plan due dates for a calculated plan. Payment due dates can occur daily, weekly, or monthly.
  • Title: Schedule Due Frequency Ordinal Code
    Maximum Length: 30
    The code for the week payments are due when a plan has monthly recurring payments. Values represent the first, second, third, fourth, or last week of the month.
  • Title: Schedule Due Frequency Ordinal
    Read Only: true
    Maximum Length: 80
    The week payments are due when a plan has monthly payments that fall on certain days of a week. Possible values are first, second, third, fourth, and last.
  • Title: Schedule Due Frequency Quantity
    The number of days, weeks, or months between payment due dates.
  • Title: Plan Availability
    Maximum Length: 30
    The code for the repeat type for monthly payment due dates.
  • Title: Schedule Due Frequency Repeat Date
    The date a payment is due each month. Used when a custom plan has monthly payments that fall on the same date of the month. When a month has fewer days than the specified date, the payment due date is on the last day of the month.
  • Title: Schedule Due Frequency Repeat Day Code
    Maximum Length: 100
    The code for the day a payment is due. Used when a custom plan has monthly payments that fall on the same day each month.
  • Title: Schedule Due Frequency Repeat Day
    Read Only: true
    Maximum Length: 80
    The day a payment is due. Used when a custom plan has monthly payments that fall on the same day. For example, the first Monday each month.
  • Title: Schedule Due Frequency Repeat
    Read Only: true
    Maximum Length: 80
    The type of repeat for monthly payment due dates. Monthly payments can be due on the same day of the month, for example the first Thursday. Or they can be due on the same date every month. For example, the 20th of the month.
  • Title: Schedule End Date
    Date before which all due dates for the payment plan must fall so that included fees are paid-in full by the time the plan ends.
  • Title: Schedule End Date Code
    Maximum Length: 30
    The code for the type of schedule end date.
  • Title: Schedule End Date
    Read Only: true
    Maximum Length: 80
    The method used to calculate when a recurring payment due date schedule should end.
  • Title: Schedule End Pivot Code
    Maximum Length: 30
    The code for the method used to determine when the plan should end.
  • Title: Schedule End Pivot Direction Code
    Maximum Length: 30
    The code for the direction between the pivot date and the end date.
  • Title: Schedule End Pivot Direction
    Read Only: true
    Maximum Length: 80
    The direction used in the end date calculation. The end date can be calculated before or after the pivot date.
  • Title: End Date Pivot
    Read Only: true
    Maximum Length: 80
    The method used to determine when the plan should end. For custom plans, you can set a specific end date or define a pivot calculation. For calculated plans, you can use a specific date, a pivot calculation, or set the number of payments in the plan.
  • Title: Schedule End Pivot Unit Code
    Maximum Length: 30
    The code for the unit of time used when calculating the end date from a pivot date.
  • Title: Schedule End Pivot Unit
    Read Only: true
    Maximum Length: 80
    The unit of time used when calculating the end date from a pivot date. There can be days, weeks, or months between the pivot date and the end date.
  • Title: Schedule End Pivot Unit Quantity
    The number of days, weeks, or months between the pivot date and the plan end date, or the number of payments if the plan includes a specific number of payments.
  • Title: Schedule First Payment Amount Code
    Maximum Length: 30
    Code for the method used to determine the amount due on the first due date for calculated plans.
  • Title: First Payment Amount
    Read Only: true
    Maximum Length: 80
    Calculated plans can be set to divide included fees into equal payments or to calculate a smaller or larger percentage for the first payment.
  • Title: Percentage
    The percentage of the first payment in a calculated plan when included fees aren't divided into equal payments.
  • Title: Schedule Start Date
    The earliest date a payment plan can start. Used for plans set to start on a specific date.
  • Title: Plan Availability
    Maximum Length: 30
    The code for the method used to determine the earliest date the plan should start.
  • Title: Plan Availability
    Read Only: true
    Maximum Length: 80
    The method used to determine the earliest date the plan should start. For custom plans, you can set a specific start date or define a pivot calculation. For calculated plans, you can use a specific date, a pivot calculation, or set the number of payments in the plan.
  • Title: Plan Availability
    Maximum Length: 30
    The code for the method used to determine when the plan should start.
  • Title: Schedule Start Pivot Direction Code
    Maximum Length: 30
    The code for the direction between the pivot date and the start date.
  • Title: Schedule Start Pivot Direction
    Read Only: true
    Maximum Length: 80
    The direction used in the start date calculation. The start date can be calculated before or after the pivot date.
  • Title: Plan Availability
    Read Only: true
    Maximum Length: 80
    The method used to determine when the plan should end. For custom plans, you can set a specific start date or define a pivot calculation. For calculated plans, you can use a specific date, a pivot calculation, or set the number of payments in the plan.
  • Title: Schedule Start Pivot Unit Code
    Maximum Length: 30
    The code for the unit of time used when calculating the start date from a pivot date.
  • Title: Schedule Start Pivot Unit
    Read Only: true
    Maximum Length: 80
    The unit of time used when calculating the start date from a pivot date. There can be days, weeks, or months between the pivot date and the start date.
  • Title: Schedule Start Pivot Unit Quantity
    The number of days, weeks, or months between the pivot date and the plan start date.
  • Title: Schedule Type Code
    Maximum Length: 30
    The code for the type of payment due schedule.
  • Title: Schedule Type
    Read Only: true
    Maximum Length: 80
    Type of payment plan schedule. Schedules can be based on fixed dates, a general recurrence pattern, or a student-specific recurrence pattern.
  • Title: Start Date
    The start of the availability date range for a fixed availability plan.
  • Title: Start Pivot Code
    Maximum Length: 30
    The code for the academic period attribute used as the pivot for the start of the payment plan availability date range.
  • Title: Start Pivot Direction Code
    Maximum Length: 30
    The code for the direction used in calculating the payment plan availability start date.
  • Title: Start Pivot Direction Code
    Read Only: true
    Maximum Length: 80
    Determines if the payment plan start date is before or after the selected academic period attribute.
  • Title: Start Pivot
    Read Only: true
    Maximum Length: 80
    The name of the academic period attribute used when the application calculates the start of the payment plan availability date range.
  • Title: Start Pivot Unit Code
    Maximum Length: 30
    The code for the time unit used in calculating the plan availability start date.
  • Title: Start Pivot Unit
    Read Only: true
    Maximum Length: 80
    The time unit used in calculating the plan availability start date. The calculation can be based on days, weeks, or months.
  • Title: Start Pivot Unit Quantity
    The number of days weeks, or months between the academic period attribute and the calculated plan availability start date.
  • Title: Status Code
    Maximum Length: 30
    Code for the version status.
  • Title: Status
    Read Only: true
    Maximum Length: 80
    Status of the payment plan. The status can be draft, published, or unpublished.
  • Tag Assignments
    Title: Tag Assignments
    Tags assigned to a plan.
  • Title: Version Description
    Maximum Length: 240
    Description of the payment plan version.
  • Title: Version Name
    Read Only: true
    Maximum Length: 50
    Default Value: test
    Name of the payment plan version.
  • Title: Version Number
    Read Only: true
    Default Value: 1
    Number of the payment plan version.
Nested Schema : Additional Texts
Type: array
Title: Additional Texts
Rich text fields presented to the payer during enrollment that allow the school to describe the details of the plan and the terms and conditions associated with enrollment in the plan.
Show Source
Nested Schema : Eligibility Data
Type: array
Title: Eligibility Data
Eligibility is the criteria that the application uses to determine if a payer is eligible for a particular payment plan.
Show Source
Nested Schema : Payment Schedules
Type: array
Title: Payment Schedules
The schedules that are applied to a payer's account when they complete enrollment in a payment plan.
Show Source
Nested Schema : Tag Assignments
Type: array
Title: Tag Assignments
Tags assigned to a plan.
Show Source
Nested Schema : paymentPlanSetups-additionalTexts-item-response
Type: object
Show Source
Nested Schema : paymentPlanSetups-eligibilities-item-response
Type: object
Show Source
  • Title: Academic Period ID
    The unique identifier of the academic period that an eligibility is associated with.
  • Title: Academic Period
    Maximum Length: 50
    The name of the academic period that an eligibility is associated with.
  • Title: Charge Priority Code
    Maximum Length: 30
    Code identifying the charge priority mapping used to define eligible fees.
  • Title: Charge Priority ID
    Unique identifier of the charge priority mapping used to define eligible fees.
  • Title: Charge Priority Name
    Read Only: true
    Maximum Length: 50
    Name of the charge priority mapping used to define eligible fees.
  • Eligible Programs
    Title: Eligible Programs
    Program requirements for payment plan eligibility.
  • Title: Eligible Student Code
    Maximum Length: 30
    The code for the eligible student setting.
  • Title: Eligible Student
    Read Only: true
    Maximum Length: 80
    The eligible student setting for each associated academic period. All students with qualifying fees might be eligible, or the plan can be set to require a student to be active or not active on a program or a list of programs.
  • Links
  • Title: Minimum Amount
    The minimum aggregate amount of eligible fees for a payer to enroll in the plan.
  • Title: Plan Eligibility ID
    Read Only: true
    Unique identifier of a plan eligibility configuration.
  • Title: Recalculation Timing Code
    Maximum Length: 30
    The code denoting when to recalculate a plan to include new or increased eligible fees.
  • Title: Recalculation Timing
    Read Only: true
    Maximum Length: 80
    When a payment plan is recalculated to include new or increased eligible fees. Options are to always include new fees, to include them after the payer has given permission, or to never include them.
Nested Schema : Eligible Programs
Type: array
Title: Eligible Programs
Program requirements for payment plan eligibility.
Show Source
Nested Schema : paymentPlanSetups-eligibilities-eligiblePrograms-item-response
Type: object
Show Source
Nested Schema : paymentPlanSetups-paymentSchedules-item-response
Type: object
Show Source
Nested Schema : paymentPlanSetups-tagAssignments-item-response
Type: object
Show Source
Back to Top