Skip to main content
This manual is designed to help integrator finance teams accurately track, calculate, and report revenue generated through Bitnob’s Trading API. It includes guidance on data structures, revenue models, reconciliation practices, and reporting formats.

​
Revenue sources

Integrators can generate revenue from trading by:
  • Applying a spread between Bitnob’s quoted rate and the user-facing rate
  • Charging a flat or percentage-based execution fee on trades
  • Offering fixed-rate trades while executing on variable backend pricing
This manual focuses on capturing revenue from both spread and fee-based models.

​
Key terms

​
Revenue calculation methods

A. Spread-Based Revenue Formula: spreadEarned = bitnobOutput - userOutput Unit: Output asset, smallest unit Use when:
  • You fetch a quote from Bitnob
  • Show a slightly different (less favorable) rate to the user
  • Execute at the original Bitnob quote
  • B. Fee-Based Revenue
  • Formula: feeCharged = percentageFee * inputAmount
  • Unit: Input asset, smallest unit
Use when:
  • You display and deduct a transparent fee (e.g., “1% execution fee”)
  • The full quote rate is passed through to the user
C. Combined Model Record both spread and fee independently.

​
Data you must store per trade

Get Order By ID returns the order fields below. Calculate the others in your own system. Track trades in a financial ledger or database table: Record every value as an integer in the smallest unit, not a float: sats for BTC, 6-decimal base units for USDT and USDC, and kobo for NGN. The trading API sends amounts as major-unit decimal strings, so convert them when you record a trade. See Currencies and amounts.

​
Sample monthly report template

​
Reconciliation practices

Reconcile revenue daily or weekly using trade logs from Get Orders, which lists crypto-pair orders only. Fetch NGN orders by ID. Compare wallet balances before and after trade execution Match outputAmount + spreadEarned + feeCharged against Bitnob quote data Review webhook logs to confirm trade completion before counting revenue Ensure reference IDs are unique and mapped to internal user accounts

​
Tax and regulatory notes

Treat earned spread and fees as revenue per local accounting rules Maintain transaction-level records for all earnings If required by jurisdiction, report asset conversions as capital gains/losses

​
When to contact Bitnob finance/Ops

Mismatch between Bitnob wallet balances and internal ledger Unexpected rate fluctuations or misquoted trades Delayed webhook resulting in uncertain trade status