Concepts

How QBitFlow works

One transaction, wallet to wallet. QBitFlow prepares it, follows it and tells you; it never holds the money.

block 48,640,429 · confirmed ✓

A real payment on Base. Every value here is on-chain: check the transaction ↗ (opens in a new tab) · the contract ↗ (opens in a new tab)
  1. Your server creates a checkout link with QBitFlow's API: data only, no funds.
  2. Your customer pays from their own wallet, to the payment contract, on-chain.
  3. The contract sends QBitFlow its fee, plus the network fee that repays the gas QBitFlow paid to send this token payment, and the rest to your wallet, in the same transaction.

What QBitFlow does

  • Opens checkouts. Your server creates one (POST /checkout-sessions/payment) and sends your customer to its link.
  • Prepares the exact transaction. Once your customer picks a currency, QBitFlow quotes the amount and the network fee. A signed transaction that differs from what was prepared is refused.
  • Follows it to the end, records the payment, and sends your server a signed webhook: fulfil on it (webhooks).
  • Bills subscriptions on their due dates, within what the customer approved (subscriptions).
  • Keeps the records: payments, bills, refunds, customers, test and live apart.

A token payment is signed by the wallet and sent by QBitFlow's operator, which pays the gas and is paid back in the token; a payment in a chain's own coin is sent by the wallet itself (network fees).

What QBitFlow never holds

  • Your money. It lands in your wallet in the transaction that pays it, so a refund comes from your wallet too (refunds). A marketplace may hold a seller's funds, but in its own wallet (held payouts).
  • Your wallets' keys. You add a wallet by signing; refunds and payouts are signed by your wallet, in the dashboard. A seller's wallets are theirs too.
  • Your subscribers' money. They approve an allowance once; each bill pulls one period's price when it's due. Nothing is prepaid.

QBitFlow keeps an API key's hash (never the key), your endpoints' secrets, and the records.

The contracts

QBitFlow's contracts are open source, and every payment is a transaction anyone can check: payments, bills and refunds carry txHash and explorerUrl. The split happens in the contract and is recorded as paid in settlement.split (fees).

QBitFlow settles on Ethereum, Base and Solana (currencies and chains); test mode runs on their test networks, with faucet tokens.