Summary
MarketplaceService:GetRobloxSubscriptionDetailsAsync() appears to occasionally return incorrect attribution data, specifically the IsOriginExperience field.
We have recently seen a significant increase in player reports that they did not receive an in-game reward which is only granted if the API reports that the subscription originated from our experience.
Expected Behavior
When a player purchases a Roblox Subscription through our experience using the in-game purchase flow, GetRobloxSubscriptionDetailsAsync() should return:
IsSubscribed = trueIsOriginExperience = true
This is the documented behavior of the API.
Actual Behavior
Recently, we’ve received a much higher number of reports from players claiming they purchased the subscription through the in-game button but did not receive the reward.
Immediately after one player’s purchase (30mins after he said he has purchased it, it is not verified that it was actually purchased through the game), I printed the result of GetRobloxSubscriptionDetailsAsync(). The returned dictionary only contained:
{
IsSubscribed = true
}
IsOriginExperience was missing entirely, causing our system to treat the purchase as if it had not originated from our experience.
Every affected player has stated that they purchased through the in-game purchase prompt, which should result in IsOriginExperience = true.
I cannot independently verify that every report is accurate, but the volume of reports has increased dramatically over the past few days/weeks compared to what we’ve historically seen.
Additional Information
This is not the first time we’ve encountered this issue. We’ve occasionally received similar reports since the Roblox Plus rollout, suggesting the API may have had intermittent reliability issues before.
However, the frequency has increased significantly recently, which makes me believe there may have been a regression or backend issue affecting GetRobloxSubscriptionDetailsAsync().
Game this was experienced in: Roanoke, VA Driving RP | Play on Roblox
