Skip to content
Merchant operations

Let customers cancel automatic crypto subscriptions

Plan customer-controlled cancellation of automatic crypto agreements while preserving charge history and service policies.

THE SHORT ANSWER

A customer-controlled cancellation flow is essential for automatic token billing. Coinvay’s separate EVM subscription system includes an on-chain cancellation path, while the merchant must also update its own service and support records consistently.

Explain which subscription is being cancelled

A merchant may have a recurring-invoice record, an automatic token agreement and a paid Coinvay merchant plan in different parts of the dashboard. These are not interchangeable. Cancelling a recurring invoice record stops that future invoice workflow; cancelling an on-chain automatic agreement concerns future token collection. Show the exact merchant, token, network and agreement being changed so a payer does not accidentally target an unrelated authorization.

Make the chain state authoritative

For an active automatic agreement, the customer uses the wallet and network associated with the payer to submit the supported cancellation transaction. Until the transaction is confirmed, do not announce that the on-chain schedule has certainly stopped. The customer may also review the token allowance in their wallet. Revoking an allowance and cancelling an agreement are different operations, even when either can prevent a later transfer. Keep transaction evidence and the latest agreement state available for support.

Coordinate cancellation with access and refunds

Suppose a customer cancels a monthly design tool halfway through a paid period. Stopping future collection does not automatically reverse the earlier transfer or determine when product access should end. Apply the service’s published policy and update the entitlement system separately. Test cancellation close to a due date, a pending collection and a failed RPC request. Do not delete the charge history when an agreement is cancelled; those earlier receipts remain necessary for reconciliation and customer questions.

Practical checklist

  • Identify the exact agreement, payer wallet and network before presenting cancellation.
  • Wait for verified on-chain state rather than trusting a browser button click.
  • Explain access timing and refund handling separately from future payment cancellation.

Common questions

Does cancellation automatically return previous payments?+

No. Completed transfers remain historical payments. Any agreed refund is a separate merchant-authorized wallet transaction.

Can a customer cancel without giving Coinvay their private key?+

Yes. The supported flow asks the customer’s own wallet to approve the necessary on-chain action. The gateway should never request a seed phrase or private key.

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