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

@tallypay/server

v0.0.3

Published

Server middleware for x402 payment gating with lifecycle tracing

Readme

@tallypay/server

Express and Hono middleware for HTTP 402 payment gating with optional TallyPay lifecycle tracing. Works with any facilitator that exposes verify/settle-style HTTP endpoints—TallyPay is the observability layer, not the payment rail.

Install

npm install @tallypay/server

Peer dependencies (install the one you use):

  • Expressexpress ≥ 4
  • Honohono ≥ 4

@tallypay/core is pulled in automatically as a dependency.

Express

import express from "express";
import { tallypay } from "@tallypay/server/express";

const app = express();

app.use(
  "/api/premium",
  tallypay({
    apiKey: "tp_live_...", // optional: enables trace collection
    facilitatorUrl: "https://your-facilitator.example",
    payTo: "0xYourMerchantAddress",
    price: "10000", // smallest units — match your facilitator’s expectations
    network: "eip155:8453",
    asset: "USDC",
    description: "Premium API access",
  }),
);

app.get("/api/premium", (_req, res) => {
  res.json({ ok: true });
});

Import path: @tallypay/server/express.

Hono

import { Hono } from "hono";
import { tallypay } from "@tallypay/server/hono";

const app = new Hono();

app.use("/api/premium/*", tallypay({
  apiKey: "tp_live_...",
  facilitatorUrl: "https://your-facilitator.example",
  payTo: "0xYourMerchantAddress",
  price: "10000",
  network: "eip155:8453",
  asset: "USDC",
}));

app.get("/api/premium/data", (c) => c.json({ ok: true }));

Import path: @tallypay/server/hono.

Config (TallyPayConfig)

| Field | Required | Description | |--------|----------|-------------| | facilitatorUrl | yes | Base URL for your facilitator (middleware calls {url}/verify and {url}/settle with the raw payment-signature body). | | payTo | yes | Recipient address (or identifier your facilitator expects). | | price | yes | Amount string (convention depends on facilitator/network). | | network | yes | e.g. eip155:8453. | | asset | yes | e.g. USDC. | | apiKey | no | TallyPay API key; if omitted, payment gating still works—traces are not sent. | | collectorUrl | no | Override for the trace collector URL. | | description | no | Shown in payment requirements. |

Behaviour

  1. No payment-signature header → 402 with payment-required header + JSON body; emits 402_ISSUED when tracing is on.
  2. With signature → POST to facilitator verify, then settle; emits lifecycle events (VERIFY_*, SETTLE_*, PAYMENT_COMPLETE or PAYMENT_ERROR).
  3. Tracing is fire-and-forget: collector failures do not block the response path.

Adjust facilitator request/response shapes if your provider differs—the middleware assumes JSON responses compatible with { valid, reason? } and { settled, txHash? } for verify/settle.

Testing

From the monorepo root (builds @tallypay/core first via Turbo):

pnpm --filter @tallypay/server test

Integration tests use supertest (Express) and Hono’s app.request() with a mocked global fetch for the facilitator.

License

MIT. Source code will be published on GitHub at launch; until then see tallypay.dev.

Links