DevProduct purchase failing when Players only have enough Robux to purchase the DevProduct one time (1x)

Players reportedly stated that when they attempted to make a DevProduct purchase while they ONLY had enough Robux to purchase the DevProduct one time, it would state:

“Your purchase failed because something went wrong. Your account has not been charged. Please try again later.”

However, Players STILL lose their Robux, and the purchase will sometimes not show up in my group’s transactions list or in the Player’s transaction history.

To explain further, let’s say hypothetically a DevProduct costs 150 Robux and a Player has less than 300 Robux (Less than 2x the price of the DevProduct), this issue will sometimes happen. This issue does not happen every time, but it occurs to the point where I have identified this as a repeated ongoing issue, and I also had this bug happen to me when I was testing DevProduct purchases in my own game. For example, Players may have lots of Robux to start out with, purchase the DevProduct listed at 150 Robux several times in a row successfully, but then when they only have enough Robux to purchase the DevProduct one time, this bug will happen.

If this was an issue that is attributed to me poorly scripting my transactions, then I apologize and I will work to fix the issue. I have reviewed my transactions script extensively to ensure that every DevProduct purchase is handled as efficiently as I can make it given my scripting knowledge. I used the CreatorHub’s DevProduct transaction page as a template when I was creating my transactions script.

I have attached details regarding my transactions script and the way purchases are handled.

A screenshot of my receipt handler, the variable “FirePurchaseCallbackEvent” is a bindable event that handles tasks like creating a new Character whenever Players purchase a new Character Slot. I did my best to ensure everything is scripted as safely as possible to create as few conditions that would error a purchase.

Here is a screenshot of a function that gets called when a Player purchases a DevProduct, intended to grant the Player the rewards of said DevProduct. My game uses ProfileService to store Player data. Assuming the Player is present within the server, and their Profile is loaded, the rewards will be granted.

Because this bug only seems to occur when Players only have enough Robux to purchase the DevProduct 1 time, and in the examples I have seen of this bug Players make several purchases that grant the rewards successfully, it leads me to believe it is LIKELY not this script that is malfunctioning. If this is not the case, I would appreciate guidance to resolve the issue so that I can make my game better for my community.

I apologize for any inconvenience this may cause and look forward to some feedback on the matter. Thank you.

Here is a link to a clip of this occuring to me.

As you can see, the purchase happens successfully several times in a row, and then it throws this error when I have just enough Robux to make 1 more purchase.

Clip

1 Like

Hi! I can help you look into this.
Can I get the following info?

  • A link to the roblox account used to make the purchases in the vid
  • A link to the roblox game where this is happening
  • A screenshot of your recent transaction history during testing
    Thanks!
1 Like

Thank you for reaching out and willing to help with this matter!

Here is a link to the Roblox account from the video (My account):

Here is a screenshot of my transactions. Circled are the transactions that occured during the video.

Here is a link to the game:

Also, the issue is only happening (and applicable) in the main starting place.

Hi Bane,

I looked into this and it turns out that there are no issues with the purchasing - it is working as intended.

What is broken is the “Robux balance after purchase” display, which is lagging. As you can see in the vid, after the first purchase, it still shows 429 robux, even though it already showed 429 before your first purchase. So for your last purchase, even though it says you will have 129 robux after purchase, in reality you only had 129 robux left which is why the purchase didn’t succeed.

Thank you for showing us this, we will work on fixing that display. In the meantime, don’t worry, no robux was lost.

1 Like

I appreciate you looking into this for me and determining what the root cause was. I didn’t realize that was the case, thank you for your time and I apologize for the inconvenience. I will be sure to look for this in the future and let my community know.

Thank you again!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.