Fees - Orenda Management API

Programs charge customers from a fee catalog. Catalog changes are made by the Orenda team (contact us); operators can read the catalog and produce customer-facing fee documents.

Reading the catalog

Endpoint	What it does
`GET /fees`	The program’s fee catalog. Still on the unprefixed path — there is no `/v1` equivalent yet.
`GET /v1/fees/csv`	The same catalog exported as CSV (data URI, Excel-friendly BOM).

A fee row is keyed by where and what it applies to:

Field	Values
`region`	`UK`, `EU`, `GLOBAL`
`accountType`	`CONSUMER`, `CORPORATE`
`tier`	Program-defined tier name
`currency`	`GBP`, `EUR`, `USD`, crypto currencies, or `MULTI`
`paymentType`	`PAYIN`, `PAYOUT`, `CUSTOMER`, `ACCOUNT`, `SCHEDULE`, `CARD`, `FEE`, `CRYPTO`
`paymentSubType`	The rail/action, e.g. `SEPA`, `BACS`, `CHAPS`, `SWIFT`, `ATM`, `PC_SETUP`, `VC_SETUP`, `MONTHLY`
`feeType`	`TRANSACTION`, `MAINTENANCE`, `SETUP`
`fixedFee` / `percentageFee`	The charge amounts
`threshold`	Usage band: `"N"` or `"N-M"`

Customer-facing fee documents

GET /v1/customers/{customerId}/accounts/{accountId}/fee-reports?type=info|statement — generates a PDF (returned as a base64 data URI):

type=info — the fee information sheet for the customer’s tier and region.
type=statement — the fee statement for a given year (required with statement).

Errors worth handling: ACCOUNT_NOT_FOUND, APPLICATION_NOT_FOUND, NO_FEE_TRANSACTIONS (statement for a year with no fees), NO_FEES_FOR_SELECTION.