Skip to main content
Reclack’s API is plain HTTP and JSON, so nothing here is required. These packages exist because two jobs are genuinely awkward to do yourself: putting a payment inside your own page, and connecting a wallet in a browser.

What we publish

On npm, with every published version and its files: @reclack/widget, @reclack/walletkit, @reclack/walletkit-react, @reclack/walletkit-vue. The widget is also served as one file for pages with no bundler:
That gives you window.Reclack, the same function the package exports.

Which one you need

Taking a payment

Use @reclack/widget. It renders our checkout in your page, so you are not rebuilding a payment form or handling a signature yourself.

Sending them to us

Use no library at all. Create a session and redirect to its url. The widget’s redirect() is a convenience, not a requirement.

Connecting a wallet

Use @reclack/walletkit. For an address, a balance, or a wallet connection that has nothing to do with a Reclack payment.

Calling the API

Use your language’s HTTP client. There is no server SDK yet, and the API is small enough that one buys you little.

On your server

Keep your secret key there and call the API directly. Every example in these docs is a plain request, so there is nothing to port.
No browser package ever takes a secret key. The widget throws on one before a request leaves the page. Use a publishable key in anything a visitor can read.

Versions and support

All four packages are published to npm under the @reclack scope, built as ESM, and ship their own TypeScript types. They are pre-1.0, so pin a version if you need the surface to hold still. widget.js on the CDN serves the current release and is cached for five minutes, so a fix reaches your pages without you editing any HTML. Browsers: Chrome, Edge, Firefox and Safari 15.4 or newer. No polyfills are bundled, and nothing here needs a build step beyond what your framework already does.