Kent Briggs wrote: Sun Apr 26, 2026 8:49 pm
alf493023 wrote: Sun Apr 26, 2026 5:47 pm
Just to re-iterate the issue, your system does not allow you to rake a table balance, only a non-table balance.
I would never allow an API call to mess with a player's live table balance.
In my opinion, the right way to look at this is to mirror what traditional card rooms do (which is what other poker software does). So we aren't removing funds from a live balance in the middle of a hand. Instead, we debit balances from the table as a whole.
So for example, at a live poker table that has no rake but does time, every period of time, play pauses for a short moment as the dealer announces time is required to be paid. Every player tosses the dealer the timed amount from their stack and then play continues. This is standard for timed collection across the world and is extremely common. As in, timed collection occurs outside of a hand in play and this is very standard. The same functionality is mirrored in other poker software as well.
I am asking that you support what is already a standard across the poker industry. This should be a fairly easy addition as well. Functionally, it would work as follows:
1) Table-based timed play. The table play is paused for a few seconds while timed pay is done and then table play continues. This would be a setting specific to a ring game poker table and not done as an API trigger.
2) Player-specific timed play. This is the ability to collect time from a specific player as done by an API trigger. The API trigger would either a) Remove timed play from a player on a table immediately if they are not in a hand. If successful, the API responds as such, or b) Queue for time deduction when their hand completes. If the queue for action is created then the API responds saying that timed is queued, of which the completion of the timed deduction is notified via standard callback/webhook, which your software already supports.
Now with regards to your comment about an API waiting to perform an action, that is not the industry standard way for APIs which perform non-immediate functionality. Instead, the API is used to trigger a queue entry, and the completion of the queue entry is notified via the callback/webhook. This is what I mentioned above and this is generally accepted as the industry standard for these types of notifications.
The setting of the timed collection (dollar amount, interval, enable/disable on cash/ring game tables, etc) is a pretty minor detail to configure.
Please let me know if there is anything I can help with this. I've been around the block so I can provide feedback as needed.
Thanks!