> ## Documentation Index
> Fetch the complete documentation index at: https://nextgen-docs.enfuce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

<Card title="Download OpenAPI specification" href="https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/api/mycore/external/processor/server/fee-api/fee-config-v1.openapi.json" style={{ maxWidth:"400px",margin:"0 auto" }} />

The Fee Configuration API lets you retrieve the fee configurations that exist on your tenant, together with the card programs and cards each configuration is currently applied to.

Fee configurations determine the issuer fees charged to your cardholders. For an introduction to the fee types, see the [Issuer Fees](/guides/transaction-lifecycle/issuer-fees/issuer-fees) guide.

<Note>
  Enfuce configures fee profiles based on the requirements you specify with your customer support representative. Use this API to confirm which configurations exist and where they are applied, not to create or edit them.
</Note>

## What a fee configuration contains

Each entry returned by the API carries a `fee_config_id` (the human readable identifier you use when creating or updating a card, for example `SILVER`, `GOLD` or `PREMIUM`) and a `fee_config` object holding up to three fee types:

| Fee type   | Field    |
| ---------- | -------- |
| ATM fee    | `atm`    |
| Cash fee   | `cash`   |
| Markup fee | `markup` |

The `atm`, `cash` and `markup` keys correspond to the `ATM_FEE`, `CASH_FEE` and `MARKUP_FEE` values reported in `transaction.issuerTransactionFees` on the Transaction Event Webhook and Authorisation Request API. See the [Issuer Fees](/guides/transaction-lifecycle/issuer-fees/issuer-fees) guide for what each fee type covers.

Any fee type can be absent from the object when it does not apply to that configuration. Each fee type can carry a `fixed` amount, a `variable` percentage with optional `min` and `max` limits, or both.

## Where a configuration is applied

The `apply_to` object lists the bindings currently in effect for a fee configuration:

* `apply_to.programs`: the card programs using this fee configuration
* `apply_to.cards`: the individual cards where this fee configuration overrides the card program default

<Info>
  Both lists return at most the 1000 most recently created bindings.
</Info>

## Related endpoints

* [Fee Config ID in Create Card Endpoint](https://nextgen-docs.enfuce.com/api/cards/post-card/create-card#body-one-of-0-fee-config-id)
* [Fee Config ID in Partially Update Card Endpoint](https://nextgen-docs.enfuce.com/api/cards/patch-card/partial-update-card#body-fee-config-id)