Skip to main content
Builder codes let integrators and partners earn a share of trading fees when users trade through their application. Fills attributed to a builder code generate builder rewards for the code owner. This is separate from the referral program. A referral code is used at signup. A builder code is attached when a user trades through an integration.

​
How it works

  1. A builder creates one builder code for its own QFEX account. QFEX generates the code as a UUID.
  2. The builder configures two fee shares in basis points (1 bp = 0.01%):
    • QFEX’s share of the trading fee must be at least 50%.
    • The builder’s share can be set up to 50%.
    • The two shares do not need to add up to 100%.
  3. The builder authenticates each end user separately, normally through QFEX OAuth.
  4. The builder automatically attaches its builder-code UUID when it authenticates that user’s Trade WebSocket connection.
  5. Orders placed over that connection generate builder rewards according to the configured share. The trader still pays the full trading fee.
You do not create a builder code for every trader, and a trader’s QFEX account is not permanently assigned to a builder. Builder attribution is scoped to the Trade WebSocket connection. If the code is missing or invalid, the trader pays the full fee and nobody receives builder rewards.

​
Create a builder code

Each QFEX account may have one active builder code.
  1. Sign in at qfex.com and open your profile.
  2. Open Developer Settings.
  3. Use the Builder code section to create your code and set the QFEX and builder fee shares.
QFEX generates the UUID. Store it in your application’s configuration and attach it automatically to attributed Trade WebSocket connections.

​
Building an aggregator or trading application

If your application needs to let users connect or create QFEX accounts and then trade through your integration, see the Builder Integration Guide. The recommended flow is:
  1. The user selects Connect QFEX in your application.
  2. QFEX handles sign-in, account creation, MFA, and onboarding.
  3. Your application receives a user OAuth token after authorisation.
  4. Your application opens the user’s authenticated Trade WebSocket.
  5. Your application adds your builder UUID to that connection’s auth message.
  6. Orders, stop orders, and TWAPs sent over the connection are attributed automatically.
Your application should never ask the user to hand over their QFEX password, MFA code, or API secret.

​
Builder rewards

The trader continues to pay the normal trading fee. The configured builder share is credited to the builder-code owner’s account as builder rewards. For example, if QFEX’s share is 50% and the builder share is 30%, QFEX keeps 50% of the trading fee, the builder receives 30% as builder rewards, and the remaining 20% is not paid out as builder rewards.

​
For developers

For the full OAuth-to-trading integration, see the Builder Integration Guide. To create or retrieve builder codes over REST, attach them to Trade WebSocket sessions, or read builder rewards programmatically, see the Builder Codes API reference.