Bitrefill

• Name: Bitrefill
• URL: https://www.bitrefill.com/
• Category: gift-card-and-eSIM commerce operator / crypto catalog platform / Lightning utility sidecar
• Tags: bitcoin-ecosystem
• Summary: Bitrefill is still mostly a crypto catalog business. Keep this project note on the product shell: catalog ordering, order delivery, Thor channel inventory, MCP access, and the software-facing purchase surface. The named operator, partner-approval, and legal/privacy perimeter now live in bitrefill.
• What it does:
  • Lets users buy gift cards, eSIMs, and mobile top-ups with crypto or account balance across 170+ countries via the API/docs surface and 186 countries per the public storefront copy
  • Exposes Personal, Business, and Affiliate API access modes for catalog browsing, invoice creation, order tracking, webhooks, and commission reporting
  • Offers an integration widget so websites and apps can embed Bitrefill’s catalog and earn revenue on sales made inside partner surfaces
  • Operates Thor Lightning utility products, including Lightning recharge, inbound channel capacity, and turbo channel inventory sold through an API
  • Provides a hosted eCommerce MCP server with OAuth or API-key access so AI assistants can search products, create invoices, track payment state, and retrieve delivered redemption info
  • Ships a CLI and related GitHub tooling around MCP and machine-payments experiments, which shows Bitrefill is trying to stay usable for software buyers as well as ordinary storefront users
• Key claims:
  • The API overview says Bitrefill lets developers programmatically purchase gift cards, mobile top-ups, and eSIMs, browse products across 170+ countries, create invoices, pay with Bitcoin, Lightning, Ethereum, USDC, USDT, or account balance, track orders, and manage eSIMs
  • The API overview explicitly separates Personal, Business, and Affiliate API modes, with Business adding full catalog access, test products, BRGC batch creation, account deposits, and dedicated support
  • The eCommerce MCP docs say AI assistants can search products, get product details, create invoices, check invoice status, fetch order details including gift-card codes, and list invoices/orders through 7 hosted tools exposed at https://api.bitrefill.com/mcp
  • The CLI repo says the command-line client dynamically discovers MCP tools, supports API-key and OAuth auth, can export LLM context, and can register Bitrefill as an MCP server plus generate an OpenClaw skill, which is a real software-facing extension but still downstream of the core catalog business
  • The Thor API docs show Bitrefill selling Lightning utility inventory such as lightning-recharge, lightning-channel, and turbo-lightning-channel, with order creation, polling, and webhook flows, which broadens the company beyond generic gift-card commerce without turning it into a payments base layer
  • The help-center integration article says partners can offer thousands of gift cards and mobile refills directly inside their website or app while earning passive income from each sale
  • The GitHub org is domain-verified for bitrefill.com and publicly exposes repos for cli, bitrefill-mcp-server, agents, awesome-agentic-payments, and x402, reinforcing that Bitrefill is trying to meet software buyers where they are instead of only serving a human storefront
• Whitepaper: No canonical Bitrefill whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were Bitrefill’s API docs, MCP docs, Thor API docs, help-center integration guidance, and first-party GitHub org/repositories; see ../whitepapers/bitrefill-primary-sources-2026-05-01.md.
• Sources:
  • https://www.bitrefill.com/
  • https://docs.bitrefill.com/docs/api-overview
  • https://docs.bitrefill.com/docs/ecommerce-mcp
  • https://help.bitrefill.com/hc/en-us/articles/8576552808722-Can-I-integrate-Bitrefill-and-sell-gift-cards-directly-from-my-website-or-app
  • https://github.com/bitrefill
  • https://github.com/bitrefill/bitrefill-mcp-server
  • https://github.com/bitrefill/cli
  • https://github.com/bitrefill/thor-api-doc

Internal linkages

• Company / operator boundary for partner approval, credential issuance, webhook truth, and the legal shell: bitrefill.
• Strongest upward payments-stack reads: btcpay-server and blink.

Protocol / company boundary

• Keep this project note on the product shell: catalog browsing, invoice creation, MCP and CLI packaging, Thor utility products, and the user- or agent-facing purchase flow.
• Use bitrefill for the named-operator layer around partner admission, Personal-versus-Business-versus-Affiliate credentialing, account and balance workflow, webhook and redemption truth, affiliate attribution, and the Airfill legal/privacy perimeter.
• That split matters because what can the Bitrefill product do? and which company controls resale access, credential issuance, and purchase workflow truth? are related but not identical questions.

Control surface

• At the product layer, the leverage sits in catalog presentation, invoice and redemption UX, Thor packaging, and whichever MCP, CLI, or API surfaces Bitrefill keeps polished for software buyers.

• The partner-approval, credentialing, webhook-truth, and legal-boundary questions now point upward to the company note because the practical authority there is organizational, not merely product-shaped.

• Read it as a commerce product with some Lightning utility inventory. The MCP and paid-API angle is real, but still downstream of the broader company-run workflow shell.

• Last reviewed: 2026-08-07 UTC