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

EndpointWhat it does
GET /feesThe program’s fee catalog.
GET /v1/fees/csvThe same catalog exported as CSV (data URI, Excel-friendly BOM).
A fee row is keyed by where and what it applies to:
FieldValues
regionUK, EU, GLOBAL
accountTypeCONSUMER, CORPORATE
tierProgram-defined tier name
currencyGBP, EUR, USD, crypto currencies, or MULTI
paymentTypePAYIN, PAYOUT, CUSTOMER, ACCOUNT, SCHEDULE, CARD, FEE, CRYPTO
paymentSubTypeThe rail/action, e.g. SEPA, BACS, CHAPS, SWIFT, ATM, PC_SETUP, VC_SETUP, MONTHLY
feeTypeTRANSACTION, MAINTENANCE, SETUP
fixedFee / percentageFeeThe charge amounts
thresholdUsage 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.