Payments & checkout

Recurring Crypto Payments

Basics Also known as recurring crypto payments crypto subscription service crypto subscription how to charge crypto monthly

In short

Recurring crypto payments run into one structural obstacle: a blockchain transfer is initiated by the holder of the funds and nobody else. Card subscriptions work because the merchant pulls money from an account it has permission to debit. No equivalent permission exists in a wallet, so subscriptions have to be built rather than switched on.

Why subscriptions need a different design

Push versus pull

The distinction explains everything that follows.

A card payment is a pull: the merchant sends a request, the issuer approves it, and money moves without the cardholder doing anything at the time. This is what makes both subscriptions and chargebacks possible, since a mechanism that can move money on request can also move it back.

A crypto payment is a push: the payer signs a transaction, and nothing happens until they do. That removes chargeback exposure entirely and removes automatic renewal along with it.

The four approaches

Invoice each cycle

The simplest. A crypto invoice is generated on schedule and the customer receives a reminder with a payment link. Nothing technical is required beyond what any payment gateway already does.

What it costs in churn

The cost is churn. Every renewal becomes a decision, and a proportion of customers do not make it. This is the honest trade-off, and it is why prepaid models below tend to win at scale.

Prepaid balance

The customer tops up an account, and the service draws from it monthly. One payment covers several cycles, so the renewal decision happens quarterly or yearly instead of monthly. Widely used by hosting and VPN providers, and it works well for the same reason gift cards do.

Smart contract allowance

The customer signs one approval permitting a smart contract to withdraw up to a set amount on a schedule. This is genuine pull, and it is the closest crypto gets to a card subscription.

The trade-off

The trade-off is the risk the contract entry describes: the approval persists until revoked, the code cannot be edited after deployment, and a customer who does not understand what they signed has given standing permission to a program. Available on networks that support contracts, absent on Bitcoin.

Custodial account

The customer holds a balance with the provider, which debits it. Operationally identical to a card subscription and it makes the provider a custodian, with the obligations that follow.

Which one to use

Depends on the billing period and the customer relationship.

Monthly consumer subscriptions suffer most from manual renewal, so prepaid balances usually win. Annual business contracts renew fine on invoices, because one decision a year is not friction. High-value contracts often move to invoicing with terms, since the amounts justify a person handling them.

For a SaaS business the practical answer is frequently a combination: prepaid credits for self-service tiers, invoicing for enterprise. The setup guide covers how the pieces connect.

What to build in either way

Three things, regardless of approach.

Reminders before the cycle date, because a customer who forgets is a customer who lapses. A grace period, so a late payment does not immediately terminate service. And a clear record of which cycle each payment covered, since the fiat value differs between cycles even when the crypto amount does not.

Frequently asked

Only through a smart contract allowance or a custodial balance. A plain wallet cannot be debited without the holder signing.

No. The absence is the same property that prevents automatic pulls.

Prepaid balances, in most cases, because they reduce the number of renewal decisions.

Yes. Pricing stays in fiat and each cycle converts at the current rate.

Service lapses. There is nothing to attempt a retry against, which changes dunning strategy entirely.

Was this article helpful?

See also