<?xml version="1.0" encoding="UTF-8"?>
<!--
  Regenerated from posts.json on every publish. Do not hand-edit.
  Each post becomes one <item> inside <channel>, newest first:

  <item>
    <title>POST TITLE</title>
    <link>https://riverark.io/blog/SLUG/</link>
    <guid isPermaLink="true">https://riverark.io/blog/SLUG/</guid>
    <description>POST DESCRIPTION</description>
    <category>CATEGORY</category>
    <pubDate>Fri, 08 Aug 2026 00:00:00 GMT</pubDate>
  </item>
-->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>riverArk Blog</title>
    <link>https://riverark.io/blog/</link>
    <atom:link href="https://riverark.io/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Practical writing on accepting Bitcoin in unattended retail, micro-markets, and e-commerce, and on the architecture underneath it.</description>
    <language>en-us</language>
    <!-- ITEMS:START -->
    <item>
      <title>Bitcoin Payments Without Custody: How It Works</title>
      <link>https://riverark.io/blog/bitcoin-payments-without-custody/</link>
      <guid isPermaLink="true">https://riverark.io/blog/bitcoin-payments-without-custody/</guid>
      <description>Every Bitcoin payment processor makes a choice: hold your money or send it straight to you. Here's how non-custodial settlement actually works.</description>
      <category>Payments</category>
      <pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Bitcoin Payments for Self-Checkout Kiosks</title>
      <link>https://riverark.io/blog/accept-bitcoin-self-checkout-kiosk/</link>
      <guid isPermaLink="true">https://riverark.io/blog/accept-bitcoin-self-checkout-kiosk/</guid>
      <description>A self-checkout kiosk customer already has a screen and a phone out. Bitcoin Lightning adds a scan-to-pay tender with no new hardware and no counter time.</description>
      <category>Unattended Retail</category>
      <pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <!-- ITEMS:END -->
  </channel>
</rss>
