---
title: "Retrieve accounts per settlement method and posting tariff"
method: GET
path: "/service-contracts/{serviceContractIndex}/account-settlement"
tags: ["Service Contract Specific Setup"]
---

# Retrieve accounts per settlement method and posting tariff

`GET /service-contracts/{serviceContractIndex}/account-settlement`

Retrieves a paginated list of valid account types and currency per settlement method and posting tariff for a service contract.

The settlement method determines how the particular merchant account is settled. E.g. Daily based on the closing balance of the account via a SEPA funding file.
The posting tariff determine where transactions are posted. E.g. All transaction gross amount will be posted to the "Payment Retail" account and all the associated transaction fees will be posted to the "Fee Collect" account.

This endpoint can be used during boring and maintenance to find for a selected service contract the valid settlement methods, and for the settlement method the valid posting tariff as well as the valid account types and currencies for the combination of settlement method and posting tariff.
By default all possible combinations are returned; the list can be filtered by settlement method and/or posting tariff.

## Path parameters

- `serviceContractIndex` string, required

## Query parameters

- `settlementMethodIndex` string — The settlement method defines the frequency and grouping of transactions posted to makeup a payment as well as the funding channel.
- `postingTariffIndex` string — The posting tariff determines how transactions and fees are posted to the merchant accounts.
- `offset` integer
- `limit` integer

## Headers

- `Content-Type` 'application/json' | 'application/json;charset=UTF-8', required
- `FSV-Interaction-Id` string, required
- `Institution-Number` string, required
- `Environment` string, required

## Response `200`

OK

- InlineResponse2003 — An API response. The API response will be either a `SUCCESS` or an `ERROR`. A partial success or warning scenario will be treated as a Success with embedded messages in the meta data. A full success may not have messages. The API response will contain at least one of the following top level members."
  - `meta` MetaType — Supplementary information about the data.
    - `paging` PagingMetaType — Map containing pagination related information about data.
      - `count` integer — Total number of records present in system which can be retrieved.
      - `totalPages` integer — Total number of pages with maximum limit taken into account.
      - `currentOffset` integer — Current offset used in request.
      - `currentNumberOfRetrievedRecords` integer — Current number of retrieved records.
      - `maxLimit` integer — Maximum limit of records that can be retrieved.
      - `hasMoreRecords` boolean — Indicates if there are more records available.
      - `pageNumber` integer — Current page number.
    - `sorting` SortingMetaType — Map containing sorting related information about data.
      - `sort` string — Indicates the elements the current data is sorted with and the direction of sorting.
    - `messages` ErrorType[] — Messages related to request processing or response data - any additional information or warnings to be returned in the case of a successful API call.
      - `id` string — Generated message identifier for particular request, helping to locate server logs.
      - `code` string, required — Machine readable, unique code of the message related to particular case within operation execution. For complete list of codes please refer to API portal, messages page.
      - `title` string, required — Short description of the error. Not for displaying purposes.
      - `detail` string — Provides additional low-level details about the error to assist with troubleshooting. Not for displaying purposes.
      - `source` SourceType — Object containing references to the source of the message.
        - `pointer` string — Indicates the element in the request document which caused the error.
        - `parameter` string — Indicates which query parameter caused the error.
        - `header` string — Indicates which header caused the error.
  - `data` object — "Contains the primary data to be returned as the API response. This object is used only when a single a single item is returned like It will not be returned in case of error."
    - `merchantStatus` OPYMerchantMerchantStatusObj — Merchant status code and description
      - `merchantStatusIndex` string — Status of the merchant. For a list of valid status codes use Acquirer Profile API GET reference-data endpoint with query parameter clasifications equal merchantStatusIndex.
      - `merchantStatusDescription` string — Contains description associated to a code in English.
    - `merchantStatusEffectiveDate` string — Effective date format YYYYMMDD
  - `errors` ErrorType[] — "Contains one or more error messages and is mutually exclusive with the data item. This will not be returned in success scenarios."
    - `id` string — Generated message identifier for particular request, helping to locate server logs.
    - `code` string, required — Machine readable, unique code of the message related to particular case within operation execution. For complete list of codes please refer to API portal, messages page.
    - `title` string, required — Short description of the error. Not for displaying purposes.
    - `detail` string — Provides additional low-level details about the error to assist with troubleshooting. Not for displaying purposes.
    - `source` SourceType — Object containing references to the source of the message.
      - `pointer` string — Indicates the element in the request document which caused the error.
      - `parameter` string — Indicates which query parameter caused the error.
      - `header` string — Indicates which header caused the error.
  - `links` LinksType — Contains the links to retrieve the resources exposed as part of this API.
    - `self` string — The link to the primary resource being retrieved in the request.
    - `first` string — This is to provide the link to retrieve the first record/page. This SHOULD be used in case server provides pagination of the resource.
    - `last` string — This is to provide the link to retrieve the last record/page. This SHOULD be used in case server provides pagination of the resource.
    - `prev` string — This is to provide the link to retrieve the previous record/page. This SHOULD be used in case server provides pagination of the resource.
    - `next` string — This is to provide the link to retrieve the last record. This SHOULD be used in case server provides pagination of the resource

## Other responses

- `400` — Bad Request - the request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
- `401` — Authentication error
- `403` — Forbidden error i.e. Consumer token credentials are valid but lack of permissions to do this action.
- `404` — Record does not exist.
- `500` — Internal Server Error - server encountered an error processing request. This should not happen normally, but it is a generic error message, given when no more specific message is suitable.

---

[API](https://skmtc.net/fiserv/apis/acquirer-profile-in-design.md) · [All operations](https://skmtc.net/fiserv/apis/acquirer-profile-in-design/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fiserv/acquirer-profile-in-design/revisions/dd7ef6ce81a1/schema)