From 405e84ef300e6a8a380904f42118dd18e510b1f1 Mon Sep 17 00:00:00 2001 From: Rae McKelvey <633012+okdistribute@users.noreply.github.com> Date: Thu, 26 Mar 2026 16:06:56 -0700 Subject: [PATCH 01/13] Add pos/payments page --- src/app/solutions/page.jsx | 28 +- src/app/solutions/paycode/page.jsx | 211 +++++++++++++ src/components/Header.jsx | 1 + src/components/PaycodePCIDiagram.jsx | 442 +++++++++++++++++++++++++++ 4 files changed, 674 insertions(+), 8 deletions(-) create mode 100644 src/app/solutions/paycode/page.jsx create mode 100644 src/components/PaycodePCIDiagram.jsx diff --git a/src/app/solutions/page.jsx b/src/app/solutions/page.jsx index 266df81e..cd59d018 100644 --- a/src/app/solutions/page.jsx +++ b/src/app/solutions/page.jsx @@ -34,6 +34,14 @@ const solutions = [ href: "/solutions/delta-chat", logo: "delta_chat", }, + { + category: "Payments / Point of Sale", + company: "Payments", + headline: "PCI-Compliant Peer-to-Peer Payments", + description: "Connect payment terminals directly to point of sale systems with no additional servers and full PCI compliance.", + href: "/solutions/paycode", + logo: null, + }, ] export default function SolutionsPage() { @@ -72,14 +80,18 @@ export default function SolutionsPage() {
{solution.company}
+ )}Payments / Point of Sale
++ Connect payment terminals directly to point of sale systems with iroh. + No additional servers, no cloud dependency, full PCI compliance. +
++ PCI-compliant payment systems require that raw payment data never flows through + anything other than the official compliant software. Traditional architectures solve + this with servers and VPNs—adding cost, complexity, and single points of failure. +
++ iroh takes a different approach. Peer-to-peer connections act as a blind command + and control channel between devices. Raw payment data never leaves the payment + terminal. Only encrypted payloads and commands travel through the iroh channel—the + compliance boundary is maintained by architecture, not by policy. +
++ The iroh channel is transparent to payment data—it only routes encrypted + payloads. Even as connectivity changes, compliance and security boundaries remain intact. +
++ Eliminate broker servers, VPNs, and cloud dependencies. + Devices connect directly, reducing infrastructure cost and points of failure. +
++ All connections are encrypted by default. Card data stays on the + payment terminal—only encrypted commands and results traverse the channel. +
++ Devices on the same local network connect directly without internet. + When connectivity returns, iroh reconnects automatically. +
++ iroh runs on Android, iOS, Windows, Linux, and embedded devices. + Connect any POS device to any terminal regardless of platform. +
++ Direct connections mean no round-trip to a cloud server. Payment + commands execute in milliseconds, not seconds. +
++ No single point of failure. If one connection path goes down, iroh + automatically finds another—direct, relay, or local network. +
+Case Study
++ Paycode used iroh to bring tap-to-pay to highway toll booths running Windows 7 + hardware—connecting Kotlin Android POS devices to .NET 6 terminals with no + additional servers, no new infrastructure, and full PCI compliance. +
++ “iroh was super easy to use… I started hacking and was able to integrate + it into our Kotlin PoS app and have a published .NET NuGet package for our client + to use in that month.” +
++ Get started with iroh in minutes. Connect payment devices directly, + maintain compliance, and eliminate infrastructure complexity. +
+- Connect payment terminals directly to point of sale systems with iroh. + Connect payment terminals directly to point of sale systems over + Bluetooth, LAN, or Wi-Fi with iroh. No additional servers, no cloud dependency, full PCI compliance.
iroh takes a different approach. Peer-to-peer connections act as a blind command - and control channel between devices. Raw payment data never leaves the payment - terminal. Only encrypted payloads and commands travel through the iroh channel—the - compliance boundary is maintained by architecture, not by policy. + and control channel between devices over Bluetooth, LAN, or Wi-Fi. Raw payment + data never leaves the payment terminal. Only encrypted payloads and commands travel + through the iroh channel—the compliance boundary is maintained by architecture, + not by policy.
- Devices on the same local network connect directly without internet. + iroh works over Bluetooth, LAN, and Wi-Fi—devices on the same + local network connect directly without internet. When connectivity returns, iroh reconnects automatically.
Payments / Point of Sale
Connect payment terminals directly to point of sale systems over Bluetooth, LAN, or Wi-Fi with iroh. - No additional servers, no cloud dependency, full PCI compliance. + No additional servers, no cloud dependency.
- PCI-compliant payment systems require that raw payment data never flows through - anything other than the official compliant software. Traditional architectures solve - this with servers and VPNs—adding cost, complexity, and single points of failure. -
-- iroh takes a different approach. Peer-to-peer connections act as a blind command - and control channel between devices over Bluetooth, LAN, or Wi-Fi. Raw payment - data never leaves the payment terminal. Only encrypted payloads and commands travel - through the iroh channel—the compliance boundary is maintained by architecture, - not by policy. -
-- The iroh channel is transparent to payment data—it only routes encrypted - payloads. Even as connectivity changes, compliance and security boundaries remain intact. -
-- All connections are encrypted by default. Card data stays on the - payment terminal—only encrypted commands and results traverse the channel. + All connections are encrypted by default using open standards. Card data stays on the + payment terminal.
- iroh works over Bluetooth, LAN, and Wi-Fi—devices on the same - local network connect directly without internet. + iroh works over Bluetooth, LAN, and Wi-Fi—devices + on the same local network connect directly without internet. When connectivity returns, iroh reconnects automatically.
- iroh runs on Android, iOS, Windows, Linux, and embedded devices. + iroh runs on Android, iOS, Windows, Linux, and embedded devices. Connect any POS device to any terminal regardless of platform.
No single point of failure. If one connection path goes down, iroh - automatically finds another—direct, relay, or local network. + automatically finds another—direct, local network, or fallback over the internet via relays.
+ PCI-compliant payment systems require that raw payment data never flows through + anything other than the official compliant software. Traditional architectures solve + this with servers and VPNs, adding cost, complexity, and single points of failure. +
++ iroh takes a different approach. Peer-to-peer connections act as a blind command + and control channel between devices over Bluetooth, LAN, or Wi-Fi. Raw payment + data never leaves the payment terminal. Only encrypted payloads and commands travel + through the iroh channel. Compliance is maintained by architecture. +
++ The iroh channel is transparent to payment data—it only routes encrypted + payloads. Even as connectivity changes, compliance and security boundaries remain intact. +
+Case Study
- Get started with iroh in minutes. Connect payment devices directly, - maintain compliance, and eliminate infrastructure complexity. + Get started with iroh in minutes. Connect devices, + maintain compliance, and reduce complexity.
Case Study
-Paycode used iroh to bring tap-to-pay to highway toll booths running Windows 7 - hardware—connecting Kotlin Android POS devices to .NET 6 terminals with no - additional servers, no new infrastructure, and full PCI compliance. + hardware. They connected Kotlin Android POS devices to .NET 6 terminals with no + additional servers.
From 7edea73dc002b3cf5489c1a99ac2af1f5237905c Mon Sep 17 00:00:00 2001 From: Rae McKelvey <633012+okdistribute@users.noreply.github.com> Date: Thu, 26 Mar 2026 17:52:06 -0700 Subject: [PATCH 06/13] add paycode --- public/img/user-logos/paycode.svg | 54 +++++++++++++++++++++++++++++++ src/app/page.jsx | 11 +++++++ src/app/solutions/page.jsx | 7 ++-- src/app/solutions/pos/page.jsx | 10 +++++- src/components/home/LogoCloud.jsx | 1 + 5 files changed, 79 insertions(+), 4 deletions(-) create mode 100644 public/img/user-logos/paycode.svg diff --git a/public/img/user-logos/paycode.svg b/public/img/user-logos/paycode.svg new file mode 100644 index 00000000..086d948a --- /dev/null +++ b/public/img/user-logos/paycode.svg @@ -0,0 +1,54 @@ + + + diff --git a/src/app/page.jsx b/src/app/page.jsx index edd6a6b1..d5ce4f23 100644 --- a/src/app/page.jsx +++ b/src/app/page.jsx @@ -136,6 +136,17 @@ export default function Page() {
Point of Sale Payments
+Connect payment terminals directly to point of sale systems over Bluetooth, LAN, or Wi-Fi with full PCI compliance and no additional servers.
+Case Study
-
Paycode used iroh to bring tap-to-pay to highway toll booths running Windows 7
hardware. They connected Kotlin Android POS devices to .NET 6 terminals with no
diff --git a/src/components/home/LogoCloud.jsx b/src/components/home/LogoCloud.jsx
index 7a10d72e..51f6b737 100644
--- a/src/components/home/LogoCloud.jsx
+++ b/src/components/home/LogoCloud.jsx
@@ -8,6 +8,7 @@ const companies = [
{ name: "spacedrive", ext: "png" },
{ name: "nous", ext: "png" },
{ name: "shaga", ext: "png" },
+ { name: "paycode", ext: "svg" },
{ name: "rave", ext: "png" },
{ name: "delta_chat", ext: "png" },
{ name: "holochain", ext: "svg" },
From c5c76d88ba04b20adf74b287d519579a2c973e87 Mon Sep 17 00:00:00 2001
From: Rae McKelvey <633012+okdistribute@users.noreply.github.com>
Date: Thu, 26 Mar 2026 18:03:45 -0700
Subject: [PATCH 07/13] add demo
---
public/img/pos-demo.mov | Bin 0 -> 5423810 bytes
src/app/solutions/pos/page.jsx | 12 +++++++++++-
2 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644 public/img/pos-demo.mov
diff --git a/public/img/pos-demo.mov b/public/img/pos-demo.mov
new file mode 100644
index 0000000000000000000000000000000000000000..ce38f289bbea4f0e5b439204bbf5f0664c2a3821
GIT binary patch
literal 5423810
zcmeFYbyQW~+CRDp1!?K-4v|(G0hLx7DUnd=6v>T*geV{aqLk7tt<)x@K}xzyx|<#A
zH~D_g9q;*__Z@fK-#vGX`_EZAnR7n#c|K3Bxz=8LZ5RwjY3J$V>gLJH3IoUAJ#&GR
zi^~fzb#!|1%;u8*UkA1^3??-J!-8G@|F7eJn*j2^%oYEO^M4v)!(hykp6*r-VA0Ie
z;V+$}|HSwYG@$oikAKngKk3Dqhrw_R{}NR3v~u+XBT8#WTf0ljKdn)^y1V>0nyvGH
zqjB2WczOU)Mq5XZORUQSSn&_r{<4S3-pS^<6`->^+5FG(Gx+(JoX9g9NB7H-(=$i+
z7td{Mtz2Cl|5^cm$dp~&ZCSN!0TintSaX5Fn65iLcfK@|@`cl1z*sQFAlT(UaNPR8
zz-$1RmE&`de+HxZComN&Pb=2@R?aq#wwKB|ZT`k&v~mACD1dh92GJ$P-($vP56>r;
zhJE$$^soW_<#EaL-s*+5$X~O+=l>Xje8R9na6#DbgW+YnJg~0Zzac6q{`cg6{7VZ#
zfX)q2m9g%?SfB+MDG%ri755}j!w=$EV_C6axV*n)g8&z~wTq*>v$dl&>>7+5w7(AG
zmmZ#fr3cKgiZB0wM)i-L67-j*{qr2>U*`Y1{(n0Eck%vR`G2+d-^KfP<^N;P|6XtZ
z8jpXS|GV-2cjf HbsnugYEIayQW{^Kq1C9b&$1ocxRGRo5
z-$`rOmg!eve>Su3AR~>xsnVB?l@pTEiPZ}HQ=py`=KS4)f~tBRCV!DWLhw{X3f)k-
z0<+D@#*g54U;m97_F?_08o{X!C$&~L+ Zar(whm7Q(AZ)CxggSCK{ooCA?2_^
z2Zr0Pz~i!%@w$-$M&Hl>VF~{~^*`i=v0^@+onW266aT)&&d1wbUZi2Cm)7dy(uw(?
z0NbNXaPW=DIXEuW8l=QAsx)dOKQT0Wo=6A<5lylVRz|G8(b>r6JzlL;=GptFMiv<7C={X2idsEOzU>-0*GI~
zy3!7*x#7pL@k+w`%df0&k!s8U%dYz8dg4s{*^Urjd4@@K$;5+DI8)#&b9X&&DPR3V
zr@}`o@j7)U;@MRu7cYE-PJXhv9~PrE#h`@J+bxv8kR<*