# US 8,788,376 B2 · System, method and computer program product for an acquisition partner interface for integrating multiple partner channels into a transaction account issuer platform > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,788,376 B2 - Document ID: US8788376B2 - Status: Granted - Kind: B2 - Application number: 11/275,066 - Filed: 2005-12-07 - Published: 2007-08-23 - Granted: 2014-07-22 - Earliest claimed: 2005-12-07 - Assignees: III Holdings l, LLC - Applicants: Simon R. Bentley; Deborah Louise Craft; Melanie Anne Dunn; Adeyemi O. Kayode; Chintan M. Mehta; Denis George Perracchio; Sejal Dilip Vora - Inventors: Simon R. Bentley; Deborah Louise Craft; Melanie Anne Dunn; Adeyemi O. Kayode; Chintan M. Mehta; Denis George Perracchio; Sejal Dilip Vora - Web page: https://patentgrep.com/patent/US8788376B2 ## CPC - G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes - G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] - G06Q 30/00: Commerce - G06Q 30/02: Marketing; Price estimation or determination; Fundraising - G06Q 50/188: {Electronic negotiation} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## 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 ### Claim 1 A method comprising: receiving, by a computer-based system for interfacing a plurality of disparate partner systems to a transaction account issuer system, a request for a new transaction account from a disparate partner system, wherein the request is received through one of: a web service, a partner portal, and a partner microsite, and wherein the at least one of the web service, the partner portal, and the partner microsite are formatted to resemble a website associated with the partner; identifying, by the computer-based system, a business partner associated with the request for the new transaction account; delegating, by the computer-based system, an action associated with the request for the new transaction account to a handler, wherein the handler is at least one of an action object, an action servlet and a worker manager; invoking, by the computer-based system and using the handler, a worker to perform the action, wherein the worker is a code block; communicating, by the computer-based system, an outcome related to the action; and re-using, by the computer-based system, the worker and the handler to process another request for a new transaction account. ### Claim 2 (depends on 1) The method of claim 1, wherein the identifying further comprises extracting a partner identifier from an XML file associated with the request. ### Claim 3 (depends on 2) The method of claim 2, wherein the XML file includes personal information associated with a transaction account applicant. ### Claim 4 (depends on 1) The method of claim 1, further comprising verifying, by the computer-based system, an identifier associated with the business partner. ### Claim 5 (depends on 1) The method of claim 1, further comprising transmitting, by the computer-based system and using at least one of: a content management utility worker, a partner pre-fill worker, a transformation worker, an itemlist worker, and a rendered worker, data associated with a user interface. ### Claim 6 (depends on 1) The method of claim 1, further comprising processing, by the computer-based system and using collection of utility workers, the request for the new transaction account. ### Claim 7 (depends on 1) The method of claim 1, further comprising authenticating, by the computer-based system, the partner system. ### Claim 8 (depends on 1) The method of claim 1, further comprising communicating, by the computer-based system, an action to the transaction account issuer system through an adapter coupled to the transaction account issuer system and a delegate, wherein the delegate deploys actions to the handler. ### Claim 9 (depends on 1) The method of claim 1, further comprising aggregating, by the computer-based system, data associated with the request for the new transaction account and data stored in the transaction account issuer system, and communicating the aggregated data to a handler. ### Claim 10 (depends on 1) The method of claim 1, further comprising receiving, by the computer-based system, the request for the new transaction account through a web service that is provided by the transaction account issuer system, wherein the partner provides a webpage for collecting application data. ### Claim 11 (depends on 1) The method of claim 1, further comprising receiving, by the computer-based system, the request for the new transaction account through a partner portal that comprises a private URL hosted by a transaction account issuer. ### Claim 12 (depends on 1) The method of claim 1, wherein the identifying the business partner associated with the request is performed by an API application server. ### Claim 13 (depends on 1) The method of claim 1, wherein the delegating the action associated with the request to the handler is performed by an API application server. ### Claim 14 (depends on 1) The method of claim 1, wherein the invoking the worker to perform the action is performed by an API application server. ### Claim 15 (depends on 1) The method of claim 1, wherein the delegating the action associated with the request to the handler is performed by an electronic acquisition (“EACQ”) system. ### Claim 16 (depends on 1) The method of claim 1, wherein the invoking the worker to perform the action is performed by an electronic acquisition (“EACQ”) system. ### Claim 17 (depends on 1) The method of claim 1, further comprising communicating, by the computer-based system and through an electronic acquisition system (“EACQ”), the request for the new transaction account to the transaction account issuer system. ### Claim 18 A system comprising: a tangible, non-transitory memory communicating with a processor for interfacing a plurality of disparate partner systems to a transaction account issuer system, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising: receiving, by the processor, a request for a new transaction account from a disparate partner system, wherein the request is received through one of: a web service, a partner portal, and a partner microsite, and wherein the at least one of the web service, the partner portal, and the partner microsite are formatted to resemble a website associated with the partner; identifying, by the processor, a business partner associated with the request for the new transaction account; delegating, by the processor, an action associated with the request for the new transaction account to a handler, wherein the handler is at least one of an action object, an action servlet and a worker manager; invoking, by the processor and using the handler, a worker to perform the action, wherein the worker is a code block; communicating, by the processor, an outcome related to the action; and re-using, by the processor, the worker and the handler to process another request for a new transaction account. ### Claim 19 An article of manufacture including a non-transitory, tangible computer readable medium having instructions stored thereon that, in response to execution by a computer-based system for interfacing a plurality of disparate partner systems to a transaction account issuer system, cause the computer-based system to perform operations comprising: receiving, by the computer-based system, a request for a new transaction account from a disparate partner system, wherein the request is received through one of: a web service, a partner portal, and a partner microsite, and wherein the at least one of the web service, the partner portal, and the partner microsite are formatted to resemble a website associated with the partner; identifying, by the computer-based system, a business partner associated with the request for the new transaction account; delegating, by the computer-based system, an action associated with the request for the new transaction account to a handler, wherein the handler is at least one of an action object, an action servlet and a worker manager; invoking, by the computer-based system and using the handler, a worker to perform the action, wherein the worker is a code block; communicating, by the computer-based system, an outcome related to the action; and re-using, by the computer-based system, the worker and the handler to process another request for a new transaction account.