Transaction account interface

• US 9,922,369 B2
• Filed: 07/21/2014
• Issued: 03/20/2018
• Est. Priority Date: 12/07/2005
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: III Holdings 1, LLC (Intellectual Ventures LLC)
• Inventors: Bentley, Simon R., Craft, Deborah Louise, Dunn, Melanie Anne, Kayode, Adeyemi O., Mehta, Chintan M., Perracchio, Denis George, Vora, Sejal Dilip
• Primary Examiner(s): Lemieux, Jessica
• Application Number:
  US14/336,658
• Publication Number:
  US 20140379542A1
• Time in Patent Office: 1,338 Days
• Field of Search: 705 35
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 50/188 Electronic negotiation

Abstract

A system, method and computer program product for interfacing disparate partner systems to a transaction account issuer system is disclosed. A Web server receives a request from a disparate partner system, such as a Web service, a portal and/or a partner microsite and an application server extracts a partner identifier from the request. In turn, a delegate engine delegates actions corresponding to the request to one or more handlers using predetermined rules associated with the partner identifier. A worker manager manages worker code blocks which perform the actions based on a subset of the predetermined rules associated with the partner identifier. The Web server then communicates an outcome to the partner system based on the actions performed by the worker code blocks.

Claims

1. A method, comprising:

receiving, by a computing system, requests to establish transaction accounts at a computing system, wherein the requests are associated with respective different partner entities of a plurality of partner entities, wherein the requests have different formats, wherein a first request is received via a web service provided by a partner application server that communicates the first request to the computing system using a predefined application programming interface (API), and wherein a second request is received based on user access to a microsite provided by the computing system in response to a partner web server redirecting a user to an address of the computing system and indicating a return address of the partner web server, wherein the microsite is formatted to match a site of a corresponding partner entity;

storing, by the computing system, web content for respective ones of the plurality of partner entities;

receiving, for each of the first and second requests, an identifier of the partner entity associated with the respective request;

invoking, by the computing system in response to each of the first and second requests, a same particular code block to perform an action for the respective request, wherein the action includes retrieving and providing web content to be displayed to a customer of the respective partner entity associated with the request based on the identifier of the respective partner entity, wherein the web content identifies the respective partner entity and is formatted and branded to maintain the look and feel of a website of the partner entity; and

generating and transmitting authorization responses for the first and second requests, wherein at least one of the authorization responses authorizes establishment of a transaction account and includes account information for the authorized transaction account.

2. The method of claim 1, wherein the web content includes a logo of the respective partner entity.

3. The method of claim 1, wherein the particular code block is invoked by a handler.

4. The method of claim 1, wherein the at least one of the requests includes pre-fill data from one of the plurality of partner entities, and wherein the action includes inserting the pre-fill data into the web content.

5. A system, comprising:

one or more processors; and

one or more memories having program instructions stored thereon that are executable by the one or more processors to cause the system to perform operations comprising;

maintaining web content for respective ones of a plurality of partner entities;

transmitting web content to be displayed to a user associated with respective partner entities of the plurality of partner entities, wherein the web content identifies the respective partner entity and is formatted and branded to maintain the look and feel of a website of the partner entity, wherein the transmitting includes transmitting first web content via a web service provided by a partner application server that communicates requests to the system using a predefined application programming interface (API), and transmitting second web content via a microsite provided by the system in response to a redirect from a partner web server to an address of the system, wherein the microsite is formatted to match a site of a corresponding partner entity;

receiving a first request via the web service provided by a partner application server that communicates the first request to the system using a predefined application programming interface (API) and a second request that is received based on user access to the microsite, wherein the first and second requests are from the users to establish transaction accounts;

receiving, for each of the first and second requests, an identifier of the partner entity associated with the respective request;

invoking a same particular code block to generate authorization decisions for the respective first and second requests based on the identifier of the respective partner entity; and

transmitting the authorization decisions to the users via the microsite and the web service.

6. The system of claim 5, wherein operations further comprise using at least one of an action servlet and a worker manager to invoke the particular code block.

7. A non-transitory computer-readable medium having instructions stored thereon that are executable by a computing device to perform operations comprising:

receiving requests to establish transaction accounts from a plurality of customers of respective partner entities of a plurality of partner entities, wherein the requests have different formats, wherein a first request is received via a web service provided by a partner application server that communicates the first request to the computing device using a predefined application programming interface (API), and wherein a second request is received based on user access to a microsite provided by the computing device in response to a partner web server redirecting a user to an address of the computing device and indicating a return address of the partner web server, wherein the microsite is formatted to match a site of a corresponding partner entity;

maintaining web content for respective ones of the plurality of partner entities; and

receiving, for each of the first and second requests, an identifier of the partner entity associated with the respective request;

generating, in response to each of the first and second requests, web content to be displayed to ones of the customers based on the identifier of the partner entity, wherein the web content identifies the respective partner and is formatted and branded to maintain the look and feel of a website of the partner entity; and

generating and transmitting authorization responses for the first and second requests, wherein at least one of the authorization responses authorizes establishment of a transaction account and includes account information for the authorized transaction account.

8. The non-transitory computer-readable medium of claim 7, wherein the requests include information provided by the customers.

9. The non-transitory computer-readable medium of claim 7, wherein the requests include customer information pre-filled by the respective partner entity.

10. The non-transitory computer-readable medium of claim 7, wherein the operations further comprise authenticating the requests.