Recurring crypto payments: how to bill on a schedule

September 22, 2026

Recurring crypto payments: how to bill on a schedule

Recurring crypto payments are payments a business collects from the same customer on a fixed schedule, in cryptocurrency instead of on a card. Think of a monthly retainer, a quarterly service fee, or an annual renewal. The commercial shape is the same as any subscription. The mechanics underneath are not, because a crypto transfer is pushed by the person holding the funds.

EukaPay handles recurring crypto payments with subscriptions, which send an invoice to your customer on the interval you choose, from daily through annually. This guide covers what that flow does and what your customer does at each cycle. It also covers where recurring crypto payments differ from card billing, so you can plan around the difference instead of discovering it in month two.

In this guide, you'll learn:

  • What recurring crypto payments are and how they differ from a card mandate

  • How EukaPay subscriptions send a recurring invoice from daily through annually

  • What your customer does at each billing cycle

  • Which parts of subscription billing still live in your own systems

What recurring crypto payments are, and why crypto has no card mandate

Card subscriptions work by pulling. Your customer signs a mandate once, their credentials sit with a processor, and the processor charges them on your instruction every cycle. The customer does nothing after the first payment. That model depends on a central network that can act on stored permission.

Crypto has no equivalent network. Funds move when the holder of the wallet signs a transaction and broadcasts it. No third party can take a payment from a wallet on a schedule. Crypto subscription billing therefore automates the request instead of the charge. You schedule the ask, and your customer completes it.

That distinction decides how you staff the work. Card billing fails quietly and gets fixed by a retry. Crypto billing needs a customer to act, which makes the invoice itself the important part of the flow. The same logic applies to one-off collection through

crypto payment links

, where the payer opens a page and sends the payment.

How EukaPay subscriptions send recurring crypto payments on a schedule

EukaPay's subscriptions product sends invoices on a recurring schedule. You create the subscription against a customer, set the amount and the interval, and EukaPay sends the invoice each cycle without anyone on your team touching it.

Intervals - from daily through annually, set when you create the subscription

The interval range runs from daily through annually. You choose it once, at creation, and the schedule runs from there. You can also create subscriptions programmatically: invoices, subscriptions, payouts, balance transfer, and customers are all part of the documented

crypto payments API

.

What the payer does each cycle - opens the invoice and sends the payment

Your customer receives the invoice and completes it in a browser. They send the payment from whichever wallet they use, the payment confirms on-chain, and the invoice closes. Nothing about that step is headless. Say so plainly to a finance team before they sign off, because it is the one assumption a card background carries over incorrectly.

Can recurring crypto payments be charged automatically like a card subscription?

Not end to end today. EukaPay sends the invoice on your schedule, and your customer completes the payment. The scheduled part is automatic; the payment itself is an action your customer takes each cycle.

The rest of the subscription tooling you may be used to also stays where it is. EukaPay's subscriptions have no plan management, no retry logic, and no programmatic control of the billing cycle. Proration, upgrades and downgrades, dunning sequences, and revenue recognition can stay in the billing system you already run. EukaPay handles the collection leg. For a wider view of what to require from any provider, the

stablecoin payments platform

guide covers the evaluation criteria.

How to choose

Recurring crypto invoices with EukaPay

Card subscription billing

Wallet contract authorization

Who starts each charge?

EukaPay sends the invoice on schedule, your customer sends the payment

The processor charges a stored mandate

A contract the payer approved in advance

Does the payer act each cycle?

Yes, they open the invoice and send the payment

No

No, after the first approval

Chargeback exposure

A crypto payment confirms on-chain, so protection against chargebacks is a property of the payment method

Set by card network rules

Set by the approved contract

What you have to build

Nothing. Create the subscription in the dashboard or through the API

Card vault and mandate handling

Contract integration and wallet support

EukaPay is the route we would put a subscription business on, because the collection leg is a product you configure instead of a system you build. A card mandate hides the per-cycle step from the payer, under rules the card networks write. Wallet contract authorization removes the per-cycle step. It asks your customer to approve a contract before the first payment, and it asks your team to support that contract. EukaPay's subscriptions ask for one action a cycle from the customer and none from you.

One platform for pay-ins, payouts, and fiat settlement

The same account behind recurring crypto payments also covers instant crypto-to-fiat conversion at a locked exchange rate to remove your exposure to crypto price swings, support for most major cryptocurrencies, and settlement in USD, EUR, GBP, and CAD to your bank account. The locked rate is the default on both sides of the account. A crypto payment confirms on-chain, so protection against chargebacks is a property of the payment method.

If you bill on a schedule and want the money in your own currency, ask for this shape: a scheduled invoice, an on-chain payment, and a fiat deposit to your account. Set up the subscriptions you need, point them at your existing customer list, and keep your billing logic where it already runs.

Get started with EukaPay

Create an account at

app.eukapay.com/signup

, complete verification, and provide your legal business information. Generate an API key when you are ready to create subscriptions programmatically, and the endpoints are documented at

docs.eukapay.com

.

Frequently asked questions

What are recurring crypto payments?

They are payments collected from the same customer on a fixed schedule, in cryptocurrency instead of on a card. The schedule is yours to set, and the payment itself is sent by the customer.

Can you set up automatic recurring crypto payments?

You can automate the scheduled invoice. EukaPay sends it on the interval you choose, and your customer completes the payment in a browser each cycle.

How often can a EukaPay subscription send an invoice?

Intervals run from daily through annually. You set the interval when you create the subscription.

What happens if a customer does not pay a recurring invoice?

EukaPay's subscriptions have no retry logic, so following up on an unpaid invoice stays with your team or with your billing system.

Which cryptocurrencies can customers pay with?

Pay-ins cover most major cryptocurrencies, including BTC, ETH, USDC, and USDT.

Can I settle recurring crypto payments in my own currency?

Yes. You can choose fiat settlement to your own bank account in USD, EUR, GBP, and CAD, and the exchange rate is locked on every conversion by default.

Do recurring crypto payments carry chargeback risk?

A crypto payment confirms on-chain, so protection against chargebacks is a property of the payment method.

Do I need to build anything to accept recurring crypto payments?

No. You can create subscriptions in the merchant dashboard, and the API is there if you would rather create them from your own systems.

Related articles