Granted Patent B2

US 12,244,588 · App. 18/220,186 · Granted Mar 4, 2025

Inventors: Nathan C. Freeling (Lafayette, CA); Imran Haider (San Francisco, CA); Ranganathan Kanchi (Danville, CA); Andrew-An Truong Luu (Berkeley, CA); Nancy Y. Mao (San Francisco, CA); Kumaran Perumal (San Ramon, CA)

Assignee: Wells Fargo Bank, N.A.

H04L63/0853G06F9/547G06Q20/401G06Q30/0601G06Q30/0613H04L9/3213H04L67/142H04L67/51

Abstract

Claims (37)

1. A method comprising:

receiving, via a networking gateway, an authentication API call from a third-party computing system providing a website to a user device, the authentication API call requesting a session token;

transmitting, in response to the authentication API call, the session token to the third-party computing system;

receiving from the user device, via the networking gateway during a communication session using the session token, user data input by a user into the user device;

determining whether to approve a new account for the user based on the user data received from the user device during the communication session; and

transmitting, to the user device, a response indicative of a result of the determining whether to approve the new account.

2. The method of claim 1 , wherein transmitting the response to the user device comprises transmitting the response to an SDK component incorporated in the website.

3. The method of claim 1 , wherein the response indicative of the result is transmitted without directing the user to a second website or application of the service provider.

4. The method of claim 1 , wherein the result indicates the new account is approved, and wherein opening of the new account is not based on user data that is received via a second website or application of the service provider after the authentication API call from the third-party computing system.

5. The method of claim 1 , further comprising receiving from the third-party computing system, via the networking gateway, a servicing API call requesting information regarding the result.

6. The method of claim 5 , wherein the new account is approved, and wherein the servicing API call requests an account number for the new account.

7. The method of claim 6 , wherein the new account is a credit card, and wherein the account number is a credit card account number.

8. The method of claim 6 , further comprising transmitting, in response to receiving the servicing API call, the account number to the third-party computing system.

9. The method of claim 8 , further comprising receiving, from the third-party computing system, a request to use the new account in a transaction.

10. The method of claim 9 , wherein the transaction is a purchase by the user of the user device of one or more items presented by the third-party computing system via the website.

11. The method of claim 10 , wherein the new account is a credit card, and wherein the method further comprises charging the purchase to the credit card.

12. The method of claim 1 , further comprising receiving, via the website, a request for an initialization script which, when executed by the website, initializes an SDK component incorporated in the website.

13. The method of claim 12 , further comprising transmitting, in response to receiving the request, the initialization script to the user device.

14. A method comprising:

receiving, from a third-party computing system, a request for a session token;

transmitting, in response to the request, the session token to the third-party computing system;

receiving from the user device, via a frame in the third-party website, user data input into the user device;

determining whether to approve a new account for the user based on the user data received via the frame in the website; and

transmitting to the user device a response indicative of a result of the determining whether to approve the new account.

15. The method of claim 14 , wherein the frame is an inline frame.

16. The method of claim 14 , wherein receiving the request from the third-party computing system comprises receiving, via an API gateway, an authentication API call requesting the session token.

17. The method of claim 14 , wherein receiving the user data via the frame comprises receiving one or more origination API calls from the user device.

18. The method of claim 14 , wherein the new account is approved and opened without directing the user to a second website or application of the service provider.

19. The method of claim 14 , wherein determining whether to approve the new account is not based on user data that is received via a second website or application of the service provider after the request for the session token is received from the third-party computing system.

20. A method, implemented via a user device, comprising:

presenting, via one or more user interfaces configured to receive inputs from a user and provide outputs to the user, a website served by a third-party computing system;

receiving, via the one or more user interfaces, a selection indicating a user request for a new account;

initializing a frame in the website to enable private communication between the user and the service provider computing system;

receiving, via the one or more user interfaces, user data input by the user into the frame;

securely transmitting the user data to the service provider computing system via the frame in the website;

receiving from the service provider computing system a transmission indicating whether the new account has been approved; and

presenting to the user, via the one or more user interfaces, information on whether the new account has been approved based on the transmission.

Continuity (4)

References Cited (241)