Step 1 of 5
Obligation Verified · real regtest
Write down the payout before anything moves.
A payout is a record: payee, exact amount in whole millisatoshis, memo, your own reference, and a Lightning invoice that Orynt decodes and checks (signature, network, amount, expiry, payee node key). Edits never overwrite: each is a new immutable revision. Batches (a CSV of up to 200 rows) and recurring schedules do not bypass this step; they only create ordinary payouts.
Features
- Payee records, optionally bound to a node key
- Lightning Address resolved to a checked invoice
- Invoice decoding and binding
- Immutable revisions
- Plan limits checked on the server when a payout is created
- Batch CSV import with per-row validation
- Recurring schedules (each cycle asks for a fresh invoice)
API surface
POST /v1/obligationsPUT /v1/obligations/:idPOST /v1/lnurl/resolvePOST /v1/batchesPOST /v1/schedules
Step 2 of 5
Authorization Verified · simulator + tests
The right people approve the exact payout, with signatures.
Submitting freezes a revision and binds the active policy. Each approver signs the intent digest, a fingerprint of the exact payout, with an Ed25519 key kept in their browser. Changing the payout or the policy voids earlier approvals. Roles are checked at approval and again at execution; API keys can never approve.
Features
- Policy revisions (approvals needed, maker-checker, thresholds)
- Ed25519 signed approvals
- Role and permission checks
- TOTP two-factor step-up (sign-in, approve, execute)
- Team invitations
API surface
POST /v1/obligations/:id/submitPOST /v1/obligations/:id/approvePOST /v1/policiesPOST /v1/me/approval-key
Step 3 of 5
Execution Verified · real regtest
An approved payout is sent exactly once.
Before the wallet is called, a single-use execution record is reserved. A second send is refused while the first is unresolved, and the request needs an Idempotency-Key. Mainnet execution is switched off.
Features
- Single-use execution reservation
- Idempotency keys
- Wallet capability check
- Mainnet disabled
API surface
POST /v1/obligations/:id/executePOST /v1/batches/:id/execute
Step 4 of 5
Reconciliation Verified · real regtest
When the answer is lost, ask the wallet. Do not guess.
If the wallet does not answer, the payout becomes UNKNOWN, then RECONCILING. Orynt asks the wallet for its own record by payment hash. Only that record moves the payout to SETTLED or DEFINITIVELY_FAILED; an expired invoice alone proves nothing. Unresolved cases open an incident with notes and an owner, and a person can attest, with fresh evidence, that nothing was sent.
Features
- UNKNOWN and RECONCILING states
- Lookup by payment hash
- Incident workbench (notes, assignment)
- Attested “confirm not sent”
- Retry only after proven failure
- Startup recovery of stuck payments
API surface
POST /v1/payments/:id/reconcilePOST /v1/payments/:id/confirm-not-sentPOST /v1/payments/:id/retryPOST /v1/incidents/:id/resolve
Step 5 of 5
Evidence Verified · real regtest
Proof anyone can check without trusting us.
A settled payment can produce a signed receipt that binds the agreement, the signed approvals and the wallet's result, including the preimage whose hash is the payment hash. A separate command-line verifier checks it offline. The audit log is hash-chained, and reports can be exported as CSV.
Features
- Signed receipts (orynt.receipt/1)
- Offline verifier CLI
- Hash-chained audit log
- Payout reports and per-recipient statements
- Signed webhooks for your own systems
API surface
GET /v1/payments/:id/receiptGET /v1/audit/verifyGET /v1/reports/payoutsPOST /v1/webhooks