Create a department payment option

post

/fscmRestApi/resources/11.13.18.05/publicSectorPaymentOptionsDepartments

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
  • The unique identifier of the agency receiving an incoming customer payment. This is usually the name of a city or county.
  • Title: Cashier Session Number Rule
    Maximum Length: 20
    The autonumbering rule used to generate cashier session numbers.
  • Maximum Length: 30
    The unique identifier of the division within the agency devoted to a specific function.
  • A number used to implement optimized locking. This number is incremented every time the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
  • Title: Payment Adapter ID
    Maximum Length: 100
    The unique identifier of the payment adapter associated with the department.
  • Title: Payment Method
    Maximum Length: 30
    The method of payment. Possible values are Cash or Check.
  • Title: Payment Reference Prefix
    Maximum Length: 4
    Prefix used by the Payment Engine during the creation of the payment reference value that is sent as pass through data to the payment processor, trust account, and cash drawer.
  • Title: Cash Receipts Number Rule
    Maximum Length: 20
    The autonumbering rule used to generate receipt numbers.
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 : publicSectorPaymentOptionsDepartments-item-response
Type: object
Show Source
  • The unique identifier of the agency receiving an incoming customer payment. This is usually the name of a city or county.
  • Title: Cashier Session Number Rule
    Maximum Length: 20
    The autonumbering rule used to generate cashier session numbers.
  • Read Only: true
    Maximum Length: 64
    The user who created the department payment option.
  • Read Only: true
    The date on which the department payment option was created.
  • Maximum Length: 30
    The unique identifier of the division within the agency devoted to a specific function.
  • Read Only: true
    The date on which the department payment option was last updated.
  • Read Only: true
    Maximum Length: 64
    The user who last updated the department payment option.
  • Read Only: true
    Maximum Length: 32
    The session login associated with the user who last updated the row.
  • Links
  • A number used to implement optimized locking. This number is incremented every time the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
  • Title: Payment Adapter ID
    Maximum Length: 100
    The unique identifier of the payment adapter associated with the department.
  • Title: Payment Method
    Maximum Length: 30
    The method of payment. Possible values are Cash or Check.
  • Title: Payment Reference Prefix
    Maximum Length: 4
    Prefix used by the Payment Engine during the creation of the payment reference value that is sent as pass through data to the payment processor, trust account, and cash drawer.
  • Title: Cash Receipts Number Rule
    Maximum Length: 20
    The autonumbering rule used to generate receipt numbers.
Back to Top