Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 1 of 24
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 1 of 24
`
`
`
`EXHIBIT E
`EXHIBIT E
`
`

`

`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2006/0229998 A1
`(43) Pub. Date:
`Oct. 12, 2006
`Harrison et al.
`
`US 20060229998A1
`
`(54) PAYMENT VIA FINANCIAL SERVICE
`PROVIDER USING NETWORK-BASED
`DEVICE
`
`(76) Inventors: Mark Harrison, San Francisco, CA
`(US); Mauria Finley, San Francisco,
`CA (US)
`Correspondence Address:
`SCHWEGMAN, LUNDBERG, WOESSNER &
`KLUTH, P.A.
`P.O. BOX 2938
`MINNEAPOLIS, MN 55402 (US)
`(21) Appl. No.:
`11/095,411
`
`(22) Filed:
`
`Mar. 31, 2005
`
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`G06Q 99/00
`(52) U.S. Cl. ................................................. 705/78; 705/52
`
`(57)
`
`ABSTRACT
`
`A system includes an interface to receive a request associ
`ated with a third party at a financial service provider from a
`network-based device via a network. The network-based
`device is associated with a user. The system further includes
`a payment transfer module, responsive to receiving the
`request, to transfer a payment from the user to the third party
`via the financial service provider.
`
`18
`
`DEVICE
`APPLICAON
`
`3ROPARY SERVER
`
`3RD ARY
`APPLICACN
`
`38
`
`:
`
`NETWORKE.G., INTERNET
`
`24
`
`|
`
`NEWORK-ASE SYSEM
`! / 25
`26
`
`17
`
`14
`
`16
`
`WEBCENT
`
`10
`
`/
`
`/ 12
`
`27
`
`APSERVER
`(PROGRAMMATIC
`INTERFACE)
`
`SMS GATEWAY
`SERVER
`(SMS INTERFACE)
`
`WEBSERVER
`WEBNTERFACE)
`
`WR SERVER
`(IVRINTERFACE)
`
`
`
`
`
`APPLICATION SERVER(S)
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 2 of 24
`
`AYMEN
`APPLICATION(S)
`
`WERIFICATION
`APPLICATIONS)
`
`32
`
`28
`
`30
`
`:
`
`36
`
`DATABASE SERVERS)
`
`DATABASE(S)
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 1 of 9
`
`US 2006/0229998 A1
`
`18
`
`DEVICE
`APPCAON
`
`PROGRAMMATC
`CENT
`
`
`
`17
`
`14
`
`WEBCUENT
`
`16
`
`10
`
`
`
`
`
`
`
`
`
`NETWORK (E.G., INTERNET)
`
`NEWORK-BASE SYSTEM
`25
`
`APSERVER
`(PROGRAMMATIC
`INTERFACE)
`
`SMS GAEWAY
`SERVER
`(SMS INTERFACE)
`
`WSEs
`
`VR SERVER
`(IVRINTERFACE)
`
`
`
`
`
`
`
`
`
`32
`
`APPLICATION SERVER(S)
`
`28
`
`PAYMENT
`APPLICATION(S)
`
`VERIFICAON
`APPLICATION(S)
`
`
`
`DATABASE SERVER(S)
`
`DATABASE(S)
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 3 of 24
`
`FIGURE 1
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 2 of 9
`
`US 2006/0229998 A1
`
`APPLICATION SERVER(S) 28
`
`PAYMENT APPLICATION(S)
`42
`
`PAYMENT TRANSFER
`MODULE
`
`FRAUDPREVENTION
`APPLICATION(S)
`
`REVENUE SHARE/
`SETTLEMENT
`APPLICATION(S)
`
`DSPUTE
`RESOLUTION
`APPLICATION(S)
`
`VERIFICATION
`APPLICATION(S)
`
`DENFER
`APPLICATION(S)
`
`MESSAGING
`APPLICATION(S)
`
`MERCHANOIZING
`APPLICATION(S)
`
`LOYALTY/PROMOTION
`APPLICATION(S)
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 4 of 24
`
`FIGURE 2
`
`
`
`PUBLICATION 162
`
`LISTING 164
`DENTIFIER 166
`
`FIGURE 4
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 3 of 9
`
`US 2006/0229998 A1
`
`o
`FAMILY
`TABLE
`
`11 O
`
`
`
`
`
`PRICE
`SUBMISSIONS
`TABLE
`
`1 OO
`
`USER
`TABLE
`
`
`
`
`
`OFFERS
`TABLE
`
`ATTRIBUTES
`TABLE(S)
`
`106
`
`
`
`USER -
`Currey
`
`108
`
`104
`
`FEEDBACK
`TABLE
`
`HISTORY
`TABLE
`
`96
`TRANSACTION
`TABLE
`
`ORDER
`TABLE
`
`FIGURE 3
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 5 of 24
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 4 of 9
`
`US 2006/0229998 A1
`
`200 - N.
`
`Submit dentifier to
`FSP through
`Device
`
`Receive User
`Identification
`
`270
`
`Transfer Payment
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`22O
`
`Connect User to FSP
`through Device
`
`250
`Verify identifier
`and/or Inventory
`
`
`
`Receive Order
`Confirmation
`
`Receive Alternate
`Shipment Information
`
`264
`
`Receive Confirmation
`for Alternate Shipment
`Information
`
`
`
`Send Order
`Information, Payment
`Confirmation to Third
`Party
`
`280
`
`FIGURE 5
`
`Shipment and/or
`Receipt Sent to User
`
`290
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 6 of 24
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 5 of 9
`
`US 2006/0229998 A1
`
`300 y
`
`Open Interactive
`Communication
`Session between
`User and Third Party
`
`31 O
`
`32O
`
`350
`
`Submit dentifier to Authorize
`Payment to Third Party
`
`325
`
`Establish Communication
`Session Between FSP and User
`
`330
`
`335
`
`
`
`340
`
`345
`
`Verify User Identification and
`Financial Authorization
`
`User-Specific Information
`Provided to Third Party
`from FSP
`
`
`
`Reconnect User
`and Third Party
`
`
`
`
`
`
`
`Establish Communication
`Session Between FSP and User
`
`Verify User laentification and
`Financial Authorization
`
`Reconnect User
`and Third Party
`
`Submit Identifier to Authorize
`Payment to Third Party
`
`User-Specific information
`Provided to Third Party
`from FSP
`
`355
`
`360
`
`365
`
`370
`
`375
`
`Order Confirmation
`
`ti
`Order Confirmation
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 7 of 24
`
`380
`
`End
`
`FIGURE 6
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 6 of 9
`
`US 2006/0229998 A1
`
`
`
`APPLICATION SERVER(S)
`
`MARKETPLACE APPLICATIONS
`
`516
`
`NAVIGATION
`APPLICATION(S)
`SEARCHMODULE
`
`FXED-PRICE
`APPLICATION(S)
`
`STORE APPLICATION(S)
`
`DONATION
`APPLICATION(S)
`
`AUCTION
`APPLICATION(S)
`
`PERSONALIZATION
`APPLICATION(S)
`
`INTERNATIONALZATION
`APPLICATION(S)
`
`REPUTATION
`APPLICATION(S)
`
`MAGING
`APPLICATION(S)
`
`OFFERCREATON
`(SELLER)
`APPLICATION(S)
`
`OFFERMANAGEMENT
`(SELLER)
`APPLICATION(S)
`
`POSTOFFER
`MANAGEMENT
`APPLICATION(S)
`
`VERIFICATION
`APPLICATION(S)
`
`PAYMENT
`APPLICATION(S)
`
`RECUEST
`APPLICATION(S)
`
`56
`
`MESSAGING
`APPLICATION(S)
`
`MERCHANZING
`APPLICATION(S)
`
`OYALTY/PROMOTION
`APPLICATION(S)
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 8 of 24
`
`FIGURE 7
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 7 of 9
`
`US 2006/0229998A1
`
`600 N
`
`PUBLICATION 610
`
`SEARCH CRITERA 620
`
`FIGURE 8
`
`650 N
`
`
`
`PUBLICATION 660
`
`Search Result Set 670
`
`680
`695
`
`69
`
`695
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 9 of 24
`
`--
`
`FIGURE 9
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 8 of 9
`
`US 2006/0229998 A1
`
`7OO
`
`
`
`Receive Search
`Request
`
`710
`
`72O
`
`Conduct Search
`Of Offers
`
`Identify Offers Satisfying
`Search Request; include
`Identified Offers in Search
`Result Set
`
`730
`
`Publish Search Result Set
`
`740
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 10 of 24
`
`FIGURE 10
`
`

`

`Patent Application Publication Oct. 12, 2006 Sheet 9 of 9
`
`US 2006/0229998 A1
`
`800 N.
`
`824
`
`802
`
`804
`
`824
`
`MANMEMORY
`
`806
`
`808
`
`810
`
`VIDEO
`OSPLAY
`
`ALPHA-NUMERIC
`NPU
`DEVCE
`
`812
`
`814
`
`824 R -
`
`instructos
`INSTRUCTIONS
`
`82O
`
`CURSOR CONTROL DEVICE
`
`816
`
`NETWORK
`INTERFACE
`DEVICE
`
`826
`
`824
`
`
`
`
`
`
`
`MACHINE
`READABLE
`MEDUM
`
`822
`
`818
`
`SIGNAL GENERATION
`OEVCE
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 11 of 24
`
`FIGURE 11
`
`

`

`US 2006/0229998 A1
`
`Oct. 12, 2006
`
`PAYMENT VIA FINANCIAL SERVICE PROVIDER
`USING NETWORK-BASED DEVICE
`
`FIELD
`0001. The disclosed subject matter relates generally to
`the technical field of data processing and, in one example
`embodiment, to a method and system of a making a payment
`to a third party via a financial service provider using a
`network-based device.
`
`BACKGROUND
`0002 Vendors spend millions every year to advertise
`their products and services to potential client users. Often it
`is difficult to track the Success of specific marketing cam
`paigns. The vendor often does not know whether a particular
`television advertisement, for example, directly caused the
`consumer to buy their product. Knowledge of the specific
`prompt that caused the consumer to purchase may be very
`helpful to the vendor in crafting future successful advertis
`ing campaigns.
`0003 Order volume may be increased when client users
`immediately make a purchase in response to point of sale
`displays and other advertisements, for instance. Client users
`may be directed to physical locations, call centers, or
`websites where the client user directly interacts with the
`vendor or charity, or a distributor/representative thereof.
`Potential client users are often reluctant to make purchases,
`or to make donations because of the time involved in the
`transaction. As such, the vendor or charity often attempt to
`make the transaction as quick and as convenient as possible.
`The time involved for each client user may also include time
`to give credit card and/or other personal information, Such as
`a shipment address. Additionally, many client users may be
`concerned about identity theft, and may be reluctant to give
`credit card or other personal information to the vendor or
`charity.
`
`SUMMARY
`0004. According to one embodiment, a system includes
`an interface to receive a request associated with a third party
`at a financial service provider from a network-based device
`via a network. The network-based device is associated with
`a user. The system further includes a payment transfer
`module, responsive to receiving the request, to authorize
`and/or transfer a payment from the user to the third party via
`the financial service provider.
`0005. Other features will be apparent from the accompa
`nying drawings and from the detailed description that fol
`lows.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0006 Embodiments of the present invention are illus
`trated by way of example and not limitation in the Figures
`of the accompanying drawings, in which like references
`indicate similar elements and in which:
`0007 FIG. 1 illustrates a network diagram depicting a
`system, according to an example embodiment of the present
`invention, having a client-server architecture.
`0008 FIG. 2 illustrates a block diagram showing an
`application server in an example embodiment of the present
`invention.
`
`0009 FIG. 3 illustrates a high-level entity-relationship
`diagram, illustrating various tables that may be maintained
`within one or more databases, according to an example
`embodiment.
`0010 FIG. 4 illustrates an interface according to an
`example embodiment.
`0011 FIG. 5 illustrates a flow chart of a method, accord
`ing to an example embodiment of the present invention.
`0012 FIG. 6 illustrates a flow chart of a method, accord
`ing to an example embodiment of the present invention.
`0013 FIG. 7 illustrates a block diagram showing an
`application server in another example embodiment of the
`present invention.
`0014 FIG. 8 illustrates an interface according to an
`example embodiment.
`0015 FIG. 9 illustrates an interface according to an
`example embodiment.
`0016 FIG. 10 illustrates a flow chart of a method,
`according to an example embodiment of the present inven
`tion.
`0017 FIG. 11 illustrates a diagrammatic representation
`of a machine in the form of a computer system within which
`a set of instructions, for causing the machine to perform any
`one or more of the methodologies discussed herein, may be
`executed, according to an example embodiment.
`
`DETAILED DESCRIPTION
`00.18 Embodiments describe a method and a system to
`receive a request associated with a third party at a financial
`service provider from a network-based device via a network.
`The network-based device is associated with a user. A
`payment transfer module, responsive to receiving the
`request, transfers a payment from the user to the third party
`via the financial service provider.
`0019. In the following description, for purposes of expla
`nation, numerous specific details are set forth in order to
`provide a thorough understanding of embodiments of the
`present invention. It will be evident, however, to one skilled
`in the art that embodiments of the present invention may be
`practiced without these specific details.
`0020. In embodiments described with respect to FIGS. 1
`to 6, the client user may use the identifier to order and pay
`for an offer associated with the third party through the
`network-based device and/or a mobile device. The user
`submits the identifier through the device to authorize pay
`ment transfer via the financial service provider to the third
`party, such as a vendor or a charity, as part of ordering a
`product, a promotion, or a service, or making a donation.
`The identifier may be submitted through a web browser on
`the device, through SMS messaging on the device, through
`IVR, through an application on the device, and/or through
`WAP for example. The device may connect to the financial
`service provider over a network. The system may read a
`cookie or other identifier from the network-based device to
`automatically identify and/or authenticate the user. The
`payment may be transferred from the account of the user to
`the account of the third party via the financial service
`provider. The user account information, e.g. shipment
`address, may be given to the third party from the financial
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 12 of 24
`
`

`

`US 2006/0229998 A1
`
`Oct. 12, 2006
`
`service provider along with the order, while the user pay
`ment details may not be given to the third party. For a
`donation, user account information may be unknown to the
`charity.
`Platform Architecture
`0021
`FIG. 1 illustrates a network diagram depicting a
`system 10 having a client-server architecture, according to
`an example embodiment of the present invention. A system,
`in the example form of a network-based system 12, provides
`server-side functionality, via a network 14 (e.g., the Internet,
`a public or private telephone network (wireline or wireless),
`a private wireless network using technologies Such as Blue
`tooth or IEEE 802.11x or other networks) to one or more
`clients. FIG. 1 illustrates, for example, a web client 16 (e.g.,
`a browser, such as the Internet ExplorerR) browser devel
`oped by Microsoft(R), and a programmatic client 18 execut
`ing on respective client machines 20 and 22, e.g. on a
`network-based device. Additionally, a device application 17
`may execute on a client machine 21. Further, while the
`system 10 shown in FIG. 1 employs a client-server archi
`tecture, embodiments are of course not limited to Such an
`architecture, and could equally well find applications in a
`distributed, or peer-to-peer, architecture system.
`0022. The client machines, including network-based
`device(s) 20, 21, 22, may include a mobile device, a palmtop
`computer, a laptop computer, a desktop computer, a personal
`digital assistant, a cellular telephone, a communications
`device, a wireless telephone, a land-line telephone, a control
`system, a camera, a scanner, a television, television cable, a
`telephone with a web browser, a facsimile machine, a
`printer, a pager, and/or a personal trusted device. The device
`20, 21, 22 may include a card, Such as a Smart card, a
`magnetic card, and/or a key card. The device may include a
`telephone or any device capable of Short Messaging Service
`(SMS) messaging, multimedia messaging service (MMS)
`messaging and/or generating audio tones, such as dual-tone
`multi-frequency (DTMF) tones. The device may be browser
`enabled. The device may engage in an interactive message
`and/or open communication session, Such as SMS, elec
`tronic mail, XHTML, Wireless Application Protocol (WAP),
`web, interactive voice response (IVR) and/or other mobile
`interfaces. The interactive messaging or open communica
`tion session may involve multiple technology modalities,
`e.g. the client user may engage the system via SMS and
`receive a responsive communication from the IVR Server or
`as an SMS with an embedded hyperlinked URL directing the
`client user's device to a WAP or web page. A hyperlinked
`URL may be delivered directly to the device from the
`application server(s) 28 and may be used to access a web site
`or a microbrowser, such as a WAP site. The device 20, 21,
`22 may enable mobile videophone communications, digital
`television signals, and/or digital radio signals. The device
`may include a receiver to receive near field communications
`as described in more detail herein. The scanner device may
`include a bar code reader/scanner, a Radio Frequency Inter
`face System (RFIS) reader, and/or a symbol reader/scanner.
`0023 Turning specifically to the network-based system
`12, an Application Program Interface (API) server 24, a
`Short Messaging Service (SMS) Gateway Server 25, a web
`server 26, and an Interactive Voice Response (IVR) server
`27 may be coupled to, and may provide programmatic, SMS,
`web, and IVR interfaces, respectively to, one or more
`
`application servers 28. The devices may use one or more of
`these interfaces to access the application server(s) 28.
`0024 For example, the web client 16 may access the
`application server(s) 28 via the web interface supported by
`the web server 26. The web interface may include a web
`browser or any microbrowser, such as XHTML or WAP.
`Similarly, the programmatic client 18 accesses the various
`services and functions provided by the application server(s)
`28, via the programmatic interface provided by the API
`server 24 and/or the web server 26. In an additional embodi
`ment, an application Supported by one or more applications
`of the application server(s) may be downloadable to the
`network-based device. The device(s) may host the interface
`associated with the one or more applications of the appli
`cation server(s) 28. The interface on the device may be an
`API interface, an SMS interface, a web interface, and/or an
`IVR interface. Consumer wireless device platforms, such as
`Java 2 Platform Micro Edition (J2ME), J2SE and J2EE
`allow developers to use Java and a wireless toolkit to create
`applications and programs for the device 22. The J2ME
`interface may include an application programming interface
`(API) for the device. The application of the programmatic
`client may also access the Internet using, for example,
`Binary Runtime Environment for Wireless (BREW).
`0025 The device application 17 executed on the client
`machine 21 may access the application server(s) 28 via the
`web interface of the web server. The application 17 may be
`selected on the device and the Internet may be launched in
`a background. The application 17 may additionally or alter
`natively access the server(s) 28 via the IVR interface of the
`IVR server 27, via the SMS interface of the SMS Gateway
`server 25, and/or via the programmatic interface of the API
`server 24. In an embodiment, the downloaded application
`described herein may include the device application 17.
`0026. The application server(s) 28 may host one or more
`verification application(s) 30 and one or more payment
`application(s) 32. The application server(s) 28 are, in turn,
`shown to be coupled to one or more database servers 34 that
`facilitate access to one or more databases 36. The verifica
`tion application(s) 30 may provide verification of an order.
`Verification may include analysis of the order, such as from
`an identifier 166, to ensure that the identifier corresponds
`with a third party offer in the database(s) 36. Further,
`verification may include ensuring that the offer, such as a
`product, a service or a donation opportunity, still exists from
`the third party. Verification may additionally or alternatively
`include inventory analysis with respect to the offer, e.g.
`verifying the product is in Stock. The verification applica
`tion(s) 30 may communicate with a third party application
`38 executing on a third party server 40 to determine if the
`identifier corresponds with the third party offer, to determine
`if the offer still exists, and/or to determine if the product is
`in stock, for example.
`0027. The payment application(s) 32 may provide a num
`ber of payment services and functions to users, such as client
`users. The payment application(s) 32 may allow users to
`accumulate value (e.g., in a commercial currency, Such as
`the U.S. dollar, or a proprietary currency, such as “points')
`in accounts, and then later to redeem the accumulated value
`for an offer (e.g., goods, services, promotions, or donation
`opportunities) offered via a listing 164, as shown in FIG. 4.
`The payment applications, e.g. a financial service provider,
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 13 of 24
`
`

`

`US 2006/0229998 A1
`
`Oct. 12, 2006
`
`may also extend credit to user, and/or may also have access
`to other funding sources to complete transactions—e.g. a
`credit card, a bank account, and/or a credit line. The financial
`service provider may operate as a money transmitter or a
`bank, for instance, and may operate using the payment
`application(s) 32.
`0028. The third party or vendor may receive from the
`payment application(s) and/or the financial service provider
`(FSP): information regarding a requested order for a prod
`uct, a service, or a donation amount (e.g. the identifier),
`information regarding the shipment address specified by the
`client user, and the payment confirmation from the financial
`service provider as specified above. The payment applica
`tion(s) and/or the financial service provider may secure
`financial information of the client user with respect to the
`third party. The FSP may not be sharing the financial
`information of the client user with the third party. For
`example, the payment may be received by the third party
`exclusive of the payment method and/or financial informa
`tion of the client user, including credit card information,
`bank information and/or other client user account informa
`tion.
`0029. The device 20, 21, 22 may host the interface
`associated with the payment application(s) 32 of the serv
`er(s) 28. The web client 16, the device application 17, and/or
`the programmatic client 18 may be associated with the
`financial service provider (FSP). In an additional embodi
`ment, the web client 16, the device application 17, and/or the
`programmatic client 18 may be associated with the third
`party application 38.
`0030 The payment application(s) and/or the financial
`service provider may have an infrastructure to pay a plural
`ity of vendors for a plurality of transactions each day. The
`payment application(s) and/or the financial service provider
`may operate independent of the third party. The payment
`application(s) and/or the financial service provider may be
`related to the third party, in other embodiments.
`0031. The payment applications 32 may also be imple
`mented as a standalone software program, which does not
`necessarily have networking capabilities. In this embodi
`ment, the device may be directly connected to the payment
`application(s) 32, without using the network 14.
`0032. The payment application(s) and/or the financial
`service provider may have access to the database 36 having,
`for example, the personal user account information through,
`for example, the database server(s) 34. The user account
`information may include payment information associated
`with the client user and an address destination of the client
`user, for example. The web client 16, the device application
`17, and/or the programmatic client 18 may operate a pro
`gram Supported by the one or more database server(s) 34.
`The database server(s) 34 may support one or more account
`information links on a user interface of the network-based
`device, for example, using the web client 16. By accessing
`the database server(s)34, the client user may add, amend or
`delete account information of the client user, among other
`information. In an embodiment, the client user may select a
`default shipment address and a default payment method in
`the payment application(s) discussed herein. Depending on
`whether goods are purchased, a service is requested, a
`donation is made, or a promotion is selected, a default
`shipment address, e.g. electronic mail address or a residen
`
`tial address, a business addresses, or a P.O. Box, may be
`selected by the client user in the payment application(s). One
`of the default payment methods may include direct transfers
`from system account balances, internal credit, a gift certifi
`cate, a bank account, a debit card, buyer credit, and/or a
`credit card.
`0033. The network 14 may include a mobile telephone
`network, a wireless wide area network (WWAN), a wireline
`telephone network, a wireless local area network (wireless
`LAN or WLAN), a wireless Metropolitan Area Network
`(MAN), and/or a wireless personal area network (PAN)
`(e.g., a Bluetooth R) network). Other network-based tech
`nologies that may be used to connect include PON, VSAT
`satellite, Micro-impulse Radar, Radio Frequency identifica
`tion (RFID), UltraWide Band, and/or Infrared. The network
`based device may connect to the web using mobile internet
`exchange, e.g. Wireless Application Protocol (WAP) and/or
`Hypertext Transport Protocol (HTTP).
`0034. The network 14 may allow the network-based
`device 20, 21, 22 to communicate with the third party, e.g.
`a vendor or a charity, and/or to communicate with the
`payment application(s) and/or the financial service provider,
`among others having the capability to communicate through
`any various means.
`0035 FIG. 1 also illustrates the third party application 38
`as having programmatic access to the network-based system
`12 via the programmatic interface provided by the API
`server 24. For example, the third party application 38 may,
`utilizing information shared with the network-based system
`12, Support one or more features or functions on any virtual
`or physical medium, Such as a website, billboard, or maga
`zine, hosted by the third party. The third party website may,
`for example, provide one or more promotional, marketplace
`or payment functions that are Supported by the relevant
`applications of the network-based system 12. For example,
`the third party website may display an interface similar to an
`interface 160 of FIG. 4.
`0036) The verification application(s) 30 may communi
`cate with the third party application 38 to verify an order, as
`discussed above. The third party may receive, from the
`payment application(s) and/or verification application(s),
`order information, shipment information, and an associated
`payment and/or payment confirmation. The third party
`application 38 may receive and process the order, send a
`virtual receipt to the payment application(s) 32, and forward
`the order to the client user. For services and/or donations, the
`third party may receive a requested order and the payment
`confirmation, exclusive of the user contact information, Such
`as a shipment address. In an additional embodiment, the
`service provider or charity may receive client user contact
`information and may send a receipt to the client user.
`Application Server(s)
`0037 FIG. 2 illustrates a block diagram showing appli
`cation server(s) that are part of the network-based system 12,
`in an example embodiment of the present invention. In this
`embodiment, the payment application(s) 32, the verification
`application(s) 30, identifier application(s) 50, messaging
`application(s) 54, merchandising application(s) 56, and/or
`loyalty/promotion application(s) 58 may be hosted by the
`application server(s) 28 of the network-based system 12.
`
`Case 6:21-cv-01101-ADA Document 25-5 Filed 04/14/22 Page 14 of 24
`
`

`

`US 2006/0229998 A1
`
`Oct. 12, 2006
`
`0038. The payment application(s) 32 may include a pay
`ment transfer module 42, fraud prevention application(s) 44,
`revenue share/settlement application(s) 46, and/or dispute
`resolution application(s) 48.
`0.039 The payment transfer module 42 may, responsive
`to the server(s) receiving the identifier 166 (of FIG. 4),
`transfer a payment from the user to the third party via the
`payment application(s) and/or the financial service provider.
`The payment may be automatically transferred, as discussed
`herein.
`0040. The fraud prevention application(s) 44 may imple
`ment various fraud detection and prevention mechanisms to
`reduce the occurrence of fraud within the system 12. The
`fraud prevention application(s) may prevent fraud with
`respect to the third party and/or the client user in relation to
`any part of the request, payment, information flows and/or
`request fulfillment. Fraud may occur with respect to unau
`thorized use of financial instruments, non-delivery of goods,
`and abuse of personal information.
`0041. The revenue share/settlement application(s) 46
`may distribute payments associated with an order to multiple
`accounts. For example, two independent third parties. Such
`as a content provider and a content distributor, may each
`receive a certain percentage of a sale in their respective
`acCOunts.
`0042. The dispute resolution application(s) 48 may pro
`vide mechanisms whereby disputes arising between trans
`acting parties may be resolved. For example, the dispute
`resolution applications 48 may provide guided procedures
`whereby the parties are guided through a number of steps in
`an attempt to settle a dispute. In the event that the dispute
`cannot be settled via the guided procedures, the dispute may
`be escalated to a mediator or arbitrator.
`0043. The identifier application(s) 50 may generate the
`identifier 166 based on selected criteria, e.g. the source (the
`third party) associated with the offer, the type of offer
`(service, product, promotion, donation opportunity) and/or
`the placement of the identifier (television ad, magazine ad,
`and/or client user device).
`0044) The identifier application(s) 50 may be associated
`with an identifier prompt, Such as a prompt link on the
`network-based device. For example, the prompt link may be
`a web link and the client user may "click through the
`hypertext link on the network-based device to be presented
`with a webpage interface Supported by the application(s)32.
`The prompt link may additionally or alternatively use WAP.
`SMS/MMS, IVR, and/or J2ME, as described herein. The
`link may allow the client user to submit the identifier to
`authorize a payment to the third party, e.g. as part of a
`product request.
`0045. The third party application(s) 38 may keep track of
`Success levels for respective marketing and advertisement
`campaigns by monitoring identifiers associated with each
`point of sale. The identifier application(s) 50, for instance,
`may receive the identifier 166 upon submission thereof
`through the device by the client user, and may forward the
`appropriate data to the third party application(s) 38. Addi
`tionally or alternatively, the identifier application(s) 50, for
`instance, or another application server may track Success
`levels of campaigns and provide this information to the third
`party, for instance.
`
`0046) The application server(s) 28 may include messag
`ing applications 54. The messaging applications 54 are
`responsible for the generation and delivery of messages to
`client users and third parties of the network-based system
`12. Such messages, for example, advise client users regard
`ing the status of products (e.g., providing “out of Stock
`notices to client users). Third parties may be notified of a
`product order, payment confirmation and/or shipment infor
`mation. The messaging application(s) 54 may use SMS,
`IVR, email, or any other appropriate messaging application.
`0047 The network-based system 12 itself, or one or more
`parties that transact via the system 12, may operate mer
`chandising programs that are Supported by one or more
`merchandising applications 56. The merchandising applica
`tions 56 Support various merchandising functions that are
`made available to third parties to enable sellers to increase
`sales via the system 12. The merchandising applications 56
`also operate the various merchandising features that may be
`invoked by third parties, and may monitor and track the
`Success of merchandising strategies employed by the third
`parties. For example, the merchandising application(s) 56
`may monitor efficacy of particular merchandising cam
`paigns using associated identifiers that may be used in the
`ordering process, as described herein.
`0048. The network-based system 12 itself, or one or more
`parties that transact via the system 12, may operate loyalty
`programs and other types of promotions that are Supported
`by one or more loyalty/promotions applications 58. For
`example, a buyer/client user may earn loyalty or promotions
`points for each transaction established and/or concluded
`with a particular seller/third party, and may be offered a
`reward for which accumulated loyalty points can be
`redeemed.
`
`Data Structures
`0049 FIG. 3 illustrates a high-level entity-relationship
`diagram, illustrating various tables 90 that may be main
`tained within the databases 36 according to an example
`embodiment. The tables 90 may be utilized by and support
`th