Skip to main content
Reclack is billing infrastructure for stablecoin payments. Your customer signs one bounded approval in the wallet they already use, and Reclack opens each billing period, submits the collection onchain, follows the transaction to a confirmed state, and tells your application what happened.
A customer wallet on the left, Reclack in the middle opening periods and submitting collections, and your own settlement address on the right.A customer wallet on the left, Reclack in the middle opening periods and submitting collections, and your own settlement address on the right.

Money moves from your customer's wallet to an address you control

You can use as much or as little of it as you need. Some teams only create checkout sessions. Others run their whole catalog, subscriptions, invoices and metered usage through the API.
first-payment

Take your first payment

A sandbox payment, end to end, in about ten minutes.
objects

How the objects fit

Products, prices, customers, checkouts, subscriptions and invoices.
authentication

Authentication

API keys, environments and the headers we accept.
webhooks

Webhooks

Signed events, retries, and how to verify them.

​
What Reclack does

​
What Reclack does not do

Being clear about this early saves you an afternoon later.
Reclack is non-custodial. Payments move from your customer’s wallet to a settlement address you control. We never hold your funds, and we never ask a merchant or a payer for a seed phrase or a private key.
A confirmed blockchain transaction is final. There is no chargeback mechanism and we cannot reverse a settled payment. If you agree to refund a customer, you send the funds back from an address you control.

​
Base URL

Every endpoint in these docs is relative to that host. The same host serves sandbox and live traffic. Which one you are talking to is decided by the API key you present, not by the URL.

​
Getting help

Write to [email protected] with the request id from the response headers, or the reference of the object you were working on. That is usually enough for us to find the exact call in the request logs.