Do we have to hold our users' funds?

No. Payments move from their wallet to an address you control, on the chain they chose. Reclack never takes custody and never holds a balance between you.

Is the approval unlimited?

Never. The checkout asks for a cap covering about twelve periods and says so in plain words. The customer can revoke it from their own wallet at any time.

What do we gate access on?

The signed events. subscription.created, renewed and cancelled arrive at your endpoint with retries, so your gate reflects the chain rather than a cached guess.

DeFi tooling

No card rails. No redirect. Just the wallet.

Your users arrived with a wallet connected. Asking them to find a card to pay for your tooling is the one step in the product that does not belong to this world.

Start building

app.yourprotocol.xyz

Pro access

0x71A4…29F2

ConnectThe wallet already in the browser
ApproveA bounded limit, signed once
AccessUnlocked while the plan is active

No card form, no redirect to a payment processor, and no seed phrase ever requested. The wallet signing is the one they are already trading with.

The flow

Four moments, all of them onchain

Nothing here routes through a card network, and nothing asks a user for a credential they would be right to refuse.

The page

What a user actually sees

The hosted checkout, with your branding, the networks you accept and the limit written out before it is signed.

pay.yourprotocol.xyz/cs_7Fh2PqX9Lm

Your Protocol

Pay Your Protocol

49.00USDC

per month

Pro accessper month: 49.00 USDC
Subtotal: 49.00 USDC
Total due: 49.00 USDC

Pay with your wallet

Network

Base

Wallets

Other walletsOr scan to pay on your phone

You pay 49.00 USDC today.

You are authorizing Your Protocol to collect 49.00 USDC per month until you cancel.

Approve a spending limit of 588.00 USDCA cap covering about 12 payments in total, you won't be charged yet.
Pay 49.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.

Your application

Gate on events, not on polling

Every state change leaves a signed event, so access opens and closes on what actually happened.

webhooks · yourprotocol.xyz/reclackstreaming

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

22:07:41.102 POST subscription.created 201 142ms 0x71A4…29F2 · Pro access
22:07:41.884 POST payment.confirmed 200 96ms 0x2e2d…f306 on Base
22:07:44.310 POST subscription.renewed 200 118ms Next charge Nov 18
22:07:44.907 POST subscription.cancelled 500 2004ms Sent from the wallet

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

$

Signed and retried

A signature and a timestamp on every delivery, with up to six attempts if your endpoint is down.

Never a seed phrase

Reclack asks a user to connect and sign. It never asks for a seed phrase or a private key.

Revocable by them

The allowance belongs to the user. Revoking it in their wallet is a thing they can simply do.

Questions

Before you charge for access

Do we have to hold our users' funds?: No. Payments move from their wallet to an address you control, on the chain they chose. Reclack never takes custody and never holds a balance between you.
Is the approval unlimited?: Never. The checkout asks for a cap covering about twelve periods and says so in plain words. The customer can revoke it from their own wallet at any time.
What do we gate access on?: The signed events. subscription.created, renewed and cancelled arrive at your endpoint with retries, so your gate reflects the chain rather than a cached guess.

No card rails. No redirect. Just the wallet.

Four moments, all of them onchain

What a user actually sees

Gate on events, not on polling

Before you charge for access

Charge where your users already are