# Recurring crypto invoices: collect each billing period clearly

> Recurring invoices organize repeat payment requests, but they do not withdraw money from a customer’s wallet automatically. In Coinvay, renewal creates or reuses a period’s invoice and the customer approves a new payment for that request.

Publisher: Coinvay | Published: 2026-10-27 | Updated: 2026-10-27 | Category: Merchant operations
Canonical: https://coinvay.com/articles/crypto-recurring-invoices

Understand recurring crypto invoices, billing-period mappings and why each renewal requires a new customer-approved payment.

## Choose recurring invoices for customer-controlled payments

A recurring invoice is suitable when customers should decide when to send each transfer. It can support retainers, repeat service work or a business arrangement that needs a recognizable billing period. The merchant still needs a process for creating renewals, notifying customers and deciding how unpaid periods affect service. Enabling a recurring-invoice feature does not establish a standing authorization over the payer’s wallet.


## Keep each period linked to its own request

For example, an agency can issue an invoice for October support and then create a November renewal. Store the subscription record, period, order reference and resulting invoice together. Repeating the renewal action for the same billing period should not create uncontrolled duplicate requests. Compare any received payment to that specific period’s invoice before extending service. Reusing an old paid checkout link is not a way to record a new month’s revenue.


## Distinguish customer billing from merchant plans

Coinvay customer recurring-invoice records are separate from your own Free, Pro or Enterprise merchant membership. A plan upgrade changes your merchant access; it does not pay a customer invoice. Automatic crypto subscriptions are another separate flow requiring deployed EVM token contracts, customer authorization and an operated collection runner. Select the workflow deliberately and use language such as pay this month’s invoice when a fresh customer transfer is required. Cancelling a recurring-invoice record stops that record, not an already completed blockchain transfer.


## Practical checklist

- Explain whether each period requires a new customer-approved transfer.
- Map the invoice to a clear service period and reconcile it before extending access.
- Define late-payment, cancellation and service policies outside the payment button.

## Questions and answers

### Does a recurring invoice mean automatic wallet withdrawals?

No. Customers pay the renewal invoice themselves. Contract-based automatic token subscriptions require a different setup and explicit authorization.

### Is cancelling a recurring invoice record a refund?

No. It changes the billing record’s future workflow. A refund is a separate, authorized transfer from the merchant wallet.

## Sources and further reading

- [Coinvay merchant API documentation](https://coinvay.com/docs)

## Related guides

- [Direct Wallet Settlement vs. Platform Balances](https://coinvay.com/articles/direct-wallet-settlement-vs-platform-balances)
- [Wrong Network at Crypto Checkout: Prevention and Support](https://coinvay.com/articles/crypto-checkout-network-mistakes)
- [Crypto Quote Expiry: What Happens When the Timer Runs Out?](https://coinvay.com/articles/crypto-quote-expiry)

Published by Coinvay with AI-assisted drafting. Product claims were checked against the implementation and linked primary sources. Provider facts and pricing can change; verify the current terms before choosing a service. Examples are illustrative, not customer results. No ranking or AI citation is guaranteed.