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

@apiosk/checkout-core

v0.1.0

Published

Shared checkout schema, rails, intent payload helpers, and webhook utilities for Apiosk checkout packages

Downloads

96

Readme

@apiosk/checkout-core

Shared checkout contract for all Apiosk checkout surfaces.

This package owns the schema and helper layer that the other checkout modules should agree on:

  • rail metadata
  • normalized checkout config
  • checkout intent payload shape
  • checkout status path helpers
  • webhook event names
  • webhook signature helpers

Install

After publish:

npm install @apiosk/checkout-core

Before publish:

npm install ./subs/checkout-core

What belongs here

checkout-core is not a UI package. It should stay framework-neutral and avoid React, Vue, DOM, and CSS concerns.

Use it when you need to:

  • build a merchant checkout intent payload
  • normalize rail configuration before rendering a button
  • keep webhook naming and signature handling consistent
  • share the same checkout schema between web, React, Vue, and server code

Quick start

import {
  createCheckoutIntentPayload,
  normalizeCheckoutConfig,
  selectDefaultRail,
} from "@apiosk/checkout-core";

const config = normalizeCheckoutConfig({
  merchantName: "Northstar Marketplace",
  productName: "Automation bundle",
  amountLabel: "24.95 EUR",
  orderReference: "ord_2048",
  rails: [
    { id: "credits", status: "live" },
    { id: "x402", status: "live" },
    { id: "agent", status: "pilot" },
  ],
  callbacks: {
    successUrl: "https://merchant.example/success",
    cancelUrl: "https://merchant.example/cancel",
    webhookUrl: "https://merchant.example/webhooks/apiosk",
    statusUrl: "https://merchant.example/api/orders/ord_2048",
  },
});

const payload = createCheckoutIntentPayload(config);
const defaultRail = selectDefaultRail(config.rails);

Normalized config

The normalizer accepts both:

  • a flat button-friendly shape like merchantName, productName, amountLabel
  • a structured config with merchant, order, appearance, and callbacks

That lets internal dashboard code migrate incrementally while external SDKs use the structured version from day one.

Intent contract

createCheckoutIntentPayload() produces the payload shape that the future checkout API should accept at:

  • POST /v1/checkout/intents
  • GET /v1/checkout/intents/:id

This package is where that contract should evolve first.

Webhook helpers

Use createWebhookSignature() and verifyWebhookSignature() for server-side signature handling:

import { verifyWebhookSignature } from "@apiosk/checkout-core";

const rawBody = '{"event":"checkout.intent.paid"}';
const signature = request.headers["x-apiosk-signature"];

const isValid = await verifyWebhookSignature(
  rawBody,
  signature,
  process.env.APIOSK_WEBHOOK_SECRET,
);

Pass the raw request body string whenever possible.