cancel_at_cycle_end: true ignored — subscription cancel is not working

[kishan79]

Steps to reproduce the behavior

When calling:

razorpay.subscriptions.cancel(subId, { cancel_at_cycle_end: true });

The subscription is not canceled at the end of the billing cycle. The API response shows:

"has_scheduled_changes": false,
"change_scheduled_at": null

even though the cancel_at_cycle_end parameter was provided.

Impact:

This makes it impossible to show a "cancels at end of period" message in the UI or honor user intent, forcing developers to implement unreliable workarounds.

Expected behavior

According to the official docs, passing cancel_at_cycle_end: true should:

Schedule cancellation at the end of the current cycle

Return:

"has_scheduled_changes": true,
"change_scheduled_at": "cycle_end",
"current_end": [timestamp]

Impact:

This makes it impossible to show a "cancels at end of period" message in the UI or honor user intent, forcing developers to implement unreliable workarounds.

Actual behavior

When calling:

razorpay.subscriptions.cancel(subId, { cancel_at_cycle_end: true });

The subscription is not canceled at the end of the billing cycle. The API response shows:

"has_scheduled_changes": false,
"change_scheduled_at": null

even though the cancel_at_cycle_end parameter was provided.

Impact:

This makes it impossible to show a "cancels at end of period" message in the UI or honor user intent, forcing developers to implement unreliable workarounds.

Code snippets

Node version

v23.11.0

Library version

^2.9.6

Additional Information

Impact:

This makes it impossible to show a "cancels at end of period" message in the UI or honor user intent, forcing developers to implement unreliable workarounds.

[vrijraj]

I am also facing the same issue

How can we inform users in the frontend that their subscription will be cancelled at the end of the current billing cycle?

Razorpay doesn't seem to return any specific value, indicating that the subscription status remains active until an immediate cancellation

From Razorpay, I always get when I cancel the subscription (immediate or cancel at cycle end)

 "has_scheduled_changes": false,
  "change_scheduled_at": null,

[DuttaAnirudh]

I encountered a similar issue with razorpay@2.9.8. The Node SDK source defines subscriptions.cancel(subscriptionId, cancelAtCycleEnd), where the second argument is a boolean, but the SDK documentation currently shows passing an options object:

instance.subscriptions.cancel(subscriptionId, {
  cancel_at_cycle_end: true
});

Passing the object causes it to be treated as a truthy cancelAtCycleEnd value. For immediate cancellation, I found that:

instance.subscriptions.cancel(subscriptionId, false);

works correctly.

I reproduced this against the same Test Mode subscription using both the SDK and the REST API. The REST API with cancel_at_cycle_end: false correctly cancelled the subscription, while the SDK call using the documented object syntax left it active.

It looks like the Node SDK documentation may need to be updated to reflect the actual method signature.