Edit: Edited this after the SUG on 5/13 to add some notes, and fix up a bit. I originally wrote this in a rush since it was brought up in the Skill Gaming User Group meeting prior to the SUG meeting.
Currently, when someone pays an object in Second Life, the name of the object that is being paid is sent by the Viewer to the server. This allows incorrect entries being entered into the transaction logs of residents, most especially causing issues in the Second Life Skill Gaming space where we are bound by policy to name objects certain ways (such as object names starting with [slgaming]).
In the transaction log of some people, the object name is either recorded as a blank, or the object DESCRIPTION is used as the NAME of the object being paid. This is because of bad implementation of whatever viewer they are using. Both official SL viewer, and firestorm put the object name in this server call. Some bot viewers, or other viewers do not.
While this could be seen as a viewer issue, this is ripe for exploitation as well as just bad design. The server itself should know that an agent is paying an object, and said object should record itself properly in the transaction description which will eventually show on the website. The server works properly when an object pays an agent, but not the other way around. The viewer leaving a comment should be preserved for resident to resident transactions, but the server should record the object name as the comment when an agent pays an object. The viewer should not be able to force a comment of its choosing with an agent to object payment.
I am classifying this as a bug, because multiple times throughout the years, Skill Gaming operators have been alerted by Linden Lab that our "transaction descriptions" are out of compliance, but this isn't anything we can control and isn't our fault. We've tried to get this addressed to no avail. I made a proposal on a llTransferLindenDollarsComment type command (https://github.com/secondlife/jira-archive/issues/8316) but was never implemented but even if it was, it would only apply to object to agent payments, which are already recorded properly by the server. The issue is in play only on agent to object payments.