Plugin de Assinaturas do Discourse

:discourse2: Summary The Discourse Subscriptions plugin allows site owners to sell recurring and one-time purchase subscriptions that grant access to a group on a Discourse instance.
:open_book: Install Guide This plugin is bundled with Discourse core. There is no need to install the plugin separately.

The Discourse Subscriptions plugin allows you to create one-time as well as recurring subscriptions that users can pay for in order to access gated content. This can be a great way to fund the hosting cost of your community.

Features

The Discourse Subscriptions plugin supports the following features:

The “Subscribe” button located in the top nav will take you to the Subscribe page /s where it lists the subscriptions you have configured for your site:

Once a user clicks on one of the “Subscribe” button for a specific plan it will open up the payment page for that plan:

After a user fills out their payment details and their address and click “Subscribe”, they are shown a “Thank you!” message and taken to their billing page:

The user is also automatically added to a group of your choosing so that you can easily see which users have subscribed as well as provide gated content in categories only that group can see.

Terms

  • Subscription - Subscriptions are a recurring payment plan which allow you to control access to content on your community. When a subscription is created or deleted, a user is added or removed from the user group you associate with your subscription plan. A subscription is made up of a product and plans.
  • Product - A product in Stripe’s terms is what you’re selling. A product can contain one or more plans.
    • To add a description to your product, add a metadata field named “description” and use that one instead. You can use Markdown.
  • Plan - A plan contains a price, recurring cycle, and associates with a group to which your subscribers gain access.

:police_car_light: Be very careful to keep your Stripe private keys safe and secure at all times.

:warning: If you were to shut down your instance of Discourse, uninstall this plugin or your site were to go offline, Stripe will continue to bill your customers for your service until the subscription is cancelled.

Configuration

  1. Install & enable the plugin
  2. Configure Payment Gateway (Stripe)
  3. Configure Webhooks & Events in Stripe
  4. Add your Stripe keys (public, secret, webhook secret) under Admin > Plugins > Installed > Subscriptions > Settings /admin/site_settings/category/discourse_subscriptions?filter=plugin%3Adiscourse-subscriptions.
  5. Create a group for your subscribers to join via purchase
  6. Create a product and plan under Admin > Plugins > Subscriptions
  7. Profit!

Set up your Payment Gateway.

Firstly, you’ll need an account with the Stripe payment gateway. To get started, you can set up an account in test mode and see how it all works without making any real transactions or having to set up a bank account. There is no test mode toggle in the plugin; instead, be sure to use your developer keys (they begin with pk_test, sk_test)

Set up Webhooks and Events in your Stripe account

:bomb: Webhooks are required to make subscription cancellations work fully. Be sure you have them configured correctly.

Once you have an account on Stripe, you’ll need to tell Stripe your website’s address so it can notify you about certain transactions. You can enter this in your Stripe dashboard under Endpoints > URL.

Webhooks address: [your server address]/s/hooks – where [your server address] is the URL of your Discourse install.

You’ll also need to tell Stripe which events it should notify you about via the webhook URL.

Currently, Discourse Subscriptions responds to the following events:

  • customer.subscription.deleted
  • customer.subscription.updated
  • checkout.session.completed

Add the Stripe API and Webhook keys to your plugin settings

Stripe needs to be authorized to communicate with your website. To do this, it publishes a pair of private and public API keys and a signing secret for your web hooks.

To authorize webhooks, add the API keys and webhook secret from Stripe to your settings page (under Developers).

:warning: Adding production keys will make live payments. If you plan to test, be sure to switch to View test data mode and get pk_test and sk_test keys under Developers.

In your Stripe account settings, see:

Add these keys under the appropriate settings in Admin > Plugins > Installed > Subscriptions > Settings /admin/site_settings/category/discourse_subscriptions?filter=plugin%3Adiscourse-subscriptions.

Set up your User Groups in Discourse

When a user successfully subscribes to your Discourse application, after their credit card transaction has been processed, they are added to a User Group. By assigning users to a User Group, you can manage what your users have access to on your website. User groups are a core functionality of Discourse and this plugin does nothing with them except add and remove users from the group you associated with your Plan.

Create one or more products with plans.

Under Admin > Plugins > Subscriptions, click add a new Product. Once you have a product saved, you can add plans to it. Keep in mind that the pricing and billing intervals of plans cannot be changed once you create them. This is to avoid confusion around subscription management.

If you take a look at your Stripe Dashboard, you’ll see all those products and plans are listed. Discourse Subscriptions does not create them locally. They are created in Stripe.

Testing

Test with these credit card numbers:

  • 4242 4242 4242 4242
  • 4111 1111 1111 1111 (no authentication required)
  • 4000 0027 6000 3184 (authentication required)

For more test card numbers: Test card numbers | Stripe Documentation

Visit /s and enter a few test transactions.

Going Live

Once you’re ready to go live, change your API and webhook secret keys to production keys. You will need to create new products and plans in live mode.

Do be aware that if if you don’t properly configure Stripe webhooks, and recurring payments fail to process for any reason (expired credit card, etc.), users will still have access to the group . To have Stripe automatically cancel subscriptions, be sure to set your Manage failed payments settings similar to the below image and configure webhooks as described above.

Update Payment Info

Users can update their card used for individual subscriptions by visiting the billing page and clicking the edit button next to the subscription which will open up this screen:

Stripe Checkout with Stripe Pricing Tables

You can also opt to replace the Subscription Plugin product and checkout pages and instead use Stripe Checkout with Stripe Pricing Tables.

In your Stripe Dashboard:

  1. After you’ve created the products on Discourse, Go to Products > Product catalog
  2. Click on the product you’d like to include in the pricing table
  3. Click Edit product
  4. More Options and enter the following under Metadata:
    • Key: group_name
    • Value: The group’s name on Discourse (e.g., trust_level_0)
  5. Click Update product to save

:red_exclamation_mark: Make sure the group name matches the group that is selected under User_Groups on Discourse

Create your Stripe pricing table

  1. Go to Products > Pricing tables
  2. Create a new table and add the products you just created
  3. After publishing the table, copy the pricing table ID found within the embed code (it starts with prctbl_...)
  4. Paste the pricing table ID into your discourse_subscriptions_pricing_table_id and enable the subscriptions pricing table setting.
  5. Click the green checkmarks to save both settings.

Recommended step:

When setting up the Pricing Table inside of Stripe it is recommended to link the user to your site after checkout is complete otherwise they will stay on a Stripe confirmation page without a link back to your site.

Redirecting to https://<your-site>/my/billing/subscriptions is a good choice for subscriptions. For one-off payments you could link directly to https://<your-site>/my/billing/payments.

Automatic Tax Collecting

To enable Automatic Tax Collecting check the Site Setting box for discourse_subscriptions_enable_automatic_tax.

If you enable it, but you have not configured your Stripe instance properly to collect tax users may see this popup after completing the checkout process:

There is this guide for more info, but there shouldn’t be much to do since the plugin is now passing in the appropriate automatic_tax[enabled]=true parameter (step 5).

Be sure you configure your registrations (step 4) as well:

Here is an example Discourse Subscription Plugin transaction in Stripe showing that tax was automatically collected:

Settings

Name Description
discourse subscriptions enabled Enable the Discourse Subscriptions plugin.
discourse subscriptions extra nav subscribe Show the subscribe button in the primary navigation
discourse subscriptions public key Stripe Publishable Key
discourse subscriptions secret key Stripe Secret Key
discourse subscriptions webhook secret Stripe Webhook Secret
discourse subscriptions currency Default Currency Code. This can be overridden when creating a subscription plan.
discourse subscriptions campaign enabled Enables a campaign banner to promote supporting this community financially.
discourse subscriptions campaign goal The numerical goal for your support campaign (subscribers or amount raised).
discourse subscriptions campaign type Selects the type of campaign to run (subscribers or monthly amount raised).
discourse subscriptions campaign banner location Selects the location of the campaign banner (top or sidebar).
discourse subscriptions campaign banner bg image Upload a custom image to use as the background on the campaign banner.
discourse subscriptions campaign banner shadow color Selects the color of the campaign banner drop shadow.
discourse subscriptions campaign show contributors Show avatars of the most recent purchases of subscription products.
discourse subscriptions campaign product The Stripe product id to send supporters when they click the button on the campaign. If this setting is blank, supporters will be directed to the main products page.
discourse subscriptions campaign grant Grants the user a free month of subscriptions
discourse subscriptions pricing table id The Stripe pricing table id from the embed code
discourse subscriptions pricing table enabled Enables using the Stripe pricing table and replaces the existing subscribe page
discourse_subscriptions_enable_automatic_tax Toggles if sales tax is going to be collected. Requires some setup in Stripe.
discourse_subscriptions_enable_verbose_logging Enables more verbose logging to aid in debugging. Please do not leave permanently enabled in production.

:discourse2: Hosted by us? This plugin is available on our Pro, Business, and Enterprise hosting plans Subscriptions | Discourse - Civilized Discussion

Last edited by @tobiaseigen 2025-07-16T21:50:25Z

Last checked by @MarkDoerr 2024-07-11T20:25:35Z

Check documentPerform check on document:
138 curtidas

5 posts were split to a new topic: A similar object exists in test mode error

Configurar Sidebar parece nĂŁo fazer nada (Ășltimo Discourse aeb3d717dc, Ășltimo plugin cc43d32a).

1 curtida

Também estou recebendo esta mensagem de log:

Aviso de depreciação: O nome do ícone "donate" foi atualizado para "circle-dollar-to-slot". Por favor, use o novo nome em seu código. Nomes antigos serão removidos no Q2 de 2025. [deprecation id: discourse.fontawesome-6-upgrade] [info: https://meta.discourse.org/t/325349]

EDIT: Fiz um PR para isso

3 curtidas

2 posts were merged into an existing topic: "Support Us" Banner Not Updating

Hmmm
 localmente o meu aparece na barra lateral quando eu o mudo.

Se vocĂȘ o tiver na barra lateral, adicionamos esta classe CSS. VocĂȘ pode inspecionar sua pĂĄgina e procurar por subscription-campain-sidebar

Ele fica apenas no topo para vocĂȘ?

Entendi. Eu tinha a pĂĄgina de Categoria como padrĂŁo. LĂĄ nĂŁo mostra, obviamente. Mostra na lista Mais Recentes. EntĂŁo funciona bem. Obrigado!

3 curtidas

Realmente deveria aparecer na pĂĄgina de Categorias (ou outras pĂĄginas padrĂŁo), nĂŁo deveria?

1 curtida

Devido Ă s restriçÔes na China Continental, Ă© difĂ­cil para a Stripe passar na revisĂŁo. VocĂȘ poderia considerar integrar as interfaces do Alipay ou WeChat Pay?

2 curtidas

Perguntas semelhantes no passado tiveram uma resposta como “a coisa a fazer seria criar um plugin para Alipay ou WeChat Pay”. O discourse.org ganha dinheiro com aqueles que pagam pela hospedagem e nĂŁo acho que eles tenham muitos clientes empresariais que queiram Alipay ou WeChat Pay, entĂŁo vocĂȘ precisarĂĄ perguntar em Marketplace ou desenvolvĂȘ-lo vocĂȘ mesmo. Talvez vocĂȘ possa interessar Alipay ou WeChat Pay em financiar o desenvolvimento.

3 curtidas

Consegui completar os itens de 1 a 5, mas acho que sou burro ou cego. NĂŁo consigo encontrar a interface para configurar produtos e planos no meu servidor.

Ugh, esquece
 Encontrei. A Ășltima peça do quebra-cabeça Ă© que nĂŁo entendi isto:

  • Para adicionar uma descrição ao seu produto, adicione um campo de metadados chamado “description” e use esse em vez disso. VocĂȘ pode usar Markdown.

Acredito que configurei tudo corretamente. Se eu verificar a configuração para:\n~~O botĂŁo de assinatura mostrarĂĄ a tabela de preços incorporada e o Stripe Checkout serĂĄ usado.\nEntĂŁo as compras funcionam corretamente, no entanto, se eu desmarcar isso e usar a interface integrada, recebo caixas de erro como:\n\n\u003eEsperava-se um mĂ©todo de pagamento do tipo cartĂŁo, mas este PaymentIntent nĂŁo tem um mĂ©todo de pagamento e nenhum foi fornecido. Tente novamente fornecendo os parĂąmetros payment_method ou payment_method_data.\n\nou~~\n\n\u003eEste cliente nĂŁo tem uma fonte de pagamento anexada ou mĂ©todo de pagamento padrĂŁo. Considere adicionar um mĂ©todo de pagamento padrĂŁo. Para mais informaçÔes, visite https://stripe.com/docs/billing/subscriptions/payment-methods-setting#payment-method-priority.\n\nO erro principal Ă© em um plano nĂŁo recorrente, o inferior Ă© um plano recorrente.\nAlguma dica de como consertar? Eu prefiro a interface integrada.\n\nEu resolvi isso, parece que enquanto eu mexia com usuĂĄrios no ambiente de teste, o Stripe nĂŁo gostou que eu usasse o mesmo usuĂĄrio do Discourse com diferentes "usuĂĄrios de assinatura".\n\nAlĂ©m disso, o OP deve esclarecer que \n\n\u003ePara adicionar uma descrição ao seu produto, adicione um campo de metadados chamado “description” e use esse em vez disso. VocĂȘ pode usar Markdown.\n\nVĂĄ para o Painel do Stripe, clique em CatĂĄlogo de Produtos, clique em um Produto, depois clique em um Preço. É aqui que vocĂȘ encontrarĂĄ os campos de metadados onde pode adicionar uma descrição.\n\nNo entanto, isso nĂŁo pareceu funcionar para mim. Adicionei uma descrição de teste e nada mudou, nem usando a tabela do Stripe, nem o layout integrado.

6 posts foram mesclados em um tópico existente: Adicionar diferentes métodos de pagamento à assinatura do Discourse

Uma postagem foi mesclada em um tópico existente: Adicionar diferentes métodos de pagamento à assinatura do Discourse

Quando tento criar um produto, recebo um erro “500”. Estou configurando isso em um ambiente de teste. O que posso verificar para descobrir o motivo do erro do servidor?

Coisa semelhante em cupons

Existe uma entrada criada ao mesmo tempo em {YOURFORUM}/logs ?

2 curtidas

Uau.. não sabia que essa pågina existia. Mostra chave de API invålida. Coloquei um lixo qualquer para a chave secreta para avançar e configurar os pacotes de assinatura por agora e voltar para as chaves mais tarde quando estiver pronto para testar.

1 curtida

Consegui configurar o plugin sem problemas, mas entĂŁo percebi que este plugin sĂł permite assinaturas recorrentes. NĂŁo assinaturas Ășnicas que expiram apĂłs o perĂ­odo definido.

Como cobrar X valor por 30 dias. ApĂłs 30 dias, o usuĂĄrio Ă© removido do grupo premium. Eles podem comprĂĄ-lo novamente se quiserem. Normalmente, ofereço assinaturas de 1 mĂȘs, 3 meses e 12 meses.

O Stripe exige que eu me registre como uma empresa para poder oferecer suporte a pagamentos recorrentes. Estou recebendo pagamentos Ășnicos no XenForo e o recurso nativo do XenForo lida com o vencimento da assinatura e a remoção da associação ao grupo.

Isso destrĂłi completamente meu plano de migrar para o Discourse em um mĂȘs. :cry:

Eu tenho uma solução. Posso ajudĂĄ-lo a criar uma ação do GitHub que extrairĂĄ dados do explorador de dados, incluindo o nome de usuĂĄrio e o ID do grupo dos quais removĂȘ-los e, em seguida, alterarĂĄ seu grupo de acordo.

Estou fazendo isso para um cliente que estĂĄ migrando para o Discourse e tem um campo personalizado com datas. Portanto, precisamos mover os usuĂĄrios para um grupo “expirando-em-breve” para dar-lhes um banner e, em seguida, para outro para removĂȘ-los do grupo pago quando o tempo acabar.

Se vocĂȘ tiver um orçamento, pode entrar em contato comigo ou perguntar em Marketplace. Estou planejando um post de blog sobre isso com um exemplo de propĂłsito geral, se eu tiver um tempo livre.

6 curtidas

Olå, as assinaturas funcionaram bem até o momento em que o retorno de chamada do Stripe chegou. Estou usando a Tabela de Preços do Stripe.

Posso ver que a assinatura foi registrada com sucesso na pĂĄgina admin/plugins/discourse-subscriptions/subscriptions.

No entanto, o usuĂĄrio nĂŁo foi movido para o grupo de usuĂĄrios necessĂĄrio.

Configurei o produto com o mesmo Nome do Produto do Stripe e também criei um plano de preços com o grupo selecionado. Mantive o preço como zero no plano de preços, pois presumo que seja irrelevante para a configuração da tabela de preços do Stripe.

O que estou perdendo?