Desktop Web · Game Designer · IAP Purchase Confirmation guide
Use a browser-playable Desktop Web context to produce an annotated player-flow specification. Own screen hierarchy, offer timing, readable choices, and visible feedback; treat the result as a workflow prototype, not proof that native billing is connected.
Create this game flow
Focused keyword and player case
Prototype a confirmation panel that keeps the item, exact Koin price, balance, Confirm, and Cancel visible together. The game designer reviews consent, duplicate input, low balance, and safe cancellation and delivers an annotated player-flow specification. Acceptance means a player can preview the offer, decline it, recover from low balance, and explain the delivered result without coaching.
Use the focused IAP Purchase Confirmation hub for an authentic screenshot, direct playable result, and the complete purchase-state checklist. Gameplay evidence supports placement testing; it does not prove a live transaction.
Start with player motivation and the core loop. The item should support a goal players already understand rather than remove deliberately created frustration.
Design for the input, layout, interruption, and return behavior players expect from desktop web games.
Desktop browser purchases remain Koin flows inside the supported experience.
Show one non-required item, its preview, specific Koin amount, current Koin balance, and ownership rule in a layout suited to desktop web games.
Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Keep each change visible to the player rather than hiding it in technical state.
Make cancellation, not enough Koin, pending, interrupted delivery, and reload visually distinct, with a safe next action.
Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership. Use the prototype to resolve player-facing questions before creating platform integration tasks.
For a game designer, this purchase confirmation prototype should make every player action and player-visible outcome easy to evaluate. Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership. Check tab order, focus indicators, mouse targets, escape behavior, and the return to game controls. Confirmation must never borrow an input that also performs a high-frequency gameplay action.
Keep the item, Koin amount, balance effect, and actions together on common desktop widths. Avoid pushing a player cancellation off screen simply because the game canvas occupies a large area.
Resize, move between displays, zoom, refresh, and restore a background tab. The interaction should preserve the selected item and resolve pending or delivered states without another grant.
Run the game without opening the purchase choice, then run it with the item. Compare pacing, motivation, difficulty, and recovery so the offer supports play instead of repairing frustration that was added deliberately.
Describe what changes on screen, how long it lasts, where it appears, and what remains available without it. Replace value labels such as better or premium with rules a player can observe.
Check what the player was doing immediately before the offer and where cancel returns them. The item should arrive after enough context to understand it, but never during a time-critical or emotionally pressured action.
The confirmation should repeat the selected item, exact Koin amount, available Koin balance, remaining balance, and ownership rule without introducing a different offer. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
Use distinct actions with clear labels and enough spacing for the target input method. Returning to the game should never spend Koin. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
After confirmation, show a pending state and disable repeated input until the result is known. A slow response should not create duplicate grants. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
Choose the input and screen behavior for desktop web games. State the platform limit beside the prototype brief.
Result: An honest scope
Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Describe the player action and visible response at each point.
Result: A clear purchase confirmation sequence
Show the item, exact price, balance, confirm, cancel, pending, success, and delivery without payment-provider screens.
Result: A complete player journey
Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership.
Result: Game designer focus
Play cancellation and a full session without purchase. Check timing, value, competitive impact, and whether the item matches the delivered result. Repeat the test after interruption and reload.
Result: A stable prototype
Create keyboard-and-mouse browser play for a game designer. Focus the IAP prototype on show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Use a direct Koin item transaction with preview, exact price, confirmation, cancel, insufficient balance, success, delivery, and reload behavior. The game designer must be able to connect the offer to the core loop and player motivation. Do not add subscriptions, payment-provider UI, revenue analytics, or native platform claims. State this boundary: Desktop browser purchases remain Koin flows inside the supported experience.
Keep the item optional. Show its specific Koin amount, current Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Own screen hierarchy, offer timing, readable choices, and visible feedback. Coordinate adjacent work, but keep the page's acceptance artifact specific to this role.
Deliver an annotated player-flow specification that records consent, duplicate input, low balance, and safe cancellation, named owners, failure states, and the next production verification step.
No. Production release still requires authenticated records, security, refunds, platform compliance, monitoring, and support procedures.
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