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

# TRANSACTION_FEE

> Fired when a fee is posted against a card — such as a cross-border fee or a decline fee.

Fires when a fee is automatically applied to a card. Fee transactions reduce the card's balance by the fee amount. The `merchant` object is absent for fee transactions.

## Event Type

```
TRANSACTION_FEE
```

## Payload

```json theme={null}
{
  "event":       "TRANSACTION_FEE",
  "eventId":     "evt_01HXY123456ABCDEF",
  "businessId":  "BUS1A2B3C4D5E6F",
  "environment": "LIVE",
  "timestamp":   "2026-05-22T10:00:00Z",
  "data": {
    "transactionId":   "txn_01HXYZ4444ABCDEF9999",
    "cardId":          "crd_01HXYZ5555ABCDEF1111",
    "cardholderId":    "chl_01HXYZ1234ABCDEF5678",
    "externalId":      "my-user-id-789",
    "type":            "FEE",
    "status":          "APPROVED",
    "amount":          1.50,
    "currency":        "USD",
    "billingAmount":   1.50,
    "billingCurrency": "USD",
    "feeLabel":        "CROSS_BORDER"
  }
}
```

## Payload Fields

| Field           | Type   | Description                                                                      |
| --------------- | ------ | -------------------------------------------------------------------------------- |
| `transactionId` | string | Unique transaction ID for this fee event                                         |
| `type`          | string | Always `FEE` for this event                                                      |
| `status`        | string | Always `APPROVED` for this event                                                 |
| `amount`        | number | Fee amount in dollars                                                            |
| `feeLabel`      | string | Fee label from the card provider — e.g. `CROSS_BORDER`, `DECLINE`, `MAINTENANCE` |

All other fields are the same as `TRANSACTION_AUTHORIZED`. See [Transaction Events](/v3.20/webhooks/events/transaction-events) for the full field reference.

<RequestExample>
  ```json Webhook Payload theme={null}
  {
    "event":       "TRANSACTION_FEE",
    "eventId":     "evt_01HXY123456ABCDEF",
    "businessId":  "BUS1A2B3C4D5E6F",
    "environment": "LIVE",
    "timestamp":   "2026-05-22T10:00:00Z",
    "data": {
      "transactionId":   "txn_01HXYZ4444ABCDEF9999",
      "cardId":          "crd_01HXYZ5555ABCDEF1111",
      "cardholderId":    "chl_01HXYZ1234ABCDEF5678",
      "externalId":      "my-user-id-789",
      "type":            "FEE",
      "status":          "APPROVED",
      "amount":          1.50,
      "currency":        "USD",
      "billingAmount":   1.50,
      "billingCurrency": "USD",
      "feeLabel":        "CROSS_BORDER"
    }
  }
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {}
  ```
</ResponseExample>


## OpenAPI

````yaml v3.20/openapi.json webhook TRANSACTION_FEE
openapi: 3.1.0
info:
  title: FYATU CaaS API v3.20
  description: >-
    FYATU Cards-as-a-Service API — API key authentication, Cardholder
    lifecycle, Card issuance, Transactions, Webhooks, and Programs.
  version: 3.20.0
  contact:
    name: FYATU Support
    url: https://fyatu.com
    email: support@fyatu.com
servers:
  - url: https://api.fyatu.com/api/v3.20
    description: >-
      FYATU CaaS API — the environment (LIVE or SANDBOX) is determined by the
      API key, not the URL
security:
  - BearerAuth: []
tags:
  - name: Meta
    description: Liveness, account info, and supported event types
  - name: Account
    description: Account-level balance and funding status
  - name: Programs
    description: Read card program configuration
  - name: Cardholders
    description: Create and manage cardholder profiles
  - name: Cards
    description: Issue, fund, freeze, and terminate virtual cards
  - name: Transactions
    description: Read-only card transaction history
  - name: Webhooks
    description: Manage webhook endpoints for real-time event delivery
  - name: Products
    description: Read card product configurations
paths: {}
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key from the FYATU CaaS portal. Pass as `Authorization: Bearer
        <key>`.

````