Biller-side biller directory and payments engine architecture

Patent metadata

Field	Value
Publication number	US-2024320718-A1
Application number	US-201916704453-A
Country	US
Kind code	A1
Filing date	Dec 5, 2019
Priority date	Aug 30, 2018
Publication date	Sep 26, 2024
Grant date	—

Abstract

A biller processor computing system is associated with a biller. The biller processor computing system includes a processing resource, a memory resource, and computer-executable instructions stored thereon and embodied in a biller processor application programming interface (API) engine. The instructions, when executed by the processing resource, cause the biller processor computing system to extract a payer identifier from an electronic bill (e.g., an electronic bill received from the biller). Based at least on the payer identifier, a corresponding electronic token is retrieved from data storage media. The electronic token relates to payer authentication information for a biller computing system, which is communicatively coupled to the biller processor computing system. The electronic token is included in the electronic bill, and the electronic bill is transmitted to a payer computing system.

First claim

1 . A biller processor computing system associated with a plurality of billers, the biller processor computing system communicatively coupled to a biller exchange computing system, a plurality of biller computing systems, and a payer computing system and comprising a processing resource, a memory resource, and computer-executable instructions stored thereon and embodied in a biller processor application programming interface (API) engine, the instructions, when executed by the processing resource, causing the biller processor computing system to:
receive, by the biller processor computing system from the bill exchange computing system, a bill inquiry regarding an electronic bill, wherein receiving the bill inquiry comprises:
displaying, on the payer computing system via a single distributed API, a plurality of tiles, each of the plurality of tiles structured to provide information in a progressive disclosure fashion such that an initial amount of content provided by a respective tile is less than a subsequent amount of content provided by the respective tile in response to a user interaction with the respective tile,
in response to receiving a tile user interaction with a billers management tile of the plurality of tiles, displaying, on the payer computing system via the single distributed API, a plurality of dynamically generated icons each associated with one biller of the plurality of billers, the dynamically generated icons comprising color icons associated with a first set of billers of the plurality of billers that were previously added by the payer computing system and grayscale icons associated with a second set of billers of the plurality of billers that were not added by the payer computing system, wherein generating each of the grayscale icons comprises:
generating a temporary color icon by combining a generic icon with properties of a corresponding biller,
for each pixel of the temporary color icon, determining a grayscale pixel color value based on red, green, and blue color values of the pixel, and
for each pixel of the temporary color icon, converting the red, green, and blue color values with the grayscale pixel color value; and

receiving, from the payer computing system via the single distributed API, an icon user interaction associated with one icon of the grayscale icons, the icon user interaction indicative of the bill inquiry from a biller computing system of the plurality of biller computing systems;
receive, by the biller processor computing system via the biller processor API engine from the biller computing system, an electronic bill; generate and send, by the biller processor computing system via the biller exchange computing system and the single distributed API, a one-time authorization code to the payer computing system; extract, by the biller processor computing system in response to being presented with the one-time authorization code by the payer computing system via the single distributed API, a payer identifier from the electronic bill; based at least on the payer identifier, retrieve, by the biller processor computing system from data storage media associated with the biller exchange computing system, an electronic authentication token generated by the biller processor computing system, the electronic authentication token comprising a de-identified reference string for the biller computing system, wherein generating the electronic authentication token comprises:
generating, by the biller processor computing system, a plurality of de-identified reference strings using a plurality of random numerical or alphanumeric characters, the plurality of de-identified reference strings comprising the de-identified reference string,
generating, by the biller processor computing system, a cross-reference table stored on the data storage media associated with the biller exchange computing system, the cross-reference table comprising the plurality of de-identified reference strings and a plurality of payer authentication information,
linking, by the biller processor computing system in the cross-reference table, the plurality of de-identified reference strings to the plurality of payer authentication information, wherein the de-identified reference string is linked to payer authentication information of the plurality of payer authentication information in the cross-reference table, and
including, by the biller processor computing system, the de-identified reference string in the electronic authentication token;
amend, by the biller processor computing system, the electronic bill, comprising including the electronic authentication token in the electronic bill; tokenize, by the biller processor computing system, the electronic bill using at least one protocol of an internet protocol (IP), a transmission control protocol (TCP), a hypertext transfer protocol (http), a simple object access protocol (SOAP), or a file transfer protocol (FTP), wherein the biller processor API engine determines the at least one protocol used to tokenize the electronic bill; and cause, by the biller processor computing system and via the biller exchange computing system and the single distributed API, the tokenized electronic bill to be transmitted to the payer computing system.

2 - 4 . (canceled)

5 . The biller processor computing system of claim 1 , wherein the instructions, when executed by the processing resource, cause the biller processor computing system to:
receive, from the biller computing system, the electronic bill, wherein the electronic bill is structured according to a format decodable by the biller processor API engine.

6 . The biller processor computing system of claim 5 , wherein the instructions, when executed by the processing resource, cause the biller processor computing system to:
receive a data set comprising a plurality of electronic bills comprising the electronic bill; parse the data set, comprising extracting at least one data subset from the plurality of electronic bills, wherein the at least one data subset comprises and is structured to aggregate, in a single API message, the electronic bill and one or more electronic bills for one of a particular payer, a particular account for the particular payer, and a particular financial institution; and for each of the electronic bill and the one or more electronic bills in the at least one data subset,
identify at least one of the particular payer and the particular account,
based on information regarding the at least one of the particular payer and the particular account, retrieve the electronic authentication token, and
amend the respective each electronic bill or the one or more electronic bills, comprising including the electronic authentication token in the electronic bill.

7 . The biller processor computing system of claim 6 , wherein the at least one data subset is structured to aggregate, in the single API message, the electronic bill and the one or more electronic bills for the particular financial institution, the particular financial institution being an originating deposit financial institution (ODFI).

8 . The biller processor computing system of claim 6 , wherein the at least one data subset is structured to aggregate, in the single API message, the electronic bill and the one or more electronic bills for the particular financial institution, the particular financial institution being an auto-pay financial institution for each of a plurality of payers found in the at least one data subset.

9 . The biller processor computing system of claim 1 , wherein the electronic bill is generated in response to an inquiry API message received from the payer computing system, the inquiry API message structured to be decodable by the biller processor API engine and comprising at least one of an i

Assignees

• Wells Fargo Bank Na

Inventors

• Hecht Alan W
• Barkas Sotirios
• Kirk Ann M
• Rozovski Peter
• Shen Peter L
• Yap Chate

Classifications

• G06Q20/3821

  Electronic credentials · CPC title

• G06Q20/385

  using an alias or single-use codes · CPC title

• G06Q20/321

  using wearable devices · CPC title

• G06Q20/3223

  Realising banking transactions through M-devices · CPC title

• G06Q20/023

  the neutral party being a clearing house · CPC title