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

@paykit-sdk/chapa

v1.0.2

Published

Chapa provider for PayKit

Readme

@paykit-sdk/chapa

Chapa provider for PayKit.

Installation

npm install @paykit-sdk/chapa
# or
pnpm add @paykit-sdk/chapa

Quick Start

import { chapa } from '@paykit-sdk/chapa';
import { createEndpointHandlers, PayKit } from '@paykit-sdk/core';

export const paykit = new PayKit(chapa());
export const endpoints = createEndpointHandlers(paykit);

Or with direct config:

import { createChapa } from '@paykit-sdk/chapa';
import { PayKit } from '@paykit-sdk/core';

export const paykit = new PayKit(
  createChapa({
    secretKey: 'CHASECK_TEST-...',
    isSandbox: true,
  }),
);

Environment Variables

CHAPA_SECRET_KEY=CHASECK_TEST-...

isSandbox is inferred from NODE_ENV — set NODE_ENV=production for live mode. Whether requests actually hit test or live data is determined by whether CHAPA_SECRET_KEY is a CHASECK_TEST- or CHASECK- key, not by isSandbox itself.

Next.js API Route

// app/api/paykit/[...endpoint]/route.ts
import { endpoints } from '@/lib/paykit';
import { EndpointPath } from '@paykit-sdk/core';
import { NextRequest, NextResponse } from 'next/server';

export async function POST(
  request: NextRequest,
  { params }: { params: Promise<{ endpoint: string[] }> },
) {
  const { endpoint: endpointArray } = await params;
  const endpoint = ('/' + endpointArray.join('/')) as EndpointPath;
  const handler = endpoints[endpoint];

  if (!handler) {
    return NextResponse.json(
      { message: 'Not found' },
      { status: 404 },
    );
  }

  const { args } = await request.json();
  const result = await handler(...args);
  return NextResponse.json({ result });
}

Webhooks

Chapa sends signed POST requests, using your secret key as the webhook secret — there is no separate webhook signing secret to configure.

// app/api/paykit/webhooks/route.ts
import { paykit } from '@/lib/paykit';
import { NextRequest, NextResponse } from 'next/server';

export async function POST(request: NextRequest) {
  const body = await request.text();

  const webhook = paykit.webhooks
    .setup({ webhookSecret: process.env.CHAPA_SECRET_KEY! })
    .on('payment.updated', async event => {
      /* charge.success */
    })
    .on('payment.failed', async event => {
      /* charge.failed/cancelled */
    })
    .on('invoice.generated', async event => {
      /* charge.success */
    });

  await webhook.handle({
    body,
    headersAsObject: Object.fromEntries(request.headers),
    fullUrl: request.url,
  });

  return NextResponse.json({ received: true });
}

Checkout

Chapa requires an email customer and amount/currency in provider_metadata:

const checkout = await paykit.checkouts.create({
  customer: { email: '[email protected]' },
  item_id: 'plan_pro',
  session_type: 'one_time',
  quantity: 1,
  success_url: 'https://example.com/success',
  cancel_url: 'https://example.com/cancel',
  provider_metadata: {
    amount: '400',
    currency: 'ETB',
  },
});

// Redirect user to checkout.payment_url

Refunds

Refunds are always sent with an explicit amount — pass the full transaction amount for a full refund.

const refund = await paykit.refunds.create({
  payment_id: 'tx_ref_from_the_original_transaction',
  amount: 400,
  reason: 'requested_by_customer',
  metadata: null,
});

Unsupported

Chapa has no customer management API and no subscription/plan API — createCustomer, createSubscription, and related methods throw ProviderNotSupportedError. Customer details are captured inline with each transaction instead.

Documentation

Full docs at docs.usepaykit.com/providers/chapa.

Support

License

ISC