Fees & Revenues
Complexity is the enemy of profitable growth, we therefore apply a simple pricing structure.
While the vast majority of Web3 projects are not profitable nor run like real organisations, our business model is based on growing our revenue streams substantially over the next 5 years, with focus on profitable growth.
Our Fees & Revenues model is based on three main revenue streams:
- 1.Sprynt Mint
- 2.Sprynt Connect
- 3.Sprynt Pay
We collect 2.5% fees on transactions passing through our Multi-chain NFT minting engine (ie. NFTs sold), with no upfront cost charged to projects (excl. the cost of contract deployment that is incurred by projects, as we are a fully non-custodial solution).
Optional: fully customised/branded webpage & URL (at an additional cost)
We will charge based on transactions passing through our Web3 Checkout API infrastructure.
We will charge based on transactions passing through our Sprynt Pay checkout.
In addition to fees on transactions, Sprynt Pay offers a wide range of add-ons, designed to make the merchant experience seamless:
- Instant settlement in stable coin service: For merchants wanting to avoid any exposure to native tokens price volatility, we are working on offering an instant settlement scheme to instantly swap any native token deposits into stable coins.
- Conversion into fiat for merchants: Sprynt Pay enables merchants to (automatically) convert any cryptocurrency received into fiat.
- Enhanced withdrawal support for merchants: Enable merchants to withdraw funds from contracts on different chains more easily & faster, relying on funds wrapped into NFT contracts (with the ability to move entire portfolios of funds in one transaction)..
Based on our fee model and different key drivers, we modelled our estimated revenue forecast in the coming years. These estimates are based on assumptions and hypotheses on the overall Web3 market in the next 5 years, as well as Sprynt's expected performance. (Note: All on-chain data is sourced through DefiLlama, DAppRadar and Dune)

Our estimated revenue forecasting is based on different drivers, the main one being the average transaction volume (in $) flowing through our solution.
Benchmarking provides insights into the estimated monthly transaction volumes behind our base case scenario & puts our revenue estimates in perspective.

Comparing Sprynt to more established projects, we can see that the projected monthly volume we modelled for the next 5 years (in our base case scenario) is still quite 'small' compared to the biggest players such as Paraswap, Uniswap or Stripe)
Last modified 18d ago