SEELE AIStart creating

Nonprofit and Cause-Game Teams · Player-first Koin purchase UX

Transparent Koin Pricing for Nonprofit and Cause-Game Teams

Design one optional Koin item around the real needs of nonprofit and cause-game teams. This guide applies transparent Koin pricing to the offer, confirmation, cancellation, recovery, and delivered result.

Create this game flow
Transparent Koin Pricing for Nonprofit and Cause-Game Teams visual reference
Visual reference only. Your generated game follows the prompt you choose.

Start with what nonprofit and cause-game teams need

Audience need

The experience must avoid donation claims and clearly separate virtual item value from charitable giving.

Design principle

Show the item, exact Koin amount, balance effect, duration, and ownership result prior to confirming.

Small first scope

Use one item and one Koin price so players can evaluate the complete choice without navigating a large shop.

Transparent Koin Pricing in practice

Offer moment

Choose a calm point where nonprofit and cause-game teams understand the game context and can decline without interrupting active play.

Offer card

Show the item, benefit, duration or quantity, full price in Koin, Koin balance now, confirm, and cancel in plain language.

Safe recovery

After a cancelled choice or an insufficient balance, preserve progress and return nonprofit and cause-game teams to an understandable game state.

Visible delivery

Following a successful result, show ownership, equipped state, unlocked content, or remaining quantity where the item will be used.

Apply transparent Koin pricing throughout the flow

Do not blur virtual value with charitable giving

Describe only the Koin item the player receives and never imply that buying it creates a donation, tax benefit, fundraising total, or verified social impact. Any real cause relationship needs separate evidence, legal review, reporting, and transparent ownership.

Run a price-comprehension check

Give a new player the offer without explanation and ask them to name the selected item, full Koin amount, available balance, expected balance afterward, quantity or duration, and ownership rule. Let them decline, then repeat with insufficient Koin and a successful choice. Review every place the value appears and remove crossed-out amounts, vague premium labels, unsupported real-currency comparisons, or urgency that distracts from the final cost. The wording on the preview, confirmation, success message, and owned view must describe the same thing. Reopen the game and verify that the balance and ownership shown to the player still match the one transaction they approved.

Keep price and balance together

Place the exact Koin amount beside the Koin balance now and show the expected remaining balance before the player confirms. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.

Explain duration and ownership

State whether the item is permanent, consumed on use, limited by quantity, or active for a fixed time. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.

Remove misleading price signals

Avoid fake urgency, crossed-out prices, unsupported currency comparisons, and labels that hide the final Koin amount. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.

Design the flow in five steps

  1. 1. Start with the audience requirement

    Write this into the prompt before the item description: Avoid donation claims and clearly separate virtual item value from charitable giving.

    Result: A clear design constraint

  2. 2. Apply transparent Koin pricing

    Show the item, exact Koin amount, balance effect, duration, and ownership result before the player confirms. Carry the same principle through confirmation and delivery.

    Result: A consistent player experience

  3. 3. Define one non-required item

    Name the benefit, duration or quantity, ownership rule, clearly stated Koin cost, and delivered result.

    Result: An understandable offer

  4. 4. Playtest with nonprofit and cause-game teams

    Try confirmation, cancellation, not enough Koin, repeated input, interruption, delivery, and reload without coaching.

    Result: Audience-specific feedback

  5. 5. Revise the unclear moment

    Change one prompt instruction, regenerate, and compare whether players understand the choice more quickly.

    Result: A focused second version

Generate it in SEELE

Prompt 1

Create a browser-playable game purchase-flow prototype for nonprofit and cause-game teams. Optimize for transparent Koin pricing: show the item, exact Koin amount, balance effect, duration, and ownership result prior to confirming. Apply this audience requirement: avoid donation claims and clearly separate virtual item value from charitable giving. Use one item the player may decline priced directly in Koin with preview, explicit confirm and cancel, insufficient-balance feedback, success, and visible delivery. Do not include subscriptions, revenue reporting, payment-provider UI, or guaranteed outcomes.

Prompt 2

Keep the item optional. Show its full price in Koin, Koin balance now, confirm, cancel, low-balance, success, visible delivery, and reload states.

Playtest with nonprofit and cause-game teams

Before this flow goes live

Frequently asked questions

Why does transparent Koin pricing matter for nonprofit and cause-game teams?

It makes the choice easier to understand while respecting this audience's needs.

Is this a subscription?

No. The player spends Koin directly on one named item or unlock.

What happens if the player cancels?

Return to the same game state without spending Koin or delivering the item.

What if the Koin balance is too low?

Explain the shortage, preserve progress, and do not deliver the item.

Does this include payment or revenue reports?

No. It covers the player-facing purchase experience, not financial reporting.

Is the prototype ready for a native store?

No. Identity, persistence, security, refunds, native APIs, policy, and accessibility still need production work.

Build a transparent Koin pricing prototype

Open the complete prompt in SEELE, adjust the item and Koin price, then generate a playable version you can test.

Open this prompt in Workspace