WO2013012876A1

WO2013012876A1 - Merchant control platform apparatuses, methods and systems

Info

Publication number: WO2013012876A1
Application number: PCT/US2012/047092
Authority: WO
Inventors: Edward Katzin
Original assignee: Visa International Service Association
Priority date: 2011-07-17
Filing date: 2012-07-17
Publication date: 2013-01-24

Abstract

The MERCHANT CONTROL PLATFORM APPARATUSES, METHODS AND SYSTEMS ("MCP") transform merchant onboarding data via MCP components into merchant enrollment record. In one implementation, a method is disclosed, comprising: receiving a merchant enrollment request via a user interface; identifying a merchant type; automatically retrieving a merchant enrollment template based on the identified merchant type; prompting a merchant to submit registration information requested by the merchant enrollment template via a user interface; obtaining merchant submitted registration information from the merchant enrollment template via the user interface; verifying merchant status via background check procedures based on the submitted registration information; and generating a merchant enrollment record.

Description

1 MERCHANT CONTROL PLATFORM APPARATUSES, METHODS

2 AND SYSTEMS

3 [o o o i] This application for letters patent discloses and describes various novel

4 innovations and inventive aspects of MERCHANT CONTROL PLATFORM technology

5 (hereinafter "disclosure") and contains material that is subject to copyright, mask work,

6 and/or other intellectual property protection. The respective owners of such intellectual

7 property have no objection to the facsimile reproduction of the disclosure by anyone as

8 it appears in published Patent Office file/records, but otherwise reserve all rights.

9 PRIORITY CLAIM

10 [0002 ] This application claims priority under Patent Cooperation Treaty and 35

11 USC § 119 and § 120 to United States provisional patent application serial no.

12 61/508,679, filed July 17, 2011, entitled "Cross Channel Merchant Consumer Bridging

13 Apparatuses, Methods And Systems," attorney docket no. 66US01 I 20270-193PV, United

14 States provisional patent application serial no. 61/618,670, filed March 30, 2012,

15 entitled "Developer Console And Merchant Control Panel Apparatuses, Methods And

16 Systems," attorney docket no. 236US01 I 20270-227PV, United States provisional patent

17 application serial no. 61/570,230, filed December 13, 2011, entitled "Dynamic Widget is Generator Apparatuses, Methods And Systems," attorney docket no. 117US01120270-

19 198PV and United States application serial no. 13/278,173, filed October 20, 2011,

20 entitled "Flexible Monetization Service Apparatuses, Methods And Systems," attorney

21 docket no. PS-99013US01I 20270-174US.

22 [0003] The entire contents of the aforementioned applications are expressly

23 incorporated by reference herein.

24 FIELD

25 [0004] The present innovations generally address apparatuses, methods, and systems for electronic transactions, and more particularly, include MERCHANT CONTROL PLATFORM APPARATUSES, METHODS AND SYSTEMS ("MCP").

BACKG ROUN D

[0005 ] A merchant is a manufacturer, a retailer or a distributor who produces, distributes or sells products. Consumers may shop with a merchant for products and pay for the product at a point of sale (POS) terminal at the merchant store to complete the purchase. Merchants who allow a consumer to pay with a credit card need to register for credit card payment. A merchant may send personnel to a local bank branch to interact with a bank representative to establish a credit card payment channel for the merchant store. Upon registration, the merchant can attach a label "major credit card accepted" at its POS terminal so that a consumer can pay by credit cards.

BRI EF DESCRI PTION OF TH E DRAWI NGS

[ 0006 ] The accompanying appendices, drawings, figures, images, etc. illustrate various example, non-limiting, inventive aspects, embodiments, and features ("e.g.," or "example(s)") in accordance with the present disclosure: [ 0007] FIGURES lA-B show block diagrams illustrating example aspects of the MCP;

[ 0008 ] FIGURES 2A-2B show a block diagram illustrating data flows between MCP affiliated entities within embodiments of MCP; [ 0009 ] FIGURES 3A-3H provide logic flow diagrams illustrating consumer merchant onboarding within embodiments of the MCP; [ 0010 ] FIGURES 4 provides a logic flow diagram illustrating merchant analytics based campaign set up within embodiments of the MCP; [ 0011] FIGURES 5 and 6A-6F provide exemplary user interface diagrams illustrating example aspects of merchant analytics and campaign set-up with the MCP; [ 0012 ] FIGURES 7A-22B show user interface diagrams illustrating example aspects of merchant control platform in some embodiments of the MCP; [ 0013 ] FIGURES 23A-26C show user interface diagrams illustrating example aspects of merchant onboarding in some embodiments of the MCP; [ 0014] FIGURES 27-3 oC show logic flow diagrams illustrating example aspects of merchant services upon onboarding in some embodiments of the MCP;

[ 0015 ] FIGURE 31 shows a datagraph diagram illustrating example aspects of transforming a user checkout request input via a User Purchase Checkout ("UPC") component into a checkout data display output; [ 0016 ] FIGURE 32 shows a logic flow diagram illustrating example aspects of transforming a user checkout request input via a User Purchase Checkout ("UPC") component into a checkout data display; [ 0017] FIGURES 33A-B show datagraph diagrams illustrating example aspects of transforming a user virtual wallet access input via a Purchase Transaction Authorization ("PTA") component into a purchase transaction receipt notification; [ 0018 ] FIGURES 34A-B show logic flow diagrams illustrating example aspects of transforming a user virtual wallet access input via a Purchase Transaction Authorization ("PTA") component into a purchase transaction receipt notification; [ 0019 ] FIGURES 35A-B show datagraph diagrams illustrating example aspects of transforming a merchant transaction batch data query via a Purchase Transaction Clearance ("PTC") component into an updated payment ledger record; [ 0020 ] FIGURES 36A-B show logic flow diagrams illustrating example aspects of transforming a merchant transaction batch data query via a Purchase Transaction Clearance ("PTC") component into an updated payment ledger record; and

[ 0021] FIGURE 37 shows a block diagram illustrating example aspects of a MCP controller. [ 0022 ] The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in Figure l. Reference number 201 is introduced in Figure 2, etc.

DETAILED DESCRIPTION

[ 0023 ] The MERCHANT CONTROL PLATFORM APPARATUSES, METHODS AND SYSTEMS (hereinafter "MCP") provides an advertising tracking and payment platform which combines online tracking of consumer behaviors and merchant advertising into purchase data. In one embodiment, MCP may provide a platform for a merchant to automatically enroll with a payment platform (e.g., Visa V.me wallet service, etc.), and provide consumer purchasing analytics for the merchant to devise a campaign.

[ 0024] Integration of an electronic wallet, a desktop application, a plug -in to existing applications, a standalone mobile application, a web based application, a smart prepaid card, and/or the like in capturing payment transaction related objects such as purchase labels, payment cards, barcodes, receipts, and/or the like reduces the number of network transactions and messages that fulfill a transaction payment initiation and procurement of payment information (e.g., a user and/or a merchant does not need to show an advertisement in the print media or obtain and send digital images of paper bills, hand in a physical payment card to a cashier, etc., to initiate a payment transaction, fund transfer, and/or the like). In this way, with the reduction of network communications, the number of transactions that may be processed per day is increased, i.e., processing efficiency is improved.

[ 0025 ] It should be noted that although a mobile platform is depicted (e.g., see FIGURES 6A-6F), a digital/electronic wallet, a smart/prepaid card linked to a user's various payment accounts, and/or other payment platforms are contemplated embodiments as well; as such, subset and superset features and data sets of each or a combination of the aforementioned payment platforms may be accessed, modified, provided, stored, etc. via cloud/server services and a number of varying client devices throughout the instant specification. Similarly, although mobile wallet user interface elements are depicted, alternative and/or complementary user interfaces are also contemplated including: desktop applications, plug-ins to existing applications, stand alone mobile applications, web based applications (e.g., applications with web objects/frames, HTML 5 applications/wrappers, web pages, etc.), and other interfaces are contemplated. It should be further noted that the MCP payment processing component may be integrated with an digital/electronic wallet (e.g., a Visa V-Wallet, etc.), comprise a separate stand alone component instantiated on a user device, comprise a server/cloud accessed component, be loaded on a smart/prepaid card that can be substantiated at a PoS terminal, an ATM, a kiosk, etc., which may be accessed through a physical card proxy, and/or the like. In further implementations, the MCP may provide a merchant configuration UI for a merchant to create a campaign, set ad revenue sharing rules, and/or the like. In one implementation, the MCP may provide a merchant information collecting page based on the merchant type. In this way, the MCP reduces redundant information for merchant enrollment, and thus improves network transmission and processing efficiency. MERCHANT CONTROL PLATFORM (MCP)

[0026] FIGURES 1A-1B provide block diagrams illustrating example aspects of merchant onboarding and merchant campaign analytics within embodiments of the MCP. Within embodiments, as shown in FIGURE lA, various merchants may register with a payment platform ii4a-b, e.g., the Visa V.me wallet payment platform, and/or the like, an online shopping site (e.g., Amazon.com, shop.com, etc.), and/or the like. In one implementation, the MCP may generate customized registration forms via a user interface (UI), e.g., a web-based application, a mobile UI, and/or the like. For example, in one implementation, a merchant may comprise a large business, e.g., "Terry Luxury Department Store" 150a with an online shopping site (e.g., www.terry-luxury.com^'), and/or a small business such as an individual seller 150b. The MCP server 120 may evaluate the type of the merchant and determine the required information for registration based on the merchant type 116. [0027] For example, for a large business merchant such as "Terry Luxury 1 Department Store" 150a, the merchant may receive a merchant registration page 118a

2 including information fields such as merchant ID 121, merchant state registration ID

3 122, Nasdaq/DJIA symbol 123 of the merchant if it is listed on the national exchange,

4 and/or the like. In another example, for a small business such as an individual seller

5 150b, the merchant may receive a seller registration page 118b, which may require

6 information such as the merchant name 125, address 126, email 127, telephone 128,

7 credit card information 129, and/or the like. The MCP server 120 may receive

8 information from the merchants and verify eligibility of the merchant based on the

9 merchant type.

10 [ 0028 ] With reference to FIGUE lB, a merchant 150 may access a merchant

11 control analytics platform to design a campaign to improve their sales performance 132.

12 In one implementation, the MCP server 120 may provide an analytics platform to the

13 merchant 150 via a UI, e.g., including graphic presentation of the merchant's sales data

14 135, etc., so that the merchant may identify unsatisfactory spots of the sales

15 performance for the MCP server to design a campaign plan. For example, various

16 performance analytics including sales data segmented by store 138, by customer

17 demographics type 137, by product type 136, etc., may be provided to the merchant 150.

18 The merchant may circle or tap on a "weak" spot on a sales curve, e.g., 139, to indicate

19 an interested spot. In one implementation, the MCP server 120 may provide a campaign

20 set-up UI 140 to the merchant to obtain campaign parameters.

21 [ 0029 ] FIGURES 2A-2B show block diagrams illustrating data flows between

22 MCP server and affiliated entities within various embodiments of the MCP. Within

23 various embodiments, one or more merchants 250a-b, MCP server 220, MCP

24 database(s) 219, a payment network 240a and/or a third party entity 240b (e.g., a credit

25 check company, etc.), and/or the like are shown to interact via various communication

26 network 213.

27 [ 0030 ] In one embodiment, a merchant 25oa-b, may operate a wide variety of

28 different user devices, including communications devices and technologies within 1 embodiments of MCP operation. For example, in one embodiment, the merchant may

2 comprise a small business with one or more individual seller 250a, who may operate a

3 variety of devices including, but are not limited to, computer terminals, work stations,

4 cellular telephony handsets, smart phones, tablets, personal digital assistants (PDAs),

5 and/or the like. In another example, the merchant 250b may comprise a large business

6 entity, e.g., a department store, a manufacturer, etc., which may be equipped with a web

7 server, etc. In one implementation, the MCP component may be instantiated on a

8 personal device to conduct MCP analysis. In another embodiment, the MCP server 220

9 may be a remote server which is accessed by the merchants 25oa-b via a communication

10 network 213, such as, but not limited to local area network (LAN), in-house intranet, the

11 Internet, and/or the like.

12 [0031] In one embodiment, a merchant 250a-b may send a registration request

13 25oa-b to a MCP server 220. For example, a merchant 25oa-b may enter basic

14 information via a web-based registration UI page (e.g., see FIGURES 23A-26C).

15 [0032] For example, in one implementation, the merchant device (e.g., a web

16 browser instantiated on a merchant computer, etc.) may provide a registration request

17 2i5a-b to the MCP server 220 as a HTTP(S) POST message including XML-formatted is data. An example listing of a merchant registration request message 2isa-b,

19 substantially in the form of a HTTP(S) POST message including XML-formatted data, is

20 provided below:

21 POST /registration_request . php HTTP/ 1 . 1

22 Host: www.MCP.com

23 Content-Type: Application/XML

24 Content-Length: 667

25 <?XML version = " 1 . 0" encoding = "UTF-8 " ?>

26 <registration_request>

27 <request_ID> req_001 </request_ID>

28 <user_id> JS- 001 </user_id>

29 <merchant_id> JS- 001 </merchant_id>

30 <timestamp> 2015- 12 -15 17 : 15 : 56 </timestamp>

31 <Source>

32 <hardware_id> JS- 00923 <hardware_id>

33 <hardware_type> Apple iPhone </hardware_type>

34 <IP address> 206 . 205 . 82 . 130 </IP address> <session_type> browser </session_type>

</ Source>

<request_type> V.me onboarding </request_type>

<business_type> individual </business_type>

<user name> John Smith </user name>

</registration_request>

[0033] In one implementation, the MCP server 220 may identify a type of the merchant and retrieve registration pages based on the merchant type 227 (e.g., whether the merchant is a sole proprietor, a registered company, etc.). In one implementation, the MCP server 220 may provide registration pages for business 23ia-b (e.g. see FIGURES 24A-24C) to the merchant 250a-b for the merchant to provide requested information 232a-b. In one implementation, with reference to FIGURE 25, the registration pages 23ia-b may vary based on requirement of an issuer, as different issuer may require different requirements to register. The MCP may automatically inquire the issuer's informational requirements in an issuer database, and generate a form for the merchant so as to require the requisite information automatically. For example, the merchant may provide information including, but not limited to company/seller information, customer service information, primary contact information, term of service, payment information, and/or the like.

[0034] For example, in one implementation, the merchant device (e.g., a web browser instantiated on a merchant computer, etc.) may provide a profile information message 232a for a sole proprietor to the MCP server 220 as a HTTP(S) POST message including XML-formatted data. An example listing of a merchant registration request message 232a, substantially in the form of a HTTP(S) POST message including XML- formatted data, is provided below:

POST /registration. php HTTP/1.1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 667

<?XML version = "1.0" encoding = "UTF-8"?>

<request_ID> req_001 </request_ID> <timestamp> 2015-12-15 17:17:56 </timestamp>

<user_id> TL-001 </user_id>

<merchant_id> TL-001 </merchant_id>

<hardware_id> JS-00923 <hardware_id>

<hardware_type> Apple iPhone </hardware_type>

<IP_address> 206.205.82.130 </IP_address>

<session_type> browser </session_type>

<session_id> G656TD <session_id> </Source>

<request_type> V.me onboarding </request_type>

<business_type> individual </business_type>

<user_name> John Smith </user_name>

<user_address>

<city> Palm Beach </city>

<user_email> js@ertiail.com </user_email>

<business_type> individual </business_type>

<type> credit </type>

<account_no> 0000 0000 0000 0000 </account_no>

<customer_service>

<term> 365 days </term> </registration> [0035] In another example, when the merchant 250b comprises a company, the merchant 250b may provide a federal tax ID (EIN) instead of the social security number. For example, an example listing of a merchant registration request message 1 232b for a company, substantially in the form of a HTTP(S) POST message including

2 XML-formatted data, is provided below:

3 POST /registration. php HTTP/1.1

4 Host: www.MCP.com

5 Content-Type: Application/XML

6 Content-Length: 667

7 <?XML version = "1.0" encoding = "UTF-8"?>

8 <registration>

9 <request_ID> req_002 </request_ID>

0 <timestamp> 2015-12-15 17:17:56 </timestamp>

1 <Source>

2 <hardware_id> TL-001 <hardware_id>

3 <hardware_type> work station </hardware_type>

4 <IP_address> 206.205.82.130 </IP_address>

5 <session_type> browser </session_type>

6 <session_id> G656TD <session_id>

7

8 </Source>

9 <request_type> V.me onboarding </request_type>

0 <business_type> LLC </business_type>

1 <user_name> Terry Luxury </user_name>

2 <user_address>

3 <file> "store_location.xls" </file>

4

5 </user_address>

6 <user_email> customerservice@terry_luxury.com </user_email>

7 <business_type> retail </business_type>

8 <EIN> 00000 </EIN>

9 <payment>

0 <type> checking </type>

1 <account_no> 00000 </account_no>

2 <routing_no> 0000000 </routing_no>

3

4 </payment>

5 <customer_service>

6 <tel> 000 000 0000 </tel>

7 <online> www . terry . com/customerservice</online>

8

9 </customer_service>

0 <term> 365 days </term>

1 </registration>

[0036] Within embodiment, upon receiving registration information 232a-b, the MCP server 220 may send a verification request 235 to a payment network 240 to verify the merchant's account validity. In another implementation, the MCP server 220 may perform various checks with third parties, e.g., credit check, background check, etc.

[0037] For example, in one implementation, the MCP server 220 may provide an account verification request message 235 to a payment network 240 as a HTTP(S) POST message including XML-formatted data. An example listing of a merchant registration request message 235, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /verification_request . php HTTP/1.1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 667

<?XML version = "1.0" encoding = "UTF-8"?>

<verification_request>

<request_ID> VR001 </request_ID>

<inquiry_type> account standing </inquiry_type>

<user_name> John Smith </user_name>

<user_address>

<city> Palm Beach </city>

<user_email> j s@email . com. </user_email>

<type> credit </type>

<account_no> 0000 0000 0000 0000 </account_no>

<individual_credit_check> yes </individual_credit_check>

<credit_check_min_threshold> $1,000 </credit_check_min_threshold>

<Experian_credit_report> yes

</Experian_credit_report> </verification_request> [0038] In another implementation, if the merchant is a business merchant, an example verification request may include request for bankruptcy information, back tax in recent years, liens, Better Business Bureau violations, Done in Brandstreet report, and/or the like. An example listing of a merchant registration request message 235 for a business merchant, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /verification_request . php HTTP/ 1 . 1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 6 67

<?XML version = " 1 . 0 " encoding = "UTF- 8 " ? >

<verification_request>

<request_ID> VR001 </request_ID>

<inquiry_type> background and credit </ inquiry_type>

<user_name> Terry Luxury </user_name>

<user_address>

<user_email> contact8terry~luxury.com </user_email>

<type> checking </type>

<account_no> 0000 0000 0000 0000 </account_no>

<request_items>

<notice_of_bankrupcy> yes </ notice_of_bankrupcy>

<notice_of_back_tax> yes </notice_of_back_tax>

<notice_of_lien> yes </notice_of_lien> <DoneinBrandstreet_credit_report>

yes

</DoneinBrandstreet_report>

</requested_item> </verification_request> [0039] Within implementations, the payment network 240 may generate a response 236 to confirm the financial status of the merchant's account for registration. For example, in one implementation, the payment network 240 may provide an account verification response message 236 to the MCP server 220 as a HTTP(S) POST message including XML-formatted data. An example listing of a merchant registration response message 236, substantially in the form of a HTTP(S) POST message including XML- formatted data, is provided below:

POST /verification_response .php HTTP/ 1 . 1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 6 67

<?XML version = " 1 . 0 " encoding = "UTF- 8 " ? >

<verification_response>

<request_ID> VR001 </request_ID>

<inquiry_type> account standing </inquiry_type>

<user_name> John Smith </user_name>

<user_address>

<city> Palm Beach </city>

<type> credit </type>

<account_no> 0000 0000 0000 0000 </account_no>

<account_status> good </account_status>

<Experian_report>

<report> "Experian_JS.pdf" </report>

<indication_bankrupcy> none </indication_bankrupcy> </verification_response>

[0040] In another implementation, the verification response for a business merchant may comprise a message substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /verification_response .php HTTP/ 1 . 1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 6 67

<?XML version = " 1 . 0 " encoding = "UTF- 8 " ? >

<verification_response>

<request_ID> VR001 </request_ID>

<inquiry_type> account standing </inquiry_type>

<inquiry_type> background and credit </ inquiry_type>

<user_name> Terry Luxury </user_name>

<user_address>

<user_email> contact@terry-luxury.com </user_email>

<notice_of_bankrupcy> clear </ notice_of_bankrupcy>

<notice_of_back_tax> clear </notice_of_back_tax>

<notice_of_lien> clear </notice_of_lien>

<DoneinBradstreet_report>

2

3 </verification_response>

4 [0041] In one implementation, upon verifying the merchant submitted

5 information, the MCP server 220 may generate and store a merchant record to the

6 database table (such as FIGURE 37, Merchant 3719ε). An example merchant record

7 store command 233, substantially in the form of PHP/SQL commands, is provided

8 below:

9 <?PHP

10 header (' Content-Type : text/plain');

11 mysql_connect ( " 254 . 92 . 1 85 . 1 03 " , $DBserver, $password) ; // access database server

12 mysql_select ( "MCP_DB . SQL" ) ; // select database to append

13 mysql_query (" INSERT INTO MerchantTable (registration_date, merchant_id,

14 merchant_name, merchant_password, merchant_type, merchant_EIN, account_no,

15 merchant_customer_serice, merchant_number , merchant_url , ...)

16 VALUES ($registration_date$, $merchant_id$, $merchant_name$ ,

17 $merchant_password$, $merchant_type$, $merchant_EIN$, $account_no$,

18 $merchant_customer_serice$, $merchant_number$ , $merchant_ur 1 $ ... ) ; / /

19 add data to table in database ; / / add data to table in database

20 mysql_close ( "MCP_DB . SQL" ) ; // close connection to database

21 ? >

22 [0042] In one implementation, the MCP server 220 may send a checkout widget

23 234 to the merchant 25oa-b so that the merchant may display a checkout lightbox (e.g.,

24 "V.me" checkout, etc.) if the merchant has an online shopping page. For example, the

25 checkout widget 234 may comprise a block of XML codes in the form similar to the

26 following:

27 <?xml version="l .0 " encoding = "UTF=8 " ? >

28

29 < ! ==

30 HTTP Request URI :

31 https : /^' /www . terry-luxury . com: 44 3/ps-primary-

32 api/store/DSTR/user/checkout/refid/ ...

33 HTTP Request Method: POST

34 HTTP Request Headers: Array

35 <Widget>

36 <method>

37 <ultimatepay-info>

38 <accept-url> www.myd.oma.in . com/payment accepted </accept-url> <reject-url> ww . mydomain . com/payment rej ected </rej ect-url>

<display> lightbox </display> </ultimatepay-info>

<custom-data>

<payment_option>

<option_l> Visa </option_l>

<option_2> Mastercard </option_2 >

<option_3> Merchant Store points </option_3> <option_4> PayPal </option_4> </method> </Widget>

[0043] Further UIs and implementations of the automatically generated checkout widget 234 are discussed in FIGURES 13A-13D.

[0044] With reference to FIGURE 2B, the MCP server 200 may provide analytics based merchant campaign set-up to merchants 250. Within embodiments, a merchant may submit an analytics request 255a, e.g., via a client device 203. The client device 203 may forward the analytics request 255b to the MCP server 220. For example, in one implementation, the merchant device (e.g., a web browser instantiated on a merchant computer, etc.) may provide an analytics request 255b to the MCP server 220 as a HTTP(S) POST message including XML-formatted data. In one implementation, FIGURES 5 and 6A-6B may be used by the merchant to select various parameters for which they are interested in obtaining analytics, and once the user makes a request, e.g., clicking a button 522-523 in FIGURE 5, the MCP may generate the analytics request message. An example listing of a merchant analytics request message 255b, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /analytics_request .php HTTP/1.1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 667

<?XML version = "1.0" encoding = "UTF-8"?>

<analytics_request> 1 <request_ID> req_008 </request_ID>

2 <timestamp> 2015-12-25 17:17:56 </timestamp>

3 <Source>

4 <hardware_id> JS-00923 <hardware_id>

5 <hardware_type> Apple iPhone </hardware_type>

6 <IP_address> 206.205.82.130 </IP_address>

7 <session_type> browser </session_type>

8 <session_id> G656TD <session_id>

9

10 </Source>

11 <request_type> analytics </request_type>

12 <business_type> individual </business_type>

13 <user_id> JS-001 </user_id>

14 <user_name> John Smith </user_name>

15

16 <term>

17 <start> 10-01-2015 </start>

18 <end> 10-31-2015 </end>

19 <sampling> daily </ sampling>

20

21 </term>

22 <requested_data>

23 <datal> past transaction value </datal>

24 <data2> number of customers </data2>

25 <data3> revenue per store </data3>

26

27 </requested_data>

28

29 </analytics_request>

30

31 [0045] The MCP server 220 may generate a transaction inquiry 261 to a payment

32 network 240 to obtain analytics query results, e.g., the merchant's transaction history

33 262. In another implementation, the MCP server 220 may access a transaction database

34 to make the merchant transaction inquiry. For example, the transaction inquiry may be

35 conducted based on a specific store location, an item category, a zipcode, a product

36 code, and/or the like. For example, the MCP server 220 may issue PHP/SQL commands

37 to query a database table (such as FIGURE 37, transactions table) for merchant data.

38 An example transaction query 261, substantially in the form of PHP/SQL commands, is

39 provided below: 1 <?PHP

2 header (' Content-Type : text/plain');

3 mysql_connect ("254.93.179.112", $DBserver, $password) ; // access database server

4 mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

5 //create query

6 $query = "SELECT Transaction_id, transaction_time, transaction_amount,

7 transaction_product_id number_customers , FROM TransactionTable WHERE

8 merchant LIKE '%' $Terry Luxury" AND category LIKE '%' $skin care$ AND time

9 LIKE '%' $last quarter$;

10 $result = mysql_query ( $query) ; // perform the search query

11 mysql_close ( "MCP_DB . SQL" ) ; // close database access

12

13 [0046] Within embodiments, the MCP server 220 may generate performance

14 analytics 265 based on the obtained transaction history (e.g., Flotr, JfreeChart, RGraph,

15 jqPlug, etc. are example charting library kits that may obtain inquiry results for user

16 chart interaction mechanisms) and provide analytics reports 266 to the merchants with

17 various graphic representations via a UI (e.g., see FIGURES 7A-7C).

18 [0047] In one implementation, the merchant 250 may indicate an interested spot

19 268, e.g., by clicking/tapping on and/or circling out a "weak" spot on a performance

20 curve displayed on a screen UI, etc., and submit such interested spot 269 to the MCP

21 server. For example, in one implementation, the merchant interested spots message

22 269 may comprise information such as a start date and an end date of the merchant

23 interested period of time to request the MCP server 220 to run heuristics of the sales

24 performance and generate a campaign set-up UI 271 (e.g., see FIGURES 5 and 6A-6D).

25 In one implementation, the user selection may be represented by a Cartesian

26 coordinates and/or a region around the Cartesian coordinates, and be incorporated into

27 a HTTP POST message to send back to the MCP.

28 [0048] For example, in one implementation, as shown at 514 in FIGURE 5, a

29 merchant may move a mouse around a graphic representation of sales performance,

30 e.g., a revenue by category pie chart 513, and the MCP may generate a heuristics

31 message if the mouse moves to a area of "beauty," showing a relatively low performance

32 of the beauty products. In one implementation, if the merchant clicks at 514, the MCP

33 may automatically generate recommended parameters for a beauty product campaign which pre-populate a campaign a series of stackable campaign control blocks(e.g., 609- 612, 645-646, 650-652, 682, 683, 691, 693, etc. in FIGURES 6A-6F), e.g., a loyalty campaign for a skin care brand "La Mer" as shown in FIGURES 6C-6D. It should be noted each of the stackable blocks in FGIURES 6A-6F may have its own set of parameters, and may modify constraints on any generated campaign, and a merchant may stack a few or as many of such constraints as desired. [0049] Within implementations, the MCP server 220 may provide campaign set- up pages 273 to the merchant 250 (e.g., see FIGURE 6C), which may in turn submit campaign parameters 275 to the MCP server 220. In one implementation, the campaign UI pages (FIGURES 6C-6D) may be pre-populated with recommended default values to improve merchant identified "weak" spots. [0050] For example, the campaign parameters may include data such as, but not limited to merchant interested campaign objective data, campaign duration, offer target, offer contents, targeted consumers, and/or the like. An example listing of a campaign parameter message 275, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /campaign_parameters .php HTTP/ 1 . 1

Host: www.MCP.com

Content-Type: Application/XML

Content-Length: 667

<?XML version = " 1 . 0" encoding = "UTF-8 " ?>

<campaign_parameters>

<campaign_id> TL- 001 </campaign_id>

<timestamp> 2015- 06-25 17 : 17 : 56 </timestamp> <campaign_name> "July Faces at Terry Luxury" </campaign_name>

<merchant_id> TL- 001 </merchant_id>

<merchant_name> Terry Luxury </merchant_name>

<merchant_ur 1> www' . terry- luxu ry . com </merchant_url> </merchant>

<campaign_term>

<available_upon_first_purchase> 24 hours

</available_upon_first_purchase> </campaign_term>

<offer>

<type> loyalty </type>

<target_product>

<target_consumers>

<existing_consumers> all </existing_consumers>

<new_consumers>

<business_type> individual </business_type>

<user_name> John Smith </user_name> </campaigin_parameters> [ O O 5 I ] [0052] In the above example, the merchant has set a campaign for all products of the brand "La Mer" for all returning customers, and new customers who has purchased any "La Mer" products at stores other than "Terry Luxury," and/or are frequent buyers of skin care products. The MCP server 220 may then generate a campaign plan 277 and distribute the campaign plan 276 with the campaign parameters 275 to various media channels, e.g., social media 260a, websites 260b, TV/radio 260c, and/or the like. For example, the campaign parameters may be compiled and stored with a merchant profile. These settings may be used to author, e.g., advertising campaign expenditures, etc., in 1 various segments, demographics, target consumer groups, and/or the like. For example,

2 if a merchant has a current advertising campaign, allocating 50% of its budget to its

3 northern region, and 50% to its southern region, and the MCP identifies weak

4 performance in the southern region, additional advertising expenditure resources may

5 be provided to the southern regions (e.g., see 5i9a-b in FIGURE 5). For example, when

6 the dashboard 503 identifies the weak performance of southern region and the

7 merchant clicks on the segment (e.g., 518a) to show interest to improve, a stackable

8 campaign block may be pre-populated, suggesting ads spend restricted to southern

9 district, e.g., see 66id in FIGURE 6E.

10 [0053 ] FIGURES 3A-3C provide exemplary logic flow diagrams illustrating

11 aspects of merchant onboarding within embodiments of the MCP. Within embodiment,

12 a merchant may access a MCP onboarding platform 302, e.g., via a web-based

13 application, via a mobile application, etc. For example, an exemplary welcome page of

14 MCP onboarding platform is provided in FIGURE 23A, and a merchant may enter an

15 email address 305 to sign up with the MCP platform.

16 [0054] Within implementations, a merchant may submit merchant login request

17 305 (e.g., see 2i5a-b in FIGURE 2A), and proceed with step 1 of the merchant

18 onboarding process (e.g., see 2310 in FIGURE 23B). In one implementation, the MCP

19 may determine whether the requesting merchant has a merchant account with MCP

20 308. For example, a merchant may select whether it accepts credit cards payment with

21 a merchant account, e.g., see 2315 in FIGURE 23B.

22 [0055] If yes, the MCP may proceed to determine a merchant type 312. For

23 example, as shown in FIGURE 23B, a merchant may select a "personal" 2311 or business

24 2312 tab for enrollment. If the merchant is a business merchant (e.g., a manufacturer, a

25 distributor, a retailer, etc.), the MCP may generate an onboarding form for business

26 314a. For example, the business merchant onboarding form as shown in FIGURES 23C-

27 D comprise information such as company information 2320, contact information, an

28 estimate of monthly sales volume 2322, website URL 2323, and/or the like. In another

29 example, if the merchant is an individual, the MCP may determine whether the

30 individual has a wallet account with MCP as an individual consumer 313. If yes, the

31 MCP may populate profile information 314c from the individual's wallet profile into a 1 registration page if the individual attempts to register as a merchant. If the individual

2 merchant does not have a wallet account, the MCP may generate an onboarding form for

3 the individual to provide profile information, e.g., including user name, address, contact

4 information, identification information such as the social security, etc., 341b.

5 [0056] In another implementation, if the merchant does not have a MCP account

6 at 308, the merchant may be denied enrollment (e.g., see 2325 in FIGURE 23E), and/or

7 be prompted a sign-up page 309 to create a MCP account with MCP. Upon establishing

8 a merchant account type 310 (e.g., see 2328 in FIGURE 23E), the MCP may proceed

9 with 312 for enrollment.

10 [0057] In one implementation, upon generating the merchant account, the MCP

11 may generate onboarding form based on merchant type 312 (e.g., the merchant may

12 click to identify itself as a corporation LLC, partnership, sole proprietor, or non-profit,

13 2405 in FIGURE 24A). For example, as shown in FIGURE 24C, a corporate LLC

14 merchant onboarding form may request merchant information such as the EIN. In

15 another example, an individual merchant may need to submit SSN information 314b for

16 enrollment, e.g., see 2328 in FIGURE 24B.

17 [ o o 58 ] In further implementation, the MCP may request the merchant to identify is a credit card processor or merchant account provider, and the account number, e.g., see

19 FIGURE 26A. For example, the merchant may identify types of payment it accept, e.g.,

20 Visa, Mastercard, American Express, Discover, PayPal, and/or the like, and the

21 merchant accepted currency type, e.g., see FIGURE 26B.

22 [0059] In one implementation, upon merchant submitting requested profile

23 information 316 (e.g., an EIN for business merchants, SSN for individual merchants,

24 name of an issuing bank, etc.) the MCP may look up issuer application informational

25 requirements 317, and retrieve web forms segments to be used based on issuer

26 requirements and generate a page for bank account information 318, e.g., see FIGURE

27 25. Upon the merchant submitting bank account information 320, the MCP may

28 generate a verification request 322 (e.g., see 235 in FIGURE 2A) to a payment

29 processing network (e.g., Visa Net, etc.), which may perform merchant verification 325

30 to determine whether the merchant is in good status. In further implementation, such 1 verification request may be sent to a third party background/credit check entity. In one

2 implementation, the merchant verification request may be passed on to a third party

3 entity, such as Experian credit reports, etc., to conduct a business background check of a

4 business merchant.

5 [0060] Continuing on with FIGURE 3B, the payment network may generate a

6 verification response 328 to MCP, which may then determine whether the merchant

7 submitted profile and financial information is valid 330 to rule our fraudulent activities.

8 If valid, the MCP may generate a merchant enrollment record 333 (e.g., see 233 in

9 FIGURE 2A), and deliver a registration complete page to the merchant (e.g., see

10 FIGURE 26C). Otherwise, the merchant may receive a denial notice 332, e.g., due to

11 unsatisfactory credit history, credit card debts, and/or the like. In one implementation,

12 upon successfully enrollment, the MCP may instantiate merchant record for merchant

13 facilities 334, e.g., to allow a merchant to login to view sales performance analytics and

14 set up campaigns (e.g., see FIGURES 5 and 6A-6F), to generate a merchant site and a

15 lightbox checkout (e.g., FIGURES 10A-12B), and/or the like.

16 [0061] With reference to FIGURE 3C, a user of the MCP onboarding platform

17 (e.g., a web developer at the merchant, etc.) may submit an API generation request with is access ID 345, e.g., a request to generate a "V.me" checkout lightbox (e.g., see merchant

19 Manage sites in FIGURE 12A). The MCP server may verify whether the merchant

20 entered access ID, merchant ID, an API key, and/or other access credentials are valid

21 347. If valid, the MCP server may proceed to retrieve a list of API options 349, such as

22 but not limited to user profile API, user subscription API, virtual wallet API, checkout

23 API, and/or the like.

24 [ o o 62 ] In one implementation, the user may select an API category 351, based on

25 which the MCP server may retrieve an API parameter input panel based on the selection

26 352 (e.g., see 406a-b in FIGURE 4A, etc.). In one implementation, the user may then

27 submit requested API parameters (e.g., I305a-f in FIGURE 13A), such as but not limited

28 to a user id, a partner name, and/or the like. In one implementation, the MCP server

29 may query for API template from an API database 319 based on the category 354. For

30 example, when the user selects a "checkout and order API," the MCP server may retrieve

31 templates for checkout and order widgets. For example, the MCP server may issue 1 PHP/SQL commands to query a database table (such as FIGURE 37, API table) for an

2 API template. In one implementation, the query may be formatted to request a json,

3 XML, etc. template (e.g., see FIGURE 12C), e.g., to provide the proper post back

4 response template type, etc. Additionally, the API key, secret and site name may help to

5 form the query request (e.g., see FIGURE 12C). An exemplary query for an API

6 template is provided below:

7 <?PHP

8 header (' Content-Type : text/plain');

9 mysql_connect ("254.93.179.112", $DBserver, $password) ; // access database server

10 mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

11 //create query

12 $query = "SELECT API_id, API_site_name, API_site_id, API_type API_template_id,

13 API_key, secret, token, sample_code, FROM APITable WHERE API_site_name LIKE

14 '%' $site2" AND API_type LIKE '%' lightbox";

15 $result = mysql_query ( $query) ; // perform the search query

16 mysql_close ( "MCP_DB . SQL" ) ; // close database access

17 [ o o 63 ] In one implementation, the MCP may select the appropriate template from

18 its MCP database and pre-fill it with an API key, token, etc., and thereby providing a

19 form (e.g., see FIGURE 13A) allowing the merchant to further customize the desired

20 merchant widget, e.g., a pre-configured product purchase checkout button, e.g., 1315. .

21 [0064] In one implementation, the MCP server may generate an XML formatted

22 API package (e.g., the widget 234 in FIGURE 2A) and provide to the merchant, e.g., see

23 1310 in FIGURE 13A. In one implementation, a developer at the merchant site may

24 copy and paste the XML formatted code from the MCP UI into the merchant site source

25 code 358 to generate updated merchant site UI with a new widget 359.

26 [0065] In alternative implementations, the MCP server 310 may send the

27 generated XML formatted API package to a merchant site server, which may

28 automatically incorporate it to update the site page.

29 [0066] FIGURES 3D-3H provide exemplary logic flow diagrams illustrating

30 alternative embodiments of merchant onboarding within implementations of the MCP.

31 With reference to FIGURE 3D, a merchant may enroll at a third party processor (e.g.,

32 Playspan checkout platform) as a developer 360, and identify as a prospective merchant

33 361 to enroll with MCP 362. In one implementation, the enrollment request may be 1 pending review 363 with MCP. If the merchant does not qualify (e.g., low credit rating,

2 fraudulent prior transactions, etc.), the enrollment may be rejected 364. Otherwise,

3 upon accepting the enrollment 365, the merchant may be onboard 366 as a digital

4 merchant. In one implementation, the merchant may create application 367, e.g.,

5 creating a site (e.g., see FIGURES 10A-12B), creating lightbox checkout widgets, etc. In

6 one implementation, the merchant may enter settlement information 368, e.g., how a

7 transaction is to be cleared, posting time, waiting period, etc., and complete the

8 onboarding 369.

9 [0067] With reference to FIGURE 3E, MCP may perform review process with a

10 non-risky merchant, e.g., an established business merchant such as "Terry Luxury," etc.

11 Within implementations, the non-risky merchant 370 may enter enrollment detail 371

12 to the MCP 372, which may perform credit check 376 with a review processor 373, a

13 background check 377 with a OFAC vendor 374, and capture merchant device

14 fingerprint (e.g., physical address, IP address, hardware ID, etc.) 378 to a threat matrix

15 375 analysis to determine whether the merchant is related to any fraudulent activities. i6 [oo68] In one implementation, the MCP may check the merchant termination list

17 376a and package the enrollment data 379 to make an enrollment decision 380. A

18 decision manager 386a may apply business rules 388 to verify whether the enrollment

19 data is complete, and approve 38ia-b the enrollment. Upon enrollment, the merchant

20 may receive a one time token/URL (e.g., a confirmation URL provided in an email, etc.)

21 382 to access a control panel 386b, which may retrieve merchant profile data 383 from

22 the MCP, and complete the enrollment to provide a landing page 384 to the merchant.

23 In one implementation, the control panel may generate API keys 389 if the merchant

24 initiates a site creation request 387 (e.g., see FIGURES 17A-B).

25 [0069] With reference to FIGURE 3F, if the merchant is a risky merchant, e.g., an

26 individual seller for first time enrollment with MCP, etc., continuing on with 388, the

27 decision manager 386a may send a review required decision 390 to the MCP 372, which

28 may request more data 391 from the merchant. The decision manager may then create a

29 case 392 for a case manager 386c to review, which may forward the request to an

30 administrator 386d. Upon reviewing, the administrator may approve the enrollment

31 381a, which prompts the MCP to provoke a one time URL 389. The administrator 386d may send the one time URL 389 to the merchant and request the merchant to enroll with the one time URL. [ 0070 ] FIGURE 3G illustrates an example of denying a fraudulent merchant within implementations of the MCP. In one implementation, upon a fraudulent merchant submitting a registration request, continuing on with 388 where the decision manager apply business rules to review the merchant, if the merchant appears to have prior fraudulent transactions, etc., the decision manager may reject 381b the request, and deny the merchant onboarding 381c. [ 0071 ] FIGURE 3H illustrates an example of merchant aborting an enrollment within implementations of the MCP. In one implementation, if during the enrollment process, e.g., after the merchant sending an enrollment request, the merchant may abort the enrollment 392 (e.g., by closing the browser, etc.), the MCP may save the enrollment state 393a. In one implementation, once the merchant restarts the enrollment, the MCP may retrieve an enrollment state 393b and send a session url 395 to the merchant, e.g., via email. The MCP may then load enrollment page 397 and send merchant resume data 396 to the approval process to resume enrollment.

[ 0072 ] FIGURE 4 provides an exemplary logic flow diagram illustrating aspects of merchant analytics and campaign set-up within embodiments of the MCP. Within implementations, a merchant may access a MCP merchant control panel platform 402, e.g., the web-based dashboard in FIGURE 5, 7B-7C and 8A-8B, and/or a mobile control panel platform as shown at 605 in FIGURE 6A. In one implementation, a merchant may submit an analytics request 405 (e.g., 255a-b in FIGURE 2B), whereas the MCP may retrieve transaction data 410 and query for purchasing history of the merchant specified product brand 413. For example, the merchant may specify performance data within interested product category (e.g., 621 in FIGURE 6A), per store(e.g., 623 in FIGURE 6A), per customer (e.g., 622 in FIGURE 6A), and/or the like. The MCP may query on the transaction history to retrieve relevant transaction data (e.g., see 261 in FIGURE 2B) and generate merchant analytics and heuristics 415. For example, as shown at 710, 715 in FIGURES 7B-7C, the MCP may flag a percentage of total transactions by state, e.g., the state that has the highest percentage, etc. In one implementation, Flotr Chart, jfree chart, etc. are example library kits that may obtain 1 inquiry results for user chart interaction mechanisms.

2 [ 0073 ] In one implementation, the merchant may receive graphic representation

3 of analytics 420 (e.g., see FIGURES 7B-7C, 8A-8B), and submit campaign parameters

4 423, such as but not limited to discount rate, loyalty units, duration, campaign targets,

5 and/or the like, e.g., see FIGURES 6D-6E. In another implementation, the merchant

6 may submit interested spots on the performance chart, e.g., a product category with low

7 performance, see 514 in FIGURE 5. In one implementation, the MCP may generate

8 campaign recommendations based on heuristics 425. For example, if the merchant is

9 interested in product category with low performance, e.g., "skin care," the MCP may

10 suggest a campaign on skin care brands. In one implementation, the MCP may generate

11 default values for offer parameters (e.g., 652a-b in FIGURE 6D) based on merchant

12 specified campaign objective parameters, e.g., 654a-c in FIUGRE 6D.

13 [ 0074] In one implementation, the MCP may generate a pre-populated campaign

14 set-up form 427 to the merchant, e.g., a stackable campaign control block with

15 recommended campaign parameters which reflect the merchant's indicated interests to

16 improve performance. The merchant may further specify campaign parameters 429,

17 e.g., at FIGURES 6C-6D.

18 [ 0075 ] In one implementation, the MCP may generate a campaign plan based on

19 merchant submitted parameters and/or campaign recommendations 431, and distribute

20 to various ad channels 435.

21 [ 0076 ] FIGURE 5 provides an exemplary web based UI for a merchant control

22 panel within embodiments of the MCP. As shown in FIUGRE 5A, a merchant may

23 access a merchant dashboard upon registering with the MCP via a URL address 502.

24 For example, a merchant may access a dashboard page 503 within a browser

25 application, which may provide different applications on different tabs, e.g., loyalty club

26 504 (e.g., to generate analytics on consumer's loyalty purchases, etc.), campaigns 505

27 (e.g., for a merchant to set up a campaign, etc.), analytics 506 (e.g., for a merchant to

28 view various campaign analytics data, graphic representations, etc.), and/or the like.

29 [ 0077] As shown in FIGURE 5 A, the merchant control panel dashboard may

30 comprise merchant profile information 507, e.g., merchant name, picture, URL, business category, contact phone number, etc. A merchant may elect edit 508 the profile information on the dashboard page.

[0078] In one implementation, the merchant may view analytics by selecting analytics target 510, e.g., the number of customers, revenue, number of purchases, etc. Such analytics may be segmented 512 in various ways, such as by zipcode, by product (SKU), by product category, by time, by store, and/or the like. For example, the example pie chart 513 in FIGURE 5A illustrates the total revenue of the merchant by product category.

[oo79] In another implementation, the merchant may elect to view real-time transactions 520, which illustrates to the merchant "who is buying" 522 (e.g., consumer demographics, geographical distribution, etc.), "buying what" 523 (e.g., popular transaction product, etc.).

[0080] In another implementation, the merchant dashboard may provide a campaign section for a merchant to click to set a new campaign 516, and/or update a campaign 517. The merchant may view the current campaign performance 518 via a bar chard displayed. Further implementations of the campaign set-up are provided in FIGURES 6B-6D.

[0081] In further implementations, the merchant dashboard may provide consumer feedbacks from social platforms 521, e.g., Facebook, Twitter, Amazon, etc., including consumer comments about the product and user ratings, etc.

[0082] FIGURES 6A-6F provide exemplary mobile UIs for a merchant control panel within embodiments of the MCP. With reference to FIGURE 6A, a merchant, e.g., "Terry Luxury" 605, may operate a mobile device and access a merchant control panel, including general information 606a, loyalty information 606b, campaign 606c tab, and/or the like. In one implementation, when a merchant selects the "performance" option 608, the general information may provide a view of sales performance, e.g., the number of customers over a period of time 608, etc. The merchant may further elect to view "who's buying" 609, which may provide a view of consumer demographics, geographical distribution information, etc.; "buying what" 610, the current sales performance and popular products, etc.; offering 611 and campaign updates 612. 1 [0083] For example, in one implementation, if the merchant tap on the option

2 "Buying What" 610, the MCP may provide a product chart 615, which shows various

3 products that are currently being purchased. For example, the MCP may list products

4 based on its popularity with the most popular product listed on the top, e.g., "Clarins

5 Rose Bud Oil" which has 581 purchases of the day 616, and a performance curve

6 showing the sales curve of the month 618, etc. In one implementation, for every product

7 tab, a merchant may click to expand 619 for more analytics options, e.g., for the product

8 "La Mer Facial Cleanser," the merchant may elect to see the performance analytics for

9 "all La Mer products" 621, "view by customer" (e.g., demographic/geographic statistics,

10 etc.) 622, store distribution 623, and/or the like.

11 [0084] With reference to FIGURE 6B, if a merchant selects to view by store (e.g.,

12 expand on 623 in FIGURE 6A), the merchant may see a page "Terry Luxury by Store"

13 625, which lists a list of retail stores 630a-c of the merchant brand "Terry Luxury." In

14 one implementation, a listed retail store may be expanded to show several options, e.g.,

15 to view performance of a specific brand product ("La Mer" products 631a), view all

16 products under one category (e.g., all facial products) 631b, view a specific product of a

17 specific brand (e.g., La Mer facial cleanser, etc.) 631c, and/or the like.

is [0085] For example, if a merchant elects to expand the specific product 631c, a

19 sales performance curve may be provided to show the number of purchase over a period

20 of time 632.

21 [ o o 86 ] In another implementation, if a merchant selects to view by customer (e.g.,

22 expand on 622 in FIGURE 6A) and/or the "who's buying" 609 option in FIGURE 6A,

23 the merchant may see a page "Terry Luxury by customers" 625, which lists the

24 purchasing statistics of existing customers of the merchant 636 and new customers 639.

25 [0087] For example, if the merchant expands on the existing customers panel

26 636, the merchant may further view a taxonomy of the customers as new to a specific

27 brand (e.g., existing "Terry Luxury" customers but first time "La Mer" buyers, etc.) 637a,

28 returning customer of a specific brand 637b, etc. A performance sales curve may be

29 provided 638 to show the number of purchases made by returning La Mer customers if

30 the merchant taps on the panel 637b. 1 [ 0088 ] In another implementation, for new customers to the merchant "Terry

2 Luxury," customers may be grouped as new to both the merchant store and a specific

3 brand 640a, returning customer of a specific brand (e.g., customers new to "Terry

4 Luxury" but have purchased "La Mer" products elsewhere, etc.) 640b, etc. Similar

5 performance curves as 638 may be provided once the merchant taps on the panel.

6 [ 0089 ] With reference to FIGURE 6C, a merchant may select a "Campaign" tab

7 642 on the merchant control panel to set up a product campaign. For example, the

8 campaign panel may allow a merchant to configure the featured products of the

9 campaign 643. In one implementation, a merchant may tap on the "feature product"0 panel 643 to expand to view a list of product categories, such as, but not limited to1 cosmetics 645a, skin care 645b, perfume 645c, and/or the like. For each product2 category, the merchant may tap to expand to configure sub-categories. For example,3 under the product category "skin care" 645b, the merchant may tap to view a sub-list of4 products 646a-f, and the merchant may slide the "on/off button to determine whether5 to include such products into the campaign.

6 [ 0090 ] In another implementation, the campaign panel may allow a merchant to7 configure the campaign type 650. For example, the campaign may have various types of8 offers to the consumers, such as loyalty punch card 651a (e.g., a consumer may obtain9 discount once he/she has purchased a count of units, etc.; see 651a in FIGURE 6D), pre-0 purchase discount (e.g., the consumer may enjoy a discount for the first purchase, etc.;1 see 651b in FIGURE 6D) 651b, geographical/store based discount 651c, offers for2 existing customers 6sid (e.g., see 651c in FIUGRE 6E), customized packages 651ε to3 targeted consumers (e.g., consumers whose purchasing records show an interest into4 beauty products, etc.; see 651ε in FIGURE 6E), units for the campaign 6sif (e.g., see5 65if in FIGURE 6D), campaign time duration 6sig (e.g., see 6sig in FIGURE 6D), and6 other parameters 651I1. In another implementation, the merchant may tap on the7 campaign goal option 652 to expand a panel for objective parameter configuration, e.g.,8 see 682 in FIGURE 6F.

9 [ 0091] With reference to FIGURE 6D, at 651a, a merchant may expand a loyalty0 punch card panel to set the discount percentage 652a and punch units 652b with sliding1 bars 652a-b. In one implementation, the merchant panel may display a summary of the 1 offer, e.g., "an additional 25% discount off your next purchase for every 6 La Mer

2 products you purchased," to reflect the parameters a merchant has configured. In one

3 implementation, a merchant may select to save the card 652d, and/or to start a new

4 loyalty punch card offer 652ε.

5 [ 0092 ] At 651b, a merchant may expand a pre-purchase discount panel to set the

6 discount percentage 653a and purchasing units 653b with sliding bars 653a-b. In one

7 implementation, the merchant panel may display a summary of the offer, e.g., "an

8 additional 25% discount off your entire purchase if you purchase 16 or more La Mer

9 products," to reflect the pre-purchase offer parameters a merchant has configured. In

10 one implementation, a merchant may select to save the offer 653d, and/or to start a new

11 offer 653ε.

12 [ 0093 ] At 65if, a merchant may expand a units panel to set the performance

13 metrics such as units to be sold 654a, profit margin 654b, revenue per visit 654c via

14 sliding bars 654a-c. In one implementation, a merchant may select to save the units

15 configuration 654d, and/or to continue with more parameters 654ε. More campaign

16 objective parameters are illustrated at 683a-g in FIGURE 6F.

17 [ 0094] At 65ig, a merchant may expand a time configuration panel to set the

18 campaign duration 655a, offer waiting period for first-time consumers 655b (e.g., a new

19 consumer may enjoy a discount a period of time after his first purchase, etc.), and

20 waiting period for returning consumers 655c with sliding bars 655a-c. In one

21 implementation, a merchant may select to save the time configuration 655d, and/or to

22 start a new setting 655ε.

23 [ 0095 ] It is worth noting that, in one implementation, a merchant may manually

24 set the parameters throughout FIGURES 6A-6F upon the merchant's preference. In

25 another implementation, the MCP may generate a recommended value for parameter

26 setting as a default value based on heuristics. In further implementations, a merchant

27 may set campaign objective parameters at the units panel at 6sif, and the MCP may

28 generate recommended parameters as default values. For example, if the merchant has

29 entered an objective of profit margin "11.2%" at 654b and revenue per visit at $134.50

30 654c, and the merchant taps on a "Pre-Purchase Discount" panel, the MCP may return 1 suggested discount rate of "25%" for every "16 La Mer products" as default parameters.

2 [ 0096 ] With reference to FIGURE 6E, at 651c, a merchant may expand a

3 geography configuration panel to set the campaign store location. For example, the

4 merchant may check to select a specific store location 661a from a drop-down list, may

5 select all stores within a state 661b, may select all stores within a zipcode range 661c,

6 and/or may add all stores in several states 66id by click on a state distribution map

7 66ie, e.g., the selected states may appear in red circles to reflect selecting southern

8 states, etc.

9 [ 0097] At 651ε, a merchant may expand a customized package panel to set the

10 target consumers. For example, the merchant may select target customers 665a as who

11 are interested in a list of product categories (e.g., as the consumers have purchased such

12 products before, etc.). The merchant may also group consumers who are interested in

13 the specific brand "La Mer" 666a (e.g., who has purchased La Mer products before),

14 and/or consumers who are interested in similar brands 666b. The merchant may

15 further define the heuristics of consumer interests based on a purchase frequency 667a

16 and/or the consumer's maximum one-time purchase value 667b via sliding bars 66ysL-b.

17 [ 0098 ] With reference to FIGURE 6F, back to the campaign panel, if the merchant

18 expands the campaign goals section 682, the merchant may configure various campaign

19 goal parameters, such as, but not limited to profit margin 683a, number of customers

20 683b, number of new customers 683d, revenue 683ε, revenue per visit 683f, and other

21 683g. In one implementation, the merchant may set each of the listed goal parameters

22 via a sliding bar 685.

23 [ 0099 ] In further implementations, the merchant may configure campaign/ad

24 channels for the campaign 690. For example, the merchant may select a list of available

25 online channels, such as social media platforms 69ia-c, shopping sites (e.g.,

26 Amazon.com 69id), merchant's own site 69ie, merchant stores 69if, and other channels

27 693. The merchant may expand the "other" section 693 to enter a customized ad

28 channel, e.g., the URL of a new website, a personal blog, group email address, etc.

29 [ 00100 ] FIGURES 7A-7C provide exemplary merchant control panel UIs

30 illustrating aspects of MCP merchant control dashboard within embodiments of the MCP. As shown in FIGURE yA, a merchant may access the dashboard site to create a merchant shopping site 710 upon registration. In another implementation, a merchant may view sales performance over a period of time, e.g., number of transactions (e.g., see FIGURE 7B), number of return transactions by state (e.g., see FIGURE 7C), etc. In one implementation, the MCP may generate heuristics to flag a state that has the highest market share, e.g., see 710/715 in FIGURES 7B-C. [ 00101] FIGURES 8A-8B provide exemplary merchant control panel UIs illustrating aspects of MCP reporting statistics within embodiments of the MCP. Within implementations, a merchant may elect to generate sales data within a selected period of time, e.g., activity per day 805. In another implementation, as shown in FIGURE 8B, a merchant may select to view sales data performance of different category, e.g., an aggregated performance curves of different merchant sites 815, and a pie chart distribution 825, and/or the like. In one implementation, the MCP may generate heuristics, e.g., to flag a site that has the highest sales share, e.g., see 825. [ 00102 ] FIGURES 9A-9H provide exemplary merchant control panel UIs illustrating aspects of MCP merchant transaction search within embodiments of the MCP. Within implementations, a merchant may enter search criteria to search a transaction within a period of time, e.g., 905 at FIGURE 9A. In further implementations, a merchant may view multiple search results that list the the transaction details of transactions satisfying the search criteria, as shown in FIGURE 9B. In further implementations, a merchant may authorize a pending transaction, as shown in FIGURE 9C. In another implementation, a merchant may authorize a pending transaction, as shown in FIGURE 9C. In further implementations, a merchant may confirm a transaction, as shown in FIGURE 9D. In further implementations, a merchant may authorize a refund request, as shown in FIGURE 9E. In further implementations, a merchant may void a pending transaction upon validating a refund, as shown in FIGURE 9F. [ 00103 ] In further implementations, the MCP may update a list of transactions, showing the merchant's latest edits of the transactions (e.g., to authorize, to capture, to allow refund, etc.), as shown at 920 in FIGURE 9G. In further implementations, a merchant may edit the date range for transaction searches, as shown at 925 in FIGURE 1 9H.

2 [ 00104] FIGURES loA-ioC provide exemplary merchant control panel UIs

3 illustrating aspects of MCP merchant managing a shopping site within embodiments of

4 the MCP. In one implementation, a merchant may create a shopping site via MCP

5 platform upon registration, e.g., see 1005 in FIGURE 10A. For example, in one

6 implementation, a merchant may create a list of merchant sites ioo8a-b by establishing

7 a variety of parameters for integration with a MCP sandbox environment, e.g., see

8 FIGURE loB-C.

9 [ 00105 ] FIGURES 11A-11B provide exemplary merchant control panel UIs

10 illustrating aspects of MCP merchant creating a new site within embodiments of the

11 MCP. In one implementation, a merchant may enter a site name to create a new site

12 and retrieve an API key from the MCP, e.g., see liosa-b in FIGURE 11A and FIGURE

13 11B.

14 [ 00106 ] FIGURES 12A-12C provide exemplary merchant control panel UIs

15 illustrating aspects of MCP merchant editing a site within embodiments of the MCP. A

16 merchant may edit site parameters such as site name 1205a, post-back URL 1205b, etc.,

17 and the MCP may update its API key 1205c, security signature I205d, and/or the like, as is shown in FIGURES 12A-C.

19 [ 00107] FIGURES 13A-13D provide exemplary merchant control panel UIs

20 illustrating aspects of MCP merchant obtaining a sandbox checkout widget within

21 embodiments of the MCP. A merchant may create a checkout lightbox by entering a

22 variety of parameters, such as amount 1305a, currency 1305b, product_id 1305c,

23 merchant transaction i305d, collect shipping i305e, process 1305^ and/or the like, e.g.,

24 see FIGURE 13A. The MCP may return a block of sample XML code 1310 for the

25 lightbox generation, with a preview 1315. In one implementation, a merchant may enter

26 an email address for obtaining transaction search results, e.g., see FIGURE 13C. In one

27 implementation, a merchant may view a purchase contract for the generated checkout

28 widget, e.g., see FIGURE 13D.

29 [ 00108 ] FIGURES 14A-16C provide exemplary merchant control panel UIs

30 illustrating aspects of MCP merchant profile management within embodiments of the 1 MCP. In one implementation, a merchant may edit company information, e.g., see

2 FIGURES 14A-B. In one implementation, a merchant may manage users and edit

3 administrators who can view and edit user profiles and access parameters, e.g., see

4 FIGURES 15A-16C.

5 [ 00109 ] FIGURES 17A-17B provide exemplary merchant control panel UIs

6 illustrating aspects of MCP merchant changing a password within embodiments of the

7 MCP.

8 [ 00110 ] FIGURES 18A-22 provide exemplary merchant control panel UIs

9 illustrating aspects of MCP merchant managing credit card processing accounts within

10 embodiments of the MCP. In one implementation, a merchant may enter various

11 information to establish a payment account, including company information, EID,

12 payment information (e.g., see FIGURE 22), etc., e.g., see FIGURES 18A-22. The MCP

13 may list the enrolled merchant accounts, wherein a merchant may specify the usage

14 scope of each account (e.g., a global account or U.S. account for U.S. transactions, etc.),

15 e.g., see FIGURE 20.

16 [ 00111 ] FIGURES 22A-22B provide exemplary merchant control panel UIs

17 illustrating aspects of MCP merchant posting notifications to different sites within

18 embodiments of the MCP. For example, a merchant may post notifications for offers,

19 loyalty rewards, campaign events, fraud alerts, etc. to a created merchant site. A

20 merchant may view pending notifications for each site via the MCP platform, and elect

21 to distribute the notifications to each site, e.g., as shown in FIGURES 22A-B.

22 [ 00112 ] FIGURES 23A-26C provide exemplary merchant onboarding UIs

23 illustrating aspects of MCP merchant onboarding within embodiments of the MCP, as

24 discussed with the process flow in FIGURES 3A-3B.

25 [ 00113 ] FIGURES 27-30C provide exemplary transaction flows illustrating MCP

26 merchant checkout services within embodiments of the MCP. In one implementation, a

27 processing network may keep a record of merchant transactions. As shown in FIGURE

28 27, a consumer 2702 may start with making a purchase using the lightbox checkout

29 2708, e.g., Visa V.me purchase checkout box, etc., 2721. The merchant 2705 may

30 forward the lightbox checkout request to the lightbox processor 2708 which may in turn 1 retrieve consumer previously established preference and account information 2725 to a

2 checkout processor 2710 (e.g., Playspan platform, etc.). In one implementation, the

3 payment request may be processed with a checkout gateway 2715 (e.g., a Chase payment

4 gateway, etc.), processing network 2718 (e.g., VisaNet, etc.) and be cleared with an

5 issuer 2720, e.g., further implementations of a card based transaction is discussed in

6 FIGURES 42A-43.

7 [ 00114 ] In one implementation, the checkout processor 2710 may provide a

8 notification for purchase completion 2730 to the lightbox processor 2708, which may

9 forward a post-back URL link 2732 to the merchant, and the completion notification

10 2735 to the consumer 2702.

11 [ 00115 ] FIGURE 28 provides an alternative logic flow diagram illustrating

12 merchant checkout between a consumer 2802, merchant 2805, lightbox 2808, checkout

13 processor 2810, gateway 2815, a global payment network (GPN) 2815, processing

14 network 2818, acquirer 2822, and an issuer 2820. In one implementation, continuing

15 on with the checkout processor 2810 obtaining card preference, an authorization

16 request message 2850 may be routed to the checkout gateway 2815 and forwarded to

17 various entities in a batch 2851 for the acquirer to capture the payment.

18 [ 00116 ] FIGURE 29 provides an alternative logic flow diagram illustrating

19 checkout on a hosting site (e.g., Amazon.com, etc.) of the merchant within

20 implementations of the MCP. Within implementations, the authorization message 2950

21 may be routed to a hosting site server 2905 upon processing from the checkout

22 processor 2810. The remaining process steps may be similar to those in FIGURES

23 28029.

24 [ 00117] FIGURES 30A-C provide alternative logic flow diagram illustrating

25 merchant creating a lightbox within implementations of the MCP. As shown in FIUGRE

26 30A, upon a checkout processor 3005 approves merchant onboarding status 3011, a

27 merchant (e.g., a merchant developer, etc.) may submit application details 3012 to the

28 MCP panel 3010 (which may have a different URL from the MCP site, etc.), e.g., see

29 FIGURES 17A-17B. In one implementation, the MCP may generate XML or html

30 formatted widgets for site setup 3013 to the merchant, who may incorporate into the merchant site 3015 to update 3014. In one implementation, the merchant may test 3015 the generated widget with the merchant site to examine whether the checkout widget is valid 3016a, or invalid 3016b upon site operation. In one implementation, the merchant may enter bank account detail 3017 to the MCP panel to set up, e.g., see FIGURES 19A- 22. [ 00118 ] With reference to FIGURE 30B, a merchant developer may create a logo of the lightbox widget 3021 and insert the logo to a URL 3022. In one implementation, a consumer may checkout 3023 by clicking on "continue to checkout," which may invoke the lightbox 3024 and return a lightbox logo 3025a-c to the consumer page. [ 00119 ] With reference to FIGURE 30C, a merchant developer may generate a lightbox widget in an alternative implementation. For example, upon merchant developer entering a checkout method preference 3031 (e.g., Visa, Mastercard, etc.), the merchant site 3015 may generate a merchant page 3032, and generate a preview of the lightbox 3033. Once the merchant approves 3035, the merchant site may store the lightbox setup with a CDN 3036. [ 00120 ] In one implementation, a consumer may checkout with the merchant site, which may invoke a lightbox 3024a-b to display a lightbox logo to the consumer. In one implementation, the CDN may return a merchant widget page 3035 and the populated lightbox 3025b to the consumer.

[ 00121] FIGURE 31 shows a datagraph diagram illustrating example aspects of transforming a user checkout request input via a User Purchase Checkout ("UPC") component into a checkout data display. In some embodiments, a user, e.g., 3101a, may desire to purchase a product, service, offering, and/or the like ("product"), from a merchant via a merchant online site or in the merchant's store. The user may communicate with a merchant/acquirer ("merchant") server, e.g., 3103a, via a client such as, but not limited to: a personal computer, mobile device, television, point-of-sale terminal, kiosk, ATM, and/or the like (e.g., 3102). For example, the user may provide user input, e.g., checkout input 3111, into the client indicating the user's desire to purchase the product. In various embodiments, the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a 1 touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC equipped

2 hardware device (e.g., electronic card having multiple accounts, smartphone, tablet,

3 etc.) within the user device, mouse clicks, depressing buttons on a joystick/game

4 console, voice commands, single/multi-touch gestures on a touch-sensitive interface,

5 touching user interface elements on a touch-sensitive display, and/or the like. As an

6 example, a user in a merchant store may scan a product barcode of the product via a

7 barcode scanner at a point-of-sale terminal. As another example, the user may select a

8 product from a webpage catalog on the merchant's website, and add the product to a

9 virtual shopping cart on the merchant's website. The user may then indicate the user's

10 desire to checkout the items in the (virtual) shopping cart. For example, the user may

11 activate a user interface element provided by the client to indicate the user's desire to

12 complete the user purchase checkout. The client may generate a checkout request, e.g.,

13 3112, and provide the checkout request, e.g., 3113, to the merchant server. For example,

14 the client may provide a (Secure) Hypertext Transfer Protocol ("HTTP(S)") POST

15 message including the product details for the merchant server in the form of data

16 formatted according to the extensible Markup Language ("XML"). An example listing

17 of a checkout request 3112, substantially in the form of a HTTP(S) POST message

18 including XML-formatted data, is provided below:

19 POST /checkoutrequest .php HTTP/1.1

20 Host: www.merchant.com

21 Content-Type: Application/XML

22 Content-Length: 667

23 <?XML version = "1.0" encoding = "UTF-8"?>

24 <checkout_request>

25 <session_ID>4NFU4RG94</session_ID>

26 <! --optional parameters-->

27 <timestamp>2011-02-22 15 : 22 : 41</timestamp>

28 <user_ID>j ohn . q. publicSgmail . com</user_ID>

29 <device_fingerprint>

30 <device_IP>192.168.23.126</device_IP>

31 <device_MAC>0123.4567.89ab</device_MAC>

32 <device_serial>312456768798765432</device_serial>

33 <device_ECID>00000AEBCDF12345</device_ECID>

34 <device_identifier>j qp_air</device_identifier>

35 <device_UDI D>21343e34-14f4-8jn4-7yfe-124578632134</device_UDI D>

36 <device browser>firefox 2.2</device browser> 1 <device_type>smartphone</device_type>

2 <device_model>HTC Hero</device_model>

3 <OS>Android 2.2</OS>

4 <wallet_app_installed_flag>true</wallet_app_installed_flag>

5 </device_fingerprint>

6 </checkout_request>

7

8 [ 0 0 122] In some embodiments, the merchant server may obtain the checkout

9 request from the client, and extract the checkout detail (e.g., XML data) from the

10 checkout request. For example, the merchant server may utilize a parser such as the

11 example parsers described below in the discussion with reference to FIGURE 37. Based

12 on parsing the checkout request 3112, the merchant server may extract product data

13 (e.g., product identifiers), as well as available PoS client data, from the checkout request.

14 In some embodiments, using the product data, the merchant server may query, e.g.,

15 3114, a merchant/acquirer ("merchant") database, e.g., 3103b, to obtain product data,

16 e.g., 3115, such as product information, product pricing, sales tax, offers, discounts,

17 rewards, and/or other information to process the purchase transaction and/or provide is value-added services for the user. For example, the merchant database may be a

19 relational database responsive to Structured Query Language ("SQL") commands. The

20 merchant server may execute a hypertext preprocessor ("PHP") script including SQL

21 commands to query a database table (such as FIGURE 37, Products 3719I) for product

22 data. An example product data query 3114, substantially in the form of PHP/SQL

23 commands, is provided below:

24 <?PHP

25 header (' Content-Type : text/plain');

26 mysql_connect ("254.93.179.112", $DBserver, $password) ; // access database server

27 mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

28 //create query

29 $query = "SELECT product_title product_attributes_list product_price

30 tax_info_list related_products_list offers_list discounts_list rewards_list

31 merchants_list merchant_availability_list FROM ProductsTable WHERE

32 product_ID LIKE '%' $prodID";

33 $result = mysql_query ( $query) ; // perform the search query

34 mysql_close ( "MCP_DB . SQL" ) ; // close database access

35 ?>

36 [00123] In some embodiments, in response to obtaining the product data, the merchant server may generate, e.g., 3116, checkout data to provide for the PoS client. In some embodiments, such checkout data, e.g., 3117, may be embodied, in part, in a HyperText Markup Language ("HTML") page including data for display, such as product detail, product pricing, total pricing, tax information, shipping information, offers, discounts, rewards, value-added service information, etc., and input fields to provide payment information to process the purchase transaction, such as account holder name, account number, billing address, shipping address, tip amount, etc. In some embodiments, the checkout data may be embodied, in part, in a Quick Response ("QR") code image that the PoS client can display, so that the user may capture the QR code using a user's device to obtain merchant and/or product data for generating a purchase transaction processing request. In some embodiments, a user alert mechanism may be built into the checkout data. For example, the merchant server may embed a URL specific to the transaction into the checkout data. In some embodiments, the alerts URL may further be embedded into optional level 3 data in card authorization requests, such as those discussed further below with reference to FIGURES 33-34. The URL may point to a webpage, data file, executable script, etc., stored on the merchant's server dedicated to the transaction that is the subject of the card authorization request. For example, the object pointed to by the URL may include details on the purchase transaction, e.g., products being purchased, purchase cost, time expiry, status of order processing, and/or the like. Thus, the merchant server may provide to the payment network the details of the transaction by passing the URL of the webpage to the payment network. In some embodiments, the payment network may provide notifications to the user, such as a payment receipt, transaction authorization confirmation message, shipping notification and/or the like. In such messages, the payment network may provide the URL to the user device. The user may navigate to the URL on the user's device to obtain alerts regarding the user's purchase, as well as other information such as offers, coupons, related products, rewards notifications, and/or the like. An example listing of a checkout data 3117, substantially in the form of XML- formatted data, is provided below:

<?XML version = "1.0" encoding = "UTF-8"?>

<! --optional data-->

<expiry_lapse>00 : 00 : 30</expiry_lapse>

<total_cost>$121.49</total_cost>

<alerts_URL>www. merchant . com/shopcarts .php?sessionID=4NFU4RG94</alerts_URL> <user_ID>j ohn . q. publicSgmail . com</user_ID>

<user_device_fingerprint>

<device_IP>192.168.23.126</device_IP>

<device_MAC>0123.4567.89ab</device_MAC>

<device_serial>312456768798765432</device_serial>

<device_ECID>00000AEBCDF12345</device_ECID>

<device_identifier>j qp_air</device_identifier>

<device_UDID>21343e34-14f4-8jn4-7yfe-124578632134</device_UDID>

<device_browser>firefox 2.2</device_browser>

<device_type>smartphone</device_type>

<device_model>HTC Hero</device_model>

<OS>Android 2.2</OS>

<wallet_app_installed_flag>true</wallet_app_installed_flag>

</user_device_fingerprint>

<purchase_detail>

<cart>

<merchant_params>

<merchant_id>54TBRELF8</merchant_id>

<merchant_name>BARNES, Inc . </merchant_name> <merchant_auth_key>TMN45GER98</merchant_auth_key> </merchant_params>

<product_type>book</product_type>

<product_params>

<product_title>XML for dummies</product_title> <ISBN>938-2-14-168710-0</ISBN>

<cover>hardbound</ cover>

</product_params>

<unit_cost>$14.46</unit_cost>

<coupon_id>AY34567</ coupon_id>

<social_flag>ON</social_flag>

<social_message>Look what I bought today ! </social_message> <social_networks>facebook twitter</social_networks> </product> <product>

<merchant_params>

<merchant_id>3FBCR4INC</merchant_id>

<merchant_name>Books , Inc . </merchant_name> <merchant_auth_key>lN484MCP</merchant_auth_key> </merchant_params>

<product_type>book</product_type>

<product_params>

<product_title>Sophie' s World</product_title> <ISBN>955-2-14-112310-0</ISBN>

<cover>hardbound</ cover>

</product_params>

<quantity>K/quantity>

<unit_cost>$34.78</unit_cost>

<coupon_id>null</coupon_id>

<social_flag>OFF</social_flag>

</product>

</cart>

<cart>

<merchant_params>

<merchant_id>RFH5IB4FT</merchant_id>

<merchant_name>Amzn, Inc . </merchant_name>

<merchant_auth_key>44543DSJFG</merchant_auth_key> </merchant_params>

<product_type>book</product_type>

<product_params>

<product_title>XML - a primer</product_title> <ISBN>938-2-14-1436710-0</ISBN> <edition>2nd ed. </edition>

<cover>hardbound</ cover>

</product_params>

<quantity>K/quantity>

<unit_cost>$12.93</unit_cost>

<coupon_id>AY34567</ coupon_id>

<social_flag>ON</social_flag>

<social_message>Look what I bought today ! </social_message> <social_networks>facebook twitter</social_networks>

</product>

<merchant_params> <merchant_id>3FBCR4INC</merchant_id>

<merchant_name>BestBooks , Inc . </merchant_name> <merchant_auth_key>lN484MCP</merchant_auth_key> </merchant_params>

<product_type>book</product_type>

<product_params>

<product_title>Sophie' s Choice</product_title> <ISBN>938-2-14-168710-0</ISBN>

</product_params>

<quantity>K/quantity>

<unit_cost>$44.86</unit_cost>

<coupon_id>null</coupon_id>

<social_flag>OFF</social_flag>

</product>

</cart>

</purchase_detail>

<checkout_data> [00124] Upon obtaining the checkout data, e.g., 3117, the PoS client may render and display, e.g., 3118, the checkout data for the user.

[00125] FIGURE 32 shows a logic flow diagram illustrating example aspects of transforming a user checkout request input via a User Purchase Checkout ("UPC") component into a checkout data display. In some embodiments, a user may desire to purchase a product, service, offering, and/or the like ("product"), from a merchant via a merchant online site or in the merchant's store. The user may communicate with a merchant/acquirer ("merchant") server via a PoS client. For example, the user may provide user input, e.g., 3201, into the client indicating the user's desire to purchase the product. The client may generate a checkout request, e.g., 3202, and provide the checkout request to the merchant server. In some embodiments, the merchant server may obtain the checkout request from the client, and extract the checkout detail (e.g., XML data) from the checkout request. For example, the merchant server may utilize a parser such as the example parsers described below in the discussion with reference to FIGURE 37. Based on parsing the checkout request, the merchant server may extract product data (e.g., product identifiers), as well as available PoS client data, from the checkout request. In some embodiments, using the product data, the merchant server may query, e.g., 3203, a merchant/acquirer ("merchant") database to obtain product data, e.g., 3204, such as product information, product pricing, sales tax, offers, discounts, rewards, and/or other information to process the purchase transaction and/or provide value-added services for the user. In some embodiments, in response to obtaining the product data, the merchant server may generate, e.g., 3205, checkout data to provide, e.g., 3206, for the PoS client. Upon obtaining the checkout data, the PoS client may render and display, e.g., 3207, the checkout data for the user. [ 00126 ] FIGURES 33A-B show datagraph diagrams illustrating example aspects of transforming a user virtual wallet access input via a Purchase Transaction Authorization ("PTA") component into a purchase transaction receipt notification. With reference to FIGURE 33A, in some embodiments, a user, e.g., 3301a, may wish to utilize a virtual wallet account to purchase a product, service, offering, and/or the like ("product"), from a merchant via a merchant online site or in the merchant's store. The user may utilize a physical card, or a user wallet device, e.g., 3301b, to access the user's virtual wallet account. For example, the user wallet device may be a personal/laptop computer, cellular telephone, smartphone, tablet, eBook reader, netbook, gaming console, and/or the like. The user may provide a wallet access input, e.g., 3311 into the user wallet device. In various embodiments, the user input may include, but not be limited to: a single tap (e.g., a one- tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC equipped hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch- sensitive display, and/or the like. In some embodiments, the user wallet device may authenticate the user based on the user's wallet access input, and provide virtual wallet features for the user. [ 00127] In some embodiments, upon authenticating the user for access to virtual wallet features, the user wallet device may provide a transaction authorization input, e.g., 3314, to a point-of-sale ("PoS") client, e.g., 3302. For example, the user wallet device may communicate with the PoS client via Bluetooth, Wi-Fi, cellular communication, one- or two-way near-field communication ("NFC"), and/or the like. In embodiments where the user utilizes a plastic card instead of the user wallet device, the user may swipe the plastic card at the PoS client to transfer information from the plastic card into the PoS client. For example, the PoS client may obtain, as transaction authorization input 3314, track 1 data from the user's plastic card (e.g., credit card, debit card, prepaid card, charge card, etc.), such as the example track 1 data provided below:

%B123456789012345^APUBLIC/ J. Q. ^Λ 99011200000000000000** 901 ******?*

(wherein ^,123456789012345' is the card number of V.Q. Public' and has a CVV

number of 901. '990112' is a service code, and *** represents decimal digits which change randomly each time the card is used. ) [00128] In embodiments where the user utilizes a user wallet device, the user wallet device may provide payment information to the PoS client, formatted according to a data formatting protocol appropriate to the communication mechanism employed in the communication between the user wallet device and the PoS client. An example listing of transaction authorization input 3314, substantially in the form of XML- formatted data, is provided below:

<?XML version = "1.0" encoding = "UTF-8"?>

<transaction_authorization_input>

<payment_data>

<charge_priority>l</ charge_priority>

<charge_ratio>40%</charge_ratio>

<account_type>debit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol>

<account_number>123456789012345</account_number>

<account_name>John Q. Public</account_name>

<bill_add>987 Green St #456, Chicago, IL 94652</bill_add>

<ship_add>987 Green St #456, Chicago, IL 94652</ship_add>

<CW_type>dynamic<CVV_type>

<CW>http: //www.paynet . com/dcvv . php?sessionID=4NFU4RG94</CW> <cloak_flag>ON</cloak_flag>

<alert_rules>tar1 tar4 tar12</alert_rules>

</account>

<charge_priority>l</ charge_priority>

<charge_ratio>60%</charge_ratio>

<account_type>rewards</account_type> <value_exchange_symbol>VME</value_exchange_symbol> <account_number>234567890123456</account_number>

<account_name>John Q. Public</account name> <bill_add>987 Green St #456, Chicago, IL 94652</bill_add> <ship_add>987 Green St #456, Chicago, IL 94652</ship_add> <CW_type>static<CW_type>

<cloak_flag>OIK/cloak_flag>

<alert_rules>tar1 tar4 tarl2</alert_rules> <mode>Bluetooth</mode>

</account>

<charge_priority>2</ charge_priority>

<charge_ratio>100%</charge_ratio>

<account_number>345678901234567</account_number>

<account_type>credit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol> <account_name>John Q. Public</account name> <bill_add>987 Green St #456, Chicago, IL 94652</bill_add> <ship_add>987 Green St #456, Chicago, IL 94652</ship_add> <CW_type>static<CW_type>

<cloak_flag>ON</cloak_flag>

<alert_rules>tarl tar4 tar12</alert_rules> <mode>lIFC</mode>

</account>

</payment_data>

<! --optional data-->

<expiry_lapse>00 : 00 : 30</expiry_lapse>

<secure_key>0445329070598623487956543322</secure_key>

<alerts_track_flag>TRUE</alerts_track_flag>

<device_fingerprint>

<device_IP>192.168.23.126</device_IP>

<device_I4AC>0123.4567.89ab</device_MAC>

<device_serial>312456768798765432</device_serial>

<device_ECID>00000AEBCDF12345</device_ECID>

<device_identifier>j qp_air</device_identifier>

<device_UDID>21343e34-14f4-8jn4-7yfe-124578632134</device_UDID> <device_browser>firefox 2.2</device_browser>

<device_type>smartphone</device_type>

<device model>HTC Hero</device model> <OS>Android 2.2</ΟΞ>

<wallet_app_installed_flag>true</wallet_app_installed_flag>

</device_fingerprint>

</transaction authorization [00129] In some embodiments, the PoS client may generate a card authorization request, e.g., 3315, using the obtained transaction authorization input from the user wallet device, and/or product/checkout data (see, e.g., FIGURE 31, 3115-3117). An example listing of a card authorization request 3315-3316, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /authorizationrequests .php HTTP/1.1

Host: www.acquirer.com

Content-Type: Application/XML

Content-Length: 1306

<?XML version = "1.0" encoding = "UTF-8"?>

<card_authorization_request>

<session_ID>4NFU4RG94</order_ID>

<! --optional data-->

<alerts_URL>www . merchant . com/ shopcarts . php?sessionID=AEBB4356</alerts_URL> <user_ID>j ohn . q. publicSgmail . com</user_ID>

<device_fingerprint>

<device_IP>192.168.23.126</device_IP>

<device_MAC>0123.4567.89ab</device_MAC>

<device_serial>312456768798765432</device_serial>

<device_ECID>00000AEBCDF12345</device_ECID>

<device_identifier>j qp_air</device_identifier>

<device_UDID>21343e34-14f4-8jn4-7yfe-124578632134</device_UDID>

<device_browser>firefox 2.2</device_browser>

<device_type>smartphone</device_type>

<device_model>HTC Hero</device_model>

<OS>Android 2.2</OS>

<wallet_app_installed_flag>true</wallet_app_installed_flag> </device_fingerprint>

<purchase_details>

<total_cost>$121.49</total_cost>

<cart>

<merchant_params> <merchant_id>54TBRELF8</merchant_id>

<product_type>book</product_type>

<product_params>

<product_title>XML for dummies</product_title> <ISBN>938-2-14-168710-0</ISBN>

<cover>hardbound</ cover>

</product_params>

<unit_cost>$14.46</unit_cost>

<coupon_id>AY34567</coupon_id>

<social_flag>ON</social_flag>

</product>

<merchant_params>

<merchant_id>3FBCR4INC</merchant_id>

<product_type>book</product_type>

<product_params>

<product_title>Sophie' s World</product_title> <ISBN>955-2-14-112310-0</ISBN>

<cover>hardbound</ cover>

</product_params>

<quantity>K/quantity>

<unit_cost>$34.78</unit_cost>

<coupon_id>null</coupon_id>

<social_flag>OFF</social_flag>

</product>

</cart>

<cart>

<merchant_params>

<merchant_id>RFH5IB4FT</merchant_id>

<merchant_name>Amzn, Inc . </merchant_name> <merchant_auth_key>44543DSJFG</merchant_auth_key> </merchant_params>

<product_type>book</product_type>

<product_params>

<product_title>XML - a primer</product_title> <ISBN>938-2-14-1436710-0</ISBN>

<cover>hardbound</ cover>

</product_params>

<quantity>K/quantity>

<unit_cost>$12.93</unit_cost>

<coupon_id>AY34567</ coupon_id>

<social_flag>ON</social_flag>

<social_message>Look what I bought today ! </social_message> <social_networks>facebook twitter</social_networks> </product>

<merchant_params>

<merchant_id>3FBCR4INC</merchant_id>

<product_type>book</product_type>

<product_params>

<product_title>Sophie' s Choice</product_title> <ISBN>938-2-14-168710-0</ISBN>

</product_params>

<quantity>K/quantity>

<unit_cost>$44.86</unit_cost>

<coupon_id>null</coupon_id>

<social_flag>OFF</social_flag>

</product>

</cart>

</purchase_details>

<account_params>

<charge_priority>l</ charge_priority>

<charge_ratio>40%</charge_ratio>

<account_type>debit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol> <account number>123456789012345</account number> <account_name>John Q. Public</account_name> <bill_add>987 Green St #456, Chicago, IL 94652</bill_add> <ship_add>987 Green St #456, Chicago, IL 94652</ship_add> <CW_type>dynamic<CVV_type>

<alert_rules>tar1 tar4 tar12</alert_rules>

</account>

<charge_priority>l</ charge_priority>

<charge_ratio>60%</charge_ratio>

<account_type>rewards</account_type>

<value_exchange_symbol>VME</value_exchange_symbol>

<account_number>234567890123456</account_number> <account_name>John Q. Public</account_name>

<bill_add>987 Green St #456, Chicago, IL 94652</bill_add> <ship_add>987 Green St #456, Chicago, IL 94652</ship_add> <CW_type>static<CW_type>

<cloak_flag>ON</cloak_flag>

<alert_rules>tar1 tar4 tar12</alert_rules>

<mode>Bluetooth</mode>

</account>

<charge_priority>2</ charge_priority>

<charge_ratio>100%</ charge_ratio>

<account_number>345678901234567</account_number> <account_type>credit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol>

<account_name>John Q. Public</account_name>

<cloak_flag>ON</cloak_flag>

<alert_rules>tar1 tar4 tar12</alert_rules>

</account>

</account_params>

<shipping_info>

<shipping_adress>#ref-ANON-123-45- 678</ shipping_address> <ship_type>expedited</ ship_type>

2 <ship_carrier>FedEx</ ship_carrier>

3 <ship_account>ANON-123-45-678</ship_account>

4 <tracking_flag>true</tracking_flag>

5 <sign_flag>false</ sign_flag>

6 </ shipping_info>

7 </card_authorization_request>

8

9 [00130] In some embodiments, the card authorization request generated by the

10 user device may include a minimum of information required to process the purchase

11 transaction. For example, this may improve the efficiency of communicating the

12 purchase transaction request, and may also advantageously improve the privacy

13 protections provided to the user and/or merchant. For example, in some embodiments,

14 the card authorization request may include at least a session ID for the user's shopping

15 session with the merchant. The session ID may be utilized by any component and/or

16 entity having the appropriate access authority to access a secure site on the merchant

17 server to obtain alerts, reminders, and/or other data about the transaction(s) within that

18 shopping session between the user and the merchant. In some embodiments, the PoS

19 client may provide the generated card authorization request to the merchant server, e.g.,

20 3316. The merchant server may forward the card authorization request to a pay gateway

21 server, e.g., 3304a, for routing the card authorization request to the appropriate

22 payment network for payment processing. For example, the pay gateway server may be

23 able to select from payment networks, such as Visa, Mastercard, American Express,

24 Paypal, etc., to process various types of transactions including, but not limited to: credit

25 card, debit card, prepaid card, B2B and/or like transactions. In some embodiments, the

26 merchant server may query a database, e.g., merchant/acquirer database 3303b, for a

27 network address of the payment gateway server, for example by using a portion of a user

28 payment card number, or a user ID (such as an email address) as a keyword for the database

29 query. For example, the merchant server may issue PHP/SQL commands to query a

30 database table (such as FIGURE 37, Pay Gateways 3719I1) for a URL of the pay gateway

31 server. An example payment gateway address query 3317, substantially in the form of

32 PHP/SQL commands, is provided below:

33 < ?PHP

34 header (' Content-Type : text/plain'); mysql_connect ("254.93.179.112", $DBserver, $password) ; // access database server mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

//create query

$query = "SELECT paygate_id paygate_address paygate_URL paygate_name FROM

PayGatewayTable WHERE card_num LIKE '%' $cardnum";

$result = mysql_query ( $query) ; // perform the search query

mysql_close ( "MCP_DB . SQL" ) ; // close database access

? > [00131] In response, the merchant/acquirer database may provide the requested payment gateway address, e.g., 3318. The merchant server may forward the card authorization request to the pay gateway server using the provided address, e.g., 3319. In some embodiments, upon receiving the card authorization request from the merchant server, the pay gateway server may invoke a component to provide one or more services associated with purchase transaction authorization. For example, the pay gateway server may invoke components for fraud prevention, loyalty and/or rewards, and/or other services for which the user-merchant combination is authorized. The pay gateway server may forward the card authorization request to a pay network server, e.g., 3305a, for payment processing. For example, the pay gateway server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions. In some embodiments, the pay gateway server may query a database, e.g., pay gateway database 3304b, for a network address of the payment network server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query. For example, the pay gateway server may issue PHP/SQL commands to query a database table (such as FIGURE 37, Pay Gateways 3719I1) for a URL of the pay network server. An example payment network address query 3321, substantially in the form of PHP/SQL commands, is provided below:

<?PHP

header (' Content-Type : text/plain');

mysql_connect ("254.93.179.112", $DBserver, $password) ; // access database server mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

//create query

$query = "SELECT payNET_id payNET_address payNET_URL payNET_name FROM 1 PayGatewayTable WHERE card_num LIKE '%' $cardnum";

2 $result = mysql_query ( $query) ; // perform the search query

3 mysql_close ( "MCP_DB . SQL" ) ; // close database access

4 ? >

5

6 [ 00132] In response, the payment gateway database may provide the requested

7 payment network address, e.g., 3322. The pay gateway server may forward the card

8 authorization request to the pay network server using the provided address, e.g., 3323.

9 [ 00133 ] With reference to FIGURE 33B, in some embodiments, the pay network

10 server may process the transaction so as to transfer funds for the purchase into an

11 account stored on an acquirer of the merchant. For example, the acquirer may be a

12 financial institution maintaining an account of the merchant. For example, the

13 proceeds of transactions processed by the merchant may be deposited into an account

14 maintained by at a server of the acquirer.

15 [ 00134] In some embodiments, the pay network server may generate a query, e.g.,

16 3324, for issuer server(s) corresponding to the user-selected payment options. For

17 example, the user's account may be linked to one or more issuer financial institutions

18 ("issuers"), such as banking institutions, which issued the account(s) for the user. For

19 example, such accounts may include, but not be limited to: credit card, debit card,

20 prepaid card, checking, savings, money market, certificates of deposit, stored (cash)

21 value accounts and/or the like. Issuer server(s), e.g., 3306a, of the issuer(s) may

22 maintain details of the user's account(s). In some embodiments, a database, e.g., pay

23 network database 3305b, may store details of the issuer server(s) associated with the

24 issuer(s). In some embodiments, the pay network server may query a database, e.g., pay

25 network database 3305b, for a network address of the issuer(s) server(s), for example by

26 using a portion of a user payment card number, or a user ID (such as an email address) as a

27 keyword for the database query. For example, the merchant server may issue PHP/SQL

28 commands to query a database table (such as FIGURE 37, Issuers 37191) for network

29 address(es) of the issuer (s) server (s). An example issuer server address(es) query 3324,

30 substantially in the form of PHP/SQL commands, is provided below:

31 <?PHP

32 header (' Content-Type : text/plain');

33 mysql_connect ( " 254 . 93 . 1 7 9 . 1 12 " , $DBserver, $password) ; // access database server mysql_select_db ( "MCP_DB . SQL" ) ; // select database table to search

//create query

$query = "SELECT issuer_id issuer_address issuer_URL issuer_name FROM

IssuersTable WHERE card_num LIKE '%' $cardnum";

$result = mysql_query ( $query) ; // perform the search query

mysql_close ( "MCP_DB . SQL" ) ; // close database access

?> [ooi35] In response to obtaining the issuer server query, e.g., 3324, the pay network database may provide, e.g., 3325, the requested issuer server data to the pay network server. In some embodiments, the pay network server may utilize the issuer server data to generate funds authorization request(s), e.g., 3326, for each of the issuer server (s) selected based on the pre-defined payment settings associated with the user's virtual wallet, and/or the user's payment options input, and provide the funds authorization request(s) to the issuer server (s). In some embodiments, the funds authorization request(s) may include details such as, but not limited to: the costs to the user involved in the transaction, card account details of the user, user billing and/or shipping information, and/or the like. An example listing of a funds authorization request 3326, substantially in the form of a HT P(S) POST message including XML- formatted data, is provided below:

POST /fundsauthorizationrequest .php HTTP/1.1

Host: www.issuer.com

Content-Type: Application/XML

Content-Length: 624

<?XML version = "1.0" encoding = "UTF-8"?>

<funds_authorization_request>

<request_ID>VNEl39FK</request_ID>

<debit_amount>$72.89</debit_amount>

<account_params>

<account_type>debit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol>

<account_number>123456789012345</account_number>

<account_name>John Q. Public</account_name>

<bill_add>987 Green St #456, Chicago, IL 94652</bill_add>

<ship_add>987 Green St #456, Chicago, IL 94652</ship_add>

</account_params>

<! --optional parameters—>

<user_device_fingerprint>

<device_IP>192.168.23.126</device_IP>

<device_MAC>0123.4567.89ab</device_MAC>

<device_serial>312456768798765432</device_serial>

<device_ECID>00000AEBCDF12345</device_ECID>

<device_identifier>j qp_air</device_identifier>

<device_UDID>21343e34-14f4-8jn4-7yfe-124578632134</device_UDID>

<device_browser>firefox 2.2</device_browser>

<device_type>smartphone</device_type>

<device_model>HTC Hero</device_model>

<OS>Android 2.2</OS>

<wallet_app_installed_flag>true</wallet_app_installed_flag> </user_device_fingerprint>

</ funds_authorization_request> [00136] In some embodiments, an issuer server may parse the authorization request(s), and based on the request details may query a database, e.g., user profile database 3306b, for data associated with an account linked to the user. For example, the merchant server may issue PHP/SQL commands to query a database table (such as FIGURE 37, Accounts 37i9d) for user account(s) data. An example user account(s) query 3327, substantially in the form of PHP/SQL commands, is provided below:

<?PHP

header (' Content-Type : text/plain');

//create query

$query = "SELECT issuer user_id user_name user_balance account_type FROM

AccountsTable WHERE account_num LIKE '%' $accountnum" ;

$result = mysql_query ( $query) ; // perform the search query

mysql_close ( "MCP_DB . SQL" ) ; // close database access

?> [00137] In some embodiments, on obtaining the user account(s) data, e.g., 3328, the issuer server may determine whether the user can pay for the transaction using funds available in the account, 3329. For example, the issuer server may determine whether the user has a sufficient balance remaining in the account, sufficient credit associated with the account, and/or the like. Based on the determination, the issuer server(s) may provide a funds authorization response, e.g., 3330, to the pay network server. For example, the issuer server(s) may provide a HT P(S) POST message similar to the examples above. In some embodiments, if at least one issuer server determines that the user cannot pay for the transaction using the funds available in the account, the pay network server may request payment options again from the user (e.g., by providing an authorization fail message to the user device and requesting the user device to provide new payment options), and re-attempt authorization for the purchase transaction. In some embodiments, if the number of failed authorization attempts exceeds a threshold, the pay network server may abort the authorization process, and provide an "authorization fail" message to the merchant server, user device and/or client. [00138] In some embodiments, the pay network server may obtain the funds authorization response including a notification of successful authorization, and parse the message to extract authorization details. Upon determining that the user possesses sufficient funds for the transaction, e.g., 3331, the pay network server may invoke a component to provide value-add services for the user. [00139] In some embodiments, the pay network server may generate a transaction data record from the authorization request and/or authorization response, and store the details of the transaction and authorization relating to the transaction in a transactions database. For example, the pay network server may issue PHP/SQL commands to store the data to a database table (such as FIGURE 37, Transactions 37191). An example transaction store command, substantially in the form of PHP/SQL commands, is provided below:

<?PHP

header (' Content-Type : text/plain');

mysql_connect ( " 254 . 92.185.103", $DBserver, $password) ; // access database server mysql_select ( "MCP_DB . SQL" ) ; // select database to append

mysql_query ("INSERT INTO TransactionsTable (PurchasesTable (timestamp,

purchase_summary_list, num_products , product_summary, product_quantity, transaction_cost, account_params_list, account_name, account_type,

account_num, billing_addres, zipcode, phone, sign, merchant_params_list, merchant_id, merchant_name, merchant_auth_key ) 1 VALUES (time(), $purchase_summary_list, $num_products , $product_summary,

2 $product_quantity, $transaction_cost, $account_params_list, $account_name

3 $account_type, $account_num, $billing_addres, $zipcode, $phone, $sign,

4 $merchant_params_list, $merchant_id, $merchant_name, $merchant_auth_key ) "

5 // add data to table in database

6 mysql_close ( "MCP_DB . SQL" ) ; // close connection to database

7 ?>

8

9 [00140 ] In some embodiments, the pay network server may forward a transaction

10 authorization response, e.g., 3332, to the user wallet device, PoS client, and/or merchant

11 server. The merchant may obtain the transaction authorization response, and

12 determine from it that the user possesses sufficient funds in the card account to conduct

13 the transaction. The merchant server may add a record of the transaction for the user to

14 a batch of transaction data relating to authorized transactions. For example, the

15 merchant may append the XML data pertaining to the user transaction to an XML data

16 file comprising XML data for transactions that have been authorized for various users,

¹⁷ e.g., 3333, and store the XML data file, e.g., 3334, in a database, e.g., merchant database

18404. For example, a batch XML data file may be structured similar to the example XML

19 data structure template provided below:

20 <?XML version = "1.0" encoding = "UTF-8"?>

21 <merchant_data>

22 <merchant_id>3FBCR4INC</merchant_id>

23 <merchant_name>Books & Things, Inc . </merchant_name>

24 <merchant_auth_key>lNNF484MCP59CHB27365</merchant_auth_key>

25 <account_number>123456789</account_number>

26 </merchant_data>

27 <transaction_data>

28 <transaction 1>

29

30 </ transaction 1>

31 <transaction 2>

32

33 </ transaction 2>

34

35

36

37 <transaction n> </ transaction n>

</transaction_data> [ 00141] In some embodiments, the server may also generate a purchase receipt, e.g., 3333, and provide the purchase receipt to the client, e.g., 3335. The client may render and display, e.g., 3336, the purchase receipt for the user. In some embodiments, the user's wallet device may also provide a notification of successful authorization to the user. For example, the PoS client/user device may render a webpage, electronic message, text / SMS message, buffer a voicemail, emit a ring tone, and/or play an audio message, etc., and provide output including, but not limited to: sounds, music, audio, video, images, tactile feedback, vibration alerts (e.g., on vibration-capable client devices such as a smartphone etc.), and/or the like. [ 00142 ] FIGURES 34A-B show logic flow diagrams illustrating example aspects of transforming a user virtual wallet access input via a Purchase Transaction Authorization ("PTA") component into a purchase transaction receipt notification. With reference to FIGURE 34A, in some embodiments, a user may wish to utilize a virtual wallet account to purchase a product, service, offering, and/or the like ("product"), from a merchant via a merchant online site or in the merchant's store. The user may utilize a physical card, or a user wallet device to access the user's virtual wallet account. For example, the user wallet device may be a personal/laptop computer, cellular telephone, smartphone, tablet, eBook reader, netbook, gaming console, and/or the like. The user may provide a wallet access input, e.g., 3401, into the user wallet device. In various embodiments, the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC equipped hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like. In some embodiments, the user wallet device may authenticate the user based on the user's wallet access input, and provide virtual wallet features for the user, e.g., 3402-3403. [ 00143 ] In some embodiments, upon authenticating the user for access to virtual 1 wallet features, the user wallet device may provide a transaction authorization input,

² e.g., 3404, to a point-of-sale ("PoS") client. For example, the user wallet device may

3 communicate with the PoS client via Bluetooth, Wi-Fi, cellular communication, one- or two-

4 way near-field communication ("NFC"), and/or the like. In embodiments where the user

5 utilizes a plastic card instead of the user wallet device, the user may swipe the plastic card at

6 the PoS client to transfer information from the plastic card into the PoS client. In

7 embodiments where the user utilizes a user wallet device, the user wallet device may

8 provide payment information to the PoS client, formatted according to a data formatting

9 protocol appropriate to the communication mechanism employed in the communication

10 between the user wallet device and the PoS client.

11 [ 00144 ] In some embodiments, the PoS client may obtain the transaction

12 authorization input, and parse the input to extract payment information from the

13 transaction authorization input, e.g., 3405. For example, the PoS client may utilize a

14 parser, such as the example parsers provided below in the discussion with reference to

15 FIGURE 37. The PoS client may generate a card authorization request, e.g., 3406, using

16 the obtained transaction authorization input from the user wallet device, and/or

17 product/checkout data (see, e.g., FIGURE 31, 3115-3117). is [ 00145 ] In some embodiments, the PoS client may provide the generated card

19 authorization request to the merchant server. The merchant server may forward the

20 card authorization request to a pay gateway server, for routing the card authorization

21 request to the appropriate payment network for payment processing. For example, the

22 pay gateway server may be able to select from payment networks, such as Visa,

23 Mastercard, American Express, Paypal, etc., to process various types of transactions

24 including, but not limited to: credit card, debit card, prepaid card, B2B and/or like

25 transactions. In some embodiments, the merchant server may query a database, e.g.,

26 3408, for a network address of the payment gateway server, for example by using a portion of

27 a user payment card number, or a user ID (such as an email address) as a keyword for the

28 database query. In response, the merchant/acquirer database may provide the requested

29 payment gateway address, e.g., 3410. The merchant server may forward the card

30 authorization request to the pay gateway server using the provided address. In some

31 embodiments, upon receiving the card authorization request from the merchant server, the pay gateway server may invoke a component to provide one or more service associated with purchase transaction authorization, e.g., 3411. For example, the pay gateway server may invoke components for fraud prevention (see e.g., VerifyChat, FIGURE 3E), loyalty and/or rewards, and/or other services for which the user-merchant combination is authorized. [ 00146 ] The pay gateway server may forward the card authorization request to a pay network server for payment processing, e.g., 3414. For example, the pay gateway server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions. In some embodiments, the pay gateway server may query a database, e.g., 3412, for a network address of the payment network server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query. In response, the payment gateway database may provide the requested payment network address, e.g., 3413. The pay gateway server may forward the card authorization request to the pay network server using the provided address, e.g., 3414. [ 00147] With reference to FIGURE 34B, in some embodiments, the pay network server may process the transaction so as to transfer funds for the purchase into an account stored on an acquirer of the merchant. For example, the acquirer may be a financial institution maintaining an account of the merchant. For example, the proceeds of transactions processed by the merchant may be deposited into an account maintained by at a server of the acquirer. In some embodiments, the pay network server may generate a query, e.g., 3415, for issuer server(s) corresponding to the user- selected payment options. For example, the user's account may be linked to one or more issuer financial institutions ("issuers"), such as banking institutions, which issued the account(s) for the user. For example, such accounts may include, but not be limited to: credit card, debit card, prepaid card, checking, savings, money market, certificates of deposit, stored (cash) value accounts and/or the like. Issuer server(s) of the issuer(s) may maintain details of the user's account(s). In some embodiments, a database, e.g., a pay network database, may store details of the issuer server(s) associated with the issuer(s). In some embodiments, the pay network server may query a database, e.g., 34!5, for a network address of the issuer(s) server(s), for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query. [o o i48 ] In response to obtaining the issuer server query, the pay network database may provide, e.g., 3416, the requested issuer server data to the pay network server. In some embodiments, the pay network server may utilize the issuer server data to generate funds authorization request(s), e.g., 3417, for each of the issuer server(s) selected based on the pre-defined payment settings associated with the user's virtual wallet, and/or the user's payment options input, and provide the funds authorization request(s) to the issuer server(s). In some embodiments, the funds authorization request(s) may include details such as, but not limited to: the costs to the user involved in the transaction, card account details of the user, user billing and/or shipping information, and/or the like. In some embodiments, an issuer server may parse the authorization request(s), e.g., 3418, and based on the request details may query a database, e.g., 3419, for data associated with an account linked to the user. [00149 ] In some embodiments, on obtaining the user account(s) data, e.g., 3420, the issuer server may determine whether the user can pay for the transaction using funds available in the account, e.g., 3421. For example, the issuer server may determine whether the user has a sufficient balance remaining in the account, sufficient credit associated with the account, and/or the like. Based on the determination, the issuer server(s) may provide a funds authorization response, e.g., 3422, to the pay network server. In some embodiments, if at least one issuer server determines that the user cannot pay for the transaction using the funds available in the account, the pay network server may request payment options again from the user (e.g., by providing an authorization fail message to the user device and requesting the user device to provide new payment options), and re-attempt authorization for the purchase transaction. In some embodiments, if the number of failed authorization attempts exceeds a threshold, the pay network server may abort the authorization process, and provide an "authorization fail" message to the merchant server, user device and/or client. [00150 ] In some embodiments, the pay network server may obtain the funds authorization response including a notification of successful authorization, and parse 1 the message to extract authorization details. Upon determining that the user possesses

2 sufficient funds for the transaction, e.g., 3423, the pay network server may invoke a

3 component to provide value-add services for the user, e.g., 3423.

4 [ 00151] In some embodiments, the pay network server may forward a transaction

5 authorization response to the user wallet device, PoS client, and/or merchant server.

6 The merchant may parse, e.g., 3424, the transaction authorization response, and

7 determine from it that the user possesses sufficient funds in the card account to conduct

8 the transaction, e.g., 3425, option"Yes." The merchant server may add a record of the

9 transaction for the user to a batch of transaction data relating to authorized

10 transactions. For example, the merchant may append the XML data pertaining to the

11 user transaction to an XML data file comprising XML data for transactions that have

12 been authorized for various users, e.g., 3426, and store the XML data file, e.g., 3427, in a

13 database. In some embodiments, the server may also generate a purchase receipt, e.g.,

14 3428, and provide the purchase receipt to the client. The client may render and display,

15 e.g., 3429, the purchase receipt for the user. In some embodiments, the user's wallet

16 device may also provide a notification of successful authorization to the user. For

17 example, the PoS client/user device may render a webpage, electronic message, text / is SMS message, buffer a voicemail, emit a ring tone, and/or play an audio message, etc.,

19 and provide output including, but not limited to: sounds, music, audio, video, images,

20 tactile feedback, vibration alerts (e.g., on vibration-capable client devices such as a

21 smartphone etc.), and/or the like.

22 [ 00152 ] FIGURES 35A-B show data flow diagrams illustrating example aspects of

23 transforming a merchant transaction batch data query via a Purchase Transaction

24 Clearance ("PTC") component into an updated payment ledger record. With reference

25 to FIGURE 35A, in some embodiments, a merchant server, e.g., 3503a, may initiate

26 clearance of a batch of authorized transactions. For example, the merchant server may

27 generate a batch data request, e.g., 3511, and provide the request, to a merchant

28 database, e.g., 3503b. For example, the merchant server may utilize PHP/SQL

29 commands similar to the examples provided above to query a relational database. In

30 response to the batch data request, the database may provide the requested batch data,

³¹ e.g., 3512. The server may generate a batch clearance request, e.g., 3513, using the batch data obtained from the database, and provide, e.g., 3514, the batch clearance request to an acquirer server, e.g., 3507a. For example, the merchant server may provide a HTTP(S) POST message including XML-formatted batch data in the message body for the acquirer server. The acquirer server may generate, e.g., 3515, a batch payment request using the obtained batch clearance request, and provide, e.g., 3518, the batch payment request to the pay network server, e.g., 3505a. The pay network server may parse the batch payment request, and extract the transaction data for each transaction stored in the batch payment request, e.g., 3519. The pay network server may store the transaction data, e.g., 3520, for each transaction in a database, e.g., pay network database 3505b. In some embodiments, the pay network server may invoke a component to provide value-add analytics services based on analysis of the transactions of the merchant for whom the MCP is clearing purchase transactions. Thus, in some embodiments, the pay network server may provide analytics-based value-added services for the merchant and/ or the merchant's users. [00153] With reference to FIGURE 35B, in some embodiments, for each extracted transaction, the pay network server may query, e.g., 3523, a database, e.g., pay network database 3505b, for an address of an issuer server. For example, the pay network server may utilize PHP/SQL commands similar to the examples provided above. The pay network server may generate an individual payment request, e.g., 3525, for each transaction for which it has extracted transaction data, and provide the individual payment request, e.g., 3525, to the issuer server, e.g., 3506a. For example, the pay network server may provide an individual payment request to the issuer server(s) as a HTTP(S) POST message including XML-formatted data. An example listing of an individual payment request 3525, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /paymentrequest.php HTTP/1.1

Host: www.issuer.com

Content-Type: Application/XML

Content-Length: 788

<?XML version = "1.0" encoding = "UTF-8"?>

<pay_request>

<request_ID>CNI4ICNW2</request_ID>

<account_params>

<account_type>debit</account_type>

<value_exchange_symbol>USD</value_exchange_symbol>

<account_number>123456789012345</account_number>

<account_name>John Q. Public</account_name>

<bill_add>987 Green St #456, Chicago, IL 94652</bill_add>

<ship_add>987 Green St #456, Chicago, IL 94652</ship_add>

</account>

</account_params>

</pay_request> [00154] In some embodiments, the issuer server may generate a payment command, e.g., 3527. For example, the issuer server may issue a command to deduct funds from the user's account (or add a charge to the user's credit card account). The issuer server may issue a payment command, e.g., 3527, to a database storing the user's account information, e.g., user profile database 3506b. The issuer server may provide an individual payment confirmation, e.g., 3528, to the pay network server, which may forward, e.g., 3529, the funds transfer message to the acquirer server. An example listing of an individual payment confirmation 3528, substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:

POST /clearance .php HTTP/1.1

Host: www.acquirer.com

Content-Type: Application/XML

Content-Length: 206

<?XML version = "1.0" encoding = "UTF-8"?>

<deposit_ack>

<request_ID>CNI4ICNW2</request_ID>

<clear_flag>true</clear_flag>

<deposit_amount>$72.89</deposit_amount>

</deposit_ack> [00155] In some embodiments, the acquirer server may parse the individual payment confirmation, and correlate the transaction (e.g., using the request_ID field in the example above) to the merchant. The acquirer server may then transfer the funds specified in the funds transfer message to an account of the merchant. For example, the acquirer server may query, e.g. 3530, an acquirer database 3507b for payment ledger and/or merchant account data, e.g., 3531. The acquirer server may utilize payment ledger and/or merchant account data from the acquirer database, along with the individual payment confirmation, to generate updated payment ledger and/or merchant account data, e.g., 3532. The acquirer server may then store, e.g., 3533, the updated payment ledger and/or merchant account data to the acquire database. [ 00156 ] FIGURES 36A-B show logic flow diagrams illustrating example aspects of transforming a merchant transaction batch data query via a Purchase Transaction Clearance ("PTC") component into an updated payment ledger record. With reference to FIGURE 36A, in some embodiments, a merchant server may initiate clearance of a batch of authorized transactions. For example, the merchant server may generate a batch data request, e.g., 3601, and provide the request to a merchant database. In response to the batch data request, the database may provide the requested batch data, e.g., 3602. The server may generate a batch clearance request, e.g., 3603, using the batch data obtained from the database, and provide the batch clearance request to an acquirer server. The acquirer server may parse, e.g., 3604, the obtained batch clearance request, and generate, e.g., 3607, a batch payment request using the obtained batch clearance request to provide, the batch payment request to a pay network server. For example, the acquirer server may query, e.g., 3605, an acquirer database for an address of a payment network server, and utilize the obtained address, e.g., 3606, to forward the generated batch payment request to the pay network server. [ 00157] The pay network server may parse the batch payment request obtained from the acquirer server, and extract the transaction data for each transaction stored in the batch payment request, e.g., 3608. The pay network server may store the transaction data, e.g., 3609, for each transaction in a pay network database. In some embodiments, the pay network server may invoke a component, e.g., 3610, to provide analytics based on the transactions of the merchant for whom purchase transaction are being cleared. [ 00158 ] With reference to FIGURE 36B, in some embodiments, for each extracted transaction, the pay network server may query, e.g., 3611, a pay network database for an 1 address of an issuer server. The pay network server may generate an individual

2 payment request, e.g., 3613, for each transaction for which it has extracted transaction

3 data, and provide the individual payment request to the issuer server. In some

4 embodiments, the issuer server may parse the individual payment request, e.g., 3614,

5 and generate a payment command, e.g., 3615, based on the parsed individual payment

6 request. For example, the issuer server may issue a command to deduct funds from the

7 user's account (or add a charge to the user's credit card account). The issuer server may

8 issue a payment command, e.g., 3615, to a database storing the user's account

9 information, e.g., a user profile database. The issuer server may provide an individual

10 payment confirmation, e.g., 3617, to the pay network server, which may forward, e.g.,

11 3618, the individual payment confirmation to the acquirer server.

12 [ 00159 ] In some embodiments, the acquirer server may parse the individual

13 payment confirmation, and correlate the transaction (e.g., using the request_ID field in

14 the example above) to the merchant. The acquirer server may then transfer the funds

15 specified in the funds transfer message to an account of the merchant. For example, the

16 acquirer server may query, e.g. 3619, an acquirer database for payment ledger and/or

17 merchant account data, e.g., 3620. The acquirer server may utilize payment ledger is and/or merchant account data from the acquirer database, along with the individual

19 payment confirmation, to generate updated payment ledger and/or merchant account

20 data, e.g., 3621. The acquirer server may then store, e.g., 3622, the updated payment

21 ledger and/or merchant account data to the acquire database.

22 MCP Controller

23 [ 00160 ] FIGURE 37 shows a block diagram illustrating example aspects of a MCP

24 controller 3701. In this embodiment, the MCP controller 3701 may serve to aggregate,

25 process, store, search, serve, identify, instruct, generate, match, and/or facilitate

26 interactions with a computer through various technologies, and/or other related data.

27 [ 00161 ] Users, e.g., 3733a, which may be people and/or other systems, may engage

28 information technology systems (e.g., computers) to facilitate information processing.

29 In turn, computers employ processors to process information; such processors 3703 1 may be referred to as central processing units (CPU). One form of processor is referred

2 to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals

3 acting as instructions to enable various operations. These instructions may be

4 operational and/or data instructions containing and/or referencing other instructions

5 and data in various processor accessible and operable areas of memory 3729 (e.g.,

6 registers, cache memory, random access memory, etc.). Such communicative

7 instructions may be stored and/or transmitted in batches (e.g., batches of instructions)

8 as programs and/or data components to facilitate desired operations. These stored

9 instruction codes, e.g., programs, may engage the CPU circuit components and other

10 motherboard and/or system components to perform desired operations. One type of

11 program is a computer operating system, which, may be executed by CPU on a

12 computer; the operating system enables and facilitates users to access and operate

13 computer information technology and resources. Some resources that may be employed

14 in information technology systems include: input and output mechanisms through

15 which data may pass into and out of a computer; memory storage into which data may

16 be saved; and processors by which information may be processed. These information

17 technology systems may be used to collect data for later retrieval, analysis, and

18 manipulation, which may be facilitated through a database program. These information

19 technology systems provide interfaces that allow users to access and operate various

20 system components.

21 [ 00162 ] In one embodiment, the MCP controller 3701 may be connected to and/or

22 communicate with entities such as, but not limited to: one or more users from user

23 input devices 3711; peripheral devices 3712; an optional cryptographic processor device

24 3728; and/or a communications network 3713. For example, the MCP controller 3701

25 may be connected to and/or communicate with users, e.g., 3733a, operating client

26 device(s), e.g., 3733b, including, but not limited to, personal computer(s), server(s)

27 and/or various mobile device(s) including, but not limited to, cellular telephone(s),

28 smartphone(s) (e.g., iPhone®, Blackberry®, Android OS-based phones etc.), tablet

29 computer(s) (e.g., Apple iPad™, HP Slate™, Motorola Xoom™, etc.), eBook reader(s)

30 (e.g., Amazon Kindle™, Barnes and Noble's Nook™ eReader, etc.), laptop computer(s),

31 notebook(s), netbook(s), gaming console(s) (e.g., XBOX Live™, Nintendo® DS, Sony PlayStation® Portable, etc.), portable scanner(s), and/or the like.

[00163] Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term "server" as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting "clients." The term "client" as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a "node." Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a "router." There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.

[00164] The MCP controller 3701 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 3702 connected to memory 3729. Computer Systemization

[00165] A computer systemization 3702 may comprise a clock 3730, central processing unit ("CPU(s)" and/or "processor(s)" (these terms are used interchangeably throughout the disclosure unless noted to the contrary)) 3703, a memory 3729 (e.g., a read only memory (ROM) 3706, a random access memory (RAM) 3705, etc.), and/or an interface bus 3707, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 3704 on one or more (mother)board(s) 1 3702 having conductive and/or otherwise transportive circuit pathways through which

2 instructions (e.g., binary encoded signals) may travel to effectuate communications,

3 operations, storage, etc. The computer systemization may be connected to a power

4 source 3786; e.g., optionally the power source may be internal. Optionally, a

5 cryptographic processor 3726 and/or transceivers (e.g., ICs) 3774 may be connected to

6 the system bus. In another embodiment, the cryptographic processor and/or

7 transceivers may be connected as either internal and/or external peripheral devices

8 3712 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s)

⁹ 3775, thereby effectuating wireless transmission and reception of various0 communication and/or sensor protocols; for example the antenna(s) may connect to: a1 Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.1m, Bluetooth2 3.0, FM, global positioning system (GPS) (thereby allowing MCP controller to determine3 its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.1m,4 Bluetooth 2.1 + EDR, FM, etc.), BCM28150 (HSPA+) and BCM2076 (Bluetooth 4.0,5 GPS, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon6 Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA7 communications); Intel's XMM 7160 (LTE & DC-HSPA), Qualcom's CDMA(2000),8 Mobile Data/Station Modem, Snapdragon; and/or the like. The system clock may have a9 crystal oscillator and generates a base signal through the computer systemization's0 circuit pathways. The clock may be coupled to the system bus and various clock1 multipliers that will increase or decrease the base operating frequency for other2 components interconnected in the computer systemization. The clock and various3 components in a computer systemization drive signals embodying information4 throughout the system. Such transmission and reception of instructions embodying5 information throughout a computer systemization may be referred to as6 communications. These communicative instructions may further be transmitted,7 received, and the cause of return and/or reply communications beyond the instant8 computer systemization to: communications networks, input devices, other computer9 systemizations, peripheral devices, and/or the like. It should be understood that in0 alternative embodiments, any of the above components may be connected directly to1 one another, connected to the CPU, and/or organized in numerous variations employed2 as exemplified by various computer systems. [ 00166 ] The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: floating point units, integer processing units, integrated system (bus) controllers, logic operating units, memory management control units, etc., and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 3729 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state/value. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's classic (e.g., ARM7/9/11), embedded (Coretx-M/R), application (Cortex-A), embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Atom, Celeron (Mobile), Core (2/Duo/i3/i5/i7), Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code). Such instruction passing facilitates communication within the MCP controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed MCP), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller mobile devices (e.g., smartphones, Personal Digital Assistants (PDAs), etc.) may be employed.

[ 00167] Depending on the particular implementation, features of the MCP may be achieved by implementing a microcontroller such as CAST'S R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the MCP, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit ("ASIC"), Digital Signal Processing ("DSP"), Field Programmable Gate Array ("FPGA"), and/or the like embedded technology. For example, any of the MCP component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the MCP may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.

[00168] Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/ software solutions. For example, MCP features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called "logic blocks", and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the MCP features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the MCP system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGAs logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or simple mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the MCP may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate MCP controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the "CPU" and/or "processor" for the MCP. Power Source

[00169] The power source 3786 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 3786 is connected to at least one of the interconnected subsequent components of the MCP thereby providing an electric current to all the interconnected components. In one example, the power source 3786 is connected to the system bus component 3704. In an alternative embodiment, an outside power source 3786 is provided through a connection across the I/O 3708 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power. Interface Adapters

[00170] Interface bus(ses) 3707 may accept, connect, and/or communicate to a number of interface adapters, frequently, although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 3708, storage interfaces 3709, network interfaces 3710, and/or the like. Optionally, cryptographic processor interfaces 3727 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters may connect to the interface bus via expansion and/or slot architecture. Various expansion and/or slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, ExpressCard, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), Thunderbolt, and/or the like.

[00171] Storage interfaces 3709 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 3714, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, Ethernet, fiber channel, Small Computer Systems Interface (SCSI), Thunderbolt, Universal Serial Bus (USB), and/or the like.

[00172] Network interfaces 3710 may accept, communicate, and/or connect to a communications network 3713. Through a communications network 3713, the MCP controller is accessible through remote clients 3733b (e.g., computers with web browsers) by users 3733a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 8o2.na-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed MCP), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the MCP controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 3710 may be used to engage with various communications network types 3713. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.

[00173] Input Output interfaces (I/O) 3708 may accept, communicate, and/or connect to user input devices 3711, peripheral devices 3712, cryptographic processor devices 3728, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), Bluetooth, IEEE I394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, DisplayPort, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 8o2.na/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One output device may be a video display, which may take the form of a Cathode Ray Tube (CRT), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic Light Emitting Diode (OLED), Plasma, and/or the like based monitor with an interface (e.g., VGA, DVI circuitry and cable) that accepts signals from a video interface. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Often, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, HDMI, etc.). [ 00174] User input devices 3711 often are a type of peripheral device 3712 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like. [ 00175] Peripheral devices 3712 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the MCP controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 3728), force-feedback devices (e.g., vibrating motors), near field communication (NFC) devices, network interfaces, printers, radio 1 frequency identifiers (RFIDs), scanners, storage devices, transceivers (e.g., cellular,

2 GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the

3 like. Peripheral devices often include types of input devices (e.g., microphones, cameras,

4 etc.).

5 [o o i76] It should be noted that although user input devices and peripheral devices

6 may be employed, the MCP controller may be embodied as an embedded, dedicated,

7 and/or monitor-less (i.e., headless) device, wherein access would be provided over a

8 network interface connection.

9 [00177] Cryptographic units such as, but not limited to, microcontrollers,

10 processors 3726, interfaces 3727, and/or devices 3728 may be attached, and/or

11 communicate with the MCP controller. A MC68HC16 microcontroller, manufactured by

12 Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16

13 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz

14 configuration and requires less than one second to perform a 512-bit RSA private key

15 operation. Cryptographic units support the authentication of communications from

16 interacting agents, as well as allowing for anonymous transactions. Cryptographic units

17 may also be configured as part of the CPU. Equivalent microcontrollers and/or is processors may also be used. Other commercially available specialized cryptographic

19 processors include: the Broadcom's CryptoNetX and other Security Processors;

20 nCipher's nShield (e.g., Solo, Connect, etc.), SafeNet's Luna PCI (e.g., 7100) series;

21 Semaphore Communications' 40 MHz Roadrunner 184; sMIP's (e.g., 208956); Sun's

22 Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500

23 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable

24 of performing 500+ MB/s of cryptographic instructions; VLSI Technology's 33 MHz

25 6868; and/or the like.

26 Memory

27 [00178] Generally, any mechanization and/or embodiment allowing a processor to

28 affect the storage and/or retrieval of information is regarded as memory 3729. However,

29 memory is a fungible technology and resource, thus, any number of memory

30 embodiments may be employed in lieu of or in concert with one another. It is to be understood that the MCP controller and/or a computer systemization may employ various forms of memory 3729. For example, a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation. In one configuration, memory 3729 may include ROM 3706, RAM 3705, and a storage device 3714. A storage device 3714 may employ any number of computer storage devices/systems. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory. Component Collection

[00179] The memory 3729 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 37!5 (operating system); information server component(s) 3716 (information server); user interface component(s) 3717 (user interface); Web browser component(s) 3718 (Web browser); database(s) 3719; mail server component(s) 3721; mail client component(s) 3722; cryptographic server component(s) 3720 (cryptographic server); the MCP component(s) 3735; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although non-conventional program components such as those in the component collection may be stored in a local storage device 3714, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.

Operating System 1 [00180] The operating system component 3715 is an executable program

2 component facilitating the operation of the MCP controller. The operating system may

3 facilitate access of I/O, network interfaces, peripheral devices, storage devices, and/or

4 the like. The operating system may be a highly fault tolerant, scalable, and secure system

5 such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like

6 system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD)

7 variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions

8 such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However,

9 more limited and/or less secure operating systems also may be employed such as Apple

10 Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows

11 2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like.

12 In addition, emobile operating systems such as Apple's iOS, Google's Android, Hewlett

13 Packard's WebOS, Microsofts Windows Mobile, and/or the like may be employed. Any

14 of these operating systems may be embedded within the hardware of the NICK

15 controller, and/or stored/loaded into memory/storage. An operating system may

16 communicate to and/or with other components in a component collection, including

17 itself, and/or the like. Most frequently, the operating system communicates with other

18 program components, user interfaces, and/or the like. For example, the operating

19 system may contain, communicate, generate, obtain, and/or provide program

20 component, system, user, and/or data communications, requests, and/or responses. The

21 operating system, once executed by the CPU, may enable the interaction with

22 communications networks, data, I/O, peripheral devices, program components,

23 memory, user input devices, and/or the like. The operating system may provide

24 communications protocols that allow the MCP controller to communicate with other

25 entities through a communications network 3713. Various communication protocols

26 may be used by the MCP controller as a subcarrier transport mechanism for interaction,

27 such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.

28 Information Server

29 [00181] An information server component 3716 is a stored program component

30 that is executed by a CPU. The information server may be an Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Apple's iMessage, Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the MCP controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request "123.124.125.126" resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the "/mylnformation.html" portion of the request and resolve it to a location in memory containing the information "mylnformation.html." Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the MCP database 1 3719, operating systems, other program components, user interfaces, Web browsers,

2 and/or the like.

3 [00182] Access to the MCP database may be achieved through a number of

4 database bridge mechanisms such as through scripting languages as enumerated below

5 (e.g., CGI) and through inter-application communication channels as enumerated below

6 (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed

7 through the bridge mechanism into appropriate grammars as required by the MCP. In

8 one embodiment, the information server would provide a Web form accessible by a Web

9 browser. Entries made into supplied fields in the Web form are tagged as having been0 entered into the particular fields, and parsed as such. The entered terms are then passed1 along with the field tags, which act to instruct the parser to generate queries directed to2 appropriate tables and/or fields. In one embodiment, the parser may generate queries in3 standard SQL by instantiating a search string with the proper join/select commands4 based on the tagged text entries, wherein the resulting command is provided over the5 bridge mechanism to the MCP as a query. Upon generating query results from the6 query, the results are passed over the bridge mechanism, and may be parsed for7 formatting and generation of a new results Web page by the bridge mechanism. Such a8 new results Web page is then provided to the information server, which may supply it to9 the requesting Web browser.

0 [00183] Also, an information server may contain, communicate, generate, obtain,1 and/or provide program component, system, user, and/or data communications,2 requests, and/or responses. 3 User Interface

4 [00184] Computer interfaces in some respects are similar to automobile operation5 interfaces. Automobile operation interface elements such as steering wheels, gearshifts,6 and speedometers facilitate the access, operation, and display of automobile resources,7 and status. Computer interaction interface elements such as check boxes, cursors,8 menus, scrollers, and windows (collectively and commonly referred to as widgets)9 similarly facilitate the access, capabilities, operation, and display of data and computer0 hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua and iOS's Cocoa Touch, IBM's OS/2, Google's Android Mobile UI, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millenium/ Mobile/NT/XP/Vista/7/8 (i.e., Aero, Metro), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.

[00185] A user interface component 3717 is a stored program component that is executed by a CPU. The user interface may be a graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Web Browser

[00186] A Web browser component 3718 is a stored program component that is executed by a CPU. The Web browser may be a hypertext viewing application such as Goofle's (Mobile) Chrome, Microsoft Internet Explorer, Netscape Navigator, Apple's (Mobile) Safari, embedded web browser objects such as through Apple's Cocoa (Touch) object class, and/or the like. Secure Web browsing may be supplied with i28bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., Chrome, FireFox, Internet Explorer, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, smartphones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly effect the obtaining and the provision of information to users, user agents, and/or the like from the MCP equipped nodes. The combined application may be nugatory on systems employing standard Web browsers. Mail Server

[00187] A mail server component 3721 is a stored program component that is executed by a CPU 3703. The mail server may be an Internet mail server such as, but not limited to Apple's Mail Server (3), dovect, sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the MCP.

[00188] Access to the MCP mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system. [00189] Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Mail Client

[00190] A mail client component 3722 is a stored program component that is executed by a CPU 3703. The mail client may be a mail viewing application such as Apple (Mobile) Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages. Cryptographic Server

[00191] A cryptographic server component 3720 is a stored program component that is executed by a CPU 3703, cryptographic processor 3726, cryptographic processor interface 3727, cryptographic processor device 3728, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the MCP may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of "security authorization" whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the MCP component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the MCP and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The MCP Database

[00192] The MCP database component 3719 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be any of a number of fault tolerant, relational, scalable, secure 1 databases, such as DB2, MySQL, Oracle, Sybase, and/or the like. Relational databases

2 are an extension of a flat file. Relational databases consist of a series of related tables.

3 The tables are interconnected via a key field. Use of the key field allows the combination

4 of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot

5 points for combining information from various tables. Relationships generally identify

6 links maintained between tables by matching primary keys. Primary keys represent

7 fields that uniquely identify the rows of a table in a relational database. More precisely,

8 they uniquely identify rows of a table on the "one" side of a one-to-many relationship.

9 [ 00193 ] Alternatively, the MCP database may be implemented using various

10 standard data-structures, such as an array, hash, (linked) list, struct, structured text file

11 (e.g., XML), table, and/or the like. Such data-structures may be stored in memory

12 and/or in (structured) files. In another alternative, an object-oriented database may be

13 used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can

14 include a number of object collections that are grouped and/or linked together by

15 common attributes; they may be related to other object collections by some common

16 attributes. Object-oriented databases perform similarly to relational databases with the

17 exception that objects are not just pieces of data but may have other types of capabilities

18 encapsulated within a given object. If the MCP database is implemented as a data-

19 structure, the use of the MCP database 3719 may be integrated into another component

20 such as the MCP component 3735. Also, the database may be implemented as a mix of

21 data structures, objects, and relational structures. Databases may be consolidated

22 and/or distributed in countless variations through standard data processing techniques.

23 Portions of databases, e.g., tables, may be exported and/or imported and thus

24 decentralized and/or integrated.

25 [ 00194 ] In one embodiment, the database component 3719 includes several tables

26 37i9a-t. A Users table 3719a may include fields such as, but not limited to: user_id, ssn,

27 dob, first_name, last_name, age, state, address_firstline, address_secondline, zipcode,

28 devices_list, contact_info, contact_type, alt_contact_info, alt_contact_type, and/or the

29 like. The Users table may support and/or track multiple entity accounts on a MCP. A

30 Devices table 3719b may include fields such as, but not limited to: device_ID,

31 device_name, device_IP, device_GPS, device_MAC, device_serial, device_ECID, device_UDID, device_browser, device_type, device_model, device_version, device_OS, device_apps_list, device_securekey, wallet_app_installed_ flag, and/or the like. An Apps table 3719c may include fields such as, but not limited to: app_ID, app_name, app_type, app_dependencies, app_access_code, user_pin, and/or the like. An Accounts table 37i9d may include fields such as, but not limited to: account_number, account_security_code, account_name, issuer_acquirer_flag, issuer_name, acquirer_name, account_address, routing_number, access_API_call, linked_wallets_list, and/or the like. A Merchants table 3719ε may include fields such as, but not limited to: merchant_id, merchant_name, merchant_address, store_id, ip_address, mac_address, auth_key, port_num, security_settings_list, and/or the like. An Issuers table 37i9f may include fields such as, but not limited to: issuer_id, issuer_name, issuer_address, ip_address, mac_address, auth_key, port_num, security_settings_list, and/or the like. An Acquirers table 37i9g may include fields such as, but not limited to: account_firstname, account_lastname, account_type, account_num, account_ balance_list, billingaddress_ linei, billingaddress_ line2, billing_zipcode, billing_state, shipping_preferences, shippingaddress_linei, shippingaddress_line2, shipping_ zipcode, shipping_state, and/or the like. A Pay Gateways table 3719I1 may include fields such as, but not limited to: gateway_ID, gateway_IP, gateway_MAC, gateway_secure_key, gateway_access_list, gateway_API_call_list, gateway_services_list, and/or the like. A Shop Sessions table 37191 may include fields such as, but not limited to: user_id, session_id, alerts_URL, timestamp, expiry_lapse, merchant_id, store_id, device_type, device_ID, device_IP, device_MAC, device_browser, device_serial, device_ECID, device_model, device_OS, wallet_app_installed, total_cost, cart_ID_list, product_params_list, social_flag, social_message, social_networks_list, coupon_lists, accounts_list, CW2_lists, charge_ratio_list, charge_priority_list, value_exchange_symbols_list, bill_address, ship_address, cloak_flag, pay_mode, alerts_rules_list, and/or the like. A Transactions table 37i9j may include fields such as, but not limited to: order_id, user_id, timestamp, transaction_cost, purchase_details_list, num_products, products_list, product_type, product_params_list, product_title, product_summary, quantity, user_id, client_id, client_ip, client_type, client_model, operating_system, os_version, app_installed_flag, user_id, account_firstname, account_lastname, account_type, account_num, 1 account_priority_account_ratio, billingaddress_linei, billingaddress_line2,

2 billing_zipcode, billing_state, shipping_preferences, shippingaddress_linei,

3 shippingaddress_line2, shipping_ zipcode, shipping_state, merchant_id,

4 merchant_name, merchant_auth_key, and/or the like. A Batches table 3719k may

5 include fields such as, but not limited to: batch_id, transaction_id_list, timestamp_list,

6 cleared_flag_list, clearance_trigger_ settings, and/or the like. A Ledgers table 3719I

7 may include fields such as, but not limited to: request_id, timestamp, deposit_amount,

8 batch_id, transaction_id, clear_flag, deposit_account, transaction_summary, payor_

9 name, payor_account, and/or the like. A Products table 3719m may include fields such

10 as, but not limited to: product_ID, product_title, product_attributes_list,

11 product_price, tax_info_list, related_products_ list, offers_list, discounts_list,

12 rewards_list, merchants_list, merchant_availability_list, and/or the like. An Offers

13 table 3719η may include fields such as, but not limited to: offer_ID, offer_title,

14 offer_attributes_list, offer_price, offer_expiry, related_products_ list, discounts_list,

15 rewards_list, merchants_list, merchant_availability_list, and/or the like. A Behavior

16 Data table 37190 may include fields such as, but not limited to: user_id, timestamp,

17 activity_type, activity_location, activity_attribute_list, activity_attribute_values_list,

18 and/or the like. An Analytics table 3719P may include fields such as, but not limited to:

19 report_id, user_id, report_type, report_algorithm_id, report_destination_address,

20 and/or the like. A Campaign Set-Up Page table 37i9q may include fields such as, but

21 not limited to: page_id, page_template_id, page_fields, page_fields_default_value,

22 page_merchant_type, page_issuer_type, and/or the like. An enrollment form table

23 37i9r may include fields such as, but not limited to: form_id, form_name, form_type,

24 form_merchant_id, form_merchant_type, form_field, form_field_default_value,

25 and/or the like. A Campaign table 3719s may include fields such as, but not limited to:

26 campaigned, campaign_name, campaign_type, campaign_merchant_id,

27 campaign_merchant_type, campaign_units, campaign_discount, campaign_brand,

28 campaign_term, and/or the like. An API table 37i9t may include fields such as, but not

29 limited to: API_id, API_id, API_site_name, API_site_id, API_type API_template_id,

30 API_key, secret,token, sample_code, and/or the like.

31 [ 00195 ] In one embodiment, the MCP database may interact with other database systems. For example, employing a distributed database system, queries and data access by search MCP component may treat the combination of the MCP database, an integrated data security layer database as a single database entity.

[ooi96] In one embodiment, user programs may contain various user interface primitives, which may serve to update the MCP. Also, various accounts may require custom database tables depending upon the environments and the types of clients the MCP may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 37i9a-t. The MCP may be configured to keep track of various settings, inputs, and parameters via database controllers.

[00197] The MCP database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MCP database communicates with the MCP component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data. The MCPs

[00198] The MCP component 3735 is a stored program component that is executed by a CPU. In one embodiment, the MCP component incorporates any and/or all combinations of the aspects of the MCP discussed in the previous figures. As such, the MCP affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks. The features and embodiments of the MCP discussed herein increase network efficiency by reducing data transfer requirements the use of more efficient data structures and mechanisms for their transfer and storage. As a consequence, more data may be transferred in less time, and latencies with regard to transactions, are also reduced. In many cases, such reduction in storage, transfer time, bandwidth requirements, latencies, etc., will reduce the capacity and structural infrastructure requirements to support the MCP's features and facilities, and in many cases reduce the costs, energy consumption/requirements, and extend the life of MCP's underlying infrastructure; this has the added benefit of making the MCP more reliable. Similarly, many of the features and mechanisms are designed to be easier for users to use and access, thereby broadening the audience that may enjoy/employ and exploit the feature sets of the MCP; such ease of use also helps to increase the reliability of the MCP. In addition, the feature sets include heightened security as noted via the Cryptographic components 3720, 3726, 3728 and throughout, making access to the features and data more reliable and secure. [ 00199 ] The MCP component may transform merchant transaction record and onboarding request via MCP components into merchant registration output, campaign ads and/or the like and use of the MCP. In one embodiment, the MCP component 3735 takes inputs (e.g., merchant profile information 2i5a-b, checkout request 3111; product data 3115; wallet access input 3311; transaction authorization input 3314; payment gateway address 3318; payment network address 3322; issuer server address(es) 3325; funds authorization request(s) 3326; user(s) account(s) data 3328; batch data 3512; payment network address 3516; issuer server address(es) 3524; individual payment request 3525; payment ledger, merchant account data 3531; and/or the like) etc., and transforms the inputs via various components (e.g., UPC 3741; PTA 3742; PTC 3743; merchant enrollment 3744, merchant analytics 3745, campaign setup 3746, and/or the like), into outputs (e.g., checkout widget 234, campaign plan 276, checkout request message 3113; checkout data 3117; card authorization request 3316, 3323; funds authorization response(s) 3330; transaction authorization response 3332; batch append data 3334; purchase receipt 3335; batch clearance request 3514; batch payment request 3518; transaction data 3520; individual payment confirmation 3528, 3529; updated payment ledger, merchant account data 3533; and/or the like). [ 00200 ] The MCP component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the MCP server employs a cryptographic server to encrypt and decrypt communications. The MCP component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MCP component communicates with the MCP database, operating systems, other program components, and/or the like. The MCP may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Distributed MCPs

[00201] The structure and/or operation of any of the MCP node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.

[00202] The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.

[00203] The configuration of the MCP controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.

[00204] If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.

[00205] For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:

w3c -post http : / / . . . Valuel [00206] where Valuei is discerned as being a parameter because "http://" is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable "Valuei" may be inserted into an "http://" post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.

[00207] For example, in some implementations, the MCP controller may be executing a PHP script implementing a Secure Sockets Layer ("SSL") socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language ("SQL"). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below:

<?PHP

header (' Content-Type : text/plain'); // set ip address and port to listen to for incoming data

$address = ¹192.168.0.100 ' ; $port = 255; // create a server-side SSL socket, listen for/accept incoming communication $sock = socket_create (AF_INET, SOCK_STREAM, 0 ) ;

socket_bind ($sock, $address, $port) or die ( 'Could not bind to address');

socket_listen ($sock) ;

$client = socket_accept ($sock) ; // read input data from client device in 1024 byte blocks until end of message do {

$ input = "";

$input = socket_read ( $client, 1024);

$data .= $input;

} while ($ input != "") ; // parse data to extract variables

$obj = j son_decode ( $data, true) ; // store input data in a database

mysql_connect ( "201.408.185.132 " , $DBserver , $password) ; // access database server mysql_select ( "CLIENT_DB . SQL" ) ; // select database to append

mysql_query ("INSERT INTO UserTable (transmission)

VALUES ($data)"); // add data to UserTable table in a CLIENT database

mysql_close ( "CLIENT_DB. SQL" ) ; // close connection to database

?> [00208] Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation:

http : / /www . xav . com/perl/ site/ lib/ SOAP/Parser . html

http : / /publib . boulder . ibm . com/ infocenter/tivihelp/v2rl/ index. j sp?topic=/com . ibm . IBMDI . doc/referenceguide295. htm [00209] and other parser implementations:

http : / /publib . boulder . ibm . com/ infocenter/tivihelp/v2rl/ index. j sp?topic=/com . ibm . IBMDI . doc/ referenceguide259. htm [oo21o ] all of which are hereby expressly incorporated by reference herein.

[00211] In order to address various issues and advance the art, the entirety of this application for MERCHANT CONTROL PLATFORM APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices and/or otherwise) shows by way of illustration various example embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any data flow sequence(s), program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, processors, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are also contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations, including the right to claim such innovations, file additional applications, continuations, continuations-in-part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a MCP individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the MCP may be implemented that allow a great deal of flexibility and customization. For example, aspects of the MCP may be adapted for offer targeting. While various embodiments and discussions of the MCP have been directed to electronic transactions, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.

Claims

CLAI MS

What is claimed is:

l. A processor-implemented merchant enrollment method, comprising:

receiving a merchant enrollment request via a user interface;

identifying a merchant type as one of a business merchant and an individual merchant;

automatically retrieving a merchant enrollment template based on the identified merchant type,

said merchant enrollment template requests federal business identification for a business merchant and individual identification for a individual merchant;

retrieving merchant issuer information requirement;

generating a bank account information form section reflecting the merchant issuer information requirement;

populating the retrieved merchant enrollment template with the generated bank account information form section;

prompting a merchant to submit registration information and bank account information requested by the merchant enrollment template and the bank account information form section via a user interface;

obtaining merchant submitted registration information from the merchant enrollment template via the user interface,

wherein the registration information is based on the merchant type and reduces redundant information to improve transmission efficiency;

verifying merchant status via background check procedures based on the submitted registration information;

generating a merchant enrollment record; and

using merchant information from the generated merchant enrollment record to instantiate merchant facilities. 2. A processor-implemented merchant enrollment method, comprising: receiving a merchant enrollment request via a user interface;

identifying a merchant type;

automatically retrieving a merchant enrollment template based on the identified merchant type;

retrieving merchant issuer information requirement;

obtaining merchant submitted registration information from the merchant enrollment template via the user interface;

verifying merchant status via background check procedures based on the submitted registration information; and

generating a merchant enrollment record. 3. The method of claim 2, wherein the user interface comprises a web based application. 4. The method of claim 2, wherein the user interface comprises a mobile based application. 5. The method of claim 2, wherein the merchant type comprises a business merchant 6. The method of claim 2, wherein the merchant type comprises an individual merchant. 7. The method of claim 2, wherein the merchant enrollment template requests federal business identification for a business merchant

8. The method of claim 2, wherein the merchant enrollment template requests individual identification for a individual merchant. 9. The method of claim 2, wherein the merchant enrollment template requests company information for a business merchant. 10. The method of claim 2, wherein the merchant enrollment template requests bank account information. 11. The method of claim 2, wherein the merchant enrollment template requests customer service information. 12. The method of claim 2, wherein the merchant enrollment template requests business contact information. 13. The method of claim 2, wherein the merchant enrollment template requests accepted payment method information. 14. The method of claim 2, wherein the registration information is based on the merchant type and reduces redundant information to improve transmission efficiency. 15. The method of claim 2, wherein the background check procedures comprises credit check. 16. The method of claim 2, wherein the background check procedures are performed by a third party entity. 17. The method of claim 2, wherein the merchant submits an application generation request. i8. The method of claim 17, wherein the application generation request comprises a checkout widget generation request. 19. The method of claim 17, wherein the merchant receives a formatted widget for incorporation into a merchant site. 20. The method of claim 2, wherein the merchant creates a merchant site upon enrollment. 21. A processor-implemented merchant enrollment system, comprising:

a memory;

a processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues instructions to:

receive a merchant enrollment request via a user interface;

identify a merchant type;

automatically retrieve a merchant enrollment template based on the identified merchant type;

retrieve merchant issuer information requirement;

generate a bank account information form section reflecting the merchant issuer information requirement;

populate the retrieved merchant enrollment template with the generated bank account information form section;

prompt a merchant to submit registration information and bank account information requested by the merchant enrollment template and the bank account information form section via a user interface;

obtain merchant submitted registration information from the merchant enrollment template via the user interface;

verify merchant status via background check procedures based on the submitted registration information; and

generate a merchant enrollment record..

22. The system of claim 21, wherein the system is associated with a payment network. 23. The system of claim 21, wherein the user interface comprises a web based application. 24. The system of claim 21, wherein the user interface comprises a mobile based application. 25. The system of claim 21, wherein the merchant type comprises a business merchant 26. The system of claim 21, wherein the merchant type comprises an individual merchant. 27. The system of claim 21, wherein the merchant enrollment template requests federal business identification for a business merchant 28. The system of claim 21, wherein the merchant enrollment template requests individual identification for a individual merchant. 29. The system of claim 21, wherein the merchant enrollment template requests company information for a business merchant. 30. The system of claim 21, wherein the merchant enrollment template requests bank account information. 31. The system of claim 21, wherein the merchant enrollment template requests customer service information. 32. The system of claim 21, wherein the merchant enrollment template requests business contact information.

33. The system of claim 21, wherein the merchant enrollment template requests accepted payment system information. 34. The system of claim 21, wherein the registration information is based on the merchant type and reduces redundant information to improve transmission efficiency. 35. The system of claim 21, wherein the background check procedures comprises credit check. 36. The system of claim 21, wherein the background check procedures are performed by a third party entity. 37. The system of claim 21, wherein the merchant submits an application generation request. 38. The system of claim 37, wherein the application generation request comprises a checkout widget generation request. 39. The system of claim 37, wherein the merchant receives a formatted widget for incorporation into a merchant site. 40. The system of claim 1, wherein the merchant creates a merchant site upon enrollment. 41. A merchant enrollment processor-readable non-transitory medium storing instructions executable by a processor to:

receive a merchant enrollment request via a user interface;

identify a merchant type;

automatically retrieve a merchant enrollment template based on the identified merchant type; retrieve merchant issuer information requirement;

generate a merchant enrollment record.. 42. The medium of claim 41, wherein the medium is associated with a payment network. 43. The medium of claim 41, wherein the user interface comprises a web based application. 44. The medium of claim 41, wherein the user interface comprises a mobile based application. 45. The medium of claim 41, wherein the merchant type comprises a business merchant 46. The medium of claim 41, wherein the merchant type comprises an individual merchant. 47. The medium of claim 41, wherein the merchant enrollment template requests federal business identification for a business merchant

48. The medium of claim 41, wherein the merchant enrollment template requests individual identification for a individual merchant. 49. The medium of claim 41, wherein the merchant enrollment template requests company information for a business merchant. 50. The medium of claim 41, wherein the merchant enrollment template requests bank account information. 51. The medium of claim 41, wherein the merchant enrollment template requests customer service information. 52. The medium of claim 41, wherein the merchant enrollment template requests business contact information. 53. The medium of claim 41, wherein the merchant enrollment template requests accepted payment medium information. 54. The medium of claim 41, wherein the registration information is based on the merchant type and reduces redundant information to improve transmission efficiency. 55. The medium of claim 41, wherein the background check procedures comprises credit check. 56. The medium of claim 41, wherein the background check procedures are performed by a third party entity. 57. The medium of claim 41, wherein the merchant submits an application generation request. 58. The medium of claim 57, wherein the application generation request I comprises a checkout widget generation request.

2

3 59. The medium of claim 57, wherein the merchant receives a formatted

4 widget for incorporation into a merchant site.

5

6 60. The medium of claim 41, wherein the merchant creates a merchant site

7 upon enrollment.

8

9 61. A processor-implemented merchant control platform method, comprising:

10 receiving a merchant request for sales performance analytics;

I I providing a merchant control panel to a merchant, wherein the merchant control

12 panel facilitates a merchant to view sales performance;

13 obtaining merchant specified sales performance representation parameters;

14 generating a graphical representation of merchant sales performance;

15 obtaining merchant interested analytics indicia via a user interface;

16 generating performance-improving heuristics reflecting the merchant interested

17 analytics indicia for a merchant campaign;

is generating stackable campaign parameter blocks pre-populated with

19 recommended merchant campaign parameters based on the performance-improving

20 heuristics;

21 obtaining merchant specified campaign parameters from the stackable campaign

22 parameter blocks;

23 generating a campaign plan based on merchant specified campaign parameters

24 from the stackable campaign parameter blocks; and

25 providing the campaign plan to a campaign channel.

26

27 62. The method of claim 61, wherein the sales performance analytics includes

28 sales revenue over a period of time.

29

30

31 63. The method of claim 61, wherein the sales performance analytics includes

32 number of new customers over a period of time.

64. The method of claim 61, wherein the sales performance analytics includes sales revenue per product category. 65. The method of claim 61, wherein the graphic representation includes aggregated performance curves. 66. The method of claim 61, wherein the generated heuristics includes a flagged sales section with a highest percentage. 67. The method of claim 61, wherein the campaign parameters comprise campaign duration. 68. The method of claim 61, wherein the campaign parameters comprise campaign offer type. 69. The method of claim 61, wherein the campaign parameters comprise campaign discount rate and units requirement. 70. The method of claim 61, wherein the campaign parameters are automatically generated based on heuristics as campaign recommendation. 71. A processor-implemented merchant control platform system, comprising: a memory;

receive a merchant request for sales performance analytics;

provide a merchant control panel to a merchant, wherein the merchant control panel facilitates a merchant to view sales performance;

obtain merchant specified sales performance representation parameters;

generate a graphical representation of merchant sales performance; obtain merchant interested analytics indicia via a user interface;

generate performance-improving heuristics reflecting the merchant interested analytics indicia for a merchant campaign;

generate stackable campaign parameter blocks pre-populated with recommended merchant campaign parameters based on the performance-improving heuristics;

obtain merchant specified campaign parameters from the stackable campaign parameter blocks;

generate a campaign plan based on merchant specified campaign parameters from the stackable campaign parameter blocks; and

provide the campaign plan to a campaign channel. 72. The system of claim 71, wherein the sales performance analytics includes sales revenue over a period of time. 73. The system of claim 71, wherein the sales performance analytics includes number of new customers over a period of time. 74. The system of claim 71, wherein the sales performance analytics includes sales revenue per product category. 75. The system of claim 71, wherein the graphic representation includes aggregated performance curves. 76. The system of claim 71, wherein the generated heuristics includes a flagged sales section with a highest percentage. 77. The system of claim 71, wherein the campaign parameters comprise campaign duration. 78. The system of claim 71, wherein the campaign parameters comprise campaign offer type.

79. The system of claim 71, wherein the campaign parameters comprise campaign discount rate and units requirement. 80. The system of claim 71, wherein the campaign parameters are automatically generated based on heuristics as campaign recommendation. 81. A merchant enrollment processor-readable non-transitory medium storing instructions executable by a processor to:

receive a merchant request for sales performance analytics;

obtain merchant specified sales performance representation parameters;

generate a graphical representation of merchant sales performance;

obtain merchant interested analytics indicia via a user interface;

provide the campaign plan to a campaign channel. 82. The medium of claim 81, wherein the sales performance analytics includes sales revenue over a period of time. 83. The medium of claim 81, wherein the sales performance analytics includes number of new customers over a period of time. 84. The medium of claim 81, wherein the sales performance analytics includes sales revenue per product category.

85. The medium of claim 81, wherein the graphic representation includes aggregated performance curves. 86. The medium of claim 81, wherein the generated heuristics includes a flagged sales section with a highest percentage. 87. The medium of claim 81, wherein the campaign parameters comprise campaign duration. 88. The medium of claim 81, wherein the campaign parameters comprise campaign offer type. 89. The medium of claim 81, wherein the campaign parameters comprise campaign discount rate and units requirement. 90. The medium of claim 81, wherein the campaign parameters are automatically generated based on heuristics as campaign recommendation. 91. The method of claim 1, further comprising: determining whether a merchant has a consumer account, and pre-loading profile information from the consumer account for merchant onboarding. 92. The method of claim 1, further comprising: using merchant information from the generated merchant enrollment record to instantiate merchant facilities.