Granted Patent B1

US 12,412,182 · App. 18/390,211 · Granted Sep 9, 2025

Inventors: James Zhang (Los Angeles, CA); Alexander Thiemann (San Francisco, CA); Theodora Chu (Los Altos Hills, CA); Jessica Jarvis (San Francisco, CA); Evan Kay (San Francisco, CA); Robert Coe (San Mateo, CA); Vihari Muttineni (San Francisco, CA)

Assignee: STRIPE, INC.

G06Q30/016G06F9/547G06F16/955G06Q30/0641H04L67/146

Abstract

Claims (77)

1. A method for providing access to a user portal, on behalf of a first system, comprising:

receiving, from the first system, a configuration request comprising configuration settings;

configuring the user portal using the configuration settings;

receiving a session request to generate a portal session that acts as an application programing interface (API) endpoint for a set of functions;

in response to receiving the session request:

extracting, from the session request, a user identifier, a secret string, a URL, and a reference to the configuration settings, the URL uniquely associated with the portal session, the URL comprising a copy of the secret string; and

generating the portal session and a portal session object;

transmitting the portal session object to the first system; and

in response to a portal access request made to the API endpoint via the URL by a user, providing access to the user portal via the portal session, comprising:

determining that the secret string matches the copy of the secret string;

determining that the portal session has not expired; and

rendering a hyper-text markup language (HTML) page that serves an application, the application to load the portal session and render a user interface (UI) of the user portal.

2. The method of claim 1 , wherein the configuration settings comprise:

the set of functions to be provided to a session of the user portal;

the user identifier;

the secret string; and

the URL, the URL comprising the secret string.

3. The method of claim 1 , wherein a schema of the portal session comprises the user identifier, the secret string, the URL, and the reference to the configuration settings.

4. The method of claim 1 , further comprising:

receiving, at the API endpoint, an API call that requests performance of a function from the set of functions; and

transmitting the received API call to one or more backend API endpoints, causing the one or more backend API endpoints to perform the function.

5. The method of claim 4 , further comprising:

translating, by the API endpoint, the received API call to one or more backend API endpoints.

6. The method of claim 1 , further comprising:

transmitting, to the first system, one or more event objects indicating changes to user data made, during the portal session, by execution of one or more of the set of functions.

7. The method of claim 1 , wherein the session request is received by a single application program interface (API) that is configured to generate the portal session and the portal session object.

8. The method of claim 1 , wherein the portal session provides access to the user portal for a pre-set amount of time before expiring.

9. A non-transitory computer-readable medium having instructions stored thereon which, when executed by a processor, cause the processor to:

receive, from a first system, a configuration request comprising configuration settings;

configure a user portal using the configuration settings;

receive a session request to generate a portal session that acts as an application programing interface (API) endpoint for a set of functions;

in response to receiving the session request:

extract, from the session request, a user identifier, a secret string, a URL, and a reference to the configuration settings, the URL uniquely associated with the portal session, the URL comprising a copy of the secret string; and

generate the portal session and a portal session object;

transmit the portal session object to the first system; and

in response to a portal access request made to the API endpoint via the URL by a user, provide access to the user portal via the portal session, comprising:

determining that the secret string matches the copy of the secret string;

determining that the portal session has not expired; and

rendering a hyper-text markup language (HTML) page that serves an application, the application to load the portal session and render a user interface (UI) of the user portal.

10. The non-transitory computer-readable medium of claim 9 , wherein the configuration settings comprise:

the set of functions to be provided to a session of the user portal;

the user identifier;

the secret string; and

the URL, the URL comprising the secret string.

11. The non-transitory computer-readable medium of claim 9 , wherein a schema of the portal session comprises the user identifier, the secret string, the URL, and the reference to the configuration settings.

12. The non-transitory computer-readable medium of claim 9 , wherein the instructions further cause the processor to:

receive, at the API endpoint, an API call that requests performance of a function from the set of functions; and

transmit the received API call to one or more backend API endpoints, causing the one or more backend API endpoints to perform the function.

13. The non-transitory computer-readable medium of claim 12 , wherein the instructions further cause the processor to:

translating, by the API endpoint, the received API call to one or more backend API endpoints.

14. The non-transitory computer-readable medium of claim 9 , wherein the instructions further cause the processor to:

transmit to the first system, one or more event objects indicating changes to user data made by execution of one or more of the set of functions within the user portal and during the portal session.

15. The non-transitory computer-readable medium of claim 9 , wherein the session request is received by a single application program interface (API) that is configured to generate the portal session and the portal session object, and wherein the portal session provides access to the user portal for a pre-set amount of time before expiring.

16. A system comprising:

a memory that stores configuration settings indicating a set of functions to be provided by a user portal; and

a processor coupled with the memory, the processor configured to:

receive, from a second system, a configuration request comprising the configuration settings;

configure the user portal using the configuration settings;

receive a session request to generate a portal session that acts as an application programing interface (API) endpoint for the set of functions;

in response to receiving the session request:

extract, from the session request, a user identifier, a secret string, a URL, and a reference to the configuration settings, the URL uniquely associated with the portal session, the URL comprising a copy of the secret string; and

generate the portal session and a portal session object;

transmit the portal session object to the second system; and

in response to a portal access request made to the API endpoint via the URL by a user, provide access to the user portal via the portal session, comprising:

determining that the secret string matches the copy of the secret string;

determining that the portal session has not expired; and

rendering a hyper-text markup language (HTML) page that serves an application, the application to load the portal session and render a user interface (UI) of the user portal.

17. The system of claim 16 , wherein the configuration settings comprise:

the set of functions to be provided to a session of the user portal;

the user identifier;

the secret string; and

the URL, the URL comprising the secret string.

18. The system of claim 16 , wherein a schema of the portal session comprises the user identifier, the secret string, the URL, and the reference to the configuration settings.

19. The system of claim 16 , further comprising the processor configured to:

receive, at the API endpoint, an API call that requests performance of a function from the set of functions; and

transmit the received API call to one or more backend API endpoints, causing the one or more backend API endpoints to perform the function.

20. The system of claim 19 , further comprising the processor configured to: translate, by the API endpoint, the received API call to one or more backend API endpoints.

Assignments (1)

Continuity (1)

References Cited (12)