# Fees Some operations may incur a fee. The API always reports the amount charged in **cents**, and you do not need to calculate anything: the platform applies the fee configured for your account and returns the amount actually charged in the transaction status. ::: tip Where the fee appears The `fee` field in the transaction status (`GET /transfers/:id` for TED, and the PIX status) carries the fee charged for that operation, in cents. When there is no fee, the value is `0`. ::: ## How the fee is charged - **Unit:** cents, like every value in the API. A fee of R$ 5.00 arrives as `500`. - **Timing:** the fee is charged when the operation completes. For outbound PIX it is posted asynchronously, right after settlement, so the `fee` field may appear as `0` on a first query and then reflect the charged value on a later query. - **Source of truth:** the `fee` in the status is the sum of what was actually posted to the fee ledger for that transaction. This is the value you should use to reconcile. - **Limit:** the fee never consumes the whole transaction. The amount charged is always less than the operation amount. - **Debit:** the fee is debited from the account that originated the operation, in addition to the amount transferred. ## Reading the fee of a PIX ```http GET /api/partner/v1/pix/{transactionId} Authorization: Bearer {{access_token}} ``` Response `200`: ```json { "transactionId": "PIX20260711a1b2c3d4e5f6", "type": "pix_out", "status": "settled", "amount": 25000, "fee": 4, "recipientKey": "cliente@empresa.com.br", "endToEndId": "E4602656220260711100000abcdef123", "errorReason": null, "createdAt": "2026-07-11T10:00:00Z", "completedAt": "2026-07-11T10:00:02Z" } ``` In this example the R$ 250.00 operation (`amount: 25000`) had a fee of R$ 0.04 (`fee: 4`). The amount debited from the account was the sum of both. ## Reading the fee of a TED ```http GET /api/partner/v1/transfers/{transactionId} Authorization: Bearer {{access_token}} ``` The TED status also exposes the `fee` field in cents, filled in when the TED settles. ## Fee catalog Lists the active fees that apply to your accounts. The fee schedule itself (values and activation) is managed by Monetarie; the API is read-only. ```http GET /api/partner/v1/fees Authorization: Bearer {{access_token}} ``` - **Scope:** `fee:read` Response `200`: ```json { "data": [ { "feeType": "ted_out", "clientType": "pf", "subType": null, "fixedAmount": 500, "percent": "0", "minAmount": 100, "maxAmount": 900, "chargingModel": "immediate", "freeTransactionsPerMonth": 0, "effectiveFrom": "2026-07-14", "effectiveUntil": null, "scope": "global" } ] } ``` Monetary values (`fixedAmount`, `minAmount`, `maxAmount`) are in **cents**; `percent` is the percentage component of the fee. `scope` indicates where the rule applies: `global` (all accounts), `customer` (one customer) or `account` (one specific account). `effectiveFrom` and `effectiveUntil` bound the validity period. ## Charged fees Lists the fees actually charged to the partner's accounts, correlated with the transaction that originated each charge. ```http GET /api/partner/v1/fees/charges?account_id=10024270&from=2026-07-01&to=2026-07-14&page=1&per_page=50 Authorization: Bearer {{access_token}} ``` - **Scope:** `fee:read` · Optional query-string filters: `account_id`, `origin_transaction_id`, `from`, `to`, `page`, `per_page` (max 200). Response `200`: ```json { "data": [ { "id": "5f6a7b8c-9d0e-4f1a-8b2c-3d4e5f6a7b8c", "feeType": "pix_out_transfer", "amount": 350, "originTransactionId": "E4602656220260714210000aabbccdd0", "originTransactionType": "pix", "originAmount": 10000, "status": "posted", "accountId": 10024270, "chargedAt": "2026-07-14T21:00:00Z" } ] } ``` `status` is `posted` when the fee is booked and `reversed` when it has been reversed. `originTransactionId`, `originTransactionType` and `originAmount` point to the main transaction and its amount. ## Fees in the statement The fee is always a separate entry from the main transaction. In the statement (`GET /accounts/{id}/statement`), fee entries have `type: "fee"` and carry two correlation fields: `feeTransactionId`, the identifier of the fee charge (the same `id` returned by the charged-fees listing), and `originTransactionId`, the transaction that originated the fee. ## The fee.charged event If you prefer to be notified instead of polling, subscribe to the `fee.charged` webhook event, delivered when a fee is charged: ```json { "feeTransactionId": "5f6a7b8c-9d0e-4f1a-8b2c-3d4e5f6a7b8c", "accountId": 10024270, "feeType": "ted_out", "amount": 500, "originTransactionId": "E4602656220260714210000aabbccdd0", "originTransactionType": "ted", "originalAmount": 150075, "status": "posted", "chargedAt": "2026-07-14T21:00:00Z" } ``` The delivery format and signature validation are described in [Webhooks](/en/endpoints/webhooks). ## Operations with no fee Some operation types are free by regulatory requirement and always arrive with `fee: 0`, regardless of the account configuration: - PIX for an individual (pessoa física), as payer or receiver, per Resolution BCB No. 19/2020. - PIX refunds. - Essential payment-account services provided for in the applicable regulation. ## When there is a fee Operations that may incur a fee include, among others, outbound PIX for a company (pessoa jurídica) and TED. The values applied to your account are defined in your agreement with Monetarie and can be checked in the fee catalog on this page. The result of each charge arrives in the `fee` field, in the charged-fees listing and in the `type: "fee"` statement entries. If you need terms different from the current ones, contact your commercial representative. ## Boletos Boleto issuance and settlement are not yet available in the Partner API. When they are released, they will follow the same model described on this page: the operation fee will be reported in cents in the `fee` field of the status, with no calculation on your side. Planning for this feature is in progress.