Change or cancel a subscription

Review the subscription you are changing

Open Billing and identify the current terminal product, status, billing interval and renewal or access-end date. If you also have an API subscription, keep its separate entry in view so you do not manage the wrong product. A legacy plan can remain active until you change it even if it is no longer sold. Record the current state before applying a change, especially when comparing immediate access with a scheduled end. A loaded page from an earlier session may need refreshing before its actions reflect a recent provider update.

Choose an available upgrade or switch

Select the desired plan and interval from the current catalog. An existing subscription may offer Upgrade or Switch, which requests a change preview rather than immediately applying the plan. Other changes can route through Manage in Stripe, including interval changes, cancellation or custom subscriptions. The action offered by the application depends on the existing subscription state. Do not assume that selecting Yearly alone modifies billing; it changes the catalog view until you complete the corresponding review or hosted management action.

Read Due now, Next invoice and Takes effect

The preview separates money due now, the next invoice and the effective timing. A prorated upgrade can have a different immediate amount from the advertised full-period price. A payment-dependent change does not grant its new access until the provider confirms payment. A scheduled change can leave the current product in place until a later boundary. Read the actual preview rather than inferring timing from whether you consider a plan an upgrade or downgrade. If no summary is returned, do not invent a charge amount from the plan card.

1. Check the current product and renewal or end date.
2. Choose the intended change and inspect all preview amount and timing rows.
3. Confirm only when the proposed result matches your intended product and interval.

Submit once and verify the resulting state

Use Confirm change to submit the reviewed change, then wait for the action to finish. Subscription change submitted acknowledges the request, while provider confirmation and saved entitlement reconciliation can occur later. Avoid opening several tabs to submit the same change while one is pending. Return to Billing and inspect the current product, status and dates after the provider flow completes. If payment action is required, complete that specific action through the supported provider page rather than repeatedly requesting the same plan switch.

Cancel through the hosted management flow

Use Manage in Stripe for the cancellation options available to the subscription. Review whether cancellation is immediate or at period end before confirming. A cancel-at-period-end state can preserve access until the displayed end date, so the presence of working tools afterward is not proof that cancellation failed. Conversely, merely opening the portal does not cancel anything. Finish the provider's confirmation flow, return to OrderMap and verify the saved cancellation or end-date state for the correct product.

Separate independent subscriptions and access sources

Terminal Options, Futures and Bundle access is independent of API Developer and API Pro. Canceling or changing one product does not establish the state of the other. Trial or account access details can also explain why a tool remains available for a stated period. Provider dataset permissions remain separate from subscription state. Before buying another plan to solve a missing chart, compare the current entitlement message and source coverage. A history gap will not be filled simply because a subscription change succeeded.

Resolve a pending or unexpected change

Refresh Billing after the provider flow and compare the intended product, effective date and relevant invoice. If the state is still pending, preserve the safe provider reference, requested plan, approximate submission time and displayed message. Distinguish a failed change, payment-required change and scheduled change; they need different investigation. Do not repeatedly cancel and resubscribe to force a screen update, as those are separate billing actions. Send support the relevant safe records through a private ticket, leaving out full card numbers, security codes, credentials and private payment or authentication links.