- Create a payout with payments, or with recipients identified by handle, email, wallet, or social account.
- Finalize it with your organization’s signer — this locks recipients, amounts, and schedule cryptographically.
- Fund it through the generated funding link, from whatever wallet your treasury controls.
- Track it through webhooks and payout records.
Environments
Pvium runs three fully isolated environments. Accounts, organizations, API keys, and payouts do not carry across environments.
The SDKs select the environment for you:
Rails and currencies
payoutCurrency is optional. If you leave it unset, the payout uses the chain’s default currency. You can also set a specific token per payment instead of a payout-wide currency.
Organizations
Every API integration acts as an organization — the workspace your payouts, records, and payees live in. (Organizations are called client apps in some older API paths.) You create one from the dashboard with Create Organization: give it a name, link it to your business profile, and optionally add a description, website, and logo. Each organization gets:- A client ID that identifies it in API calls and OAuth flows
- Its own API keys, scoped to that organization
- Its own webhook configuration and signing secret
- Its own payouts, records, tax forms, and connected payees
Organizations concept
What organizations scope, and how they relate to business profiles.
Next steps
Send your first payout
Create, finalize, and fund a payout with the Node SDK.
Authentication
API keys, OAuth access tokens, and signer keys.
Create a payout
Payout types, chains, currencies, payments, and recipients.
Finalize a payout
Sign a payout and generate its funding link.

