Scattered records
The amount is in a spreadsheet, the “ok” is in a chat, the payment is in a wallet app, and the proof is a screenshot. Answering “who approved this, and was it paid?” becomes detective work.
Early-stage · Real Lightning verified on regtest · Mainnet disabled · Not yet audited
Orynt sits in front of a Lightning wallet you already control. It records what you owe, gets the right people to approve it, sends each payment once, and keeps proof you can check without trusting us.
Free Developer plan. Practice wallet or your own regtest node. No card is charged. See how it works.
Every payment. Under control.
Teams that pay contractors, contributors or grant recipients over Lightning often keep each piece somewhere different.
The amount is in a spreadsheet, the “ok” is in a chat, the payment is in a wallet app, and the proof is a screenshot. Answering “who approved this, and was it paid?” becomes detective work.
When a wallet’s reply is lost mid-payment, nobody can tell whether the money moved. People either retry and risk paying twice, or wait and leave someone unpaid.
A screenshot shows what someone saw, not what was agreed or who authorised it. Accountants, funders and payees often ask for more.
These are the problems the product is designed around. We have not yet measured how often they occur for real teams; that is one of the things we want to learn.
Record who is owed what: the exact amount and a Lightning invoice that is decoded, checked and bound to the payout.
The right people approve the exact payout, each signing with a key held on their own device.
An approved payout is reserved once, then sent through a wallet you control.
If an answer is lost, the payout says Unknown, not Failed, and is not sent twice.
A receipt ties the agreement, the approvals and proof of payment together. A separate command-line verifier checks it offline.
A REST API, a typed TypeScript SDK and signed webhooks, so payouts can live inside your own tools.
Truthful state
A payout only becomes failed when the wallet’s own record proves it. Until then, sending again is refused, because the first attempt may still have gone through.
Unknown is indigo, on purpose.
It is a situation to work through, not an error to panic about. Orynt asks the wallet what happened and shows what is known and what is not.
Green when proven paid. Indigo when not yet proven either way. Red only when proven not paid.
Clear limits are part of the design.
Honest limit.
Approval and limit checks are enforced by the Orynt application, not by the wallet. Protection of funds is only as strong as the permissions you give Orynt in your wallet. See security.
Beyond a single payout. Each of these exists in the app and the API; the limits per plan are on the pricing page.
Upload up to 200 rows. A preview flags bad rows without creating anything, and each item still needs its own approval.
Weekly or monthly. Each cycle asks for a fresh invoice and never pays by itself.
Payout reports and recipient statements. Only real settlements are summed; no fiat values.
Invite teammates, set roles, turn on authenticator-app (TOTP) two-factor sign-in.
A typed client and signed webhooks. Plan limits are enforced on the server and surface as 402 errors.
Plans with real limits, billed through a sandbox provider for now. Support requests with safe diagnostics attached.
Single payouts are verified against real LND nodes on regtest. Batches, schedules, reports, accounts and billing are verified with the practice wallet and automated tests, not on real nodes. Support requests and analytics are implemented, with less testing.
Create an account, connect the practice wallet or a regtest LND node, and send a first payout through approval to a receipt.
Already have a workspace? Sign in to your payouts, approvals and receipts.
Want to walk through your own workflow before touching anything? Ask for a pilot conversation, or ask support a question.
Early-stage. Read this before anything else on this site.
Source of truth: docs/EXECUTION-REGISTER.md, read when this site was built. More detail on the security and status page.
Create a free account and use the practice wallet or your own regtest node, or ask for a pilot conversation. No sales pressure, no card charged, no real funds at risk.