How Piggy Bank progress syncs between the game and the Hub

Piggy Bank progress shown in the Hub is driven by the player attributes Aghanim receives during player.verify. If a player keeps both the game and the Hub open, the Hub may continue showing the previously verified value until the next verification happens.

Why progress may not refresh immediately in the Hub

The Hub updates Piggy Bank progress when player.verify runs again and your backend returns refreshed player attributes such as PiggyBankBalance.

In practice, that means the Hub value can refresh in these common cases:

• when the player logs back into the game or logs out and back in
• during background re-verification, which happens every 6 hours
• before and after a purchase, if a webhook store is configured

If QA sees progress update only after closing and reopening the Hub tab, that usually indicates the player attributes were refreshed on the next player.verify call rather than on a browser refresh alone.

Why progress can reset after a Piggy Bank purchase

After a Piggy Bank purchase, the player's PiggyBankBalance attribute may be reset. When that happens, the Piggy Bank offer can disappear from the Hub until the next player.verify updates the player's attributes again.

This reset behavior is expected if using the Piggy Bank consumes the accumulated balance.

How to force the Hub to reflect a new Piggy Bank balance

If the player has accumulated Piggy Bank value again and you need the Hub to reflect it without waiting for the next normal verification cycle, send an S2S Update Player request to update the player's PiggyBankBalance attribute.

Using multiple Piggy Banks for multi-step tier flows

If your in-game implementation uses multiple sequential Piggy Bank stages, you can model this in the Hub with separate Piggy Bank offers and use a player attribute such as PiggyBankTier for segmentation to determine which offer should be shown.

When doing this, make sure the same balance and tier logic is kept in sync between the game and the Hub so players see the same current stage in both places.

What to check if a Hub purchase does not advance the in-game Piggy Bank tier

If purchasing a Piggy Bank tier in the Hub updates the Hub but does not move the player to the next tier in-game, the most likely cause is that the Hub purchase is not being processed by the game server as part of the game's own Piggy Bank flow.

In this setup, the game backend should treat the Hub purchase as part of the same source-of-truth progression used by the in-game Piggy Bank. Otherwise, the Hub can move to the next segmented offer while the in-game Piggy Bank remains at the previous tier's max threshold.

For sequential Piggy Bank tiers, verify that:

• the Hub purchase reaches the game server or fulfillment logic that advances the Piggy Bank stage
• the backend updates the attributes used for Piggy Bank state, such as PiggyBankBalance and PiggyBankTier
• the next player.verify response returns the updated values so both the Hub and the game stay aligned

Implementation notes

• Return the latest Piggy Bank-related custom attributes in the player.verify response.
• Declare custom attributes such as PiggyBankBalance and PiggyBankTier in Game → Player attributes.
• If store visibility depends on current player state, ensure your store setup triggers verification at the appropriate points.