Fees and your revenue

CRISP lets you configure a trading-fee program for your product. The program defines the total fee, whether it applies to buys, sells or both, and how it is allocated to your treasury, referral beneficiaries and CRISP revenue. Agree the commercial configuration with CRISP before enabling collection.

How a trading fee becomes revenue

Eligible matched trade
  → Fee calculated using the order's saved program
  → Collection into the CRISP collection wallet
  → Allocations reconciled and the UTC day concluded
  → Your treasury payout / user referral claim

An accepted order is not revenue. Fees accrue on eligible confirmed matched notional; an unfilled or cancelled portion does not generate a fee. Partial fills contribute their actual matched amounts. Collection and payout are separate steps, and a pending collection is not yet available to withdraw.

Basis points and allocations

One basis point (bps) is 0.01%. Each program rule is a rate of eligible trading notional, not a percentage of another fee. Rules must add up to the total program rate. The currently enforced total program limit is 1,000 bps (10%).

For illustration only, a 100 bps program on a 100 pUSD trade could allocate:

These are example rates, not a price offer or standard commercial terms. If a referral beneficiary is missing, that allocation goes to your treasury. The referral program guide explains multi-tier configuration and examples.

Amounts are calculated in six-decimal integer token units. The total fee is rounded down; any allocation remainder goes to your treasury so the ledger balances.

What the program fee includes

The program total includes its CRISP revenue, treasury and referral allocations. Applicable venue fees and the separate builder-fee component are outside that total. The 1,000 bps program cap is not an all-in cap on every trading cost. Execution checks account for applicable costs when determining buying power.

Use your active fee program as the source for the total rate, charging sides and allocation rules displayed in your application. Your treasury and referral allocations are portions of that program fee, not additional fees on top of it.

Agree any setup, subscription, support, volume commitments and other commercial terms separately. An API fee configuration does not define the entire contract.

Three different wallet roles

Current program settlement uses pUSD on Polygon. Supply your treasury's Polygon-compatible address to CRISP; CRISP configures the collection wallet and its custody. A user's external contact-wallet address is not their referral payout destination.

Treasury payouts

Treasury allocations accumulate after collections settle and UTC fee days close. Payout policies support daily, weekly or monthly cadence and a minimum amount. The implementation defaults to daily payouts when the eligible unpaid amount is strictly greater than 10 pUSD. Your agreed configuration may differ. Amounts below the threshold remain unpaid allocations rather than being discarded.

This treasury threshold does not apply to user referral claims. A payout is complete only after transfer confirmation; a scheduled date or queued record does not guarantee that funds have arrived. Collection or reconciliation issues can delay eligibility.

Changes apply to future orders

Fee-program changes create new versions. An order retains the program and referral ancestry captured at acceptance, even if it fills after a rate change. Changing the treasury destination also creates a forward-only program version; it does not redirect historical allocations. Coordinate payout-wallet changes with CRISP when older allocations are still outstanding.

Authorized dashboard owners and operators can manage permitted referral settings; only owners can change the payout wallet. Commercial configuration and settlement enablement remain coordinated with CRISP. API access does not provide unrestricted permission to rewrite the whole program.

Reading reports correctly

Distinguish accrued fees, collected fees, your net treasury allocation, pending payouts and confirmed payouts. Program-wide collections include money allocated to referrers and CRISP; they are not all your revenue.

Use the Partner Dashboard for operations and the fees and referrals integration guide for exact API reads and claim behavior.