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

@riskdefy/chargebacks

v1.0.16

Published

Chargebacks Vue component

Readme

Chargeback Response Builder

The chargeback response builder is an NPM module powered by Riskdefy.io, a web-based merchant management platform built to help merchant organizations that manage portfolios of merchant accounts.

Riskdefy.io technology creates dynamic-URL PDF chargeback responses in seconds. It streamlines the entire dispute process — loading chargebacks to generating credit card rules-based responses — saving merchants valuable time, money and lost revenue from chargebacks.

| Overview | | -------- | | You'll need to create an account in order to use the API. If you have a riskdefy.io Standard API package or higher, you can enable the API Workflow from the user account settings. The API is available for NPM level customer accounts only. Create an account |

Features

  • Auto-load new/incoming chargebacks
  • Auto-retrieve customer records and details
  • Advanced conditional logic based on card brand rules
  • Create and send digital response packets via dynamic URL PDF
  • Auto-match transactions with chargebacks
  • Customizable generated responses
  • Create automation flows for each merchant

Installation

Install the Chargebacks module using npm:

npm install chargebacks

Usage

Here is an example of how to use the Chargebacks module in a Vue project:

import Chargebacks from 'chargebacks';

<Chargebacks apikey={your_api_key} merchantId={your_merchant_id} />

Contributing

We welcome contributions! If you encounter any issues or have suggestions for improvements, feel free to open an issue or submit a pull request.

For Businesses

Integrate seamless chargeback responses into your web or mobile apps with Riskdefy

At Riskdefy.io we have expertise and technologies to create and respond to chargebacks seamlessly integrated with your product. We specialize in working with low to high risk merchant processing industries, including Gambling, Adult, Online Games, Coaching, Nutra, Vape, CRM, and other software products that require chargeback prevention and responding. By leveraging Riskdefy, we can assist in reducing the overall cost of developing and creating chargebck responses while ensuring security and compliance with local electronic document laws.

Book a Meeting

Documentation

License

This version follows the best practices for README.md formatting and ensures clarity. Let me know if you need any modifications! 🚀