Installation

Install revenue-sdk with npm, pnpm, yarn, or bun, check the runtime requirements, and learn the ESM subpath exports for each provider.

Install revenue-sdk from npm with your package manager of choice.

npm install revenue-sdk

pnpm add revenue-sdk

yarn add revenue-sdk

bun add revenue-sdk

Requirements

revenue-sdk ships as ESM only and depends on nothing but the platform’s fetch, Web Crypto, TextEncoder, URL, and btoa/atob — all Web standards.

There are no node:* imports anywhere in the package, so it drops into edge runtimes unchanged.

Subpath exports

The client lives at the package root; each provider factory lives on its own subpath so a bundler only pulls in the provider you actually import. Every provider subpath also exports that provider’s standalone webhook helpers.

Import the client and a provider

import { createClient } from 'revenue-sdk';
import { stripe } from 'revenue-sdk/stripe';

const client = createClient({
  provider: stripe({ secretKey: process.env.STRIPE_SECRET_KEY! }),
});

The webhook helpers are imported separately and never need a client:

import { parseWebhookEvent, verifyWebhook } from 'revenue-sdk/stripe';