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.2Server-held payment credentials
What ifWhat if a remote payment server held the transaction cards and the vehicle stored only a device authentication key?
Claim language“storing one or more transaction cards thereon”
The vehicle signs a request containing the charging session identifier with its device key. The server verifies the signature, looks up the payment token assigned to the vehicle, and submits an authorization request.
1.4Fixed payment message format
What ifWhat if every session used a single preconfigured payment message format and the station sent only the session identifier and price data?
Claim language“receive a list of supported payment applications”
The vehicle encodes its payment token and the session identifier in the configured format. The station forwards the message to its configured payment gateway and receives the authorization result.
1.6Driver selects a charging card
What ifWhat if the driver picked a saved card before connecting and the gateway decided whether to authorize that card?
Claim language“match the stored one or more transaction cards”
The vehicle sends the selected card's token with the charging session identifier. The gateway attempts authorization and returns the result, and the vehicle prompts the driver for another card after a rejection.
1.8Direct lookup of driver choice
What ifWhat if the driver assigned one saved card to each charging account and the vehicle looked up that assignment at session start?
Claim language“prioritize the candidate list of transaction cards”
The station provides a charging account identifier, and the vehicle uses it as a key in a table that maps account identifiers to card references. The vehicle checks the referenced card's compatibility and uses it when compatible. A missing or incompatible assignment prompts the driver to choose a card.
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
Payment selection at bulk water dispensers
A tanker truck controller stores payment card records containing payment application identifiers and per-fill spending limits. A metered water dispenser sends its supported application identifiers and the estimated fill price over a local radio link. The truck controller forms a candidate list from matching records whose limits cover the estimate and selects the card with the smallest remaining margin above that estimate. The dispenser controller associates the resulting authorization reference with the meter reading used to calculate the final charge.
Component substitution
Binary search for payment application matching
A sorted array and binary search replace a sequential comparison of every stored card against every station application. The vehicle processor sorts the station's supported application identifiers and searches the array for each application identifier in a stored card record. It adds a card to the candidate list on the first successful lookup and orders the candidates by the transaction fee advertised for the matching application.
Parameter or scale variation
Bounded matching for a depot charger
A depot charger advertises up to 64 supported payment application identifiers in one message, and each vehicle stores up to 16 card records with up to four application identifiers per record. The vehicle indexes the station identifiers on receipt and performs at most 64 membership checks to build the candidate list. It completes selection within 200 milliseconds of receiving the full message and gives priority to the compatible card with the highest remaining daily spending allowance. If selection exceeds the time budget, the vehicle discards the partial list and requests a fresh advertisement.
Combination with existing systems
Credential selection with depot dispatch schedules
A fleet dispatch system sends the vehicle a trip identifier, planned departure time, and a list of card records approved for the trip. The vehicle intersects that list with cards whose application identifiers appear in the charger advertisement. For each candidate, the vehicle adds the station's advertised authorization time to the predicted charging duration and selects the lowest-fee candidate that fits before departure. The vehicle reports the trip identifier, selected card record identifier, and resulting charging session identifier to the dispatch system.
Automated or data-driven variant
Card selection from recent authorization outcomes
The vehicle maintains counts of approved and completed authorization attempts for each card and charging site over a rolling 30-day window. After filtering stored cards against the station's supported application identifiers, the processor ranks each candidate by its approval fraction at the current site. For candidates with fewer than five site attempts, the processor uses the card's fleetwide approval fraction from the same window and assigns a default fraction of one-half when no attempts are recorded. The processor selects the highest-ranked card, breaks ties by the station's advertised transaction fee, and records the result when authorization completes.
Specific version of a part
Driver starts charging by phone
The driver scans a printed code that identifies the charging connector, and the phone sends that identifier and a payment token to a remote server over a cellular connection. After authorization, the server enables the connector through the station controller. The vehicle's charging circuitry uses the pilot duty cycle and voltage levels to determine the current limit and signal readiness.
Gateway selects the payment card
The vehicle sends a signed account reference and a charging session identifier to the station. The station forwards both values to the gateway, which checks the account's stored card tokens against the station configuration, applies the driver's preferences, and submits the selected token for authorization.
Dedicated payment microcontroller
A 32-bit microcontroller executes payment selection code from on-chip flash memory. The vehicle's charging controller passes session messages to the microcontroller over a serial link.
Data link over charging conductors
The vehicle and station use power-line modems coupled to the charging cable's pilot and protective earth conductors. The vehicle establishes an authenticated, encrypted session over the data link before exchanging payment messages.
Card records from secure storage
The processor reads saved card records from a secure storage chip over a serial bus after authenticating to the chip. Each record contains a token reference, an application identifier, and an expiration date.
Candidate list of card indices
The processor appends a stored card's record index to an array in working memory when its application identifier matches a station entry. Each index appears once and identifies the card record used during prioritization.
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.
The logic subsystem may include one or more processors configured to execute software instructions.
A · US 2017/0278095 A1 · ¶ 56
1.2a memory device storing one or more transaction cards thereon,
Mobile payment systems can enable mobile devices to function as virtual wallets with mobile payment (e.g., credit, debit, and gift) cards, membership cards, and loyalty cards stored therein.
A · US 2017/0278095 A1 · ¶ 2
(5) receiving, by the electronic wallet application, the number of eligible payment cards that are already provisioned to the electronic wallet application;
B · US 2022/0261784 A1 · ¶ 4
1.3the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: establish a communication channel with a charging station (CS) computing system via one or more communication protocols;
1.4the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: receive a list of supported payment applications from the CS computing system;
(8) receiving, by electronic wallet application, a list of identifiers for one or more eligible accounts for provisioning;
B · US 2022/0261784 A1 · ¶ 9
1.5the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: retrieve the stored one or more transaction cards from the memory device;
The user account server may then determine, for each of the retrieved mobile payment cards, whether that card is eligible for use in a mobile wallet application.
A · US 2017/0278095 A1 · ¶ 9
In one embodiment, a method for determining card availability may include: (1) retrieving, by an electronic wallet application executed by an electronic device, a profile identifier from a memory of the electronic device;
B · US 2022/0261784 A1 · ¶ 4
1.6the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: match the stored one or more transaction cards to the list of supported payment applications;
The user account server may then determine, for each of the retrieved mobile payment cards, whether that card is eligible for use in a mobile wallet application. Eligibility may be based on eligibility parameters such as whether the card has been suspended (e.g., due to suspected fraud or exceeding of credit limit), whether the card has expired, verification parameters, card type parameters, user preferences, etc.
A · US 2017/0278095 A1 · ¶ 9
1.7the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: based on the matching, generate a candidate list of transaction cards compatible with the CS computing system;
Continuing with FIG. 1, once the eligibility of the mobile payment cards is determined by the user account server 106, the mobile payment card list 132 may be narrowed down by removing any ineligible mobile payment cards from the list. As such an eligible mobile payment card list 148 including one or more eligible mobile payment cards 150 may be stored in the user account 134.
A · US 2017/0278095 A1 · ¶ 22
1.8the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: prioritize the candidate list of transaction cards based on one or more predefined rules; and
1.9the memory device further having computer-executable instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to: select a prioritized transaction card for processing a transaction at the CS computing system.
(10) receiving, by the electronic wallet application, a selection of one of the one or more eligible accounts for provisioning;
B · US 2022/0261784 A1 · ¶ 9
An empty cell means only that no passage was reproduced there.
Statements in these documents
Manual entry can be tedious, time consuming, and prone to error.
A · US 2017/0278095 A1 · ¶ 2
This, in conjunction with other features, can streamline setting up, maintaining, and using a mobile wallet.
A · US 2017/0278095 A1 · ¶ 8
Despite this ability, that may not be enough to determine if the applications should be linked in a business meaningful way.
B · US 2022/0261784 A1 · ¶ 3
Systems and methods for determining payment card provisioning availability in mobile applications are disclosed.
B · US 2022/0261784 A1 · ¶ 4
Cite aspatent.fyi, US 2026/0356233 A1, claim 1, first published 2026-11-19T22:39:24-05:00, https://patent.fyi/US20260356233/, SHA-256 c5122d7378bf6d7fe95c56ee67ad8b9d9dc5cbe8a710f5b23faa316b02246947