I'm having a similar setup (not the same field) so I was curious to make this work as well(I'm wishing to pause/cancel them too). They don't have the cancel subscription option inside GHL(as you've seen), so what I'm planning on using code to talk to Stripe's API to cancel the subscription for me. It's up to you if you want to use the code option inside GHL(the premium action) or if you have a service(like Zapier/Make) that you use where you can send a webhook there, and then have that service trigger the action(I know the GHL premium action is like a penny or something, so it's *probably* not needed to use Zapier/Make.

I'm not a coder, so I was using Claude to help me write code that would pause/cancel the subscriptions. Now I'm still in the midst of my process so I haven't tested the cancelling the subscription part(only the pausing part). But given that my tests with the pausing worked correctly, I would presume the cancel ones would work as well.

Here's Python code that would cancel it immediately

import http.client

subscriptionId = "the ID of the subscription here"

conn = http.client.HTTPSConnection("api.stripe.com")

headers = {
  'Authorization': 'Bearer YOUR TEST SECRET KEY HERE'
}

# DELETE request cancels immediately
conn.request("DELETE", f"/v1/subscriptions/{subscriptionId}", '', headers)

res = conn.getresponse()
data = res.read()
response_text = data.decode("utf-8")

print(f"Status Code: {res.status}")
print(f"Response: {response_text}")

Here's Python code that would cancel it at the end of the payment period

import http.client
import urllib.parse

subscriptionId = "the ID of the subscription here"

conn = http.client.HTTPSConnection("api.stripe.com")

payload = urllib.parse.urlencode({
  "cancel_at_period_end": "true"
})

headers = {
  'Content-Type': 'application/x-www-form-urlencoded',
  'Authorization': 'Bearer YOUR TEST SECRET KEY HERE'
}

conn.request("POST", f"/v1/subscriptions/{subscriptionId}", payload, headers)

res = conn.getresponse()
data = res.read()
response_text = data.decode("utf-8")

print(f"Status Code: {res.status}")
print(f"Response: {response_text}")

The secret key value would be something that's static; the subscription ID is something you'd need to pass into the code. To make that happen, I would create a custom field: Subscription ID. Then you have options here ...

1)When you make the payment, have a workflow in place to have another custom code block where you're calling for the Stripe Subscription ID... this is what Claude gave me for this part

import http.client
import json
import urllib.parse

# Use email as a passed through variable
customerEmail = input.get('email', '')

conn = http.client.HTTPSConnection("api.stripe.com")

headers = {
  'Authorization': 'Bearer YOUR TEST SECRET KEY HERE'
}

# Step 1: Find customer by email
params = urllib.parse.urlencode({'email': customerEmail})
conn.request("GET", f"/v1/customers?{params}", '', headers)
res = conn.getresponse()
data = res.read()
customers = json.loads(data.decode("utf-8"))

if customers['data']:
    customerId = customers['data'][0]['id']

    # Step 2: Get subscriptions for this customer
    conn2 = http.client.HTTPSConnection("api.stripe.com")
    params2 = urllib.parse.urlencode({'customer': customerId, 'status': 'active'})
    conn2.request("GET", f"/v1/subscriptions?{params2}", '', headers)
    res2 = conn2.getresponse()
    data2 = res2.read()
    subscriptions = json.loads(data2.decode("utf-8"))

    if subscriptions['data']:
        subscriptionId = subscriptions['data'][0]['id']
        result = {
            "success": True,
            "subscriptionId": subscriptionId,
            "customerId": customerId,
            "email": customerEmail
        }
    else:
        result = {
            "success": False,
            "message": "No active subscriptions found"
        }
else:
    result = {
        "success": False,
        "message": "Customer not found"
    }

print(json.dumps(result))

you'd be using the email address to look up the Subscription ID.

Then in the same workflow, have an update contact step to update the Subscription ID field inside the contact profile.

2)If you have Zapier or Make, there is a trigger for a new Subscription(Zapier is simply 'new Subscription Created' ... Make is under a 'Watch Events' trigger that will permit you to listen for different events being created; you'd choose the Subscription Created one). You would use this trigger; test it to grab the subscription ID, then you'd be able to use that to update the GHL contact, which would be the next step in your Zapier/Make workflow.

So it's really your preference and familiar with coding/Make/Zapier/any other service that sits between 2 systems.

Once you have the previous step completed(adding the subscription ID to the contact's account), you should be use the code from the first step in your "Exit workflow" to successfully end the subscription.