Get all checkout payments

get

/fscmRestApi/resources/11.13.18.05/publicSectorCheckouts/{CheckoutId}/child/CheckoutPmt

Request

Path Parameters
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey: FRD s
      Finder Variables:
      • CheckoutId; string; Unique identifier for the checkout payment data generated using the Fusion unique ID API.
      • CheckoutPmtId; integer; Unique sequence number for the checkout payment row generated using the Fusion unique ID API.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AgencyId; integer; Identifies the identifier associated with an agency.
    • AuthorizationCode; string; Authorization code value returned by the payment gateway or trust account system.
    • AuthorizationDttm; string; Authorization date and time returned by payment gateway system or trust account system.
    • AuthorizationStatus; string; The status value returned by the payment gateway or trust account system.
    • CashierId; string; The unique identifier for the cashier.
    • ChangeAmount; number; The amount of money to be handed back to the payer if the payment received from the payer is more than the amount due.
    • CheckAddress; string; The address on the check.
    • CheckDate; string; The date that the check was received from the payer.
    • CheckName; string; The name on the check.
    • CheckNumber; string; The number of the check that was received from the payer.
    • CheckoutId; string; Unique identifier for the checkout data. Generated using the Fusion unique ID API.
    • CheckoutPmtId; integer; Unique sequence number for the checkout payment row generated using the Fusion unique ID API.
    • Comments; string; Comments provided for the payment.
    • Description; string; Description provided for the payment.
    • DrawerId; string; The unique identifier for the cash drawer.
    • FirstResponseMessage; string; First part of the response message returned by the payment gateway or a free form message entered by agency staff for cash drawer or trust account.
    • LineAmount; number; That dollar amount that applies to a line item.
    • PayerAddress; string; The address of the person who made the payment.
    • PayerName; string; The name of the person who made the payment.
    • PaymentCurrency; string; Currency used for the payment transaction.
    • PaymentDate; string; Date on which the payment transaction occurred.
    • PaymentMethodCode; string; Type of payment selected during checkout.
    • PaymentReferenceId; string; Global unique payment identifier that comprises a 4-character prefix and random digits.
    • PaymentTrackingData; string; The identifying attribute passed during checkout by the originator of the assessed fees.
    • PaymentTrackingDataPlus; string; The additional identifying attribute passed during checkout by the originator of the assessed fees.
    • PaymentTransactionId; string; Transaction ID/reference number received from the payment gateway or trust account system.
    • PrimaryId; string; The unique identifier for the primary document used to identify the payer of a cash drawer check payment.
    • SecondResponseMessage; string; Second part of the response message returned by the payment gateway or a free form message entered by agency staff for cash drawer or trust account.
    • SecondaryId; string; The unique identifier for the secondary document used to identify the payer of a cash drawer check payment.
    • SessionId; string; The unique identifier for the cashier session.
    • ThirdResponseMessage; string; Third part of the response message returned by the payment gateway or a free form message entered by agency staff for cash drawer or trust account.
    • TotalTendAmount; number; The total amount of money received in payment from the payer. If this amount is more than the amount due, the difference is handed back to the payer.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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.

There's no request body for this operation.

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 : publicSectorCheckouts-CheckoutPmt
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : publicSectorCheckouts-CheckoutPmt-item-response
Type: object
Show Source
Back to Top