Target use case No customers
Developer payouts
- Who it might suit
- A product team or open-source maintainer that pays people from code: bounties, bug rewards, creator or referral rewards, sent over Lightning when something happens in their own system.
- Workflow
- Create from codeThe backend calls
POST /v1/obligations(orobligations.createin the SDK) with an API key. The payee, exact amount and invoice are recorded and the invoice is checked. - Humans approveThe payout waits for the policy's signed approvals. API keys cannot approve, so software cannot release its own spending.
- Execute onceThe backend calls execute with an
Idempotency-Key. A202means “not certain yet”: it waits or reconciles and never sends again. - Close the loopA signed
payment.settledwebhook updates your own records, and the receipt can be attached to the reward.
- Create from codeThe backend calls
- Plan fit
- The free Developer plan allows 25 payouts a month, 2 API keys and 1 webhook endpoint.
- What we don’t know
- Lightning invoices are single-use, so a payee supplies a fresh invoice for every payout, or a Lightning Address that Orynt resolves into a checked invoice. Whether that friction is acceptable for rewards is something we have not tested.