Cowrie Research

bitrefill-company-primary-sources-2026-08-07

5 min read

Bitrefill company primary-source snapshot

Fetched: 2026-08-07 UTC

1) API overview

Source: https://docs.bitrefill.com/docs/api-overview

Selected excerpts from the official docs:

The Bitrefill API lets you programmatically purchase gift cards, mobile top-ups, and eSIMs.

The Personal API lets you access Bitrefill programmatically using a Bearer token from your personal account.

Contact the Bitrefill team to set up a Business account … Receive your API ID and API Secret.

Apply to the Bitrefill Affiliate Program … Once approved, receive your API credentials.

Additional signals from the API overview:

  • Bitrefill splits access into Personal, Business, and Affiliate modes rather than exposing one flat public API surface.
  • The self-service personal path versus approved Business / Affiliate access is a strong company-boundary clue: the operator decides who gets fuller catalog access, test products, deposits, and dedicated support.
  • Credential issuance and account structure are part of the real dependency, not just the gift-card catalog.

2) Resell / partner integration flow

Source: https://docs.bitrefill.com/docs/integration-flow

Selected excerpts from the official docs:

A typical integration involves five steps: Cache Products → Create Invoice → Pay Invoice → Receive Webhook → Deliver to User

When an invoice reaches its final state, Bitrefill POSTs to your webhook_url.

Once the invoice is complete, get the redemption info … order.redemption_info.code … order.redemption_info.instructions

Additional signals from the integration docs:

  • The standard B2B pattern assumes one company-managed control plane for product availability, invoice creation, payment confirmation, webhook delivery, and final redemption state.
  • Bitrefill explicitly tells partners to cache the product catalog and refresh it regularly because products can go out of stock or have issues, which shows catalog admission and inventory truth sit with the operator.
  • The same docs treat delivery notifications and redemption details as company-hosted workflow primitives rather than protocol-native state.

3) Hosted eCommerce MCP

Source: https://docs.bitrefill.com/docs/ecommerce-mcp

Selected excerpts from the official docs:

Every MCP session is authenticated. When you connect, you sign in to your Bitrefill account via OAuth.

For programmatic access or clients that don’t support OAuth, use an API key in the URL instead.

The MCP server exposes 7 tools.

buy-products returns JSON with an agent_instructions field that guides the agent on next steps.

Additional signals from the MCP docs:

  • The hosted MCP endpoint is not just a passive wrapper; it is a curated agent-facing operating surface with controlled auth paths and a bounded tool set.
  • OAuth sign-in and API-key fallbacks mean Bitrefill decides which identities and credentials can purchase through agent workflows.
  • The same endpoint becomes the source of invoice, order, and redemption truth for AI-assisted purchases.

4) Partner widget guidance

Sources:

Selected excerpts and snippets from first-party pages:

Yes, with Bitrefill’s integration widget you can offer thousands of gift cards and mobile refills available from Bitrefill, directly to your customers from within your website or app, while earning a passive income from each sale.

If you submit more details about your request … it will go to our management team, who will reach out to you with more details about working together if it is a good fit.

Grow your Business with the Bitrefill widget … offer thousands of gift cards to your customers worldwide, while earning a passive income from each sale. Become a partner.

Additional signals from the partner materials:

  • Bitrefill is explicit that partner distribution is approval- and relationship-based, not a neutral open catalog anyone can redistribute the same way.
  • The management-team review language matters because it places marketplace expansion, partner admission, and revenue-share packaging inside a named operating shell.

5) Legal / privacy perimeter

Sources:

Because direct fetches of these pages were Cloudflare-blocked in this pass, the strongest accessible evidence came from search snippets pointing at the official URLs.

Selected snippet text observed from search results:

This privacy policy is issued on behalf of AIRFILL PREPAID AB, a limited company incorporated under the laws of Sweden and registration no. 559001-6035 (“Airfill”). Airfill is a data controller of the personal data collected through our websites www.bitrefill.com and www.airfill.com (“Websites”), or through our mobile application Bitrefill …

These Terms, the transactions between Customers and us made through Bitrefill, and any disputes relating to these Terms or the Customer’s use of Bitrefill, shall be governed in all respects by the laws of Sweden and shall be resolved exclusively in the courts of Sweden.

Additional signals from the legal pages:

  • The privacy materials tie the Bitrefill product shell to a named Swedish company boundary: Airfill Prepaid AB.
  • The terms snippet makes the legal forum and governing law explicit, which helps justify a company note separate from the product note.

6) GitHub org / AI-facing repos

Source: https://github.com/bitrefill

Selected excerpt from the GitHub org page:

Agent skills for Bitrefill: browse, buy, and manage gift cards, mobile top-ups, and eSIMs from AI coding agents.

A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.

Browse, buy, and manage gift cards, mobile top-ups, and eSIMs from the command line.

Additional signals from the GitHub org page:

  • The verified first-party GitHub org reinforces that Bitrefill is intentionally packaging AI- and CLI-facing access modes around the same commerce backend.
  • This is useful support for the company note because it shows one operator curating not only a storefront but also agent, MCP, and command-line distribution surfaces.

Notes

  • This pass did not surface a classic Bitrefill company whitepaper or litepaper.
  • The strongest current company-boundary materials are Bitrefill’s own API docs, partner/reseller docs, MCP docs, help-center partnership guidance, and the official legal-page snippets that identify Airfill Prepaid AB and Swedish-law governance.
  • Bitrefill is best treated as a named commerce operator boundary around catalog access, partner admission, invoice and redemption workflow, credential issuance, and agent-facing purchase surfaces rather than as a neutral payment rail or generic merchant protocol.

Graph View