npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@arki/payments

v0.3.2

Published

Payments for ARKI apps — Stripe provider, plans, customers, subscriptions, payments, refunds, dunning and tax, as Drizzle table factories, repositories, services and @arki/journal commands.

Readme

@arki/payments

Payments for ARKI apps: a Stripe provider, plans, customers, subscriptions, payments, refunds, dunning and tax. It ships Drizzle table factories, repositories, services and @arki/journal commands. Routers stay in each consuming app, so the app owns its RPC context and its authorization policy.

Installation

npm install @arki/payments
# or
bun add @arki/payments

Subpath exports

| Subpath | Contents | | ----------------------------- | ---------------------------------------------------------------------------- | | @arki/payments | Provider abstraction (BasePaymentProvider, StripeProvider), shared types | | @arki/payments/core | Plans, customers, subscriptions, payments, webhook events, UserId | | @arki/payments/presets | Ready-made subscription and RevenueCat flows | | @arki/payments/env | Typed environment schema for the Stripe keys and notification settings | | @arki/payments/dunning | Dunning campaigns and retry services | | @arki/payments/tax | Stripe Tax integration | | @arki/payments/refunds | Refund request and approval workflow | | @arki/payments/repositories | Aggregate repository factory |

Deeper paths such as @arki/payments/core/tables resolve to the compiled file of the same name.

User ids

Every owner column is a UserId, the string type `usr_${string}` exported from @arki/payments/core, with userIdSchema to validate one and userIdFactory to build foreign-key columns. It has the same shape as the user id of @arki/auth, so an app built on that package passes its ids through unchanged. An app with its own user table only needs ids of that shape.

Consuming app integration

Every consuming app must:

  1. Call the table factories with its own pgSchema and a reference to its user id column (see createCoreTables in @arki/payments/core/tables).
  2. Register the resulting Drizzle relations in its relations.ts.
  3. Build its own RPC router from the package's services and the app's protected and public procedures.
  4. Inject env-driven config (STRIPE_SECRET_KEY, notification settings) at app boot, not per request.

License

MIT — see LICENSE.