One Merchant hub, several clear roles
The Merchant became one focused destination with General, Traveling, Legendary, Cosmetics and Gold sections. Equipment, consumables and portrait cosmetics remain part of the in-game Gold economy, while the Gold section is reserved for the optional Google Play packs.
The General Merchant can stock a Minor Energy Potion, an Adventurer's Draught and a Fleetfoot Tonic. The potion restores a limited amount of Adventure Energy, while the timed items can improve the next Adventure's success chance or shorten its duration.
Consumables with narrow jobs
Purchased consumables remain in a persisted Inventory pouch until the player chooses to use them. Reusing a timed effect refreshes its duration instead of stacking it, and an Adventure records the active effect when it begins so an item cannot rewrite a journey already underway.
Optional Gold, verified before it is granted
Ascendant's Android internal build offers four optional Gold pack sizes through Google Play. The app displays Google's localised price and only grants Gold after the purchase token has been checked by a server-side verifier.
The verification flow is designed to reject replayed or invalid purchases and to avoid adding the same verified grant twice on one installation. Purchase credentials and raw tokens are not stored in the public game repository.
What Gold cannot buy
At this milestone, Gold can be used inside the existing economy for equipment, consumables and permanently owned portrait cosmetics. It cannot purchase Quest completion, XP, character levels or attributes.
That boundary matters because Ascendant is not meant to replace effort with a payment. Real-life Quests remain the source of meaningful character growth; optional Gold changes what can be bought from Merchants, not what the player has accomplished.
Still an internal-testing system
The purchase backend and automated safeguards were verified before the first internal release was accepted by Google Play. Licence-tester purchase, cancellation and interrupted-verification journeys were still listed for hands-on device testing at this milestone, so this work should be read as an alpha implementation rather than a finished public launch.