Skip to main content
PATCH
Update a fee schedule

Authorizations

​
Authorization
string
header
required

Bearer token authentication (format: "Bearer {token}")

Headers

​
X-Request-Id
string

A unique identifier for tracing the request across services.

​
X-Idempotency
string

Optional idempotency key for safe retries. Matcher reads the key only from this header, and only when you send one. A request that carries a key only in X-Idempotency-Key or Idempotency-Key is refused with 400 (MTCH-0015), and nothing is processed. If the same key is sent again and the original request was already processed, the stored response is returned with X-Idempotency-Replayed: true. A malformed key returns 400, a key whose first request is still in progress returns 409, and an idempotency storage failure returns 500. These refusals are problem documents.

Path Parameters

​
scheduleId
string<uuid>
required

The unique identifier of the fee schedule. Schedule ID

Body

application/json

Fee schedule updates

​
applicationOrder
enum<string>

How items combine. PARALLEL applies every item to the same gross base; CASCADING applies each item to the net remaining after prior items.

Available options:
PARALLEL,
CASCADING
Example:

"CASCADING"

​
name
string

New human-readable name of the fee schedule.

Example:

"Updated Schedule"

​
roundingMode
enum<string>

Rounding strategy. HALF_UP rounds halves away from zero; BANKERS rounds halves to the nearest even digit; FLOOR rounds down; CEIL rounds up; TRUNCATE drops extra digits.

Available options:
HALF_UP,
BANKERS,
FLOOR,
CEIL,
TRUNCATE
Example:

"BANKERS"

​
roundingScale
integer<int64>

Number of decimal places fee amounts are rounded to.

Example:

4

Response

Successfully updated fee schedule.

​
applicationOrder
enum<string>
required

How items combine. PARALLEL applies every item to the same gross base; CASCADING applies each item to the net remaining after prior items.

Available options:
PARALLEL,
CASCADING
Example:

"PARALLEL"

​
createdAt
string
required

Creation timestamp in RFC 3339 format.

Example:

"2025-01-15T10:30:00Z"

​
currency
string
required

ISO 4217 currency code the schedule's amounts are denominated in.

Example:

"USD"

​
id
string
required

Unique identifier of the fee schedule.

Example:

"550e8400-e29b-41d4-a716-446655440000"

​
items
object[] | null
required

Fee items that make up the schedule.

Maximum array length: 100
​
name
string
required

Human-readable name of the fee schedule.

Example:

"Card Processing - Visa"

​
roundingMode
enum<string>
required

Rounding strategy. HALF_UP rounds halves away from zero; BANKERS rounds halves to the nearest even digit; FLOOR rounds down; CEIL rounds up; TRUNCATE drops extra digits.

Available options:
HALF_UP,
BANKERS,
FLOOR,
CEIL,
TRUNCATE
Example:

"HALF_UP"

​
roundingScale
integer<int64>
required

Number of decimal places fee amounts are rounded to.

Example:

2

​
tenantId
string
required

Identifier of the tenant that owns the schedule.

Example:

"550e8400-e29b-41d4-a716-446655440000"

​
updatedAt
string
required

Last update timestamp in RFC 3339 format.

Example:

"2025-01-15T10:30:00Z"

​
usedByContexts
integer<int64>
required

Number of distinct contexts whose fee rules reference this schedule. Computed at read time from the fee rules that reference this schedule (never persisted).

Example:

2