# Retail Spend Examples and Lightning Relay Growth Broaden Bitcoin Payment Use *By Bitcoin Payment Adoption Tracker • June 30, 2026* This brief covers a BTCMap-linked retail purchase example, a Burundi Bitcoin/BIF exchange demonstration, Kenya-focused wallet-flow improvements, and Lightning Enable's growth in L402-based service discovery. It also notes the absence of new regulatory changes or transaction-volume disclosures. ## Major Adoption News ### Burundi — Bitcoin/BIF bridge demonstrated through mysatoshis.bi A Burundi-based demonstration showed participants using `mysatoshis.bi` for direct peer-to-peer exchange between Bitcoin and Burundian Francs (BIF), described as moving "from theory to action" in bridging local currency and Bitcoin [^1]. **Why it matters:** The cited use case is payments-relevant because it shows a direct bridge between Bitcoin and local currency rather than a closed Bitcoin-only flow [^1]. ### Geography not specified in the source post — Richland general shop accepts sats BitBiashara documented a purchase of eggs at **Richland general shop** using sats, and the merchant was published with a BTCMap listing and the contact `richlandgeneralshop@blink.sv` [^2]. **Why it matters:** This is straightforward retail acceptance for a low-ticket everyday purchase, with merchant discoverability strengthened by the attached BTCMap entry [^2]. ## Payment Infrastructure ### Kenya — Tando and BuhoGo reduce LNURL payment friction A Tando-related post highlighted BuhoGo wallet auto-detecting a phone number and automatically filling the domain to complete an LNURL payment [^3]. In a related exchange, a post said the setup had been enabled for Kenya using Tando [^4]. Another post proposed LUD-09 support so the sender could receive a link to an M-Pesa receipt after payment [^5]. **Significance:** The updates target two practical friction points in a Kenya-oriented payment flow: payee entry and post-payment confirmation [^3][^4][^5]. ### Global — Lightning Enable expands relay-based paid-service discovery Lightning Enable said agents can settle payments over Lightning using **L402** [^6]. It also said its agent relay now has **99 live capability events**, including **65+ third-party service listings** from Sats4AI, allowing agents to discover paid services through standard Nostr relay queries instead of a central marketplace or API directory [^6]. > "Open agent commerce should not require every agent to register with the same company. It should work like the internet: keys, relays, signed messages, and payments." [^6] **Significance:** This extends Bitcoin payment infrastructure beyond consumer checkout into machine-to-machine service payments, while keeping discovery and settlement tied to open relay queries and Lightning payments [^6]. ## Regulatory Landscape ### Africa No legal, tax, licensing, or enforcement changes affecting Bitcoin payments were cited in the supplied material for African markets. ### Latin America No regulatory changes affecting Bitcoin payments were cited in the supplied material for Latin American markets. ### Global infrastructure No policy or compliance changes were cited for the payment infrastructure updates covered here. ## Usage Metrics The supplied material did **not** include transaction-volume totals, merchant growth rates, or active-user counts. The clearest quantitative signals were: - **Global:** Lightning Enable said its relay had **99 live capability events** and **65+ third-party service listings** [^6] - **Kenya / Burundi / Paraguay:** the updates were operational or educational, but did not disclose payment counts, user totals, or merchant aggregates [^4][^1][^7] ## Emerging Markets ### Paraguay — Lightning payment education at Asu Bitcoin Meetup Bitcoin Paraguay announced a dedicated Lightning Network workshop at Asu Bitcoin Meetup covering what Lightning is, what problem it solves, and how to use it to send and receive payments quickly and easily [^7]. **Why it matters:** This is not a merchant-integration announcement, but it directly supports payment adoption by teaching practical send/receive workflows to newer users [^7]. ### Kenya — Localized payment UX around phone numbers and M-Pesa receipts The Kenya-related Tando discussion centered on phone-number-based LNURL completion in BuhoGo and the possibility of returning an M-Pesa receipt link through LUD-09 support [^3][^5]. **Why it matters:** The work is tailored to a mobile-money context rather than generic wallet functionality, which is relevant to Bitcoin payment usability in a developing-market setting [^3][^5]. ## Adoption Outlook The strongest signals in this batch were **grassroots and infrastructure-led** rather than enterprise-scale: a mapped retail purchase at Richland general shop, a Burundi demo linking Bitcoin with BIF, Kenya-focused payment-flow refinements, and global growth in Lightning-based service discovery [^2][^1][^3][^5][^6]. What remains missing is measurement and policy detail. The supplied material did not add transaction totals, merchant-growth statistics, or regulatory changes, so the clearest read is continued progress through small merchant examples, local-currency bridges, and usability improvements rather than large disclosed rollouts [^2][^1][^3][^6]. --- ### Sources [^1]: [𝕏 post by @mysatoshi257](https://x.com/mysatoshi257/status/2071497034629009448) [^2]: [𝕏 post by @BitBiashara](https://x.com/BitBiashara/status/2071668285934858319) [^3]: [𝕏 post by @tando_me](https://x.com/tando_me/status/2071506494378352964) [^4]: [𝕏 post by @DrShift3](https://x.com/DrShift3/status/2064370092620550456) [^5]: [𝕏 post by @tando_me](https://x.com/tando_me/status/2071507590761082936) [^6]: [𝕏 post by @lightningenable](https://x.com/lightningenable/status/2071674788049760579) [^7]: [𝕏 post by @BTCParaguay](https://x.com/BTCParaguay/status/2071683128997916806)