Ability to change subscription's collection method from platform
🔍 Problem Statement
Currently, changing a subscription’s collection method (for example, from charge_automatically to send_invoice) is supported through the Core API, but this functionality is not available in the platform “Update Subscription” interface which creates an operational gap.
💡 User Story
As a billing or customer support administrator,
I want to change a subscription’s collection method directly from the subscription update page,
So that I can switch customers between automatic charging and invoice-based billing without using external API calls or engineering support.
🎯 Definition of Done (DoD)
A feature is done when:
✔️ When updating a subscription from the platform:
Admin can view the current collection method.
Admin can select a different collection method.
Saving the subscription triggers the backend subscription update endpoint.
The validation rules that apply from core api should be applied on platform too. for example:
Switching to
charge_automaticallyrequires:Valid default payment method
Chargeable customer state
Log in to comment and vote
Comments3
Rana Haleem
May 10
•Merged request
•4 votes
Ability to Update Subscription Collection Method
🔍 Problem Statement
Admins cannot change a subscription's collection method (e.g. from auto-charge to send-invoice) after creation. Switching a customer to invoice-based billing requires cancelling and recreating the subscription.
💡 User Story
As a Pelcro admin, I want to update a subscription's collection method (e.g. auto-charge to invoice), so that I can change billing arrangements without recreating subscriptions.
🎯 Definition of Done (DoD)
A feature is done when:
✔️ Given an active subscription, when an admin changes the collection method from auto-charge to send-invoice (or vice versa), then the change takes effect on the next billing cycle and no subscription recreation is needed.
An Anonymous User
May 7
•Merged request
•3 votes
Switch Subscription Payment Mode: Auto-Renew ↔ Send Invoice
🔍 Problem Statement
As an admin, I experience having to cancel and recreate a subscription to change a customer's payment mode between auto-renew and send invoice, which disrupts subscription dates and creates unnecessary churn.
💡 User Story
As an admin, I want to toggle a subscription between auto-renew and send-invoice without cancelling it, so that I can honor customer payment preferences without affecting subscription history.
🎯 Definition of Done
- Given an active subscription, when an admin changes the payment mode, then the change is applied without altering subscription start/end dates or renewal history.
- This change impacts the UI (subscription detail actions) and API (subscription update endpoint — add paymentMode field).
- Limitations: switching to send-invoice removes auto-charge; a manual invoice must be triggered at next renewal.
What would you like to be able to do? (One idea per form): Change payment settings from "auto renew" to "send invoice" and vice versa without needing to cancel the existing subscription. We would like to be able to change the payment terms per customer request without effecting the start and end dates of the subscription. Customers frequently request to remove the auto renewal feature from their account and currently we aren't able to do that. This includes deleting saved credit card information that is tied to a subscription set to auto renewal. How would that help you?: This would help keep our customers satisfied per their requests and allow us to keep clean records with consistent start and end dates. How important is this to you?: Important Email address: ksouders@wtwhmedia.com ——————————————— This task was submitted through Suggest an idea https://form.asana.com/?k=qsv6hMm2wL8SXD_R-h-N9Q&d=742417627358732Michele Peoples
Jan 9
I strongly agree with this. Thank you!