Why store.get can return an empty item list for players with Web Checkout

If a player has Web Checkout enabled, it is expected that the in-game Web Shop button is unavailable for that player.

In this case, the player may still be able to open or authorize into the hub through other entry points, but the store payload can be returned as an empty list:

{
  "items": []
}

This behavior is considered expected for players on the Web Checkout flow, even if it may look confusing from the client side.

What this means

• Empty items in store.get does not always indicate a webhook or auth failure.
• If the player is on Web Checkout, the in-game Web Shop is not available to them.
• The server may still authorize and accept the player normally.
• A player can still end up in the hub through another path, for example via a web interface.

How to interpret support cases

• If support sees store.get returning {"items": []} for a specific player, first check whether that player is using Web Checkout.
• If Web Checkout is enabled, the empty in-hub store is expected behavior.
• If Web Checkout is not enabled, continue investigating the store configuration or webhook response logic.

Notes

This behavior is currently expected, although it may not be ideal from a UX perspective because the player can still appear to enter the hub while seeing an empty store.