AU2011261259B2 - Payment tokenization apparatuses, methods and systems - Google Patents
Payment tokenization apparatuses, methods and systems Download PDFInfo
- Publication number
- AU2011261259B2 AU2011261259B2 AU2011261259A AU2011261259A AU2011261259B2 AU 2011261259 B2 AU2011261259 B2 AU 2011261259B2 AU 2011261259 A AU2011261259 A AU 2011261259A AU 2011261259 A AU2011261259 A AU 2011261259A AU 2011261259 B2 AU2011261259 B2 AU 2011261259B2
- Authority
- AU
- Australia
- Prior art keywords
- user
- token
- payment
- request
- purchase
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 84
- 238000012545 processing Methods 0.000 claims abstract description 81
- 238000013475 authorization Methods 0.000 claims abstract description 69
- 230000004044 response Effects 0.000 claims abstract description 57
- 238000004891 communication Methods 0.000 claims description 57
- 230000008569 process Effects 0.000 claims description 29
- 238000012546 transfer Methods 0.000 abstract description 28
- 238000010586 diagram Methods 0.000 description 16
- 230000002093 peripheral effect Effects 0.000 description 14
- 238000013515 script Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 11
- 230000007246 mechanism Effects 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 8
- 238000011161 development Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 6
- 230000003213 activating effect Effects 0.000 description 5
- 238000004422 calculation algorithm Methods 0.000 description 5
- 230000001413 cellular effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 239000008186 active pharmaceutical agent Substances 0.000 description 4
- 239000002131 composite material Substances 0.000 description 4
- 241000699666 Mus <mouse, genus> Species 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 3
- 239000000203 mixture Substances 0.000 description 3
- 230000002265 prevention Effects 0.000 description 3
- WHXSMMKQMYFTQS-UHFFFAOYSA-N Lithium Chemical compound [Li] WHXSMMKQMYFTQS-UHFFFAOYSA-N 0.000 description 2
- 241001275944 Misgurnus anguillicaudatus Species 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000013078 crystal Substances 0.000 description 2
- 238000013478 data encryption standard Methods 0.000 description 2
- 230000000881 depressing effect Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 229910052744 lithium Inorganic materials 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 239000003550 marker Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000037361 pathway Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- FMFKNGWZEQOWNK-UHFFFAOYSA-N 1-butoxypropan-2-yl 2-(2,4,5-trichlorophenoxy)propanoate Chemical compound CCCCOCC(C)OC(=O)C(C)OC1=CC(Cl)=C(Cl)C=C1Cl FMFKNGWZEQOWNK-UHFFFAOYSA-N 0.000 description 1
- 241000010972 Ballerus ballerus Species 0.000 description 1
- 102100026816 DNA-dependent metalloprotease SPRTN Human genes 0.000 description 1
- 101710175461 DNA-dependent metalloprotease SPRTN Proteins 0.000 description 1
- 241000272183 Geococcyx californianus Species 0.000 description 1
- HBBGRARXTFLTSG-UHFFFAOYSA-N Lithium ion Chemical compound [Li+] HBBGRARXTFLTSG-UHFFFAOYSA-N 0.000 description 1
- 241000699670 Mus sp. Species 0.000 description 1
- 241001025261 Neoraja caerulea Species 0.000 description 1
- 101100162169 Xenopus laevis adrm1-a gene Proteins 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- OJIJEKBXJYRIBZ-UHFFFAOYSA-N cadmium nickel Chemical compound [Ni].[Cd] OJIJEKBXJYRIBZ-UHFFFAOYSA-N 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- JHIVVAPYMSGYDF-UHFFFAOYSA-N cyclohexanone Chemical compound O=C1CCCCC1 JHIVVAPYMSGYDF-UHFFFAOYSA-N 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 150000004678 hydrides Chemical class 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 239000007788 liquid Substances 0.000 description 1
- 229910001416 lithium ion Inorganic materials 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- SUTJFACQYOCLNG-UHFFFAOYSA-N methyl 6-[[2-[9a-[2-[(2-methoxycarbonyl-3,3-dimethyl-7-oxo-4-thia-1-azabicyclo[3.2.0]heptan-6-yl)amino]-2-oxoethyl]-7-oxo-5a,6-dihydrodibenzofuran-3-yl]acetyl]amino]-3,3-dimethyl-7-oxo-4-thia-1-azabicyclo[3.2.0]heptane-2-carboxylate Chemical compound C1=C2OC3CC(=O)C=CC3(CC(=O)NC3C(N4C(C(C)(C)SC43)C(=O)OC)=O)C2=CC=C1CC(=O)NC(C1=O)C2N1C(C(=O)OC)C(C)(C)S2 SUTJFACQYOCLNG-UHFFFAOYSA-N 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 229920000642 polymer Polymers 0.000 description 1
- 230000000246 remedial effect Effects 0.000 description 1
- 210000001525 retina Anatomy 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The PAYMENT TOKENIZATION APPARATUSES, METHODS AND SYSTEMS ("PT") transform payment token-based purchase orders via PT components into multi-issuer purchase payment funds transfers. In one embodiment, the PT obtains a token arbitration request including unique source-neutral universally-resolvable payment token information from a merchant for processing a purchase order. The PT queries a token database for issuer information using the payment token information, and obtains the issuer information. The PT also determines the user should be queried for payment options based on the issuer information, generates a payment options request, and provides the payment options request to a user?s mobile device. Upon obtaining a response to the payment options request from the mobile device, the PT generates a purchase authorization request based on the payment options and pre-defined settings for issuers to be contacted for processing the purchase order, and provides the generated purchase authorization request to the issuer.
Description
WO 20111153505 PCT/US2011/039178 1 PAYMENT TOKENIZATION APPARATUSES, METHODS AND 2 SYSTEMS 3 [o001] This patent application disclosure document (hereinafter "description" 4 and/or "descriptions") describes inventive aspects directed at various novel innovations 5 (hereinafter "innovation," "innovations," and/or "innovation(s)") and contains material 6 that is subject to copyright, mask work, and/or other intellectual property protection. 7 The respective owners of such intellectual property have no objection to the facsimile 8 reproduction of the patent disclosure document by anyone as it appears in published 9 Patent Office file/records, but otherwise reserve all rights. 10 RELATED APPLICATIONS 11 [000 21 Applicant hereby claims priority under 35 USC §119 for: United States 12 provisional patent application serial no. 61/351,475 filed June 4, 2010, entitled 13 "SYSTEM AND METHOD USING MERCHANT PAYMENT OPTIONS," attorney docket 14 no. P-41572PRV|20270-152PV; and United States provisional patent application serial 1s no. 61/447,644 filed February 28, 2011, entitled "SECURE ANONYMOUS 16 TRANSACTION APPARATUSES, METHODS AND SYSTEMS," attorney docket no. P 17 42055PRV|20270-137PV. The entire contents of the aforementioned applications are 18 expressly incorporated herein by reference.
WO 2011/153505 PCT/US2011/039178 2 1 FIELD 2 [00031 The present inventions are directed generally to apparatuses, methods, 3 and systems for purchase transactions, and more particularly, to PAYMENT 4 TOKENIZATION APPARATUSES, METHODS AND SYSTEMS ("PT"). 5 BACKGROUND 6 [0004] Card-based consumer transactions typically require a customer to enter 7 numerous details of a credit or debit card, or utilize a payment method such as cash or 8 check. Engaging in card transactions requires transmission of personal information to a 9 wide range of third-party merchants. 10 BRIEF DESCRIPTION OF THE DRAWINGS 11 [ooo5] The accompanying appendices and/or drawings illustrate various non 12 limiting, example, inventive aspects in accordance with the present disclosure: 13 [oo06] FIGURE 1 shows a block diagram illustrating example aspects of payment 14 tokenization in some embodiments of the PT; 15 [00071 FIGURES 2A-B shows application user interface diagrams illustrating 16 example features of application interfaces for controlling tokenized payments for 17 purchase transactions in some embodiments of the PT; 18 [0008] FIGURES 3A-C show application user interface diagrams illustrating 19 example features of a payment tokenization mobile app for securing user data and 20 preventing fraud in some embodiments of the PT; WO 2011/153505 PCT/US2011/039178 3 1 [o oo9] FIGURE 4 shows a data flow diagram illustrating an example procedure to 2 enroll in a token-based purchase payment program in some embodiments of the PT; 3 [0010] FIGURE 5 shows a logic flow diagram illustrating example aspects of 4 enrolling in a token-based purchase payment program in some embodiments of the PT, 5 e.g., a Token-Based Purchase Enrollment ("TPE") component 500; 6 [0011] FIGURES 6A-E show data flow diagrams illustrating an example 7 procedure to execute a token-based purchase transaction in some embodiments of the 8 PT; 9 [00121 FIGURES 7A-F show logic flow diagrams illustrating example aspects of 1o executing a token-based purchase transaction in some embodiments of the PT, e.g., a 11 Token-Based Purchase Transaction Execution ("tPTE") component 700; and 12 [00131 FIGURE 8 shows a block diagram illustrating embodiments of a PT 13 controller. 14 [00141 The leading number of each reference number within the drawings 15 indicates the figure in which that reference number is introduced and/or detailed. As 16 such, a detailed discussion of reference number 101 would be found and/or introduced 17 in Figure 1. Reference number 201 is introduced in Figure 2, etc. 18 WO 2011/153505 PCT/US2011/039178 4 1 DETAILED DESCRIPTION 2 PAYMENT TOKENIZATION (PT) 3 [0015] The PAYMENT TOKENIZATION APPARATUSES, METHODS AND 4 SYSTEMS (hereinafter "PT") transform payment token-based purchase orders, via PT 5 components, into multi-issuer purchase payment funds transfers. 6 [o016] FIGURE 1 shows a block diagram illustrating example aspects of payment 7 tokenization in some embodiments of the PT. In some implementations, a user may 8 desire to purchase a product, service and/or other offering ("product") from a merchant, 9 e.g., 106. The user may desire to utilize a card (e.g., debit, credit, prepaid, etc.), e.g., 10 loa, cash (or its equivalent), e.g., io2a, securities, e.g., io3a, virtual currency, rewards, 11 points, miles, etc., e.g., io4a, and/or other payment options. However, the user may 12 wish to maintain anonymity to prevent personal information of the user from being 13 collected by the merchant. As another example, the user may be wary of the user's card 14 data being misused to conduct fraudulent transactions. In some implementations, the 1s user may be able to utilize aliases, or tokens in lieu of payment information. For 16 example, the user may be able to pass a token, e.g., 1ob, 102b, 103b, 104b, to a 17 merchant instead of complete card information, cash or account information. A secure 18 token arbitrator may operate in conjunction with the merchant to process the 19 transaction. For example, upon receiving a payment token from the user, the merchant 20 may pass the token to a transaction arbitrator. The secure transaction arbitrator may 21 have the ability to parse the incoming token, and determine the identity of the user for 22 that token. The transaction arbitrator may also determine financial payment WO 2011/153505 PCT/US2011/039178 5 1 information to use to process the transaction. In some implementations, the transaction 2 arbitrator may also only have another token stored as payment information. In such 3 implementations, the issuer of the token may be the only entity other than the user to 4 know the actual personal and/or financial information of the user. Thus, in some 5 implementations, a token may comprise a combination of other token. For example, a 6 token held by the transaction arbitrator may point to other token held by the transaction 7 arbitrator and/or the issuer. Thus, in some implementations, multiple layers of security 8 of personal and financial information may be generated by structuring the payment 9 tokens accordingly. In some implementations, a token may specify a composition, 1o including a mix of other payment tokens. For example, a payment token 105 may 11 indicate that the transaction may be processed by assigning a percentage (e.g., 55%) of 12 the transaction cost to a token ioib (e.g., linked to credit card information iola 13 ultimately), and a different percentage (e.g., 45%) to a different token 102b (e.g., linked 14 to a stored cash account 102a ultimately). In some implementations, the percentages 15 may be determined in real-time or near real-time. For example, the token arbitrators 16 may operate in conjunction with the issuers having user accounts linked to the payment 17 token to determine which of the user accounts should be charged, and how much should 18 be charged to each user account (e.g., in accordance with a predetermined algorithm). 19 As another example, the percentages may be determined only at the time of processing 20 the transaction, see, e.g., 103b, 104b, for example by requesting the user to provide 21 payment options at the time of processing the purchase transaction. 22 [0017] In some implementations, additional security may be layered by using 23 authentication methods. As an example, a user may be required to provide a user name 24 and password to activate a payment token. As another example, a user may be required WO 2011/153505 PCT/US2011/039178 6 1 to provide a digital certificate to verify the user's identity prior to utilization of a 2 payment token for a purchase transaction. As another example, device fingerprinting 3 may be utilized. For example, a client device of a user may be a device that is used 4 exclusively by the user, such as a smartphone, tablet computer, laptop computer, and/or 5 the like. In some implementations, a custom hardware authentication chip, e.g., 103, 6 may be disposed in communication with the client. In various implementations, the 7 chip may be embedded into the client, come pre-installed in the client, attached as a 8 periphery to the client, and/or the like. In some implementations, the user may perform 9 an authentication procedure with the client and a user's card linked to the user's 10 payment token. For example, the authentication chip may be configured to recognize 11 the user's payment token physical card when the card is in the vicinity of the 12 authentication chip. For example, the authentication chip and the card may 13 communicate signals via BluetoothTM, Wi-FiTM, RFID tags, cellular connectivity (e.g., 3G, 14 4G), and/or the like. Thus, in order to make purchase with the payment token, in some 15 implementations, the user may be required to present the payment token physical card 16 to the authentication chip disposed in communication with the client before the user can 17 make a purchase order using the token. Thus, the system provides an authenticity 18 shield preventing others who may know of the user's payment token from utilizing the 19 user's payment token in a fraudulent transaction. 20 [0 18] FIGURES 2A-B shows application user interface diagrams illustrating 21 example features of application interfaces for controlling tokenized payments for 22 purchase transactions in some embodiments of the PT. In some implementations, an 23 app executing on the device of the user may include an app interface providing various 24 features for the user. In some implementations, the app may include an indication of WO 2011/153505 PCT/US2011/039178 7 1 the location (e.g., name of the merchant store, geographical location, information about 2 the aisle within the merchant store, etc.) of the user, e.g., 201. The app may provide an 3 indication of a pay amount due for the purchase of the product, e.g., 202. In some 4 implementations, the app may provide various options for the user to pay the amount 5 for purchasing the product(s). For example, the app may utilize the GPS coordinates to 6 determine the merchant store within the user is present, and direct the user to a website 7 of the merchant. In some implementations, the PT may provide an API for participating 8 merchants directly to facilitate transaction processing. In some implementations, a 9 merchant-branded PT application may be developed with the PT functionality, which 10 may directly connect the user into the merchant's transaction processing system. For 11 example, the user may choose from a number of cards (e.g., credit cards, debit cards, 12 prepaid cards, etc.) from various card providers, e.g., 203. In some implementations, 13 the app may provide the user the option to pay the purchase amount using funds 14 included in a bank account of the user, e.g., a checking, savings, money market, current 1s account, etc., e.g., 204. In some implementations, the user may have set default options 16 for which card, bank account, etc. to use for the purchase transactions via the app. In 17 some implementations, such setting of default options may allow the user to initiate the 18 purchase transaction via a single click, tap, swipe, and/or other remedial user input 19 action, e.g., 205. In some implementations, when the user utilizes such an option, the 20 app may utilize the default settings of the user to initiate the purchase transaction. In 21 some implementations, the app may allow the user to utilize other accounts (e.g., 22 GoogleTM Checkout, PaypalT' account, etc.) to pay for the purchase transaction, e.g., 23 206. In some implementations, the app may allow the user to utilize rewards points, 24 airline miles, hotel points, electronic coupons, printed coupons (e.g., by capturing the WO 2011/153505 PCT/US2011/039178 8 1 printed coupons similar to the product identifier) etc., to pay for the purchase 2 transaction, e.g., 207-208. In some implementations, the app may provide an option to 3 provide express authorization before initiating the purchase transaction, e.g., 209. In 4 some implementations, the app may provide a progress indicator provide indication on 5 the progress of the transaction after the user has selected an option to initiate the 6 purchase transaction, e.g., 210. In some implementations, the app may provide the user 7 with historical information on the user's prior purchases via the app, e.g., 211. In some 8 implementations, the app may provide the user with an option to share information 9 about the purchase (e.g., via email, SMS, wall posting on Facebook@, tweet on 10 TwitterTM, etc.) with other users, e.g., 212. In some implementations the app may 11 provide the user an option to display the product identification information captured by 12 the client device (e.g., in order to show a customer service representative at the exit of a 13 store the product information), e.g., 214. In some implementations, the user, app, 14 device and or PT may encounter an error in the processing. In such scenarios, the user 15 may be able to chat with a customer service representative (e.g., VerifyChat 213) to 16 resolve the difficulties in the purchase transaction procedure. 17 [o 019] In some implementations, the user may select to conduct the transaction 18 using a one-time token, e.g., an anonymized credit card number, see e.g., 205b. For 19 example, the PT may utilize a tokenized and anonymized set of card details (see, e.g., 20 "AnonCard1," "AnonCard2"). As another example, the PT may generate, e.g., in real 21 time, a one-time anonymous set of card details to securely complete the purchase 22 transaction (e.g., "Anon It 1X"). In such implementations, the app may automatically 23 set the user profile settings such that the any personal identifying information of the 24 user will not be provided to the merchant and/or other entities. For example, the app WO 2011/153505 PCT/US2011/039178 9 1 may automatically send only a token or alias in lieu of payment information. The 2 payment system may process the token to obtain its associated payment information for 3 processing the purchase transaction. In some implementations, the user may be 4 required to enter a user name and password to enable the anonymization features. 5 [o020] In some implementations, a user may be able to control the attributes of 6 each token associated with the user via a web interface, e.g., 220. For example, the user 7 may be able to login to the web interface, e.g., 221, and visualize payment tokens 8 associated with the user, e.g., 223. The user may also be provided with user interface 9 elements to generate new tokens. For example, the user interface may provide elements 10 for creating a new token, e.g., 224. For example, the user interface may allow the user to 11 select financial details 225 such as, but not limited to: a funding source from whom to 12 obtain a token, an account type for the token, an initial token value (e.g., for pre 13 funding, and/or pore-authorization), a value decay option (e.g., to assist with time 14 controlled spending controls for the user), billing address information, shipping address 15 information, contact settings, a security protocol, token administrator, user 16 anonymization (for security) option and/or the like. In some implementations, the web 17 interface may allow the user to select personal details 226 such as, but not limited to: 18 token holders, contact frequency (e.g., for token offers), token offer preferences, 19 parental controls, activated devices, and/or the like. In some implementations, the web 20 interface may allow the user to specify activation 227 and expiry 228 dates for the 21 tokens. 22 [0 0 21] FIGURES 3A-C show application user interface diagrams illustrating 23 example features of a payment tokenization mobile app for securing user data and WO 2011/153505 PCT/US2011/039178 10 1 preventing fraud in some embodiments of the PT. In some implementations, the app 2 executing on the user's device may provide a "VerifyChat" feature for fraud prevention 3 (e.g., by activating UI element 213 in FIGURE 2). For example, the PT may detect an 4 unusual and/or suspicious transaction. The PT may utilize the VerifyChat feature to 5 communicate with the user, and verify the authenticity of the originator of the purchase 6 transaction. In various implementations, the PT may send electronic mail message, text 7 (SMS) messages, Facebook® messages, TwitterTM tweets, text chat, voice chat, video 8 chat (e.g., Apple FaceTime), and/or the like to communicate with the user. For 9 example, the PT may initiate a video challenge for the user, e.g., 301. For example, the 1o user may need to present him/her-self via a video chat, e.g., 302. In some 11 implementations, a customer service representative, e.g., agent 304b, may manually 12 determine the authenticity of the user using the video of the user. In some 13 implementations, the PT may utilize face, biometric and/or like recognition (e.g., using 14 pattern classification techniques) to determine the identity of the user, e.g., 304a. In 15 some implementations, the app may provide reference marker (e.g., cross-hairs, target 16 box, etc.), e.g., 303, so that the user may the video to facilitate the PT' automated 17 recognition of the user. In some implementations, the user may not have initiated the 18 transaction, e.g., the transaction is fraudulent. In such implementations, the user may 19 cancel, e.g., 305, the challenge. The PT may then cancel the transaction, and/or initiate 20 fraud investigation procedures on behalf of the user. 21 [o 0221 In some implementations, the PT may utilize a text challenge procedure to 22 verify the authenticity of the user, e.g., 306. For example, the PT may communicate 23 with the user via text chat, SMS messages, electronic mail, Facebook@ messages, 24 TwitterTM tweets, and/or the like. The PT may pose a challenge question, e.g., 308, for WO 2011/153505 PCT/US2011/039178 1 the user. The app may provide a user input interface element(s) (e.g., virtual keyboard 2 309) to answer the challenge question posed by the PT. In some implementations, the 3 challenge question may randomly selected by the PT automatically; in some 4 implementations, a customer service representative may manually communicate with 5 the user. In some implementations, the user may not have initiated the transaction, 6 e.g., the transaction is fraudulent. In such implementations, the user may cancel, e.g., 7 307, 310, the text challenge. The PT may then cancel the transaction, and/or initiate 8 fraud investigation procedures on behalf of the user. 9 [o 0231 In some implementations, the app may be configured to recognize product 10 identifiers (e.g., barcodes, QR codes, etc.). For example, for fraud prevention, the app 11 may require the user to utilize the user's device to obtain snapshot of the items being 12 purchased, thus ensuring that the person who swiped the card is also in possession of 13 the user's device as well as the purchase items. In some implementations, the user may 14 be required to sign in to the app to enable its features. Once enabled, the camera may 15 provide in-person one tap purchasing features for the user. For example, the client 16 device may have a camera via which the app may acquire images, video data, streaming 17 live video, and/or the like, e.g., 313. The app may be configured to analyze the incoming 18 data, and search, e.g., 311, for a product identifier, e.g., 314. In some implementations, 19 the app may overlay cross-hairs, target box, and/or like alignment reference markers, 20 e.g., 315, so that a user may align the product identifier using the reference markers so 21 facilitate product identifier recognition and interpretation. In some implementations, 22 the app may include interface elements to allow the user to switch back and forth 23 between the product identification mode and the product offer interface display screens 24 (see, e.g., 316), so that a user may accurately study the deals available to the user before WO 2011/153505 PCT/US2011/039178 12 1 capturing a product identifier. In some implementations, the app may provide the user 2 with the ability to view prior product identifier captures (see, e.g., 317) so that the user 3 may be able to better decide which product identifier the user desires to capture. In 4 some implementations, the user may desire to cancel product purchasing; the app may 5 provide the user with a user interface element (e.g., 318) to cancel the product identifier 6 recognition procedure and return to the prior interface screen the user was utilizing. In 7 some implementations, the user may be provided with information about products, user 8 settings, merchants, offers, etc. in list form (see, e.g., 319) so that the user may better 9 understand the user's purchasing options. Various other features may be provided for 10 in the app (see, e.g., 320). 11 [o 0 24] In some implementations, the user may be able to view and/or modify the 12 user profile and/or settings of the user, e.g., by activating user interface element 309 13 (see FIGURE 3A). For example, the user may be able to view/modify a user name (e.g., 14 321a-b), account number (e.g., 322a-b), user security access code (e.g., 323a-b), user pin 15 (e.g., 324a-b), user address (e.g., 325a-b), social security number associated with the 16 user (e.g., 326a-b), current device GPS location (e.g., 327a-b), user account of the 17 merchant in whose store the user currently is (e.g., 328a-b), the user's rewards accounts 18 (e.g., 329a-b), and/or the like. In some implementations, the user may be able to select 19 which of the data fields and their associated values should be transmitted to facilitate 20 the purchase transaction, thus providing enhanced data security for the user. For 21 example, in the example illustration in FIGURE 3C, the user has selected the name 312a, 22 account number 322a, security code 323a, merchant account ID 328a and rewards 23 account ID 329a as the fields to be sent as part of the notification to process the 24 purchase transaction. In some implementations, the user may toggle the fields and/or WO 2011/153505 PCT/US2011/039178 13 1 data values that are sent as part of the notification to process the purchase transactions. 2 In some implementations, the app may provide multiple screens of data fields and/or 3 associated values stored for the user to select as part of the purchase order transmission. 4 In some implementations, the app may provide the PT with the GPS location of the user. 5 Based on the GPS location of the user, the PT may determine the context of the user 6 (e.g., whether the user is in a store, doctor's office, hospital, postal service office, etc.). 7 Based on the context, the user app may present the appropriate fields to the user, from 8 which the user may select fields and/or field values to send as part of the purchase order 9 transmission. 10 [00 251 For example, a user may go to doctor's office and desire to pay the co-pay 11 for doctor's appointment. In addition to basic transactional information such as 12 account number and name, the app may provide the user the ability to select to transfer 13 medical records, health information, which may be provided to the medical provider, 14 insurance company, as well as the transaction processor to reconcile payments between 15 the parties. In some implementations, the records may be sent in a Health Insurance 16 Portability and Accountability Act (HIPAA)-compliant data format and encrypted, and 17 only the recipients who are authorized to view such records may have appropriate 18 decryption keys to decrypt and view the private user information. 19 [0026] FIGURE 4 shows a data flow diagram illustrating an example procedure to 20 enroll in a token-based purchase payment program in some embodiments of the PT. In 21 some implementations, a user, e.g., 401, may desire to purchase a product, service, 22 offering, and/or the like ("product"), from a merchant. The user may communicate with 23 a merchant server, e.g., 403a, via a client such as, but not limited to: a personal WO 2011/153505 PCT/US2011/039178 14 1 computer, mobile device, television, point-of-sale terminal, kiosk, ATM, and/or the like 2 (e.g., 402). For example, the user may provide user input, e.g., purchase input 411, into 3 the client indicating the user's desire to purchase the product. In various 4 implementations, the user input may include, but not be limited to: keyboard entry, card 5 swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having 6 multiple accounts, smartphone, tablet, etc.), mouse clicks, depressing buttons on a 7 joystick/game console, voice commands, single/multi-touch gestures on a touch 8 sensitive interface, touching user interface elements on a touch-sensitive display, and/or 9 the like. For example, the user may direct a browser application executing on the client 10 device to a website of the merchant, and may select a product from the website via 11 clicking on a hyperlink presented to the user via the website. As another example, the 12 client may obtain track i data from the user's card (e.g., credit card, debit card, prepaid 13 card, charge card, etc.), such as the example track 1 data provided below: 14 %Bl23456789012345^PUBLIC/J.Q.^99011200000000000000**90l******?* 15 (wherein '123456789012345' is the card number of 'J.Q. Public' and has a CVV 16 number of 901. '990112' is a service code, and *** represents decimal digits 17 which change randomly each time the card is used.) 18 19 20 [0027] In some implementations, the client may generate a purchase order 21 message, e.g., 412, and provide, e.g., 413, the generated purchase order message to the 22 merchant server. For example, a browser application executing on the client may 23 provide, on behalf of the user, a (Secure) Hypertext Transfer Protocol ("HTTP(S)") GET 24 message including the product order details for the merchant server in the form of data 25 formatted according to the eXtensible Markup Language ("XML"). Below is an example 26 HTTP(S) GET message including an XML-formatted purchase order message for the 27 merchant server: WO 2011/153505 PCT/US2011/039178 15 1 GET /purchase.php HTTP/1.1 2 Host: www.merchant.com 3 Content-Type: Application/XML 4 Content-Length: 1306 5 <?XML version = "1.0" encoding = "UTF-8"?> 6 <purchaseorder> 7 <order_ID>4NFU4RG94</order_ID> 8 <timestamp>2011-02-22 15:22:43</timestamp> 9 <user ID>john.q.public@gmail.com</user_ID> 10 <clientdetails> 11 <clientIP>192.168.23.126</clientIP> 12 <client type>smartphone</client type> 13 <clientmodel>HTC Hero</clientmodel> 14 <OS>Android 2.2</OS> 15 <appinstalled_flag>true</app installed flag> 16 </clientdetails> 17 <purchasedetails> 18 <num products>l</numproducts> 19 <product> 20 <product type>book</producttype> 21 <product params> 22 <product title>XML for dummies</product title> 23 <ISBN>938-2-14-168710-0</ISBN> 24 <edition>2nd ed.</edition> 25 <cover>hardbound</cover> 26 <seller>bestbuybooks</seller> 27 </product params> 28 <quantity>l</quantity> 29 </product> 30 </purchasedetails> 31 <account params> 32 <account-name>John Q. Public</account name> 33 <accounttype>credit</account type> 34 <accountnum>123456789012345</accountnum> 35 <billing address>123 Green St., Norman, OK 98765</billing address> 36 <phone>123-456-7809</phone> 37 <sign>/jqp/</sign> 38 <confirmtype>email</confirm type> 39 <contact info>john.q.public@gmail.com</contact info> 40 </account params> 41 <shipping info> 42 <shipping adress>same as billing</shipping address> 43 <ship type>expedited</shiptype> 44 <ship carrier>FedEx</ship carrier> 45 <ship account>123-45-678</ship account> 46 <tracking flag>true</tracking flag> 47 <sign flag>false</signflag> 48 </shippinginfo> 49 </purchaseorder> 50 51 52 [o0 028] In some implementations, the merchant server may obtain the purchase 53 order message from the client, and may parse the purchase order message to extract 54 details of the purchase order from the user. Based on the parsing, the merchant server 55 may determine that the purchase order message is not tokenized, e.g., 414. Upon 56 determining that the purchase order message is not tokenized, the merchant server may WO 2011/153505 PCT/US2011/039178 16 1 determine that the user needs to be provided with an option to sign up for payment 2 tokenization services. The merchant server may attempt to identify a token arbitrator to 3 provide the payment tokenization services for the user. For example, the merchant 4 server may query, e.g., 415, a merchant database, e.g., 404, for an address of a token 5 arbitrator. For example, the merchant server may utilize a hypertext preprocessor 6 ("PHP") script including Structured Query Language ("SQL") commands to query a 7 relational database for an address of a token arbitator. An example PHP/SQL listing for 8 querying a database for a token arbitrator address is provided below: 9 <?PHP 10 header('Content-Type: text/plain'); 11 mysql connect("254.93.179.112",$DBserver,$password) ; // access database server 12 mysql select_db("ARBITRATORS.SQL"); // select database table to search 13 //create query for token arbitrators 14 $query = "SELECT arbitratorid, arbitators_name arbitratoraddress 15 arbitrator_URL FROM TokenizationTable WHERE usercard_num LIKE '%' 16 $userpaymentcardnumber"; 17 $result = mysqlquery($query); // perform the search query 18 mysql close("ARBITRATORS.SQL"); // close database access 19 ?> 20 21 22 [0029] In response, the merchant database may provide the token arbitrator 23 address, e.g., 416. The merchant server may generate a tokenization invitation request 24 on behalf of the user, e.g., 417, and provide the tokenization invitation request to a token 25 server, e.g., 405. For example, the merchant server may provide a HTTP(S) POST 26 message including the tokenization invitation request similar to the example below: 27 POST /inviterequest.php HTTP/1.1 28 Host: www.tokenizer.com 29 Content-Type: Application/XML 30 Content-Length: 579 31 <?XML version = "1.0" encoding = "UTF-8"?> 32 <invitation request> 33 <timestamp>2011-02-22 15:22:43</timestamp> 34 <userID>john.q.public@gmail.com</user_ID> 35 <clientdetails> 36 <clientIP>192.168.23.126</client_IP> 37 <client type>smartphone</client type> 38 <clientmodel>HTC Hero</clientmodel> 39 <OS>Android 2.2</OS> 40 <app installed flag>true</app installed flag> WO 2011/153505 PCT/US2011/039178 17 1 </clientdetails> 2 <merchant params> 3 <merchant id>3FBCR4INC</merchant id> 4 <merchant-name>Books & Things, Inc.</merchant_name> 5 <merchant_auth_key>lNNF484MCP59CHB27365</merchant_auth key> 6 </merchant params> 7 </invitation request> 8 9 10 [0030] In some implementations, the token server may parse the invitation 11 request message, and extract details of the user and client from the message. The token 12 server may generate, e.g., 419, a tokenization invitation and an application form for the 13 user to complete to sign up for tokenization services. The token server may provide, 14 e.g., 420, the tokenization invitation and the application form to the client (either 15 directly to the client or via the merchant server). For example, the token server may 16 provide a HTTP(S) POST message including XML data representative of the application 17 form, such as the example HTTP(S) POST message below: 18 POST /purchase.php HTTP/l.1 19 Host: www.merchant.com 20 Content-Type: Application/XML 21 Content-Length: 1306 22 <?XML version = "1.0" encoding = "UTF-8"?> 23 <tokenapplicationform> 24 <provisional-tokenID>4NFU4RG94</provisional-tokenID> 25 <timestamp>2011-02-22 15:22:43</timestamp> 26 <userID>john.q.public@gmail.com</user_ID> 27 <clientdetails> 28 <clientIP>192.168.23.126</clientIP> 29 <client type>smartphone</client type> 30 <clientmodel>HTC Hero</clientmodel> 31 <OS>Android 2.2</OS> 32 <app installed_flag>true</app installed flag> 33 </clientdetails> 34 <account params> 35 <accountname> COMPLETE </accountname> 36 <account type> COMPLETE </accounttype> 37 <accountnum>1234 COMPLETE 56789012345</accountnum> 38 <billing address> COMPLETE </billing address> 39 <phone> COMPLETE </phone> 40 <sign> COMPLETE </sign> 41 <confirm type> COMPLETE </confirm_type> 42 <contact info> COMPLETE </contactinfo> 43 </account params> 44 <shipping info> 45 <shipping adress> COMPLETE </shippingaddress> 46 <ship type> COMPLETE </ship type> 47 <ship carrier> COMPLETE </shipcarrier> 48 <shipaccount> COMPLETE </shipaccount> 49 <tracking flag> COMPLETE </tracking flag> WO 2011/153505 PCT/US2011/039178 18 1 <signflag> COMPLETE </signflag> 2 </shipping info> 3 </token application form> 4 5 6 [0031] The client may render, e.g., 421, the tokenization invitation and 7 application form, and display, e.g., 422, the invitation and application form for the user, 8 e.g., 423. In some implementations, the user may desire to enroll for payment 9 tokenization services, and may provide token creation input to complete the application 10 form, e.g., 423. The client may generate a competed application form, and provide, e.g., 11 424, the token application to the token server (either directly or via the merchant 12 server). For example, the client may provide a HTTP(S) POST message similar to the 13 example above. The token server may obtain the application form, and parse the form 14 to extract data fields and values from the form to generate a token data record, e.g., 425. 15 The token server may store the data extracted from the application form to a token 16 database, e.g., 406. For example, the token server may issue PHP/SQL commands 17 similar to the example below: 18 <?PHP 19 header('Content-Type: text/plain'); 20 mysql connect ("254.92.185.103",$DBserver,$password); // access database server 21 mysql select("TOKENS.SQL"); // select database to append 22 mysql-query("INSERT INTO PaymentTokensTable (timestamp, tokenid, userid, 23 username, clientid, client type, clientmodel, clientOS, 24 app installed-flag, account params list, account name, account type, 25 accountnum, billing addres, zipcode, phone, sign, merchant paramslist, 26 merchantid, merchantname, merchantauthkey) 27 VALUES (time(), $userid, $username, $clientid, $clienttype, $clientmodel, 28 $clientOS, $appflag, $purchase_summary list, $num products, 29 $productsummary, $product quantity, $transaction cost, 30 $account paramslist, $accountname, $account type, $accountnum, 31 $billing addres, $zipcode, $phone, $sign, $merchant params list, 32 $merchant id, $merchant-name, $merchantauthkey)"); // add data to table in 33 database 34 mysqlclose("TOKENS.SQL"); // close connection to database 35 ?> 36 37 38 [0032] FIGURE 5 shows a logic flow diagram illustrating example aspects of 39 enrolling in a token-based purchase payment program in some embodiments of the PT, WO 2011/153505 PCT/US2011/039178 19 1 e.g., a Token-Based Purchase Enrollment ("TPE") component 500. In some 2 implementations, a user may desire to purchase a product, service, offering, and/or the 3 like ("product"), from a merchant. The user may provide user input, e.g., purchase 4 input 501, into the client indicating the user's desire to purchase the product. In some 5 implementations, the client may generate a purchase order message, e.g., 502, and 6 provide the generated purchase order message to the merchant server. The merchant 7 server may obtain the purchase order message from the client, and may parse the 8 purchase order message to extract details of the purchase order from the user, e.g., 503. 9 For example, the merchant server may utilize parsers similar to the example parsers 1o discussed below in the description with reference to FIGURE 8. Based on the parsing, 11 the merchant server may determine that the purchase order message is not tokenized, 12 e.g., 504, option "No". If the merchant server determines that the purchase order 13 message is tokenization, the merchant server may invoke a procedure to process the 14 transaction such as tPTE 700 component described further below in the discussion with 1s reference to FIGURE 7. Upon determining that the purchase order message is not 16 tokenized, the merchant server may determine that the user needs to be provided with 17 an option to sign up for payment tokenization services. The merchant server may 18 attempt to identify a token arbitrator to provide the payment tokenization services for 19 the user. For example, the merchant server may query, e.g., 505, a merchant database 20 for an address of a token arbitrator. In response, the merchant database may provide 21 the token arbitrator address, e.g., 5o6. The merchant server may generate a 22 tokenization invitation request on behalf of the user, e.g., 507, and provide the 23 tokenization invitation request to a token server.
WO 2011/153505 PCT/US2011/039178 20 1 [00331 In some implementations, the token server may parse the invitation 2 request message, and extract details of the user and client from the message, e.g., 508. 3 The token server may determine if additional information is required from the user to 4 generate a token data structure and/or token data record, e.g., 509. If additional 5 information is needed (e.g., not all fields of the token data record can be completed with 6 the available information), the token server may generate a token input form, e.g., 511, 7 and provide the token input form for the user. The token server may provide the token 8 input form to the client (either directly to the client or via the merchant server). The 9 client may render the form, and display, e.g., 512, the form for the user. In some 10 implementations, the user may obtain a form such as the example user interface 11 illustration depicted in FIGURE 2B. 12 [0034] In some implementations, the user may desire to enroll for payment 13 tokenization services, and may provide token creation input to complete the form, e.g., 14 513. The client may generate a competed form, and provide, e.g., 514, the form to the 15 token server (either directly or via the merchant server). The token server may obtain 16 the form, and parse the form to extract data fields and values from the form to generate 17 a token data record, e.g., 515. For example, the token server may generate a unique and 18 resolvable token identifier irrespective of the token requesting channel (e.g., merchant, 19 issuer, acquirer, payment network, user, etc). In some implementations, the token 20 server keeps track of all generated tokens via token identifiers, and as each is created, 21 subsequent requests for creation of a token with the same token identifier will be 22 denied. In some implementations, token record creation may be performed done 23 serially. For example, a serial series of token identifiers may be created for each issuer, 24 merchant, acquirer and/or payment network. For example, each series may involve a WO 2011/153505 PCT/US2011/039178 21 1 numeric range that is unique to each source. In other implementations, rather than 2 serial application, token identifiers may be assigned by random allocation. In some 3 implementations, each token may be pre-funded. For example, the source of the token 4 (e.g., issuer, acquirer, independent token arbitrator) may first obtain assurance that 5 funds have been uniquely and exclusively allocated for the token from the source to 6 which the token points. Thus, in some implementations, the token may be pre-funded 7 and pre-authorized for up to (or in the alternative, for exactly) a predefined amount of a 8 purchase transaction. For example, the token server may generate a token data 9 structure similar to the example XML-encoded data structure below: 10 <?XML version = "1.0" encoding = "UTF-8"?> 11 <token> 12 <unique ID>4NFU4RG94</uniqueID> 13 <!-- user_ID may optionally be used in some embodiments--> 14 <user ID>john.q.public@gmail.com</user_ID> 15 <timestamp>2011-02-22 15:22: 43</timestamp> 16 <expiry>2011-02-28 23:59:59</expiry> 17 <auth flag>true</auth_flag> 18 <auth protocol>verifychat</authprotocol> 19 <security protocol>digital certificate, digital cer link 20 </securityprotocol> 21 <digitalcert>52486ghb0bn encryptedhashinformation_89032y4gh<digitalcert> 22 <digital_certlink>http://www.acmedigitalcertification.com/auth.php?var=tlh 23 v43059876</digital cert link> 24 <!-- In some embodiments, clientdetails are optional and the token may be 25 tied to a specific client--> 26 <clientdetails> 27 <clientIP>192.168.23.126</clientIP> 28 <client type>smartphone</client type> 29 <clientmodel>HTC Hero</clientmodel> 30 <OS>Android 2.2</OS> 31 <app installedflag>true</app installed flag> 32 <client fingerprint>font list, MAC address, memory size, hardware 33 chip, screen resolution</clientfingerprint> 34 </clientdetails> 35 <funding> 36 <value decay>10%/mo</value decay> 37 <tokenadmin>issuer 123.65.78.129 123456789012345</tokenadmin> 38 <!--alternatively, token administrator may be different from funding 39 source and may also include merchant, pay network, third party--> 40 <funding source>issuer</funding source> 41 <!--merchant, pay networks, third parties pay also be funding 42 sources--> 43 <accounts> 44 <l> 45 <issuer-name>BankA</issuername> 46 <accountnum>123456789012345</accountnum> 47 <account type>checking</account type> WO 2011/153505 PCT/US2011/039178 22 1 <confirmtype>email</confirmtype> 2 <!-- fields below optional in some embodiments--> 3 <account-name>John Q. Public</account name> 4 <billing addres>123 Green Street Apt 1</billing address> 5 <phone>909-333-2345</phone> 6 <sign>/jqp/</sign> 7 <contactinfo>jqp@gmail.com</contactinfo> 8 <defaultcostshare>65%</defaultcost_share> 9 </1> 10 <2> 11 <issuer-name>TokenArbit</issuer-name> 12 <account tvpe>prefunded</accounttype> 13 <uniqueid>2325678654322345</unique id> 14 <individualdecay>1.5%</individual decay> 15 <defaultcostshare>l0%</defaultcostshare> 16 </2> 17 <3> 18 <issuer_name>BankC</issuer name> 19 <account type>stored value account</account type> 20 <accountnum>123456789012345</accountnum> 21 <maxvalue>$500</maxvalue> 22 <!-- fields below optional in some embodiments--> 23 <account-name>John Q. Public</accountname> 24 <billing addres>123 Green Street Apt 1</billing address> 25 <phone>909-333-2345</phone> 26 <sign>/jqp/</sign> 27 <confirm type>email</confirm type> 28 <contact info>jqp@gmail.com</contact info> 29 <defaultcostshare>25%</defaultcostshare> 30 </3> 31 </accounts> 32 </funding> 33 <shipping info> 34 <unique shipping transaction ID>A89349HH 35 </unique shipping transactionID> 36 <!-- use of shipping unique allows anonymous shipping to user in some 37 embodiments -- > 38 <!-- fields below optional in some embodiments -- > 39 <shipping address>123 Green Street</shippingaddress> 40 <ship type>Overnight</ship type> 41 <ship carrier>FedEx</shipcarrier> 42 <shipaccount>231453564392</ship account> 43 <tracking flag>true</tracking flag> 44 <sign flag>true</signflag> 45 </shippinginfo> 46 </token> 47 48 49 [00351 The token server may store the token data structure to a token database, 5o e.g., 516. The token server may also provide a token identifier, e.g., 517 to the client. 51 The client may store the token identifier and/or display the token identifier for the user, 52 e.g., 518. 53 [0036] FIGURES 6A-E show data flow diagrams illustrating an example 54 procedure to execute a token-based purchase transaction in some embodiments of the WO 2011/153505 PCT/US2011/039178 23 1 PT. In some implementations, a user, e.g., 601, may desire to purchase a product, 2 service, offering, and/or the like ("product"), from a merchant. The user may 3 communicate with a merchant server, e.g., 603a, via a client such as, but not limited to: 4 a personal computer, mobile device, television, point-of-sale terminal, kiosk, ATM, 5 and/or the like (e.g., 602). For example, the user may provide user input, e.g., purchase 6 input 611, into the client indicating the user's desire to purchase the product. In various 7 implementations, the user input may include, but not be limited to: keyboard entry, card 8 swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having 9 multiple accounts, smartphone, tablet, etc.), mouse clicks, depressing buttons on a 10 joystick/game console, voice commands, single/multi-touch gestures on a touch 11 sensitive interface, touching user interface elements on a touch-sensitive display, and/or 12 the like. For example, the user may direct a browser application executing on the client 13 device to a website of the merchant, and may select a product from the website via 14 clicking on a hyperlink presented to the user via the website. As another example, the 15 client may obtain track i data from the user's card (e.g., credit card, debit card, prepaid 16 card, charge card, etc.), such as the example track 1 data provided below: 17 %B123456789012345^PUBLIC/J.Q.^99011200000000000000**901******?* 18 (wherein '123456789012345' is the card number of 'J.Q. Public' and has a CVV 19 number of 901. '990112' is a service code, and *** represents decimal digits 20 which change randomly each time the card is used.) 21 22 23 [0037] In some implementations, the client may generate a tokenized purchase 24 order message, e.g., 612, and provide, e.g., 613, the tokenized purchase order message to 25 the merchant server. For example, a browser application executing on the client may 26 provide, on behalf of the user, a (Secure) Hypertext Transfer Protocol ("HTTP(S)") GET 27 message including the product order details for the merchant server in the form of data WO 2011/153505 PCT/US2011/039178 24 1 formatted according to the eXtensible Markup Language ("XML"). Below is an example 2 HTTP(S) GET message including an XML-formatted purchase order message for the 3 merchant server: 4 GET /purchase.php HTTP/1.1 5 Host: www.merchant.com 6 Content-Type: Application/XML 7 Content-Length: 1306 8 <?XML version = "1.0" encoding = "UTF-8"?> 9 <purchase_order> 10 <order_ID>4NFU4RG94</order_ID> 11 <timestamp>2011-02-22 15:22:43</timestamp> 12 <user ID>john.q.public@gmail.com</user_ID> 13 <clientdetails> 14 <clientIP>192.168.23.126</clientIP> 15 <client type>smartphone</client type> 16 <clientmodel>HTC Hero</clientmodel> 17 <OS>Android 2.2</OS> 18 <app installedflag>true</app installed flag> 19 </clientdetails> 20 <purchasedetails> 21 <num products>l</num products> 22 <product> 23 <product type>book</product type> 24 <product params> 25 <producttitle>XML for dummies</product title> 26 <ISBN>938-2-14-168710-0</ISBN> 27 <edition>2nd ed.</edition> 28 <cover>hardbound</cover> 29 <seller>bestbuybooks</seller> 30 </product params> 31 <quantity>l</quantity> 32 </product> 33 </purchasedetails> 34 <account params> 35 <token id>1234567890123456</tokenid> 36 </account params> 37 <shipping info> 38 <shipping adress>same as billing</shipping address> 39 <ship type>expedited</shiptype> 40 <ship carrier>FedEx</ship carrier> 41 <ship account>123-45-678</ship account> 42 <tracking flag>true</tracking flag> 43 <sign flag>false</signflag> 44 </shippinginfo> 45 </purchaseorder> 46 47 48 [o038] In some implementations, the merchant server may obtain the purchase 49 order message from the client, and may parse the purchase order message to extract 5o details of the purchase order from the user. Based on parsing the message, the 51 merchant may determine that the purchase order is tokenized. The merchant server WO 2011/153505 PCT/US2011/039178 25 1 may issue a query to a database, e.g., 615, to a merchant database, e.g., 604, to 2 determine an arbitrator to process the tokenized purchase order. For example, the 3 merchant server may utilize a hypertext preprocessor ("PHP") script including 4 Structured Query Language ("SQL") commands to query a relational database for an 5 address of a token arbitator. An example PHP/SQL listing for querying a database for a 6 token arbitrator address 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 selectdb("ARBITRATORS.SQL"); // select database table to search 11 //create query for token arbitrators 12 $query = "SELECT arbitratorid, arbitators_name arbitratoraddress 13 arbitratorURL FROM TokenizationTable WHERE usercardnum LIKE '%' 14 $userpaymentcardnumber"; 15 $result = mysql-query($query); // perform the search query 16 mysql-close("'ARBITRATORS.SQL"); // close database access 17 ?> 18 19 20 [0039] In response, the merchant database may provide the token arbitrator 21 address, e.g., 616. The merchant server may generate a token arbitration request, e.g., 22 617, and provide the token arbitration request, e.g., 618, to a token server, e.g., 605. For 23 example, the merchant server may provide a HTTP(S) POST message including the 24 token arbitration request similar to the example below: 25 POST /arbitrate.php HTTP/1.1 26 Host: www.tokenizer.com 27 Content-Type: Application/XML 28 Content-Length: 579 29 <?XML version = "1.0" encoding "UTF-8"?> 30 GET /purchase.php HTTP/l.1 31 Host: www.merchant.com 32 Content-Type: Application/XML 33 Content-Length: 1306 34 <?XML version = "1.0" encoding ="UTF-"?> 35 <purchase_order> 36 <order_ID>4LFU4RG94</order_ID> 37 <timestamp>2011-02-22 15:22:43</timestamp> 38 <user_ID>john.q.public@gmail.com</user_ID> 39 <clientdetails> 40 <client_IP>192.168.23.126</client_IP> 41 <clienttype>smartphone</clienttype> 42 <client_model>HTC Hero</client model> 43 <OS>Android 2.2</OS> WO 2011/153505 PCT/US2011/039178 26 1 <appinstalledflag>true</appinstalled flag> 2 </clientdetails> 3 <merchant params> 4 <merchant_id>3FBCR4INCK/merchantid> 5 <merchant_name>Books & Things, Inc.</merchant_name> 6 <merchantauth_key>1NN1F484MCP59CHB27365</merchantauth key> 7 </merchant params> 8 <purchasedetails> 9 <num products>l</num products> 10 <product> 11 <product type>book</product type> 12 <product params> 13 <producttitle>XML for dummies</product title> 14 <ISBN>938-2-14-168710-0</ISBNT> 15 <edition>2nd ed.</edition> 16 <cover>hardbound</cover> 17 <seller>bestbuybooks</seller> 18 </product params> 19 <quantity>l</quantity> 20 </product> 21 </purchase details> 22 <account params> 23 <token-id>1234567890123456</tokenid> 24 </account params> 25 <shipping info> 26 <shipping adress>same as billing</shippingaddress> 27 <ship type>expedited</ship type> 28 <ship carrier>FedEx</shipcarrier> 29 <ship account>123-45-678</ship account> 30 <trackingflag>true</trackingflag> 31 <sign flag>false</sign flag> 32 </shippinginfo> 33 </purchase_order> 34 35 36 [o 040] In various implementations, the token server may be part of the merchant 37 system (e.g., a merchant process), or part of the payment network (e.g., a pay network 38 server), or an independent server operating in conjunction with the merchant, issuer, 39 acquirer and payment network. In general, it is to be understood that any entity and/or 40 component included in the PT may serve as a token arbitrator. In some 41 implementations, the token server may parse the token arbitration request message, and 42 extract the payment token from the message. The token server may determine the 43 payment options to utilize (or determine whether to request the user to provide 44 payment options details) for processing the transaction, using the payment token. For 45 example, the token server may issue, e.g., 619, a user issuer query to a database, e.g., 46 token database 606, using the payment token as search term in the query. For example, WO 2011/153505 PCT/US2011/039178 27 1 the token server may utilize PHP/SQL commands similar to the examples described 2 above. In response, the token database may provide an issuer data response, e.g., 620, 3 including data on issuers to contact for payment. For example, the issuer data response 4 may include an XML-encoded data file including instructions for the token server on 5 how to proceed with payment processing for the transaction. An example XML-encoded 6 issuer data file is provided below: 7 <?XML version = "1.0" encoding = "UTF-8"?> 8 <issuer data> 9 <auto-default>false</auto-default> 10 <user-contact>in-app</usercontact> 11 <device id>B17BP927</device id> 12 <default> 13 <issuer> 14 <issuerid>A12345</issuer-id> 15 <issuername>Bank de Tolkien</issuer_name> 16 <issuerIP>123.45.67.891</issuerIP> 17 <accounttype>token</account type> 18 <accountnumber>1234567890123456</account-number> 19 <percentage>65</percentage> 20 </issuer> 21 <issuer> 22 <issuerid>B12345</issuer-id> 23 <issuername>ABC Credit Union</issuer_name> 24 <issuer TP>223.25.67.091</issuer_IP> 25 <account_type>token</accounttype> 26 <accountnumber>6543210987654321</account-number> 27 <percentage>25</percentage> 28 </issuer> 29 <issuer> 30 <issuerid>C67890</issuerid> 31 <issuer name>BNR Bank</issuer name> 32 <issuerIP>l53.65.87.231</issuerIP> 33 <accounttype>token</accounttype> 34 <accountnumber>1234567890123456</accountnumber> 35 <percentage>10</percentage> 36 </issuer> 37 </default> 38 </issuerdata> 39 40 41 [00411 In some implementations, the token server may determine whether the 42 user token is authenticated, e.g., 621. For example, if no XML data is available 43 associated with the payment token, the token server may determine that the user has 44 not signed up for payment tokenization services. As another example, if the XML data 45 indicates that the user must be queried for authentication (e.g., login and password), WO 2011/153505 PCT/US2011/039178 28 1 then the token server may determine that verification of authentication is necessary. 2 The token server may initiate a user verification session. For example, an app executing 3 on the user's device may provide a "VerifyChat" feature for fraud prevention (e.g., by 4 activating UI element 213 in FIGURE 2). The token server may utilize the VerifyChat 5 feature to communicate with the user, and verify the authenticity of the originator of the 6 purchase transaction. In various implementations, the token server may send electronic 7 mail message, text (SMS) messages, Facebook@ messages, TwitterTM tweets, text chat, 8 voice chat, video chat (e.g., Apple FaceTime), and/or the like to communicate with the 9 user. For example, the token server may initiate a video challenge for the user. For 10 example, the user may need to present him/her-self via a video chat. In some 11 implementations, a customer service representative may manually determine the 12 authenticity of the user using the video of the user. In some implementations, the PT 13 may utilize face, biometric and/or like recognition (e.g., using pattern classification 14 techniques) to determine the identity of the user. In some implementations, the app 15 may provide reference marker (e.g., cross-hairs, target box, etc.), so that the user may 16 the video to facilitate the PT' automated recognition of the user. As another example, 17 token server may request the user for a digital certificate to verify authenticity. As 18 another example, the token server may request a user name and password to enable the 19 token for payment processing. 20 [0042] If the token server determines that the user is authenticated, the token 21 server may provide a token authentication confirmation, e.g., 622a. Also, if the token 22 server determines that the user should be queried for payment options (e.g., instead of 23 using only the pre-defined settings in the issuer data response 620), the token server 24 may request payment options from the user. For example, the token server may provide WO 2011/153505 PCT/US2011/039178 29 1 a HTTP(S) POST message similar to the examples above to the client 602. The client 2 may render, e.g., 623, the token authentication confirmation and/or payment options 3 request, and display the message(s) for the user, e.g., 624. 4 [o043] In some implementations, the user may desire to enter custom payment 5 options to process the current purchase transaction. In such implementations, the user 6 may provide a payment options input 626, for example, such as discussed above in the 7 description with reference to FIGURE 2. The client may generate a payment options 8 message using the user's input, and provide the payment options message, e.g., 627, to 9 the token server. In some implementations, the token server may determine the issuers 10 to contact for payment processing using the pre-defined issuer settings and/or the 11 payment options input provided by the user, e.g., 628. In some implementations, the 12 token server may update the issuer data stored in the token database using the payment 13 options input provided by the user, e.g., 629. 14 [0044] In some implementations, the token server may provide the token data, 15 issuer data, and/or user payment options input, e.g., 634, to a pay network server (e.g., 16 if the token server is separate from the pay network system). For example, the token 17 server may provide a HTTP(S) POST message to the pay network server similar to the 18 examples above. The pay network server may process the transaction so as to transfer 19 funds for the purchase into an account stored on an acquirer of the merchant. For 20 example, the acquirer may be a financial institution maintaining an account of the 21 merchant. For example, the proceeds of transactions processed by the merchant may be 22 deposited into an account maintained by at a server of the acquirer.
WO 2011/153505 PCT/US2011/039178 30 1 [o0451 In some implementations, the pay network server may generate a query, 2 e.g., 635, for issuer server(s) corresponding to the payment token and user-selected 3 payment options. For example, the user's payment token may be linked to one or more 4 issuer financial institutions ("issuers"), such as banking institutions, which issued the 5 account(s) for the user linked to the payment token. For example, such accounts may 6 include, but not be limited to: credit card, debit card, prepaid card, checking, savings, 7 money market, certificates of deposit, stored (cash) value accounts and/or the like. 8 Issuer server(s), e.g., 6o9a-n, of the issuer(s) may maintain details of the user's account 9 linked to the payment token. In some implementations, a database, e.g., pay network 10 database 6o8, may store details of the issuer server(s) associated with the issuer(s). For 11 example, the database may be a relational database responsive to Structured Query 12 Language ("SQL") commands. The pay network server may query the pay network 13 database for issuer server(s) details. For example, the pay network server may execute a 14 hypertext preprocessor ("PHP") script including SQL commands to query the database 15 for details of the issuer server(s). An example PHP/SQL command listing, illustrating 16 substantive aspects of querying the database, is provided below: 17 <?PHP 18 header('Content-Type: text/plain'); 19 mysql connect("254.93.179.112",$DBserver,$password); // access database server 20 mysql selectdb("ISSUERS.SQL"); // select database table to search 21 //create query for issuer server data 22 $query = "SELECT issuername issueraddress issuerid ip address macaddress 23 auth key port num security settings list FROM IssuerTable WHERE accountnum 24 LIRE '%' $accountnum"; 25 $result = mysql-query($query); // perform the search query 26 mysqlcloe("ISSUERS.SQL"); // close database access 27 ?> 28 29 30 [0046] In response to obtaining the issuer server query, e.g., 635, the pay network 31 database may provide, e.g., 636, the requested issuer server data to the pay network 32 server. In some implementations, the pay network server may utilize the issuer server WO 2011/153505 PCT/US2011/039178 31 1 data to generate authorization request(s), e.g., 637, for each of the issuer server(s) 2 selected based on the pre-defined payment settings associated with the token, and/or 3 the user's payment options input, and provide the card authorization request(s), e.g., 4 638a-n, to the issuer server(s), e.g., 6o9a-n. In some implementations, the authorization 5 request(s) may include details such as, but not limited to: the costs to the user involved 6 in the transaction, card account details of the user, user billing and/or shipping 7 information, and/or the like. For example, the pay network server may provide a 8 HTTP(S) POST message including an XML-formatted authorization request similar to 9 the example listing provided below: 10 POST /authorization.php HTTP/1.1 11 Host: www.issuer.com 12 Content-Type: Application/'XML 13 Content-Length: 624 14 <?XML version = "1.0" encoding = "UTF-8"?> 15 <card query request> 16 <query ID>VNEi39FK</query ID> 17 <timestamp>2011-02-22 15:22:44</timestamp> 18 <purchasesummary> 19 <num products>1</numproducts> 20 <product> 21 <product summary>Book - XML for dummies</product summary> 22 <product quantity>1</productquantity? 23 </product> 24 </purchase_summary> 25 <transaction cost>$22.61</transaction-cost> 26 <account params> 27 <account type>token</account type> 28 <accountnum>1234567890123456</'accountnum> 29 </account params> 30 <merchant params> 31 <merchant id>3FBCR4INC</merchant id> 32 <merchant name>Books & Things, Inc.</merchantname> 33 <merchantauthkey>lNNF484MCP59CHB27365</merchant_auth key> 34 </merchant params> 35 </card_queryrequest> 36 37 38 [0047] In some implementations, an issuer server may parse the authorization 39 request(s), and based on the request details may query a database, e.g., user profile 40 database 61oa-n, for data associated with an account linked to the user's payment token.
WO 2011/153505 PCT/US2011/039178 32 1 For example, the issuer server may issue PHP/SQL commands similar to the example 2 provided below: 3 <?PHP 4 header('Content-Type: text/plain'); 5 mysql connect("254.93.179.ll2",$DBserver,$password); // access database server 6 mysql selectdb("USERS.SQL"); // select database table to search 7 //create query for user data 8 $query = "SELECT userid username user_balance account-type FROM UserTable 9 WHERE account-num LIKE '%' $accountnum"; 10 $result = mysql-query($query); // perform the search query 11 mysql-close("USERS.SQL"); // close database access 12 ?> 13 14 15 [0048] In some implementations, on obtaining the user data, e.g., 64oa-n, the 16 issuer server may determine whether the user can pay for the transaction using funds 17 available in the account, e.g., 641a-n. For example, the issuer server may determine 18 whether the user has a sufficient balance remaining in the account, sufficient credit 19 associated with the account, and/or the like. Based on the determination, the issuer 20 server(s) may provide an authorization response, e.g., 642a-n, to the pay network 21 server. For example, the issuer server(s) may provide a HTTP(S) POST message similar 22 to the examples above. In some implementations, if at least one issuer server 23 determines that the user cannot pay for the transaction using the funds available in the 24 account, see e.g., 643-644, the pay network server may request payment options again 25 from the user (e.g., by providing an authorization fail message 644 to the token server 26 and requesting the token server to obtain payment options input again from the user), 27 and re-attempt authorization for the purchase transaction. In some implementations, if 28 the number of failed authorization attempts exceeds a threshold, the pay network server 29 may abort the authorization process, and provide an "authorization fail" message to the 30 merchant server, token server and/or client.
WO 2011/153505 PCT/US2011/039178 33 1 [o049] In some implementations, the pay network server may obtain the 2 authorization message including a notification of successful authorization, see e.g., 643, 3 646, and parse the message to extract authorization details. Upon determining that the 4 user possesses sufficient funds for the transaction, the pay network server may generate 5 a transaction data record, e.g., 645, from the authorization request and/or authorizarion 6 response, and store the details of the transaction and authorization relating to the 7 transaction in a transactions database. For example, the pay network server may issue 8 PHP/SQL commands similar to the example listing below to store the transaction data 9 in a database: 10 <?PHP 11 header('Content-Type: text/plain'); 12 mysql connect("254.92.185.103",$DBserver,$password) ; // access database server 13 mysql select("TRANSACTIONS.SQL"); // select database to append 14 mysqlgquery("INSERT INTO PurchasesTable (timestamp, purchasesummary list, 15 num products, product summary, product quantity, transactioncost, 16 account paramslist, accountname, account type, accountnum, 17 billing addres, zipcode, phone, sign, merchantparamslist, merchantid, 18 merchantname, merchant auth key) 19 VALUES (time), $purchase summary list, $numproducts, $product-summary, 20 $product quantity, $transactioncost, $accountparamslist, $accountname, 21 $account type, $accountnum, $billing addres, $zipcode, $phone, $sign, 22 $merchantparamslist, $merchantid, $merchantname, $merchantauthkey)"); 23 // add data to table in database 24 mysqlclose("TRANSACTIONS.SQL"); // close connection to database 25 ?> 26 27 28 [0050] In some implementations, the pay network server may forward an 29 authorization success message, e.g., 646, to the token server, which may in turn forward 30 the authorization success message, e.g., 647, to the merchant server. The merchant may 31 obtain the authorization message, and determine from it that the user possesses 32 sufficient funds in the card account to conduct the transaction. The merchant server 33 may add a record of the transaction for the user to a batch of transaction data relating to 34 authorized transactions. For example, the merchant may append the XML data 35 pertaining to the user transaction to an XML data file comprising XML data for WO 2011/153505 PCT/US2011/039178 34 1 transactions that have been authorized for various users, e.g., 648, and store the XML 2 data file, e.g., 649, in a database, e.g., merchant database 604. For example, a batch 3 XML data file may be structured similar to the example XML data structure template 4 provided below: 5 <?XML version = "1.0" encoding = "UTF--"?> 6 <merchantdata> 7 <merchantid>3FBCR4INC</merchant id> 8 <merchant name>Books & Things, Tnc.</merchantname> 9 <merchantauthkey>lNNF484MCP59CHB27365</merchant_authkey> 10 <accountnumber>123456789</account number> 11 </merchantdata> 12 <transactiondata> 13 <transaction 1> 14 15 </transaction 1> 16 <transaction 2> 17 18 </transaction 2> 19 20 21 22 <transaction n> 23 24 </transaction n> 25 </transactiondata> 26 27 28 [o 0 51] In some implementations, the server may also generate a purchase receipt, 29 e.g., 648, and provide the purchase receipt to the client, e.g., 650. The client may render 30 and display, e.g., 651-652, the purchase receipt for the user. For example, the client may 31 render a webpage, electronic message, text / SMS message, buffer a voicemail, emit a 32 ring tone, and/or play an audio message, etc., and provide output including, but not 33 limited to: sounds, music, audio, video, images, tactile feedback, vibration alerts (e.g., 34 on vibration-capable client devices such as a smartphone etc.), and/or the like. 35 [0052] With reference to FIGURE 6E, in some implementations, the merchant 36 server may initiate clearance of a batch of authorized transactions. For example, the 37 merchant server may generate a batch data request, e.g., 653, and provide the request, 38 e.g., 654, to a database, e.g., merchant database 604. For example, the merchant server WO 2011/153505 PCT/US2011/039178 35 1 may utilize PHP/SQL commands similar to the examples provided above to query a 2 relational database. In response to the batch data request, the database may provide the 3 requested batch data, e.g., 655. The server may generate a batch clearance request, e.g., 4 656, using the batch data obtained from the database, and provide, e.g., 657, the batch 5 clearance request to an acquirer server, e.g., 603b. For example, the merchant server 6 may provide a HTTP(S) POST message including XML-formatted batch data in the 7 message body for the acquirer server. The acquirer server may generate, e.g., 658, a 8 batch payment request using the obtained batch clearance request, and provide the 9 batch payment request to the pay network server, e.g., 659. The pay network server may 10 parse the batch payment request, and extract the transaction data for each transaction 11 stored in the batch payment request, e.g., 660. The pay network server may store the 12 transaction data, e.g., 661, for each transaction in a database, e.g., pay network database 13 6o8. For each extracted transaction, the pay network server may query, e.g., 662-663, a 14 database, e.g., pay network database 608, for an address of an issuer server. For 1s example, the pay network server may utilize PHP/SQL commands similar to the 16 examples provided above. The pay network server may generate an individual payment 17 request, e.g., 664, for each transaction for which it has extracted transaction data, and 18 provide the individual payment request, e.g., 665, to the issuer server, e.g., 609. For 19 example, the pay network server may provide a HTTP(S) POST request similar to the 20 example below: 21 POST /requestpay.php HTTP/1.1 22 Host: www.issuer.com 23 Content-Type: Application/XML 24 Content-Length: 788 25 <?XML version = "1.0" encoding = "UTF-8"?> 26 <payrequest> 27 <request ID>CNI4ICNTW2</request ID> 28 <timestamp>20ll-02-22 17:00:01</timestamp> 29 <payamount>$34.78</pay_amount> WO 2011/153505 PCT/US2011/039178 36 1 <accountparams> 2 <account name>John Q. Public</account name> 3 <account type>credit</account type> 4 <accountnum>123456789012345</account num> 5 <billing address>123 Green St., Norman, OK 98765</billing address> 6 <phone>123-456-7809</phone> 7 <sign>/jqp/</sign> 8 </account params> 9 <merchant params> 10 <merchant id>3FBCR4INC</merchant id> 11 <merchant name>Books & Things, Inc.</merchant-name> 12 <merchantauthkey>lNNlF484MCP59CHB27365</merchant_auth key> 13 </merchant params> 14 <purchasesummary> 15 <numproducts>l</num products> 16 <product> 17 <productsummary>Book - XML for dummies</product summary> 18 <product quantity>l</product quantity? 19 </product> 20 </purchasesummary> 21 </pay request> 22 23 24 [0053] In some implementations, the issuer server may generate a payment 25 command, e.g., 666. For example, the issuer server may issue a command to deduct 26 funds from the user's account (or add a charge to the user's credit card account). The 27 issuer server may issue a payment command, e.g., 667, to a database storing the user's 28 account information, e.g., user profile database 61o. The issuer server may provide a 29 funds transfer message, e.g., 668, to the pay network server, which may forward, e.g., 30 669, the funds transfer message to the acquirer server. An example HTIP(S) POST 31 funds transfer message is provided below: 32 POST /clearance.php HTTP/1.1 33 Host: www.acquirer.com 34 Content-Type: Application/XML 35 Content-Length: 206 36 <?XML version = "1.0" encoding = "UTF-8"?> 37 <depositack> 38 <requestID>CIII4ICNW2</request ID> 39 <clear flag>true</clear flag> 40 <timestamp>2011-02-22 17:00:02</timestamp> 41 <deposit amount>$34.78</deposit amount> 42 </depositack> 43 44 45 [0054] In some implementations, the acquirer server may parse the funds 46 transfer message, and correlate the transaction (e.g., using the requestID field in the WO 2011/153505 PCT/US2011/039178 37 1 example above) to the merchant. The acquirer server may then transfer the funds 2 specified in the funds transfer message to an account of the merchant, e.g., 670. 3 [o055] FIGURES 7A-F show logic flow diagrams illustrating example aspects of 4 executing a token-based purchase transaction in some embodiments of the PT, e.g., a 5 Token-Based Purchase Transaction Execution ("tPTE") component 700. In some 6 implementations, a user may desire to purchase a product, service, offering, and/or the 7 like ("product"), from a merchant. The user may communicate with a merchant server, 8 via a client. For example, the user may provide purchase input, e.g., 701, into the client 9 indicating the user's desire to purchase the product. In some implementations, the 10 client may generate a tokenized purchase order message, e.g., 702, and provide the 11 tokenized purchase order message to the merchant server. The merchant server may 12 obtain the purchase order message from the client, and may parse the purchase order 13 message to extract details of the purchase order from the user. Based on parsing the 14 message, the merchant may determine that the purchase order is tokenized, e.g., 703. If 15 the merchant server determines that the purchase order is not tokenized, e.g., 704, 16 option "No," then the merchant server may process the transaction as a normal card 17 based transaction, and bypass the token interpretation process. If the merchant server 18 determines that the purchase order is tokenized, e.g., 704, option "Yes," then the 19 merchant server may issue a query, e.g., 705, to a merchant database to determine an 20 arbitrator to process the tokenized purchase order. In response, the merchant database 21 may provide the token arbitrator address, e.g., 707. The merchant server may generate 22 a token arbitration request, e.g., 708, and provide the token arbitration request to a 23 token server.
WO 2011/153505 PCT/US2011/039178 38 1 [o056] In some implementations, the token server may parse the token 2 arbitration request message, and extract the payment token from the message. The 3 token server may determine the payment options to utilize (or determine whether to 4 request the user to provide payment options details) for processing the transaction, 5 using the payment token. For example, the token server may issue, e.g., 708, a user 6 issuer query to a token database using the payment token as search term in the query. 7 In response, the token database may provide an issuer data response, e.g., 709, 8 including data on issuers to contact for payment. In some implementations, the token 9 server may determine whether the user token is authenticated, e.g., 710. If the token 10 server determines that the user is not authenticated, e.g., 711, option "No," the token 11 server may generate an "authentication fail message," e.g., 712, and initiate an error 12 handling routine and/or a user enrollment routine, e.g., 713, such as the PTE 500 13 component discussed above in the description with reference to FIGURE 5. If the token 14 server determines that the user is authenticated, e.g., 711, option "Yes," the token server 15 may determine whether the user should be queried for payment options (e.g., instead of 16 using only the pre-defined settings in the issuer data response), e.g., 714. If the token 17 server determines that the user should be queries for payment options settings, e.g., 715, 18 option "No," the token server may request payment options from the user, e.g., 716. The 19 client may render the payment options request and display the request, e.g., 717. 20 [00571 In some implementations, the user may desire to enter custom payment 21 options to process the current purchase transaction. In such implementations, the user 22 may provide a payment options input 718. The client may generate a payment options 23 message using the user's input, and provide the payment options message to the token 24 server. In some implementations, the token server may determine the issuers to contact WO 2011/153505 PCT/US2011/039178 39 1 for payment processing using the pre-defined issuer settings and/or the payment 2 options input provided by the user, e.g., 719. In some implementations, the token server 3 may update the issuer data stored in the token database using the payment options 4 input provided by the user, e.g., 720. In some implementations, the token server may 5 generate an "authorization in progress" message, e.g., 721, and provide the message to 6 the merchant server, which may in turn forward, e.g., 722, the message to the client. 7 The client may render and display, e.g., 723, the "authorization in progress" message for 8 the user. 9 [o 058] In some implementations, the token server may generate a message 1o including the token data, issuer data, and/or user payment options input, e.g., 724, and 11 provide the message to a pay network server (e.g., if the token server is separate from 12 the pay network system). The pay network server may process the transaction so as to 13 transfer funds for the purchase into an account stored on an acquirer of the merchant. 14 If the merchant server initially received a non-tokenized purchase order message for the 15 client, e.g., 725, the merchant server may generate a card query request, e.g., 726, and 16 provide the card query request to an acquirer server. The acquirer server may parse the 17 merchant server's request, e.g., 727, generate a card authorization request, e.g., 728, and 18 provide the card authorization request to a pay network server. However, if the initial 19 purchase order from the client is tokenized, the token server may deconstruct the 20 payment details to be utilized, as discussed above, and may provide the token, issue and 21 payment options to a pay network server, e.g., 729. 22 [0059] In some implementations, the pay network server may generate a query, 23 e.g., 729, for issuer server(s) corresponding to the payment token and user-selected WO 2011/153505 PCT/US2011/039178 40 1 payment options. In some implementations, the pay network server may query the pay 2 network database for issuer server(s) details, e.g., 730. In response to obtaining the 3 issuer server query, the pay network database may provide, e.g., 731, the requested 4 issuer server data to the pay network server. In some implementations, the pay network 5 server may utilize the issuer server data to generate authorization request(s), e.g., 732, 6 for each of the issuer server(s) selected based on the pre-defined payment settings 7 associated with the token, and/or the user's payment options input, and provide the 8 card authorization request(s) to the issuer server(s). In some implementations, an issuer 9 server may parse the authorization request(s), e.g., 733, and based on the request details 10 may query a user profile database for data associated with an account linked to the 11 user's payment token, e.g., 734. In some implementations, on obtaining the user data, 12 e.g., 735, the issuer server may determine whether the user can pay for the transaction 13 using funds available in the account, e.g., 736. For example, the issuer server may 14 determine whether the user has a sufficient balance remaining in the account, sufficient 15 credit associated with the account, and/or the like. Based on the determination, the 16 issuer server(s) may generate and provide an authorization response, e.g., 737, to the 17 pay network server. In some implementations, if at least one issuer server determines 18 that the user cannot pay for the transaction using the funds available in the account, see 19 e.g., 738, 739, option "No," the pay network server may request payment options again 20 from the user (e.g., by providing an authorization fail message 644 to the token server 21 and requesting the token server to obtain payment options input again from the user), 22 and re-attempt authorization for the purchase transaction. In some implementations, if 23 the number of failed authorization attempts exceeds a threshold, e.g., 740, option "Yes," WO 2011/153505 PCT/US2011/039178 41 1 the pay network server may abort the authorization process, and provide an "transaction 2 terminated" message, e.g., 741, to the merchant server, token server and/or client. 3 [o060] In some implementations, the pay network server may obtain the 4 authorization message including a notification of successful authorization and parse the 5 message to extract authorization details. Upon determining that the user possesses 6 sufficient funds for the transaction, e.g., 739, option "Yes," the pay network server may 7 generate a transaction data record, e.g., 742, from the authorization request and/or 8 authorization response, and store, e.g., 743, the details of the transaction and 9 authorization relating to the transaction in a transactions database. In some 10 implementations, the pay network server may generate an authorization success 11 message, e.g., 744, and forward the message to the token server, which may in turn 12 forward the authorization success message, e.g., 745-746, to the acquirer server and/or 13 the merchant server. In some embodiments, the authorization success message may 14 include no personally identifying information, and may, in some embodiments, include 15 only the payment token identifier. The merchant may obtain the authorization message, 16 and determine from it whether the transaction was authorized, e.g., 747-748. If the 17 transaction was authorized, e.g., 748, option "Yes," the merchant server may add a 18 record of the transaction for the user to a batch of transaction data relating to 19 authorized transactions, e.g., 749-750. In some implementations, the server may also 20 generate a purchase receipt, e.g., 751, and provide the purchase receipt to the client. The 21 client may render and display, e.g., 753, the purchase receipt for the user. 22 [o061] With reference to FIGURES 7E-F, in some implementations, the merchant 23 server may initiate clearance of a batch of authorized transactions. For example, the WO 2011/153505 PCT/US2011/039178 42 1 merchant server may generate a batch data request, e.g., 754, and provide the request to 2 a merchant database. In response to the batch data request, the merchant database may 3 provide the requested batch data, e.g., 755. The server may generate a batch clearance 4 request, e.g., 756, using the batch data obtained from the database, and provide the 5 batch clearance request to an acquirer server. The acquirer server may parse the batch 6 clearance request, e.g., 657, and generate, e.g., 758, a batch payment request using the 7 Obtained batch clearance request, and provide the batch payment request to the pay 8 network server. The pay network server may parse the batch payment request, e.g., 759, 9 and extract the transaction data for each transaction stored in the batch payment 10 request. For each payment request in the batch, the pay network server may extract 11 purchase transaction data, e.g., 761, and generate a transaction data record, e.g., 762. 12 The pay network server may store the transaction data, e.g., 763, for each transaction in 13 a pay network database. For each extracted transaction, the pay network server may 14 query, e.g., 764-765, the pay network database for an address of an issuer server. The 1s pay network server may generate an individual payment request, e.g., 766, for each 16 transaction for which it has extracted transaction data, and provide the individual 17 payment request to the issuer server. 18 [o062] In some implementations, the issuer server may parse the individual 19 payment request, e.g., 767, and generate a payment command, e.g., 768. For example, 20 the issuer server may issue a command to deduct funds from the user's account (or add 21 a charge to the user's credit card account). The issuer server may issue a payment 22 command to a user profile database. The issuer server may generate a funds transfer 23 message, e.g., 770, and provide the message to the pay network server. As described 24 above, the system may process each individual payment request in the batch, until all WO 2011/153505 PCT/US2011/039178 43 1 requests in the batch have been processed, see e.g., 771. The pay network server may 2 then generate a batch funds transfer message, e.g., 772, and provide the batch funds 3 transfer message to the acquirer server, e.g., 773. In some implementations, the 4 acquirer server may parse the funds transfer message, and correlate the transaction to 5 the merchant. The acquirer server may then transfer the funds specified in the funds 6 transfer message to an account of the merchant, e.g., 774. 7 PT Controller 8 [o0631 FIGURE 8 illustrates inventive aspects of a PT controller 8o1 in a block 9 diagram. In this embodiment, the PT controller 8o1 may serve to aggregate, process, 10 store, search, serve, identify, instruct, generate, match, and/or facilitate interactions 11 with a computer through various technologies, and/or other related data. 12 [o064] Typically, users, which may be people and/or other systems, may engage 13 information technology systems (e.g., computers) to facilitate information processing. 14 In turn, computers employ processors to process information; such processors 803 may 15 be referred to as central processing units (CPU). One form of processor is referred to as 16 a microprocessor. CPUs use communicative circuits to pass binary encoded signals 17 acting as instructions to enable various operations. These instructions may be 18 operational and/or data instructions containing and/or referencing other instructions 19 and data in various processor accessible and operable areas of memory 829 (e.g., 20 registers, cache memory, random access memory, etc.). Such communicative 21 instructions may be stored and/or transmitted in batches (e.g., batches of instructions) 22 as programs and/or data components to facilitate desired operations. These stored 23 instruction codes, e.g., programs, may engage the CPU circuit components and other WO 2011/153505 PCT/US2011/039178 44 1 motherboard and/or system components to perform desired operations. One type of 2 program is a computer operating system, which, may be executed by CPU on a 3 computer; the operating system enables and facilitates users to access and operate 4 computer information technology and resources. Some resources that may be employed 5 in information technology systems include: input and output mechanisms through 6 which data may pass into and out of a computer; memory storage into which data may 7 be saved; and processors by which information may be processed. These information 8 technology systems may be used to collect data for later retrieval, analysis, and 9 manipulation, which may be facilitated through a database program. These information 1o technology systems provide interfaces that allow users to access and operate various 11 system components. 12 [0065] In one embodiment, the PT controller 8o1 may be connected to and/or 13 communicate with entities such as, but not limited to: one or more users from user 14 input devices 811; peripheral devices 812; an optional cryptographic processor device 15 828; and/or a communications network 813. For example, the PT controller 8o1 may be 16 connected to and/or communicate with users operating client device(s) including, but 17 not limited to, personal computer(s), server(s) and/or various mobile device(s) 18 including, but not limited to, cellular telephone(s), smartphone(s) (e.g., iPhone®, 19 Blackberry, Android OS-based phones etc.), tablet computer(s) (e.g., Apple iPadTM, 20 HP Slate"M, Motorola Xoom'M, etc.), eBook reader(s) (e.g., Amazon Kindle"M, Barnes 21 and Noble's NookTM eReader, etc.), laptop computer(s), notebook(s), netbook(s), 22 gaming console(s) (e.g., XBOX Live T M , Nintendo® DS, Sony PlayStation® Portable, 23 etc.), portable scanner(s) and/or the like.
WO 2011/153505 PCT/US2011/039178 45 1 [o066] Networks are commonly thought to comprise the interconnection and 2 interoperation of clients, servers, and intermediary nodes in a graph topology. It should 3 be noted that the term "server" as used throughout this application refers generally to a 4 computer, other device, program, or combination thereof that processes and responds to 5 the requests of remote users across a communications network. Servers serve their 6 information to requesting "clients." The term "client" as used herein refers generally to a 7 computer, program, other device, user and/or combination thereof that is capable of 8 processing and making requests and obtaining and processing any responses from 9 servers across a communications network. A computer, other device, program, or 10 combination thereof that facilitates, processes information and requests, and/or 11 furthers the passage of information from a source user to a destination user is 12 commonly referred to as a "node." Networks are generally thought to facilitate the 13 transfer of information from source points to destinations. A node specifically tasked 14 with furthering the passage of information from a source to a destination is commonly 15 called a "router." There are many forms of networks such as Local Area Networks 16 (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. 17 For example, the Internet is generally accepted as being an interconnection of a 18 multitude of networks whereby remote clients and servers may access and interoperate 19 with one another. 20 [0067] The PT controller 8oi may be based on computer systems that may 21 comprise, but are not limited to, components such as: a computer systemization 802 22 connected to memory 829.
WO 2011/153505 PCT/US2011/039178 46 1 Computer Systemization 2 [0068] A computer systemization 802 may comprise a clock 830, central 3 processing unit ("CPU(s)" and/or "processor(s)" (these terms are used interchangeable 4 throughout the disclosure unless noted to the contrary)) 803, a memory 829 (e.g., a read 5 only memory (ROM) 806, a random access memory (RAM) 805, etc.), and/or an 6 interface bus 807, and most frequently, although not necessarily, are all interconnected 7 and/or communicating through a system bus 804 on one or more (mother)board(s) 802 8 having conductive and/or otherwise transportive circuit pathways through which 9 instructions (e.g., binary encoded signals) may travel to effect communications, 10 operations, storage, etc. Optionally, the computer systemization may be connected to an 11 internal power source 886; e.g., optionally the power source may be internal. 12 Optionally, a cryptographic processor 826 and/or transceivers (e.g., ICs) 874 may be 13 connected to the system bus. In another embodiment, the cryptographic processor 14 and/or transceivers may be connected as either internal and/or external peripheral 1s devices 812 via the interface bus I/O. In turn, the transceivers may be connected to 16 antenna(s) 875, thereby effectuating wireless transmission and reception of various 17 communication and/or sensor protocols; for example the antenna(s) may connect to: a 18 Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 19 3.0, FM, global positioning system (GPS) (thereby allowing PT controller to determine 20 its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, 21 Bluetooth 2.1 + EDR, FM, etc.); a Broadcom BCM475oIUB8 receiver chip (e.g., GPS); an 22 Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA 23 communications); and/or the like. The system clock typically has a crystal oscillator and 24 generates a base signal through the computer systemization's circuit pathways. The WO 2011/153505 PCT/US2011/039178 47 1 clock is typically coupled to the system bus and various clock multipliers that will 2 increase or decrease the base operating frequency for other components interconnected 3 in the computer systemization. The clock and various components in a computer 4 systemization drive signals embodying information throughout the system. Such 5 transmission and reception of instructions embodying information throughout a 6 computer systemization may be commonly referred to as communications. These 7 communicative instructions may further be transmitted, received, and the cause of 8 return and/or reply communications beyond the instant computer systemization to: 9 communications networks, input devices, other computer systemizations, peripheral 10 devices, and/or the like. Of course, any of the above components may be connected 11 directly to one another, connected to the CPU, and/or organized in numerous variations 12 employed as exemplified by various computer systems. 13 [o069] The CPU comprises at least one high-speed data processor adequate to 14 execute program components for executing user and/or system-generated requests. 15 Often, the processors themselves will incorporate various specialized processing units, 16 such as, but not limited to: integrated system (bus) controllers, memory management 17 control units, floating point units, and even specialized processing sub-units like 18 graphics processing units, digital signal processing units, and/or the like. Additionally, 19 processors may include internal fast access addressable memory, and be capable of 20 mapping and addressing memory 829 beyond the processor itself; internal memory may 21 include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 22 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a 23 memory address space that is accessible via instruction address, which the processor 24 can construct and decode allowing it to access a circuit path to a specific memory WO 2011/153505 PCT/US2011/039178 48 1 address space having a memory state. The CPU may be a microprocessor such as: 2 AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure 3 processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell 4 processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; 5 and/or the like processor(s). The CPU interacts with memory through instruction 6 passing through conductive and/or transportive conduits (e.g., (printed) electronic 7 and/or optic circuits) to execute stored instructions (i.e., program code) according to 8 conventional data processing techniques. Such instruction passing facilitates 9 communication within the PT controller and beyond through various interfaces. Should 10 processing requirements dictate a greater amount speed and/or capacity, distributed 11 processors (e.g., Distributed PT), mainframe, multi-core, parallel, and/or super 12 computer architectures may similarly be employed.Alternatively, should deployment 13 requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may 14 be employed. 15 [0070] Depending on the particular implementation, features of the PT may be 16 achieved by implementing a microcontroller such as CAST's R8o51XC2 microcontroller; 17 Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain 18 features of the PT, some feature implementations may rely on embedded components, 19 such as: Application-Specific Integrated Circuit ("ASIC"), Digital Signal Processing 20 ("DSP"), Field Programmable Gate Array ("FPGA"), and/or the like embedded 21 technology. For example, any of the PT component collection (distributed or otherwise) 22 and/or features may be implemented via the microprocessor and/or via embedded 23 components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some WO 2011/153505 PCT/US2011/039178 49 1 implementations of the PT may be implemented with embedded components that are 2 configured and used to achieve a variety of features or signal processing. 3 [o 071] Depending on the particular implementation, the embedded components 4 may include software solutions, hardware solutions, and/or some combination of both 5 hardware/software solutions. For example, PT features discussed herein may be 6 achieved through implementing FPGAs, which are a semiconductor devices containing 7 programmable logic components called "logic blocks", and programmable 8 interconnects, such as the high performance FPGA Virtex series and/or the low cost 9 Spartan series manufactured by Xilinx. Logic blocks and interconnects can be 10 programmed by the customer or designer, after the FPGA is manufactured, to 11 implement any of the PT features. A hierarchy of programmable interconnects allow 12 logic blocks to be interconnected as needed by the PT system designer/administrator, 13 somewhat like a one-chip programmable breadboard. An FPGA's logic blocks can be 14 programmed to perform the function of basic logic gates such as AND, and XOR, or 15 more complex combinational functions such as decoders or simple mathematical 16 functions. In most FPGAs, the logic blocks also include memory elements, which may be 17 simple flip-flops or more complete blocks of memory. In some circumstances, the PT 18 may be developed on regular FPGAs and then migrated into a fixed version that more 19 resembles ASIC implementations. Alternate or coordinating implementations may 20 migrate PT controller features to a final ASIC instead of or in addition to FPGAs. 21 Depending on the implementation all of the aforementioned embedded components and 22 microprocessors may be considered the "CPU" and/or "processor" for the PT.
WO 2011/153505 PCT/US2011/039178 50 1 Power Source 2 [0072] The power source 886 may be of any standard form for powering small 3 electronic circuit board devices such as the following power cells: alkaline, lithium 4 hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. 5 Other types of AC or DC power sources may be used as well. In the case of solar cells, in 6 one embodiment, the case provides an aperture through which the solar cell may 7 capture photonic energy. The power cell 886 is connected to at least one of the 8 interconnected subsequent components of the PT thereby providing an electric current 9 to all subsequent components. In one example, the power source 886 is connected to the 1o system bus component 804. In an alternative embodiment, an outside power source 11 886 is provided through a connection across the I/O 8o8 interface. For example, a USB 12 and/or IEEE 1394 connection carries both data and power across the connection and is 13 therefore a suitable source of power. 14 Interface Adapters 15 [00731 Interface bus(ses) 807 may accept, connect, and/or communicate to a 16 number of interface adapters, conventionally although not necessarily in the form of 17 adapter cards, such as but not limited to: input output interfaces (I/0) 8o8, storage 18 interfaces 809, network interfaces 81o, and/or the like. Optionally, cryptographic 19 processor interfaces 827 similarly may be connected to the interface bus. The interface 20 bus provides for the communications of interface adapters with one another as well as 21 with other components of the computer systemization. Interface adapters are adapted 22 for a compatible interface bus. Interface adapters conventionally connect to the 23 interface bus via a slot architecture. Conventional slot architectures may be employed, WO 2011/153505 PCT/US2011/039178 51 1 such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) 2 Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, 3 Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal 4 Computer Memory Card International Association (PCMCIA), and/or the like. 5 [0074] Storage interfaces 809 may accept, communicate, and/or connect to a 6 number of storage devices such as, but not limited to: storage devices 814, removable 7 disc devices, and/or the like. Storage interfaces may employ connection protocols such 8 as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet 9 Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), 1o Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small 11 Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like. 12 [0075] Network interfaces 81o may accept, communicate, and/or connect to a 13 communications network 813. Through a communications network 813, the PT 14 controller is accessible through remote clients 833b (e.g., computers with web browsers) 15 by users 833a. Network interfaces may employ connection protocols such as, but not 16 limited to: direct connect, Ethernet (thick, thin, twisted pair 1o/ioo/1ooo Base T, 17 and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the 18 like. Should processing requirements dictate a greater amount speed and/or capacity, 19 distributed network controllers (e.g., Distributed PT), architectures may similarly be 20 employed to pool, load balance, and/or otherwise increase the communicative 21 bandwidth required by the PT controller. A communications network may be any one 22 and/or the combination of the following: a direct interconnection; the Internet; a Local 23 Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as WO 2011/153505 PCT/US2011/039178 52 1 Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network 2 (WAN); a wireless network (e.g., employing protocols such as, but not limited to a 3 Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A 4 network interface may be regarded as a specialized form of an input output interface. 5 Further, multiple network interfaces 810 may be used to engage with various 6 communications network types 813. For example, multiple network interfaces may be 7 employed to allow for the communication over broadcast, multicast, and/or unicast 8 networks. 9 [0076] Input Output interfaces (I/O) 808 may accept, communicate, and/or 10 connect to user input devices 811, peripheral devices 812, cryptographic processor 11 devices 828, and/or the like. I/O may employ connection protocols such as, but not 12 limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple 13 Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; 14 keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop 15 Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface 16 (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, 17 and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code 18 division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed 19 downlink packet access (HSDPA), global system for mobile communications (GSM), 20 long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may 21 include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid 22 Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) 23 that accepts signals from a video interface, may be used. The video interface composites 24 information generated by a computer systemization and generates video signals based WO 2011/153505 PCT/US2011/039178 53 1 on the composited information in a video memory frame. Another output device is a 2 television set, which accepts signals from a video interface. Typically, the video interface 3 provides the composited video information through a video connection interface that 4 accepts a video display interface (e.g., an RCA composite video connector accepting an 5 RCA composite video cable; a DVI connector accepting a DVI display cable, etc.). 6 [0077] User input devices 811 often are a type of peripheral device 812 (see below) 7 and may include: card readers, dongles, finger print readers, gloves, graphics tablets, 8 joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch 9 screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., 10 accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the 11 like. 12 [0078] Peripheral devices 812 may be connected and/or communicate to I/O 13 and/or other facilities of the like such as network interfaces, storage interfaces, directly 14 to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be 15 external, internal and/or part of the PT controller. Peripheral devices may include: 16 antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), 17 cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring 18 secure transactions with a digital signature, and/or the like), external processors (for 19 added capabilities; e.g., crypto devices 828), force-feedback devices (e.g., vibrating 20 motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., 21 cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, 22 and/or the like. Peripheral devices often include types of input devices (e.g., cameras).
WO 2011/153505 PCT/US2011/039178 54 1 [o 079] It should be noted that although user input devices and peripheral devices 2 may be employed, the PT controller may be embodied as an embedded, dedicated, 3 and/or monitor-less (i.e., headless) device, wherein access would be provided over a 4 network interface connection. 5 [0080] Cryptographic units such as, but not limited to, microcontrollers, 6 processors 826, interfaces 827, and/or devices 828 may be attached, and/or 7 communicate with the PT controller. A MC68HC16 microcontroller, manufactured by 8 Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 9 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz 1o configuration and requires less than one second to perform a 512-bit RSA private key 11 operation. Cryptographic units support the authentication of communications from 12 interacting agents, as well as allowing for anonymous transactions. Cryptographic units 13 may also be configured as part of CPU. Equivalent microcontrollers and/or processors 14 may also be used. Other commercially available specialized cryptographic processors 15 include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, 16 SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz 17 Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, 18 Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, 19 which is capable of performing 500+ MB/s of cryptographic instructions; VLSI 20 Technology's 33 MHz 6868; and/or the like. 21 Memory 22 [o081] Generally, any mechanization and/or embodiment allowing a processor to 23 affect the storage and/or retrieval of information is regarded as memory 829. However, WO 2011/153505 PCT/US2011/039178 55 1 memory is a fungible technology and resource, thus, any number of memory 2 embodiments may be employed in lieu of or in concert with one another. It is to be 3 understood that the PT controller and/or a computer systemization may employ various 4 forms of memory 829. For example, a computer systemization may be configured 5 wherein the functionality of on-chip CPU memory (e.g., registers), RAM, ROM, and any 6 other storage devices are provided by a paper punch tape or paper punch card 7 mechanism; of course such an embodiment would result in an extremely slow rate of 8 operation. In a typical configuration, memory 829 will include ROM 806, RAM 805, 9 and a storage device 814. A storage device 814 may be any conventional computer 10 system storage. Storage devices may include a drum; a (fixed and/or removable) 11 magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD 12 ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an 13 array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state 14 memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable 15 storage mediums; and/or other devices of the like. Thus, a computer systemization 16 generally requires and makes use of memory. 17 Component Collection 18 [0082] The memory 829 may contain a collection of program and/or database 19 components and/or data such as, but not limited to: operating system component(s) 815 20 (operating system); information server component(s) 816 (information server); user 21 interface components) 817 (user interface); Web browser component(s) 818 (Web 22 browser); database(s) 819; mail server component(s) 821; mail client component(s) 23 822; cryptographic server component(s) 820 (cryptographic server); the PT WO 2011/153505 PCT/US2011/039178 56 1 component(s) 835; and/or the like (i.e., collectively a component collection). These 2 components may be stored and accessed from the storage devices and/or from storage 3 devices accessible through an interface bus. Although non-conventional program 4 components such as those in the component collection, typically, are stored in a local 5 storage device 814, they may also be loaded and/or stored in memory such as: 6 peripheral devices, RAM, remote storage facilities through a communications network, 7 ROM, various forms of memory, and/or the like. 8 Operating System 9 [00831 The operating system component 815 is an executable program 10 component facilitating the operation of the PT controller. Typically, the operating 11 system facilitates access of I/O, network interfaces, peripheral devices, storage devices, 12 and/or the like. The operating system may be a highly fault tolerant, scalable, and 13 secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and 14 Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution 15 (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux 16 distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating 17 systems. However, more limited and/or less secure operating systems also may be 18 employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 19 20oo/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like. 20 An operating system may communicate to and/or with other components in a 21 component collection, including itself, and/or the like. Most frequently, the operating 22 system communicates with other program components, user interfaces, and/or the like. 23 For example, the operating system may contain, communicate, generate, obtain, and/or WO 2011/153505 PCT/US2011/039178 57 1 provide program component, system, user, and/or data communications, requests, 2 and/or responses. The operating system, once executed by the CPU, may enable the 3 interaction with communications networks, data, I/0, peripheral devices, program 4 components, memory, user input devices, and/or the like. The operating system may 5 provide communications protocols that allow the PT controller to communicate with 6 other entities through a communications network 813. Various communication 7 protocols may be used by the PT controller as a subcarrier transport mechanism for 8 interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the 9 like. 10 Information Server 11 [0084] An information server component 816 is a stored program component that 12 is executed by a CPU. The information server may be a conventional Internet 13 information server such as, but not limited to Apache Software Foundation's Apache, 14 Microsoft's Internet Information Server, and/or the like. The information server may 15 allow for the execution of program components through facilities such as Active Server 16 Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway 17 Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, 18 JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor 19 (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. 20 The information server may support secure communications protocols such as, but not 21 limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure 22 Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols 23 (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), WO 2011/153505 PCT/US2011/039178 58 1 ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence 2 and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) 3 Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging 4 Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol 5 (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and 6 Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The 7 information server provides results in the form of Web pages to Web browsers, and 8 allows for the manipulated generation of the Web pages through interaction with other 9 program components. After a Domain Name System (DNS) resolution portion of an 10 HTTP request is resolved to a particular information server, the information server 11 resolves requests for information at specified locations on the PT controller based on the 12 remainder of the HTTP request. For example, a request such as 13 http://123.124.125.126/myInformation.html might have the IP portion of the request 14 "123.124.125.126" resolved by a DNS server to an information server at that IP address; 1s that information server might in turn further parse the http request for the 16 "/myInformation.html" portion of the request and resolve it to a location in memory 17 containing the information "myInformation.html." Additionally, other information 18 serving protocols may be employed across various ports, e.g., FTP communications 19 across port 21, and/or the like. An information server may communicate to and/or with 20 other components in a component collection, including itself, and/or facilities of the 21 like. Most frequently, the information server communicates with the PT database 819, 22 operating systems, other program components, user interfaces, Web browsers, and/or 23 the like.
WO 2011/153505 PCT/US2011/039178 59 1 [o 085] Access to the PT database may be achieved through a number of database 2 bridge mechanisms such as through scripting languages as enumerated below (e.g., 3 CGI) and through inter-application communication channels as enumerated below (e.g., 4 CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed 5 through the bridge mechanism into appropriate grammars as required by the PT. In one 6 embodiment, the information server would provide a Web form accessible by a Web 7 browser. Entries made into supplied fields in the Web form are tagged as having been 8 entered into the particular fields, and parsed as such. The entered terms are then passed 9 along with the field tags, which act to instruct the parser to generate queries directed to 10 appropriate tables and/or fields. In one embodiment, the parser may generate queries in 11 standard SQL by instantiating a search string with the proper join/select commands 12 based on the tagged text entries, wherein the resulting command is provided over the 13 bridge mechanism to the PT as a query. Upon generating query results from the query, 14 the results are passed over the bridge mechanism, and may be parsed for formatting and 15 generation of a new results Web page by the bridge mechanism. Such a new results Web 16 page is then provided to the information server, which may supply it to the requesting 17 Web browser. 18 [o086] Also, an information server may contain, communicate, generate, obtain, 19 and/or provide program component, system, user, and/or data communications, 20 requests, and/or responses. 21 User Interface 22 [o087] Computer interfaces in some respects are similar to automobile operation 23 interfaces. Automobile operation interface elements such as steering wheels, gearshifts, WO 2011/153505 PCT/US2011/039178 60 1 and speedometers facilitate the access, operation, and display of automobile resources, 2 and status. Computer interaction interface elements such as check boxes, cursors, 3 menus, scrollers, and windows (collectively and commonly referred to as widgets) 4 similarly facilitate the access, capabilities, operation, and display of data and computer 5 hardware and operating system resources, and status. Operation interfaces are 6 commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple 7 Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 8 2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows 9 (e.g., which may include additional Unix graphic interface libraries and layers such as K 10 Desktop Environment (KDE), mythTV and GNU Network Object Model Environment 11 (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, 12 JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), 13 MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which 14 may be used and) provide a baseline and means of accessing and displaying information 15 graphically to users. 16 [o088] A user interface component 817 is a stored program component that is 17 executed by a CPU. The user interface may be a conventional graphic user interface as 18 provided by, with, and/or atop operating systems and/or operating environments such 19 as already discussed. The user interface may allow for the display, execution, 20 interaction, manipulation, and/or operation of program components and/or system 21 facilities through textual and/or graphical facilities. The user interface provides a facility 22 through which users may affect, interact, and/or operate a computer system. A user 23 interface may communicate to and/or with other components in a component 24 collection, including itself, and/or facilities of the like. Most frequently, the user WO 2011/153505 PCT/US2011/039178 61 1 interface communicates with operating systems, other program components, and/or the 2 like. The user interface may contain, communicate, generate, obtain, and/or provide 3 program component, system, user, and/or data communications, requests, and/or 4 responses. 5 Web Browser 6 [o089] A Web browser component 818 is a stored program component that is 7 executed by a CPU. The Web browser may be a conventional hypertext viewing 8 application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web 9 browsing may be supplied with 128bit (or greater) encryption by way of HTTPS, SSL, 10 and/or the like. Web browsers allowing for the execution of program components 11 through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web 12 browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the 13 like. Web browsers and like information access tools may be integrated into PDAs, 14 cellular telephones, and/or other mobile devices. A Web browser may communicate to 15 and/or with other components in a component collection, including itself, and/or 16 facilities of the like. Most frequently, the Web browser communicates with information 17 servers, operating systems, integrated program components (e.g., plug-ins), and/or the 18 like; e.g., it may contain, communicate, generate, obtain, and/or provide program 19 component, system, user, and/or data communications, requests, and/or responses. Of 20 course, in place of a Web browser and information server, a combined application may 21 be developed to perform similar functions of both. The combined application would 22 similarly affect the obtaining and the provision of information to users, user agents, WO 2011/153505 PCT/US2011/039178 62 1 and/or the like from the PT enabled nodes. The combined application may be nugatory 2 on systems employing standard Web browsers. 3 Mail Server 4 [o09o] A mail server component 821 is a stored program component that is 5 executed by a CPU 803. The mail server may be a conventional Internet mail server such 6 as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server 7 may allow for the execution of program components through facilities such as ASP, 8 ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, 9 PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support 10 communications protocols such as, but not limited to: Internet message access protocol 11 (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, 12 post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The 13 mail server can route, forward, and process incoming and outgoing mail messages that 14 have been sent, relayed and/or otherwise traversing through and/or to the PT. 15 [0091] Access to the PT mail may be achieved through a number of APIs offered 16 by the individual Web server components and/or the operating system. 17 [0092] Also, a mail server may contain, communicate, generate, obtain, and/or 18 provide program component, system, user, and/or data communications, requests, 19 information, and/or responses. 20 Mail Client 21 [0093] A mail client component 822 is a stored program component that is 22 executed by a CPU 803. The mail client may be a conventional mail viewing application WO 2011/153505 PCT/US2011/039178 63 1 such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook 2 Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of 3 transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A 4 mail client may communicate to and/or with other components in a component 5 collection, including itself, and/or facilities of the like. Most frequently, the mail client 6 communicates with mail servers, operating systems, other mail clients, and/or the like; 7 e.g., it may contain, communicate, generate, obtain, and/or provide program 8 component, system, user, and/or data communications, requests, information, and/or 9 responses. Generally, the mail client provides a facility to compose and transmit 10 electronic mail messages. 11 Cryptographic Server 12 [0094] A cryptographic server component 820 is a stored program component 13 that is executed by a CPU 803, cryptographic processor 826, cryptographic processor 14 interface 827, cryptographic processor device 828, and/or the like. Cryptographic 15 processor interfaces will allow for expedition of encryption and/or decryption requests 16 by the cryptographic component; however, the cryptographic component, alternatively, 17 may run on a conventional CPU. The cryptographic component allows for the 18 encryption and/or decryption of provided data. The cryptographic component allows for 19 both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or 20 decryption. The cryptographic component may employ cryptographic techniques such 21 as, but not limited to: digital certificates (e.g., X.5o9 authentication framework), digital 22 signatures, dual signatures, enveloping, password access protection, public key 23 management, and/or the like. The cryptographic component will facilitate numerous WO 2011/153505 PCT/US2011/039178 64 1 (encryption and/or decryption) security protocols such as, but not limited to: checksum, 2 Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data 3 Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash 4 function), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet 5 encryption and authentication system that uses an algorithm developed in 1977 by Ron 6 Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure 7 Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTIPS), and/or the like. 8 Employing such encryption security protocols, the PT may encrypt all incoming and/or 9 outgoing communications and may serve as node within a virtual private network (VPN) 10 with a wider communications network. The cryptographic component facilitates the 11 process of "security authorization" whereby access to a resource is inhibited by a 12 security protocol wherein the cryptographic component effects authorized access to the 13 secured resource. In addition, the cryptographic component may provide unique 14 identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an 15 digital audio file. A cryptographic component may communicate to and/or with other 16 components in a component collection, including itself, and/or facilities of the like. The 17 cryptographic component supports encryption schemes allowing for the secure 18 transmission of information across a communications network to enable the PT 19 component to engage in secure transactions if so desired. The cryptographic component 20 facilitates the secure accessing of resources on the PT and facilitates the access of 21 secured resources on remote systems; i.e., it may act as a client and/or server of secured 22 resources. Most frequently, the cryptographic component communicates with 23 information servers, operating systems, other program components, and/or the like. 24 The cryptographic component may contain, communicate, generate, obtain, and/or WO 2011/153505 PCT/US2011/039178 65 1 provide program component, system, user, and/or data communications, requests, 2 and/or responses. 3 The PT Database 4 [o095] The PT database component 819 may be embodied in a database and its 5 stored data. The database is a stored program component, which is executed by the 6 CPU; the stored program component portion configuring the CPU to process the stored 7 data. The database may be a conventional, fault tolerant, relational, scalable, secure 8 database such as Oracle or Sybase. Relational databases are an extension of a flat file. 9 Relational databases consist of a series of related tables. The tables are interconnected 10 via a key field. Use of the key field allows the combination of the tables by indexing 11 against the key field; i.e., the key fields act as dimensional pivot points for combining 12 information from various tables. Relationships generally identify links maintained 13 between tables by matching primary keys. Primary keys represent fields that uniquely 14 identify the rows of a table in a relational database. More precisely, they uniquely 15 identify rows of a table on the "one" side of a one-to-many relationship. 16 [00961 Alternatively, the PT database may be implemented using various 17 standard data-structures, such as an array, hash, (linked) list, struct, structured text file 18 (e.g., XML), table, and/or the like. Such data-structures may be stored in memory 19 and/or in (structured) files. In another alternative, an object-oriented database may be 20 used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can 21 include a number of object collections that are grouped and/or linked together by 22 common attributes; they may be related to other object collections by some common 23 attributes. Object-oriented databases perform similarly to relational databases with the WO 2011/153505 PCT/US2011/039178 66 1 exception that objects are not just pieces of data but may have other types of 2 functionality encapsulated within a given object. If the PT database is implemented as a 3 data-structure, the use of the PT database 819 may be integrated into another 4 component such as the PT component 835. Also, the database may be implemented as a 5 mix of data structures, objects, and relational structures. Databases may be consolidated 6 and/or distributed in countless variations through standard data processing techniques. 7 Portions of databases, e.g., tables, may be exported and/or imported and thus 8 decentralized and/or integrated. 9 [0097] In one embodiment, the database component 819 includes several tables 10 819a-k. A Users table 819a may include fields such as, but not limited to: userid, ssn, 11 dob, firstname, lastname, age, state, addressfirstline, addresssecondline, zipcode, 12 deviceslist, contactinfo, contact-type, altcontactinfo, altcontact-type, and/or the 13 like. The Users table may support and/or track multiple entity accounts on a PT. A 14 Clients table 819b may include fields such as, but not limited to: userid, clientid, 15 client ip, clientjtype, client_model, operating-system, os version, app-installed flag, 16 and/or the like. An Apps table 819c may include fields such as, but not limited to: 17 appID, app-name, app type, OS-compatibilities list, version, timestamp, 18 developerID, and/or the like. A Merchants table 819d may include fields such as, but 19 not limited to: merchantid, merchantname, provi merchantaddress, ip-address, 20 mac_address, authkey, port num, securitysettings-list, and/or the like. An Issuers 21 table 819e may include fields such as, but not limited to: issuerid, issuername, 22 issueraddress, ip-address, macaddress, authkey, portnum, security-settings list, 23 and/or the like. An Acquirers table 819f may include fields such as, but not limited to: 24 accountfirstname, accountlastname, account type, accountnum, account_ WO 2011/153505 PCT/US2011/039178 67 1 balancelist, billingaddress_ line, billingaddress_ line2, billing-zipcode, billing-state, 2 shipping-preferences, shippingaddressline1, shippingaddressline2, shipping_ 3 zipcode, shipping-state, and/or the like. A Tokens table 819g may include fields such as, 4 but not limited to: tokenid, token-phrase, token-issuer, tokenmd5, token-security, 5 userid, password, tokencompositionlist, accountlink, and/or the like. A 6 Transactions table 819h may include fields such as, but not limited to: orderid, 7 userid, timestamp, transaction-cost, purchase detailslist, numproducts, products 8 list, product-type, product-params _list, producttitle, product-summary, quantity, 9 userid, clientid, client ip, client-type, clientmodel, operatingsystem, osversion, 10 app-installed flag, userid, accountfirstname, accountlastname, account type, 11 accountnum, billingaddress_ line, billingaddressline2, billing_ zipcode, 12 billing-state, shipping-preferences, shippingaddresslinei, shippingaddress_ line2, 13 shipping-zipcode, shipping-state, merchantid, merchantname, merchantauth_ 14 key, and/or the like. A Batches table 819i may include fields such as, but not limited to: 15 batchid, transactionidlist, timestamp-list, clearedflaglist, clearance trigger 16 settings, and/or the like. An Arbitrators table 819j may include fields such as, but not 17 limited to: arbitratorid, arbitratorname, arbitrator geo, arbitratorIP, arbitrator_ 18 URL, merchantservicelist, and/or the like. A Payment Ledgers table 819k may 19 include fields such as, but not limited to: requestid, timestamp, deposit-amount, 20 batchid, transaction id, clear-flag, deposit account, transactionsummary, payor 21 name, payor account, and/or the like. 22 [o098] In one embodiment, the PT database may interact with other database 23 systems. For example, employing a distributed database system, queries and data access WO 2011/153505 PCT/US2011/039178 68 1 by search PT component may treat the combination of the PT database, an integrated 2 data security layer database as a single database entity. 3 [0099] In one embodiment, user programs may contain various user interface 4 primitives, which may serve to update the PT. Also, various accounts may require 5 custom database tables depending upon the environments and the types of clients the 6 PT may need to serve. It should be noted that any unique fields may be designated as a 7 key field throughout. In an alternative embodiment, these tables have been 8 decentralized into their own databases and their respective database controllers (i.e., 9 individual database controllers for each of the above tables). Employing standard data 10 processing techniques, one may further distribute the databases over several computer 11 systemizations and/or storage devices. Similarly, configurations of the decentralized 12 database controllers may be varied by consolidating and/or distributing the various 13 database components 819a-k. The PT may be configured to keep track of various 14 settings, inputs, and parameters via database controllers. 15 [o 010 o] The PT database may communicate to and/or with other components in a 16 component collection, including itself, and/or facilities of the like. Most frequently, the 17 PT database communicates with the PT component, other program components, and/or 18 the like. The database may contain, retain, and provide information regarding other 19 nodes and data. 20 The PTs 21 [o0101] The PT component 835 is a stored program component that is executed by 22 a CPU. In one embodiment, the PT component incorporates any and/or all 23 combinations of the aspects of the PT discussed in the previous figures. As such, the PT WO 2011/153505 PCT/US2011/039178 69 1 affects accessing, obtaining and the provision of information, services, transactions, 2 and/or the like across various communications networks. 3 [o0102] The PT component may transform payment token-based purchase orders 4 via PT components into multi-issuer purchase payment funds transfers, and/or the like 5 and use of the PT. In one embodiment, the PT component 835 takes inputs (e.g., 6 purchase input 411, token arbitrator address 416, token creation input 423, purchase 7 input 611, token arbitrator address 616, issuer data response 620, payment option input 8 626, issuer server data 636, user data 64oa-n, batch data 655, issuer server data 663, 9 and/or the like) etc., and transforms the inputs via various components (e.g., TPE 841, 10 tPTE 842, and/or the like), into outputs (e.g., tokenization invitation 420, token data 11 426, token authentication confirmation 622a, issuer data update 629, "authorization in 12 progress" message 630-31, token data 634, authorization fail message 644, transaction 13 data 645, authorization response 642a-n, authorization success message 646-47, batch 14 append data 649, purchase receipt 650, transaction data 661, funds transfer message 15 668-69, and/or the like). 16 [00103] The PT component enabling access of information between nodes may be 17 developed by employing standard development tools and languages such as, but not 18 limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) 19 (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, 20 mapping tools, procedural and object oriented development tools, PERL, PHP, Python, 21 shell scripts, SQL commands, web application server extensions, web development 22 environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; 23 AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; WO 2011/153505 PCT/US2011/039178 70 1 script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User 2 Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the PT 3 server employs a cryptographic server to encrypt and decrypt communications. The PT 4 component may communicate to and/or with other components in a component 5 collection, including itself, and/or facilities of the like. Most frequently, the PT 6 component communicates with the PT database, operating systems, other program 7 components, and/or the like. The PT may contain, communicate, generate, obtain, 8 and/or provide program component, system, user, and/or data communications, 9 requests, and/or responses. 10 Distributed PTs 11 [00104] The structure and/or operation of any of the PT node controller 12 components may be combined, consolidated, and/or distributed in any number of ways 13 to facilitate development and/or deployment. Similarly, the component collection may 14 be combined in any number of ways to facilitate deployment and/or development. To 15 accomplish this, one may integrate the components into a common code base or in a 16 facility that can dynamically load the components on demand in an integrated fashion. 17 [00105] The component collection may be consolidated and/or distributed in 18 countless variations through standard data processing and/or development techniques. 19 Multiple instances of any one of the program components in the program component 20 collection may be instantiated on a single node, and/or across numerous nodes to 21 improve performance through load-balancing and/or data-processing techniques. 22 Furthermore, single instances may also be distributed across multiple controllers 23 and/or storage devices; e.g., databases. All program component instances and WO 2011/153505 PCT/US2011/039178 71 1 controllers working in concert may do so through standard data processing 2 communication techniques. 3 [o0106] The configuration of the PT controller will depend on the context of 4 system deployment. Factors such as, but not limited to, the budget, capacity, location, 5 and/or use of the underlying hardware resources may affect deployment requirements 6 and configuration. Regardless of if the configuration results in more consolidated 7 and/or integrated program components, results in a more distributed series of program 8 components, and/or results in some combination between a consolidated and 9 distributed configuration, data may be communicated, obtained, and/or provided. 10 Instances of components consolidated into a common code base from the program 11 component collection may communicate, obtain, and/or provide data. This may be 12 accomplished through intra-application data processing communication techniques 13 such as, but not limited to: data referencing (e.g., pointers), internal messaging, object 14 instance variable communication, shared memory space, variable passing, and/or the 15 like. 16[00107] If component collection components are discrete, separate, and/or 17 external to one another, then communicating, obtaining, and/or providing data with 18 and/or to other component components may be accomplished through inter-application 19 data processing communication techniques such as, but not limited to: Application 20 Program Interfaces (API) information passage; (distributed) Component Object Model 21 ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), 22 Common Object Request Broker Architecture (CORBA), Jini local and remote 23 application program interfaces, JavaScript Object Notation (JSON), Remote Method WO 2011/153505 PCT/US2011/039178 72 1 Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent 2 between discrete component components for inter-application communication or within 3 memory spaces of a singular component for intra-application communication may be 4 facilitated through the creation and parsing of a grammar. A grammar may be 5 developed by using development tools such as lex, yacc, XML, and/or the like, which 6 allow for grammar generation and parsing capabilities, which in turn may form the basis 7 of communication messages within and between components. 8 [o 0108] For example, a grammar may be arranged to recognize the tokens of an 9 HTTP post command, e.g.: 10 w3c -post http://... Valuel 11 12 [00109] where Value1 is discerned as being a parameter because "http://" is part of 13 the grammar syntax, and what follows is considered part of the post value. Similarly, 14 with such a grammar, a variable "Valuei" may be inserted into an "http://" post 15 command and then sent. The grammar syntax itself may be presented as structured data 16 that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a 17 syntax description text file as processed by lex, yacc, etc.). Also, once the parsing 18 mechanism is generated and/or instantiated, it itself may process and/or parse 19 structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, 20 structured text streams, XML, and/or the like structured data. In another embodiment, 21 inter-application data processing protocols themselves may have integrated and/or 22 readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed 23 to parse (e.g., communications) data. Further, the parsing grammar may be used 24 beyond message parsing, but may also be used to parse: databases, data collections, data WO 2011/153505 PCT/US2011/039178 73 1 stores, structured data, and/or the like. Again, the desired configuration will depend 2 upon the context, environment, and requirements of system deployment. 3 [o0110] For example, in some implementations, the PT controller may be 4 executing a PHP script implementing a Secure Sockets Layer ("SSL") socket server via 5 the information server, which listens to incoming communications on a server port to 6 which a client may send data, e.g., data encoded in JSON format. Upon identifying an 7 incoming communication, the PHP script may read the incoming message from the 8 client device, parse the received JSON-encoded text data to extract information from the 9 JSON-encoded text data into PHP script variables, and store the data (e.g., client 10 identifying information, etc.) and/or extracted information in a relational database 11 accessible using the Structured Query Language ("SQL"). An exemplary listing, written 12 substantially in the form of PHP/SQL commands, to accept JSON-encoded input data 13 from a client device via a SSL connection, parse the data to extract variables, and store 14 the data to a database, is provided below: 15 <?PHP 16 header('Content-Type: text/plain'); 17 18 // set ip address and port to listen to for incoming data 19 $address = '192.168.0.100'; 20 $port = 255; 21 22 // create a server-side SSL socket, listen for/accept incoming communication 23 $sock = socketcreate(AF_IINET, SOCKSTREAM, 0); 24 socketbind($sock, $address, $port) or die('Could not bind to address'); 25 socketlisten($sock); 26 $client = socketaccept($sock); 27 28 // read input data from client device in 1024 byte blocks until end of message 29 do { 30 $input = 31 $input = socketread($client, 1024); 32 $data .= $input; 33 } while($input 34 35 // parse data to extract variables 36 $obj = json-decode($data, true); 37 38 // store input data in a database WO 2011/153505 PCT/US2011/039178 74 1 mysql connect("201.408.185.132",$DBserver,$password) ; // access database server 2 mysql select("CLIENT_DB.SQL"); // select database to append 3 mysql query("INSERT INTO UserTable (transmission) 4 VALUES ($data)"); // add data to UserTable table in a CLIENT database 5 mysql-close("CLIEIT_DB.SQL"); // close connection to database 6 ?> 7 8 [o0111] Also, the following resources may be used to provide example 9 embodiments regarding SOAP parser implementation: 10 http://www.xav.com/perl /site/lib/SOAP/Parser.html 11 http://publib.boulder.ibm.com/infocenter/tivihelp/v2rl/index.jsp?topic=/com.ibm 12 .IBMDI.doc/referenceguide295.htm 13 14 [00112] and other parser implementations: 15 http://publib.boulder.ibm.com/infocenter/tivihelp/v2rl/index.jsp?topic=/com.ibm 16 .IBMDI.doc/referenceguide259.htm 17 18 [00113] all of which are hereby expressly incorporated by reference. 19 [00114] Non-limiting exemplary embodiments highlighting numerous further 20 advantageous aspects include: WO 2011/153505 PCT/US2011/039178 75 1 Al. A payment tokenization enrollment processor-implemented method 2 embodiment, comprising: 3 obtaining a purchase order from a client device of a user; 4 extracting purchase payment information from the purchase order 5 message; 6 determining via a processor that the user is not enrolled for payment 7 tokenization services based on the purchase payment information; 8 generating a tokenization invitation request; and 9 providing the tokenization invitation request to a token arbitration server. 10 11 A2. The method of embodiment A1, further comprising: 12 determining an address for the token arbitration server based on the 13 purchase payment information. 14 1s A3. The method of embodiment A2, wherein the address for the token arbitration 16 server is determined by querying a database using data extracted from the purchase 17 payment information. 18 19 A4. The method of embodiment A3, wherein the data extracted from the 20 purchase payment information includes a portion of a user card account number. 21 22 A5. The method of embodiment Ai, wherein the client device is a mobile device. 23 WO 2011/153505 PCT/US2011/039178 76 1 A6. The method of embodiment Ai, wherein the tokenization invitation request 2 includes the purchase payment information. 3 4 A7. The method of embodiment Al, wherein the token arbitration server is 5 included within a payment network. 6 7 A8. A payment tokenization enrollment means, comprising: 8 means for obtaining a purchase order from a client device of a user; 9 means for extracting purchase payment information from the purchase 10 order message; 11 means for determining that the user is not enrolled for payment 12 tokenization services based on the purchase payment information; 13 means for generating a tokenization invitation request; and 14 means for providing the tokenization invitation request to a token 1s arbitration server. 16 17 A9. The means of embodiment A8, further comprising: 18 means for determining an address for the token arbitration server based 19 on the purchase payment information. 20 21 Aio. The means of embodiment A9, wherein the address for the token arbitration 22 server is determined by querying a database using data extracted from the purchase 23 payment information. 24 WO 2011/153505 PCT/US2011/039178 77 1 A11. The means of embodiment Aio, wherein the data extracted from the 2 purchase payment information includes a portion of a user card account number. 3 4 A12. The means of embodiment A8, wherein the client device is a mobile device. 5 6 A13. The means of embodiment A8, wherein the tokenization invitation request 7 includes the purchase payment information. 8 9 A14. The means of embodiment A8, wherein the token arbitration server is 1o included within a payment network. 11 12 A15. A payment tokenization enrollment system embodiment, comprising: 13 a processor; and 14 a memory disposed in communication with the processor and storing processor 15 executable instructions to: 16 obtain a purchase order from a client device of a user; 17 extract purchase payment information from the purchase order message; 18 determine that the user is not enrolled for payment tokenization services 19 based on the purchase payment information; 20 generate a tokenization invitation request; and 21 provide the tokenization invitation request to a token arbitration server. 22 23 A16. The system of embodiment A15, the memory further storing instructions to: WO 2011/153505 PCT/US2011/039178 78 1 determine an address for the token arbitration server based on the 2 purchase payment information. 3 4 A17. The system of embodiment A16, wherein the address for the token 5 arbitration server is determined by querying a database using data extracted from the 6 purchase payment information. 7 8 A18. The system of embodiment A17, wherein the data extracted from the 9 purchase payment information includes a portion of a user card account number. 10 11 A19. The system of embodiment A15, wherein the client device is a mobile device. 12 13 A2o. The system of embodiment A15, wherein the tokenization invitation request 14 includes the purchase payment information. 15 16 A21. The system of embodiment A15, wherein the token arbitration server is 17 included within a payment network. 18 19 A22. A processor-readable tangible medium embodiment storing processor 20 executable payment tokenization enrollment instructions to: 21 obtain a purchase order from a client device of a user; 22 extract purchase payment information from the purchase order message; 23 determine that the user is not enrolled for payment tokenization services 24 based on the purchase payment information; WO 2011/153505 PCT/US2011/039178 79 1 generate a tokenization invitation request; and 2 provide the tokenization invitation request to a token arbitration server. 3 4 A23. The medium of embodiment A22, further storing instructions to: 5 determine an address for the token arbitration server based on the 6 purchase payment information. 7 8 A24. The medium of embodiment A23, wherein the address for the token 9 arbitration server is determined by querying a database using data extracted from the 1o purchase payment information. 11 12 A25. The medium of embodiment A24, wherein the data extracted from the 13 purchase payment information includes a portion of a user card account number. 14 15 A26. The medium of embodiment A22, wherein the client device is a mobile 16 device. 17 18 A27. The medium of embodiment A22, wherein the tokenization invitation 19 request includes the purchase payment information. 20 21 A28. The medium of embodiment A22, wherein the token arbitration server is 22 included within a payment network. 23 WO 2011/153505 PCT/US2011/039178 80 1 Bi. A tokenized payment purchasing processor-implemented method 2 embodiment, comprising: 3 obtaining purchase input from a user into a mobile device; 4 identifying a unique source-neutral universally-resolvable payment token 5 to utilize in lieu of user financial payment information; 6 generating a tokenized purchase order using the purchase input and the 7 payment token; and 8 providing the tokenized purchase order for processing. 9 10 B2. The method of embodiment Bi, further comprising: 11 obtaining an indication to verify user authentication for processing 12 tokenized purchase order; 13 generating a user authentication response via device fingerprinting using a 14 hardware authentication chip embedded in the mobile device; 15 providing the user authentication response; and 16 obtaining an indication of user authentication for processing the tokenized 17 purchase order. 18 19 B3. The method of embodiment Bi, wherein the payment token is associated with 20 a plurality of user issuer accounts. 21 22 B4. The method of embodiment B3, wherein at least one of the user issuer 23 accounts is a stored value account. 24 WO 2011/153505 PCT/US2011/039178 81 1 B5. The method of embodiment B3, wherein at least one of the user issuer 2 accounts is another payment token. 3 4 B6. The method of embodiment Bi, further comprising: 5 obtaining a payment options request including a list of user issue accounts 6 to utilize for processing the tokenized purchase order, after providing the tokenized 7 purchase order for processing; 8 obtaining a user selection of at least one of the user issuer accounts to 9 utilize for processing the tokenized purchase order; and 10 providing the user selection for processing the tokenized purchase order. 11 12 B7. The method of embodiment B6, further comprising: 13 obtaining a user selection of at least another of the user issuer accounts, as 14 well as a user indication of purchase amounts to be charged to the user-selected user 15 issuer accounts; and 16 providing the user selection of the user issuer accounts and the indication 17 of the purchase amounts to be charged to the user-selected user issuer accounts. 18 19 B8. A tokenized payment purchasing means, comprising: 20 means for obtaining purchase input from a user into a mobile device; 21 means for identifying a unique source-neutral universally-resolvable 22 payment token to utilize in lieu of user financial payment information; 23 means for generating a tokenized purchase order using the purchase input 24 and the payment token; and WO 2011/153505 PCT/US2011/039178 82 1 means for providing the tokenized purchase order for processing. 2 3 B9. The means of embodiment B8, further comprising: 4 means for obtaining an indication to verify user authentication for 5 processing tokenized purchase order; 6 means for generating a user authentication response via device 7 fingerprinting using a hardware authentication chip embedded in the mobile device; 8 means for providing the user authentication response; and 9 means for obtaining an indication of user authentication for processing the 10 tokenized purchase order. 11 12 Blo. The means of embodiment B8, wherein the payment token is associated 13 with a plurality of user issuer accounts. 14 1s B11. The means of embodiment Bio, wherein at least one of the user issuer 16 accounts is a stored value account. 17 18 B12. The means of embodiment Bio, wherein at least one of the user issuer 19 accounts is another payment token. 20 21 B13. The means of embodiment B8, further comprising: 22 means for obtaining a payment options request including a list of user 23 issue accounts to utilize for processing the tokenized purchase order, after providing the 24 tokenized purchase order for processing; WO 2011/153505 PCT/US2011/039178 83 1 means for obtaining a user selection of at least one of the user issuer 2 accounts to utilize for processing the tokenized purchase order; and 3 means for providing the user selection for processing the tokenized 4 purchase order. 5 6 B14. The means of embodiment B13, further comprising: 7 means for obtaining a user selection of at least another of the user issuer 8 accounts, as well as a user indication of purchase amounts to be charged to the user 9 selected user issuer accounts; and 10 means for providing the user selection of the user issuer accounts and the 11 indication of the purchase amounts to be charged to the user-selected user issuer 12 accounts. 13 14 B15. A tokenized payment purchasing apparatus embodiment, comprising: 1s a processor; and 16 a memory disposed in communication with the processor and storing processor 17 executable instructions to: 18 obtain purchase input from a user into a mobile device; 19 identify a unique source-neutral universally-resolvable payment token to 20 utilize in lieu of user financial payment information; 21 generate a tokenized purchase order using the purchase input and the 22 payment token; and 23 provide the tokenized purchase order for processing. 24 WO 2011/153505 PCT/US2011/039178 84 1 B16. The apparatus of embodiment B15, the memory further storing instructions 2 to: 3 obtain an indication to verify user authentication for processing tokenized 4 purchase order; 5 generate a user authentication response via device fingerprinting using a 6 hardware authentication chip embedded in the mobile device; 7 provide the user authentication response; and 8 obtain an indication of user authentication for processing the tokenized 9 purchase order. 10 11 B17. The apparatus of embodiment B15, wherein the payment token is associated 12 with a plurality of user issuer accounts. 13 14 B18. The apparatus of embodiment B17, wherein at least one of the user issuer 15 accounts is a stored value account. 16 17 B19. The apparatus of embodiment B17, wherein at least one of the user issuer 18 accounts is another payment token. 19 20 B2o. The apparatus of embodiment B15, the memory further storing instructions 21 to: 22 obtain a payment options request including a list of user issue accounts to 23 utilize for processing the tokenized purchase order, after providing the tokenized 24 purchase order for processing; WO 2011/153505 PCT/US2011/039178 85 1 obtain a user selection of at least one of the user issuer accounts to utilize 2 for processing the tokenized purchase order; and 3 provide the user selection for processing the tokenized purchase order. 4 5 B21. The apparatus of embodiment B20, the memory further storing instructions 6 to: 7 obtain a user selection of at least another of the user issuer accounts, as 8 well as a user indication of purchase amounts to be charged to the user-selected user 9 issuer accounts; and 10 provide the user selection of the user issuer accounts and the indication of 11 the purchase amounts to be charged to the user-selected user issuer accounts. 12 13 B22. A processor-readable tangible medium embodiment storing processor 14 executable tokenized payment purchasing instructions to: 15 obtain purchase input from a user into a mobile device; 16 identify a payment token to utilize in lieu of user financial payment 17 information; 18 generate a tokenized purchase order using the purchase input and the 19 payment token; and 20 provide the tokenized purchase order for processing. 21 22 B23. The medium of embodiment B22, further storing instructions to: 23 obtain an indication to verify user authentication for processing tokenized 24 purchase order; WO 2011/153505 PCT/US2011/039178 86 1 generate a user authentication response via device fingerprinting using a 2 hardware authentication chip embedded in the mobile device; 3 provide the user authentication response; and 4 obtain an indication of user authentication for processing the tokenized 5 purchase order. 6 7 B24. The medium of embodiment B22, wherein the payment token is associated 8 with a plurality of user issuer accounts. 9 10 B25. The medium of embodiment B24, wherein at least one of the user issuer 11 accounts is a stored value account. 12 13 B26. The medium of embodiment B24, wherein at least one of the user issuer 14 accounts is another payment token. 15 16 B27. The medium of embodiment B22, further storing instructions to: 17 obtain a payment options request including a list of user issue accounts to 18 utilize for processing the tokenized purchase order, after providing the tokenized 19 purchase order for processing; 20 obtain a user selection of at least one of the user issuer accounts to utilize 21 for processing the tokenized purchase order; and 22 provide the user selection for processing the tokenized purchase order. 23 24 B28. The medium of embodiment B27, further storing instructions to: WO 2011/153505 PCT/US2011/039178 87 1 obtain a user selection of at least another of the user issuer accounts, as 2 well as a user indication of purchase amounts to be charged to the user-selected user 3 issuer accounts; and 4 provide the user selection of the user issuer accounts and the indication of 5 the purchase amounts to be charged to the user-selected user issuer accounts. 6 7 [o0115] In order to address various issues and advance the art, the entirety of this 8 application for PAYMENT TOKENIZATION APPARATUSES, METHODS AND 9 SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, 10 Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, 11 Appendices and/or otherwise) shows by way of illustration various embodiments in 12 which the claimed inventions may be practiced. The advantages and features of the 13 application are of a representative sample of embodiments only, and are not exhaustive 14 and/or exclusive. They are presented only to assist in understanding and teach the 15 claimed principles. It should be understood that they are not representative of all 16 claimed inventions. As such, certain aspects of the disclosure have not been discussed 17 herein. That alternate embodiments may not have been presented for a specific portion 18 of the invention or that further undescribed alternate embodiments may be available for 19 a portion is not to be considered a disclaimer of those alternate embodiments. It will be 20 appreciated that many of those undescribed embodiments incorporate the same 21 principles of the invention and others are equivalent. Thus, it is to be understood that 22 other embodiments may be utilized and functional, logical, organizational, structural 23 and/or topological modifications may be made without departing from the scope and/or 24 spirit of the disclosure. As such, all examples and/or embodiments are deemed to be WO 2011/153505 PCT/US2011/039178 88 1 non-limiting throughout this disclosure. Also, no inference should be drawn regarding 2 those embodiments discussed herein relative to those not discussed herein other than it 3 is as such for purposes of reducing space and repetition. For instance, it is to be 4 understood that the logical and/or topological structure of any combination of any 5 program components (a component collection), other components and/or any present 6 feature sets as described in the figures and/or throughout are not limited to a fixed 7 operating order and/or arrangement, but rather, any disclosed order is exemplary and 8 all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it 9 is to be understood that such features are not limited to serial execution, but rather, any 10 number of threads, processes, services, servers, and/or the like that may execute 11 asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the 12 like are contemplated by the disclosure. As such, some of these features may be 13 mutually contradictory, in that they cannot be simultaneously present in a single 14 embodiment. Similarly, some features are applicable to one aspect of the invention, and 15 inapplicable to others. In addition, the disclosure includes other inventions not 16 presently claimed. Applicant reserves all rights in those presently unclaimed inventions 17 including the right to claim such inventions, file additional applications, continuations, 18 continuations in part, divisions, and/or the like thereof. As such, it should be 19 understood that advantages, embodiments, examples, functional, features, logical, 20 organizational, structural, topological, and/or other aspects of the disclosure are not to 21 be considered limitations on the disclosure as defined by the claims or limitations on 22 equivalents to the claims. It is to be understood that, depending on the particular needs 23 and/or characteristics of a PT individual and/or enterprise user, database configuration 24 and/or relational model, data type, data transmission and/or network framework, WO 2011/153505 PCT/US2011/039178 89 1 syntax structure, and/or the like, various embodiments of the PT may be implemented 2 that enable a great deal of flexibility and customization. For example, aspects of the PT 3 may be adapted for compression algorithms, security systems, communications 4 optimization, and/or the like. While various embodiments and discussions of the PT 5 have been directed to purchase transactions, however, it is to be understood that the 6 embodiments described herein may be readily configured and/or customized for a wide 7 variety of other applications and/or implementations. 8
Claims (21)
1. A payment token arbitration processor-implemented method, comprising: obtaining a token arbitration request including unique source-neutral universally-resolvable payment token information from a merchant for processing a purchase order from a user; querying a token database for issuer information on an issuer using the payment token information; obtaining the issuer information based on querying the token database; generating via a processor a purchase authorization request using the issuer information and data extracted from the token arbitration request; and providing the generated purchase authorization request to the issuer; wherein purchase authorization requests are generated for a plurality of issuers based on the payment options and pre-defined settings for issuers to be contacted for processing the purchase order from the user.
2. The method of claim 1, further comprising: determining that the user should be queried for payment options based on the issuer information; generating a payment options request for the user; and providing the payment options request to a mobile device of the user.
3. The method of claim 2, further comprising: obtaining a response to the payment options request from the mobile device of the user; extracting the payment options from the response; providing the generated purchase authorization requests for the plurality of issuers.
4. The method of claim 3, wherein the issuer information includes the pre-defined settings for issuers to be contacted for processing the purchase order from the user. 91
5. The method of claim 2, further comprising: providing a request for user authentication to the mobile device of the user; obtaining a response from the mobile device to the request for user authentication; determining that the user is authenticated to utilize the payment token information for the purchase order, based on the response to the request for user authentication; and generating the purchase authorization request after determining that the user is authenticated to utilize the payment token information for the purchase order.
6. The method of claim 2, further comprising: obtaining a response to the payment options request from the mobile device of the user; extracting the payment options from the response; generating updated pre-defined settings for issuers to be contacted for processing the purchase order from the user; and storing the updated pre-defined settings for issuers to be contacted for processing the purchase order from the user.
7. The method of claim 1, wherein the purchase authorization request is generated using pre-defined settings included in the issuer information on issuers to be contacted for processing the purchase order from the user.
8. A payment token arbitration system, comprising: a processor; and a memory disposed in communication with the process and storing processor executable instructions to: obtain a token arbitration request including unique source-neutral universally-resolvable payment token information from a merchant for processing a purchase order from a user; query a token database for issuer information on an issuer using the payment token information; 92 obtain the issuer information based on querying the token database; generate a purchase authorization request using the issuer information and data extracted from the token arbitration request; and provide the generated purchase authorization request to the issuer; wherein purchase authorization requests are generated for a plurality of issuers based on the payment options and pre-defined settings for issuers to be contacted for processing the purchase order from the user.
9. The system of claim 8, the memory further storing instructions to: determine that the user should be queried for payment options based on the issuer information; generate a payment options request for the user; and provide the payment options request to a mobile device of the user.
10. The system of claim 9, the memory further storing instructions to: obtain a response to the payment options request from the mobile device of the user; extract the payment options from the response; provide the generated purchase authorization requests for the plurality of issuers.
11. The system of claim 10, wherein the issuer information includes the pre-defined settings for issuers to be contacted for processing the purchase order from the user.
12. The system of claim 9, the memory further storing instructions to: provide a request for user authentication to the mobile device of the user; obtain a response from the mobile device to the request for user authentication; determine that the user is authenticated to utilize the payment token information for the purchase order, based on the response to the request for user authentication; and generate the purchase authorization request after determining that the user is 93 authenticated to utilize the payment token information for the purchase order.
13. The system of claim 9, the memory further storing instructions to: obtain a response to the payment options request from the mobile device of the user; extract the payment options from the response; generate updated pre-defined settings for issuers to be contacted for processing the purchase order from the user; and store the updated pre-defined settings for issuers to be contacted for processing the purchase order from the user.
14. The system of claim 8, wherein the purchase authorization request is generated using pre-defined settings included in the issuer information on issuers to be contacted for processing the purchase order from the user.
15. A processor-readable tangible medium storing processor-executable payment token arbitration instructions to: obtain a token arbitration request including payment token information from a merchant for processing a purchase order from a user; query a token database for issuer information on an issuer using the payment token information; obtain the issuer information based on querying the token database; generate a purchase authorization request using the issuer information and data extracted from the token arbitration request; and provide the generated purchase authorization request to the issuer; wherein purchase authorization requests are generated for a plurality of issuers based on the payment options and pre-defined settings for issuers to be contacted for processing the purchase order from the user.
16. The medium of claim 15, further storing instructions to: determine that the user should be queried for payment options based on the issuer information; generate a payment options request for the user; and 94 provide the payment options request to a mobile device of the user.
17. The medium of claim 16, further storing instructions to: obtain a response to the payment options request from the mobile device of the user; extract the payment options from the response; provide the generated purchase authorization requests for the plurality of issuers.
18. The medium of claim 17, wherein the issuer information includes the pre defined settings for issuers to be contacted for processing the purchase order from the user.
19. The medium of claim 16, further storing instructions to: provide a request for user authentication to the mobile device of the user; obtain a response from the mobile device to the request for user authentication; determine that the user is authenticated to utilize the payment token information for the purchase order, based on the response to the request for user authentication; and generate the purchase authorization request after determining that the user is authenticated to utilize the payment token information for the purchase order.
20. The medium of claim 16, further storing instructions to: obtain a response to the payment options request from the mobile device of the user; extract the payment options from the response; generate updated pre-defined settings for issuers to be contacted for processing the purchase order from the user; and store the updated pre-defined settings for issuers to be contacted for processing the purchase order from the user.
21. The medium of claim 15, wherein the purchase authorization request is generated using pre-defined settings included in the issuer information on issuers to be 95 contacted for processing the purchase order from the user.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US35147510P | 2010-06-04 | 2010-06-04 | |
| US61/351,475 | 2010-06-04 | ||
| US201161447644P | 2011-02-28 | 2011-02-28 | |
| US61/447,644 | 2011-02-28 | ||
| PCT/US2011/039178 WO2011153505A1 (en) | 2010-06-04 | 2011-06-03 | Payment tokenization apparatuses, methods and systems |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| AU2011261259A1 AU2011261259A1 (en) | 2012-10-04 |
| AU2011261259B2 true AU2011261259B2 (en) | 2015-05-14 |
Family
ID=45067101
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2011261259A Active AU2011261259B2 (en) | 2010-06-04 | 2011-06-03 | Payment tokenization apparatuses, methods and systems |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20120030047A1 (en) |
| CN (1) | CN102939613A (en) |
| AU (1) | AU2011261259B2 (en) |
| BR (1) | BR112012023314A2 (en) |
| WO (1) | WO2011153505A1 (en) |
Families Citing this family (315)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140019352A1 (en) | 2011-02-22 | 2014-01-16 | Visa International Service Association | Multi-purpose virtual card transaction apparatuses, methods and systems |
| US8762263B2 (en) | 2005-09-06 | 2014-06-24 | Visa U.S.A. Inc. | System and method for secured account numbers in proximity devices |
| US7739169B2 (en) | 2007-06-25 | 2010-06-15 | Visa U.S.A. Inc. | Restricting access to compromised account information |
| US7937324B2 (en) | 2007-09-13 | 2011-05-03 | Visa U.S.A. Inc. | Account permanence |
| US8219489B2 (en) | 2008-07-29 | 2012-07-10 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
| US9715681B2 (en) | 2009-04-28 | 2017-07-25 | Visa International Service Association | Verification of portable consumer devices |
| US8534564B2 (en) | 2009-05-15 | 2013-09-17 | Ayman Hammad | Integration of verification tokens with mobile communication devices |
| US10846683B2 (en) | 2009-05-15 | 2020-11-24 | Visa International Service Association | Integration of verification tokens with mobile communication devices |
| US8893967B2 (en) | 2009-05-15 | 2014-11-25 | Visa International Service Association | Secure Communication of payment information to merchants using a verification token |
| US9038886B2 (en) | 2009-05-15 | 2015-05-26 | Visa International Service Association | Verification of portable consumer devices |
| US9105027B2 (en) | 2009-05-15 | 2015-08-11 | Visa International Service Association | Verification of portable consumer device for secure services |
| US10140598B2 (en) | 2009-05-20 | 2018-11-27 | Visa International Service Association | Device including encrypted data for expiration date and verification value creation |
| US10255591B2 (en) * | 2009-12-18 | 2019-04-09 | Visa International Service Association | Payment channel returning limited use proxy dynamic value |
| CA3045817A1 (en) | 2010-01-12 | 2011-07-21 | Visa International Service Association | Anytime validation for verification tokens |
| US9245267B2 (en) | 2010-03-03 | 2016-01-26 | Visa International Service Association | Portable account number for consumer payment account |
| US9342832B2 (en) | 2010-08-12 | 2016-05-17 | Visa International Service Association | Securing external systems with account token substitution |
| US20120296826A1 (en) | 2011-05-18 | 2012-11-22 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
| US10089606B2 (en) | 2011-02-11 | 2018-10-02 | Bytemark, Inc. | System and method for trusted mobile device payment |
| CN109118199A (en) | 2011-02-16 | 2019-01-01 | 维萨国际服务协会 | Snap mobile payment device, method and system |
| US10586227B2 (en) | 2011-02-16 | 2020-03-10 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
| SG193510A1 (en) | 2011-02-22 | 2013-10-30 | Visa Int Service Ass | Universal electronic payment apparatuses, methods and systems |
| CN107967602A (en) | 2011-03-04 | 2018-04-27 | 维萨国际服务协会 | Ability to pay is bound to the safety element of computer |
| US8494967B2 (en) | 2011-03-11 | 2013-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
| US10453067B2 (en) | 2011-03-11 | 2019-10-22 | Bytemark, Inc. | Short range wireless translation methods and systems for hands-free fare validation |
| US10360567B2 (en) | 2011-03-11 | 2019-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with data integrity checking |
| US10762733B2 (en) | 2013-09-26 | 2020-09-01 | Bytemark, Inc. | Method and system for electronic ticket validation using proximity detection |
| WO2012142045A2 (en) | 2011-04-11 | 2012-10-18 | Visa International Service Association | Multiple tokenization for authentication |
| US9256874B2 (en) * | 2011-04-15 | 2016-02-09 | Shift4 Corporation | Method and system for enabling merchants to share tokens |
| US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
| US10121129B2 (en) | 2011-07-05 | 2018-11-06 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
| US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
| US20130018759A1 (en) * | 2011-07-13 | 2013-01-17 | Ebay Inc. | Third party token system for anonymous shipping |
| SG10201605288SA (en) * | 2011-07-15 | 2016-08-30 | Mastercard International Inc | Methods and systems for payments assurance |
| WO2013019567A2 (en) | 2011-07-29 | 2013-02-07 | Visa International Service Association | Passing payment tokens through an hop/sop |
| US10242358B2 (en) | 2011-08-18 | 2019-03-26 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
| US9710807B2 (en) | 2011-08-18 | 2017-07-18 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods and systems |
| US10825001B2 (en) | 2011-08-18 | 2020-11-03 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
| US10223730B2 (en) | 2011-09-23 | 2019-03-05 | Visa International Service Association | E-wallet store injection search apparatuses, methods and systems |
| US9830596B2 (en) | 2011-11-01 | 2017-11-28 | Stripe, Inc. | Method for conducting a transaction between a merchant site and a customer's electronic device without exposing payment information to a server-side application of the merchant site |
| US9898728B2 (en) * | 2011-12-19 | 2018-02-20 | Gfa Worldwide, Inc. | System and method for one-time payment authorization in a portable communication device |
| US8880027B1 (en) * | 2011-12-29 | 2014-11-04 | Emc Corporation | Authenticating to a computing device with a near-field communications card |
| RU2017131424A (en) | 2012-01-05 | 2019-02-06 | Виза Интернэшнл Сервис Ассосиэйшн | TRANSFER DATA PROTECTION |
| WO2013113004A1 (en) | 2012-01-26 | 2013-08-01 | Visa International Service Association | System and method of providing tokenization as a service |
| AU2013214801B2 (en) | 2012-02-02 | 2018-06-21 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia database platform apparatuses, methods and systems |
| US20130212007A1 (en) * | 2012-02-10 | 2013-08-15 | Protegrity Corporation | Tokenization in payment environments |
| US10282724B2 (en) | 2012-03-06 | 2019-05-07 | Visa International Service Association | Security system incorporating mobile device |
| US9203860B1 (en) | 2012-03-20 | 2015-12-01 | United Services Automobile Association (Usaa) | Dynamic risk engine |
| US9185095B1 (en) * | 2012-03-20 | 2015-11-10 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
| US10432605B1 (en) * | 2012-03-20 | 2019-10-01 | United Services Automobile Association (Usaa) | Scalable risk-based authentication methods and systems |
| US20130282582A1 (en) * | 2012-04-18 | 2013-10-24 | Edgard Lobo Baptista Pereira | System and method for data and identity verfication and authentication |
| WO2013159110A1 (en) * | 2012-04-20 | 2013-10-24 | Conductiv Software, Inc. | Multi-factor mobile transaction authentication |
| US20130297501A1 (en) | 2012-05-04 | 2013-11-07 | Justin Monk | System and method for local data conversion |
| US9576279B2 (en) * | 2012-06-05 | 2017-02-21 | Autoscribe Corporation | System and method for registering financial accounts |
| US9524501B2 (en) | 2012-06-06 | 2016-12-20 | Visa International Service Association | Method and system for correlating diverse transaction data |
| US20130339116A1 (en) * | 2012-06-15 | 2013-12-19 | Leaf Holdings, Inc. | System and method for a transaction system |
| US9547769B2 (en) | 2012-07-03 | 2017-01-17 | Visa International Service Association | Data protection hub |
| US9043609B2 (en) | 2012-07-19 | 2015-05-26 | Bank Of America Corporation | Implementing security measures for authorized tokens used in mobile transactions |
| US9846861B2 (en) | 2012-07-25 | 2017-12-19 | Visa International Service Association | Upstream and downstream data conversion |
| US9256871B2 (en) | 2012-07-26 | 2016-02-09 | Visa U.S.A. Inc. | Configurable payment tokens |
| US9665722B2 (en) | 2012-08-10 | 2017-05-30 | Visa International Service Association | Privacy firewall |
| WO2014043278A1 (en) | 2012-09-11 | 2014-03-20 | Visa International Service Association | Cloud-based virtual wallet nfc apparatuses, methods and systems |
| CA3126471A1 (en) | 2012-10-17 | 2014-04-17 | Royal Bank Of Canada | Virtualization and secure processing of data |
| US11961075B2 (en) | 2014-10-10 | 2024-04-16 | Royal Bank Of Canada | Systems for processing electronic transactions |
| US11080701B2 (en) | 2015-07-02 | 2021-08-03 | Royal Bank Of Canada | Secure processing of electronic payments |
| US11210648B2 (en) | 2012-10-17 | 2021-12-28 | Royal Bank Of Canada | Systems, methods, and devices for secure generation and processing of data sets representing pre-funded payments |
| US10176478B2 (en) | 2012-10-23 | 2019-01-08 | Visa International Service Association | Transaction initiation determination system utilizing transaction data elements |
| US9363288B2 (en) | 2012-10-25 | 2016-06-07 | Verisign, Inc. | Privacy preserving registry browsing |
| US9202079B2 (en) * | 2012-10-25 | 2015-12-01 | Verisign, Inc. | Privacy preserving data querying |
| US10565394B2 (en) | 2012-10-25 | 2020-02-18 | Verisign, Inc. | Privacy—preserving data querying with authenticated denial of existence |
| US9911118B2 (en) * | 2012-11-21 | 2018-03-06 | Visa International Service Association | Device pairing via trusted intermediary |
| SG11201407413WA (en) * | 2012-12-07 | 2014-12-30 | Yota Devices Ipr Ltd | Display surface contains a cut out region reformatting display data |
| US20140164243A1 (en) * | 2012-12-07 | 2014-06-12 | Christian Aabye | Dynamic Account Identifier With Return Real Account Identifier |
| WO2014087381A1 (en) | 2012-12-07 | 2014-06-12 | Visa International Service Association | A token generating component |
| US10521794B2 (en) * | 2012-12-10 | 2019-12-31 | Visa International Service Association | Authenticating remote transactions using a mobile device |
| US10740731B2 (en) | 2013-01-02 | 2020-08-11 | Visa International Service Association | Third party settlement |
| US9741051B2 (en) | 2013-01-02 | 2017-08-22 | Visa International Service Association | Tokenization and third-party interaction |
| US8875247B2 (en) * | 2013-03-14 | 2014-10-28 | Facebook, Inc. | Instant personalization security |
| CN103259787B (en) * | 2013-04-18 | 2017-05-10 | 银江股份有限公司 | Safety interactive method of cloud and terminal based on JSON protocol packet in medical field |
| US11055710B2 (en) | 2013-05-02 | 2021-07-06 | Visa International Service Association | Systems and methods for verifying and processing transactions using virtual currency |
| WO2014186635A1 (en) | 2013-05-15 | 2014-11-20 | Visa International Service Association | Mobile tokenization hub |
| US10878422B2 (en) | 2013-06-17 | 2020-12-29 | Visa International Service Association | System and method using merchant token |
| CN105556531A (en) * | 2013-07-03 | 2016-05-04 | 荷宝信息科技(香港)有限公司 | Method and system for authenticating user using out-of-band channel |
| CA2918788C (en) | 2013-07-24 | 2020-06-16 | Visa International Service Association | Systems and methods for interoperable network token processing |
| EP3025291A1 (en) | 2013-07-26 | 2016-06-01 | Visa International Service Association | Provisioning payment credentials to a consumer |
| US10496986B2 (en) | 2013-08-08 | 2019-12-03 | Visa International Service Association | Multi-network tokenization processing |
| CN105612543B (en) | 2013-08-08 | 2022-05-27 | 维萨国际服务协会 | Method and system for provisioning payment credentials for mobile devices |
| WO2015023986A2 (en) * | 2013-08-15 | 2015-02-19 | @Pay Ip Holdings Llc | System and method utilizing a one-to-many payment button for completing a financial transaction |
| ES2531386B1 (en) * | 2013-09-13 | 2015-12-22 | Pomo Posibilidades, S.A. | System and method of payment via mobile device |
| DE102013016119B4 (en) * | 2013-09-27 | 2023-07-20 | Giesecke+Devrient Mobile Security Gmbh | Payment Procedures |
| US10515370B2 (en) | 2013-10-09 | 2019-12-24 | The Toronto-Dominion Bank | Systems and methods for providing tokenized transaction accounts |
| US10891610B2 (en) * | 2013-10-11 | 2021-01-12 | Visa International Service Association | Network token system |
| US9978094B2 (en) | 2013-10-11 | 2018-05-22 | Visa International Service Association | Tokenization revocation list |
| US10515358B2 (en) | 2013-10-18 | 2019-12-24 | Visa International Service Association | Contextual transaction token methods and systems |
| US10489779B2 (en) | 2013-10-21 | 2019-11-26 | Visa International Service Association | Multi-network token bin routing with defined verification parameters |
| US10366387B2 (en) | 2013-10-29 | 2019-07-30 | Visa International Service Association | Digital wallet system and method |
| US8856045B1 (en) * | 2013-12-18 | 2014-10-07 | PayRange Inc. | Mobile-device-to-machine payment systems |
| US11205163B2 (en) | 2013-12-18 | 2021-12-21 | PayRange Inc. | Systems and methods for determining electric pulses to provide to an unattended machine based on remotely-configured options |
| US11481781B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Processing interrupted transaction over non-persistent network connections |
| US9875473B2 (en) | 2013-12-18 | 2018-01-23 | PayRange Inc. | Method and system for retrofitting an offline-payment operated machine to accept electronic payments |
| US11481780B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
| US11475454B2 (en) | 2013-12-18 | 2022-10-18 | PayRange Inc. | Intermediary communications over non-persistent network connections |
| US9659296B2 (en) | 2013-12-18 | 2017-05-23 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
| US11983692B2 (en) | 2013-12-18 | 2024-05-14 | PayRange Inc. | Mobile payment module with dual function radio transmitter |
| US10019724B2 (en) | 2015-01-30 | 2018-07-10 | PayRange Inc. | Method and system for providing offers for automated retail machines via mobile devices |
| US11074580B2 (en) | 2013-12-18 | 2021-07-27 | PayRange Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
| US11966926B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
| US11966895B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Refund centers for processing and dispensing vending machine refunds via an MDB router |
| KR102293822B1 (en) | 2013-12-19 | 2021-08-26 | 비자 인터네셔널 서비스 어소시에이션 | Cloud-based transactions methods and systems |
| US9922322B2 (en) | 2013-12-19 | 2018-03-20 | Visa International Service Association | Cloud-based transactions with magnetic secure transmission |
| US11580518B2 (en) * | 2014-01-03 | 2023-02-14 | Apple Inc. | Disabling mobile payments for lost electronic devices |
| US10433128B2 (en) | 2014-01-07 | 2019-10-01 | Visa International Service Association | Methods and systems for provisioning multiple devices |
| US9148284B2 (en) * | 2014-01-14 | 2015-09-29 | Bjoern Pirrwitz | Identification and/or authentication method |
| US9846878B2 (en) | 2014-01-14 | 2017-12-19 | Visa International Service Association | Payment account identifier system |
| US9965606B2 (en) | 2014-02-07 | 2018-05-08 | Bank Of America Corporation | Determining user authentication based on user/device interaction |
| US9647999B2 (en) | 2014-02-07 | 2017-05-09 | Bank Of America Corporation | Authentication level of function bucket based on circumstances |
| US9286450B2 (en) | 2014-02-07 | 2016-03-15 | Bank Of America Corporation | Self-selected user access based on specific authentication types |
| US9208301B2 (en) | 2014-02-07 | 2015-12-08 | Bank Of America Corporation | Determining user authentication requirements based on the current location of the user in comparison to the users's normal boundary of location |
| US9223951B2 (en) | 2014-02-07 | 2015-12-29 | Bank Of America Corporation | User authentication based on other applications |
| US10853799B2 (en) | 2014-02-20 | 2020-12-01 | Swoop Ip Holdings Llc | System and method for dual email and web based checkout in an unsegmented list |
| US9721268B2 (en) | 2014-03-04 | 2017-08-01 | Bank Of America Corporation | Providing offers associated with payment credentials authenticated in a specific digital wallet |
| US10002352B2 (en) | 2014-03-04 | 2018-06-19 | Bank Of America Corporation | Digital wallet exposure reduction |
| US9600817B2 (en) | 2014-03-04 | 2017-03-21 | Bank Of America Corporation | Foreign exchange token |
| US9721248B2 (en) | 2014-03-04 | 2017-08-01 | Bank Of America Corporation | ATM token cash withdrawal |
| US9830597B2 (en) | 2014-03-04 | 2017-11-28 | Bank Of America Corporation | Formation and funding of a shared token |
| US9406065B2 (en) | 2014-03-04 | 2016-08-02 | Bank Of America Corporation | Customer token preferences interface |
| US9600844B2 (en) | 2014-03-04 | 2017-03-21 | Bank Of America Corporation | Foreign cross-issued token |
| US9424572B2 (en) | 2014-03-04 | 2016-08-23 | Bank Of America Corporation | Online banking digital wallet management |
| US10026087B2 (en) | 2014-04-08 | 2018-07-17 | Visa International Service Association | Data passed in an interaction |
| US9942043B2 (en) | 2014-04-23 | 2018-04-10 | Visa International Service Association | Token security on a communication device |
| CN106233664B (en) | 2014-05-01 | 2020-03-13 | 维萨国际服务协会 | Data authentication using an access device |
| CN106462849B (en) | 2014-05-05 | 2019-12-24 | 维萨国际服务协会 | System and method for token domain control |
| US10070310B2 (en) | 2014-05-08 | 2018-09-04 | Visa International Service Association | Method and system for provisioning access data to mobile device |
| US10959093B2 (en) * | 2014-05-08 | 2021-03-23 | Visa International Service Association | Method and system for provisioning access data to mobile device |
| AU2015264124B2 (en) | 2014-05-21 | 2019-05-09 | Visa International Service Association | Offline authentication |
| US11023890B2 (en) | 2014-06-05 | 2021-06-01 | Visa International Service Association | Identification and verification for provisioning mobile application |
| US9780953B2 (en) | 2014-07-23 | 2017-10-03 | Visa International Service Association | Systems and methods for secure detokenization |
| US10484345B2 (en) | 2014-07-31 | 2019-11-19 | Visa International Service Association | System and method for identity verification across mobile applications |
| US9775029B2 (en) | 2014-08-22 | 2017-09-26 | Visa International Service Association | Embedding cloud-based functionalities in a communication device |
| AP2017009835A0 (en) * | 2014-08-29 | 2017-03-31 | Ruan & Riana Familie Trust | System and method for electronic payments |
| US10140615B2 (en) | 2014-09-22 | 2018-11-27 | Visa International Service Association | Secure mobile device credential provisioning using risk decision non-overrides |
| SG10201810140QA (en) | 2014-09-26 | 2018-12-28 | Visa Int Service Ass | Remote server encrypted data provisioning system and methods |
| CA2906911C (en) | 2014-09-29 | 2023-08-15 | The Toronto-Dominion Bank | Systems and methods for generating and administering mobile applications using pre-loaded tokens |
| US11257074B2 (en) | 2014-09-29 | 2022-02-22 | Visa International Service Association | Transaction risk based token |
| US10015147B2 (en) | 2014-10-22 | 2018-07-03 | Visa International Service Association | Token enrollment system and method |
| GB201419016D0 (en) | 2014-10-24 | 2014-12-10 | Visa Europe Ltd | Transaction Messaging |
| CN113537988B (en) | 2014-11-26 | 2024-05-28 | 维萨国际服务协会 | Method and apparatus for tokenizing requests via an access device |
| US10257185B2 (en) | 2014-12-12 | 2019-04-09 | Visa International Service Association | Automated access data provisioning |
| WO2016094122A1 (en) | 2014-12-12 | 2016-06-16 | Visa International Service Association | Provisioning platform for machine-to-machine devices |
| US11354651B2 (en) | 2015-01-19 | 2022-06-07 | Royal Bank Of Canada | System and method for location-based token transaction processing |
| EP3248159A4 (en) | 2015-01-19 | 2018-08-01 | Royal Bank Of Canada | Secure processing of electronic payments |
| US10096009B2 (en) | 2015-01-20 | 2018-10-09 | Visa International Service Association | Secure payment processing using authorization request |
| US11250391B2 (en) | 2015-01-30 | 2022-02-15 | Visa International Service Association | Token check offline |
| USD862501S1 (en) | 2015-01-30 | 2019-10-08 | PayRange Inc. | Display screen or portion thereof with a graphical user interface |
| KR102460459B1 (en) * | 2015-02-27 | 2022-10-28 | 삼성전자주식회사 | Method and apparatus for providing card service using electronic device |
| EP3065366B1 (en) * | 2015-03-02 | 2020-09-09 | Bjoern Pirrwitz | Identification and/or authentication system and method |
| CN107408244B (en) * | 2015-03-06 | 2021-12-31 | 万事达卡国际股份有限公司 | Secure mobile remote payment |
| US10164996B2 (en) | 2015-03-12 | 2018-12-25 | Visa International Service Association | Methods and systems for providing a low value token buffer |
| CA2977427A1 (en) | 2015-04-10 | 2016-10-13 | Visa International Service Association | Browser integration with cryptogram |
| US9998978B2 (en) | 2015-04-16 | 2018-06-12 | Visa International Service Association | Systems and methods for processing dormant virtual access devices |
| US11954671B2 (en) * | 2015-04-27 | 2024-04-09 | Paypal, Inc. | Unified login across applications |
| US11176527B2 (en) * | 2015-04-28 | 2021-11-16 | Ncr Corporation | Cross-network action approval |
| US10552834B2 (en) | 2015-04-30 | 2020-02-04 | Visa International Service Association | Tokenization capable authentication framework |
| US10878411B2 (en) * | 2015-05-13 | 2020-12-29 | Sony Corporation | Method and apparatus for issued token management |
| US20180152429A1 (en) * | 2015-05-29 | 2018-05-31 | Digital Cc Ip Pty Ltd. | Systems and methods for publicly verifiable authorization |
| US11599879B2 (en) * | 2015-07-02 | 2023-03-07 | Royal Bank Of Canada | Processing of electronic transactions |
| JP6516009B2 (en) * | 2015-07-10 | 2019-05-22 | 富士通株式会社 | Device authentication system, management apparatus and device authentication method |
| US11803784B2 (en) | 2015-08-17 | 2023-10-31 | Siemens Mobility, Inc. | Sensor fusion for transit applications |
| AU2016307794A1 (en) | 2015-08-17 | 2017-12-07 | Bytemark, Inc. | Short range wireless translation methods and systems for hands-free fare validation |
| US10607215B2 (en) | 2015-09-30 | 2020-03-31 | Bank Of America Corporation | Account tokenization for virtual currency resources |
| US10453059B2 (en) | 2015-09-30 | 2019-10-22 | Bank Of America Corporation | Non-intrusive geo-location determination associated with transaction authorization |
| US11068889B2 (en) | 2015-10-15 | 2021-07-20 | Visa International Service Association | Instant token issuance |
| US9729536B2 (en) | 2015-10-30 | 2017-08-08 | Bank Of America Corporation | Tiered identification federated authentication network system |
| US10685352B2 (en) * | 2015-11-09 | 2020-06-16 | Paypal, Inc. | System, method, and medium for an integration platform to interface with third party channels |
| CN113542293B (en) | 2015-12-04 | 2023-11-07 | 维萨国际服务协会 | Method and computer for token verification |
| US10445755B2 (en) * | 2015-12-30 | 2019-10-15 | Paypal, Inc. | Data structures for categorizing and filtering content |
| AU2017206119B2 (en) | 2016-01-07 | 2020-10-29 | Visa International Service Association | Systems and methods for device push provisioning |
| US20170213206A1 (en) * | 2016-01-25 | 2017-07-27 | Apple Inc. | Conducting transactions using electronic devices with geographically restricted non-native credentials |
| WO2017136418A1 (en) | 2016-02-01 | 2017-08-10 | Visa International Service Association | Systems and methods for code display and use |
| US11501288B2 (en) | 2016-02-09 | 2022-11-15 | Visa International Service Association | Resource provider account token provisioning and processing |
| US10313321B2 (en) | 2016-04-07 | 2019-06-04 | Visa International Service Association | Tokenization of co-network accounts |
| CN109074578A (en) | 2016-04-19 | 2018-12-21 | 维萨国际服务协会 | System and method for executing push transaction |
| US10460367B2 (en) | 2016-04-29 | 2019-10-29 | Bank Of America Corporation | System for user authentication based on linking a randomly generated number to the user and a physical item |
| US11250424B2 (en) | 2016-05-19 | 2022-02-15 | Visa International Service Association | Systems and methods for creating subtokens using primary tokens |
| BR112018072903A2 (en) | 2016-06-03 | 2019-02-19 | Visa International Service Association | method, and, communication devices and connected. |
| US20230401564A1 (en) * | 2022-06-09 | 2023-12-14 | Capital One Services, Llc | Techniques to process contactless card functions in a multiple banking system environment |
| US11068899B2 (en) | 2016-06-17 | 2021-07-20 | Visa International Service Association | Token aggregation for multi-party transactions |
| US10268635B2 (en) | 2016-06-17 | 2019-04-23 | Bank Of America Corporation | System for data rotation through tokenization |
| SG11201808737YA (en) | 2016-06-24 | 2018-11-29 | Visa Int Service Ass | Unique token authentication cryptogram |
| CN106203998A (en) * | 2016-07-04 | 2016-12-07 | 天脉聚源(北京)传媒科技有限公司 | A kind of method and device of withdrawing deposit of net cast |
| SG10202110839VA (en) | 2016-07-11 | 2021-11-29 | Visa Int Service Ass | Encryption key exchange process using access device |
| EP3488406A4 (en) | 2016-07-19 | 2019-08-07 | Visa International Service Association | Method of distributing tokens and managing token relationships |
| US10509779B2 (en) | 2016-09-14 | 2019-12-17 | Visa International Service Association | Self-cleaning token vault |
| CN117009946A (en) | 2016-11-28 | 2023-11-07 | 维萨国际服务协会 | Access identifier supplied to application program |
| US10915899B2 (en) | 2017-03-17 | 2021-02-09 | Visa International Service Association | Replacing token on a multi-token user device |
| US10755339B2 (en) | 2017-03-17 | 2020-08-25 | Team Labs, Inc. | System and method of purchase request management using plain text messages |
| US10902418B2 (en) | 2017-05-02 | 2021-01-26 | Visa International Service Association | System and method using interaction token |
| US11494765B2 (en) | 2017-05-11 | 2022-11-08 | Visa International Service Association | Secure remote transaction system using mobile devices |
| US10313480B2 (en) | 2017-06-22 | 2019-06-04 | Bank Of America Corporation | Data transmission between networked resources |
| US10511692B2 (en) | 2017-06-22 | 2019-12-17 | Bank Of America Corporation | Data transmission to a networked resource based on contextual information |
| US10524165B2 (en) | 2017-06-22 | 2019-12-31 | Bank Of America Corporation | Dynamic utilization of alternative resources based on token association |
| US10491389B2 (en) | 2017-07-14 | 2019-11-26 | Visa International Service Association | Token provisioning utilizing a secure authentication system |
| RU2673398C1 (en) * | 2018-01-22 | 2018-11-26 | Олег Александрович Серебренников | Method of carrying out payment transactions |
| EP3762844A4 (en) | 2018-03-07 | 2021-04-21 | Visa International Service Association | Secure remote token release with online authentication |
| US11144921B2 (en) | 2018-04-05 | 2021-10-12 | The Toronto-Dominion Bank | Generation and provisioning of digital tokens based on dynamically obtained contextual data |
| US11361284B1 (en) | 2018-05-31 | 2022-06-14 | Stripe, Inc. | Payment processing method and apparatus using an intermediary platform |
| US11256789B2 (en) | 2018-06-18 | 2022-02-22 | Visa International Service Association | Recurring token transactions |
| US10546444B2 (en) | 2018-06-21 | 2020-01-28 | Capital One Services, Llc | Systems and methods for secure read-only authentication |
| WO2020023632A1 (en) * | 2018-07-25 | 2020-01-30 | Jpmorgan Chase Bank, N.A. | Systems and methods for out-of-band, time-based matching for applying issuer benefits to transactions |
| EP3841498B1 (en) | 2018-08-22 | 2024-05-01 | Visa International Service Association | Method and system for token provisioning and processing |
| US10771254B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for email-based card activation |
| JP2022508010A (en) | 2018-10-02 | 2022-01-19 | キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニー | Systems and methods for cryptographic authentication of non-contact cards |
| SG11202101874SA (en) | 2018-10-02 | 2021-03-30 | Capital One Services Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10554411B1 (en) | 2018-10-02 | 2020-02-04 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10489781B1 (en) | 2018-10-02 | 2019-11-26 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10511443B1 (en) | 2018-10-02 | 2019-12-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10771253B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10581611B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| CA3113590A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| CA3115084A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US11210664B2 (en) | 2018-10-02 | 2021-12-28 | Capital One Services, Llc | Systems and methods for amplifying the strength of cryptographic algorithms |
| WO2020072670A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10579998B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10505738B1 (en) | 2018-10-02 | 2019-12-10 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| JP2022502891A (en) | 2018-10-02 | 2022-01-11 | キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニーCapital One Services, LLC | Systems and methods for cryptographic authentication of non-contact cards |
| KR20210068028A (en) | 2018-10-02 | 2021-06-08 | 캐피탈 원 서비시즈, 엘엘씨 | System and method for cryptographic authentication of contactless card |
| US10949520B2 (en) | 2018-10-02 | 2021-03-16 | Capital One Services, Llc | Systems and methods for cross coupling risk analytics and one-time-passcodes |
| US10680824B2 (en) | 2018-10-02 | 2020-06-09 | Capital One Services, Llc | Systems and methods for inventory management using cryptographic authentication of contactless cards |
| AU2019354421A1 (en) | 2018-10-02 | 2021-04-29 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| WO2020072474A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10733645B2 (en) | 2018-10-02 | 2020-08-04 | Capital One Services, Llc | Systems and methods for establishing identity for order pick up |
| US10607216B1 (en) | 2018-10-02 | 2020-03-31 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10909527B2 (en) | 2018-10-02 | 2021-02-02 | Capital One Services, Llc | Systems and methods for performing a reissue of a contactless card |
| US10565587B1 (en) | 2018-10-02 | 2020-02-18 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10592710B1 (en) | 2018-10-02 | 2020-03-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10542036B1 (en) | 2018-10-02 | 2020-01-21 | Capital One Services, Llc | Systems and methods for signaling an attack on contactless cards |
| CA3115064A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| WO2020072552A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10582386B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US10607214B1 (en) | 2018-10-02 | 2020-03-31 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
| US11301862B2 (en) | 2018-10-04 | 2022-04-12 | Capital One Services, Llc | Secure transfer of tokens between devices |
| CN113015992B (en) | 2018-11-14 | 2023-02-17 | 维萨国际服务协会 | Cloud token provisioning of multiple tokens |
| US11361302B2 (en) | 2019-01-11 | 2022-06-14 | Capital One Services, Llc | Systems and methods for touch screen interface interaction using a card overlay |
| US11037136B2 (en) | 2019-01-24 | 2021-06-15 | Capital One Services, Llc | Tap to autofill card data |
| US11120453B2 (en) | 2019-02-01 | 2021-09-14 | Capital One Services, Llc | Tap card to securely generate card data to copy to clipboard |
| US10510074B1 (en) | 2019-02-01 | 2019-12-17 | Capital One Services, Llc | One-tap payment using a contactless card |
| US10467622B1 (en) | 2019-02-01 | 2019-11-05 | Capital One Services, Llc | Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms |
| US10425129B1 (en) | 2019-02-27 | 2019-09-24 | Capital One Services, Llc | Techniques to reduce power consumption in near field communication systems |
| US10523708B1 (en) | 2019-03-18 | 2019-12-31 | Capital One Services, Llc | System and method for second factor authentication of customer support calls |
| US10643420B1 (en) | 2019-03-20 | 2020-05-05 | Capital One Services, Llc | Contextual tapping engine |
| US10438437B1 (en) | 2019-03-20 | 2019-10-08 | Capital One Services, Llc | Tap to copy data to clipboard via NFC |
| US10984416B2 (en) | 2019-03-20 | 2021-04-20 | Capital One Services, Llc | NFC mobile currency transfer |
| US10535062B1 (en) | 2019-03-20 | 2020-01-14 | Capital One Services, Llc | Using a contactless card to securely share personal data stored in a blockchain |
| US10970712B2 (en) | 2019-03-21 | 2021-04-06 | Capital One Services, Llc | Delegated administration of permissions using a contactless card |
| US10467445B1 (en) | 2019-03-28 | 2019-11-05 | Capital One Services, Llc | Devices and methods for contactless card alignment with a foldable mobile device |
| US11849042B2 (en) | 2019-05-17 | 2023-12-19 | Visa International Service Association | Virtual access credential interaction system and method |
| US11521262B2 (en) | 2019-05-28 | 2022-12-06 | Capital One Services, Llc | NFC enhanced augmented reality information overlays |
| US10516447B1 (en) | 2019-06-17 | 2019-12-24 | Capital One Services, Llc | Dynamic power levels in NFC card communications |
| US10871958B1 (en) | 2019-07-03 | 2020-12-22 | Capital One Services, Llc | Techniques to perform applet programming |
| US11392933B2 (en) | 2019-07-03 | 2022-07-19 | Capital One Services, Llc | Systems and methods for providing online and hybridcard interactions |
| US11694187B2 (en) | 2019-07-03 | 2023-07-04 | Capital One Services, Llc | Constraining transactional capabilities for contactless cards |
| US10713649B1 (en) | 2019-07-09 | 2020-07-14 | Capital One Services, Llc | System and method enabling mobile near-field communication to update display on a payment card |
| US10885514B1 (en) | 2019-07-15 | 2021-01-05 | Capital One Services, Llc | System and method for using image data to trigger contactless card transactions |
| US10498401B1 (en) | 2019-07-15 | 2019-12-03 | Capital One Services, Llc | System and method for guiding card positioning using phone sensors |
| US10832271B1 (en) | 2019-07-17 | 2020-11-10 | Capital One Services, Llc | Verified reviews using a contactless card |
| US11182771B2 (en) | 2019-07-17 | 2021-11-23 | Capital One Services, Llc | System for value loading onto in-vehicle device |
| US10733601B1 (en) | 2019-07-17 | 2020-08-04 | Capital One Services, Llc | Body area network facilitated authentication or payment authorization |
| US11521213B2 (en) | 2019-07-18 | 2022-12-06 | Capital One Services, Llc | Continuous authentication for digital services based on contactless card positioning |
| US10506426B1 (en) | 2019-07-19 | 2019-12-10 | Capital One Services, Llc | Techniques for call authentication |
| US10541995B1 (en) | 2019-07-23 | 2020-01-21 | Capital One Services, Llc | First factor contactless card authentication system and method |
| KR20220071211A (en) | 2019-10-02 | 2022-05-31 | 캐피탈 원 서비시즈, 엘엘씨 | Client Device Authentication Using Contactless Legacy Magnetic Stripe Data |
| US11423375B2 (en) * | 2019-10-30 | 2022-08-23 | Mastercard International Incorporated | Systems and methods for bill payment using transaction cards within a financial institution payment platform |
| US10657754B1 (en) | 2019-12-23 | 2020-05-19 | Capital One Services, Llc | Contactless card and personal identification system |
| US10862540B1 (en) | 2019-12-23 | 2020-12-08 | Capital One Services, Llc | Method for mapping NFC field strength and location on mobile devices |
| US10733283B1 (en) | 2019-12-23 | 2020-08-04 | Capital One Services, Llc | Secure password generation and management using NFC and contactless smart cards |
| US11651361B2 (en) | 2019-12-23 | 2023-05-16 | Capital One Services, Llc | Secure authentication based on passport data stored in a contactless card |
| US10885410B1 (en) | 2019-12-23 | 2021-01-05 | Capital One Services, Llc | Generating barcodes utilizing cryptographic techniques |
| US11113685B2 (en) | 2019-12-23 | 2021-09-07 | Capital One Services, Llc | Card issuing with restricted virtual numbers |
| US11615395B2 (en) | 2019-12-23 | 2023-03-28 | Capital One Services, Llc | Authentication for third party digital wallet provisioning |
| US10664941B1 (en) | 2019-12-24 | 2020-05-26 | Capital One Services, Llc | Steganographic image encoding of biometric template information on a card |
| US10853795B1 (en) | 2019-12-24 | 2020-12-01 | Capital One Services, Llc | Secure authentication based on identity data stored in a contactless card |
| US11200563B2 (en) | 2019-12-24 | 2021-12-14 | Capital One Services, Llc | Account registration using a contactless card |
| US10909544B1 (en) | 2019-12-26 | 2021-02-02 | Capital One Services, Llc | Accessing and utilizing multiple loyalty point accounts |
| US10757574B1 (en) | 2019-12-26 | 2020-08-25 | Capital One Services, Llc | Multi-factor authentication providing a credential via a contactless card for secure messaging |
| US11038688B1 (en) | 2019-12-30 | 2021-06-15 | Capital One Services, Llc | Techniques to control applets for contactless cards |
| US10860914B1 (en) | 2019-12-31 | 2020-12-08 | Capital One Services, Llc | Contactless card and method of assembly |
| US11455620B2 (en) | 2019-12-31 | 2022-09-27 | Capital One Services, Llc | Tapping a contactless card to a computing device to provision a virtual number |
| US11210656B2 (en) | 2020-04-13 | 2021-12-28 | Capital One Services, Llc | Determining specific terms for contactless card activation |
| US11222342B2 (en) | 2020-04-30 | 2022-01-11 | Capital One Services, Llc | Accurate images in graphical user interfaces to enable data transfer |
| US11823175B2 (en) | 2020-04-30 | 2023-11-21 | Capital One Services, Llc | Intelligent card unlock |
| US10861006B1 (en) | 2020-04-30 | 2020-12-08 | Capital One Services, Llc | Systems and methods for data access control using a short-range transceiver |
| US11030339B1 (en) | 2020-04-30 | 2021-06-08 | Capital One Services, Llc | Systems and methods for data access control of personal user data using a short-range transceiver |
| US10915888B1 (en) | 2020-04-30 | 2021-02-09 | Capital One Services, Llc | Contactless card with multiple rotating security keys |
| US10963865B1 (en) | 2020-05-12 | 2021-03-30 | Capital One Services, Llc | Augmented reality card activation experience |
| US11100511B1 (en) | 2020-05-18 | 2021-08-24 | Capital One Services, Llc | Application-based point of sale system in mobile operating systems |
| US11063979B1 (en) | 2020-05-18 | 2021-07-13 | Capital One Services, Llc | Enabling communications between applications in a mobile operating system |
| US11062098B1 (en) | 2020-08-11 | 2021-07-13 | Capital One Services, Llc | Augmented reality information display and interaction via NFC based authentication |
| US11263164B1 (en) | 2020-08-28 | 2022-03-01 | Tata Consultancy Services Lmited | Multiple field programmable gate array (FPGA) based multi-legged order transaction processing system and method thereof |
| US11482312B2 (en) | 2020-10-30 | 2022-10-25 | Capital One Services, Llc | Secure verification of medical status using a contactless card |
| US11165586B1 (en) | 2020-10-30 | 2021-11-02 | Capital One Services, Llc | Call center web-based authentication using a contactless card |
| US11373169B2 (en) | 2020-11-03 | 2022-06-28 | Capital One Services, Llc | Web-based activation of contactless cards |
| US11216799B1 (en) | 2021-01-04 | 2022-01-04 | Capital One Services, Llc | Secure generation of one-time passcodes using a contactless card |
| US11682012B2 (en) | 2021-01-27 | 2023-06-20 | Capital One Services, Llc | Contactless delivery systems and methods |
| US11562358B2 (en) | 2021-01-28 | 2023-01-24 | Capital One Services, Llc | Systems and methods for near field contactless card communication and cryptographic authentication |
| US11687930B2 (en) | 2021-01-28 | 2023-06-27 | Capital One Services, Llc | Systems and methods for authentication of access tokens |
| US11792001B2 (en) | 2021-01-28 | 2023-10-17 | Capital One Services, Llc | Systems and methods for secure reprovisioning |
| US11438329B2 (en) | 2021-01-29 | 2022-09-06 | Capital One Services, Llc | Systems and methods for authenticated peer-to-peer data transfer using resource locators |
| US11777933B2 (en) | 2021-02-03 | 2023-10-03 | Capital One Services, Llc | URL-based authentication for payment cards |
| US11637826B2 (en) | 2021-02-24 | 2023-04-25 | Capital One Services, Llc | Establishing authentication persistence |
| US11245438B1 (en) | 2021-03-26 | 2022-02-08 | Capital One Services, Llc | Network-enabled smart apparatus and systems and methods for activating and provisioning same |
| US11935035B2 (en) | 2021-04-20 | 2024-03-19 | Capital One Services, Llc | Techniques to utilize resource locators by a contactless card to perform a sequence of operations |
| US11961089B2 (en) | 2021-04-20 | 2024-04-16 | Capital One Services, Llc | On-demand applications to extend web services |
| US11902442B2 (en) | 2021-04-22 | 2024-02-13 | Capital One Services, Llc | Secure management of accounts on display devices using a contactless card |
| US11354555B1 (en) | 2021-05-04 | 2022-06-07 | Capital One Services, Llc | Methods, mediums, and systems for applying a display to a transaction card |
| WO2023119144A1 (en) * | 2021-12-22 | 2023-06-29 | Mandar Agashe | A system for secure transaction processing and a method thereof |
| CN115630340B (en) * | 2022-12-21 | 2023-09-05 | 南开大学 | Content resource library group interactive operation method based on copyright service route |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070276765A1 (en) * | 2004-09-07 | 2007-11-29 | Hazel Patrick K | Method and system for secured transactions |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6636833B1 (en) * | 1998-03-25 | 2003-10-21 | Obis Patents Ltd. | Credit card system and method |
| US6422462B1 (en) * | 1998-03-30 | 2002-07-23 | Morris E. Cohen | Apparatus and methods for improved credit cards and credit card transactions |
| US7571139B1 (en) * | 1999-02-19 | 2009-08-04 | Giordano Joseph A | System and method for processing financial transactions |
| US20060178986A1 (en) * | 2000-02-17 | 2006-08-10 | Giordano Joseph A | System and method for processing financial transactions using multi-payment preferences |
| US7499889B2 (en) * | 2000-10-23 | 2009-03-03 | Cyota Inc. | Transaction system |
| US20030101134A1 (en) * | 2001-11-28 | 2003-05-29 | Liu James C. | Method and system for trusted transaction approval |
| US7707120B2 (en) * | 2002-04-17 | 2010-04-27 | Visa International Service Association | Mobile account authentication service |
| GB0318000D0 (en) * | 2003-07-31 | 2003-09-03 | Ncr Int Inc | Mobile applications |
| US8762283B2 (en) * | 2004-05-03 | 2014-06-24 | Visa International Service Association | Multiple party benefit from an online authentication service |
| US7849020B2 (en) * | 2005-04-19 | 2010-12-07 | Microsoft Corporation | Method and apparatus for network transactions |
| KR101322515B1 (en) * | 2005-09-29 | 2013-10-25 | 콘텐트가드 홀딩즈 인코포레이티드 | System and method for digital rights management using advanced copy with issue rights, and managed copy tokens |
| US20080223918A1 (en) * | 2007-03-15 | 2008-09-18 | Microsoft Corporation | Payment tokens |
| CN101711383B (en) * | 2007-04-17 | 2016-06-08 | 维萨美国股份有限公司 | For the method and system of authenticating transactions side |
| US8060413B2 (en) * | 2008-03-14 | 2011-11-15 | Research In Motion Limited | System and method for making electronic payments from a wireless mobile device |
| US9053474B2 (en) * | 2008-08-04 | 2015-06-09 | At&T Mobility Ii Llc | Systems and methods for handling point-of-sale transactions using a mobile device |
-
2011
- 2011-06-03 WO PCT/US2011/039178 patent/WO2011153505A1/en active Application Filing
- 2011-06-03 BR BR112012023314A patent/BR112012023314A2/en not_active IP Right Cessation
- 2011-06-03 AU AU2011261259A patent/AU2011261259B2/en active Active
- 2011-06-03 US US13/153,301 patent/US20120030047A1/en not_active Abandoned
- 2011-06-03 CN CN2011800150126A patent/CN102939613A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070276765A1 (en) * | 2004-09-07 | 2007-11-29 | Hazel Patrick K | Method and system for secured transactions |
Also Published As
| Publication number | Publication date |
|---|---|
| US20120030047A1 (en) | 2012-02-02 |
| BR112012023314A2 (en) | 2018-07-24 |
| AU2011261259A1 (en) | 2012-10-04 |
| CN102939613A (en) | 2013-02-20 |
| WO2011153505A1 (en) | 2011-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2011261259B2 (en) | Payment tokenization apparatuses, methods and systems | |
| US11250352B2 (en) | Secure anonymous transaction apparatuses, methods and systems | |
| US11715097B2 (en) | Cloud-based virtual wallet NFC apparatuses, methods and systems | |
| US11900359B2 (en) | Electronic wallet checkout platform apparatuses, methods and systems | |
| US20120158589A1 (en) | Social Media Payment Platform Apparatuses, Methods and Systems | |
| US20120316992A1 (en) | Payment privacy tokenization apparatuses, methods and systems | |
| US20140279474A1 (en) | Multi-purse one card transaction apparatuses, methods and systems | |
| US20130144785A1 (en) | Social network payment authentication apparatuses, methods and systems | |
| US20130218765A1 (en) | Graduated security seasoning apparatuses, methods and systems | |
| AU2012261904A1 (en) | Virtual wallet card selection apparatuses, methods and systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FGA | Letters patent sealed or granted (standard patent) |