Skip to content

Stablecoin billing infrastructure

Accept subscriptions directly from wallets

Take one-time and recurring USDC payments straight from your customers’ wallets, with the checkout, invoices and billing infrastructure to run a real business around them.

Start buildingRead the docs

Non-custodial · API-first · Built for stablecoins

Your customers already hold stablecoins in wallets like these

  • MetaMask
  • Coinbase Wallet
  • Brave Wallet
  • Phantom
  • Trust Wallet
  • OKX Wallet
  • Binance 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
USDCUSDC
Networks
BaseEthereumSolanaPolygonBNBTronBitcoin+ 20 more
Settlement
Your own address, per network

Over 20 networks supported. Sandbox runs the same list on test chains.

Pro Plan

Acme Labs · dana@acme.dev

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 exposes

412.80USDC

balance

Reclack

Billing

Signed 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

Card billing was not designed for wallet-native businesses.

If your customers already hold stablecoins, they should not have to find a card just to subscribe to your product. Some crypto-native businesses also struggle to onboard with card processors at all.

Card-native billing

6 steps

A familiar rail, with a payment method your customers may not want to use for this purchase.

Card details

1234 1234 1234 1234
MM / YY
CVC
Pay

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

MetaMaskDetected
Coinbase Wallet
Pay 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.

Subscriptions that collect themselves

app.reclack.com/subscriptions

Pro Plan

29.00 USDC

Acme Labs · monthly on Base

3 of 12 periods collected · next on Nov 18

Oct 1829.00 USDCPaid
Sep 1829.00 USDCPaid

Checkout your customers can read

pay.reclack.com

Pay with your wallet

29.00 USDC

MetaMask
Coinbase WalletDetected
Brave Wallet
Pay 29.00 USDC

Payment links with nothing to deploy

pay.reclack.com/pl_8Qd3

Premium Research Access

49.00 USDC

Pay with wallet

pay.reclack.com/pl_8Qd3ZkR2

Invoices that chase themselves

pay.reclack.com/in_0182

INV-00182

Open

Due Nov 10

Platform seats (4)
80.00
Support retainer
40.00
Total due
120.00 USDC
Pay invoice

Usage billing on what was recorded

app.reclack.com/usage

API usage · October

1,284,922

requests

Current bill38.41 USDC

Customer portal that answers your billing email

pay.reclack.com/acme

Acme Labs

Your billing

0x71A4…29F2
SubscriptionsInvoicesPayments
  • INV-00182120.00 USDCPaid
  • INV-0016429.00 USDCPaid

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.
POST/v1/checkouts
const session = await reclack.checkout.sessions.create({  price: "price_pro_monthly",  customer: { external_id: "user_123" },  networks: ["base"],  success_url: "https://acme.dev/welcome"})
Response128 ms

Checkout created

200 OK

pay.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

dana@acme.dev · Base

29.00 USDC

  1. 1Oct 18, 22:07insufficient_balance
  2. 2Oct 19, 04:07insufficient_balance
  3. 3Oct 20, 22:07collected
Schedule6h · 24h · 72h · 7d
After the last attemptSubscription pauses
Transaction0x2e2d…f306

Spaced on purpose. A customer whose balance arrives tomorrow should not be chased every minute tonight.

For crypto-native businesses

Your business does not fit card rails? That is fine.

Reclack gives crypto-native businesses another way to get paid: directly from customer wallets, with the billing infrastructure to run a real business around it.

Start in sandboxRead the docs

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.

Payment methodCardCards and bank railsReclackStablecoin wallets
Recurring paymentsCardCard mandate on fileReclackBounded wallet authorization
SettlementCardProcessor settles to your bankReclackSettles to your own address
Settlement speedCardDays if not weeksReclackInstant
ChargebacksCardDisputes and representmentReclackNone. A refund is yours to send
Proof of paymentCardThe processor's recordReclackA public transaction either side can check
Hosted checkoutCardYesReclackYes
Invoices and PDFsCardYesReclackYes
Payment linksCardYesReclackYes
Customer portalCardYesReclackYes, wallet sign-in
Signed webhooksCardYesReclackYes
Crypto-native businessesCardDepends on the processorReclackThe core use case

Card 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.

Start buildingRead the docs