It's based on lightning addresses, but should be any reason it couldn't be modified to look up the lightning addresses using the npubs.
It does require a wallet the can receive webhooks to work. The basic idea is you have a list of splits stored on the server or in a file somewhere. Someone pays your wallet, you get a verification that the payment was completed via the webhook, so now you have the funds in your wallet, Then you look up the splits and send a payment to each of those wallets, which is a percentage of the original payment.
I've got it tied into a websocket, so it's dynamic. The lookup stuff is in the comments of the invoice, when it's paid, the server can look at that comment, then connect to the websocket to get the current splits, then send those out. The QR stays static because it's the parent wallet, but the webhook wallet can look up the dynamic splits.
It is a single point of failure. If the first wallet goes down, the whole chain breaks.
StevenB
npub1yv…d6pv9
2025-04-09 00:22:48
in reply to nevent1q…jpgc
Author Public Key
npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9Seen on
wss://relay.nostr.bandPublished at
2025-04-09 00:22:48Event JSON
{
"id": "7bed9791e1a828a9d2c9ea67096562e2a2c1422312637c66f2b7f658e7a9bf1a",
"pubkey": "23103189356cf7c8bc09bb8b431fc3e71e85582c8f755b9ee160203c9c19e403",
"created_at": 1744158168,
"kind": 1,
"tags": [
[
"p",
"d70d50091504b992d1838822af245d5f6b3a16b82d917acb7924cef61ed4acee"
],
[
"p",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975"
],
[
"p",
"23103189356cf7c8bc09bb8b431fc3e71e85582c8f755b9ee160203c9c19e403"
],
[
"p",
"426f11348ff0e3eda2d5b906f9cb7d9743075ab85ebb3c15d57fb80b4e25ec3e"
],
[
"p",
"f7922a0adb3fa4dda5eecaa62f6f7ee6159f7f55e08036686c68e08382c34788"
],
[
"e",
"841793a4f00bec851aa387e8610243d7b6686f55f95a98837f498530ea56dac1",
"",
"root"
],
[
"e",
"d5dc994f06c5bd94216c2c658f6b552f039940616ce0b025fb461823f9118aa7",
"",
"reply",
"d70d50091504b992d1838822af245d5f6b3a16b82d917acb7924cef61ed4acee"
]
],
"content": "It's based on lightning addresses, but should be any reason it couldn't be modified to look up the lightning addresses using the npubs.\n\nIt does require a wallet the can receive webhooks to work. The basic idea is you have a list of splits stored on the server or in a file somewhere. Someone pays your wallet, you get a verification that the payment was completed via the webhook, so now you have the funds in your wallet, Then you look up the splits and send a payment to each of those wallets, which is a percentage of the original payment. \n\nI've got it tied into a websocket, so it's dynamic. The lookup stuff is in the comments of the invoice, when it's paid, the server can look at that comment, then connect to the websocket to get the current splits, then send those out. The QR stays static because it's the parent wallet, but the webhook wallet can look up the dynamic splits.\n\nIt is a single point of failure. If the first wallet goes down, the whole chain breaks.",
"sig": "800c4e866c72c0a62e6e90e1c75c28fe0ee2d9daf92a795c39a1f52024b25775ddde23fc892b52e1b35b4452361cbeef5660f1fac78f6765ed831234d68216f0"
}