IBEX Pay

• Name: IBEX Pay
• URL: https://www.ibexpay.io/
• Category: hosted Bitcoin merchant checkout wrapper / Lightning terminal shell / optional fiat-conversion middleware
• Tags: bitcoin-ecosystem
• Summary: IBEX Pay is still worth keeping as a product note because the merchant-facing surface is specific enough: POS, ecommerce checkout, donation flows, settlement timing, and the narrow country window where fiat conversion appears. The named operator boundary around IBEXHub accounts, node and liquidity management, webhook truth, and broader payment / withdrawal workflow now lives in ibex. Useful shell, but still not a merchant-stack center.
• What it does:
  • Runs a Bitcoin Payment Terminal on iOS and Android for in-person Lightning acceptance
  • Supports hosted ecommerce and marketplace checkout for Lightning and onchain bitcoin
  • Settles merchant funds to a BTC address, with optional fiat conversion in a small set of countries
  • Offers LNURL donation flows and references plugin or API implementations for common commerce platforms
  • Keeps onboarding, account access, and support inside the IBEX-operated platform
• Key claims:
  • The core product is simple: present a Lightning QR, take payment, then settle to bitcoin or convert to fiat where IBEX is willing to intermediate
  • The real operator details are settlement timing, fee levels, country limits on fiat conversion, and the split between Lightning-first checkout and onchain handling for larger payments
  • The ecommerce plugins and donation flows make it broader than a point-of-sale app, but not by much; it is still merchant software, not a deeper Lightning primitive
  • IBEX’s broader Lightning-infrastructure posture matters mainly because it explains why this hosted gateway exists, not because IBEX Pay itself becomes a category anchor
• Whitepaper: No canonical standalone IBEX Pay whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, product pages, and support FAQ; see ../whitepapers/ibex-pay-primary-sources-2026-04-30.md.
• Sources:
  • https://www.ibexpay.io/
  • https://www.ibexpay.io/support
  • https://www.ibexpay.io/ibex-pay-point-of-sale-for-merchants
  • https://www.ibexpay.io/ibexpay-payment-gateway-for-marketplaces
  • https://www.ibexpay.io/ibexpay-donations-lnurl
  • https://ibexpay.ibexmercado.com/login
  • https://ibexpay.ibexmercado.com/onboard

Internal linkages

• Company / operator boundary for IBEXHub account issuance, node and liquidity management, webhook truth, and fiat / withdrawal policy: ibex.
• Best upward product reads: btcpay-server and opennode.

Protocol / company boundary

• Keep this note on the merchant-facing product surface: terminal UX, ecommerce checkout, donation flow, settlement window, and the practical difference between Lightning-first payments and the fallback onchain path.
• Use ibex for the named-operator layer around account issuance, managed nodes and liquidity, webhooks, fiat-conversion geography, and the wider payout / withdrawal workflow.
• That split matters because how does IBEX Pay behave for a merchant? and who actually operates the payment and settlement shell behind it? are related but not identical questions.

Control surface

• At the product layer, power sits in hosted checkout and terminal defaults, settlement timing, invoice expiry, plugin coverage, and how easy IBEX makes Lightning versus onchain acceptance for merchants.

• Read it as hosted merchant software with a Lightning-heavy shell. The terminal and donation surfaces are packaging, not new rails.

• For the node, liquidity, and broader settlement-workflow authority behind that shell, read ibex.

• Last reviewed: 2026-08-08 UTC