Stripe, Inc. patent applications on October 17th, 2024
Patent Applications by Stripe, Inc. on October 17th, 2024
Stripe, Inc.: 3 patent applications
Stripe, Inc. has applied for patents in the areas of G06Q20/40 (2), H04L9/40 (2), G06F16/957 (1), G06F16/958 (1), G06F21/60 (1) G06F16/9577 (1), G06Q20/4012 (1), H04L63/083 (1)
With keywords such as: pin, device, token, embedded, key, third, app, remote, permissions, and computing in patent application abstracts.
Patent Applications by Stripe, Inc.
20240346105. EMBEDDED USER INTERFACE ELEMENTS_simplified_abstract_(stripe, inc.)
Inventor(s): Gabriel HURLEY of Oakland CA (US) for stripe, inc., Julia CHAVES of Oakland CA (US) for stripe, inc., Peter YAWORSKI of Aurora (CA) for stripe, inc., Fred KUO of Seattle WA (US) for stripe, inc., Konstantin TENNHARD of Pointe-Claire (CA) for stripe, inc., Jorge Eugenio AGUIRRE GONZALEZ of Bothell WA (US) for stripe, inc.
IPC Code(s): G06F16/957, G06F16/958, G06F21/60
CPC Code(s): G06F16/9577
Abstract: in some embodiments, an electronic device is configured to transmit a first request for an account session key, receive the account session key associated with a first set of permissions corresponding to the embedded interface element and a second set of permissions corresponding to the embedded app, transmit a second request for an embedded app key, receive the embedded app key associated with a third set of permissions corresponding to the embedded app, and proxy communications between the embedded interface element and the processor server, based on the account session key associated with the first set of permissions, and between the embedded app and the processor server, based on the embedded app key associated with the third set of permissions.
Inventor(s): Chi Wah Lo of Tsuen Wan (HK) for stripe, inc., Hwai Sian Tsai of Tsuen Wan (HK) for stripe, inc., Namson Kwok of Tsuen Wan (HK) for stripe, inc.
IPC Code(s): G06Q20/40, G06Q20/20, G06Q20/32, G07F7/10, H04L9/40, H04W12/02, H04W12/069
CPC Code(s): G06Q20/4012
Abstract: a system for accepting the input of a pin comprises a first device receiving a randomized pin layout derived on a fourth device. the randomized pin layout is displayed on a display of the first device. a second device comprises an input for accepting a series of key presses to produce a pin token. the pin token indicating each of the series of key presses. a third device is in communication with the second device. the third device derives the randomized pin layout and receives the pin token from the second device without the pin token being present on the first device. the third device combines the pin layout and the pin token to produce a pin. the pin is used to authenticate a transaction. the fourth and third devices each store a shared secret used to independently derive the randomized pin layout on the fourth and third devices.
20240348598. SECURE TOKEN DRIVEN CONDITIONAL ROUTING OF PROCEEDS_simplified_abstract_(stripe, inc.)
Inventor(s): Matthew William Janiga of South San Francisco CA (US) for stripe, inc., Karen Elizabeth Brinkley of San Francisco CA (US) for stripe, inc., Vincent Michael Cogan of San Francisco CA (US) for stripe, inc., Brian David Krausz of San Francisco CA (US) for stripe, inc.
IPC Code(s): H04L9/40, G06Q20/00, G06Q20/02, G06Q20/40, H04L9/32
CPC Code(s): H04L63/083
Abstract: methods and systems for secure token driven conditional routing of proceeds are described. a request to initiate routing of data between remote systems is received by a server computer system, where the request includes an incomplete set of parameters. a validation challenge and a challenge response defined by a first remote computing system are received, and a token that references the first remote computing system and the incomplete parameter set is generated. a validation may then be performed for a second remote computing system using the validation challenge and the challenge response defined by the first remote computing system. the incomplete set of parameters may then be completed by the second remote computing system when the challenge is validated to enable the routing of data according to the complete set of parameters referenced by the token.
