Stablecoin billing infrastructure
Accept subscriptions directly from wallets
Accept one-time and recurring stablecoin payments directly from your customers’ wallets. Checkout, subscriptions, invoices and billing, without depending on a card processor.
Non-custodial · API-first · Built for stablecoins
Your customers already hold stablecoins in wallets like these
MetaMask
Phantom
Coinbase Wallet
Brave Wallet
Binance Wallet
Trust Wallet
OKX Wallet
Crypto.com
How a payment moves
Collect where your customers already hold value.
A customer signs once, in their own wallet. Reclack opens each billing period, collects against that authorization, and settles to the address you configured.
- Asset
USDC- Networks
+ 20 more- Settlement
- Your own address, per network
Over 20 networks supported. Sandbox runs the same list on test chains.
Pro Plan
Acme Labs · [email protected]
29.00USDC
per month
Spending limit
3 of 12 periods collected
348.00 USDC approved, revocable from the customer’s own wallet.
Customer
MetaMask
0x71A4…29F2
and any wallet the browser exposes412.80USDC
balance
Reclack
Billing
BillingSigned once, in the customer's own wallet.
Active
Merchant
Acme Labs
Base · 0x93F2…1FB4
awaiting
Illustration of a Reclack subscription. Reclack never holds the funds and never asks for a seed phrase or a private key.
The problem
Billing software was built around cards.
Customers who already hold stablecoins should not have to find a card to subscribe to your product. And for some businesses, a card processor was never the right fit for how they sell.
Card-native billing
6 steps
A familiar rail, with a payment method your customers may not want to use for this purchase.
Card details
Wallet-native billing
3 steps
The same billing software your finance team expects, with the payment taken from a wallet instead of a card.
Pay with your wallet
29.00 USDC
One payment stack. More than subscriptions. Everything a business needs around a wallet payment, in one place, on one set of customer records, and designed to work alone or together.
Developers
Built for developers. Ready for product teams.
- Idempotency
- Retry a write safely. It charges once.
- Scoped keys
- No access, read or write, per resource.
- Signed events
- HMAC over the timestamp and the body.
- Sandbox
- Test chains, same code path as live.
const session = await reclack.checkout.sessions.create({ price: "price_pro_monthly", customer: { external_id: "user_123" }, networks: ["base"], success_url: "https://acme.dev/welcome"})Checkout created
200 OKpay.reclack.com/cs_7Fh2PqX9Lm
Send the customer there. The page handles the wallet, the network and the approval.
Infrastructure
Billing infrastructure, not just a transaction button.
Taking one stablecoin payment is a few lines of code. Running a business on recurring ones is everything underneath.
Collection attempts
sub_4Kd9
Pro Plan
[email protected] · Base
29.00 USDC
- 1Oct 18, 22:07insufficient_balance
- 2Oct 19, 04:07insufficient_balance
- 3Oct 20, 22:07collected
Spaced on purpose. A customer whose balance arrives tomorrow should not be chased every minute tonight.
Another way to get paid
Your business should not depend on cards to get paid.
Whether your customers would rather pay in stablecoins or card processors are not the right fit for how you sell, Reclack is another way to take one-time and recurring payments.
Comparison
Built around wallets from day one.
A different rail with the billing experience your team already expects. Most of this list is deliberately the same on both sides.
wallet-nativeCard billing works. It is a payment method some customers would rather not use for this purchase. Settlement timing depends on the network: Reclack marks a payment paid once the chain has confirmed it, which is seconds on the networks it collects on today.
Your customers already have wallets.
Let them subscribe with the money they already hold.