---
title: "Create a fee collection transaction"
method: POST
path: "/v1/accounts/{account_id}/transactions/fees"
tags: ["Fee collection"]
---

# Create a fee collection transaction

`POST /v1/accounts/{account_id}/transactions/fees`

Creates a fee transaction on the account specified in the URL. Solaris will debit the amount from the customer's account and transfer the funds to a Solaris settlement account. Each month, Solaris will pay out the amounts collected from fee transactions to your partner account.

## Path parameters

- `account_id` string, required

## Request body

- object
  - `type` 'ChargeATM' | 'ChargeATMForeignCurrency' | 'CashDepositRetail' | 'CashWithdrawalRetail' | 'ChargeCardDelivery' | 'ChargeCard' | 'ChargeVirtualCard' | 'ChargeReissuePhysicalCard' | 'ChargeAdditionalPhysicalCard' | 'ChargeAdditionalVirtualCard' | 'ChargeReissueVirtualCard' | 'ChargeCardMaintenance' | 'BoosterPackage' | 'ChargeAccountMaintenance' | 'ChargeTopUpCard' | 'ChargeAdditionalAccountMaintenance' | 'ChargeSharedAccount' | 'ChargeAuthorizedUser' | 'ChargeGamblingTransactionPartner' | 'ChargeSEPAInstantOutgoing' | 'ChargeSEPAInstantIncoming' | 'ChargeManualSepaTransferPartner' | 'ChargeIncomingSwift' | 'ChargeGamblingOrCashEquivalent' | 'ChargeFXCardTransaction', required — The type of fee. Note that you may only collect the types of fees that have been enabled for you.
  - `amount` object, required — The amount of the fee transaction.
    - `value` integer, required — The value of the fee, in Euro cents.
    - `currency` string, required — The currency of the fee. Only EUR is currently supported.
  - `original_transaction_id` string — Optional ID to be provided for fee types that relate to or are charged for individual transactions. In this case, you would provide the ID of the booking linked to the transaction.
  - `initiator_reference` string — Optional reference for the fee transaction to be populated by you.
  - `idempotency_key` string — Optional idempotency key to be used when creating the fee transaction.
  - `valuta_date` string — Optional valuta date provided by client. If both 'original_transaction_id' and 'valuta_date' are provided in the request payload, the provided valuta_data will be used.

## Response `201`

The operation was successful.

- FeeTransaction
  - `type` string — The type of fee. Note that you may only collect the types of fees that have been enabled for you.
  - `amount` object — The amount of the fee transaction.
    - `value` integer
    - `currency` string
  - `reconciliation_id` string — An ID linking a fee transaction to an account booking for reconciliation.
  - `initiator_reference` string — Optional reference for the fee transaction to be populated by you.
  - `original_transaction_id` string — Optional ID to be provided for fee types that relate to or are charged for individual transactions. In this case, you would provide the ID of the booking linked to the transaction.
  - `solaris_initiated` boolean — A field to indicate whether the fee transaction solaris initiated or not.
  - `valuta_date` string — Optional valuta date provided by client. If both 'original_transaction_id' and 'valuta_date' are provided in the request payload, the provided valuta_data will be used.

## Other responses

- `400` — There was an error on the client side.
- `403` — You are not authorized to perform this action.
- `404` — The model could not be found.
- `500` — Internal server error.
- `default` — Unexpected error

---

[API](https://skmtc.net/solarisgroup/apis/account-management.md) · [All operations](https://skmtc.net/solarisgroup/apis/account-management/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/account-management/revisions/099ef636a5a1/schema)