Granted Patent B2

US 12,547,746 · App. 18/751,920 · Granted Feb 10, 2026

Inventors: Venil Loyd Noronha (San Jose, CA); Angel Samsuddin Maredia (New Rochelle, NY); Tushar Dhoot (Seattle, WA); Bryan Berg (Seattle, WA); Daniel James Cobb (Sheboygan, WI); Joyce Zhang (Thousand Oaks, CA); Matthew Jeffryes (Moscow, ID); Ben Dong (Oakland, CA); Frank Yu (Seattle, WA)

Assignee: Stripe, Inc.

G06F21/606

Abstract

Claims (72)

1 . A method performed by a data processing system in communication with a network, comprising:

storing, in a database, a plurality of secure data, wherein each of the plurality of secure data is associated with a respective token;

receiving from a first server, over the network, a request through a first application programming (API) call, the request comprising at least: an indicator associated with a secure data, a destination indicator, a first API key, a second API key, and a body having a predefined data format;

validating the request based on the first API key;

referencing the database to obtain the secure data based on the indicator and the respective token;

populating the body with the secure data; and

transmitting, over the network, a second request comprising the second API key and the populated body to a second server that is associated with the destination indicator, through a second API call.

2 . The method of claim 1 , wherein a first one or more services of the data processing system

receives the request,

validates the request with the first API key,

encrypts the second API key, and

provides a resulting partially encrypted request to a second one or more services.

3 . The method of claim 2 , wherein the second one or more services of the data processing system

references the respective token with the indicator,

stores metadata associated with the partially encrypted request, and

provides the respective token to the first one or more services.

4 . The method of claim 3 , wherein the first one or more services

references the secure data with the respective token received from the second one or more services,

validates the second API key,

populates the body with the secure data, and

transmits the second request according to a uniform resources locator (URL) mapped to the destination indicator.

5 . The method of claim 1 , wherein the second API call is performed as a hypertext transfer protocol (HTTP) message with an HTTP method type selected based on the destination indicator.

6 . The method of claim 1 , wherein the predefined data format comprises a JavaScript Object Notation (JSON) data format with one or more populated fields and one or more unpopulated fields.

7 . The method of claim 1 , further comprising: storing, in a second database, metadata associated with the request, the metadata omitting the secure data and the second API key.

8 . The method of claim 1 , wherein the request further comprises an idempotency key, and wherein transmitting the second request comprises populating the second request with the idempotency key.

9 . The method of claim 1 , wherein the second server is associated with a secure vault, and the second request is transmitted to the second server to update the secure vault with the secure data in accordance with the populated body of the second request.

10 . The method of claim 1 , wherein the second server is associated with a third party server, and the second request is transmitted to the second server for the third party to perform an action with the secure data and other populated fields in the body of the second request.

11 . A server computer system comprising:

a memory, and one or more processors coupled with the memory configured to perform operations, comprising:

storing, in a database, a plurality of secure data, wherein each of the plurality of secure data is associated with a respective token;

receiving from a first server, over a network, a request through a first application programming (API) call, the request comprising at least: an indicator associated with a secure data, a destination indicator, a first API key, a second API key, and a body having a predefined data format;

validating the request based on the first API key;

referencing the database to obtain the secure data based on the indicator and the respective token;

populating the body with the secure data; and

transmitting, over the network, a second request comprising the second API key and the populated body to a second server that is associated with the destination indicator, through a second API call.

12 . The server computer system of claim 11 , wherein a first one or more services of the server computing system

receives the request,

validates the request with the first API key,

encrypts the second API key, and

provides a resulting partially encrypted request to a second one or more services.

13 . The server computer system of claim 12 , wherein the second one or more services

references the respective token with the indicator,

stores metadata associated with the partially encrypted request, and

provides the respective token to the first one or more services.

14 . The server computer system of claim 13 , wherein the first one or more services references the secure data with the respective token received from the

second one or more services,

validates the second API key;

populates the body with the secure data, and

transmits the second request according to a uniform resources locator (URL) mapped to the destination indicator.

15 . The server computer system of claim 11 , wherein the second API call is performed as a hypertext transfer protocol (HTTP) message with an HTTP method type selected based on the destination indicator.

16 . A non-transitory computer readable storage medium storing instructions, which when executed by a computer processing system, causes the computer processing system to perform operations comprising:

storing, in a database, a plurality of secure data, wherein each of the plurality of secure data is associated with a respective token;

receiving from a first server, over a network, a request through a first application programming (API) call, the request comprising at least: an indicator associated with a secure data, a destination indicator, a first API key, a second API key, and a body having a predefined data format;

validating the request based on the first API key;

referencing the database to obtain the secure data based on the indicator and the respective token;

populating the body with the secure data; and

transmitting, over the network, a second request comprising the second API key and the populated body to a second server that is associated with the destination indicator, through a second API call.

17 . The non-transitory computer readable storage medium of claim 16 , wherein a first one or more services of the computer processing system

receives the request,

validates the request with the first API key,

encrypts the second API key, and

provides a resulting partially encrypted request to a second one or more services.

18 . The non-transitory computer readable storage medium of claim 17 , wherein the second one or more services of the computer processing system

references the respective token with the indicator,

stores metadata associated with the partially encrypted request, and

provides the respective token to the first one or more services.

19 . The non-transitory computer readable storage medium of claim 18 , wherein the first one or more services

references the secure data with the respective token received from the second one or more services,

validates the second API key,

populates the body with the secure data, and

transmits the second request according to a uniform resources locator (URL) mapped to the destination indicator.

20 . The non-transitory computer readable storage medium of claim 16 , wherein the second API call is performed as a hypertext transfer protocol (HTTP) message with an HTTP method type selected based on the destination indicator.

Assignments (2)

Continuity (1)

References Cited (18)