Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
1.1Credit meter triggers purchase
What ifWhat if a low-balance event from the credit meter triggers an automatic card purchase?
Claim language“in response to user input”
The controller monitors the credit meter and requests a preset top-up when the balance falls below a configured threshold and automatic top-up is enabled. The processor checks the requested amount against the spending limit before submitting the payment for authorization.
1.3Counters track window spending
What ifWhat if the processor checks spending against a running total for each token and spending window?
Claim language“a database of transaction records”
A counter service stores one aggregate amount per token and calendar day, with the day boundary set to a configured time zone. The service atomically reserves each requested amount against that day's total and releases the reservation if payment fails.
1.5Speaker announces limit result
What ifWhat if the processor reports the spending-limit result through a speaker?
Claim language“via a display”
The processor selects one of two prerecorded messages based on the limit check. A directional speaker at the player interface plays the message stating whether the requested purchase exceeds the limit.
Section 2 · machine-generated
Variations
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
Other field of use
Spending checks at laundry kiosks
A laundry kiosk initiates a card payment to add wash credits to a shared machine controller. The kiosk receives a stable card token from its payment terminal and queries a site ledger for purchases indexed by that token during the current day. The kiosk compares the recorded purchase total plus the proposed charge with a site limit and displays whether the purchase fits within that limit.
Combination with existing systems
Spending checks linked to cashier reconciliation
The spending service sends a purchase identifier, terminal identifier, and authorized amount to the cashier reconciliation system when a card-funded credit purchase settles. At shift close, the reconciliation system matches settled payments to credit issuance records using the purchase identifier. A cashier dashboard lists payments with missing credit records, and the spending service updates its token-indexed history when it receives a confirmed reversal.
Automated or data-driven variant
Automatic calculation of available purchase amounts
A payment service recalculates the remaining spending allowance whenever a token receives a settled purchase, a confirmed reversal, or a reservation release. After the terminal supplies the token, the player interface requests the allowance and filters its fixed credit bundles to amounts that fit. The service repeats the limit check and reserves the selected amount when the player confirms the purchase.
Specific version of a part
Stable token from terminal
After the processor starts the purchase, the payment terminal reads the card and submits its encrypted details to a token service. The terminal returns the stable card token and transaction reference to the processor in its response.
Integer spending limit comparison
The processor sums the completed purchase amounts found for the token and adds the requested purchase amount, with all values stored in integer cents. It flags a limit breach when the sum exceeds the configured cap and performs the comparison using only the amounts, without resolving a player account identifier.
Section 3 · quoted from USPTO records
Other work
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
1.1initiating, by a processor in response to user input via a player interface device connected to a gaming machine and a gaming network, a payment-card transaction to purchase game credits for use at the gaming machine;
Cardholder 102 tenders payment for a purchase with a transaction card and merchant 110 requests authorization from a merchant bank 108 for the amount of the purchase. The request may be performed over the telephone, but is usually performed through the use of a point-of-sale terminal, which reads cardholder's 102 account information from a magnetic stripe, a chip, or embossed characters on the transaction card and communicates electronically with the transaction processing computers of merchant bank 108.
A · US 2019/0385166 A1 · ¶ 46
The customer device 102 may be presented to the merchant device 104 to consummate a purchase transaction and to permit the merchant device 104 to read payment card account data (including, for example, a payment account number) from the customer device 102.
B · US 2020/0065819 A1 · ¶ 3
1.2obtaining, by the processor from a payment terminal in response to initiating the payment-card transaction, a token that replaces sensitive payment-card information;
During the reading of the payment IC card 202, the merchant device 104 may read the token/PAN stored in the payment IC card 202. The merchant device 104 may generate a payment account system transaction authorization request message, including the payment token read by the reader component as the payment account number information for the transaction authorization request message.
B · US 2020/0065819 A1 · ¶ 67
1.3determining, by the processor using the token as a search parameter into a database of transaction records, a previous use of the token, via the gaming network, for one or more additional payment-card transactions that occurred via the gaming network within a given period;
1.4determining, by the processor in response to determining the previous use of the token, whether a spending limit would be exceeded by an amount of the payment-card transaction, wherein determining whether the spending limit would be exceeded is performed without resolving a player account identifier for the payment-card transaction; and
SL computing device 120 may communicate with spend limit database 180, reset time database 170, and balance database 190 to determine if the requested transaction will exceed the spend limit and trigger an automatic transaction denial.
A · US 2019/0385166 A1 · ¶ 47
1.5presenting, by the processor via a display, an indication of whether the spending limit would be exceeded.
In some embodiments, a display may be present at or in a merchant location and configured to identify a particular user and communicate with SL computing device to determine and display a message or warning to indicate whether potential purchases may trigger an automatic denial.
A · US 2019/0385166 A1 · ¶ 24
An empty cell means only that no passage was reproduced there.
Statements in these documents
To prevent potentially embarrassing situations from arising, a convenient way that allows parties engaging in transactions to see that they are nearing their spend limit while retaining security protections is required.
A · US 2019/0385166 A1 · ¶ 5
Furthermore, a system that allows a party to exceed limits without triggering an automatic denial is needed.
A · US 2019/0385166 A1 · ¶ 5
Although contact reading of payment cards is fairly expeditious, contactless reading, with just a tap of the card on the reader, may be noticeably faster.
B · US 2020/0065819 A1 · ¶ 8
However, the “tap to pay” type of transaction is not possible when the payment card in question lacks contactless capabilities.
B · US 2020/0065819 A1 · ¶ 8
Cite aspatent.fyi, US 2026/0355640 A1, claim 1, first published 2026-11-19T13:37:15-05:00, https://patent.fyi/US20260355640/, SHA-256 64830290fd97132d2be437eb90302db2b76ce520bf7caf0254d16c1a23d7445a