# Can Subscriptions use something other then Stripe?

**URL:** <https://meta.discourse.org/t/can-subscriptions-use-something-other-then-stripe/293954>\
**Category:** Product Support\
**Tags:** subscriptions\
**Created:** [November 25, 2023, 11:41am UTC](https://meta.discourse.org/t/can-subscriptions-use-something-other-then-stripe/293954 "2023-11-25T11:41:52Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [November 27, 2023, 11:25am UTC](https://meta.discourse.org/t/can-subscriptions-use-something-other-then-stripe/293954/4 "2023-11-27T11:25:11Z")

</div>

Oh. Right. A plugin could just catch whatever webhook the subscription plugin made and plugin settings could map the subscription name to the group (and match user but email address). A group custom field could hold the associated subscription ID and move the user in ou out of the group when the subscription was updated. If it used a subscription name rather than id, a single custom field could handle multiple payment handlers.

The admin would be responsible for setting up the payment system and arranging for the user to get to a payment page.

Here is the webhook info for lemon squeezy

> **[Docs: Webhooks](https://docs.lemonsqueezy.com/help/webhooks)**
>
> Lemon Squeezy's webhooks notify your application of key store events, such as license key creation or subscription expiration, enabling efficient handling of asynchronous activities.

I’d love to do this for someone who had a budget.

---

_[View the full topic](https://meta.discourse.org/t/can-subscriptions-use-something-other-then-stripe/293954)._