Guideline 3.1.3(d) vs. EU External Purchase Link Entitlement — real-time one-to-many servic

Hello,

We are the developers of UbiFit Go, a fitness marketplace app (Portugal/EU). We offer live, real-time group fitness classes via video call, purchased as a credit pack exclusively on our external website (Stripe), and consumed in-app via a native button — with no links, buttons, or WebViews pointing to our website inside the app (only static informational text, e.g. "manage your credits from your account on our website").

Guideline 3.1.3(d) states that "one-to-few and one-to-many real-time services must use in-app purchase." We would like to confirm:

Does this static-text-only pattern (no in-app link of any kind) still fall under 3.1.3(d), or is it exempt because there is no purchase flow or redirection happening inside the app at all? If it does fall under 3.1.3(d), does the EU External Purchase Link Entitlement (per the Digital Markets Act) apply to real-time one-to-many services such as live group fitness classes, or is that entitlement limited to non-real-time digital goods?

We want to ensure full compliance before implementing this feature. Thank you.

Guideline 3.1.3(d) vs. EU External Purchase Link Entitlement — real-time one-to-many servic
 
 
Q