Stripe, Inc. patent applications on January 9th, 2025
Patent Applications by Stripe, Inc. on January 9th, 2025
Stripe, Inc.: 2 patent applications
Stripe, Inc. has applied for patents in the areas of G06Q30/0601 (1), G06Q20/12 (1), G06Q20/32 (1), H04L43/0852 (1), H04L43/0817 (1) G06Q30/0613 (1), H04L43/0858 (1)
With keywords such as: third, application, product, service, party, movement, interface, software, comprises, and performing in patent application abstracts.
Patent Applications by Stripe, Inc.
Inventor(s): Rasmus Rygaard of San Francisco CA (US) for stripe, inc., Devesh Kumar Senapati of San Francisco CA (US) for stripe, inc., Christopher Ross Continanza of Berkeley CA (US) for stripe, inc., James William Danz of Los Altos CA (US) for stripe, inc.
IPC Code(s): G06Q30/0601, G06Q20/12, G06Q20/32
CPC Code(s): G06Q30/0613
Abstract: a method and apparatus for a commerce platform coordinating a purchase of a product sold by a merchant system through a third party application are described. the method may include receiving a notification from the third party application requesting to purchase a product from within the third party application, wherein the notification comprises an identifier for the product and an identifier for the merchant system that sells the product. the method may also include a product checkout interface having an appearance consistent with an appearance of a user interface of the third party application, and transmitting the product checkout interface generated by the commerce platform to a user device executing the third party application causing the third party application to render the product checkout interface within at least a portion of the user interface of the third party application.
Inventor(s): Ray Morgan of San Francisco CA (US) for stripe, inc., Alessandro Catorcini of Bellevue WA (US) for stripe, inc., Isaac Diamond of San Francisco CA (US) for stripe, inc.
IPC Code(s): H04L43/0852, H04L43/0817, H04L67/00
CPC Code(s): H04L43/0858
Abstract: a method and system for performing a movement of a service within a distributed system. in one embodiment, the method comprises determining one or more locations where the service is to be moved. the method further comprises for each of the one or more locations, computing a metric including a cross-cell cost (c-cost) or a data locality-cost (dl-cost) of the software service if a movement of the software service to a location was to occur, prior to performing the movement of the software service; and modelling a latency and availability of the system due to the movement of the software service to the location based on the metric. the method further comprises performing the movement of the service based on the modelled latency and availability of the system.
