What is Jorvi
In self-custody there is no card on file. The payer holds their own keys, so a merchant cannot simply pull funds the way a card processor does. That is the gap Jorvi closes, without ever taking custody.
A payer signs one authorization that sets a cap and the exact terms of what may be charged. The merchant then charges against that authorization. Funds settle on-chain, payer to merchant, in a single hop. The cap is enforced by the chain, not by Jorvi’s backend.
What Jorvi provides
Section titled “What Jorvi provides”Three products on one rail. The status against each is the same one shown on the home page, because a list of names with no status reads as a shipped lineup.
Jorvi Pay · In progress A self-custodial payment app for retail users. Connect a wallet, hold USDC, pay a merchant by scanning a code.
Jorvi Gateway · In progress A merchant gateway. Mandates, charges, refunds, payment links, and signed webhooks. Settlement lands in the merchant’s own wallet.
Jorvi SDK · Not yet published
TypeScript packages: @jorvi/sdk for your server, @jorvi/checkout for the browser, plus types, webhook verification, and the Solana adapter.
What is working today, and what is not, is set out in Where the project is below.
What Jorvi is not
Section titled “What Jorvi is not”- Not an exchange. We do not facilitate trading.
- Not a custodian. We never take custody of funds.
- Not an on-ramp or off-ramp. Fiat conversion is handled by licensed third parties.
- Not a bank or a financial institution.
Where the project is
Section titled “Where the project is”Jorvi is pre-launch. The engine, refunds, multi-tenancy, signed webhooks, hosted checkout and the TypeScript packages are built and tested. Settlement currently runs against a simulated client; the live on-chain client is the next milestone.
Pages describing anything not yet built are marked. Where this documentation uses the present tense, the feature exists today.
- Quickstart: accept a payment
- How settlement works: where the money actually goes