> ## Documentation Index > Fetch the complete documentation index at: https://developer.finogates.com/llms.txt > Use this file to discover all available pages before exploring further. # List Your Fee Schedule > Return your platform's **complete, effective fee schedule** in a single call — one row per fee line (wallet, ACH, card, check-mail, international, comms, …). Each line is the value that will actually be charged: your own configured **override** if one is set, otherwise the platform-wide **default**. Read the ``source`` field to tell them apart: - ``"override"`` — a value Finogate configured specifically for your platform. - ``"default"`` — the universal default; you inherit it because no override exists for this line. A schedule that mixes the two is normal and fully represented here. Per line you get: ``fee_code``, ``label``, ``category``, ``domain``; the active ``structure`` (``flat`` / ``percent`` / ``flat_plus_percent`` / ``per_unit`` / ``tiered`` / ``component``) and the ``allowed_structures`` it can take; the fee ``bearer`` (``payer`` / ``payee``); the concrete ``actions`` (the fee numbers — e.g. ``flat_fee`` / ``percent_fee`` / tier brackets, in major units) and ``caps`` (``min_fee`` / ``max_fee``); the ``source`` flag; and metadata flags (``is_metered``, ``is_dormant``, ``supports_caps``, ``amount_based``). ## OpenAPI ````yaml GET /v1/platform/fees/catalog openapi: 3.1.0 info: title: Finogate Platform API v1 version: 0.1.0 servers: - url: https://api-sandbox.finogates.com description: Sandbox - url: https://api.finogates.com description: Production security: [] tags: - name: auth - name: users - name: payees - name: verification - name: bank accounts - name: card processing - name: digital-assets - name: international - name: fees - name: onboarding - name: pending-applications - name: wallets - name: payments - name: document mailing - name: merchant onboarding - name: catalog - name: webhooks - name: screening - name: Platform - File Scanning - name: phone-numbers - name: sms - name: calls - name: listings - name: Card Transfers - name: embed-tokens paths: /v1/platform/fees/catalog: get: tags: - fees summary: List Your Fee Schedule description: >- Return your platform's **complete, effective fee schedule** in a single call — one row per fee line (wallet, ACH, card, check-mail, international, comms, …). Each line is the value that will actually be charged: your own configured **override** if one is set, otherwise the platform-wide **default**. Read the ``source`` field to tell them apart: - ``"override"`` — a value Finogate configured specifically for your platform. - ``"default"`` — the universal default; you inherit it because no override exists for this line. A schedule that mixes the two is normal and fully represented here. Per line you get: ``fee_code``, ``label``, ``category``, ``domain``; the active ``structure`` (``flat`` / ``percent`` / ``flat_plus_percent`` / ``per_unit`` / ``tiered`` / ``component``) and the ``allowed_structures`` it can take; the fee ``bearer`` (``payer`` / ``payee``); the concrete ``actions`` (the fee numbers — e.g. ``flat_fee`` / ``percent_fee`` / tier brackets, in major units) and ``caps`` (``min_fee`` / ``max_fee``); the ``source`` flag; and metadata flags (``is_metered``, ``is_dormant``, ``supports_caps``, ``amount_based``). operationId: get_fee_catalog_v1_platform_fees_catalog_get responses: '200': description: Your platform's full effective fee schedule, one row per line. content: application/json: schema: $ref: '#/components/schemas/ListResponse' example: status_code: 200 data: - fee_code: ach.push label: ACH Push category: ACH domain: payout structure: flat_plus_percent allowed_structures: - flat - percent - flat_plus_percent - tiered bearer: payer bearer_selectable: true is_metered: false is_dormant: false supports_caps: true amount_based: true actions: flat_fee: 0.25 percent_fee: 0.5 caps: min_fee: 0.25 max_fee: 5 source: override policy_id: 7a1c9e2b-4d6f-4a8b-9c1e-2d5f3a6b7c8d - fee_code: card.acquiring label: Card Acquiring category: Card domain: funding structure: component allowed_structures: - component bearer: payer bearer_selectable: false is_metered: false is_dormant: false supports_caps: true amount_based: true actions: processing_fee: percent_fee: 2.9 flat_fee: 0.3 bearer: payer delivery_fee: flat_fee: 0 bearer: payee caps: {} source: default row_count: 2 query_generated_time: 1712847600000 security: - _AuthenticatedBearer: [] components: schemas: ListResponse: properties: status_code: type: integer title: Status Code description: HTTP status code for the response. data: title: Data description: Payload or error details. query_generated_time: type: integer title: Query Generated Time description: >- UTC timestamp (milliseconds since epoch) when response was generated. row_count: type: integer minimum: 0 title: Row Count description: Total rows matching the request filters (not just this page). limit: anyOf: - type: integer minimum: 1 - type: 'null' title: Limit description: >- Page size used for this response. Null for cursor-paginated endpoints. current_page: anyOf: - type: integer minimum: 1 - type: 'null' title: Current Page description: >- 1-indexed page number for this response. Null for cursor-paginated endpoints. total_page_number: anyOf: - type: integer minimum: 0 - type: 'null' title: Total Page Number description: >- Total number of pages given the current limit. Null for cursor-paginated endpoints. next_cursor: anyOf: - type: string - type: 'null' title: Next Cursor description: Cursor for the next page, if available. type: object required: - status_code - data - query_generated_time - row_count title: ListResponse description: |- Standard response wrapper for list responses. Declare ``ListResponse[list[SomeModel]]`` to render the real ``data`` array schema in OpenAPI/Swagger; a bare ``ListResponse`` leaves ``data`` untyped. securitySchemes: _AuthenticatedBearer: type: oauth2 flows: password: scopes: {} tokenUrl: /v1/platform/auth/token ````