Third party enablement of game features

A device comprising:

• one or more processors;
• and
• a client application hosted on the device and executed by the one or more processors, the client application associated with a first enterprise, the client application configured to:
• receive, via a network from an award provider service hosted on a server device and different from the device, data defining one or more game features corresponding to a game application associated with a second enterprise, the data including, for each of the one or more game features, feature enablement criteria, the feature enablement criteria including at least one of:
• the device hosting the client application is at a location of the first enterprise,
• the client application automatically detects a qualifying interaction with the first enterprise represented by the client application;
• monitor for satisfaction of the feature enablement criteria;
• automatically detect that the feature enablement criteria corresponding to the game feature has been satisfied;
• and
• in response to the automatic detection that the feature enablement criteria corresponding to the game feature has been satisfied, communicate, via the network to the award provider service, a first indicator indicating that the feature enablement criteria has been satisfied to cause the award provider service to automatically enable via the network the game feature for the game application.

The device of claim 20, wherein the client application is further configured to perform at least one of:

• receive, from the game application, the second identifier;
• receive, from the award provider service, the second identifier and an enrollment identifier, wherein the first enrollment request message includes at least the enrollment identifier, the first identifier, and the second identifier;
• or
• receive, from the award provider service, the enrollment identifier, wherein the second enrollment request message includes the enrollment identifier and the first identifier.