At times, users may choose to cancel their subscription—whether it's their primary plan, an app-specific subscription, or another service. This cancellation can be initiated directly within the product or through a partner's system. Similar to the purchase process, the cancellation flow varies based on who manages the billing—whether it's handled by inTandem or the partner.

inTandem billing

Step-by-Step Process:

1. Cancellation Initiation – The user begins the cancellation process by selecting the cancel subscription call-to-action (CTA) and confirming their decision.

2. Subscription Update – Once confirmed, the system updates the subscription accordingly, triggering a Subscription Update webhook to notify relevant systems.

3. Final Status Update – When the subscription reaches its expiration date, its status changes to "Expired", triggering another Subscription Update webhook to reflect the final state.

Partner billing

Step-by-Step Process:

1. Cancellation Initiation – The user starts the cancellation process by selecting the cancel subscription call-to-action (CTA) and confirming their decision.

2. Subscription Update – The partner must inform inTandem of the cancellation request. At this stage, the partner can:

   • Set a future expiration date, allowing inTandem to handle the expiration automatically.
   • Wait until the expiration date and then send another Update Subscription API call to immediately expire the subscription.

3. Final Status Update – The subscription status changes to "Expired", either by inTandem or the partner, once the expiration date is reached. This status change triggers a Subscription Update webhook, ensuring all systems reflect the final state.

📘

At this stage, apps no longer have a valid token for the business, preventing any Get Subscription API calls. Additionally, it is the app’s responsibility to shut down any related services, access, or resources previously provided to the business.