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

@slates-integrations/flutterwave

v0.3.1

Published

Inspect transactions, payouts, refunds and settlements through the supported Flutterwave API v3. Manage payment plans, subscriptions, beneficiaries and virtual accounts; discover bank and bill-product details; submit and inspect bill payments.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

tobihrbrtobihrbrvnxvnxvnxvnx

Keywords

Readme

Flutterwave

Inspect transactions, payouts, refunds and settlements through the supported Flutterwave API v3. Manage payment plans, subscriptions, beneficiaries and virtual accounts; discover bank and bill-product details; submit and inspect bill payments.

Use an API v3 Secret Key. Configure sandbox for FLWSECK_TEST- test keys and production for live FLWSECK- keys. Both modes use the documented v3 API host. A mismatched environment/key or an API v4 token is rejected before any request. The retained oauth_v4 auth option is deprecated and unavailable: v4 uses a separate client-credentials grant and different APIs. Reconnect with an API v3 Secret Key for these tools.

Financial operations may remain pending or have irreversible effects. Inspect exact transaction/transfer/refund references before retrying an uncertain request. Bill submission returns acceptance, not delivery; use get_bill_payment with the returned tx_ref. Dynamic virtual accounts expire; issuance does not confirm collection. Subscription activation may resume automatic billing. Test-mode receipts can still reach the business email.

For prepaid utility bills, get_bill_payment exposes the provider's redemption token as rechargeToken when returned. This is the code used to redeem the purchased utility credit; API and reusable payment credentials remain withheld.

Bill payments currently support Nigerian billers (NG). Confirm cable and utility customer details before submitting a payment. Flutterwave recommends its separate customer-validation API for this; that optional API is not exposed here. Airtime and data payments do not require that validation.

Legacy input/output keys remain available. Transaction listing requires explicit from and to dates at invocation. paymentType has no documented v3 listing filter and fails with remediation rather than silently ignoring it. Bill customer maps to customer_id; type remains a descriptive label, and unsupported recurring schedules are rejected. Reusable card credentials are withheld from the retained optional cardToken field.

License

Licensed under the FSL-1.1.