How fendfee actually works under the hood.

fendfee earns a referral commission from each partner exchange we send users to. This commission is paid by the exchange, on top of the user's normal trading fee — never deducted from the user's balance and never charged separately.

The exact partner-commission percentage varies per exchange (typically between 50% and 70% of the user's taker fee). We share a configurable majority of that commission back with the user as cashback, retain the rest as our operating margin, and pay a second slice forward to whoever referred that user via our lifetime affiliate program.

Net effect: every taker fee a user pays produces a referral cashflow that is split in three — exchange → fendfee operations → user. The user is paid the largest single share, denominated in USDT.

For every confirmed trading session, our reconciliation job (runs daily, at 03:00 UTC) pulls each partner's commission feed and produces a per-user, per-exchange, per-period table:

• volumeUsd: aggregate trading volume the partner reports for that user
• commissionPaidByExchange: the dollar amount the partner paid fendfee on that volume
• rebatePct: the user's configured cashback share (currently capped at 40%)
• cashbackUsd: commissionPaidByExchange × rebatePct

The result is inserted into a volume_record row, immediately credited to the user's pending balance, and made visible on the user's dashboard. If the user has a referrer, an affiliate commission is computed at cashbackUsd × tierPct and added to the referrer's pending balance in the same transaction.

When a user submits an exchange UID, our matcher compares it against the partner's referral roster. Three outcomes:

1. Match found, referrer is fendfee → UID transitions to approved, cashback accrual begins on the next reconciliation cycle.
2. Match found, referrer is someone else → UID is rejected with the reason "Not registered via fendfee referral"; the user is sent steps to re-register or, where supported by the exchange, complete a KYC transfer.
3. No match found → UID is rejected with a fall-through reason that walks through KYC completion + retry windows.

Most matches resolve within minutes; partner feed lag stretches outliers to a few hours but never longer than 24 hours. Every UID decision is recorded in our audit log with the operator's identifier and a timestamp.

Every withdrawal — regardless of amount — passes through a human review queue before it ever touches a blockchain. A reviewer checks:

• The withdrawal address is verified (the user confirmed it via email code at first use).
• The amount matches the available balance and clears risk-flag heuristics.
• The destination address is not on an on-chain risk database.

The reviewer signs off, the bot or web admin broadcasts the transaction on BEP-20, and the user is emailed with the tx hash and an explorer link. The full review + send loop is designed to clear within one hour of the user confirming the email code. Withdrawals that fail the risk check are returned to the user's available balance with a reason; nothing is ever silently swallowed.

fendfee does not hold, trade, transfer, or otherwise touch user funds. Our integration with each partner exchange is strictly read-only: we receive aggregated trading- volume and commission data, and nothing else.

fendfee does not request, receive, or store any exchange API keys from users. We have no ability to place trades, withdraw assets, or modify positions on a user's exchange account.

The cashback balance that accrues on fendfee is an internal accounting balance, denominated in USDT, paid out by fendfee's own treasury when a user submits a withdrawal request and the manual review passes.

A risk pipeline flags accounts that meet any of the following: multiple registrations from the same IP within a short window, wallet address overlap with known abusive clusters, abnormal trading volume relative to deposit pattern, KYC mismatch between fendfee and the partner exchange, and a few other heuristics whose exact form we don't publish (we don't want to publish the playbook to abusers).

Accounts that score above the risk threshold are flagged for manual review before their next payout. Confirmed abusive accounts are suspended with the reason logged in the audit log and the affiliate chain associated with the abuse is removed from any pending affiliate commission claims.

Our integration with each partner sends them the user's UID and nothing else. We never share a user's email, IP, browsing data, or wallet address with the partner exchange.

fendfee's internal data store is encrypted at rest. Withdrawal addresses are hashed in our audit log so a leaked log file cannot deanonymize the user's wallet history. See the Privacy Policy for the full retention and data-rights breakdown.