On this page
Make the exchange understandableCompare the funding modelsPlace the paywall at an understandable boundaryDistinguish tokens, credits and the person’s taskBYOK changes billing and trustTest understanding, not just conversionInterface optionsSources and limits8-minute guide · Editorial guidance
Fund the product without exploiting trust
Paywalls, subscriptions, credits and bring-your-own-key choices.
A useful starting point
Define the access promise first, then make price, limits and leaving understandable.
Ask: What is being paid for—and what happens when payment stops?
Make the exchange understandable
Good content, licensed editions, reliable infrastructure, safeguarding and human work cost money. Charging can support those commitments. The design question is whether the exchange is clear, proportionate and compatible with the relationship the app invites.
Start with an access policy: what remains usable without payment, which costs are recurring, and what people retain when they leave. Never imply that a paid tier buys greater spiritual worth, a more faithful prayer or guaranteed divine guidance.
Compare the funding models
Scroll the comparison sideways to see all options.
| Model | Useful when | Design obligation |
|---|---|---|
| Donations or sponsorship | A community funds broad access | Explain the funding purpose. Keep giving voluntary and distinguish donor recognition from spiritual standing. |
| One-time purchase | A defined resource or edition has lasting value | State licence, download rights and ongoing service limits. Avoid a “lifetime” promise that cannot be sustained. |
| Subscription | Ongoing content, service or operating costs create recurring value | Show billing period, renewal, access limits and cancellation. Annual totals must be as understandable as monthly equivalents. |
| Credits or metered use | Expensive generation varies substantially by use | Define the unit, estimate the task cost, explain expiry and failures, and prevent unapproved overage. |
| Bring your own API key | An informed user wants to connect their own provider account | Explain provider billing, credentials, data recipients, limits and fallback. Offer a simpler alternative where feasible. |
| Church or organisation licence | A group pays for members’ access | State who can see participation and what happens on leaving. Funding must not grant leaders access to private chats. |
Place the paywall at an understandable boundary
- Let the person understand the feature and price before collecting intimate input or beginning a paid task.
- Present included capabilities, recurring total, trial end, renewal and any minimum commitment. Show a real decline or free route if one exists.
- Confirm the selected plan in the platform purchase flow; handle pending payment, restored purchases and an existing subscription.
- Show entitlement and the next billing date in settings, with a direct management route.
- On cancellation or expiry, explain when access ends and which saved work remains readable or exportable under its licence.
Keep emergency contacts and basic safety information reachable when credits run out. Do not present a conversion offer as the response to suicidal distress or an abuse disclosure. This is an editorial service boundary, not a claim that unlimited AI use must be free.
The FTC’s 2022 dark-pattern report summary identifies hidden terms, obstructive cancellation and manipulative data choices. It is a design reference, not a statement that a particular later subscription rule is currently in force. Apple’s subscription guidance provides platform-specific purchase and management expectations.
Distinguish tokens, credits and the person’s task
Model tokens measure processing units; product credits are a pricing abstraction. Neither inherently corresponds to one verse, one answer or one minute of audio. Explain your conversion and its uncertainty. Hidden history, tools and retries can change cost.
Illustrative flow · example units, not market prices
Create a 5-minute audio reflection
Estimated 2–4 credits. Maximum 4 credits for this request. 12 available.
Review sources → Confirm generation → Show actual charge and remaining balance.
Implement the promised cap; a warning alone is not enforcement. Define partial output, failed generation, user cancellation, retries, refunds and reservation release. Disclose expiry, rollover, top-up price and auto-recharge separately. If estimates cannot be bounded, offer a smaller predictable task.
BYOK changes billing and trust
Here BYOK means a provider API credential, not an encryption key. Show whether requests go directly to the provider or through your server or a router, who can access content, where credentials are held, and how to revoke them. Keep keys out of analytics, browser bundles, URLs and ordinary logs. A key does not make a conversation private or remove your responsibilities.
OpenRouter documents provider-key routing, data-policy controls and shared-capacity fallback. Some fallback paths can spend router credits. This is one provider’s implementation, not a universal BYOK contract. Make cost-bearing fallback an explicit choice and test expired keys, rate limits, unavailable models and exhausted budgets. Do not silently switch the payer or data destination.
Test understanding, not just conversion
Before purchase, ask someone to explain what they will pay today and later, what is included and how to leave. Then test a failed generation, exhausted credits and cancellation. Track billing confusion, refunds and support burden alongside revenue. Research affordability and access with intended audiences; do not infer generosity or faith from spending.
Decision to record: which revenue opportunity would you decline because it exploits the trust this product asks for?
Sources, review scope and limits
- Auto-renewable subscriptionsSelected purchase, management and marketing-notification guidance reviewed · Apple platform guidance; not universal law. Verify storefront-specific rules before shipping.
- FTC report summary: dark patterns that trick and trap consumersOfficial report summary reviewed · Historical report summary, not a claim about the current validity of later subscription rules.
- Bring your own provider API keysRouting, fallback and data-policy sections reviewed · One provider implementation; pricing and defaults can change. BYOK does not itself guarantee privacy.
- Digital Spiritual Formation: The Aperto Vision · selected Draft 4 reviewSelected sections on reading, engagement, multimodal and communal formation, incentives and honest assessment reviewed 5 October 2026 · Not an effectiveness study. Full bibliography and manuscript are not published or comprehensively reviewed here.
Take this into a product decision
Write down the intended benefit, the chosen option, who carries the burden, and what evidence would change your mind.
Use the decision worksheet · Explore another guide