Looking for a Blockonomics alternative? Here is how chainkit compares
Both are non-custodial Bitcoin payment processors. The differences: pricing shape, receipts and tax handling, webhook verification, and how much of the stack you can inspect.
If you're searching for a Blockonomics alternative, you probably already agree with the premise both products share: a payment processor should never hold your money. Blockonomics pioneered the xpub-based, direct-to-wallet model, and it deserves credit for that. This post is about where the two products make different calls — so you can pick on facts, not vibes.
Competitor details below reflect Blockonomics' published pricing and docs as of July 2026 — if something has changed since, trust their site over this post. The always-current, line-by-line version lives at /compare-blockonomics.
Where we're the same
Both products are non-custodial: you register an extended public key, every invoice derives a fresh address, and customers pay straight into your wallet. Both give you invoices, webhooks, and an API. Neither can spend your funds, freeze your account balance, or get between you and your money. If custody is your only criterion, you have two good options — and that's a good problem.
Difference 1: pricing shape
Blockonomics charges a flat 1% per transaction, with 20 free incoming payments (lifetime). chainkit bills a smaller percentage of settled volume against a monthly minimum — you pay whichever is greater, and the free tier renews monthly instead of capping for life.
The shapes cross: at low volume a flat 1% is cheaper; past the breakeven point the minimum-plus-smaller-fee model wins, and the gap widens as you grow. We put a worked example with live numbers in the comparison table — at five figures of monthly volume the difference is real money every month.
Difference 2: receipts and tax are first-class
chainkit invoices are fiat-priced with the BTC rate locked and printed at issuance, and every invoice renders an immutable PDF receipt carrying your business identity, VAT id, and tax breakdown — snapshotted at issue time. Quarter-end, your accountant gets CSV/JSON exports and a bulk receipts ZIP. If you sell to EU customers, there's a PII-redaction endpoint for GDPR "forget" requests, and hosting is EU-based.
Blockonomics gives you the payment rails; the bookkeeping layer is largely yours to build. If you already have invoicing software you love, that might be fine. If you don't, it's the difference between "accepting Bitcoin" and "running a business that accepts Bitcoin."
Difference 3: webhook verification
chainkit callbacks are HMAC-signed and verified in one SDK call — plus, if you run the Go SDK, an SDK-side watcher can see confirmations independently of the cloud, so you're not trusting even us as the single source of payment truth. Invoice creation is idempotent, so network retries can't double-issue.
Difference 4: what's underneath
chainkit's payment detection runs on a multi-provider RPC routing layer (nine providers, scored and failed-over per call) — the same MIT-licensed Go SDK anyone can read and run. The provider fleet we route against is public, live, on the scoreboard. When a block explorer API has a bad afternoon, your payment confirmations shouldn't.
Where Blockonomics is the right call
Honesty cuts both ways. Blockonomics has been around far longer, supports store plugins we don't yet (notably its long-standing WooCommerce integration), and its flat 1% with no minimum is genuinely better for a shop doing a handful of small payments a month. If that's you today, it's a fine choice — the comparison page will still be here when your volume grows.
Switching is a small afternoon
Both products key off an xpub, so migration is: paste the same xpub into chainkit, verify a derived address against your wallet (the console walks you through it), point your checkout at the invoice API, and swap the webhook handler to verified HMAC callbacks. Your funds were never in either product, so there is nothing to withdraw or transfer — start here.