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

@ng-pay/core

v0.1.6

Published

Core types, HTTP client, and error handling for the ng-pay unified Nigerian fintech SDK

Readme

@ng-pay/core

Core types, HTTP client, and error classes for the ng-pay unified Nigerian fintech SDK.

This package is a peer dependency of all ng-pay adapters. You don't use it directly unless you're building a custom provider.

Installation

npm install @ng-pay/core

What's in here

Money utilities

All monetary amounts in ng-pay are in the smallest currency unit (kobo for NGN). Never use floats for money.

import { toKobo, fromKobo, formatMoney } from '@ng-pay/core';

toKobo(5000)                                    // → 500000
fromKobo(500000)                                // → 5000
formatMoney({ amount: 500000, currency: 'NGN' }) // → "₦5,000.00"

Validation utilities

import { isValidNUBAN, isValidBankCode, generateReference } from '@ng-pay/core';

isValidNUBAN('0123456789')   // → true  (10-digit CBN account number)
isValidBankCode('058')       // → true  (3-digit CBN bank code)
generateReference('pstk')    // → "pstk_1712345678_a3f9b2c1"

Error handling

Every error thrown by an ng-pay adapter extends NgPayError:

import { isNgPayError, isRateLimitError, NgPayError } from '@ng-pay/core';

try {
  await provider.initializePayment({ ... });
} catch (err) {
  if (isRateLimitError(err)) {
    console.log(`Retry after ${err.retryAfter}s`);
  } else if (isNgPayError(err)) {
    console.error({
      provider: err.provider,  // 'paystack' | 'flutterwave' | 'monnify'
      code: err.code,          // 'INVALID_PARAMS' | 'RATE_LIMITED' | ...
      message: err.message,
      raw: err.raw,            // original provider response
    });
  }
}

Error codes

| Code | Meaning | |---|---| | INVALID_API_KEY | Secret key is wrong or expired | | INVALID_PARAMS | Bad request parameters | | DUPLICATE_REFERENCE | Payment reference already used | | PAYMENT_NOT_FOUND | Reference doesn't exist | | INSUFFICIENT_BALANCE | Not enough balance for transfer | | ACCOUNT_NOT_FOUND | Account number resolution failed | | RATE_LIMITED | Too many requests — check error.retryAfter | | TIMEOUT | Request timed out | | PROVIDER_ERROR | Provider-side 5xx error | | NETWORK_ERROR | Could not reach the provider |

Provider interface

All adapters implement the same NgPayProvider interface:

interface NgPayProvider {
  readonly name: string;
  initializePayment(params: PaymentParams): Promise<PaymentResponse>;
  verifyPayment(reference: string): Promise<VerificationResponse>;
  createVirtualAccount(params: VirtualAccountParams): Promise<VirtualAccount>;
  createTransferRecipient(params: TransferRecipientParams): Promise<TransferRecipient>;
  initiateTransfer(params: TransferParams): Promise<TransferResponse>;
  verifyTransfer(reference: string): Promise<TransferResponse>;
  getBanks(country?: string): Promise<Bank[]>;
  resolveAccount(accountNumber: string, bankCode: string): Promise<AccountDetails>;
  verifyWebhook(payload: unknown, signature: string): boolean;
  parseWebhookEvent(payload: unknown): WebhookEvent;
}

Security

Auth credentials are stored as non-enumerable properties — they will not appear in JSON.stringify, console.log, Object.keys, or error reporting tools like Sentry. Network errors are scrubbed before being stored in NgPayError.raw.

Links