Use this endpoint to update the fields of a specific fee schedule by its identifier.
Bearer token authentication (format: "Bearer {token}")
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Also accepts Idempotency-Key as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with X-Idempotency-Replayed: true.
See Retries and idempotency for details.
The unique identifier of the fee schedule.
Fee schedule updates
Payload for updating a fee schedule
Updated display name
100"Updated Schedule"
Updated application order
PARALLEL, CASCADING "CASCADING"
Updated number of decimal places
4
Updated rounding method
HALF_UP, BANKERS, FLOOR, CEIL, TRUNCATE "BANKERS"
Successfully updated fee schedule.
The response includes the X-Idempotency-Replayed header.
If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.
Fee schedule with its fee items
Unique identifier for the fee schedule
"019c96a0-2b20-7123-9a1b-2c3d4e5f6a7b"
Tenant that owns this fee schedule
"019c96a0-0a98-7287-9a31-786e0809c769"
Display name for the fee schedule
100"Card Processing - Visa"
Currency code (ISO 4217)
"USD"
How multiple fee items compose
PARALLEL, CASCADING "PARALLEL"
Number of decimal places for rounding
2
Rounding method for intermediate calculations
HALF_UP, BANKERS, FLOOR, CEIL, TRUNCATE "HALF_UP"
Fee items in this schedule
100Creation timestamp in RFC 3339 format
"2025-01-15T10:30:00Z"
Last update timestamp in RFC 3339 format
"2025-01-15T10:30:00Z"