Skip to content
Merchant operations

How Coinvay automatic crypto subscriptions work

Learn the setup required for automatic EVM token billing: customer authorization, reviewed contracts and an operated runner.

THE SHORT ANSWER

Automatic crypto subscriptions use an explicitly authorized EVM token contract, not a stored customer seed phrase. Coinvay’s separate system needs a deployed and reviewed billing contract, approved token allowance, customer activation and an operated gas-funded collection runner.

Understand the customer authorization

The payer reviews a fixed token amount, merchant recipient, network, billing schedule and finite payment budget. A token approval gives the specified contract permission within that allowance; activation establishes the agreement’s terms on-chain. A connected wallet alone is not permission to take future payments. The customer must understand both the approval and activation transactions before agreeing to the subscription.

Operate the billing infrastructure

The gateway interface does not make monthly collections active by itself. The operator needs the supported contract deployed on the selected EVM network, validated configuration, a separate relayer wallet with gas, reliable RPC access and an authenticated scheduled runner. Monitor failed transactions and runner health. For example, a service charging a fixed USDC amount each calendar month must plan for insufficient customer balance, exhausted allowance or unavailable relayer gas without pretending those periods were paid.

Keep entitlements and cancellation synchronized

After a verified charge, the merchant should update its own service entitlement once and retain the agreement and period identity for reconciliation. The customer can cancel through the supported on-chain agreement flow, and the merchant can close its separate link workflow. Explain whether cancellation ends future collection only or also affects access; the contract cannot invent your service policy. This feature applies to configured EVM tokens, not autonomous withdrawals of native Bitcoin, SOL, TRX or TON. A normal recurring invoice remains the simpler choice when customers will pay each period manually.

Practical checklist

  • Review deployed contract identity, exact token, recipient and finite authorization budget.
  • Verify runner scheduling, RPC health, gas funding and failed-charge handling.
  • Test customer cancellation and entitlement updates before offering automatic collection.

Common questions

Is automatic collection live as soon as I select a plan feature?+

No. Plan eligibility grants access to the workflow, while contract deployment and operational readiness are separate requirements.

Can the merchant change the amount after approval?+

The subscription’s reviewed on-chain terms govern collection. A new price or different agreement should require an appropriately new customer authorization, not an invisible dashboard edit.

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