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

@hwsdev/yupay

v1.0.3

Published

Official Node.js SDK for the Yupay merchant API (charges, refunds, balance, webhooks).

Readme

Yupay Node.js SDK

Official Node.js client for the Yupay merchant API. Zero dependencies (global fetch + crypto), Node 18+. Ships TypeScript types.

Website & docs: yupay.id · Dashboard · API reference

Install

npm install @hwsdev/yupay

Quickstart

const { Yupay, YupayError } = require('@hwsdev/yupay');

const yupay = new Yupay(process.env.YUPAY_API_KEY, {
  baseUrl: 'https://yupay.id/api/v1', // your Yupay instance
});

try {
  const charge = await yupay.createCharge(
    { amount: 50000, method: 'qris' },
    { idempotencyKey: 'order-1001' },
  );

  console.log(charge.payment_no, charge.status); // PAY-260626-AB12CD pending
  console.log(charge.artifact);                  // qr_string / va_number / redirect_url …
} catch (err) {
  if (err instanceof YupayError) {
    console.error(err.message, err.statusCode, err.validationErrors);
  }
}

ESM works too: import { Yupay, webhooks } from '@hwsdev/yupay';

Methods

yupay.createCharge(params, { idempotencyKey? }): Promise<Payment>;
yupay.retrieveCharge(paymentNo): Promise<Payment>;
yupay.refundCharge(paymentNo, { amount?, reason? }): Promise<RefundResult>;
yupay.balance(): Promise<Balance>;
yupay.paymentChannels({ category?, all? }): Promise<ChannelList>;

All reject with YupayError (.statusCode, .response, .validationErrors) on failure.

Webhooks (Express)

You must verify the signature against the raw body, so register the route with express.raw (not express.json):

const express = require('express');
const { webhooks } = require('@hwsdev/yupay');

const app = express();
const secret = process.env.YUPAY_WEBHOOK_SECRET;

app.post('/yupay/webhook', express.raw({ type: 'application/json' }), (req, res) => {
  let event;
  try {
    event = webhooks.constructEvent(req.body, req.get('X-Yupay-Signature'), secret);
  } catch {
    return res.status(400).send('invalid signature');
  }

  // Dedupe on event.id (Yupay delivers at least once), then handle:
  if (event.event === 'payment.succeeded') {
    const p = event.data;
    // fulfillOrder(p.payment_no, p.amount) — offload heavy work to a queue
  }

  res.status(200).send('ok'); // ack fast
});

app.listen(3000);

Test your handler without real payments: in the dashboard (Developer → Webhooks) use Kirim test or Simulasi to send a signed event to this endpoint, then check the delivery log — it shows your endpoint's response body, so a failed constructEvent() (HTTP 400) is easy to spot. See webhooks docs.

See examples/ for runnable scripts.

Links