Skip to content

Subscriptions

subscriptions that collect themselves

Your customer signs one bounded approval in their own wallet. Reclack opens every billing period against it, submits the collection onchain, reconciles the payment and tells your application what happened.

Start building

Settles in USDC on

BaseEthereumSolanaPolygonBNBTronBitcoin

Over 20 networks supported

For your customer
Sign once

They approve the plan one time, in the wallet they already use. Nothing to renew, nothing to re-enter.

Every month after
Nobody chases

Each period opens, collects and reconciles on its own, without anyone on your side running anything.

When a payment misses
It tries again

A failed collection is retried over the following days, with a reminder, instead of becoming a lost customer.

Where the money lands
Straight to you

Paid in stablecoins to an address you control. Reclack never holds your money in between.

Lifecycle

What happens every period

The whole cycle runs without the customer coming back, and without anybody on your side running a script.

  1. app.reclack.com/catalog/prod_2Pb8

    Pro Plan

    price_pro_monthly

    Active
    Amount29.00 USDC
    CadenceMonthly
    NetworksBase · Ethereum · Polygon
    TypeFixed

    A price is a record, so you can change what you sell without rewriting the integration.

  2. pay.reclack.com/cs_7Fh2PqX9Lm

    Acme Labs

    Pay Acme Labs

    29.00USDC

    per month

    Pro Planper month
    29.00 USDC
    Subtotal
    29.00 USDC
    Total due
    29.00 USDC

    Pay with your wallet

    Network

    Base

    Wallets

    PhantomTrust WalletOKXOther walletsOr scan to pay on your phone

    You pay 29.00 USDC today.

    You are authorizing Acme Labs to collect 29.00 USDC per month until you cancel.

    1. Approve a spending limit of 348.00 USDCA cap covering about 12 payments in total, you won't be charged yet.
    2. Pay 29.00 USDC todayThe only amount that leaves your wallet now.

    Reclack never requests unlimited access to your funds, and never asks for your seed phrase or private keys.

    Subscribe

    Powered by Reclack · Reclack never asks for your seed phrase or private keys.

  3. app.reclack.com/subscriptions/sub_4Kd9
    DA

    Pro Plan

    [email protected] · monthly on Base

    29.00 USDC

    per month

    Authorization

    2 of 12 periods

    348.00 USDC approved · bounded, revocable from their wallet

    StatusActive
    Next chargeNov 18, 2026
    Collected to date87.00 USDC

    Recent collections

    • Oct 1829.00 USDC0x2e2d…f306
    • Sep 1829.00 USDC0x7b41…c0a9
    • Aug 1829.00 USDC0x15ce…88d4
  4. app.reclack.com/subscriptions/sub_4Kd9

    Retry schedule

    Pro Plan · October period

    Retrying
    1. First attemptOn the billing dateInsufficient balance
    2. Second attemptThe next dayInsufficient balance
    3. Third attemptThree days laterReminder emailed
    4. CollectedDay six29.00 USDC settled

Decide the rules before a charge happens.

The approval, the schedule and the collection are set once and applied every period, so nobody on your side runs anything by hand.

Bounded by what the customer signed.

One approval covering about twelve periods, explained in words on the checkout before anything is signed. A collection can never exceed it, and it is revocable from their own wallet.

Spending limit

348.00 USDC

2 of 12 periods collected · 58.00 USDC used

  • Can exceed the capNever
  • Revocable by the customerAny time

Every period opens on its own date.

Daily, weekly, monthly or yearly. A period can only ever open one invoice, enforced in the database rather than in a worker.

Billing schedule

  1. Oct 18Invoice opened
  2. Nov 18Scheduled
  3. Dec 18Scheduled
  4. Jan 18Scheduled

Collection runs against the authorization.

The charge is submitted onchain and followed to a confirmed state. Nothing is marked paid on optimism.

0x2e2d…f306

Base · 29.00 USDC

Submitted

Followed to confirmation before the period is marked paid

Failures handled, not forwarded.

A payment that does not land is a schedule, not an incident. Your team hears about the ones that matter and nothing else.

First attemptInsufficient balance
Next dayInsufficient balance
Three days laterReminder emailed
Day six29.00 USDC collected

Dunning that behaves.

Customer-caused failures retry over hours and days rather than hammering the chain, with a reminder email on the way. When the schedule runs out the subscription pauses.

subscription.renewed200 OK
invoice.paid200 OK
payment.confirmed200 OK
subscription.cancelled200 OK

Your application is told, not asked.

Signed events with up to six delivery attempts, replayable from the dashboard. Nothing has to poll a chain to find out whether a customer paid.

Subscriptions

One approval. Recurring payments.

Customers do not come back every month to approve the same subscription again. They sign a bounded authorization once, and Reclack runs the billing against it.

Pro Plan

29 USDC/ month

Active

Authorization

Spending limit of 348 USDC, covering about twelve periods. Bounded, revocable from the customer’s own wallet, and never unlimited.

Oct 18

29 USDC

Paid

Nov 18

29 USDC

Paid

Dec 18

29 USDC

Paid

Jan 18

29 USDC

Scheduled

Illustration. Figures are sample data.

What you get

Billing, not just a charge

Fixed or metered

Charge the same amount each period, or bill on the usage recorded through the API.

Dunning that behaves

Customer-caused failures retry on a spaced schedule instead of hammering the chain.

Reconciliation

Every submitted transaction is followed to a confirmed state before a period is marked paid.

Self-service cancellation

Subscribers end a plan from their own wallet, which is their right under the contract.

Invoices per period

Each period opens a real invoice with a PDF, not just a line in a ledger.

Bounded approvals

The limit covers about twelve periods. Reclack never requests unlimited access to funds.

Your application

Told what happened, as it happens

Every state change leaves a signed event. Your application never has to poll a chain to find out whether a customer paid.

webhooks · acme.dev/reclackstreaming

$ reclack logs tail --events --format=json

  • 22:07:41.102 POST subscription.created 201 142ms sub_4Kd9 · Pro Plan
  • 22:07:41.884 POST invoice.opened 200 96ms October period · 29.00 USDC
  • 22:07:44.310 POST payment.confirmed 200 118ms 0x2e2d…f306 on Base
  • 22:07:44.907 POST invoice.paid 500 2004ms Receipt emailed
  • 22:07:46.915 POST subscription.renewed 200 134ms Next charge Nov 18

Reclack-Signature: t=1792447200,v1=5d41402abc4b2a76b9719d911017c592

$

Signed, and retried

Each delivery carries a signature and a timestamp, with up to six attempts if your endpoint is down.

Replayable

Deliveries can be inspected and replayed from the dashboard, so a bad deploy does not cost you a day of events.

Or read it back

Every subscription carries its status, its next charge date and everything it has collected.

Questions

Before you wire it up

What happens when a collection fails?
A failure the customer can fix, such as an insufficient balance, retries on a spaced schedule measured in hours and days rather than minutes. When the schedule runs out the subscription pauses instead of retrying forever.
Can a customer cancel without contacting us?
Yes, when you allow it. Cancelling is the subscriber's own authority under the contract, so it is sent from their wallet and Reclack confirms the chain agreed before marking it cancelled.
How large is the approval?
A cap covering about twelve periods, not unlimited access. The hosted checkout says so in plain words before anything is signed, and the customer can revoke it at any time.
What if the same period is scanned twice?
A period can only open one invoice. The billing scan claims each subscription under a row lock, so several workers divide the work rather than duplicating it.

The rest of the stack

CheckoutPayment linksInvoicesUsage billingCustomer portal

Put your plans on a wallet rail

Start in sandbox on test chains, then move the same code to live.

Start building