IBEX

• Name: IBEX
• URL: https://www.poweredbyibex.io/
• Category: bitcoin payments operator / Lightning-liquidity and merchant-infrastructure company / programmable settlement rails company
• Tags: bitcoin-ecosystem
• Summary: IBEX belongs in companies/ because the useful control surface is not just the IBEX Pay checkout shell but the named operator that provisions IBEXHub accounts, manages Lightning nodes and liquidity, decides where fiat conversion and off-ramp workflows exist, and acts as the source of webhook and settlement truth across merchant and API integrations. The practical leverage sits in who operates the node cluster, who issues production access, and who chooses which payment, withdrawal, and conversion paths merchants or apps can actually use.
• What it does:
  • Operates IBEX Pay as the merchant-facing POS, ecommerce, and donation-collection surface for Lightning and onchain bitcoin acceptance
  • Operates IBEXHub, an API platform for creating and paying Lightning invoices, associating onchain addresses, using LNURL flows, and receiving asynchronous webhooks
  • Manages a cluster of Lightning nodes and liquidity for customers so merchants and apps do not need to run their own channels or routing infrastructure
  • Packages account, beneficiary, withdrawal-destination, on-ramp, off-ramp, and crypto send/receive workflows that make the company boundary larger than a simple payment terminal
  • Markets the broader stack as Bitcoin-native programmable settlement rails rather than only as a single merchant app
• Key claims:
  • The main site describes IBEX as The Internet of Payments and Programmable Settlement Rails. Asset-Agnostic. Bitcoin-Native., which is a strong first-party signal that the company wants to be read as payment infrastructure rather than only as a POS app vendor
  • The docs welcome page says IBEXHub lets customers create and pay Lightning invoices, manage unlimited accounts, associate unlimited onchain addresses, use LNURL flows, and receive webhook notifications when asynchronous tasks complete
  • That same docs page says IBEX has a team of dedicated engineers managing a cluster of nodes and Lightning liquidity for customers, which makes the operator boundary explicit in a way many payment sites avoid
  • The docs index shows a much broader managed workflow than accept bitcoin: authentication, account management, webhooks, transactions, beneficiaries, on-ramp, off-ramp, withdrawal destinations, fiat withdrawals to bank accounts, and crypto send/receive all sit under one company-run API surface
  • The IBEX Pay FAQ says BTC settlement to an onchain address takes 24 to 48 hours and that fiat conversion is currently available only in Guatemala, El Salvador, Australia, and the US, which matters because geography and settlement timing are operator policy, not Lightning protocol facts
• Whitepaper: No classic standalone company whitepaper is the key artifact here. The strongest primary materials were the main company site, the IBEXHub docs welcome page, the docs index, and the IBEX Pay FAQ; see ../whitepapers/ibex-company-primary-sources-2026-08-08.md.
• Sources:
  • https://www.poweredbyibex.io/
  • https://www.poweredbyibex.io/about
  • https://docs.poweredbyibex.io/reference/welcome
  • https://docs.poweredbyibex.io/llms.txt
  • https://www.ibexpay.io/
  • https://www.ibexpay.io/support

Internal linkages

• Product-layer note: ibex-pay.
• Closest adjacent hosted merchant operator: opennode.
• Useful merchant-stack contrast when a team wants self-hosted control instead of IBEX-operated workflow: btcpay-server.

Protocol / company boundary

• ibex-pay is the product-layer note for the merchant-facing terminal, checkout, donation, and settlement UX.
• This company note is the operator boundary: account issuance, node and liquidity management, webhook truth, off-ramp and bank-withdrawal workflow, fiat-conversion geography, and the broader API surface all sit with IBEX as a named company.
• That split matters because the dependency merchants and integrators inherit is not just Lightning support; it is a company-managed payment, liquidity, and settlement workflow shell.

Control surface

• Practical leverage sits in merchant and developer admission, Lightning-node and liquidity operation, webhook delivery, settlement timing, fiat-conversion availability, withdrawal-destination policy, and which countries or payout routes are supported.

• The sticky dependency is operational: once a merchant or app relies on IBEXHub accounts, managed liquidity, fiat/off-ramp handling, and IBEX-authored status truth, the real lock-in is to the company-run workflow graph rather than to Bitcoin or Lightning alone.

• Read IBEX as a merchant-and-settlement operator first and a Lightning integration second.

• Last reviewed: 2026-08-08 UTC