Summary: How 7Mind subscriptions work since the 2026-09-14 migration: store in-app purchases in the app, Adyen on the web through Gymondo’s checkout, Gymondo’s subscription service as the source of truth, and legacy Chargebee and FastSpring subscriptions carried along as shadow records. Sources: Gymondo-git (function-payment PRs #27, #28, #32; function-subscription cmd/function-subscription/main.go; function-app-store-receipt; terraform-workspace-service-gateway productsConfig.json; function-sevenmind-legacy-gateway README and internal/billingperiod); sevenmind/7mind-mobile-apps-monorepo (MIND-663, lib/features/core/domain/monetization/); Notion “Platform unification Q&A”, “Migration Bug Status, Summary for CTO (23 Sep 2026)”; Slack 7m_product-team-public, 7nxt_marketing Last updated: 2026-10-23


The short version

ChannelBeforeNow
iOS / Android appChargebee SDK on device, plus store purchasesStore in-app purchases only (in_app_purchase plugin, app 4.0.0, MIND-663). Receipts go to Gymondo function-app-store-receipt
WebChargebee hosted checkout (and FastSpring before that)Adyen through frontend-public-pages on app.7mind.de
Insurance, B2B, partnersChargebee gift SKUs and Elixir activation codeGymondo vouchers redeemed by function-sevenmind-legacy-gateway; access granted as roles
Telco (Mondia)Elixir monetization domainGateway serves the Mondia webhooks; function-partner and service-event-broker handle lifecycle
Source of truthElixir monetization databaseGymondo service-subscription (MySQL)

Legacy subscriptions

Chargebee is retired for new purchases (“not used anymore since the migration”, 2026-09-29). Existing subscribers were not forced to re-subscribe:

  • function-payment ingests Chargebee webhooks as CHARGEBEE_SHADOW transactions and FastSpring webhooks as FASTSPRING_SHADOW, both with vendor SEVENMIND. About 5,800 FastSpring subscriptions were carried over.
  • function-subscription mirrors cancellations back to Chargebee and FastSpring, so a user cancelling in 7Mind stops the renewal at the old provider.
  • The gateway derives the billing period and display name from the old SKU (internal/billingperiod).

At cutover, about 3.6k Chargebee subscribers temporarily lost access; 4.4k active and 600 cancelled subscriptions were repaired afterwards.

Products and SKUs

  • App store products for 7Mind are served from Gymondo (/api/v3/sevenmind/products/{platform}, answered by the product-change-v3 Lambda). A SKU is offered only when it is in the Contentful tier card, in the Lambda’s productsConfig.json allow-list and in the product catalog synced from the Contentful Product. Receipts sync through /api/v4/sevenmind/receipts/google/sync and /api/v1/sevenmind/receipts/transactions. See app-subscription-products for the model and adding-an-app-store-sku for the setup steps.
  • New web SKUs are Contentful Product entries with payment service provider ADYEN and type RECURRING. Vouchers and campaigns are created in the Gymondo Back Office, with campaign titles following the 7NXT naming convention XX-[GRP]-7M-.... Nobody creates SKUs in Chargebee anymore. See adding-a-web-sku for the steps, including insurance partners and prevention courses.
  • Gift vouchers (buying 7Mind for someone else) were dropped as a feature with Chargebee. The website’s gift purchase pages were retired on 2026-09-24.
  • The free trial endpoint on the gateway answers 200 but grants nothing; the free trial flag is only set for web subscriptions (MIND-816).

Entitlement

Premium access is computed per vendor from subscription plans and roles in Gymondo (function-user). Content packages from the old 7Mind world were mapped to Gymondo roles. Insurance activations do not create purchases: they redeem a voucher, the grant arrives asynchronously (about ten seconds later), and the gateway reads entitlement from roles and package slugs. See function-sevenmind-legacy-gateway for the per-partner flows.

What agents should know

  • Do not add Chargebee code anywhere. The chargebee_flutter SDK is gone from the app and the Chargebee checkout is gone from the web.
  • Subscription changes in the Gymondo services are multi-vendor. Check the SEVENMIND vendor branch and test that Gymondo and Buddyfit behaviour does not change.
  • Reporting on subscriptions now happens in Tableau (7NXT) and the 7nxt_subscriptions bot, not in Chargebee or Looker.