Skip to content
Business use cases

Choose the right crypto billing flow for a SaaS product

Choose one-time, recurring-invoice or automatic token billing for SaaS and connect verified charges to customer entitlements.

THE SHORT ANSWER

A SaaS product can use one-time crypto invoices, recurring invoices or separately configured automatic token subscriptions. Choose the flow that matches customer consent and entitlement rules rather than calling every repeat invoice an automatic subscription.

Start with your access model

Define what a payment buys: a fixed-duration membership, usage credits, a one-time license or a service milestone. Your backend should calculate the price and map the Coinvay invoice to that exact entitlement. For example, a thirty-day access purchase should become active only after verified settlement and should record its own start and end rules. The browser’s return to the product is not permission to unlock a paid account.

Choose manual or automatic renewal deliberately

A recurring invoice is appropriate when the customer will approve each new transfer. Automatic token subscriptions require the supported EVM contract workflow, finite allowance, customer activation, deployed reviewed contracts and an operated gas-funded runner. Native Bitcoin, SOL and TON do not become automatically chargeable through an EVM token approval. Keep the service’s cancellation and failed-payment policy aligned with the actual billing method shown to the customer.

Design for failed collections and support

Insufficient balance, exhausted allowance, unavailable relayer gas and RPC failures can interrupt automatic collection. Do not grant a fresh paid period solely because a due date arrived. Update entitlements from verified charges with unique agreement-and-period identities, and avoid duplicate extensions when notifications repeat. Provide a clear customer cancellation path and explain whether previously paid access continues. Sandbox helps test checkout and testnet receipt handling, but the SaaS entitlement engine, email delivery and automatic contract deployment need separate acceptance checks before launch.

Practical checklist

  • Define the entitlement purchased and map it to a trusted invoice or agreement period.
  • Explain whether renewal is a fresh customer payment or an on-chain automatic agreement.
  • Test cancellation, failed collection, duplicate charges and entitlement recovery.

Common questions

Can a customer connect a wallet once and then be charged without further setup?+

No. Connection alone is not debit authorization. Automatic token billing requires explicit approval and activation of the supported agreement.

Does paying my Coinvay merchant plan renew my customer’s SaaS membership?+

No. Your merchant membership and customer subscriptions are separate records with different purposes and payment flows.

Sources and further reading

Primary references and Coinvay product documentation. Check the linked pages for current details.

  1. Coinvay merchant API documentation

AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.

Back to all articles