Patent Applications by Stripe, Inc. on June 19th, 2025

Stripe, Inc.: 8 patent applications

Stripe, Inc. has applied for patents in the areas of G06Q40/02 (Banking, e.g. interest calculation or account maintenance (credit or loans ), 2), G06F9/542 (Interprogram communication, 1), G06F16/2379 ({Updates performed during online database operations; commit processing}, 1), G06Q20/0855 ({involving a third party}, 1), G06Q20/10 (specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems, 1), G06Q40/04 (Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange, 1), G06Q40/06 (Asset management; Financial planning or analysis, 1)

With keywords such as: event, digital, messages, disclosed, herein, methods, systems, hydrating, updating, incomplete in patent application abstracts.

Top Inventors:

Varshinee Sreekanth of Seattle WA US (1 patents)
Sidharth Vijayachandran of Issaquah WA US (1 patents)
Sasank Chundi of San Francisco CA US (2 patents)
Salil Bapat of Bellevue WA US (1 patents)
Devesh Chourasiya of Mountain View CA US (4 patents)

Patent Applications by Stripe, Inc.

20250199884. HYDRATION SYSTEM DISTRIBUTED ASSETS MANAGEMENT PLATFORM (Stripe, .)

Abstract: disclosed herein are methods and systems for hydrating (e.g., updating) incomplete event messages in a digital asset management platform. in one embodiment, a part of the platform (e.g., hydration system) receives a request to update an event message that has a unique identifier and includes a placeholder data field (e.g., a blank data record) for some missing information that is unknown to the system at the time of receipt. the hydration system then receives a set of possible information, along with a candidate identifier and a corresponding source identifier. when the identifier from the event message matches the candidate identifier, the hydration system fills in the missing information accordingly, thereby updating (hydrating) the incomplete event message. thereby, the processes disclosed herein correspond to finding and adding missing pieces of information to event messages within a digital asset management platform.

20250200025. SYSTEMS METHODS ZERO DOWNTIME DISTRIBUTED SEARCH SYSTEM UPDATES (Stripe, .)

Abstract: a method for performing search system upgrades is described. the method may include processing a software upgrade for a search system cluster distributed over one or more nodes, the one or more nodes comprising current search system data nodes. the method may include allocating at least a set of one or more search system data nodes for the software upgrade including at least one upgraded search system data node. the method may include receiving, during the software upgrade, transaction data for a transaction, and receiving search requests to be executed by the search system cluster. the method may include performing ingestion of received transaction data in both the current search system data nodes and the at least one upgraded search system data node, and processing the search requests by the search system cluster against the current search system data nodes until the software upgrade is determined to be complete.

20250200536. ASSETS INTERFACE DISTRIBUTED ASSETS MANAGEMENT PLATFORM (Stripe, .)

Abstract: disclosed here are methods and systems for managing the movement of assets between accounts on a distributed digital platform. in one embodiment, a specialized interface in the distributed digital platform receives a message about an asset transfer request that includes various data fields and an identifier. the interface then queries the specific configuration for the type of asset transfer (based on the data included within the received message), which might involve multiple steps or “legs.” next, the digital platform converts the original message into one or more new messages, each corresponding to a step in the transfer process. finally, the digital platform sends at least one of these new messages to a system responsible for actually causing/facilitating the movement, thereby completing the transfer.

20250200537. MACHINE-LEARNING BASED DELAY PREDICTION (Stripe, .)

Abstract: aspects of the subject technology include obtaining a transfer request event associated with a transaction, the transfer request event indicating a request day of week and time of day, and, when the request time of day is past a pre-determined cutoff time, adjusting the request day of week to be a subsequent day. aspects also include determining, using the transfer request event and based on a machine learning model trained on historical transaction data, a predicted transfer delay for the transaction, obtaining a set of relevant non-transfer days based on a comparison between the historical transaction data and a set of past non-transfer days, and, when one or more non-transfer days from the set of relevant non-transfer days occur within a time period from the request day of week and over the predicted transfer delay, adjusting the predicted transfer delay based on the one or more non-transfer days.

20250200648. DATA AGGREGATION THRESHOLDING-BASED ACCOUNT MANAGEMENT (Stripe, .)

Abstract: aspects of the subject technology allow an entity to aggregate transaction data for safeguarding. aspects include obtaining a set of data items associated with a set of transactions, and, for each respective data item, determining a funding type corresponding to the respective data item based at least in part on a respective attribute and augmenting the respective data item based on the determined funding type and an attribute estimation. aspects also include aggregating the set of data items into respective groups based on the funding type, the merchant identifier, and/or the jurisdiction identifier, and transmitting a respective group to a service for determining whether a respective bank account includes a threshold amount of funds based on the amounts of data items in the respective group.

20250200649. TOOLS ACCOUNT MANAGEMENT (Stripe, .)

Abstract: aspects of the subject technology include providing, from a sever to a first device, balance information for a plurality of accounts of an organization. for a first selected account, information for first expected sweeps which are to be received within a first time period, information for second expected sweeps for a second time period, and information for reconciled sweeps for the second time period are received. the first expected sweeps or the second expected sweeps include a first portion of expected sweeps which are automatically initiated by a service. when an anomaly is detected in the first account, the service may schedule an automated event to resolve the anomaly, and the automated event is reported. the service may not schedule an automated event and an input is received to resolve the anomaly.

20250200658. EXCHANGE PLATFORM DISTRIBUTED ASSETS MANAGEMENT PLATFORM (Stripe, .)

Abstract: disclosed herein are methods and systems for a simplified process for managing the exchange of different types of assets on a digital platform for disparate users. the processes discussed with respect to the digital platform streamline the exchange of assets based on various conditions in an efficient manner. in one example, the platform initially receives an event message (via an endpoint api) that specifies the amounts and types of two different assets. the platform then aggregates the received data within the event message. next, the platform's exchange manager continually monitors the data indicated within the event message. when the totals reach a predefined threshold or condition, such as reaching a certain amount, the platform triggers a process where a remote system automatically converts a specified amount of one asset type into another asset type.

20250200662. DISTRIBUTED ASSETS MANAGEMENT PLATFORM (Stripe, .)

Abstract: disclosed herein are methods and systems for a digital platform to manage data related to the movement of assets between accounts. in one embodiment, the platform receives a continuous stream of messages, each indicating a transfer of assets between accounts. the platform verifies the messages to ensure that no digital information is missing. once a message is verified as complete, the platform generates a liquidity event message to manage the regular transfer of assets between accounts, based on certain conditions (e.g., account balances). the liquidity event message is sent to another part of the platform, known as the liquidity engine, which then carries out the asset transfers as described in the message. thereby, the workload of receiving, checking, completing, and acting on messages about asset transfers is bifurcated to ensure efficient and controlled movement of assets within the digital platform.