This page covers the concept and the query endpoint reference. To understand how the platform fee factors into value splitting, see Split.
How a fee is composed
Every fee is described by two fields:The fee percentage. Example:
3.99 means 3.99% of the transaction amount. Use 0 when there is no percentage component.The fixed component in cents (integer). Example:
350 means R$ 3.50. Use 0 when there is no fixed component.percentage: 3.99 and fixed: 0 charges only 3.99% of the amount. A boleto fee with percentage: 0 and fixed: 350 charges a flat R$ 3.50 per boleto, regardless of the transaction amount.
Resolved fees per account
The table returned by the API delivers the effective value already resolved for your account. You get the final fee that applies to your transactions — without needing to know where it comes from or combine any rules yourself.- When a specific fee is not configured, it defaults to
0(both percentage and fixed). - The fee is per currency (ISO 4217:
BRL,USD…). Without thecurrencyparameter, the API uses the default currency configured for your account.
The platform fee in splits
When you use Split to divide a transaction amount among recipients, you can inject a platform fee as a split item. In the split configuration payload, each item has atype field:
The split item type. Possible values:
sale (sale — default), interest (interest) and platform_fee (platform fee).type: "platform_fee" represents the portion that goes to the platform account, separate from the recipients’ sale portions. This is what allows the platform to retain its margin on each split transaction.
The fees from the
GET /fees endpoint are the PSP fees charged to your account (Pix, boleto, card, withdrawal, refund, chargeback). The platform_fee in a split is a division that you define within a transaction. These are distinct concepts — do not confuse them. The complete splitting mechanics, including the rules for processingFee and liable, are covered in Split.Endpoints
| Method | Route | Description |
|---|---|---|
GET | /fees | Returns the resolved fee table for your account |
Retrieve the fee table
GET /fees
Returns the resolved fees for your account: Pix, boleto, credit card from 1 to 12 installments, withdrawal, refund, and chargeback (fee + penalty). Each fee includes percentage and fixed (in cents).
Authentication uses the x-api-key header (see Authentication).
Query parameters
The currency code in ISO 4217, exactly 3 letters (e.g.
BRL, USD). Automatically converted to uppercase. Optional — without it, the API uses the default currency configured for your account.Request example
Response 200 OK
The numbers above are examples. The actual fees for your account may differ — the response always reflects what is configured for your company.
Response fields
The currency of the returned fees (ISO 4217). If you did not pass
currency in the query, this is the account’s default currency.Fee for the Pix payment method. Object with
percentage and fixed.Fee for the boleto payment method. Object with
percentage and fixed.Array with one entry per installment count, from 1 to 12 (always 12 items). Each entry includes
installments (number of installments), percentage, and fixed.Withdrawal/payout fee. Object with
percentage and fixed.Refund fee. Object with
percentage and fixed.Chargeback-related fees. Contains two sub-objects:
fee (chargeback fee) and penalty (chargeback penalty), each with percentage and fixed.Errors
The endpoint returns200 OK on the happy path. Authentication errors (invalid or missing key) follow the standard API error format. See Errors for the list of status codes and the response format.
See also
Reference: Fees
Technical details of the fees endpoint in the Core API.
Split
How to split amounts among recipients and inject the platform fee.
Values overview
How Z2Pay calculates fees, splits, and settlement.
Settlement
When and how net amounts land in your wallet.

