Stripe, Inc. patent applications on February 27th, 2025
Patent Applications by Stripe, Inc. on February 27th, 2025
Stripe, Inc.: 2 patent applications
Stripe, Inc. has applied for patents in the areas of G06Q30/018 (1), G06F9/54 (1), G06F16/2455 (1), G06Q20/02 (1), G06Q30/0601 (1) G06Q30/018 (1), H04L45/24 (1)
With keywords such as: request, device, include, path, account, user, via, also, destination, and capability in patent application abstracts.
Patent Applications by Stripe, Inc.
Inventor(s): Andrew HOSKINS of Burlingame CA (US) for stripe, inc., Jay SHAH of New York NY (US) for stripe, inc., Matthew William JANIGA of South San Francisco CA (US) for stripe, inc., Peter Cronin TERRILL of San Francisco CA (US) for stripe, inc.
IPC Code(s): G06Q30/018, G06F9/54, G06F16/2455, G06Q20/02, G06Q30/0601, H04L67/306
CPC Code(s): G06Q30/018
Abstract: a method and apparatus for managing capabilities of an account of a user system at a commerce platform are described. the method includes receiving a request for a desired functionality of the account from a user system. the method may also include mapping the requested capability to a compliance plan that defines a set of account data to be collected before activation of the capability for the account. the method may also include transmitting a message that includes a list of additional data to be provided by the user system before activation of the capability for the account. the method may further include receiving a response from the user system that includes the additional data for activating the capability for the account.
Inventor(s): Ji Huang of Bothell WA (US) for stripe, inc., Stefan Gawrys of Seattle WA (US) for stripe, inc.
IPC Code(s): H04L45/24, H04L45/302
CPC Code(s): H04L45/24
Abstract: aspects of the subject technology include receiving from a user device a request for obtaining data associated with the user device. the request is addressed to a destination device. aspects also include determining with a first controller whether to transmit the request to the destination device via a first path. the determination is based on a first success rate of the first path. aspects also include transmitting the request to the destination device via the first path in response to a determination to transmit the request to the destination device via the first path. aspects also include determining, with a second controller, whether to transmit the request to the destination device via a second path, in response to a determination not to transmit the request via the first path. the determination is based on a second success rate of the second path.
