Integrations

One wallet type works. The rest are not built.

Orynt sits in front of a Lightning wallet you control. Today that means an LND node over REST, verified on Bitcoin regtest. This page says plainly what is and is not supported, so nobody plans around an adapter that does not exist.

  • LND · verified on regtest
  • Lightning Address · regtest
  • NWC · BTCPay · Core Lightning
  • Mainnet disabled

Wallet capability matrix.

Verified means a command was run against real software and the result recorded in docs/EXECUTION-REGISTER.md: 15 real-node tests plus an end-to-end demo against bitcoind and two LND nodes on regtest.

Wallet adapters and what each one supports. A dash means the capability does not exist because the adapter is not built.
WalletStatusPay an invoiceLook up a paymentCapability discoveryRead-only credentialMainnet
LND (REST)Verified · regtestYesYes, by payment hashDiscovered by authorization probesRejected, with the reason shownRefused (mainnet is disabled)
Practice wallet (simulator)Built · labelledSimulatedSimulatedSimulatedSimulatedNot applicable
Nostr Wallet Connect (NWC)Planned · not implemented—————
BTCPay ServerPlanned · not implemented—————
Core LightningPlanned · not implemented—————
LNURL-pay and Lightning AddressVerified · regtest, local LNURL serverResolved to a checked BOLT11 invoice, then paid through LNDAs LNDAs LNDAs LNDRefused (mainnet is disabled)

“Planned” means we expect to look at it, not that it has a date. None of the planned adapters has code that can pay anything. Names of other products belong to their owners; listing them implies no partnership or endorsement.

Connecting LND.

An operator connects an LND node over its REST interface with a macaroon. Orynt does not assume what the credential allows: it probes the permissions and records what it found. A credential that can only read cannot be used to send, and a connection that reports an unexpected network is refused.

Give Orynt the narrowest credential that works: one that can pay invoices and look up payments (LND's offchain read and write), never your admin macaroon. The credential is stored encrypted on the server.

What the real-node tests cover

  • The invoice decoder agrees with LND's own decoding
  • A real payment, and a duplicate refused by the wallet
  • A lost response, then reconciliation: one payment only
  • Insufficient liquidity, expired invoice, payee node offline then retry
  • Read-only credential blocked; destination and network substitution rejected
  • 10 concurrent executes produce 1 payment
  • Restart of our node in the middle of an uncertain payment

Not covered: mainnet, other LND versions than the one tested, other node implementations, and channel-management behaviour. First-use guide (public): /app/guide.

What payees need to provide.

Every payout is paid from a BOLT11 invoice. A Lightning invoice is single-use and expires, so a payee normally supplies a fresh one for each payout. Recurring schedules are built around this: each cycle opens a task that asks for a new invoice, and never pays by itself.

A payee can instead give a Lightning Address (name@domain, LUD-16). Orynt asks that server for an invoice for the exact amount and treats the answer as untrusted: it checks the amount, network, expiry and that the invoice commits to the advertised description before it can reach approval. The node key that signed the invoice is shown to the approver, because a name or domain alone is never proof of destination.

How far that is verified.

Against a local LNURL test server on regtest. It has not been run against real third-party Lightning Address providers. Keysend (spontaneous payments) is not supported, and the wallet-side fee limit is passed through but not separately asserted.

Everything else Orynt connects to.

Other integration points and their status
IntegrationStatusWhat existsRead more
REST API and OpenAPIBuiltJSON over HTTPS under /v1. The OpenAPI document is served at /v1/openapi.json.Developers
TypeScript SDKBuilt · not on npmA typed client in the repository; it is not published to a package registry.Quickstart
Outbound webhooksVerified · testsSigned with HMAC-SHA256, timestamped, at-least-once, de-duplicated by event id.Webhooks
Billing provider: sandboxVerifiedSimulates checkout through the real signed-webhook path. No card is charged.Billing FAQ
Billing providers: Stripe, PaystackImplemented · not commissionedCheckout and signature-verified webhooks are written but have never run against a live provider account. No real charge has ever happened.Billing FAQ
Email deliveryImplemented · not commissionedBy default mail is written to an outbox and marked sent without being delivered. A Resend adapter exists but has never been exercised with a real key and a verified sending domain.Account help
CSV import and exportBuiltBatch payouts in from CSV (up to 200 rows) and payout reports out as CSV. No accounting-package connectors.Solutions

Need a different wallet?

Tell us which one and why. Demand is how we decide what to build next, and we will say plainly if we cannot verify it.