Skip to main content
Pvium ships three official SDKs from the pvium/sdks monorepo. All three expose the same service surface — payouts, invites, OAuth, and webhook helpers — and share cross-SDK parity fixtures, so payout hashing, signing, and Merkle behavior are identical regardless of language.

Initialize

Create and finalize a payout

The same flow in each SDK: create the payout, finalize it with your organization’s signer, and get the funding link.

Language notes

  • TypeScript — written in TypeScript with full type definitions; the primary SDK and the one this documentation’s examples default to.
  • Python — the PyPI package is pvium, the import is pvium_sdk. AsyncPviumSdk mirrors the same surface for async codebases.
  • Go — services hang off the SDK struct (sdk.Payouts, sdk.Invites, sdk.OAuth, sdk.Endpoints) and every call takes a context.Context.
Payouts with more than 200 payees should be created as Scheduled rather than Instant — use createFinalized to create and finalize them in one call.

What every SDK covers

  • Payouts — create, list, and get payouts; manage payments and identity-based recipients; finalize with your signer and get funding links; authorize delegated signing keys.
  • Invites — payout invites and organization open invites, including the cryptographic invite proofs.
  • OAuth — token exchange and refresh for acting on a user’s granted scopes.
  • Webhook helpers — verify webhook deliveries before trusting them.
  • Signing utilities — private-key signers plus lower-level hashing helpers for custom signer setups.

Where to start

Send your first payout

The full create → finalize → fund → track loop.

Authentication

API keys, OAuth tokens, and signer keys.