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

daraza

v1.0.3

Published

A lightweight, flexible payment processing library for mobile money transactions.

Readme

Daraza Pay

A lightweight, flexible payment processing library for mobile money transactions.

Installation

npm install daraza

Usage

import { PaymentService } from 'daraza';

// Initialize the payment service
const paymentService = new PaymentService({
  apiKey: 'YOUR_API_KEY'
});

// Process a payment
async function processPayment() {
  try {
    // Validate phone number and amount
    const validatedPhone = paymentService.validatePhoneNumber('772123456');
    const validatedAmount = paymentService.validateAmount(1000);

    // Prepare payment data
    const paymentData = {
      method: 1,
      amount: validatedAmount,
      phone: validatedPhone,
      note: 'Payment'
    };

    // Request to pay
    const response = await paymentService.requestToPay(paymentData);
    
    if (response.code === 'Success') {
      console.log('Payment successful:', response);
    } else {
      console.error('Payment failed:', response.details);
    }
  } catch (error) {
    console.error('Payment error:', error);
  }
}

API Reference

PaymentService Constructor

new PaymentService(config: PaymentConfig)

PaymentConfig

  • apiKey: (Required) Your API key for payment processing

Methods

validatePhoneNumber(phoneNumber: string): string

  • Validates and formats phone number
  • Throws an error for invalid phone numbers
  • Returns formatted phone number (e.g., '+256772123456')

validateAmount(amount: number): number

  • Validates payment amount
  • Throws an error for invalid amounts
  • Returns validated amount

requestToPay(data: PaymentData): Promise<PaymentResponse>

  • Sends payment request to the API
  • Returns payment response

PaymentData Interface

interface PaymentData {
  method: number;
  amount: number;
  phone: string;
  note: string;
}

PaymentResponse Interface

interface PaymentResponse {
  code: string;
  details?: string;
}

Error Handling

The library throws descriptive errors for:

  • Invalid phone numbers
  • Invalid payment amounts
  • API request failures

Features

  • Simple, lightweight payment processing
  • Phone number validation
  • Amount validation
  • Flexible API configuration
  • TypeScript support

Requirements

  • Node.js 14+
  • Daraza API Key

License

MIT


The key differences from the previous README:
1. Removed React-specific references
2. Updated installation instructions
3. Provided comprehensive usage example
4. Added API reference with detailed explanations
5. Included information about error handling
6. Specified requirements

This README now accurately reflects the non-UI, service-based nature of the package. Would you like me to modify anything further?