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

billerapi-react

v1.0.1

Published

React bindings for the BillerAPI Elements SDK — hooks and provider for the connect, add-payment-method, and pay flows

Readme

billerapi-react

React bindings for the BillerAPI Elements SDK (billerapi-js). Wrap your app in ElementsProvider, then drive each flow with a hook: useConnect, useAddPaymentMethod, usePay.

The hooks are thin wrappers over the billerapi-js flow factories. The hosted iframe owns all sensitive UI — card PAN/CVV and credentials never enter your React context.

Install

pnpm add billerapi-react billerapi-js react

react (>=16.8) is a peer dependency. billerapi-js is a direct dependency and provides the underlying SDK.

Setup

Provide a single SDK instance once, near the root of your tree. Keep config stable (module scope or memoized) so the instance is not recreated each render.

import { ElementsProvider } from 'billerapi-react';

const elementsConfig = { clientId: 'your_client_id' };

export function App() {
  return (
    <ElementsProvider config={elementsConfig}>
      <Checkout />
    </ElementsProvider>
  );
}

Hooks

Every hook returns the same shape:

interface ElementsFlowResult {
  open: () => Promise<void>; // open the modal (idempotent)
  close: () => void;         // close the modal (idempotent)
  isOpen: () => boolean;     // is the modal open?
  ready: boolean;            // true once a provider instance is available
  error: ElementsError | null; // last open failure (also routed to onExit)
}

The modal is closed automatically when the consuming component unmounts.

useConnect

import { useConnect } from 'billerapi-react';

function ConnectButton({ linkToken }: { linkToken: string }) {
  const { open, ready, error } = useConnect({
    linkToken,
    onSuccess: (publicToken, metadata) => {
      // exchange publicToken server-side
    },
    onExit: (err) => {
      if (err) console.error(err.code, err.message);
    },
  });

  return (
    <>
      <button disabled={!ready} onClick={() => void open()}>
        Connect account
      </button>
      {error && <p role="alert">{error.message}</p>}
    </>
  );
}

useAddPaymentMethod

import { useAddPaymentMethod } from 'billerapi-react';

function AddCardButton({ payToken }: { payToken: string }) {
  const { open, ready } = useAddPaymentMethod({
    payToken,
    onSuccess: (paymentMethodId, metadata) => {
      // metadata.last_4 / metadata.card_brand available
    },
  });
  return (
    <button disabled={!ready} onClick={() => void open()}>
      Add card
    </button>
  );
}

usePay

import { usePay } from 'billerapi-react';

function PayButton({ payToken, billId }: { payToken: string; billId?: string }) {
  const { open, ready } = usePay({
    payToken,
    billId,
    onSuccess: (paymentAttemptId, metadata) => {
      // metadata.bill_id available
    },
  });
  return (
    <button disabled={!ready} onClick={() => void open()}>
      Pay bill
    </button>
  );
}

Notes

  • onSuccess is required for every flow; onExit, onLoad, onEvent, and theme are optional and forwarded straight through to billerapi-js.
  • Calling open() outside an ElementsProvider resolves to an error with code MODAL_OPEN_ERROR and invokes onExit instead of throwing.
  • All wire fields (metadata, theme) are snake_case, matching the core SDK's contract; developer-facing options are camelCase.

Escape hatch

Need the raw SDK instance (e.g. for getConfig() or a custom flow)? Use useElements() inside a provider:

import { useElements } from 'billerapi-react';

const elements = useElements(); // throws if no provider in tree