Early-stage · Real Lightning verified on regtest · Mainnet disabled · Not yet audited

Your payments, under control.

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.

Scattered payment records resolving into one ordered receipt On the left, six separate places a payout usually leaves traces: a chat message, a spreadsheet row, a wallet app, a screenshot, an invoice and an email thread. Dotted lines carry them through a single gate, and from there to an ordered receipt on the right with five steps: obligation, approved, sent once, settled, and proof that can be checked offline. This is an illustration, not a real receipt. chat message sheet, row 14 wallet app screenshot.png invoice email thread RECEIPT illustration Obligation exact amount Approved signed by people Sent once never twice Settled wallet’s record Proof preimage, offline verify it offline
Illustration: the scattered places a payout leaves traces, resolving into one ordered receipt. Not a real receipt.

Paying people in Bitcoin leaves a trail in too many places.

Teams that pay contractors, contributors or grant recipients over Lightning often keep each piece somewhere different.

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.

A lost answer

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.

Weak proof

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.

One careful path from “we owe them” to “here is the proof”.

  1. Step 1

    Obligation

    Record who is owed what: the exact amount and a Lightning invoice that is decoded, checked and bound to the payout.

  2. Step 2

    Approval

    The right people approve the exact payout, each signing with a key held on their own device.

  3. Step 3

    Execution

    An approved payout is reserved once, then sent through a wallet you control.

  4. Step 4

    Truthful state

    If an answer is lost, the payout says Unknown, not Failed, and is not sent twice.

  5. Step 5

    Evidence

    A receipt ties the agreement, the approvals and proof of payment together. A separate command-line verifier checks it offline.

  6. Step 6

    Developer platform

    A REST API, a typed TypeScript SDK and signed webhooks, so payouts can live inside your own tools.

Truthful state

When the answer is lost, we say “unknown”. Not “failed”.

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.

See the state timeline

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.

  • SETTLED
  • UNKNOWN
  • DEFINITIVELY_FAILED

Green when proven paid. Indigo when not yet proven either way. Red only when proven not paid.

What Orynt is not.

Clear limits are part of the design.

  • Not a custodian. Orynt does not hold your funds. You connect a wallet you control.
  • Not an exchange, escrow service or lender.
  • Not a trading tool.
  • Not an autonomous AI spender. People approve payouts; software does not decide to spend.

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.

What you can do in the app today.

Beyond a single payout. Each of these exists in the app and the API; the limits per plan are on the pricing page.

Batch CSV payouts

Upload up to 200 rows. A preview flags bad rows without creating anything, and each item still needs its own approval.

Recurring schedules

Weekly or monthly. Each cycle asks for a fresh invoice and never pays by itself.

Reports and CSV

Payout reports and recipient statements. Only real settlements are summed; no fiat values.

Teams and sign-in

Invite teammates, set roles, turn on authenticator-app (TOTP) two-factor sign-in.

API, SDK and webhooks

A typed client and signed webhooks. Plan limits are enforced on the server and surface as 402 errors.

Plans and support

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.

Three ways to start.

Try it yourself

Create an account, connect the practice wallet or a regtest LND node, and send a first payout through approval to a receipt.

Create account

Come back

Already have a workspace? Sign in to your payouts, approvals and receipts.

Sign in

Talk first

Want to walk through your own workflow before touching anything? Ask for a pilot conversation, or ask support a question.

Request a pilot Contact support

Honest status

Early-stage. Read this before anything else on this site.

Verified Checked in this project

  • M0 — Repo baseline, source register, runbook VERIFIED
  • M2 — Monorepo, migrations, Postgres, schema VERIFIED
  • M2 — Regtest network (bitcoind 29.5 + 2×LND v0.20.1, funded channel, least-privilege macaroons) VERIFIED
  • M3 — Auth, tenancy, roles, policy, signed approvals VERIFIED
  • M4 — **Real Lightning adapter** (LND REST) VERIFIED (regtest)
  • M4 — Invoice decode/validation (BOLT11) VERIFIED vs spec
  • M4 — State machine, durable intents, reconciliation, incidents VERIFIED (simulator)
  • M5 — Operations app, real APIs, mobile VERIFIED
  • M6 — Receipts + standalone verifier CLI VERIFIED
  • M7 — Marketing site, trust centre, pricing hypotheses VERIFIED (build, links, claims)
  • M8 — Negative-case suite VERIFIED
  • M8 — Failpoints, load/concurrency VERIFIED (simulator)
  • M8 — Cross-device screenshots, a11y VERIFIED (automated)
  • R2-P3 — Recipients, BOLT11, LNURL-pay / Lightning Address (LUD-06/16) VERIFIED (simulator + regtest LNURL)
  • — VERIFIED COMPLETE (simulator and real regtest)
  • — VERIFIED COMPLETE

Open Not yet verified

  • Mainnet is disabled. Real Lightning payments are verified on Bitcoin regtest only, a test network with no monetary value.
  • One wallet type. NWC, BTCPay and Core Lightning adapters are not built. Lightning Address payments are verified on regtest against a local test server only.
  • No human audit. One AI-assisted independent code review was done and its findings fixed; no penetration test, human security audit, SOC 2 or other certification exists.
  • Billing is a sandbox. Live Stripe and Paystack checkout is written but not commissioned; no card has ever been charged.
  • Nothing is deployed publicly, and there are no customers, revenue, testimonials or usage numbers.
  • Pricing, willingness to pay and market size are unvalidated hypotheses. The name “Orynt” has unresolved trademark risk and no domain is owned.

Source of truth: docs/EXECUTION-REGISTER.md, read when this site was built. More detail on the security and status page.

Try it on regtest, or tell us about your payouts.

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.