# Retrieve financial settings of a gateway account Retrieves the financial settings of a gateway account with a specified ID. > This operation is experimental and may not be backward compatible. Endpoint: GET /gateway-accounts/{id}/financial-settings Version: latest Security: SecretApiKey, JWT ## Path parameters: - `id` (string, required) ID of the resource. ## Response 200 fields (application/json): - `settlementSettings` (object, required) Settlement settings. Use these settings to set up settlement accounts. - `settlementSettings.settlementCurrency` (string, required) Currency code in ISO 4217 format. Example: "USD" - `settlementSettings.settlementPeriod` (object, required) Instruction for calculating the settlement time. The settlement time and settlement period anchor are used in conjunction with the transaction processed time, to calculate the time in which the amount settles. - `settlementSettings.advancedSettings` (array) Advanced settlement settings. Use these settings to override either default settlement currency, period, or both for the transactions matched a filter. - `settlementSettings.advancedSettings.filter` (string, required) Filter that is based on transaction properties and is used to determine when to apply the settings. Example: "currency:EUR,GBP" - `riskReserveSettings` (array) Risk reserve settings. Use these settings to set up funds reserves before settlement. - `riskReserveSettings.filter` (string, required) Filter that is based on the properties of the transaction and used to determine when to apply the settings. Example: "paymentInstrument.method:payment-card" - `riskReserveSettings.bips` (number, required) Basis points. Example: 100 bips = 1%, 1 bip = 0.01%. Example: 100 - `riskReserveSettings.period` (object, required) - `riskReserveSettings.period.method` (string, required) Enum: "date-interval" - `riskReserveSettings.period.duration` (integer, required) Number of time units. - `riskReserveSettings.period.unit` (any, required) Unit of time. - `riskReserveSettings.period.anchor` (object) Instruction for calculating the period anchor. ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 404 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.