Fees

This guide explains the fee model used across the Fintegence Partner API, including platform-level pricing, crypto withdrawal charges, and recommended patterns for collecting partner-defined fees transparently.

Platform Fees

Fintegence pricing may apply across supported products and transaction types. These charges are separate from any additional partner-defined fees that you choose to charge in your own product model.

Commercial Model

Platform fee levels are commercial terms and are defined in your partnership agreement. The exact fee schedule depends on your setup, product scope, and negotiated pricing.

Services Commonly Covered By Commercial Pricing

SEPA Withdrawals: outgoing fiat withdrawals to external bank accounts.

KYC Services: identity verification and related compliance processing.

Currency Exchange: conversion between supported fiat, stablecoin, and cryptocurrency assets.

Crypto Withdrawals: withdrawal processing for blockchain transfers.

Other enabled product operations: according to your commercial agreement.

Internal Transfers

Internal transfers are the current exception and are treated as fee-free in the standard operational model.

At the moment, internal transfers should be treated as a crypto-only flow in practice. Fiat transfers such as EUR are not currently supported.

Card Services Status

Current documentation marks card services as suspended. If your commercial agreement mentions card-related fees, treat them as inactive unless the card module is explicitly re-enabled for your environment.

Crypto Withdrawal Fees

Crypto withdrawals may involve two separate cost components:

Configured Withdrawal Fee: a per-network withdrawal fee exposed in the balances payload.

Dynamic Network Fee: the current blockchain execution cost returned by the network-fee endpoint.

For the list of supported assets and networks, see Supported Currencies.

How To Prepare A Crypto Withdrawal

1. Read Configured Withdrawal Fee And Limits

Use Get Balances for partner context or Get User Balances for user context.

The cryptoBalances[].networkConfig structure contains network-level withdrawal constraints such as:

feeWithdrawal

minWithdrawal

Example structure:

{
  "cryptoBalances": [
    {
      "name": "usdc",
      "amount": "55.184524",
      "networkConfig": {
        "ethereum": {
          "mainnet": false,
          "name": "sepolia",
          "withdrawal": {
            "feeWithdrawal": 10,
            "minWithdrawal": 1
          }
        },
        "polygon": {
          "mainnet": false,
          "name": "amoy",
          "withdrawal": {
            "feeWithdrawal": 0.5,
            "minWithdrawal": 2
          }
        }
      }
    }
  ]
}

2. Read The Current Network Fee

Call the withdrawal network-fee endpoint before submission:

Typical response:

{
  "networkFee": 0.286203
}

3. Calculate Available Amount

To estimate the maximum amount available for withdrawal, subtract both fee components from the available asset balance.

Do Not Assume Fee Symmetry

Configured withdrawal fees come from the balances payload and can differ by asset and network. Network fees are dynamic and can change over time. Always read both values close to execution time.

Partner Fee Collection

Partners may choose to collect their own fees separately from platform fees. The cleanest operational model is to keep partner fee collection as a distinct transfer or balance movement instead of hiding it inside the principal transaction amount.

Recommended Pattern

Where internal transfers are used, keep the fee movement separate from the main transaction flow.

Benefits:

clear audit trail,

easier reconciliation,

explicit user-facing fee reporting,

cleaner separation between platform fees and partner fees.

Important Constraint

Because internal transfers are currently used only for non-fiat crypto flows, do not assume the same transfer pattern is available for fiat fee collection.

Example: Separate Partner Fee Transfer

Using Create Transfer, a partner can move a fee from user balance to partner balance as a distinct operation.

{
  "sourceExternalUserId": "user-123",
  "amount": "5.00",
  "currency": "usdc",
  "description": "Partner service fee",
  "reference": "fee_user123_20240115"
}

Best Practices

Practice	Description	Benefit
Pre-validation	Check the relevant user or partner balance before creating the fee movement.	Reduces avoidable failures
Clear references	Use explicit descriptions and references for fee transfers.	Improves transparency and reconciliation
Sequenced execution	Because processing is asynchronous, design a clear sequence for fee collection and the main operation.	Avoids ambiguous operational states
Separate tracking	Track partner-defined fees independently from platform charges.	Simplifies accounting and dispute handling

Internal Transfers

Crypto Withdrawals

User Crypto Withdrawals

Supported Currencies

Platform Fees#

Services Commonly Covered By Commercial Pricing#

Internal Transfers#

Crypto Withdrawal Fees#

How To Prepare A Crypto Withdrawal#

1. Read Configured Withdrawal Fee And Limits#

2. Read The Current Network Fee#

3. Calculate Available Amount#

Partner Fee Collection#

Recommended Pattern#

Important Constraint#

Example: Separate Partner Fee Transfer#

Best Practices#

Related Documentation#

Platform Fees

Services Commonly Covered By Commercial Pricing

Internal Transfers

Crypto Withdrawal Fees

How To Prepare A Crypto Withdrawal

1. Read Configured Withdrawal Fee And Limits

2. Read The Current Network Fee

3. Calculate Available Amount

Partner Fee Collection

Recommended Pattern

Important Constraint

Example: Separate Partner Fee Transfer

Best Practices

Related Documentation