Update fee range

Update an existing fee range. Every field is replaced by what the body carries, so a field the body omits is cleared — read the range first and send back the values that are to stay, `sender_share_percent` included.

Authorization

bearerAuth

AuthorizationBearer <token>

In: header

Path Parameters

range_id*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

range_start?integer

Lower bound of the transaction amount this range prices, exclusive. In MINOR units, as a whole number — 25 is 0.25 EUR, 3000 is 30.00 EUR. Used exactly as stored: the pricing path performs no precision conversion. A fee range carries no currency of its own (asset may be 'any'), so the value is read in the currency of the transaction being priced — do not use one 'any' range for both fiat and crypto.

range_end?integer

Upper bound of the transaction amount this range prices, inclusive. In MINOR units, as a whole number — 25 is 0.25 EUR, 3000 is 30.00 EUR. Used exactly as stored: the pricing path performs no precision conversion. A fee range carries no currency of its own (asset may be 'any'), so the value is read in the currency of the transaction being priced — do not use one 'any' range for both fiat and crypto.

fixed_fee?integer

Fixed fee component. In MINOR units, as a whole number — 25 is 0.25 EUR, 3000 is 30.00 EUR. Used exactly as stored: the pricing path performs no precision conversion. A fee range carries no currency of its own (asset may be 'any'), so the value is read in the currency of the transaction being priced — do not use one 'any' range for both fiat and crypto.

percent_fee?number

Decimal rate, not a percentage: 0.01 is 1%, 0.0015 is 0.15%. Must be between 0 and 1; a higher value would price a fee above the transaction and is rejected with tariffs.invalid_percent_fee.

method?string

min_fee?integer

Floor applied to the calculated fee; 0 disables it. In MINOR units, as a whole number — 25 is 0.25 EUR, 3000 is 30.00 EUR. Used exactly as stored: the pricing path performs no precision conversion. A fee range carries no currency of its own (asset may be 'any'), so the value is read in the currency of the transaction being priced — do not use one 'any' range for both fiat and crypto.

max_fee?integer

Cap applied to the calculated fee; 0 disables it. In MINOR units, as a whole number — 25 is 0.25 EUR, 3000 is 30.00 EUR. Used exactly as stored: the pricing path performs no precision conversion. A fee range carries no currency of its own (asset may be 'any'), so the value is read in the currency of the transaction being priced — do not use one 'any' range for both fiat and crypto.

sender_share_percent?|

Share of the total fee the SENDER bears when the transfer's fee bearer is SHA, as a percentage with up to two decimals: 50 is half, 100 the whole fee on the sender (the ISO 20022 convention for the sending bank's own charge), 0 the whole fee deducted from the beneficiary. An exact decimal, so it is carried as a string; a JSON number is accepted on write and always read back as a string. Absent or null means the range declares no split, and a SHA payment priced on this range is refused with tariffs.sha_share_not_declared rather than guessed at. OUR and BEN are fixed shares and never read it. Outside 0..100 is rejected with tariffs.invalid_fee_range. This endpoint replaces the whole fee range, so omitting the field on an update CLEARS a share the range already declared, and every SHA payment priced on it is refused from then on; send the current value back to keep it.

media?string

asset?string

from_channel?string

to_channel?string

valid_from?string

valid_to?string

active?boolean

Response Body

`application/json`

curl -X PUT "https://example.com/v1/tariffs/ranges/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "Content-Type: application/json" \  -d '{}'

{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "tariff_id": "d82b8db6-f412-4b9c-8c5e-6a0221035c86",
  "range_start": 0,
  "range_end": 0,
  "fixed_fee": 0,
  "percent_fee": 0,
  "method": "fixed",
  "min_fee": 0,
  "max_fee": 0,
  "sender_share_percent": "50",
  "media": "string",
  "asset": "string",
  "from_channel": "string",
  "to_channel": "string",
  "transaction_type": "string",
  "valid_from": "2019-08-24T14:15:22Z",
  "valid_to": "2019-08-24T14:15:22Z",
  "active": true
}

Authorization

Path Parameters

Request Body

Response Body

200application/json

`application/json`