US20120123924A1 - Virtual currency configuration apparatuses, methods and systems - Google Patents
Virtual currency configuration apparatuses, methods and systems Download PDFInfo
- Publication number
- US20120123924A1 US20120123924A1 US13/278,163 US201113278163A US2012123924A1 US 20120123924 A1 US20120123924 A1 US 20120123924A1 US 201113278163 A US201113278163 A US 201113278163A US 2012123924 A1 US2012123924 A1 US 2012123924A1
- Authority
- US
- United States
- Prior art keywords
- user
- currency
- virtual
- merchant
- sale price
- 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.)
- Abandoned
Links
Images
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/38—Payment protocols; Details thereof
- G06Q20/384—Payment protocols; Details thereof using social networks
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
-
- 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
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
-
- 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/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- 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/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/127—Shopping or accessing services according to a time-limitation
-
- 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/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- 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/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3224—Transactions dependent on location of M-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/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/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/327—Short range or proximity payments by means of M-devices
- G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
-
- 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/327—Short range or proximity payments by means of M-devices
- G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
-
- 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/327—Short range or proximity payments by means of M-devices
- G06Q20/3278—RFID or NFC payments by means of M-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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
-
- 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/381—Currency conversion
-
- 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/385—Payment protocols; Details thereof using an alias or single-use codes
-
- 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/386—Payment protocols; Details thereof using messaging services or messaging apps
-
- 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/405—Establishing or using transaction specific rules
-
- 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
-
- 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- 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
-
- 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]
-
- 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]
- G06Q30/0641—Shopping interfaces
-
- 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
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/01—Social networking
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/70—Game security or game management aspects
- A63F13/79—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
- A63F13/792—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories for payment purposes, e.g. monthly subscriptions
Definitions
- the entire contents of the aforementioned applications are expressly incorporated by reference herein.
- the present innovations generally address apparatuses, methods, and systems for electronic commerce, and more particularly, include VIRTUAL CURRENCY CONFIGURATION APPARATUSES, METHODS AND SYSTEMS (“VCC”).
- Consumers engaging in transactions typically select a product from a store shelf or website, and then check them out at a checkout counter or webpage.
- Product information is typically selected from a webpage catalog or entered into a point-of-sale terminal device.
- the consumer utilizes a payment option, such as cash, check, credit card, or debit card, to pay for the transaction.
- a payment option such as cash, check, credit card, or debit card
- the point-of-sale terminal device memorializes the transaction in the merchant's computer system, and a receipt is generated indicating satisfactory consummation of the transaction.
- FIG. 1 shows a block diagram illustrating example aspects of flexible monetization services in some embodiments of the VCC
- FIG. 2 shows a block diagram illustrating an example VCC component configuration in some embodiments of the VCC
- FIGS. 3A-E show user interface diagrams illustrating example features of standalone app and web interfaces for a virtual wallet application in some embodiments of the VCC;
- FIGS. 4A-E show user interface diagrams illustrating example features of a flexible monetization service web browser interface in some embodiments of the VCC;
- FIGS. 5A-C show user interface diagrams illustrating example features of dynamic payment optimization and virtual currency configuration, as part of providing flexible monetization services, in some embodiments of the VCC;
- FIGS. 6A-D show user interface diagrams illustrating example features of geographic transaction volume analytics in some embodiments of the VCC
- FIG. 7A-C show block and data flow diagrams illustrating an example purchase catalog browsing procedure in some embodiments of the VCC
- FIG. 8 shows a logic flow diagram illustrating example aspects of purchase catalog browsing in some embodiments of the VCC, e.g., a Purchase Catalog Browsing (“PCB”) component 800 ;
- PCB Purchase Catalog Browsing
- FIG. 9 shows a data flow diagram illustrating an example user purchase checkout procedure in some embodiments of the VCC
- FIG. 10 shows a logic flow diagram illustrating example aspects of user purchase checkout in some embodiments of the VCC, e.g., a User Purchase Checkout (“UPC”) component woo;
- UPC User Purchase Checkout
- FIGS. 11A-B show data flow diagrams illustrating an example flexible monetization service procedure in some embodiments of the VCC
- FIGS. 12A-B shows logic flow diagrams illustrating example aspects of flexible monetization service in some embodiments of the VCC, e.g., a Flexible Monetization Service (“FMS”) component 1200 ;
- FMS Flexible Monetization Service
- FIGS. 13A-F show block and logic flow diagrams illustrating example aspects of virtual currency configuration in some embodiments of the VCC, e.g., a Virtual Currency Configuration (“VCC”) component 1300 ;
- VCC Virtual Currency Configuration
- FIG. 14 shows a logic flow diagram illustrating example aspects of dynamic payment optimization in some embodiments of the VCC, e.g., a Dynamic Payment Optimization (“DPO”) component 1400 ;
- DPO Dynamic Payment Optimization
- FIGS. 15A-B show data flow diagrams illustrating an example purchase transaction authorization procedure in some embodiments of the VCC
- FIGS. 16A-B show logic flow diagrams illustrating example aspects of purchase transaction authorization in some embodiments of the VCC, e.g., a Purchase Transaction Authorization (“PTA”) component 1600 ;
- PTA Purchase Transaction Authorization
- FIGS. 17A-D show block and data flow diagrams illustrating an example person-2-person social network marketing procedure in some embodiments of the VCC
- FIGS. 18A-B shows logic flow diagrams illustrating example aspects of person-2-person social network marketing in some embodiments of the VCC, e.g., a Person-2-Person (P2P) Social Network Marketing (“P2P-SNM”) component 1800 ;
- P2P Person-2-Person
- P2P-SNM Social Network Marketing
- FIGS. 19A-B show data flow diagrams illustrating an example purchase transaction clearance procedure in some embodiments of the VCC
- FIGS. 20A-B show logic flow diagrams illustrating example aspects of purchase transaction clearance in some embodiments of the VCC, e.g., a Purchase Transaction Clearance (“PTC”) component 2000 ;
- PTC Purchase Transaction Clearance
- FIG. 21 shows a data flow diagram illustrating an example geographic transaction volume analytics procedure in some embodiments of the VCC
- FIG. 22 shows a logic flow diagram illustrating example aspects of geographic transaction volume analytics in some embodiments of the VCC, e.g., a Geographic Transaction Volume Analytics (“GTVA”) component 2200 ; and
- GTVA Geographic Transaction Volume Analytics
- FIG. 23 shows a block diagram illustrating embodiments of a VCC controller.
- VCC Virtual Currency Configuration
- VCC VIRTUAL CURRENCY CONFIGURATION APPARATUSES, METHODS AND SYSTEMS
- B2C Business-to-consumer
- B2C Business-to-consumer
- ARPU Average Revenue Per User
- the VCC implements a flexible monetization platform based on a completely new way of thinking about how to monetize different types of users at various price points and at different life cycle stages of customers' engagement with the content offered. It calls for a 360-degree view of a customer who is looking to access and consume content across devices, platforms and networks. For example, when a lot of AAA content is available for free, merely setting a $14.99 monthly subscription price point and up-sell buckets may limit revenue generation capabilities. Consumers may want to pay at their own pace and at the price point they can afford. Thus, in some embodiments, the VCC enables a disruptive business model of microtransactions, which unlocks a massive consumer base that could become paying customers.
- FIG. 1 shows a block diagram illustrating example aspects of flexible monetization services in some embodiments of the VCC.
- the VCC may provide merchants and/or users with a variety of features to facilitate an expedited shopping experience.
- a user e.g., 101
- a user e.g., 101
- an online website e.g., a gaming site, a gaming application, an eCommerce website, etc.
- a merchant e.g., 102
- a payment network e.g., a credit card company
- the VCC may provide a stack of application services, from which the merchant can select according to the merchant's needs.
- the VCC may provide applications that can be customized by the merchants to provide the appearance that the provided service is seamlessly integrated with the merchant's systems, while outsourcing the processing associated with those services provided by the VCC.
- the VCC may provide application services that can automatically customize themselves according to the needs of the user, e.g., as adjudged by transaction analytics and/or the like user behavior analysis, e.g., 114 .
- FIG. 2 shows a block diagram illustrating an example VCC component configuration in some embodiments of the VCC.
- the VCC may enable online commerce sites to utilize a third party solution as a service to manage, operate and maintain the various components used in conducting and facilitating online transactions.
- the VCC may provide merchants with a variety of application services to enhance the consumer shopping experience during purchase product catalog browsing, e.g., 201 , user purchase checkout, e.g., 202 , purchase transaction authorization, e.g., 203 , and/or purchase transaction clearance, e.g., 204 .
- the merchant may make requests for such services to the VCC via a flexible monetization services interface, e.g., 205 .
- the VCC may provide an application programming interface (API) for the merchant to request such services.
- API application programming interface
- a service provided by the VCC may include, e.g., 206 a , the ability to select from a plurality of payment service providers (PSP) for routing the transaction, but from the same user interface, see e.g., FIGS. 4A-E .
- the VCC may offer a large variety of payment methods to users, and determine what methods to offer to what segment of the user base in specific countries to maximize conversion.
- the VCC may manage a vast amount of technical integrations with PSPs, but obfuscate the differences by presenting the merchant with a single integration. Each PSP may have its own interfaces and APIs and so the complexity in providing a unified customer experience may be large.
- the VCC may handle this complexity to present a unified consistent experience to consumers making purchasing transactions.
- This unified integration may take the form of either API integration in some embodiments, or the use of widgets or front end pages that manage the payments on behalf of the merchant in other embodiments.
- the VCC may have a translation module that repurposes all the various integration, settlement, and use of third party PSPs into a common infrastructure. Because of this unified User Interface and unified integration APIs, the the VCC may allow the continued addition or updating of payment customers without requiring that the merchants make updates or changes to their integration or billing systems.
- a service provided by the VCC may include, e.g., 206 b , risk management services for the user and/or merchant, including fraud detection and prevention, identity theft, and/or the like.
- the VCC may manage risk by using a comprehensive fraud engine to monitor and prevent and minimize the number of fraudulent transactions that occur.
- the Fraud Engine may gather information from multiple sources such as third party fraud services such as negative file databases, AVS matching services, device fingerprinting services and/or the like.
- the Fraud Engine may combine these various data points as well as analyzes historical data to create heuristics and rules to prevent fraudulent transactions from occurring.
- the VCC in some embodiments, may also provide a number of on-demand reports that help merchants gain insight into the incidence of fraud on their site and tune and configure their detection rules to better prevent fraud while maintaining a positive customer experience.
- a service provided by the VCC may include, e.g., 206 c , micro-payment and subscription services.
- the VCC may include an electronic wallet that maintains stored value balances for user accounts either in the form of real world balances or virtual currency balances. These balances may be broken down and tracked according to the method of payment made to create the balance such that the merchants can gain visibility into the actual cost basis for any user's balance.
- the VCC may further include subscription, and recurring billing engines and related features such as automatic entitlement delivery, overdue bill collection and event notifications.
- the VCC may include tracking of account balances, spend tracking, billing and/or product subscriptions, product offers and/or recommendations, event notifications, and/or the like.
- a service provided by the VCC may include in-app optimization, e.g., 206 d .
- the front end user experience around the presentation of purchasing options may be optimized by the VCC for the individual user in order to maximize the likelihood of a user completing a transaction.
- One such method that may be used by the VCC in some embodiments is lightbox (pop-up) front end UI that is embedded on the merchants site through the use of for example, javascript. Users who click the Buy button may experience a pop-up window that is seamlessly integrated into the merchant site, with a look and feel that is customized to the merchant site.
- the Lightbox may have a dynamic user interface that reorders the payment methods in the order that is most likely to have a user complete a transaction based on the users demographic information as well as historic data around users purchasing activity and payment method preferences. For example, users in country A may see payment option X and Y listed first, because those methods convert highly in country A, whereas a user in Country B may see payment options Z listed first because that method converts highly in country B.
- the VCC may provide features to modify the front-end user experience of a user purchasing a product to maximize the likelihood of the user completing the purchase and/or returning to the merchant's site for additional purchases.
- the VCC may allow for configuration of the user interface according to the user's demographics, behavior, location, language, payment preferences (either specific to the user, or generally for the user's demographic), and/or the like.
- the VCC may provide storefronts and/or marketplaces for users to browse products for purchase. Before a user can make a payment, they need to see which items they desire to purchase.
- the VCC may include a presentation layer and front end user interface in the form of a storefronts (app stores/marketplace) where items are presented to users.
- the VCC may further provide the necessary backend infrastructure to enable storefronts to function such as inventory management modules, catalog and offer management modules, merchandizing modules, coupon code and discount promotion modules, inclusion of virtual currency wallet across games, one-click purchases, recommendation engine, search engine.
- VCC may provide back-end services for the merchants, including inventory management, product search, advertisement placement, offer managements, consumer purchase incentives such as rewards or discounts, and/or the like.
- the VCC may provide analytics for the merchant based on card transaction data obtained from users purchasing products from the merchant, e.g., 206 f .
- the VCC may also allow developers to develop third-party apps that may be provided by the VCC to merchants via an application service store for the merchants.
- the VCC may provide a Developer Console that gives clients the information they need in a unified fashion for all aspects of the MaaS stack. Reports and data include products, pricing or revenue by payment method and/or country, spending patterns, free-to-paid conversion and ARPU metrics.
- the VCC may provide customer support services, such as on-demand live video/text chat, and/or the like services, for the users, e.g., 206 g .
- the VCC may facilitate a Developer Console that provides role based permissions to allow users of different levels to access different parts of the platform.
- One such level may be a customer support representative who can gain access to user transaction data to assist them with any issues, but would not gain access to other information such as revenue reports.
- the customer support tools may include ability for CS reps to issue refunds, look up pending transactions as well as whitelist or black list users.
- FIGS. 3A-E show user interface diagrams illustrating example features of standalone app and web interfaces for a virtual wallet application in some embodiments of the VCC.
- a virtual wallet mobile app e.g., 311
- a device e.g., 300
- the app may include an app interface providing various features for the user.
- the device may include a camera via which the app may acquire image frames, video data, live video, and/or the like, e.g., 316 .
- the app may be configured to analyze the incoming data, and search, e.g., 312 , for a product identifier, e.g., 314 , such as barcodes, QR codes and/or the like.
- the app may be configured to automatically detect, e.g., 312 , the presence of a product identifier within an image or video frame grabbed by the device (e.g., via a webcam, in-built camera, etc.). For example, the app may provide a “hands-free” mode of operation wherein the user may move the device to bring product identifiers within the field of view of the image/video capture mechanism of the device, and the app may perform image/video processing operations to automatically detect the product identifier within the field of view.
- the app may overlay cross-hairs, target box, and/or like alignment reference markers, e.g., 315 , so that a user may align the product identifier using the reference markers to facilitate product identifier recognition and interpretation.
- the detection of a product identifier may trigger various operations to provide products, services, information, etc. for the user.
- the app may be configured to detect and capture a QR code having embedded merchant and/or product information, and utilize the information extracted from the QR code to process a transaction for purchasing a product from a merchant.
- the app may be configured to provide information on related products, quotes, pricing information, related offers, (other) merchants related to the product identifier, rewards/loyalty points associated with purchasing the product related to the product identifier, analytics on purchasing behavior, alerts on spend tracking, and/or the like.
- the app may include user interface elements to allow the user to manually search, e.g., 313 , for products (e.g., by name, brand, identifier, etc.).
- the app may provide the user with the ability to view prior product identifier captures (see, e.g., 317 a ) so that the user may be able to better decide which product identifier the user desires to capture.
- the app may include interface elements to allow the user to switch back and forth between the product identification mode and product offer interface display screens (see, e.g., 317 b ), so that a user may accurately study deals available to the user before capturing a product identifier.
- the user may be provided with information about products, user settings, merchants, offers, etc. in list form (see, e.g., 317 c ) so that the user may better understand the user's purchasing options.
- Various other features may be provided for in the app (see, e.g., 317 d ).
- the user may desire to cancel product purchasing; the app may provide the user with a user interface element (e.g., 318 ) to cancel the product identifier recognition procedure and return to the prior interface screen the user was utilizing.
- the app may include an indication of the location (e.g., name of the merchant store, geographical location, information about the aisle within the merchant store, etc.) of the user, e.g., 321 .
- the app may provide an indication of a pay amount due for the purchase of the product, e.g., 322 .
- the app may provide various options for the user to pay the amount for purchasing the product(s).
- the app may utilize GPS coordinates associated with the device to determine the merchant store within which the user is present, and direct the user to a website of the merchant.
- the app may be configured to make an application programming interface (“API”) call to participating merchants to directly facilitate transaction processing for purchases.
- API application programming interface
- a merchant-branded app may be developed with an in-app purchasing mode, which may directly connect the user into the merchant's transaction processing system.
- the user may choose from a number of cards (e.g., credit cards, debit cards, prepaid cards, etc.) from various card providers, e.g., 323 a .
- the app may provide the user the option to pay the purchase amount using funds included in a bank account of the user, e.g., a checking, savings, money market, current account, etc., e.g., 323 b .
- the user may have set default options for which card, bank account, etc. to use for the purchase transactions via the app.
- such setting of default options may allow the user to initiate the purchase transaction via a single click, tap, swipe, and/or other remedial user input action, e.g., 323 c .
- the app may utilize the default settings of the user to initiate the purchase transaction.
- the app may allow the user to utilize other accounts (e.g., GoogleTM Checkout, PaypalTM account, etc.) to pay for the purchase transaction, e.g., 323 d .
- the app may allow the user to utilize rewards points, airline miles, hotel points, electronic coupons, printed coupons (e.g., by capturing the printed coupons similar to the product identifier) etc., to pay for the purchase transaction, e.g., 323 e .
- the app may provide an option to provide express authorization before initiating the purchase transaction, e.g., 324 .
- the app may provide a progress indicator provide indication on the progress of the transaction after the user has selected an option to initiate the purchase transaction, e.g., 325 .
- the app may provide the user with historical information on the user's prior purchases via the app, e.g., 327 a .
- the app may provide the user with an option to share information about the purchase (e.g., via email, SMS, wall posting on Facebook®, tweet on TwitterTM, etc.) with other users and/or control information shared with the merchant, acquirer, payment network etc., to process the purchase transaction, e.g., 327 b .
- the app may provide the user an option to display the product identification information captured by the client device (e.g., in order to show a customer service representative at the exit of a store the product information), e.g., 327 c .
- the user, app, device and or purchase processing system may encounter an error in the processing. In such scenarios, the user may be able to chat with a customer service representative (e.g., VerifyChat 327 d ) to resolve the difficulties in the purchase transaction procedure.
- a customer service representative e.g., VerifyChat 327 d
- the user may select to conduct the transaction using a one-time anonymized credit card number, see e.g., 323 f .
- the app may utilize a pre-designated anonymized set of card details (see, e.g., “AnonCard1,” “AnonCard2”).
- the app may generate, e.g., in real-time, a one-time anonymous set of card details to securely complete the purchase transaction (e.g., “Anon It 1X”).
- the app may automatically set the user profile settings such that the any personal identifying information of the user will not be provided to the merchant and/or other entities.
- the user may be required to enter a user name and password to enable the anonymization features.
- the user interface elements of the app may be advantageously arranged to provide the user the ability to process a purchase with customized payment parameters with a minimum number of user inputs applied to the user's device. For example, if the user has a QR pay code, e.g., 332 , within the viewing angle of a camera included in the user's mobile device, the user may activate a user interface element to snap the QR code. In some embodiments, the user may control the field of view of the camera using a user interface zoom element, e.g., 333 .
- the user interface may be designed such that the user may touch an image of a QR code displayed on the screen to capture the QR code (see e.g., 334 ).
- the position of the user's touch may be utilized as an input by an image processing module executing on the user's device to process the displayed video frame (and/or adjacent video frames), and extract the QR code from the frame(s) based on the user's input.
- the user's touch may provide an approximate center point of the QR code.
- the image processing module may be able to better perform an automated QR code image recognition, and accordingly capture the correct QR code (e.g., if portions of many QR codes are displayed within the video frame(s)) selected by the user for capture and processing.
- the app may utilize predetermined default settings for a particular merchant, e.g., 331 , to process the purchase based on the QR code (e.g., in response to the user touching an image of a QR code displayed on the screen of the user device).
- the user may activate a user interface element 335 (or e.g., press and continue to hold the image of the QR code 332 ).
- the app may provide a pop-up menu, e.g., 337 , providing a variety of payment customization choices, such as those described with reference to FIG. 3B .
- the user may, e.g., drag the user's finger to the appropriate settings the user prefers, and release the user's finger from the touchscreen of the user's mobile device to select the setting for payment processing.
- the payment settings options, e.g., 337 , and QR capture activation button, e.g., 336 may be included in the user interface along with a window for capturing the QR code via the mobile device's camera.
- the user's mobile device may generate a hybrid QR code-payment settings graphic, and the POS terminal (or user's trusted computing device) may capture the entire graphic for payment processing.
- the app may provide a user interface element 338 for the user to minimize the payment options settings user interface elements.
- the app may provide additional user interface elements, e.g., 339 , to display previous purchases, data shared about those purchases, purchase receipts (e.g., via barcodes) and customer support options (e.g., VerifyChat).
- additional user interface elements e.g., 339
- purchase receipts e.g., via barcodes
- customer support options e.g., VerifyChat
- the user may be able to view and/or modify the user profile and/or settings of the user, e.g., by activating user interface element 322 (of FIG. 3B ).
- the user may be able to view/modify a user name (e.g., 341 a - b ), account number (e.g., 342 a - b ), user security access code (e.g., 343 a - b ), user pin (e.g., 344 a - b ), user address (e.g., 345 a - b ), social security number associated with the user (e.g., 346 a - b ), current device GPS location (e.g., 347 a - b ), user account of the merchant in whose store the user currently is (e.g., 348 a - b ), the user's rewards accounts (e.g., 349 a
- a user name e.g., 341
- the user may be able to select which of the data fields and their associated values should be transmitted to facilitate the purchase transaction, thus providing enhanced data security for the user.
- the user has selected the name 341 a , account number 342 a , security code 343 a , merchant account ID 348 a and rewards account ID 349 a as the fields to be sent as part of the notification to process the purchase transaction.
- the user may toggle the fields and/or data values that are sent as part of the notification to process the purchase transactions.
- the app may provide multiple screens of data fields and/or associated values stored for the user to select as part of the purchase order transmission.
- the app may obtain the GPS location of the user. Based on the GPS location of the user, the app may determine the context of the user (e.g., whether the user is in a store, doctor's office, hospital, postal service office, etc.). Based on the context, the app may present the appropriate fields to the user, from which the user may select fields and/or field values to send as part of the purchase order transmission.
- the app may determine the context of the user (e.g., whether the user is in a store, doctor's office, hospital, postal service office, etc.). Based on the context, the app may present the appropriate fields to the user, from which the user may select fields and/or field values to send as part of the purchase order transmission.
- a user may go to doctor's office and desire to pay the co-pay for a doctor's appointment.
- the app may provide the user the ability to select to transfer medical records, health information, which may be provided to the medical provider, insurance company, as well as the transaction processor to reconcile payments between the parties.
- the records may be sent in a Health Insurance Portability and Accountability Act (HIPAA)-compliant data format and encrypted, and only the recipients who are authorized to view such records may have appropriate decryption keys to decrypt and view the private user information.
- HIPAA Health Insurance Portability and Accountability Act
- the app executing on the user's device may provide a “VerifyChat” feature for fraud prevention (e.g., by activating UI element 327 d in FIG. 3B ).
- the VCC may detect an unusual and/or suspicious transaction.
- the VCC may utilize the VerifyChat feature to communicate with the user, and verify the authenticity of the originator of the purchase transaction.
- the VCC may send electronic mail message, text (SMS) messages, Facebook® messages, TwitterTM tweets, text chat, voice chat, video chat (e.g., Apple FaceTime), and/or the like to communicate with the user.
- the VCC may initiate a video challenge for the user, e.g., 351 a .
- the user may need to present him/her-self via a video chat, e.g., 352 a .
- a customer service representative e.g., agent 355 a
- the VCC may utilize face, biometric and/or like recognition (e.g., using pattern classification techniques) to determine the identity of the user, e.g., 354 a .
- the app may provide reference marker (e.g., cross-hairs, target box, etc.), e.g., 353 a , so that the user may the video to facilitate the VCC's automated recognition of the user.
- the user may not have initiated the transaction, e.g., the transaction is fraudulent.
- the user may cancel, e.g., 358 a , the challenge.
- the VCC may then cancel the transaction, and/or initiate fraud investigation procedures on behalf of the user.
- the app may provide additional user interface elements, e.g., to display previous session 356 a , and provide additional customer support options (e.g., VerifyChat 357 a ).
- the VCC may utilize a text challenge procedure to verify the authenticity of the user, e.g., 351 b .
- the VCC may communicate with the user via text chat, SMS messages, electronic mail, Facebook® messages, TwitterTM tweets, and/or the like.
- the VCC may pose a challenge question, e.g., 352 b , for the user.
- the app may provide a user input interface element(s) (e.g., virtual keyboard 353 b ) to answer the challenge question posed by the VCC.
- the challenge question may randomly selected by the VCC automatically; in some embodiments, a customer service representative 355 b may manually communicate with the user.
- the user may not have initiated the transaction, e.g., the transaction is fraudulent.
- the user may cancel, e.g., 358 b , the text challenge.
- the VCC may then cancel the transaction, and/or initiate fraud investigation procedures on behalf of the user.
- the app may provide additional user interface elements, e.g., to display previous session 356 b , and provide additional customer support options (e.g., VerifyChat 357 b ).
- FIGS. 4A-E show user interface diagrams illustrating example features of a flexible monetization service web browser interface in some embodiments of the VCC.
- a light box 410 may be instantiated to complete a transaction (e.g., buying woo Gold Coins for $10.00) between a user and a merchant.
- the light box web interface may include various payment options 412 for selection by the user.
- Non-limiting examples of the payment options include credit and/or debit cards such as VISA, MASTERCARD, AMERICAN EXPRESS and DISCOVER, PAYPAL, bank account and/or personal check information, and/or the like.
- the payment options that may be provided may be based on the country where the transaction is conducted.
- the country option 411 may be pre-selected for the user or the user may change it.
- a series of fields 413 may be provided to the user for entering credit card details.
- Example fields of information required for purchase with credit card include name on card, address, city, state/region, zip/postal, country, and/or the like.
- the light box 410 may display a confirmation page.
- the confirmation page may provide a summary 415 of the transaction. For example, the payment option selected, the item purchased and the amount that was charged may be displayed to provide confirmation to the user that the purchase is complete. Other information such as more information on the UltimatePay 416 may also be provided on the same confirmation page view.
- a continue button 417 may also be provided to allow the user to return back to the page where he or she was previously on. In this way, the light box 410 may provide an integrated way to conduct a transaction using a variety of payment options from anywhere on a website and allow the user to return back to his or activity seamlessly.
- the PAYPAL option may be selected by the user from the variety of payment options 412 available to conduct a transaction.
- a user interface 418 customized for PAYPAL may be displayed to the user.
- the amount due may be pre-populated and a “check out with PALPAL” button 419 may be provided.
- a customized interface 420 as shown in FIG. 4D , may be provided within the light box showing payment information for user confirmation.
- the interface 420 may display purchase information 421 including description of the item(s) to be purchased, payment amount, payment method (e.g., PALPAL balance), payment currency, applicable discounts, and/or the like.
- the interface 420 may also include shipping and contact information 422 . Once the user reviews the displayed information and makes any necessary changes, the user may confirm payment with the “pay now” button 423 . This may conclude the transaction and a message 424 may be displayed informing the user that the user will be returned to the web page he or she was previously on before initiating the transaction (e.g., the PlaySpan marketplace). The user may also have the option to manually close the window and return to the previous web page.
- facilities may be provided by customizing the payment light box with different skins, payment options, logos, advertisement, and/or the like as shown by light boxes 425 and 426 .
- Such customizations may provide the appearance of a payment system that is seamlessly integrated with the merchant.
- FIGS. 5A-C show user interface diagrams illustrating example features of dynamic payment optimization and virtual currency configuration, as part of providing flexible monetization services, in some embodiments of the VCC.
- the VCC may facilitate optimization of the display and presentation of the most relevant payment options to a user based on parameters such as their country, age and purchasing behavior of users with similar transactional history.
- the VCC may include a selection engine that utilizes information gained from a payment gateway to get user behavior across different regions, age groups, locale, and applications (ecommerce websites, or sections of a website, or games). At an aggregate level, patterns of behavior across different applications may be used predictably by the VCC to select the most optimal payment list for a optimizing the users propensity to pay.
- VCC may know the most optimal payment list for 18-20 year olds playing strategy games historically and therefore may present those methods to a new user in that demographic. It further may refine that with regional information for 18-20 year old users from VS playing strategy games. Feedback in the form of users' input back to the VCC in turns of purchasing activities may allow the selection engine to self refine the component of the payments system and continually present optimal payment methods. All payment activities (anything from launching a payments application and abandoning to launching and making a payment) may be characterized by one or more attributes.
- Some attributes may be related to user profile information (locale, age, familiarity with the application, etc.), some may be application specific (game type, social dimensions, payment information/required, etc.), or region specific (what payment methods categorically convert better in different regions). All these attributes may be used to create patterns of behavior which ultimately result in a number of actions (abandoning application somewhere in the completion funnel, successfully finishing the payment process or starting over with some changes to the input). Mapping all of that data to the payments that were presented may give weight to accuracy of that presented selection list.
- the presentation of the payment options can be displayed to the user on a merchant in a number of ways.
- the merchant may send a query or API call to the payment provider that contains certain user demographic information such as age, location, item to be purchased, social networking ID or many others.
- the payment processing system may then compute, based on its algorithms and historic data, which payment methods are most likely to be the ones that will have the user complete a transaction.
- the VCC may generate an API list that the merchant receives for the recommended order list of payment method to display to users. This API can further include graphics such as payment logos, or know payment methods of a user such as for example a Visa Credit card ending with the last 4 digits of ABCD.
- the merchant may integrate a payment widget, lightbox, web-redirect or iframe to allow the payment processor to directly optimize the VI and front end user experience of the display of the methods.
- This could be through a simple list, or through a tabbed based approach. In the tab based approach the tabs selected and the methods that are shown by default may dynamically change based on the users demographic information.
- the VCC can further optimize the purchasing experience by adjusting language, price points, currencies, merchandizing (such as promotions or display ads) or the user interface and look and feel of the payment experience for the user.
- the VCC may tailor the purchasing experience dynamically for each individual user and can optimize and adjust a variety of parameters such as those listed above in order to create an experience that is most likely to have a user complete a transaction.
- the VCC can also favor particular payment methods if the merchant desires them to be given prominent placement if there are economic reasons or strategic preferences for favoring particular methods.
- One method that might be favored is an existing account balance of stored currency that the user already has. By presenting the stored currency as a payment option ahead of other payment options, users can complete the transaction with a simple one click and the merchant can then recognize the revenues from the utilization of the stored balance.
- facilities may be provided for customizing payment options according to geography (e.g., continent, country, region, etc.) 511 a , language and/or the like.
- geography e.g., continent, country, region, etc.
- the country Germany 511 b may be pre-selected or chosen by a user.
- payment options, language and currency information may be automatically updated to cater to the users of the selected country.
- language may be German or any of the world's most spoken languages 512 .
- payment options may be updated to show most popular payment methods in Germany or the highest converting payment methods 513 in Germany.
- the interface may also be updated to display localized currencies and price points 514 .
- an exemplary payment interface customized for the selected country Japan 521 is provided. While credit and/or debit card options such as VISA and AMERICAN EXPRESS and PAYPAL may be acceptable forms of payment in Japan or accepted by merchants, other country-specific payment choices 523 may also be provided under “more choices” tab 522 in the payment interface. The user may then select any of the provided choices for completing the transaction.
- credit and/or debit card options such as VISA and AMERICAN EXPRESS and PAYPAL may be acceptable forms of payment in Japan or accepted by merchants
- other country-specific payment choices 523 may also be provided under “more choices” tab 522 in the payment interface. The user may then select any of the provided choices for completing the transaction.
- payment options and ordering in mobile application interfaces may also be customized based on geography.
- the amount due 632 a may be displayed in the currency of the United States.
- Various payment options in the mobile application may displayed in an arrangement customized for (or in some instances by the user) in the region 533 a on the mobile application interface.
- the country selection is changed to Germany 531 b from the United States, the amount due 532 b may displayed in local or popular currency.
- various payment options and orderings may be modified as shown in the region 533 b of the mobile application interface.
- the highest converting payment methods may be provided.
- the user may configure the settings for a country and may save it for future use.
- various currency configurations may also be available in mobile interfaces of the payment system.
- a user may use Visa 542 a to pay for an amount due 541 a in United States currency.
- the user may also have the option to pay for the amount (or a portion thereof) using rewards points 542 b .
- the corresponding amount due may be displayed in currency points at 541 b.
- FIGS. 6A-D show user interface diagrams illustrating example features of geographic transaction volume analytics in some embodiments of the VCC.
- the VCC in some embodiments, may provide online merchant with services to visualize the geographic payment volumes through the display of a country heat map graph with configurable parameters to highlight different features of the payment distribution.
- the VCC may enable users to view their payments from users on a country-by-country basis, understanding market share for countries, e.g. US is 10% and Canada is 3%, total users, total payments and average payment size.
- These analytics and insights may give merchants clues that they need to increase revenue streams in their commerce activities.
- this data may be provided graphically showing a global heat map with countries having more payments with a darker color and payments with few payments with a lighter color (or no color for no payments).
- the levels, color contrast and granularity of the map can be configured and may provide merchants with simple and quick ways to visualize the effectiveness of their commerce activities across geographic regions.
- the geographies shown are country maps and the levels of payments are segmented into five spectrums based on an exponential scale such that each darker color level represents twice the payment volume than the next level.
- the map may be divided into states, cities or districs and the color gradient can be a linear spectrum from light to dark and normalized to from the lowest paying location to the highest paying location,
- the graphical display may be populated, in one example, as follows: Each order and payment transaction may be tagged with an IP address and country stamp. Geopayments reports then created by the payment network by filtering all transactions for a given merchant, then aggregated by country, and counting the sum of users and transactions and calculating the country market share and average payment size.
- Graphic charts may be created by taking a map of the globe, aggregating payment volume and coloring different countries based on the market share of payments in that specific country.
- An example merchant analytics dashboard 610 may include various options for generating graphical and other representations 616 of analytics such as geographic transaction volume.
- Example options available for configuration include, without limitation, type of data 611 (e.g., users and transactions), service codes 612 (e.g., UT01-PBC Test Merchant), date range 613 (e.g., Sep. 20, 2010 to Oct. 20, 2010), frequency (e.g., daily, weekly, monthly, etc.), and/or the like to observe trends for users and transactions over time.
- the graphical display area 616 may further display the trends for transactions 617 and users 618 in graphical charts such as trend line and bar chart among others.
- the merchant may also change any of the parameters on the dashboard 610 on the fly, and click on update button 615 to generate a graphics for the updated parameters.
- email 619 , download or export facilities may also be available for the merchant to download raw or processed data in EXCEL, text, WORD, .CSV and other formats, as well as graphics in various graphic formats such as .bmp, .jpg, .jpeg/, .png, .gif, .PDF, and/or the like.
- the merchant may reconfigure his or her dashboard to select other data types such as revenue by payment method 621 .
- the merchant may also select another service code 622 , data range 623 and frequency 624 .
- updated graphical charts may be displayed on the graphical display area 626 .
- a pie chart 627 may be displayed showing a percentage breakdown of revenue for each payment method.
- a line chart 628 may also be displayed showing the daily revenue amount (y-axis) for each payment method over a period of time (x-axis) defined by the date range 623 .
- raw and/or processed data and graphics may be available for email 629 , export or download.
- a merchant may select revenue by country 631 data analysis.
- the merchant may also specify service codes 632 , date range 633 and frequency 634 .
- the graphical display area may display various graphical charts and maps showing revenue breakdown by country.
- the heat map 637 may identify, using color or other indicators, each country which produced a revenue in the range of 0-5%, 5-10%, 10-25%, 25-50% and higher than 50% during the defined time period. Other percentage ranges for revenue breakdown are contemplated and are within the scope of the payment system analytics.
- the graphical chart 638 may show the revenue amount (y-axis) over a period of time (x-axis) for each revenue producing country.
- dashboard 640 analytics 641 , customer service 642 , manage systems 643 and mobile apps 644 facilities may be integrated together in a single console.
- the merchant or service user in general
- the dashboard tab is selected, an overview of various analyses, data and charts may be provided. For example, sub-windows such as geopayments 645 , revenue 646 , conversion 647 and summary 648 may be displayed.
- the summary table 648 may include various columns of data such as date 648 a , revenue 648 b , users 648 c , transactions 648 d , average spending per user 648 e , average amount per transaction 648 f , conversion rate 648 g , and/or the like.
- the summary table may include data for a predefined time period (e.g., current month, current week).
- the data from the summary table may then be displayed using graphical charts in sub-windows such as the geopayments sub-window 645 , revenue 646 sub-window and conversion sub-window 647 .
- the geopayments sub-window 646 may display geographical heat maps of revenue described in FIG. 6C .
- the revenue window 646 may display a column chart of revenue amount 648 b (y-axis) plotted against date 648 a (x-axis).
- the conversion sub-window 647 may display a column chart that shows revenue 648 b on the left y-axis and conversion rate on the right y-axis plotted again date 648 a on the x-axis.
- the “view reports” option on any of the sub-windows may be selected for further data analysis and/or reconfiguration of one or more parameters.
- FIG. 7A-C show block and data flow diagrams illustrating an example purchase catalog browsing procedure in some embodiments of the VCC.
- the VCC may provide a foundation for merchandising items, subscriptions and other offers via a comprehensive and robust storefront component that supports a global universal catalog.
- the VCC may enable a merchant to manage multiple offerings, across multiple properties (online and/or mobile) in multiple formats (in-game, widgets, social network-based applications, etc). Within this context, merchants may be able to manage up to thousands of items, price promotions, up-sell and cross-sell opportunities in a global setting with payment and support in all areas.
- the VCC may provide a unique turn-key offering that leverages contextual offer management to drive higher conversion.
- the marketplace may be implemented in-game, on social networks and the web or across all three.
- the full suite of merchandising tools, coupons, custom offers, bundles, promotional pricing, analytics, etc., provided by the VCC may enable the merchant to maximize sales while providing a high quality experience to its customers.
- the VCC may provide features such as, but limited to: Virtual currency wallet across games; One-click purchases; Recommendation engine; Catalog and offer management; Comprehensive customer service and analytical tools; and/or the like. In some embodiments.
- the VCC may also enable merchants to profit from additional revenue streams as users transact among each other in an official and organized manner. These marketplaces may serve not only as additional revenue streams, but also may increase stickiness to the site by adding the social dimension of transaction and the promise of profiting from customer loyalty.
- a user may desire to browse through a product catalog of a merchant managed by the VCC.
- the user may provide a catalog browsing input, e.g., 711 , into a point-of-sale (PoS) client, e.g., 702 , to browse through a product catalog.
- PoS point-of-sale
- the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like.
- a single tap e.g., a one-tap mobile app purchasing embodiment
- keyboard entry e.g., a one-tap mobile app purchasing embodiment
- card swipe e.g., a RFID/NFC enabled hardware device
- a RFID/NFC enabled hardware device e.g., electronic card having multiple accounts, smartphone, tablet, etc.
- mouse clicks e.g., electronic card having multiple accounts, smartphone, tablet, etc.
- voice commands e.g., single
- the PoS client may generate a product search request, e.g., 712 , and provide the product search request, e.g., 713 , to a merchant/acquirer (“merchant”) server, e.g., 703 a .
- the client may provide a product search request to the merchant server as a HTTP(S) POST message including XML-formatted data.
- HTTP(S) POST message including XML-formatted data
- the merchant server may utilize the VCC to search through the merchant's inventory to respond to the user's product catalog browse request.
- the merchant server may provide a product search request, e.g., 714 , to a Monetization-as-a-Service (“MaaS”) server, e.g., 704 a .
- the merchant server may generate an application programming interface call to request the MaaS server to provide product catalog search results.
- the client may provide a product search request to the MaaS server as a HTTP(S) POST message including XML-formatted data.
- HTTP(S) POST message including XML-formatted data.
- the MaaS server may utilize a social network service to determine products to recommend for the user.
- the MaaS server may request the user 701 to log into the social networking service in order to enable the user social graph search.
- the MaaS server may request the social networking service to provide information on the user's communications on the social networking service, the user's social graph, and/or the social networking communications of the members of the user's social graph on the social networking service, e.g., 715 .
- the MaaS server may execute a PHP script to generate an application interface programming call to the social network server.
- An example listing of commands to generate a user social graph search request 715 written substantially in the form of PHP commands, is provided below:
- the social networking server may query, e.g., 716 , its own database (e.g., social network database 705 b ), and obtain the requested social search results, e.g., 717 , from its database.
- the social networking server may provide the retrieved information for the MaaS server, e.g., user social graph search results 718 .
- the social networking server may provide a JavaScript Object Notation format (“JSON”)-encoded data structure embodying the requested information.
- JSON JavaScript Object Notation format
- the MaaS server may query, e.g., 719 , its own database, e.g., MaaS database 704 b , for products matching the products search request key terms.
- the merchant server may obtain product catalog data, e.g., 720 , such as product information, product pricing, sales tax, offers, discounts, rewards, and/or other information to process the purchase transaction and/or provide value-added services for the user.
- the MaaS database may be a relational database responsive to Structured Query Language (“SQL”) commands.
- the MaaS server may execute a hypertext preprocessor (“PHP”) script including SQL commands to query a database table (such as FIG. 23 , Products 23191 ) for product data.
- PGP hypertext preprocessor
- the MaaS server may generate a product search response using the product catalog data and user social graph search results, e.g., 721 .
- the MaaS server may provide the product search response, e.g., 722 , to the merchant server as a response to the merchant server's product search request 714 .
- the MaaS server may provide the product search response to the merchant server as a HTTP(S) POST message including XML-formatted data.
- HTTP(S) POST message including XML-formatted data.
- the merchant server may provide the product search response, e.g., 723 , to the PoS client, which may display, e.g., 724 , the product search results to the user.
- the user may select a product from among the displayed products for purchase.
- the user may provide a product selection input, e.g., 725 , to indicate the user's desire to obtain the product.
- the PoS client may generate a product cart request, e.g., 726 , and provide the product cart request, e.g., 727 , to the merchant server, in response to obtaining the user's product selection input.
- the PoS client may generate a HTTP(S) POST message similar to the example above, and provide it to the merchant server.
- the merchant server may query its database, e.g., 728 , for prior product cart data, e.g., 729 .
- it may execute a hypertext preprocessor (“PHP”) script including SQL commands to query a database table (such as FIG. 23 , Products 23191 ) for product cart data.
- PHP/SQL commands An example product cart data query 728 , substantially in the form of PHP/SQL commands, is provided below:
- the merchant server may generate updated product data based on the product cart request, e.g., 730 , and store the updated product cart data in the merchant database, e.g., 731 .
- the merchant server may issue PHP/SQL commands to store the data to a database table (such as FIG. 23 , Products 23191 ).
- An example updated product cart store command 731 substantially in the form of PHP/SQL commands, is provided below:
- FIG. 8 shows a logic flow diagram illustrating example aspects of purchase catalog browsing in some embodiments of the VCC, e.g., a Purchase Catalog Browsing (“PCB”) component 800 .
- a user may desire to browse through a product catalog of a merchant managed by the VCC.
- the user may provide a catalog browsing input, e.g., 801 , into a point-of-sale (PoS) client to browse through a product catalog.
- PoS point-of-sale
- the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like.
- the PoS client may generate a product search request, e.g., 802 , and provide the product search request to a merchant/acquirer (“merchant”) server.
- a product search request e.g. 802
- the merchant server may utilize the VCC to search through the merchant's inventory to respond to the user's product catalog browse request.
- the merchant server may provide a product search request to a MaaS server.
- the merchant server may generate an application programming interface call to request the MaaS server to provide product catalog search results, e.g., 803 .
- the MaaS server may utilize a social network service to determine products to recommend for the user.
- the MaaS server may request the user to log into the social networking service in order to enable the user social graph search.
- the MaaS server may request the social networking service to provide information on the user's communications on the social networking service, the user's social graph, and/or the social networking communications of the members of the user's social graph on the social networking service, e.g., 804 .
- the social networking server may query its own database, e.g., 805 , and obtain the requested social search results from its database, e.g., 806 .
- the social networking server may provide the retrieved information for the MaaS server, e.g., 807 .
- the MaaS server may query its own database for products matching the products search request key terms, e.g., 808 .
- the merchant server may obtain product catalog data, such as product information, product pricing, sales tax, offers, discounts, rewards, and/or other information to process the purchase transaction and/or provide value-added services for the user.
- the MaaS server may generate a product search response using the product catalog data and user social graph search results, e.g., 810 .
- the MaaS server may provide the product search response to the merchant server as a response to the merchant server's product search request.
- the merchant server may provide the product search response to the PoS client, e.g., 811 , which may display the product search results to the user, e.g., 812 .
- the user may select a product from among the displayed products for purchase, e.g., 813 .
- the user may provide a product selection input to indicate the user's desire to obtain the product.
- the PoS client may generate a product cart request, e.g., 814 , and provide the product cart request to the merchant server, in response to obtaining the user's product selection input.
- the merchant server may generate updated product data based on the product cart request, e.g., 815 - 817 , and store the updated product cart data in the merchant database, e.g., 818 .
- FIG. 9 shows a data flow diagram illustrating an example user purchase checkout procedure in some embodiments of the VCC.
- a user e.g., Sola
- product a product, service, offering, and/or the like
- the user may communicate with a merchant/acquirer (“merchant”) server, e.g., 903 a , via a client such as, but not limited to: a personal computer, mobile device, television, point-of-sale terminal, kiosk, ATM, and/or the like (e.g., 902 ).
- a client such as, but not limited to: a personal computer, mobile device, television, point-of-sale terminal, kiosk, ATM, and/or the like (e.g., 902 ).
- the user may provide user input, e.g., checkout input 911 , into the client indicating the user's desire to purchase the product.
- the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like.
- a single tap e.g., a one-tap mobile app purchasing embodiment
- keyboard entry e.g., a one-tap mobile app purchasing embodiment
- card swipe e.g., a RFID/NFC enabled hardware device
- a RFID/NFC enabled hardware device e.g., electronic card having multiple accounts, smartphone, tablet, etc
- a user in a merchant store may scan a product barcode of the product via a barcode scanner at a point-of-sale terminal.
- the user may select a product from a webpage catalog on the merchant's website, and add the product to a virtual shopping cart on the merchant's website.
- the user may then indicate the user's desire to checkout the items in the (virtual) shopping cart.
- the user may activate a user interface element provided by the client to indicate the user's desire to complete the user purchase checkout.
- the client may generate a checkout request, e.g., 912 , and provide the checkout request, e.g., 913 , to the merchant server.
- the client may provide a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST message including the product details for the merchant server in the form of data formatted according to the eXtensible Markup Language (“XML”).
- HTTP(S) Secure Hypertext Transfer Protocol
- XML eXtensible Markup Language
- the merchant server may obtain the checkout request from the client, and extract the checkout detail (e.g., XML data) from the checkout request.
- the merchant server may utilize a parser such as the example parsers described below in the discussion with reference to FIG. 23 .
- the merchant server may extract product data (e.g., product identifiers), as well as available PoS client data, from the checkout request.
- the merchant server may query, e.g., 914 , a merchant/acquirer (“merchant”) database, e.g., 903 b , to obtain product data, e.g., 915 , such as product information, product pricing, sales tax, offers, discounts, rewards, and/or other information to process the purchase transaction and/or provide value-added services for the user.
- product data e.g., 915
- the merchant database may be a relational database responsive to Structured Query Language (“SQL”) commands.
- the merchant server may execute a hypertext preprocessor (“PHP”) script including SQL commands to query a database table (such as FIG. 23 , Products 23191 ) for product data.
- PGP hypertext preprocessor
- the merchant server may generate, e.g., 916 , checkout data to provide for the PoS client.
- checkout data e.g., 917
- HTML HyperText Markup Language
- the checkout data may be embodied, in part, in a Quick Response (“QR”) code image that the PoS client can display, so that the user may capture the QR code using a user's device to obtain merchant and/or product data for generating a purchase transaction processing request.
- a user alert mechanism may be built into the checkout data.
- the merchant server may embed a URL specific to the transaction into the checkout data.
- the alerts URL may further be embedded into optional level 3 data in card authorization requests, such as those discussed further below with reference to FIGS. 15-16 .
- the URL may point to a webpage, data file, executable script, etc., stored on the merchant's server dedicated to the transaction that is the subject of the card authorization request.
- the object pointed to by the URL may include details on the purchase transaction, e.g., products being purchased, purchase cost, time expiry, status of order processing, and/or the like.
- the merchant server may provide to the payment network the details of the transaction by passing the URL of the webpage to the payment network.
- the payment network may provide notifications to the user, such as a payment receipt, transaction authorization confirmation message, shipping notification and/or the like. In such messages, the payment network may provide the URL to the user device. The user may navigate to the URL on the user's device to obtain alerts regarding the user's purchase, as well as other information such as offers, coupons, related products, rewards notifications, and/or the like.
- An example listing of a checkout data 917 substantially in the form of XML-formatted data, is provided below:
- the merchant server may invoke a component to generate checkout data, such as the example flexible monetization service component discussed below with reference to FIGS. 11-12 .
- the PoS client may render and display, e.g., 918 , the checkout data for the user.
- FIG. 10 shows a logic flow diagram illustrating example aspects of user purchase checkout in some embodiments of the VCC, e.g., a User Purchase Checkout (“UPC”) component woo.
- a user may desire to purchase a product, service, offering, and/or the like (“product”), from a merchant via a merchant online site or in the merchant's store.
- the user may communicate with a merchant/acquirer (“merchant”) server via a PoS client.
- the user may provide user input, e.g., 1001 , into the client indicating the user's desire to purchase the product.
- the client may generate a checkout request, e.g., 1002 , and provide the checkout request to the merchant server.
- the merchant server may obtain the checkout request from the client, and extract the checkout detail (e.g., XML data) from the checkout request.
- the merchant server may utilize a parser such as the example parsers described below in the discussion with reference to FIG. 23 .
- the merchant server may extract product data (e.g., product identifiers), as well as available PoS client data, from the checkout request.
- the merchant server may query, e.g., 1003 , a merchant/acquirer (“merchant”) database to obtain product data, e.g., 1004 , such as product information, product pricing, sales tax, offers, discounts, rewards, and/or other information to process the purchase transaction and/or provide value-added services for the user.
- product data e.g., 1004
- the merchant server may generate, e.g., 1005 , checkout data to provide, e.g., 1006 , for the PoS client.
- the merchant server may invoke a component to generate checkout data, such as the example flexible monetization service component discussed below with reference to FIGS. 11-12 .
- the PoS client may render and display, e.g., 1007 , the checkout data for the user.
- FIGS. 11A-B show data flow diagrams illustrating an example flexible monetization service procedure in some embodiments of the VCC.
- a merchant server or other entity or component within the VCC may obtain a trigger, e.g., 1111 , to provide flexible monetization services (see, e.g., FIG. 9 , 916 ).
- the merchant server may parse the obtained trigger for providing P2P social network marketing service, and extract details of services required by the merchant to service the trigger. For example, the merchant may require to provide checkout services, including configuration the UI of the checkout page for the user, configuring the currency in which the purchase price is displayed in currencies available to the user, and/or the like.
- the merchant server may identify the services required to be performed to service the flexible monetization service trigger, and generate, e.g., 1112 , a flexible monetization service request based on identifying the required services.
- the merchant server may provide, e.g., 1113 , the flexible monetization service request to a MaaS server, e.g., 1104 a , for processing.
- the merchant server may provide a flexible monetization service request to the MaaS server as a HTTP(S) POST message including XML-formatted data.
- An example listing of a flexible monetization service request 1113 substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:
- the MaaS server may, in response to obtaining the flexible monetization service request, determine whether the merchant-user combination is authorized to utilize flexible monetization services. For example, the MaaS server may query, e.g., 1114 , a MaaS database, e.g., 1104 b , to determine whether the merchant and/or user are authorized to receive its services, e.g., 1115 . For example, the MaaS server may utilize PHP/SQL commands similar to those described previously to determine service authorization.
- the MaaS server may utilize the service authorization response, e.g., 1115 , to identify, e.g., 1116 , the services in which the merchant is enrolled which can be provided for the particular user shopping session for which the merchant obtained the flexible monetization service request.
- the MaaS server may provide a service authorization confirmation message (or retry message, if the MaaS server determines that the session is not authorized for services), e.g., 1117 , to the merchant server.
- the MaaS server may identify, among the enrolled services, the services associated with PoS notification/offer generation, e.g., 1119 .
- the MaaS server may obtain any service data, e.g., via PHP/SQL commands to its database as described previously, to obtain the data necessary to perform the services.
- the MaaS server may invoke components for each enrolled service associated with PoS notification/offer generation, e.g., 1112 .
- the MaaS server may invoke the VCC 1300 and DPO 1400 components described further below with reference to FIGS. 13 and 14 respectively.
- the MaaS server may generate, e.g., 1123 a checkout widget customized to a user purchase checkout session (e.g., a javascript or AJAX lightbox). For example, the MaaS server may generate a code listing similar to the example code listing provided below as the checkout widget 1124 :
- the MaaS server may provide the checkout widget, e.g., 1124 , to the merchant server, which may provide the widget back to the source of the trigger for flexible monetization services.
- FIGS. 12A-B shows logic flow diagrams illustrating example aspects of flexible monetization service in some embodiments of the VCC, e.g., a Flexible Monetization Service (“FMS”) component 1200 .
- a merchant server or other entity or component within the VCC may obtain a trigger, e.g., 1201 , to provide flexible monetization services (see, e.g., FIG. 9 , 916 ).
- the merchant server may parse the obtained trigger for providing P2P social network marketing service, and extract details of services required by the merchant to service the trigger.
- the merchant may require to provide checkout services, including configuration the UI of the checkout page for the user, configuring the currency in which the purchase price is displayed in currencies available to the user, and/or the like.
- the merchant server may identify the services required to be performed to service the flexible monetization service trigger, and generate, e.g., 1202 , a flexible monetization service request based on identifying the required services.
- the merchant server may provide the flexible monetization service request to a MaaS server for processing.
- the MaaS server may, in response to obtaining the flexible monetization service request, determine whether the merchant-user combination is authorized to utilize flexible monetization services.
- the MaaS server may query, e.g., 1203 , a MaaS database to determine whether the merchant and/or user are authorized to receive its services, e.g., 1204 .
- the MaaS server may utilize PHP/SQL commands similar to those described previously to determine service authorization.
- the MaaS server may utilize the service authorization response to identify, e.g., 1206 , the services in which the merchant is enrolled which can be provided for the particular user shopping session for which the merchant obtained the flexible monetization service request.
- the MaaS server may provide a service authorization confirmation message (or retry message, if the MaaS server determines that the session is not authorized for services), e.g., 1207 , to the merchant server.
- a service authorization confirmation message or retry message, if the MaaS server determines that the session is not authorized for services
- the MaaS server may identify, among the enrolled services, the services associated with PoS notification/offer generation, e.g., 1209 .
- the MaaS server may obtain any service data, e.g., via PHP/SQL commands to its database as described previously, to obtain the data necessary to perform the services, e.g., 1210 - 1211 .
- the MaaS server may invoke components for each enrolled service associated with PoS notification/offer generation, e.g., 1212 - 1213 .
- the MaaS server may invoke the VCC 1300 and DPO 1400 components described further below with reference to FIGS. 13 and 14 respectively.
- the MaaS server may generate, e.g., 1214 , a checkout widget customized to a user purchase checkout session (e.g., a javascript or AJAX lightbox).
- the MaaS server may provide the checkout widget, e.g., 1214 , to the merchant server, which may provide the widget back to the source of the trigger for flexible monetization services.
- FIGS. 13A-F show block and logic flow diagrams illustrating example aspects of virtual currency configuration in some embodiments of the VCC, e.g., a Virtual Currency Configuration (“VCC”) component 1300 .
- VCC Virtual Currency Configuration
- the VCC may allow for game developers to price and package their virtual currencies in multiple currencies and multiple payment methods. Price packaging may allow game developers the ability to specify ratios, discreet pricing and even “smart pricing”—which auto rounds virtual currency bundles. For example, game developers may configure virtual currency bundles.
- one or more virtual currencies and/or currency managent rules may be included in a virtual currency bundle, and wherein a discount level for any virtual currency bundle may vary based on a user-selected payment method, and a device type from where the user procures the virtual currency bundle. For example, a user purchasing using a preferred payment method such as a Visa credit crad may be offered a currency bundle of $1 to 1000 virtual game gold pieces, but only 750 gold pieces were they to select a check as a payment mechanism. Also, merchants may incentivize or decentivize users to obtain gold pieces through certain devices, applications, and/or other mechanisms.
- a preferred payment method such as a Visa credit crad
- merchants may incentivize or decentivize users to obtain gold pieces through certain devices, applications, and/or other mechanisms.
- a premium may be added, and the currency bundle may result in providing only 900 gold pieces instead of woo gold pieces in the above example.
- the merchant may provide 1250 gold pieces for the same $1.
- These virtual currency bundles may be specified by the merchant and/or other components and/or entities within the VCC.
- the VCC may manage ratios. For example, let's say that a game wants to see virtual currency for a ratio of $1 to 100. The VCC may automatically calculate virtual currency amounts, so that if you enter a payment for $ 5 , then 500 points is automatically created.
- the VCC may manage Discreet Pricing. For example, let's say that a game wants to give away more coins for money invested. Discreet pricing allows game developers to enter discreet point packages for different prices points. For example, the user might get 500 coins for $5, but 1,100 coins for $10 (a 100 coin bonus).
- a setting for each country, merchant, and/or product may specify the number of threshold digits that may be rounded. For example, in the US, aggregate analysis of consumer behavior may show that two-digit rounding to enhance and increase transaction throughput for 4-digit point levels. For example, if a strict conversion ratio for $10 would 1237 virtual coins, having a two-digit rounding for the 4-digit value may result in an amount of 1250 coins, with “50” being the last two digits allowed for threshold rounding.
- the VCC may adapt virtual currencies according to the costs of the payment method employed by the user.
- the game developer may utilize different discrete mobile price points across multiple carriers, and set ratios (or discrete points) so that the VCC can automatically calculate a discrete number of price points per carrier for each country and show the appropriate pricing to the user.
- a VCC may facilitate dividing up the available price points to maximize the range of payment options provided to the user, and then provide a set number of payment choices, and calculating the applicable virtual currency to display.
- the VCC may accommodate the above mentioned virtual currency use cases as follows:
- Virtual Currencies may be created by the game developer on a Developer Console.
- Virtual currencies may be configured with names, like “Coins” and virtual currency codes, which reference the virtual currency during API calls. Once a virtual currency has been created, the game developer may create pricing rules for the virtual currency.
- the virtual currency is ready for use.
- the game developer may sell the virtual currency on their service, and when the user clicks on “buy”; then the game developer may also pass a virtual currency code, to let the VCC know that the purchase is for a virtual currency configured in the VCC.
- the payment interface on the game developer's site may then allow the user to make the payment.
- the interface may show price packages in drop downs and buttons according to the rules set up in the developer console.
- the VCC may send a postback communication to the game developer that the payment is complete.
- the VCC may also pass the virtual currency code (so the game developer knows to credit the user with virtual currency), as well as the amount of virtual currency to credit.
- the virtual currency code and the virtual currency amount may be MD5 hashed, so that users can't tamper with or grant themselves extra virtual currency.
- an entity and/or component of the VCC may obtain a trigger for virtual currency configuration (e.g., MaaS server 1104 a in FIG. 11A ), e.g., 1301 .
- the VCC may obtain the trigger when a user requires on-demand modification of payment options in a UI (see e.g., FIG. 3B ).
- the VCC may obtain data on the product being purchased for which virtual currency configuration is sought, e.g., 1302 .
- the VCC may identify a set of currencies using which the user desires to pay for the product purchase, e.g., 1303 .
- the VCC may identify the specific type of rewards points and Japanese yen as the set of currencies to convert the purchase price into, from the present currency(ies) in which the pricing information is available. Based on identifying the set of currencies, the VCC may decompose the purchase price according to the share of identified currencies, e.g., 1304 . For example, if the purchase price is $10, for the example set of currencies above, the VCC may decompose the purchase prices into $4 for payment through rewards points, and $6 for payment through Japanese yen.
- the VCC may determine currency exchange rates for the virtual currency configuration based on one or more factors, which may include, but not be limited to: user device platform (e.g., mobile device, online game, eCommerce site, shopping in physical store, etc.), user payment method (e.g., debit, credit, etc.), and/or the like.
- user device platform e.g., mobile device, online game, eCommerce site, shopping in physical store, etc.
- user payment method e.g., debit, credit, etc.
- the VCC may determine the user's platform using communications forwarded to it from the PoS client where the user is engaged in the purchase transaction, e.g., 1305 .
- the VCC may also determine the user payment method being utilized for payment, e.g., using user payment selections made by the user at the PoS client being utilized for the purchase transactions, e.g., 1306 .
- the VCC may determine a currency conversion exchange rate for each of the set of currencies identified as being implicated in the virtual currency configuration. For example, the VCC may select a currency from the identified set of currencies for conversion, e.g., 1307 .
- the VCC may query a database for a conversion algorithm to utilize for the conversion, based on the user platform, payment method, selected currency, and/or the like. For example the VCC may query a database using PHP/SQL commands similar to the example described previously to obtain the conversion algorithm to utilize.
- conversion algorithms are described below.
- the VCC may utilize any single algorithm, or combinations of the algorithms in any sequence and to any portion of the conversion of the set of currencies, to convert the price from one currency to another
- one algorithm may assign a constant exchange rate, regardless of the total value of the purchase price.
- a discreet pricing algorithm may assign a variable exchange rate depending on the total value of the purchase price. For example, the exchange rate may be lowered (e.g., more beneficial to the user) when the total purchase price is higher than a threshold value, than when it the total purchase price is lower than the threshold value.
- the discreet pricing algorithm may, in some embodiments, utilize a plaurality of thresholds to generate virtual currency conversions.
- one algorithm, a smart pricing algorithm may round the value of any input passed to it to at least one significant digit.
- the inputs passed to the smart pricing algorithm may, in various embodiments, be the exchange rate calculated by another algorithm, a price calculated by another algorithm, a (portion of a) purchase price of a product, and/or the like.
- the VCC may utilize a pre-specified table for performing some of the currency conversions.
- the VCC may query a database for a conversion table for the identified currency conversions, using the user platform, payment method and conversion algorithms as keys for the query, e.g., 1309 .
- the VCC may compute a conversion currency equivalent of the share of the total purchase price.
- the conversion currency equivalent may be rounded using the smart pricing algorithm before being returned as a response to the trigger.
- the VCC may perform such currency conversions for each currency identified as belonging to the set of cureencies implicated in the virtual currency conversion.
- the VCC may return the conversion currency equivalents in a result data record as a response to the obtained trigger.
- FIG. 14 shows a logic flow diagram illustrating example aspects of dynamic payment optimization in some embodiments of the VCC, e.g., a Dynamic Payment Optimization (“DPO”) component 1400 .
- an entity and/or component of the VCC may obtain a trigger for dynamic payment optimization (e.g., MaaS server 1104 a in FIG. 11A ), e.g., 1401 .
- the VCC may obtain the trigger when a user requires on-demand modification of payment options in a UI (see e.g., FIG. 3B ).
- the VCC may obtain a checkout request for which payment UI is to be optimized (see e.g., FIG. 9 , 913 ), e.g., 1402 .
- the VCC may parse the checkout request, and identify user device attributes: type, orientation, screen size, resolution, etc., e.g., 1403 .
- the VCC may utilize parsers similar to the example parsers described below with reference to FIG. 23 .
- the VCC may parse the checkout request, and identify a user location (e.g., via IP address lookup), e.g., 1404 .
- the VCC may classify the location type of user's device location (e.g., urban, rural, etc.), for example, based on an lookup of the IP address of the user device, e.g., 1405 .
- the VCC may query a database for a user profile, and identify a set of user demographic(s), e.g., 1406 .
- the VCC may obtain demographic data such as, but not limited to: age group, gender, education level, political preferences, and/or other classifications.
- the VCC may query, e.g., 1407 , a database for a widget template (e.g., javascript, AJAX lightbox, etc.) using the user device attributes, user location, user location type, and user demographic(s) as key terms in the query.
- a widget template e.g., javascript, AJAX lightbox, etc.
- the VCC may be able to generate, using a template widget, a customized widget that is optimized based on the user device attributes, user location, user location type, and user demographic(s), among other attributes.
- the VCC may identify, e.g., 1408 , a merchant ID for the merchant, and query a database for merchant-specific customization (e.g., see skins in FIG. 4E ).
- the VCC may generate a user-merchant session specific widget using the obtained widget template (customized to the user, user device, user location, etc.) and merchant-specific customizations, e.g., 1409 .
- the VCC may return the user-merchant specific widget to source of obtained trigger, e.g., 1410 .
- the VCC may provide a notification of customizations to be performed for optimizing a user payment interface via an application programming interface (e.g., encoded in XML or JSON data format), as opposed to providing the customized interface itself.
- FIGS. 15A-B show data flow diagrams illustrating an example purchase transaction authorization procedure in some embodiments of the VCC.
- a user e.g., 1501 a
- product a product, service, offering, and/or the like
- the user may utilize a physical card, or a user wallet device, e.g., 1501 b , to access the user's virtual wallet account.
- the user wallet device may be a personal/laptop computer, cellular telephone, smartphone, tablet, eBook reader, netbook, gaming console, and/or the like.
- the user may provide a wallet access input, e.g., 1511 , into the user wallet device.
- the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like.
- the user wallet device may authenticate the user based on the user's wallet access input, and provide virtual wallet features for the user.
- the user wallet device may provide a transaction authorization input, e.g., 1514 , to a point-of-sale (“PoS”) client, e.g., 1502 .
- PoS point-of-sale
- the user wallet device may communicate with the PoS client via Bluetooth, Wi-Fi, cellular communication, one- or two-way near-field communication (“NFC”), and/or the like.
- the user may swipe the plastic card at the PoS client to transfer information from the plastic card into the PoS client.
- the PoS client may obtain, as transaction authorization input 1514 , track 1 data from the user's plastic card (e.g., credit card, debit card, prepaid card, charge card, etc.), such as the example track 1 data provided below:
- the user wallet device may provide payment information to the PoS client, formatted according to a data formatting protocol appropriate to the communication mechanism employed in the communication between the user wallet device and the PoS client.
- a data formatting protocol appropriate to the communication mechanism employed in the communication between the user wallet device and the PoS client.
- the PoS client may generate a card authorization request, e.g., 1515 , using the obtained transaction authorization input from the user wallet device, and/or product/checkout data (see, e.g., FIG. 9 , 915 - 917 ).
- a card authorization request 1515 substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:
- the card authorization request generated by the PoS client may include a minimum of information required to process the purchase transaction. For example, this may improve the efficiency of communicating the purchase transaction request, and may also advantageously improve the privacy protections provided to the user and/or merchant.
- the card authorization request may include at least a session ID for the user's shopping session with the merchant. The session ID may be utilized by any component and/or entity having the appropriate access authority to access a secure site on the merchant server to obtain alerts, reminders, and/or other data about the transaction(s) within that shopping session between the user and the merchant.
- the PoS client may provide the generated card authorization request to the merchant server, e.g., 1516 .
- the merchant server may forward the card authorization request to a MaaS server, e.g., 1504 a , for routing the card authorization request to the appropriate payment network for payment processing.
- a MaaS server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions.
- the merchant server may query a database, e.g., merchant/acquirer database 1503 b , for a network address of the payment gateway server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the merchant server may issue PHP/SQL commands to query a database table (such as FIG. 23 , Pay Gateways 2319 h ) for a URL of the MaaS server.
- a database table such as FIG. 23 , Pay Gateways 2319 h
- An example payment gateway address query 1517 substantially in the form of PHP/SQL commands, is provided below:
- the merchant/acquirer database may provide the requested payment gateway address, e.g., 1518 .
- the merchant server may forward the card authorization request to the MaaS server using the provided address.
- the MaaS server may invoke a component to provide one or more service associated with purchase transaction authorization.
- the MaaS server may invoke components for fraud prevention (see e.g., FIG. 2 , risk management 206 b ; VerifyChat, FIG. 3E ), loyalty and/or rewards, and/or other services for which the user-merchant combination is authorized.
- the MaaS server may forward the card authorization request to a pay network server, e.g., 1505 a , for payment processing.
- the MaaS server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions.
- the MaaS server may query a database, e.g., MaaS database 1504 b , for a network address of the payment network server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the MaaS server may issue PHP/SQL commands to query a database table (such as FIG. 23 , Pay Gateways 2319 h ) for a URL of the pay network server.
- An example payment network address query 1521 substantially in the form of PHP/SQL commands, is provided below:
- the payment gateway database may provide the requested payment network address, e.g., 1522 .
- the MaaS server may forward the card authorization request to the pay network server using the provided address, e.g., 1523 .
- the pay network server may process the transaction so as to transfer funds for the purchase into an account stored on an acquirer of the merchant.
- the acquirer may be a financial institution maintaining an account of the merchant.
- the proceeds of transactions processed by the merchant may be deposited into an account maintained by at a server of the acquirer.
- the pay network server may generate a query, e.g., 1524 , for issuer server(s) corresponding to the user-selected payment options.
- issuers issuer financial institutions
- banking institutions which issued the account(s) for the user.
- issuers may include, but not be limited to: credit card, debit card, prepaid card, checking, savings, money market, certificates of deposit, stored (cash) value accounts and/or the like.
- Issuer server(s), e.g., 1506 a of the issuer(s) may maintain details of the user's account(s).
- a database may store details of the issuer server(s) associated with the issuer(s).
- the pay network server may query a database, e.g., pay network database 1505 b , for a network address of the issuer(s) server(s), for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the merchant server may issue PHP/SQL commands to query a database table (such as FIG. 23 , Issuers 23190 for network address(es) of the issuer(s) server(s).
- An example issuer server address(es) query 1524 substantially in the form of PHP/SQL commands, is provided below:
- the pay network database may provide, e.g., 1525 , the requested issuer server data to the pay network server.
- the pay network server may utilize the issuer server data to generate funds authorization request(s), e.g., 1526 , for each of the issuer server(s) selected based on the pre-defined payment settings associated with the user's virtual wallet, and/or the user's payment options input, and provide the funds authorization request(s) to the issuer server(s).
- the funds authorization request(s) may include details such as, but not limited to: the costs to the user involved in the transaction, card account details of the user, user billing and/or shipping information, and/or the like.
- An example listing of a funds authorization request 1526 substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:
- an issuer server may parse the authorization request(s), and based on the request details may query a database, e.g., user profile database 1506 b , for data associated with an account linked to the user.
- the merchant server may issue PHP/SQL commands to query a database table (such as FIG. 23 , Accounts 2319 d ) for user account(s) data.
- An example user account(s) query 1527 substantially in the form of PHP/SQL commands, is provided below:
- the issuer server may determine whether the user can pay for the transaction using funds available in the account, 1529 . For example, the issuer server may determine whether the user has a sufficient balance remaining in the account, sufficient credit associated with the account, and/or the like. Based on the determination, the issuer server(s) may provide a funds authorization response, e.g., 1530 , to the pay network server. For example, the issuer server(s) may provide a HTTP(S) POST message similar to the examples above.
- the pay network server may request payment options again from the user (e.g., by providing an authorization fail message to the user device and requesting the user device to provide new payment options), and re-attempt authorization for the purchase transaction.
- the pay network server may abort the authorization process, and provide an “authorization fail” message to the merchant server, user device and/or client.
- the pay network server may obtain the funds authorization response including a notification of successful authorization, and parse the message to extract authorization details.
- the pay network server may invoke a component to provide value-add services for the user, e.g., 1531 .
- the pay network server may invoke a P2P social network marketing component to post a notification of the user's successful purchase of the product to a social profile of the user hosted by a social networking service.
- the pay network server may invoke the P2P social network marketing component to reward a different user whose social post via a social networking service caused the user to engage in the purchase transaction.
- the pay network server may invoke the example P2P social network marketing component discussed below with reference to FIGS. 17-18 .
- the pay network server may also generate a transaction data record from the authorization request and/or authorization response, and store the details of the transaction and authorization relating to the transaction in a transactions database.
- the pay network server may issue PHP/SQL commands to store the data to a database table (such as FIG. 23 , Transactions 2319 i ).
- An example transaction store command substantially in the form of PHP/SQL commands, is provided below:
- the pay network server may forward a transaction authorization response, e.g., 1532 , to the user wallet device, PoS client, and/or merchant server.
- the merchant may obtain the transaction authorization response, and determine from it that the user possesses sufficient funds in the card account to conduct the transaction.
- the merchant server may add a record of the transaction for the user to a batch of transaction data relating to authorized transactions.
- the merchant may append the XML data pertaining to the user transaction to an XML data file comprising XML data for transactions that have been authorized for various users, e.g., 1533 , and store the XML data file, e.g., 1534 , in a database, e.g., merchant database 404 .
- a batch XML data file may be structured similar to the example XML data structure template provided below:
- the server may also generate a purchase receipt, e.g., 1533 , and provide the purchase receipt to the client, e.g., 1535 .
- the client may render and display, e.g., 1536 , the purchase receipt for the user.
- the user's wallet device may also provide a notification of successful authorization to the user.
- the PoS client/user device may render a webpage, electronic message, text/SMS message, buffer a voicemail, emit a ring tone, and/or play an audio message, etc., and provide output including, but not limited to: sounds, music, audio, video, images, tactile feedback, vibration alerts (e.g., on vibration-capable client devices such as a smartphone etc.), and/or the like.
- FIGS. 16A-B show logic flow diagrams illustrating example aspects of purchase transaction authorization in some embodiments of the VCC, e.g., a Purchase Transaction Authorization (“PTA”) component 1600 .
- PTA Purchase Transaction Authorization
- a user may wish to utilize a virtual wallet account to purchase a product, service, offering, and/or the like (“product”), from a merchant via a merchant online site or in the merchant's store.
- product a physical card, or a user wallet device to access the user's virtual wallet account.
- the user wallet device may be a personal/laptop computer, cellular telephone, smartphone, tablet, eBook reader, netbook, gaming console, and/or the like.
- the user may provide a wallet access input, e.g., 1601 , into the user wallet device.
- the user input may include, but not be limited to: a single tap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreen interface, keyboard entry, card swipe, activating a RFID/NFC enabled hardware device (e.g., electronic card having multiple accounts, smartphone, tablet, etc.) within the user device, mouse clicks, depressing buttons on a joystick/game console, voice commands, single/multi-touch gestures on a touch-sensitive interface, touching user interface elements on a touch-sensitive display, and/or the like.
- the user wallet device may authenticate the user based on the user's wallet access input, and provide virtual wallet features for the user, e.g., 1602 - 1603 .
- the user wallet device may provide a transaction authorization input, e.g., 1604 , to a point-of-sale (“PoS”) client.
- PoS point-of-sale
- the user wallet device may communicate with the PoS client via Bluetooth, Wi-Fi, cellular communication, one- or two-way near-field communication (“NFC”), and/or the like.
- the user may swipe the plastic card at the PoS client to transfer information from the plastic card into the PoS client.
- the user wallet device may provide payment information to the PoS client, formatted according to a data formatting protocol appropriate to the communication mechanism employed in the communication between the user wallet device and the PoS client.
- the PoS client may obtain the transaction authorization input, and parse the input to extract payment information from the transaction authorization input, e.g., 1605 .
- the PoS client may utilize a parser, such as the example parsers provided below in the discussion with reference to FIG. 23 .
- the PoS client may generate a card authorization request, e.g., 1606 , using the obtained transaction authorization input from the user wallet device, and/or product/checkout data (see, e.g., FIG. 9 , 915 - 917 ).
- the PoS client may provide the generated card authorization request to the merchant server.
- the merchant server may forward the card authorization request to a MaaS server, for routing the card authorization request to the appropriate payment network for payment processing.
- the MaaS server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions.
- the merchant server may query a database, e.g., 1608 , for a network address of the payment gateway server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the merchant/acquirer database may provide the requested payment gateway address, e.g., 1610 .
- the merchant server may forward the card authorization request to the MaaS server using the provided address.
- the MaaS server may invoke a component to provide one or more service associated with purchase transaction authorization.
- the MaaS server may invoke components for fraud prevention (see e.g., FIG. 2 , risk management 206 b ; VerifyChat, FIG. 3E ), loyalty and/or rewards, and/or other services for which the user-merchant combination is authorized.
- the MaaS server may forward the card authorization request to a pay network server for payment processing, e.g., 1614 .
- the MaaS server may be able to select from payment networks, such as Visa, Mastercard, American Express, Paypal, etc., to process various types of transactions including, but not limited to: credit card, debit card, prepaid card, B2B and/or like transactions.
- the MaaS server may query a database, e.g., 1612 , for a network address of the payment network server, for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the payment gateway database may provide the requested payment network address, e.g., 1613 .
- the MaaS server may forward the card authorization request to the pay network server using the provided address, e.g., 1614 .
- the pay network server may process the transaction so as to transfer funds for the purchase into an account stored on an acquirer of the merchant.
- the acquirer may be a financial institution maintaining an account of the merchant.
- the proceeds of transactions processed by the merchant may be deposited into an account maintained by at a server of the acquirer.
- the pay network server may generate a query, e.g., 1615 , for issuer server(s) corresponding to the user-selected payment options.
- issuers issuer financial institutions
- banking institutions which issued the account(s) for the user.
- such accounts may include, but not be limited to: credit card, debit card, prepaid card, checking, savings, money market, certificates of deposit, stored (cash) value accounts and/or the like.
- Issuer server(s) of the issuer(s) may maintain details of the user's account(s).
- a database e.g., a pay network database, may store details of the issuer server(s) associated with the issuer(s).
- the pay network server may query a database, e.g., 1615 , for a network address of the issuer(s) server(s), for example by using a portion of a user payment card number, or a user ID (such as an email address) as a keyword for the database query.
- the pay network database may provide, e.g., 1616 , the requested issuer server data to the pay network server.
- the pay network server may utilize the issuer server data to generate funds authorization request(s), e.g., 1617 , for each of the issuer server(s) selected based on the pre-defined payment settings associated with the user's virtual wallet, and/or the user's payment options input, and provide the funds authorization request(s) to the issuer server(s).
- the funds authorization request(s) may include details such as, but not limited to: the costs to the user involved in the transaction, card account details of the user, user billing and/or shipping information, and/or the like.
- an issuer server may parse the authorization request(s), e.g., 1618 , and based on the request details may query a database, e.g., 1619 , for data associated with an account linked to the user.
- the issuer server may determine whether the user can pay for the transaction using funds available in the account, e.g., 1621 . For example, the issuer server may determine whether the user has a sufficient balance remaining in the account, sufficient credit associated with the account, and/or the like. Based on the determination, the issuer server(s) may provide a funds authorization response, e.g., 1622 , to the pay network server.
- a funds authorization response e.g., 1622
- the pay network server may request payment options again from the user (e.g., by providing an authorization fail message to the user device and requesting the user device to provide new payment options), and re-attempt authorization for the purchase transaction.
- the pay network server may abort the authorization process, and provide an “authorization fail” message to the merchant server, user device and/or client.
- the pay network server may obtain the funds authorization response including a notification of successful authorization, and parse the message to extract authorization details.
- the pay network server may invoke a component to provide value-add services for the user, e.g., 1623 .
- the pay network server may invoke a P2P social network marketing component to post a notification of the user's successful purchase of the product to a social profile of the user hosted by a social networking service.
- the pay network server may invoke the P2P social network marketing component to reward a different user whose social post via a social networking service caused the user to engage in the purchase transaction.
- the pay network server may invoke the example P2P social network marketing component discussed below with reference to FIGS. 17-18 .
- the pay network server may forward a transaction authorization response to the user wallet device, PoS client, and/or merchant server.
- the merchant may parse, e.g., 1624 , the transaction authorization response, and determine from it that the user possesses sufficient funds in the card account to conduct the transaction, e.g., 1625 , option“Yes.”
- the merchant server may add a record of the transaction for the user to a batch of transaction data relating to authorized transactions. For example, the merchant may append the XML data pertaining to the user transaction to an XML data file comprising XML data for transactions that have been authorized for various users, e.g., 1626 , and store the XML data file, e.g., 1627 , in a database.
- the server may also generate a purchase receipt, e.g., 1628 , and provide the purchase receipt to the client.
- the client may render and display, e.g., 1629 , the purchase receipt for the user.
- the user's wallet device may also provide a notification of successful authorization to the user.
- the PoS client/user device may render a webpage, electronic message, text/SMS message, buffer a voicemail, emit a ring tone, and/or play an audio message, etc., and provide output including, but not limited to: sounds, music, audio, video, images, tactile feedback, vibration alerts (e.g., on vibration-capable client devices such as a smartphone etc.), and/or the like.
- FIGS. 17A-D show block and data flow diagrams illustrating an example person-2-person social network marketing procedure in some embodiments of the VCC.
- the VCC may facilitate rewarding individual users of a social network for any sales activity that might arise from them posting, commenting or communicating with their friends on a social network on their personal purchasing activities, preferences or tastes.
- the VCC may implement an affiliate Tracking Server (referred to as Server) that may keep track of user's communications (posts, comments, update and the like) on a social network through integration to the social network server, API or platform.
- Server affiliate Tracking Server
- the affiliate Server may track the update, and its associated vendor, advertiser or product link in the communication.
- the affiliate Server may also track any user in the friend's network that clicks on that link. If any member from the social network who received or viewed the communication or from the users “social graph”) clicks on the link and lands on the vendor, advertiser or product site, the affiliate Server may credit the click-through to the user who created the original communication post.
- the affiliate Server may, in some embodiments, place tracking pixels on the advertisers/brand/vendor site. The tracking pixel may send further details if the referred user did any purchase activity or browsing activity.
- the affiliate Server may then attribute the credit related to the browsing of the site (click) or of the purchase (action) done by the referred user to the recommending user's (affiliate user's) account.
- the “Affiliate Server” Rewards module may reward the recommending user on the successful click or action (sale) to the second user (referred user) resulting from the recommending user propagating the vendor offering to the second user, through his/her Social Network communication.
- the reward may include one or more items selected from a group including a cash value, one or more virtual currency based rewards, or products, offers or coupons.
- This access could be granted in the form of adding a Facebook Affilate Application, or through the use of Facebook Connect on a website.
- the user is now incented to post to hislher social network about any products he/she finds appealing, or can endorse because such posts can not only infoml hislher friends about his/her preferences, but can also lead to affiliate rewards if his/her friends decide to click on the posts.
- the user posts a link that he/she recently purchased a pair of Levy Jeans. This post gets communicated to hundreds of the user's friends through Facebook's friend feed. Ten users click on the link to browse the Levy Jean's Website. Two of the then users make a jeans purchase of $50 each.
- Levy has agreed to reward an affiliate with $0.50 for every user who browses their site and 5% of the sales price for any purchase.
- the affiliate Server tracks the activity of the referred users on Levy's site and knows to reward the recommending user appropriately with $6.00 in this example.
- the affiliate Server may take a percentage of all rewards as a service fee, or may receive a service fee from the merchants independently.
- a MaaS server or other entity or component within the VCC may obtain a trigger, e.g., 1711 , to provide P2P social network marketing service (see, e.g., FIG. 15B , 1531 ).
- the MaaS server may parse the obtained trigger for provide P2P social network marketing service, and extract transaction details from the trigger, e.g., 1714 .
- the pay network may extract fields such as, but not limited to: session ID, timestamp, alters URL, user ID, PoS client type and address, purchased products, product pricing, offers redeemed in the purchase, coupons utilized in the purchase, rewards provided due to the purchase, merchant name, URL to the product on the merchant website, and/or the like.
- the MaaS server may generate a user social post request for a social networking service using the details of the purchase transactions extracted from the trigger and/or other communications (e.g., card authorization requests) associated with the trigger.
- the MaaS server may query, e.g., 1712 - 1713 , its own database (e.g., via PHP/SQL commands) to obtain a user ID of the user associated with the social networking service.
- the MaaS server may generate a user social post request, e.g., an API call, to the social networking server 1705 a .
- the MaaS server may utilize a HTTP(S) POST request message similar to the examples provided previously.
- the MaaS server may utilize an API provided by the social networking service.
- the MaaS server may execute a PHP script to make a call to the social networking service's API.
- An example listing for a user social post request 1715 substantially in the form of PHP commands, is provided below:
- the social networking service may generate a user profile social post command, e.g., 1716 , in response to obtaining the user social post request from the MaaS server.
- the social network server may provide a social post confirmation, e.g., 1717 , in response, to the MaaS server.
- the MaaS server may attempt to identify the source of the recommendation leading to the product purchase by the user. For example, the MaaS server may parse all of the communications it received with regard to the purchase transaction (e.g., flexible monetization service requests, card authorization requests and/or the like) to identify a source for the recommendations. In some embodiments, the MaaS server may identify a social post of another user, e.g., user 2 1701 a , as being part of the social search results that were presented to the user, which caused the user to engage in the purchase transaction (for example, the user performing the purchase transactions may have been in a similar situation to the user 701 in FIG.
- the MaaS server may identify a social post of another user, e.g., user 2 1701 a , as being part of the social search results that were presented to the user, which caused the user to engage in the purchase transaction (for example, the user performing the purchase transactions may have been in a similar situation to the user 701 in FIG.
- the MaaS server may determine whether a recommendation was from a social search result.
- the MaaS server may identify a user 2 associated with the social search result (e.g., a user 2 who posted the recommendation to the social network; a user on whose behalf the MaaS server generated a social post request, etc.), e.g., 1720 .
- the MaaS server may determine a reward to provide for the user 2 .
- the reward may include a crediting of real currency, virtual currency, an additional of rewards points, loyalty points, providing additional offers, recommendations, providing additional posts to the social profile of the user 2 on other related offers and/or products that user 2 may be interested in purchasing, and/or other benefits for the user 2 .
- the MaaS server may provide the social marketing credit request to an issuer server hosting an account of the user 2 , e.g., 1722 .
- the issuer server may, in response, generate a user account credit command, e.g., 1723 , to the issuer database, e.g., 1706 b .
- the issuer server may also provide a social marketing credit notification, e.g., 1724 , to a device of the user 2 , e.g., 1701 b , which may display, e.g., 1725 , the credit notification to the user 2 .
- a social marketing credit notification e.g., 1724
- a device of the user 2 e.g., 1701 b
- the issuer server may also provide a social marketing credit notification, e.g., 1724 , to a device of the user 2 , e.g., 1701 b , which may display, e.g., 1725 , the credit notification to the user 2 .
- FIGS. 18A-B shows logic flow diagrams illustrating example aspects of person-2-person social network marketing in some embodiments of the VCC, e.g., a Person-2-Person (P2P) Social Network Marketing (“P2P-SNM”) component 1800 .
- a MaaS server or other entity or component within the VCC may obtain a trigger, e.g., 1801 , to provide P2P social network marketing service (see, e.g., FIG. 15B , 1531 ).
- the MaaS server may parse the obtained trigger for provide P2P social network marketing service, and extract transaction details from the trigger.
- the pay network may extract fields such as, but not limited to: session ID, timestamp, alters URL, user ID, PoS client type and address, purchased products, product pricing, offers redeemed in the purchase, coupons utilized in the purchase, rewards provided due to the purchase, merchant name, URL to the product on the merchant website, and/or the like.
- the MaaS server may generate a user social post request for a social networking service using the details of the purchase transactions extracted from the trigger and/or other communications (e.g., card authorization requests) associated with the trigger.
- the MaaS server may query, e.g., 1802 - 1803 , its own database (e.g., via PHP/SQL commands) to obtain a user ID of the user associated with the social networking service.
- the MaaS server may generate a user social post request, e.g., an API call, to the social networking server 1805 - 1807 .
- the MaaS server may utilize a HTTP(S) POST request message similar to the examples provided previously.
- the MaaS server may utilize an API provided by the social networking service.
- the social networking service may generate a user profile social post command, e.g., 1808 , in response to obtaining the user social post request from the MaaS server.
- the social network server may provide a social post confirmation, e.g., 1810 , in response, to the MaaS server.
- the MaaS server may attempt to identify the source of the recommendation leading to the product purchase by the user. For example, the MaaS server may parse all of the communications it received with regard to the purchase transaction (e.g., flexible monetization service requests, card authorization requests and/or the like) to identify a source for the recommendations. In some embodiments, the MaaS server may identify a social post of another user, e.g., user 2 , as being part of the social search results that were presented to the user, which caused the user to engage in the purchase transaction (for example, the user performing the purchase transactions may have been in a similar situation to the user 701 in FIG.
- the MaaS server may identify a social post of another user, e.g., user 2 , as being part of the social search results that were presented to the user, which caused the user to engage in the purchase transaction (for example, the user performing the purchase transactions may have been in a similar situation to the user 701 in FIG.
- the MaaS server may determine, e.g., 1812 , whether a recommendation was from a social search result.
- the MaaS server may identify a user 2 associated with the social search result (e.g., a user 2 who posted the recommendation to the social network; a user on whose behalf the MaaS server generated a social post request, etc.), e.g., 1814 .
- the MaaS server may determine a reward to provide for the user 2 .
- the reward may include a crediting of real currency, virtual currency, an additional of rewards points, loyalty points, providing additional offers, recommendations, providing additional posts to the social profile of the user 2 on other related offers and/or products that user 2 may be interested in purchasing, and/or other benefits for the user 2 .
- the MaaS server may provide the social marketing credit request to an issuer server hosting an account of the user 2 , e.g., 1815 .
- the issuer server may, in response, generate a user account credit command, e.g., 1817 , to the issuer database.
- the issuer server may also provide a social marketing credit notification, e.g., 1816 , to a device of the user 2 , which may display, e.g., 1818 , the credit notification to the user 2 .
- FIGS. 19A-B show data flow diagrams illustrating an example purchase transaction clearance procedure in some embodiments of the VCC.
- a merchant server e.g., 1903 a
- the merchant server may initiate clearance of a batch of authorized transactions.
- the merchant server may generate a batch data request, e.g., 1911 , and provide the request, to a merchant database, e.g., 1903 b .
- the merchant server may utilize PHP/SQL commands similar to the examples provided above to query a relational database.
- the database may provide the requested batch data, e.g., 1912 .
- the server may generate a batch clearance request, e.g., 1913 , using the batch data obtained from the database, and provide, e.g., 1914 , the batch clearance request to an acquirer server, e.g., 1907 a .
- the merchant server may provide a HTTP(S) POST message including XML-formatted batch data in the message body for the acquirer server.
- the acquirer server may generate, e.g., 1915 , a batch payment request using the obtained batch clearance request, and provide, e.g., 1918 , the batch payment request to the pay network server, e.g., 1905 a .
- the pay network server may parse the batch payment request, and extract the transaction data for each transaction stored in the batch payment request, e.g., 1919 .
- the pay network server may store the transaction data, e.g., 1920 , for each transaction in a database, e.g., pay network database 1905 b .
- the pay network server may invoke a component to provide analytics based on the transactions of the merchant for whom purchase transaction are being cleared.
- the pay network server may invoke a geographic transaction volume analytics component, such as the example component discussed below with reference to FIGS. 21-22 .
- the pay network server may provide analytics-based value-added services for the merchant and/or the merchant's users.
- the pay network server may query, e.g., 1923 , a database, e.g., pay network database 1905 b , for an address of an issuer server.
- the pay network server may utilize PHP/SQL commands similar to the examples provided above.
- the pay network server may generate an individual payment request, e.g., 1925 , for each transaction for which it has extracted transaction data, and provide the individual payment request, e.g., 1925 , to the issuer server, e.g., 1906 a .
- the pay network server may provide an individual payment request to the issuer server(s) as a HTTP(S) POST message including XML-formatted data.
- An example listing of an individual payment request 1925 substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:
- the issuer server may generate a payment command, e.g., 1927 .
- the issuer server may issue a command to deduct funds from the user's account (or add a charge to the user's credit card account).
- the issuer server may issue a payment command, e.g., 1927 , to a database storing the user's account information, e.g., user profile database 1906 b .
- the issuer server may provide an individual payment confirmation, e.g., 1928 , to the pay network server, which may forward, e.g., 1929 , the funds transfer message to the acquirer server.
- An example listing of an individual payment confirmation 1928 substantially in the form of a HTTP(S) POST message including XML-formatted data, is provided below:
- the acquirer server may parse the individual payment confirmation, and correlate the transaction (e.g., using the request ID field in the example above) to the merchant.
- the acquirer server may then transfer the funds specified in the funds transfer message to an account of the merchant.
- the acquirer server may query, e.g. 1930 , an acquirer database 1907 b for payment ledger and/or merchant account data, e.g., 1931 .
- the acquirer server may utilize payment ledger and/or merchant account data from the acquirer database, along with the individual payment confirmation, to generate updated payment ledger and/or merchant account data, e.g., 1932 .
- the acquirer server may then store, e.g., 1933 , the updated payment ledger and/or merchant account data to the acquire database.
- FIGS. 20A-B show logic flow diagrams illustrating example aspects of purchase transaction clearance in some embodiments of the VCC, e.g., a Purchase Transaction Clearance (“PTC”) component 2000 .
- a merchant server may initiate clearance of a batch of authorized transactions.
- the merchant server may generate a batch data request, e.g., 2001 , and provide the request to a merchant database.
- the database may provide the requested batch data, e.g., 2002 .
- the server may generate a batch clearance request, e.g., 2003 , using the batch data obtained from the database, and provide the batch clearance request to an acquirer server.
- the acquirer server may parse, e.g., 2004 , the obtained batch clearance request, and generate, e.g., 2007 , a batch payment request using the obtained batch clearance request to provide, the batch payment request to a pay network server.
- the acquirer server may query, e.g., 2005 , an acquirer database for an address of a payment network server, and utilize the obtained address, e.g., 2006 , to forward the generated batch payment request to the pay network server.
- the pay network server may parse the batch payment request obtained from the acquirer server, and extract the transaction data for each transaction stored in the batch payment request, e.g., 2008 .
- the pay network server may store the transaction data, e.g., 2009 , for each transaction in a pay network database.
- the pay network server may invoke a component, e.g., 2010 , to provide analytics based on the transactions of the merchant for whom purchase transaction are being cleared.
- the pay network server may invoke a geographic transaction volume analytics component, such as the example component discussed below with reference to FIGS. 21-22 .
- the pay network server may query, e.g., 2011 , a pay network database for an address of an issuer server.
- the pay network server may generate an individual payment request, e.g., 2013 , for each transaction for which it has extracted transaction data, and provide the individual payment request to the issuer server.
- the issuer server may parse the individual payment request, e.g., 2014 , and generate a payment command, e.g., 2015 , based on the parsed individual payment request.
- the issuer server may issue a command to deduct funds from the user's account (or add a charge to the user's credit card account).
- the issuer server may issue a payment command, e.g., 2015 , to a database storing the user's account information, e.g., a user profile database.
- the issuer server may provide an individual payment confirmation, e.g., 2017 , to the pay network server, which may forward, e.g., 2018 , the individual payment confirmation to the acquirer server.
- the acquirer server may parse the individual payment confirmation, and correlate the transaction (e.g., using the request ID field in the example above) to the merchant.
- the acquirer server may then transfer the funds specified in the funds transfer message to an account of the merchant.
- the acquirer server may query, e.g. 2019 , an acquirer database for payment ledger and/or merchant account data, e.g., 2020 .
- the acquirer server may utilize payment ledger and/or merchant account data from the acquirer database, along with the individual payment confirmation, to generate updated payment ledger and/or merchant account data, e.g., 2021 .
- the acquirer server may then store, e.g., 2022 , the updated payment ledger and/or merchant account data to the acquire database.
- FIG. 21 shows a data flow diagram illustrating an example geographic transaction volume analytics procedure in some embodiments of the VCC.
- a pay network server e.g., 2105 a , or other entity or component within the VCC, may obtain a trigger to provide transaction-based analytics (see, e.g., FIG. 19A , 1921 ).
- An example listing of a trigger 211 substantially in the form of a XML-formatted data, is provided below:
- the pay network server may parse the obtained trigger for transaction-based analytics, and extract a merchant identifier from the trigger, e.g., 2112 .
- the pay network may extract a ‘merchant_id’ field from transaction data relating to a transaction involving the merchant, embedded in the obtained trigger.
- the pay network server may attempt to aggregate the transactions of the merchant to service the trigger.
- the trigger may provide filters, e.g., an indication of the type of transaction, time period of transaction, geographical region of transactions, and/or other attributes to be utilized in the transaction-based analytics.
- the pay network server may utilize the filters provided in the trigger data to query, e.g., 2113 , a pay network database, e.g., 2105 b , for transactions of the merchant.
- the pay network server may utilize PHP/SQL commands similar to those described previously to send the merchant transactions query 2113 to the pay network database.
- the pay network database may provide, e.g., 2114 , the merchant transactions data satisfying the filters provided by the trigger obtained by the pay network server.
- the pay network server may analyze the aggregated transaction data to generate the analytics.
- the pay network server may engage in an algorithm to provide a heat map of transactions in the US made by consumers using credit cards in an online environment, and provide a heat map, resolved at the level of cities within the US in .JPEG image and .XLS spreadsheet formats to the email address reports@merchant.com.
- the pay network server may provide, e.g., 2116 , the analytics results to the merchant acquirer server according to the instructions provided in the trigger, or using default settings if available.
- the merchant/acquirer server may be able to display the analytics results via a display system, and/or store, e.g., 2117 , the analytics results to a merchant/acquirer database, e.g., 2103 b.
- FIG. 22 shows a logic flow diagram illustrating example aspects of geographic transaction volume analytics in some embodiments of the VCC, e.g., a Geographic Transaction Volume Analytics (“GTVA”) component 2200 .
- a pay network server or other entity or component within the VCC may obtain a trigger, e.g., 2201 , to provide transaction-based analytics (see, e.g., FIG. 19A , 1921 ).
- the pay network server may parse the obtained trigger for transaction-based analytics, and extract a merchant identifier from the trigger, e.g., 2202 .
- the pay network may extract a ‘merchant_id’ field from transaction data relating to a transaction involving the merchant, embedded in the obtained trigger.
- the pay network server may attempt to aggregate the transactions of the merchant to service the trigger.
- the trigger may provide filters, e.g., an indication of the type of transaction, time period of transaction, geographical region of transactions, and/or other attributes to be utilized in the transaction-based analytics.
- the pay network server may utilize the filters provided in the trigger data to query, e.g., 2203 , a pay network database for transactions of the merchant.
- the pay network database may provide, e.g., 2203 - 2204 , the merchant transactions data satisfying the filters provided by the trigger obtained by the pay network server.
- the pay network server may analyze the aggregated transaction data to generate the analytics.
- the pay network server may engage in an algorithm to provide a heat map of transactions in the US made by consumers using credit cards in an online environment, and provide a heat map, resolved at the level of cities within the US in .JPEG image and .XLS spreadsheet formats to the email address reports@merchant.com.
- the pay network server may identify the parameters according to which to analyze the aggregated merchant transactions data, e.g., 2205 .
- the pay network server may select an identified parameters, e.g., 2206 , and generate a histogram of the number of transactions or transaction volume against all possible values of that parameter, e.g., 2207 .
- the pay network server may generate a histogram plotting the number of transaction or total value of transaction against a y-axis, and a set of all cities within the US plotted against the x-axis.
- the pay network server may generate a graphical representation of the histogram, e.g., 2208 .
- the pay network server may generate a map of the identified geographical region with a color scheme to represent volume/total value of transactions by resolvable region.
- the pay network server may generate bar graphs, pie charts, and/or like graphical representations, regardless of the type of parameter identified for analytics.
- the pay network server may perform such histogram analysis, see e.g., 2209 , option “Yes,” for each identified parameter in the obtained trigger.
- the pay network server may generate an analytics results package for the merchant, e.g., 2210 .
- the pay network server may provide the analytics results to the merchant acquirer server according to the instructions provided in the trigger, or using default settings if available.
- the merchant/acquirer server may be able to display the analytics results via a display system, e.g., 2211 , and/or store, e.g., 2212 , the analytics results to a merchant/acquirer database.
- FIG. 23 shows a block diagram illustrating embodiments of a VCC controller 2301 .
- the VCC controller 2301 may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through various technologies, and/or other related data.
- processors 2303 may be referred to as central processing units (CPU).
- CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 2329 (e.g., registers, cache memory, random access memory, etc.).
- Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations.
- These stored instruction codes e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations.
- One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources.
- Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.
- the VCC controller 2301 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 2311 ; peripheral devices 2312 ; an optional cryptographic processor device 2328 ; and/or a communications network 2313 .
- the VCC controller 2301 may be connected to and/or communicate with users, e.g., 2333 a , operating client device(s), e.g., 2333 b , including, but not limited to, personal computer(s), server(s) and/or various mobile device(s) including, but not limited to, cellular telephone(s), smartphone(s) (e.g., iPhone®, Blackberry®, Android OS-based phones etc.), tablet computer(s) (e.g., Apple iPadTM, HP SlateTM, Motorola XoomTM, etc.), eBook reader(s) (e.g., Amazon KindleTM, Barnes and Noble's NookTM eReader, etc.), laptop computer(s), notebook(s), netbook(s), gaming console(s) (e.g., XBOX LiveTM, Nintendo® DS, Sony PlayStation® Portable, etc.), portable scanner(s), and/or the like.
- users e.g., 2333 a
- operating client device(s) e.g.,
- Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology.
- server refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.”
- client refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network.
- a computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a “node.”
- Networks are generally thought to facilitate the transfer of information from source points to destinations.
- a node specifically tasked with furthering the passage of information from a source to a destination is commonly called a “router.”
- There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc.
- LANs Local Area Networks
- WANs Wide Area Networks
- WLANs Wireless Networks
- the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.
- the VCC controller 2301 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 2302 connected to memory 2329 .
- a computer systemization 2302 may comprise a clock 2330 , central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 2303 , a memory 2329 (e.g., a read only memory (ROM) 2306 , a random access memory (RAM) 2305 , etc.), and/or an interface bus 2307 , and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 2304 on one or more (mother)board(s) 2302 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc.
- CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 2303
- a memory 2329 e.g., a read only memory (ROM) 2306 , a random access memory (RAM) 2305 ,
- the computer systemization may be connected to a power source 2386 ; e.g., optionally the power source may be internal.
- a cryptographic processor 2326 and/or transceivers (e.g., ICs) 2374 may be connected to the system bus.
- the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 2312 via the interface bus I/O.
- the transceivers may be connected to antenna(s) 2375 , thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing VCC controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like.
- a Texas Instruments WiLink WL1283 transceiver chip e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing VCC controller to determine its
- the system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways.
- the clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization.
- the clock and various components in a computer systemization drive signals embodying information throughout the system.
- Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications.
- These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. It should be understood that in alternative embodiments, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.
- the CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests.
- the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like.
- processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 2329 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1 , 2 , 3 , etc.), RAM, etc.
- the processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state.
- the CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s).
- the CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques.
- instruction passing facilitates communication within the VCC controller and beyond through various interfaces.
- distributed processors e.g., Distributed VCC
- mainframe multi-core
- parallel parallel
- super-computer architectures may similarly be employed.
- PDAs Personal Digital Assistants
- features of the VCC may be achieved by implementing a microcontroller such as CAST's R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like.
- some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology.
- ASIC Application-Specific Integrated Circuit
- DSP Digital Signal Processing
- FPGA Field Programmable Gate Array
- any of the VCC component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like.
- some implementations of the VCC may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.
- the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions.
- VCC features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx.
- Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the VCC features.
- a hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the VCC system designer/administrator, somewhat like a one-chip programmable breadboard.
- An FPGA's logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or simple mathematical operations.
- the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory.
- the VCC may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate VCC controller features to a final ASIC instead of or in addition to FPGAs.
- all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the VCC.
- the power source 2386 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy.
- the power cell 2386 is connected to at least one of the interconnected subsequent components of the VCC thereby providing an electric current to all subsequent components.
- the power source 2386 is connected to the system bus component 2304 .
- an outside power source 2386 is provided through a connection across the I/O 2308 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.
- Interface bus(ses) 2307 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 2308 , storage interfaces 2309 , network interfaces 2310 , and/or the like.
- cryptographic processor interfaces 2327 similarly may be connected to the interface bus.
- the interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization.
- Interface adapters are adapted for a compatible interface bus.
- Interface adapters conventionally connect to the interface bus via a slot architecture.
- Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.
- AGP Accelerated Graphics Port
- Card Bus Card Bus
- E Industry Standard Architecture
- MCA Micro Channel Architecture
- NuBus NuBus
- PCI(X) Peripheral Component Interconnect Express
- PCMCIA Personal Computer Memory Card International Association
- Storage interfaces 2309 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 2314 , removable disc devices, and/or the like.
- Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
- connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
- Network interfaces 2310 may accept, communicate, and/or connect to a communications network 2313 .
- the VCC controller is accessible through remote clients 2333 b (e.g., computers with web browsers) by users 2333 a .
- Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like.
- connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like.
- distributed network controllers e.g., Distributed VCC
- architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the VCC controller.
- a communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like.
- a network interface may be regarded as a specialized form of an input output interface.
- multiple network interfaces 2310 may be used to engage with various communications network types 2313 . For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.
- I/O 2308 may accept, communicate, and/or connect to user input devices 2311 , peripheral devices 2312 , cryptographic processor devices 2328 , and/or the like.
- I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HS), etc.
- One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used.
- the video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame.
- Another output device is a television set, which accepts signals from a video interface.
- the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).
- User input devices 2311 often are a type of peripheral device 2312 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
- peripheral device 2312 may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
- Peripheral devices 2312 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the VCC controller.
- Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 2328 ), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras).
- audio devices e.g., line-in, line-out, microphone input, speakers, etc.
- cameras e.g., still, video, webcam, etc.
- dongles e.g., for copy protection
- VCC controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.
- Cryptographic units such as, but not limited to, microcontrollers, processors 2326 , interfaces 2327 , and/or devices 2328 may be attached, and/or communicate with the VCC controller.
- a MC68HC16 microcontroller manufactured by Motorola Inc., may be used for and/or within cryptographic units.
- the MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation.
- Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions.
- Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used.
- Typical commercially available specialized cryptographic processors include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.
- the Broadcom's CryptoNetX and other Security Processors include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (
- any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 2329 .
- memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another.
- the VCC controller and/or a computer systemization may employ various forms of memory 2329 .
- a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation.
- memory 2329 will include ROM 2306 , RAM 2305 , and a storage device 2314 .
- a storage device 2314 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like.
- a computer systemization generally requires and makes use of memory.
- the memory 2329 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 2315 (operating system); information server component(s) 2316 (information server); user interface component(s) 2317 (user interface); Web browser component(s) 2318 (Web browser); database(s) 2319 ; mail server component(s) 2321 ; mail client component(s) 2322 ; cryptographic server component(s) 2320 (cryptographic server); the VCC component(s) 2335 ; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus.
- operating system component(s) 2315 operating system
- information server component(s) 2316 information server
- user interface component(s) 2317 user interface
- Web browser component(s) 2318 Web browser
- database(s) 2319 ; mail server component(s) 2321 ; mail client component(s) 2322 ; cryptographic server component
- non-conventional program components such as those in the component collection, typically, are stored in a local storage device 2314 , they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.
- the operating system component 2315 is an executable program component facilitating the operation of the VCC controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like.
- the operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Nan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems.
- Apple Macintosh OS X Server
- AT&T Nan 9 Be OS
- Unix and Unix-like system distributions such as AT&T's UNIX
- Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like
- Linux distributions such as
- an operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- the operating system may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like.
- the operating system may provide communications protocols that allow the VCC controller to communicate with other entities through a communications network 2313 .
- Various communication protocols may be used by the VCC controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.
- An information server component 2316 is a stored program component that is executed by a CPU.
- the information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like.
- the information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like.
- ASP Active Server Page
- ActiveX ActiveX
- ANSI Objective-
- C++ C#
- CGI Common Gateway Interface
- CGI Common Gateway Interface
- D hypertext markup language
- FLASH Java
- JavaScript JavaScript
- PROL Practical Extraction Report Language
- PGP
- the information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo!
- FTP File Transfer Protocol
- HTTP HyperText Transfer Protocol
- HTTPS Secure Hypertext Transfer Protocol
- SSL Secure Socket Layer
- messaging protocols e.g., America Online (A
- the information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components.
- DNS Domain Name System
- a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.”
- other information serving protocols may be employed across various ports, e.g., FTP communications across port 21 , and/or the like.
- An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the VCC database 2319 , operating systems, other program components, user interfaces, Web browsers, and/or the like.
- Access to the VCC database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the VCC.
- the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields.
- the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the VCC as a query.
- the results are passed over the bridge mechanism, and may be parsed formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser.
- an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- Computer interfaces in some respects are similar to automobile operation interfaces.
- Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status.
- Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces.
- GUIs Graphical user interfaces
- GUIs such as the Apple Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.
- KDE K Desktop Environment
- GNOME GNU Network Object Model Environment
- web interface libraries e.g., ActiveX
- a user interface component 2317 is a stored program component that is executed by a CPU.
- the user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed.
- the user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities.
- the user interface provides a facility through which users may affect, interact, and/or operate a computer system.
- a user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like.
- the user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- a Web browser component 2318 is a stored program component that is executed by a CPU.
- the Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like.
- Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like.
- Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices.
- a Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the VCC enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.
- a mail server component 2321 is a stored program component that is executed by a CPU 2303 .
- the mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like.
- the mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like.
- the mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like.
- the mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the VCC.
- Access to the VCC mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.
- a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
- a mail client component 2322 is a stored program component that is executed by a CPU 2303 .
- the mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like.
- Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like.
- a mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
- the mail client provides a facility to compose and transmit electronic mail messages.
- a cryptographic server component 2320 is a stored program component that is executed by a CPU 2303 , cryptographic processor 2326 , cryptographic processor interface 2327 , cryptographic processor device 2328 , and/or the like.
- Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU.
- the cryptographic component allows for the encryption and/or decryption of provided data.
- the cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption.
- PGP Pretty Good Protection
- the cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like.
- the cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like.
- digital certificates e.g., X.509 authentication
- the VCC may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network.
- the cryptographic component facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource.
- the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file.
- a cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like.
- the cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the VCC component to engage in secure transactions if so desired.
- the cryptographic component facilitates the secure accessing of resources on the VCC and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources.
- the cryptographic component communicates with information servers, operating systems, other program components, and/or the like.
- the cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- the VCC database component 2319 may be embodied in a database and its stored data.
- the database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data.
- the database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase.
- Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship.
- the VCC database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files.
- an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like.
- Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object.
- VCC database 2319 may be integrated into another component such as the VCC component 2335 .
- the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.
- the database component 2319 includes several tables 2319 a - o .
- a Users table 2319 a may include fields such as, but not limited to: user_id, ssn, dob, first_name, last_name, age, state, address_firstline, address_secondline, zipcode, devices_list, contact_info, contact_type, alt_contact_info, alt_contact_type, and/or the like.
- the Users table may support and/or track multiple entity accounts on a VCC.
- a Devices table 2319 b may include fields such as, but not limited to: device_ID, device_name, device_IP, device_MAC, device_type, device_model, device_version, device_OS, device_apps_list, device_securekey, wallet_app_installed_flag, and/or the like.
- An Apps table 2319 c may include fields such as, but not limited to: app_ID, app_name, app_type, app_dependencies, and/or the like.
- An Accounts table 2319 d may include fields such as, but not limited to: account_number, account_security_code, account_name, issuer_acquirer_flag, issuer_name, acquirer_name, account_address, routing_number, access_API_call, linked_wallets_list, and/or the like.
- a Merchants table 2319 e may include fields such as, but not limited to: merchant_id, merchant_name, merchant_address, ip_address, mac_address, auth_key, port_num, security_settings_list, and/or the like.
- An Issuers table 2319 f may include fields such as, but not limited to: issuer_id, issuer_name, issuer_address, ip_address, mac_address, auth_key, port_num, security_settings_list, and/or the like.
- An Acquirers table 2319 g may include fields such as, but not limited to: account_firstname, account_lastname, account_type, account_num, account_balance_list, billingaddress_line1, billingaddress_line2, billing_zipcode, billing_state, shipping_preferences, shippingaddress_line1, shippingaddress_line2, shipping_zipcode, shipping_state, and/or the like.
- a Pay Gateways table 2319 h may include fields such as, but not limited to: service_type, service_list, secure_ley, access_API_list, API_template_array, paygate_id, paygate_address, paygate_URL, paygate_name, payNET_id, payNET_address, payNET_URL, payNET_name, and/or the like.
- a Transactions table 2319 i may include fields such as, but not limited to: order_id, user_id, timestamp, transaction_cost, purchase_details_list, num_products, products_list, product_type, product_params_list, product_title, product_summary, quantity, user_id, client_id, client_ip, client_type, client_model, operating_system, os_version, app_installed_flag, user_id, account_firstname, account_lastname, account_type, account_num, account_priority_account_ratio, billingaddress_line1, billingaddress_line2, billing_zipcode, billing_state, shipping_preferences, shippingaddress_line1, shippingaddress_line2, shipping_zipcode, shipping_state, merchant_id, merchant_name, merchant_auth_key, and/or the like.
- a Batches table 2319 j may include fields such as, but not limited to: batch_id, transaction_id_list, timestamp_list, cleared_flag_list, clearance_trigger_settings, and/or the like.
- a Ledgers table 2319 k may include fields such as, but not limited to: request_id, timestamp, deposit_amount, batch_id, transaction_id, clear_flag, deposit_account, transaction_summary, payor_name, payor_account, and/or the like.
- a Products table 23191 may include fields such as, but not limited to: product_ID, product_title, product_attributes_list, product_price, tax_info_list, related_products_list, offers_list, discounts_list, rewards_list, merchants_list, merchant_availability_list, and/or the like.
- An Offers table 2319 m may include fields such as, but not limited to: offer_ID, offer_title, offer_attributes_list, offer_price, offer_expiry, related_products_list, discounts_list, rewards_list, merchants_list, merchant_availability_list, and/or the like.
- a Behavior Data table 2319 n may include fields such as, but not limited to: user_id, user_name, user_gaming_times_hist, user_gaming_list, user_product_purchase_categories_list, and/or the like.
- An Analytics table 23190 may include fields such as, but not limited to: merchant_id, timestamp, report_type, report_criterion_list, algorithm_list, results_array, and/or the like.
- a Social Graph table 2319 p may include fields such as, but not limited to: user_id, user_name, user_graph_list, graph_weight_list, user_friend_list, user_enemy_list, user_posts_list, and/or the like.
- a Recommendations table 2319 q may include fields such as, but not limited to: recommendation_id, recommendation_name, recommendsation_type, user_id, products_list, pricing_list, expriry_date, tax_info, and/or the like.
- a Currency Exchange table 2319 r may include fields such as, but not limited to: currency_id, currency_name, currency_type, algorithm_pref_list, threshold_values, base_currency, and/or the like.
- a Geographical Customizations table 2319 s may include fields such as, but not limited to: geo_id, geo_name, geo_UI customizations_list, geo_currnecy_customizations_list, and/or the like.
- the VCC database may interact with other database systems. For example, employing a distributed database system, queries and data access by search VCC component may treat the combination of the VCC database, an integrated data security layer database as a single database entity.
- user programs may contain various user interface primitives, which may serve to update the VCC.
- various accounts may require custom database tables depending upon the environments and the types of clients the VCC may need to serve. It should be noted that any unique fields may be designated as a key field throughout.
- these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 2319 a - o .
- the VCC may be configured to keep track of various settings, inputs, and parameters via database controllers.
- the VCC database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the VCC database communicates with the VCC component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.
- the VCC component 2335 is a stored program component that is executed by a CPU.
- the VCC component incorporates any and/or all combinations of the aspects of the VCC discussed in the previous figures. As such, the VCC affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.
- the VCC component may transform requests for on-demand and flexible monetization and related services via VCC components into currency transfers, purchase receipt notifications, social networking communications and transaction analytics reports, and/or the like and use of the VCC.
- the VCC component 2335 takes inputs (e.g., catalog browsing input 711 , product cart data 729 , product catalog 720 , social search results 717 , product selection input 725 , checkout request input 911 , product data 915 , service authorization response 1115 , service data 1121 , wallet access input 1511 , transaction authorization input 1514 , payment gateway address 1518 , payment network address 1522 , issuer server address(es) 1525 , user account(s) data 1528 , user profile data 1713 , batch data 1912 , payment network address 1916 , issuer server address(es) 1924 , payment ledger, merchant account data 1931 , merchant transactions data 2114 , and/or the like) etc., and transforms the inputs via various components (e.g., UPC 23
- the VCC component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo!
- Apache components Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET
- database adapters CGI scripts
- Java JavaScript
- mapping tools procedural and object
- the VCC server employs a cryptographic server to encrypt and decrypt communications.
- the VCC component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the VCC component communicates with the VCC database, operating systems, other program components, and/or the like.
- the VCC may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- any of the VCC node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment.
- the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.
- the component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.
- the configuration of the VCC controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.
- data referencing e.g., pointers
- internal messaging e.g., object instance variable communication, shared memory space, variable passing, and/or the like.
- API Application Program Interfaces
- DCOM Component Object Model
- D Distributed
- SOAP SOAP
- a grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.
- a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:
- Value1 is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value.
- a variable “Value1” may be inserted into an “http://” post command and then sent.
- the grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data.
- character e.g., tab
- inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data.
- parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.
- the VCC controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format.
- the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”).
- SQL Structured Query Language
- a virtual currency configuration processor-implemented method embodiment comprising:
- the identified virtual currency management rule includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency.
- the identified virtual currency management rule includes a smart pricing rule that specifies that the calculated sale price in the virtual currency be rounded to at least one significant digit.
- the identified virtual currency management rule includes a linear pricing rule that specifies a first constant virtual-to-real currency exchange rate up to a threshold sale price in the real currency, and a second constant virtual-to-real currency exchange rate above the threshold sale price in the real currency.
- the plurality of virtual currency management rules includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency, and a smart pricing rule.
- the merchant can create a plurality of virtual currencies for purchases from the merchant, and specify rules for currency conversion between the plurality of virtual currencies, wherein the plurality of currency management rules may be included in a virtual currency bundle, and wherein a discount level for any virtual currency bundle may vary based on a user-selected payment method and a device type from where the user procures the virtual currency bundle.
- a virtual currency configuration system embodiment comprising:
- a memory disposed in communication with the processor and storing processor-executable instructions to:
- the identified virtual currency management rule includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency.
- the identified virtual currency management rule includes a smart pricing rule that specifies that the calculated sale price in the virtual currency be rounded to at least one significant digit.
- the identified virtual currency management rule includes a linear pricing rule that specifies a first constant virtual-to-real currency exchange rate up to a threshold sale price in the real currency, and a second constant virtual-to-real currency exchange rate above the threshold sale price in the real currency.
- the plurality of virtual currency management rules includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency, and a smart pricing rule.
- the merchant can create a plurality of virtual currencies for purchases from the merchant, and specify rules for currency conversion between the plurality of virtual currencies, wherein the plurality of currency management rules may be included in a virtual currency bundle, and wherein a discount level for any virtual currency bundle may vary based on a user-selected payment method and a device type from where the user procures the virtual currency bundle.
- the identified virtual currency management rule includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency.
- the identified virtual currency management rule includes a smart pricing rule that specifies that the calculated sale price in the virtual currency be rounded to at least one significant digit.
- the identified virtual currency management rule includes a linear pricing rule that specifies a first constant virtual-to-real currency exchange rate up to a threshold sale price in the real currency, and a second constant virtual-to-real currency exchange rate above the threshold sale price in the real currency.
- the plurality of virtual currency management rules includes a discrete pricing rule that specifies a higher virtual-to-real currency exchange rate for larger amounts of the real currency, and a smart pricing rule.
- the merchant can create a plurality of virtual currencies for purchases from the merchant, and specify rules for currency conversion between the plurality of virtual currencies, wherein the plurality of currency management rules may be included in a virtual currency bundle, and wherein a discount level for any virtual currency bundle may vary based on a user-selected payment method and a device type from where the user procures the virtual currency bundle.
- a geographically-resolved transaction volume analytics processor-implemented method embodiment comprising:
- transaction volume is represented in the geographical heat map by varying a size of one or more countries on the heat map according to transaction volumes associated with the one or more countries.
- volume of transactions is defined as one of: a number of aggregated transactions; and a total sale price of aggregated transactions.
- volume of transactions is defined as a ratio of users transacting with the merchant to users visiting a website of the merchant.
- volume of transactions is defined as a number of aggregated transactions via a particular payment mechanism.
- a geographically-resolved transaction volume analytics system embodiment comprising:
- a memory disposed in communication with the processor and storing processor-executable instructions to:
- transaction volume is represented in the geographical heat map by varying a size of one or more countries on the heat map according to transaction volumes associated with the one or more countries.
- volume of transactions is defined as one of: a number of aggregated transactions; and a total sale price of aggregated transactions.
- volume of transactions is defined as a ratio of users transacting with the merchant to users visiting a website of the merchant.
- volume of transactions is defined as a number of aggregated transactions via a particular payment mechanism.
- transaction volume is represented in the geographical heat map by varying a size of one or more countries on the heat map according to transaction volumes associated with the one or more countries.
- volume of transactions is defined as one of: a number of aggregated transactions; and a total sale price of aggregated transactions.
- volume of transactions is defined as a ratio of users transacting with the merchant to users visiting a website of the merchant.
- volume of transactions is defined as a number of aggregated transactions via a particular payment mechanism.
- a person-to-person social network marketing processor-implemented method embodiment comprising:
- the product purchase request including an identifier of a user who made a communication about the product
- the credit includes one of: cash value; a virtual currency reward; a product; an offer for purchase of a product; and a coupon.
- a person-to-person social network marketing system embodiment comprising:
- a memory disposed in communication with the processor and storing processor-executable instructions to:
- the memory further storing instructions to:
- the credit includes one of: cash value; a virtual currency reward; a product; an offer for purchase of a product; and a coupon.
- the memory further storing instructions to:
- the product purchase request including an identifier of a user who made a communication about the product
- the credit includes one of: cash value; a virtual currency reward; a product; an offer for purchase of a product; and a coupon.
- a dynamic payment optimization processor-implemented method embodiment comprising:
- the at least one attribute of the user is at least one of: the user's age; an approximate location of the user; an experience level of the user with the online experience; and a prior behavioral pattern of the user.
- the at least one attribute of the online experience is at least one of: an online experience type, an online experience genre; and an online experience game level.
- the at least one attribute of the point of sale device is at least one of: an approximate location of the point of sale device; a type of the point of sale device; a display attribute of the point of sale device; an orientation of the point of sale device; and a default language setting associated with the point of sale device.
- customizing one or more properties of the user interface includes customizing a number of displayed user interface element within the user interface display.
- customizing one or more properties of the user interface includes modifying a set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- modifying the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request includes modifying an order of display of the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- customizing one or more properties of a user interface includes customizing a language utilized in the user interface display.
- customizing one or more properties of a user interface includes customizing a currency utilized for the user product purchase request.
- customizing one or more properties of a user interface includes customizing an ordering of payment options provided within the user interface.
- customizing one or more properties of a user interface includes customizing a logo displayed within the user interface.
- customizing one or more properties of a user interface includes customizing offer and product pricing displayed within the user interface.
- a dynamic payment optimization system embodiment comprising:
- a memory disposed in communication with the processor and storing processor-executable instructions to:
- the at least one attribute of the user is at least one of: the user's age; an approximate location of the user; an experience level of the user with the online experience; and a prior behavioral pattern of the user.
- the at least one attribute of the online experience is at least one of: an online experience type, an online experience genre; and an online experience game level.
- the at least one attribute of the point of sale device is at least one of: an approximate location of the point of sale device; a type of the point of sale device; a display attribute of the point of sale device; an orientation of the point of sale device; and a default language setting associated with the point of sale device.
- customizing one or more properties of the user interface includes customizing a number of displayed user interface element within the user interface display.
- customizing one or more properties of the user interface includes modifying a set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- modifying the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request includes modifying an order of display of the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- customizing one or more properties of a user interface includes customizing a language utilized in the user interface display.
- customizing one or more properties of a user interface includes customizing a currency utilized for the user product purchase request.
- customizing one or more properties of a user interface includes customizing an ordering of payment options provided within the user interface.
- customizing one or more properties of a user interface includes customizing a logo displayed within the user interface.
- customizing one or more properties of a user interface includes customizing offer and product pricing displayed within the user interface.
- the at least one attribute of the user is at least one of: the user's age; an approximate location of the user; an experience level of the user with the online experience; and a prior behavioral pattern of the user.
- the at least one attribute of the online experience is at least one of: an online experience type, an online experience genre; and an online experience game level.
- the at least one attribute of the point of sale device is at least one of: an approximate location of the point of sale device; a type of the point of sale device; a display attribute of the point of sale device; an orientation of the point of sale device; and a default language setting associated with the point of sale device.
- customizing one or more properties of the user interface includes customizing a number of displayed user interface element within the user interface display.
- customizing one or more properties of the user interface includes modifying a set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- modifying the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request includes modifying an order of display of the set of payment options displayed as available for initiating the purchase transaction related to the user product purchase request.
- customizing one or more properties of a user interface includes customizing a language utilized in the user interface display.
- customizing one or more properties of a user interface includes customizing a currency utilized for the user product purchase request.
- customizing one or more properties of a user interface includes customizing an ordering of payment options provided within the user interface.
- customizing one or more properties of a user interface includes customizing a logo displayed within the user interface.
- customizing one or more properties of a user interface includes customizing offer and product pricing displayed within the user interface.
- a flexible monetization service processor-implemented method embodiment comprising:
- the one or more services to conduct electronic transactions include at least one of: payment service provider transaction routing; risk management; micro-payment; subscription management; in-app optimization; storefronts and marketplaces; analytics; developer applications; virtual currency management; and customer support.
- a flexible monetization service system embodiment comprising:
- a memory disposed in communication with the processor and storing processor-executable instructions to:
- the one or more services to conduct electronic transactions include at least one of: payment service provider transaction routing; risk management; micro-payment; subscription management; in-app optimization; storefronts and marketplaces; analytics; developer applications; virtual currency management; and customer support.
- the one or more services to conduct electronic transactions include at least one of: payment service provider transaction routing; risk management; micro-payment; subscription management; in-app optimization; storefronts and marketplaces; analytics; developer applications; virtual currency management; and customer support.
- VCC VCC
- database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like various embodiments of the VCC may be implemented that enable a great deal of flexibility and customization.
- aspects of the VCC may be adapted for electronic service management, crowd-source management, order processing, and/or the like. While various embodiments and discussions of the VCC have been directed to electronic commerce, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/278,163 US20120123924A1 (en) | 2010-10-20 | 2011-10-20 | Virtual currency configuration apparatuses, methods and systems |
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US45537810P | 2010-10-20 | 2010-10-20 | |
US45537910P | 2010-10-20 | 2010-10-20 | |
US45538310P | 2010-10-20 | 2010-10-20 | |
US45545410P | 2010-10-21 | 2010-10-21 | |
US45611810P | 2010-11-02 | 2010-11-02 | |
US201161506425P | 2011-07-11 | 2011-07-11 | |
US13/278,163 US20120123924A1 (en) | 2010-10-20 | 2011-10-20 | Virtual currency configuration apparatuses, methods and systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120123924A1 true US20120123924A1 (en) | 2012-05-17 |
Family
ID=45975634
Family Applications (10)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/278,166 Abandoned US20120124496A1 (en) | 2010-10-20 | 2011-10-20 | Geographic volume analytics apparatuses, methods and systems |
US13/278,173 Abandoned US20120215701A1 (en) | 2010-10-20 | 2011-10-20 | Flexible monetization service apparatuses, methods and systems |
US13/278,163 Abandoned US20120123924A1 (en) | 2010-10-20 | 2011-10-20 | Virtual currency configuration apparatuses, methods and systems |
US13/278,171 Active US8571937B2 (en) | 2010-10-20 | 2011-10-20 | Dynamic payment optimization apparatuses, methods and systems |
US13/278,169 Abandoned US20120209677A1 (en) | 2010-10-20 | 2011-10-20 | Person-2-person social network marketing apparatuses, methods and systems |
US14/037,162 Abandoned US20140214653A1 (en) | 2010-10-20 | 2013-09-25 | Virtual Currency Subscriptions Apparatuses, Methods and Systems |
US14/037,131 Active 2033-08-28 US10688385B2 (en) | 2010-10-20 | 2013-09-25 | In-application universal storefront apparatuses, methods and systems |
US14/036,562 Active 2031-12-26 US9757644B2 (en) | 2010-10-20 | 2013-09-25 | Dynamic payment optimization apparatuses, methods and systems |
US15/701,391 Active US10500481B2 (en) | 2010-10-20 | 2017-09-11 | Dynamic payment optimization apparatuses, methods and systems |
US16/696,662 Active 2031-12-15 US11311797B2 (en) | 2010-10-20 | 2019-11-26 | Dynamic payment optimization apparatuses, methods and systems |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/278,166 Abandoned US20120124496A1 (en) | 2010-10-20 | 2011-10-20 | Geographic volume analytics apparatuses, methods and systems |
US13/278,173 Abandoned US20120215701A1 (en) | 2010-10-20 | 2011-10-20 | Flexible monetization service apparatuses, methods and systems |
Family Applications After (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/278,171 Active US8571937B2 (en) | 2010-10-20 | 2011-10-20 | Dynamic payment optimization apparatuses, methods and systems |
US13/278,169 Abandoned US20120209677A1 (en) | 2010-10-20 | 2011-10-20 | Person-2-person social network marketing apparatuses, methods and systems |
US14/037,162 Abandoned US20140214653A1 (en) | 2010-10-20 | 2013-09-25 | Virtual Currency Subscriptions Apparatuses, Methods and Systems |
US14/037,131 Active 2033-08-28 US10688385B2 (en) | 2010-10-20 | 2013-09-25 | In-application universal storefront apparatuses, methods and systems |
US14/036,562 Active 2031-12-26 US9757644B2 (en) | 2010-10-20 | 2013-09-25 | Dynamic payment optimization apparatuses, methods and systems |
US15/701,391 Active US10500481B2 (en) | 2010-10-20 | 2017-09-11 | Dynamic payment optimization apparatuses, methods and systems |
US16/696,662 Active 2031-12-15 US11311797B2 (en) | 2010-10-20 | 2019-11-26 | Dynamic payment optimization apparatuses, methods and systems |
Country Status (3)
Country | Link |
---|---|
US (10) | US20120124496A1 (fr) |
AU (3) | AU2011316955B2 (fr) |
WO (1) | WO2012054786A1 (fr) |
Cited By (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120109937A1 (en) * | 2010-10-28 | 2012-05-03 | Microsoft Corporation | Web services runtime for dataset transformation |
US20120150669A1 (en) * | 2010-12-13 | 2012-06-14 | Langley Garrett S | System and method for point of service payment acceptance via wireless communication |
US20130179341A1 (en) * | 2012-01-06 | 2013-07-11 | Bruce Boudreau | Virtual wallet |
US20130325701A1 (en) * | 2012-06-05 | 2013-12-05 | International Business Machines Corporation | E-currency validation and authorization services platform |
WO2013188820A2 (fr) * | 2012-06-15 | 2013-12-19 | Nyz Holdings Inc. | Appareil, procédés et produits manufacturés destinés à des transactions en monnaie virtuelle |
US20140006206A1 (en) * | 2012-06-29 | 2014-01-02 | Ebay, Inc. | Shopping Assistive Device and Commerce Infrastructure |
WO2014004342A2 (fr) * | 2012-06-29 | 2014-01-03 | Music One Live, Llc | Systèmes et procédés pour intégrer des ventes géolocalisées à des plateformes de média social |
US20140075329A1 (en) * | 2012-09-10 | 2014-03-13 | Samsung Electronics Co. Ltd. | Method and device for transmitting information related to event |
US20140074655A1 (en) * | 2012-09-07 | 2014-03-13 | David Lim | System, apparatus and methods for online one-tap account addition and checkout |
US20140108166A1 (en) * | 2012-10-15 | 2014-04-17 | Bank Of America Corporation | Merchant category code ("mcc") based acceptance cost recovery |
US20140173513A1 (en) * | 2012-12-18 | 2014-06-19 | Salesforce.Com, Inc. | User interface date selectors for historical reports |
US20140188734A1 (en) * | 2012-12-31 | 2014-07-03 | Volker Neuwirth | Securely Receiving Data Input At A Computing Device Without Storing The Data Locally |
US20140250013A1 (en) * | 2011-10-31 | 2014-09-04 | Ncr Corporation | Techniques for mobile transaction processing |
US20150012414A1 (en) * | 2011-12-28 | 2015-01-08 | Rakuten, Inc. | Electronic money server, electronic money processing method, electronic money processing program product, and storage medium on which electronic money processing program product is stored |
US20150032816A1 (en) * | 2012-05-30 | 2015-01-29 | Sony Corporation | Information processing apparatus, information processing method, and recording medium |
CN104657899A (zh) * | 2013-11-22 | 2015-05-27 | 国际商业机器公司 | 用于处理有自我意识的代币的方法和系统 |
US20150170112A1 (en) * | 2013-10-04 | 2015-06-18 | Erly Dalvo DeCastro | Systems and methods for providing multi-currency platforms comprising means for exchanging and interconverting tangible and virtual currencies in various transactions, banking operations, and wealth management scenarios |
US9092767B1 (en) | 2013-03-04 | 2015-07-28 | Google Inc. | Selecting a preferred payment instrument |
US20150324828A1 (en) * | 2014-05-09 | 2015-11-12 | Myworld, Inc. | Commerce System and Method of Providing Communication Between Publishers and Intelligent Personal Agents |
US20150363769A1 (en) * | 2014-06-16 | 2015-12-17 | Bank Of America Corporation | Cryptocurrency Real-Time Conversion System |
US20150371222A1 (en) * | 2014-06-19 | 2015-12-24 | Go Daddy Operating Company, LLC | Website content optimization for target market |
US20160012111A1 (en) * | 2014-07-10 | 2016-01-14 | Oracle International Corporation | Embedding analytics within transaction search |
US9251530B1 (en) * | 2012-08-31 | 2016-02-02 | Sprinklr, Inc. | Apparatus and method for model-based social analytics |
US9288123B1 (en) | 2012-08-31 | 2016-03-15 | Sprinklr, Inc. | Method and system for temporal correlation of social signals |
US20160092875A1 (en) * | 2014-09-29 | 2016-03-31 | Mastercard International Incorporated | Product authentication over a payment network |
US20160098486A1 (en) * | 2014-10-03 | 2016-04-07 | Throughtek Technology (Shenzhen) Co., Ltd. | Searching system, method and p2p device for p2p device community |
US9361616B2 (en) * | 2002-10-01 | 2016-06-07 | Dylan T X Zhou | One-scan and one-touch payment and buying using haptic control via messaging and calling multimedia system on mobile and wearable device, currency token interface, point of sale device, and electronic payment card |
US20160162875A1 (en) * | 2012-02-17 | 2016-06-09 | Paypal, Inc. | Login using qr code |
JP2016126669A (ja) * | 2015-01-07 | 2016-07-11 | 株式会社イントラスト | 情報管理サーバ及びその方法 |
US9483797B1 (en) * | 2014-04-21 | 2016-11-01 | Intuit Inc. | Method and system for recording a transaction using a dynamic user interface within an application |
JP6071025B1 (ja) * | 2016-08-27 | 2017-02-01 | 株式会社ギフトプライス | 商品代理購入装置 |
US20170061659A1 (en) * | 2015-08-31 | 2017-03-02 | Accenture Global Solutions Limited | Intelligent visualization munging |
US20170064398A1 (en) * | 2015-08-31 | 2017-03-02 | Verizon Patent And Licensing Inc. | Video on demand platform |
US9641556B1 (en) | 2012-08-31 | 2017-05-02 | Sprinklr, Inc. | Apparatus and method for identifying constituents in a social network |
US9690781B1 (en) * | 2014-10-17 | 2017-06-27 | James E. Niles | System for automatically changing language of an interactive informational display for a user by referencing a personal electronic device of the user |
US9704155B2 (en) | 2011-07-29 | 2017-07-11 | Visa International Service Association | Passing payment tokens through an hop/sop |
US20170310561A1 (en) * | 2015-01-08 | 2017-10-26 | Huawei Technologies Co., Ltd. | Network Control Method and Apparatus |
US9892460B1 (en) * | 2013-06-28 | 2018-02-13 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
US9959548B2 (en) | 2012-08-31 | 2018-05-01 | Sprinklr, Inc. | Method and system for generating social signal vocabularies |
US20180121260A1 (en) * | 2016-10-31 | 2018-05-03 | Intuit Inc. | Defining variability schemas in an application programming interface (api) |
US10003560B1 (en) | 2012-08-31 | 2018-06-19 | Sprinklr, Inc. | Method and system for correlating social media conversations |
USD822689S1 (en) * | 2016-02-14 | 2018-07-10 | Paypal, Inc. | Display screen or portion thereof with animated graphical user interface |
WO2018132816A1 (fr) * | 2017-01-13 | 2018-07-19 | Skale Company | Procédé, appareil et support lisible par ordinateur pour classer des messages dans un réseau social sur la base d'une devise virtuelle |
US10068228B1 (en) | 2013-06-28 | 2018-09-04 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
US10121268B2 (en) | 2012-12-04 | 2018-11-06 | Entit Software Llc | Displaying information technology conditions with heat maps |
US20180349987A1 (en) * | 2016-04-28 | 2018-12-06 | Tencent Technology (Shenzhen) Company Limited | System, method, and apparatus for supporting cash currency exchange |
US10169787B2 (en) * | 2012-06-29 | 2019-01-01 | Paypal, Inc. | Method, medium, and system for session based shopping |
US10185954B2 (en) | 2012-07-05 | 2019-01-22 | Google Llc | Selecting a preferred payment instrument based on a merchant category |
US10269009B1 (en) * | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US20190130376A1 (en) * | 2017-10-31 | 2019-05-02 | Ncr Corporation | Voice-device aided operation |
US10286298B1 (en) * | 2013-06-18 | 2019-05-14 | Electronic Arts Inc. | Dynamically adjusting virtual rewards presented in offers |
US10331899B2 (en) | 2015-10-24 | 2019-06-25 | Oracle International Corporation | Display of dynamic contextual pivot grid analytics |
US10354325B1 (en) | 2013-06-28 | 2019-07-16 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
US10373158B1 (en) | 2018-02-12 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
US10373129B1 (en) | 2018-03-05 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US20190268238A1 (en) * | 2014-04-04 | 2019-08-29 | Carii, Inc | Methods, systems, and computer-readable media for providing community-based information networks |
US20190287094A1 (en) * | 2018-03-15 | 2019-09-19 | Jpmorgan Chase Bank, N.A. | Automated purchase card disable system and method |
US10438290B1 (en) | 2018-03-05 | 2019-10-08 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US10484376B1 (en) | 2015-01-26 | 2019-11-19 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
US10504126B2 (en) | 2009-01-21 | 2019-12-10 | Truaxis, Llc | System and method of obtaining merchant sales information for marketing or sales teams |
US20200013049A1 (en) * | 2018-03-20 | 2020-01-09 | Carl B. Ingram | Coin-Basis application designed to calculate the basis of crypto currency |
US10540654B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US10552818B2 (en) * | 2013-09-02 | 2020-02-04 | Paypal, Inc. | Optimized multiple digital wallet presentation |
US10586250B1 (en) * | 2011-11-18 | 2020-03-10 | Amazon Technologies, Inc. | Incentivized crowd-source pricing |
US10585892B2 (en) | 2014-07-10 | 2020-03-10 | Oracle International Corporation | Hierarchical dimension analysis in multi-dimensional pivot grids |
US10594870B2 (en) | 2009-01-21 | 2020-03-17 | Truaxis, Llc | System and method for matching a savings opportunity using census data |
WO2020061239A1 (fr) * | 2018-09-18 | 2020-03-26 | Mx Technologies, Inc. | Sous-comptes virtuels |
US10630769B2 (en) * | 2017-12-26 | 2020-04-21 | Akamai Technologies, Inc. | Distributed system of record transaction receipt handling in an overlay network |
US10636029B2 (en) | 2016-11-14 | 2020-04-28 | Bank Of America Corporation | System for priority presentation integration on third party systems for limiting resource disbursement |
US10666569B1 (en) * | 2016-09-23 | 2020-05-26 | Amazon Technologies, Inc. | Journal service with named clients |
US10693632B1 (en) | 2015-03-16 | 2020-06-23 | Winklevoss Ip, Llc | Autonomous devices |
US10726098B2 (en) * | 2014-01-23 | 2020-07-28 | Dror Samuel Brama | Method, system and program product for transferring genetic and health data |
US20200250658A1 (en) * | 2019-01-31 | 2020-08-06 | Fujitsu Limited | Information processing apparatus, information processing method, and computer-readable recording medium |
US10805238B1 (en) | 2016-09-23 | 2020-10-13 | Amazon Technologies, Inc. | Management of alternative resources |
US10915891B1 (en) | 2015-03-16 | 2021-02-09 | Winklevoss Ip, Llc | Autonomous devices |
US10929842B1 (en) | 2018-03-05 | 2021-02-23 | Winklevoss Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
US10977639B2 (en) | 2016-01-25 | 2021-04-13 | Freelancer Technology Pty Limited | Adaptive gateway switching system |
US11037138B2 (en) * | 2011-08-18 | 2021-06-15 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods, and systems |
US11074218B2 (en) | 2012-02-02 | 2021-07-27 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia merchant analytics database platform apparatuses, methods and systems |
EP3779697A4 (fr) * | 2018-09-30 | 2021-07-28 | Advanced New Technologies Co., Ltd. | Procédé, dispositif et appareil de traitement de données |
US20210233112A1 (en) * | 2014-06-19 | 2021-07-29 | Go Daddy Operating Company, LLC | Software application customized for target market |
US11100490B1 (en) * | 2020-09-10 | 2021-08-24 | Square, Inc. | Application integration for contactless payments |
US20210287200A1 (en) * | 2019-08-30 | 2021-09-16 | Advanced New Technologies Co., Ltd. | Recommending target transaction code setting region |
US11139955B1 (en) | 2018-02-12 | 2021-10-05 | Winklevoss Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US11200569B1 (en) | 2018-02-12 | 2021-12-14 | Winklevoss Ip, Llc | System, method and program product for making payments using fiat-backed digital assets |
US11282139B1 (en) * | 2013-06-28 | 2022-03-22 | Gemini Ip, Llc | Systems, methods, and program products for verifying digital assets held in a custodial digital asset wallet |
US11288661B2 (en) | 2011-02-16 | 2022-03-29 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
US11308487B1 (en) | 2018-02-12 | 2022-04-19 | Gemini Ip, Llc | System, method and program product for obtaining digital assets |
US11334883B1 (en) | 2018-03-05 | 2022-05-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding and/or distributing collateral as a stable value token in the form of digital assets |
US11354723B2 (en) | 2011-09-23 | 2022-06-07 | Visa International Service Association | Smart shopping cart with E-wallet store injection search |
US11379550B2 (en) * | 2017-08-29 | 2022-07-05 | Paypal, Inc. | Seamless service on third-party sites |
US11397931B2 (en) | 2011-08-18 | 2022-07-26 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US11416924B2 (en) | 2018-01-12 | 2022-08-16 | Wells Fargo Bank, N.A. | Bill presentment based on a user learning style |
US11475442B1 (en) | 2018-02-12 | 2022-10-18 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
US11501370B1 (en) | 2019-06-17 | 2022-11-15 | Gemini Ip, Llc | Systems, methods, and program products for non-custodial trading of digital assets on a digital asset exchange |
US11522700B1 (en) | 2018-02-12 | 2022-12-06 | Gemini Ip, Llc | Systems, methods, and program products for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US11544695B2 (en) | 2020-09-10 | 2023-01-03 | Block, Inc. | Transaction identification by comparison of merchant transaction data and context data |
US11763294B2 (en) | 2011-08-18 | 2023-09-19 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
US11900359B2 (en) | 2011-07-05 | 2024-02-13 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US11909860B1 (en) | 2018-02-12 | 2024-02-20 | Gemini Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US11941008B2 (en) | 2015-02-08 | 2024-03-26 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
Families Citing this family (206)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110061002A1 (en) * | 2009-08-25 | 2011-03-10 | Bethune David | System and method for sending various application programming interfaces to a customized user interface |
US11887105B2 (en) | 2010-04-09 | 2024-01-30 | Paypal, Inc. | Transaction token issuing authorities |
US10304051B2 (en) | 2010-04-09 | 2019-05-28 | Paypal, Inc. | NFC mobile wallet processing systems and methods |
US20130311329A1 (en) * | 2012-03-29 | 2013-11-21 | Digimarc Corporation | Image-related methods and arrangements |
US9990673B2 (en) * | 2010-05-03 | 2018-06-05 | Symbol Technologies, Llc | Universal payment module systems and methods for mobile computing devices |
US20120124496A1 (en) | 2010-10-20 | 2012-05-17 | Mark Rose | Geographic volume analytics apparatuses, methods and systems |
US9064268B2 (en) | 2010-11-01 | 2015-06-23 | Outerwall Inc. | Gift card exchange kiosks and associated methods of use |
US20120130889A1 (en) * | 2010-11-19 | 2012-05-24 | Mastercard International Incorporated | Financial card method, device and system utilizing bar codes to identify transaction details |
US20120158528A1 (en) * | 2010-12-21 | 2012-06-21 | Ebay, Inc. | Efficient transactions at a point of sale location |
AU2011348061B2 (en) | 2010-12-23 | 2015-12-10 | Paypal, Inc. | Mobile phone atm processing methods and systems |
US20120173351A1 (en) * | 2010-12-29 | 2012-07-05 | Qthru, Llc | Mobile Electronic Shopping |
US20130218657A1 (en) * | 2011-01-11 | 2013-08-22 | Diane Salmon | Universal value exchange apparatuses, methods and systems |
US8620799B2 (en) | 2011-01-18 | 2013-12-31 | The Western Union Company | Universal ledger |
US20120198369A1 (en) * | 2011-01-31 | 2012-08-02 | Sap Ag | Coupling analytics and transaction tasks |
US9953334B2 (en) * | 2011-02-10 | 2018-04-24 | Visa International Service Association | Electronic coupon issuance and redemption apparatuses, methods and systems |
US10586227B2 (en) | 2011-02-16 | 2020-03-10 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
BR112013021057A2 (pt) | 2011-02-22 | 2020-11-10 | Visa International Service Association | aparelhos, métodos e sistemas de pagamento eletrônico universal |
US20130144785A1 (en) * | 2011-03-29 | 2013-06-06 | Igor Karpenko | Social network payment authentication apparatuses, methods and systems |
US8694593B1 (en) * | 2011-03-31 | 2014-04-08 | Google Inc. | Tools for micro-communities |
US20120284116A1 (en) * | 2011-05-02 | 2012-11-08 | Herman John C | Systems and methods for incentivized network advertising and data aggregation |
US8538845B2 (en) | 2011-06-03 | 2013-09-17 | Mozido, Llc | Monetary transaction system |
US11049110B2 (en) * | 2011-06-17 | 2021-06-29 | Zelis Payments, Llc | Healthcare transaction facilitation platform apparatuses, methods and systems |
US8688524B1 (en) | 2011-06-28 | 2014-04-01 | Amazon Technologies, Inc. | Tracking online impressions to offline purchases |
US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US10438176B2 (en) | 2011-07-17 | 2019-10-08 | Visa International Service Association | Multiple merchant payment processor platform apparatuses, methods and systems |
US10318941B2 (en) * | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
US10372712B2 (en) * | 2011-08-18 | 2019-08-06 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
US8452708B1 (en) * | 2011-09-03 | 2013-05-28 | Arnold N Birenbaum | Universal payment processing |
US8775570B2 (en) * | 2011-09-15 | 2014-07-08 | Hewlett-Packard Development Company, L. P. | Geographic recommendation online search system |
US9002322B2 (en) | 2011-09-29 | 2015-04-07 | Apple Inc. | Authentication with secondary approver |
US8769624B2 (en) | 2011-09-29 | 2014-07-01 | Apple Inc. | Access control utilizing indirect authentication |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US9805385B2 (en) * | 2011-11-21 | 2017-10-31 | Nant Holdings Ip, Llc | Subscription bill service, systems and methods |
JP2015501984A (ja) * | 2011-11-21 | 2015-01-19 | ナント ホールディングス アイピー,エルエルシー | 加入請求書サービス、システムおよび方法 |
US8874467B2 (en) | 2011-11-23 | 2014-10-28 | Outerwall Inc | Mobile commerce platforms and associated systems and methods for converting consumer coins, cash, and/or other forms of value for use with same |
US9953378B2 (en) * | 2012-04-27 | 2018-04-24 | Visa International Service Association | Social checkout widget generation and integration apparatuses, methods and systems |
US10096022B2 (en) * | 2011-12-13 | 2018-10-09 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
WO2013093638A2 (fr) * | 2011-12-21 | 2013-06-27 | Mashinery Pty Ltd. | Dispositif basé sur les gestes |
US20130161153A1 (en) * | 2011-12-27 | 2013-06-27 | Coinstar, Inc. | Consumer operated kiosk-based marketplace systems and associated methods |
US10223710B2 (en) | 2013-01-04 | 2019-03-05 | Visa International Service Association | Wearable intelligent vision device apparatuses, methods and systems |
JP6065400B2 (ja) * | 2012-03-28 | 2017-01-25 | 富士通株式会社 | 図形検索装置及び図形検索方法 |
US20130262201A1 (en) * | 2012-04-03 | 2013-10-03 | Brad Bergersen | Gold-Buying Enterprise |
AU2013205711B1 (en) * | 2012-05-07 | 2013-07-18 | Google Llc | Value regulation based advertising |
US8458024B1 (en) * | 2012-05-07 | 2013-06-04 | Google Inc. | Value regulation based advertising |
US10445721B2 (en) * | 2012-06-25 | 2019-10-15 | Visa International Service Association | Method and system for data security utilizing user behavior and device identification |
US9020835B2 (en) * | 2012-07-13 | 2015-04-28 | Facebook, Inc. | Search-powered connection targeting |
US20140046843A1 (en) * | 2012-08-07 | 2014-02-13 | Mastercard International, Inc. | Leverage Transaction Card Acceptor Name for Cardholder Communication |
KR20140020055A (ko) * | 2012-08-07 | 2014-02-18 | 주식회사 케이티 | 결제 방법 및 그 시스템 |
KR101969350B1 (ko) * | 2012-08-20 | 2019-04-16 | 엘지전자 주식회사 | 이동 단말기 및 그 제어 방법 |
CA2787817C (fr) * | 2012-08-21 | 2019-01-08 | Dcr Strategies Inc. | Systeme de paiement et d'information sur les produits utilisant des codes pouvant etre balayes |
US20140059161A1 (en) * | 2012-08-23 | 2014-02-27 | Appsense Limited | User virtualization initialization |
US20140073420A1 (en) * | 2012-09-07 | 2014-03-13 | Downing Matthew | System and method for optimizing user value in an online environment |
US20140089068A1 (en) * | 2012-09-25 | 2014-03-27 | Jirbo, Inc. | Videos for In Application Purchases and Rewards for Sharing Same through Social Media and Video Advertising for Reengagement |
US20140164062A1 (en) * | 2012-12-06 | 2014-06-12 | Capital One Financial Corporation | Systems and methods for performing socio-graphic consumer segmentation for targeted advertising |
US10296968B2 (en) | 2012-12-07 | 2019-05-21 | United Parcel Service Of America, Inc. | Website augmentation including conversion of regional content |
US20140171017A1 (en) * | 2012-12-17 | 2014-06-19 | Verizon Patent And Licensing, Inc. | Billing system user interface tool |
US10354237B2 (en) * | 2012-12-17 | 2019-07-16 | Capital One Services Llc | Systems and methods for effecting personal payment transactions |
US10565571B2 (en) * | 2012-12-19 | 2020-02-18 | Capital One Services, Llc | Systems and methods for effecting application programming interfaces for personal payment transactions |
US20140201057A1 (en) * | 2013-01-11 | 2014-07-17 | Brian Mark Shuster | Medium of exchange based on right to use or access information |
US10586246B2 (en) | 2013-01-11 | 2020-03-10 | Google Llc | Reporting mobile application actions |
EP2948909A4 (fr) * | 2013-01-23 | 2016-09-07 | Cardinalcommerce Corp | Implémentation encadrée pour gadgets logiciels de paiement |
US9613183B2 (en) * | 2013-02-11 | 2017-04-04 | Datavi, LLC | Post-authorization transaction bundling control |
US10304050B2 (en) | 2013-02-13 | 2019-05-28 | Paypal, Inc. | NFC card verification |
US10121130B2 (en) * | 2013-03-13 | 2018-11-06 | Capital One Services, Llc | System and method for providing third party payments with non-integrated merchants |
US20140279107A1 (en) * | 2013-03-14 | 2014-09-18 | William P. Vasquez | Systems and methods for integrated, secure point-of-sale transactions |
US8898076B2 (en) | 2013-03-14 | 2014-11-25 | Simply Charged, Inc. | Systems and methods for integrated, secure point-of-sale transactions having an adjustable base station |
US9022286B2 (en) | 2013-03-15 | 2015-05-05 | Virtual Electric, Inc. | Multi-functional credit card type portable electronic device |
US10255613B1 (en) * | 2013-05-06 | 2019-04-09 | Kabam, Inc. | Identity-recognition-based promotions using virtual containers |
US10558958B2 (en) | 2013-05-17 | 2020-02-11 | Visa International Service Association | Contactless message transmission |
US11037137B2 (en) * | 2013-06-13 | 2021-06-15 | Blackberry Limited | Mobile wireless communications device having digital wallet with multi-mode user card and related methods |
WO2014204832A1 (fr) * | 2013-06-17 | 2014-12-24 | Jvl Ventures, Llc | Systèmes, procédés et produits-programmes d'ordinateur pour le traitement d'une requête concernant un dispositif de communication mobile |
US20140379558A1 (en) | 2013-06-20 | 2014-12-25 | Microsoft Corporation | Extensible Interface for Synchronous and Asynchronous Payment |
KR101574156B1 (ko) * | 2013-09-03 | 2015-12-07 | 엔에이치엔엔터테인먼트 주식회사 | 결제 서비스 방법 및 시스템 |
US9898642B2 (en) | 2013-09-09 | 2018-02-20 | Apple Inc. | Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs |
US20150088686A1 (en) * | 2013-09-23 | 2015-03-26 | Note Social, Inc. | System and Method for Improving the Efficiency And Security For Online Order Payment and Shipping and Tracking the Value of Social Networking Related To Same |
US20150161671A1 (en) * | 2013-12-06 | 2015-06-11 | Action Exchange, Inc. | System for harnessing user behavior associated with a server-based resource |
US9635108B2 (en) | 2014-01-25 | 2017-04-25 | Q Technologies Inc. | Systems and methods for content sharing using uniquely generated idenifiers |
US10395237B2 (en) | 2014-05-22 | 2019-08-27 | American Express Travel Related Services Company, Inc. | Systems and methods for dynamic proximity based E-commerce transactions |
US11216815B2 (en) * | 2014-05-27 | 2022-01-04 | American Express Travel Related Services Company, Inc. | Systems and methods for fraud liability shifting |
US10482461B2 (en) | 2014-05-29 | 2019-11-19 | Apple Inc. | User interface for payments |
US9324065B2 (en) | 2014-06-11 | 2016-04-26 | Square, Inc. | Determining languages for a multilingual interface |
WO2015191468A1 (fr) * | 2014-06-11 | 2015-12-17 | Square, Inc. | Commande d'accès basée sur une orientation d'afficheur |
US20150363778A1 (en) * | 2014-06-16 | 2015-12-17 | Bank Of America Corporation | Cryptocurrency electronic payment system |
US10454926B2 (en) | 2014-06-27 | 2019-10-22 | American Express Travel Related Services Company, Inc. | System and method for connectivity contextual services local online experience |
US10360597B2 (en) | 2014-06-27 | 2019-07-23 | American Express Travel Related Services Company, Inc. | System and method for contextual services experience |
US10217151B1 (en) | 2014-07-23 | 2019-02-26 | American Express Travel Related Services Company, Inc. | Systems and methods for proximity based communication |
CN106605201B (zh) | 2014-08-06 | 2021-11-23 | 苹果公司 | 用于电池管理的减小尺寸的用户界面 |
US20160042374A1 (en) * | 2014-08-11 | 2016-02-11 | Mastercard International Incorporated | Methods and Systems for Identifying Merchant and ATM Demand |
US10990941B1 (en) | 2014-08-15 | 2021-04-27 | Jpmorgan Chase Bank, N.A. | Systems and methods for facilitating payments |
US10198738B2 (en) * | 2014-08-25 | 2019-02-05 | Accenture Global Services Limited | System architecture for customer genome construction and analysis |
US10062073B2 (en) | 2014-08-26 | 2018-08-28 | American Express Travel Related Services Company, Inc. | System and method for providing a BLUETOOTH low energy mobile payment system |
US10066959B2 (en) | 2014-09-02 | 2018-09-04 | Apple Inc. | User interactions for a mapping application |
KR102016160B1 (ko) | 2014-09-02 | 2019-08-29 | 애플 인크. | 경고를 관리하기 위한 축소된 크기의 인터페이스 |
US9614680B2 (en) | 2014-09-22 | 2017-04-04 | Standard Register, Inc. | System and method for signature capture |
US9092766B1 (en) * | 2014-10-28 | 2015-07-28 | Poynt Co. | Payment terminal system and method of use |
US10984482B1 (en) * | 2014-10-29 | 2021-04-20 | Wells Fargo Bank, N.A. | Systems and methods for enhanced transaction detail |
US10587541B2 (en) * | 2014-12-02 | 2020-03-10 | Facebook, Inc. | Device, method, and graphical user interface for lightweight messaging |
US20160224973A1 (en) * | 2015-02-01 | 2016-08-04 | Apple Inc. | User interface for payments |
US10360583B2 (en) | 2015-02-05 | 2019-07-23 | Direct Path, Llc | System and method for direct response advertising |
US9574896B2 (en) | 2015-02-13 | 2017-02-21 | Apple Inc. | Navigation user interface |
US10147108B2 (en) | 2015-04-02 | 2018-12-04 | The Nielsen Company (Us), Llc | Methods and apparatus to identify affinity between segment attributes and product characteristics |
WO2016178084A1 (fr) * | 2015-05-05 | 2016-11-10 | Fexco Merchant Services | Système et procédé de conversion de monnaie |
US20160335650A1 (en) | 2015-05-15 | 2016-11-17 | Mastercard International Incorporated | Systems and methods for generating aggregated merchant analytics for a sector location |
US9940637B2 (en) | 2015-06-05 | 2018-04-10 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US20160358133A1 (en) | 2015-06-05 | 2016-12-08 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10282718B1 (en) * | 2015-06-11 | 2019-05-07 | Staples, Inc. | Selective invoice option for business customers in an E-commerce application |
US11367077B2 (en) | 2015-06-11 | 2022-06-21 | Idid Tecnologia Ltda | Antifraud resilient transaction identifier datastructure apparatuses, methods and systems |
US11715109B2 (en) | 2015-06-11 | 2023-08-01 | Idid Tecnologia Ltda | Point of sale apparatuses, methods and systems |
US20170024743A1 (en) * | 2015-07-23 | 2017-01-26 | Dashlane, Inc. | Method and system for managing payment options |
CN108352029A (zh) | 2015-09-08 | 2018-07-31 | 万事达卡国际股份有限公司 | 使用在线交易的起始位置生成聚合商业分析 |
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 |
US20170099980A1 (en) * | 2015-10-08 | 2017-04-13 | Michel Abou Haidar | Integrated tablet computer in hot and cold dispensing machine |
US20170099981A1 (en) * | 2015-10-08 | 2017-04-13 | Michel Abou Haidar | Callisto integrated tablet computer in hot and cold dispensing machine |
JP2018533774A (ja) * | 2015-10-27 | 2018-11-15 | ベイジン ディディ インフィニティ テクノロジー アンド ディベロップメント カンパニー リミティッド | メッセージを配信するためのシステム及び方法 |
US10296963B2 (en) * | 2015-10-28 | 2019-05-21 | Accenture Global Services Limited | Predictive modeling for unintended outcomes |
US10453042B2 (en) | 2015-11-11 | 2019-10-22 | Quisk, Inc. | Token use for transactions in a payment system |
US10346819B2 (en) | 2015-11-19 | 2019-07-09 | Coinstar Asset Holdings, Llc | Mobile device applications, other applications and associated kiosk-based systems and methods for facilitating coin saving |
US20170161745A1 (en) * | 2015-12-03 | 2017-06-08 | Mastercard International Incorporated | Payment account fraud detection using social media heat maps |
US10496970B2 (en) | 2015-12-29 | 2019-12-03 | Square, Inc. | Animation management in applications |
US10489777B2 (en) | 2016-01-05 | 2019-11-26 | Visa International Service Association | Universal access to an electronic wallet |
US11232187B2 (en) | 2016-01-13 | 2022-01-25 | American Express Travel Related Services Company, Inc. | Contextual identification and information security |
US10515384B2 (en) | 2016-05-13 | 2019-12-24 | American Express Travel Related Services Company, Inc. | Systems and methods for contextual services using voice personal assistants |
US11159519B2 (en) | 2016-01-13 | 2021-10-26 | American Express Travel Related Services Company, Inc. | Contextual injection |
US20170330233A1 (en) | 2016-05-13 | 2017-11-16 | American Express Travel Related Services Company, Inc. | Systems and methods for contextual services across platforms based on selectively shared information |
CN107067251B (zh) * | 2016-01-25 | 2021-08-24 | 苹果公司 | 使用具有地理上受限的非本地凭据的电子设备进行交易 |
EP3414869B1 (fr) * | 2016-02-12 | 2021-07-21 | Visa International Service Association | Systèmes et procédés d'authentification utilisant la mise en correspondance de positions |
US10990507B2 (en) * | 2016-02-25 | 2021-04-27 | Dell Products L.P. | System and method for provisioning a virtual machine test environment |
DK179186B1 (en) | 2016-05-19 | 2018-01-15 | Apple Inc | REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION |
US10789596B2 (en) * | 2016-05-25 | 2020-09-29 | Facebook, Inc. | Generating and utilizing user identifying digital visual codes in electronic payment transactions |
US10621581B2 (en) | 2016-06-11 | 2020-04-14 | Apple Inc. | User interface for transactions |
DK201670622A1 (en) | 2016-06-12 | 2018-02-12 | Apple Inc | User interfaces for transactions |
US10289991B1 (en) * | 2016-06-13 | 2019-05-14 | Square, Inc. | Utilizing APIs to facilitate open ticket synchronization |
US10692055B2 (en) * | 2016-07-29 | 2020-06-23 | Square, Inc. | Reprogrammable point-of-sale transaction flows |
US10872320B2 (en) | 2016-07-29 | 2020-12-22 | Square, Inc. | Reprogrammable point-of-sale transaction flows |
US10496973B2 (en) | 2016-07-29 | 2019-12-03 | Square, Inc. | Reprogrammable point-of-sale transaction flows |
US20180053252A1 (en) * | 2016-08-16 | 2018-02-22 | Comenity Llc | Mobile credit acquisition with form population |
CA3031156A1 (fr) | 2016-08-19 | 2018-02-22 | Visa International Service Association | Detection automatique de changement de donnees d'acces |
US20180068313A1 (en) | 2016-09-06 | 2018-03-08 | Apple Inc. | User interfaces for stored-value accounts |
US10217031B2 (en) * | 2016-10-13 | 2019-02-26 | International Business Machines Corporation | Identifying complimentary physical components to known physical components |
US10496808B2 (en) | 2016-10-25 | 2019-12-03 | Apple Inc. | User interface for managing access to credentials for use in an operation |
US10346905B1 (en) | 2016-11-02 | 2019-07-09 | Wells Fargo Bank, N.A. | Facilitating finance based on behavioral triggers |
US11074325B1 (en) * | 2016-11-09 | 2021-07-27 | Wells Fargo Bank, N.A. | Systems and methods for dynamic bio-behavioral authentication |
WO2018089824A1 (fr) * | 2016-11-11 | 2018-05-17 | Honey Inc. | Communication par gestes et de proximité de dispositif mobile |
US10552841B1 (en) * | 2016-12-15 | 2020-02-04 | Worldpay, Llc | Systems and methods for partial authorization of electronic transactions |
US10380579B1 (en) | 2016-12-22 | 2019-08-13 | Square, Inc. | Integration of transaction status indications |
US20180181591A1 (en) | 2016-12-22 | 2018-06-28 | Robert Bryant | Real estate searching system and method |
US10574648B2 (en) | 2016-12-22 | 2020-02-25 | Dashlane SAS | Methods and systems for user authentication |
US20180294047A1 (en) * | 2017-03-01 | 2018-10-11 | Seqster Pdm, Inc. | Personal data marketplace for genetic, fitness, and medical information including health trust management |
US11107061B2 (en) * | 2017-03-10 | 2021-08-31 | Jpmorgan Chase Bank, N.A. | System and method for implementing payment via quick response (QR) code |
US10755339B2 (en) | 2017-03-17 | 2020-08-25 | Team Labs, Inc. | System and method of purchase request management using plain text messages |
CN107122179A (zh) * | 2017-03-31 | 2017-09-01 | 阿里巴巴集团控股有限公司 | 语音的功能控制方法和装置 |
US10496995B2 (en) * | 2017-05-01 | 2019-12-03 | Facebook, Inc. | Facilitating payment transactions between users of a plurality of payment providers |
US10515518B2 (en) | 2017-05-18 | 2019-12-24 | Bank Of America Corporation | System for providing on-demand resource delivery to resource dispensers |
US20180336508A1 (en) * | 2017-05-18 | 2018-11-22 | Bank Of America Corporation | Resource grid system for tracking and reconciling resource movement |
US10783541B2 (en) * | 2017-08-30 | 2020-09-22 | Dell Products L.P. | Systems and methods of using indirect user input signal characteristics to control inventory and/or server operations |
KR102389678B1 (ko) | 2017-09-09 | 2022-04-21 | 애플 인크. | 생체측정 인증의 구현 |
KR102185854B1 (ko) | 2017-09-09 | 2020-12-02 | 애플 인크. | 생체측정 인증의 구현 |
SG11202002874VA (en) | 2017-09-27 | 2020-04-29 | Securrency Inc | Method, apparatus, and computer-readable medium for compliance aware tokenization and control of asset value |
US20190164144A1 (en) * | 2017-11-27 | 2019-05-30 | WAITR, Inc. | Systems and methods for one-tap buy order completion |
US10803476B2 (en) * | 2017-12-28 | 2020-10-13 | Paypal, Inc. | Monitoring device application usage for completion of checkout data processing |
US20190213607A1 (en) * | 2018-01-11 | 2019-07-11 | Point Inside, Inc. | Shopper Traffic Flow Visualization Based on Point of Sale (POS) Transaction Data |
CN111630827A (zh) | 2018-01-22 | 2020-09-04 | 苹果公司 | 基于数据的视觉表示的具有认证的安全登录 |
US10885536B2 (en) * | 2018-02-01 | 2021-01-05 | Ebay Inc. | Garnering interest on potential listing in a photo or video |
US11790470B1 (en) | 2018-03-16 | 2023-10-17 | Block, Inc. | Storage service for sensitive customer data |
US10275613B1 (en) * | 2018-04-20 | 2019-04-30 | Capital One Services, Llc | Identity breach notification and remediation |
US11170085B2 (en) | 2018-06-03 | 2021-11-09 | Apple Inc. | Implementation of biometric authentication |
US11037133B2 (en) * | 2018-07-30 | 2021-06-15 | Visa International Service Association | System, method, and computer program product for selectively displaying information regarding activity in a geographic area |
US11217232B2 (en) * | 2018-09-10 | 2022-01-04 | Sap Portals Israel Ltd. | Recommendations and fraud detection based on determination of a user's native language |
US20200211137A1 (en) * | 2018-12-31 | 2020-07-02 | PayGround, Inc. | Healthcare payment aggregation system |
US11037123B2 (en) * | 2019-01-07 | 2021-06-15 | Visa International Service Association | System, method, and computer program product for customizing functions of a point-of-sale terminal |
US11282066B1 (en) * | 2019-01-18 | 2022-03-22 | Worldpay, Llc | Systems and methods to provide user verification in a shared user environment via a device-specific display |
US11049085B2 (en) | 2019-02-05 | 2021-06-29 | Freedompay, Inc. | Point of sale client integration platform |
US10909523B2 (en) | 2019-02-25 | 2021-02-02 | Capital One Services, Llc | Generation of a combinatorial payment QR code |
US11328352B2 (en) | 2019-03-24 | 2022-05-10 | Apple Inc. | User interfaces for managing an account |
US11328316B2 (en) | 2019-04-04 | 2022-05-10 | Visa International Service Association | Method, system, and computer program product for processing a transaction initiated using an electronic wallet |
US11250462B2 (en) | 2019-04-18 | 2022-02-15 | Benjamin D. Smith | System and method for trading and tracking digitized coupons |
CN114913641A (zh) * | 2019-04-25 | 2022-08-16 | 益逻触控系统公司 | 自助购物系统以及用于运行该自助购物系统的方法 |
US11551216B2 (en) * | 2019-05-01 | 2023-01-10 | Sony Corporation | Transaction security on distributed-ledger based MaaS platform |
US10698704B1 (en) | 2019-06-10 | 2020-06-30 | Captial One Services, Llc | User interface common components and scalable integrable reusable isolated user interface |
US11488133B2 (en) * | 2019-06-21 | 2022-11-01 | Five Stars Loyalty, Inc. | Add-on application for point of sale device |
US11120432B2 (en) | 2019-09-30 | 2021-09-14 | Bank Of America Corporation | Security tool for information exchange |
JP6768911B1 (ja) | 2019-11-01 | 2020-10-14 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | 決済システムおよび決済方法 |
US20210133703A1 (en) * | 2019-11-04 | 2021-05-06 | Bank Of America Corporation | Direct resource distribution system |
US11348084B2 (en) * | 2019-11-04 | 2022-05-31 | Bank Of America Corporation | Entity recognition system |
US10846436B1 (en) | 2019-11-19 | 2020-11-24 | Capital One Services, Llc | Swappable double layer barcode |
US11755228B1 (en) * | 2019-12-16 | 2023-09-12 | Stripe, Inc. | Global heterogeneous data mirroring |
US10909544B1 (en) | 2019-12-26 | 2021-02-02 | Capital One Services, Llc | Accessing and utilizing multiple loyalty point accounts |
US20210216986A1 (en) * | 2020-01-10 | 2021-07-15 | Citycheers Media Corp. | System for conducting transactions |
US11887138B2 (en) * | 2020-03-03 | 2024-01-30 | Daisy Intelligence Corporation | System and method for retail price optimization |
US11748727B2 (en) * | 2020-06-17 | 2023-09-05 | Capital One Services, Llc | Systems and methods for a user interface for making recommendations |
US11816194B2 (en) | 2020-06-21 | 2023-11-14 | Apple Inc. | User interfaces for managing secure operations |
US11310215B2 (en) * | 2020-06-29 | 2022-04-19 | Sony Group Corporation | Access management of publisher nodes for secure access to MaaS network |
US11763238B2 (en) * | 2020-08-07 | 2023-09-19 | Sony Group Corporation | User interface-based mobility transaction management on a MaaS platform |
US11765221B2 (en) | 2020-12-14 | 2023-09-19 | The Western Union Company | Systems and methods for adaptive security and cooperative multi-system operations with dynamic protocols |
US11783338B2 (en) | 2021-01-22 | 2023-10-10 | Daisy Intelligence Corporation | Systems and methods for outlier detection of transactions |
US11756098B2 (en) | 2021-01-28 | 2023-09-12 | Bank Of America Corporation | Geographic predictive indirect distribution network |
US11741435B1 (en) * | 2021-01-29 | 2023-08-29 | Meta Platforms, Inc. | Online session scheduling from a networking platform |
US11687519B2 (en) | 2021-08-11 | 2023-06-27 | T-Mobile Usa, Inc. | Ensuring availability and integrity of a database across geographical regions |
US11803898B2 (en) | 2021-08-25 | 2023-10-31 | Bank Of America Corporation | Account establishment and transaction management using biometrics and intelligent recommendation engine |
US20230069798A1 (en) * | 2021-08-27 | 2023-03-02 | Fidelity Information Services, Llc | Systems and methods for executing real-time electronic transactions using graphical user interface |
US11907997B2 (en) | 2021-09-29 | 2024-02-20 | Capital One Services, Llc | Device, method, and computer-readable media for recommendation networking based on connections, characteristics, and assets using machine learning |
US20230154288A1 (en) * | 2021-11-15 | 2023-05-18 | Tom Mangan | System for mobile sports betting |
US20230351415A1 (en) * | 2022-04-29 | 2023-11-02 | Truist Bank | Using machine learning to leverage interactions to generate hyperpersonalized actions |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010044774A1 (en) * | 2000-04-28 | 2001-11-22 | Tatsuya Sasazawa | Processing system and recording medium for economic data in a virtual space |
US20030233286A1 (en) * | 2002-05-10 | 2003-12-18 | Hahn-Carlson Dean W. | Automated transaction processing system and approach |
US20050177464A1 (en) * | 2000-06-19 | 2005-08-11 | E4X Inc. | System and method for multiple currency transactions |
US20070061250A1 (en) * | 2005-09-15 | 2007-03-15 | Itake Technology Co., Ltd. | System and method for virtual capital operation on the internet |
US20070087820A1 (en) * | 2005-10-14 | 2007-04-19 | Leviathan Entertainment, Llc | Financial institutions and instruments in a virtual environment |
US20070087822A1 (en) * | 2005-10-14 | 2007-04-19 | Leviathan Entertainment, Llc | Financing Options in a Virtual Environment |
US20080167965A1 (en) * | 2007-01-09 | 2008-07-10 | Von Nothaus Bernard | Apparatus, system, and method for extracting real world value from a virtual account |
US20100216542A1 (en) * | 2005-10-14 | 2010-08-26 | Andrew Van Luchene | Agreements in video games permitting virtual and real world penalties obligations and remedies |
US20100227675A1 (en) * | 2009-03-06 | 2010-09-09 | Zynga Game Network, Inc. | Virtual Playing Chips in a Multiuser Online Game Network |
US20110212762A1 (en) * | 2009-09-30 | 2011-09-01 | Matthew Ocko | Apparatuses, methods and systems for a multi-level in-game currency platform |
US20110258031A1 (en) * | 2009-06-29 | 2011-10-20 | David Valin | Method and process for registration, creation and management of campaigns and advertisements in a network system |
US20120005030A1 (en) * | 2010-07-04 | 2012-01-05 | David Valin | Apparatus for connecting Protect Anything Human Key identification mechanism to objects, content, and virtual currency for identification, tracking, delivery, advertising and marketing |
US20120022981A1 (en) * | 2010-07-20 | 2012-01-26 | Jared Morgenstern | Creation, redemption, and accounting in a virtual currency system |
Family Cites Families (640)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US789106A (en) | 1904-10-29 | 1905-05-02 | Howard Preston Tweed | Combined cash-slip and refunding-voucher. |
US5237164A (en) | 1989-05-12 | 1993-08-17 | Sony Corporation | Card having retroreflective bar codes and a magnetic stripe |
US5459656A (en) | 1989-09-12 | 1995-10-17 | Park City Group, Inc. | Business demand projection system and method |
CA2078246C (fr) | 1991-09-23 | 1998-02-03 | Randolph J. Pilc | Methode amelioree de controle d'acces protege |
US5446890A (en) | 1991-11-27 | 1995-08-29 | Hewlett-Packard Company | System for using subsets of rules applied to a database for updating and generating the rule knowledge base and forecasts of system demand |
US5588105A (en) | 1992-11-16 | 1996-12-24 | Apple Computer, Inc. | Status bar for application windows |
US5311594A (en) | 1993-03-26 | 1994-05-10 | At&T Bell Laboratories | Fraud protection for card transactions |
US5649118A (en) | 1993-08-27 | 1997-07-15 | Lucent Technologies Inc. | Smart card with multiple charge accounts and product item tables designating the account to debit |
CN1057178C (zh) | 1994-05-19 | 2000-10-04 | 黄金富 | 非现金即时付款的防盗保全的方法和设备系统 |
US5521362A (en) | 1994-06-08 | 1996-05-28 | Mci Communications Corporation | Electronic purse card having multiple storage memories to prevent fraudulent usage and method therefor |
US6963859B2 (en) | 1994-11-23 | 2005-11-08 | Contentguard Holdings, Inc. | Content rendering repository |
US5536045A (en) | 1994-12-28 | 1996-07-16 | Adams; Thomas W. | Debit/credit card system having primary utility in replacing food stamps |
US5530438A (en) | 1995-01-09 | 1996-06-25 | Motorola, Inc. | Method of providing an alert of a financial transaction |
EP1555591B1 (fr) | 1995-02-13 | 2013-08-14 | Intertrust Technologies Corp. | Procédé et dispositif de gestion de transactions sécurisées |
US6321208B1 (en) | 1995-04-19 | 2001-11-20 | Brightstreet.Com, Inc. | Method and system for electronic distribution of product redemption coupons |
US5615264A (en) | 1995-06-08 | 1997-03-25 | Wave Systems Corp. | Encrypted data package record for use in remote transaction metered data system |
US5794221A (en) | 1995-07-07 | 1998-08-11 | Egendorf; Andrew | Internet billing method |
US5815657A (en) | 1996-04-26 | 1998-09-29 | Verifone, Inc. | System, method and article of manufacture for network electronic authorization utilizing an authorization instrument |
US5963924A (en) | 1996-04-26 | 1999-10-05 | Verifone, Inc. | System, method and article of manufacture for the use of payment instrument holders and payment instruments in network electronic commerce |
US7555458B1 (en) | 1996-06-05 | 2009-06-30 | Fraud Control System.Com Corporation | Method of billing a purchase made over a computer network |
US8229844B2 (en) | 1996-06-05 | 2012-07-24 | Fraud Control Systems.Com Corporation | Method of billing a purchase made over a computer network |
US5850446A (en) | 1996-06-17 | 1998-12-15 | Verifone, Inc. | System, method and article of manufacture for virtual point of sale processing utilizing an extensible, flexible architecture |
US5943624A (en) | 1996-07-15 | 1999-08-24 | Motorola, Inc. | Contactless smartcard for use in cellular telephone |
US5903830A (en) | 1996-08-08 | 1999-05-11 | Joao; Raymond Anthony | Transaction security apparatus and method |
US7096003B2 (en) | 1996-08-08 | 2006-08-22 | Raymond Anthony Joao | Transaction security apparatus |
US5991749A (en) | 1996-09-11 | 1999-11-23 | Morrill, Jr.; Paul H. | Wireless telephony for collecting tolls, conducting financial transactions, and authorizing other activities |
US8156026B2 (en) | 2000-05-12 | 2012-04-10 | Nintendo of America Ltd. | Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection |
US5961593A (en) | 1997-01-22 | 1999-10-05 | Lucent Technologies, Inc. | System and method for providing anonymous personalized browsing by a proxy system in a network |
US6374250B2 (en) | 1997-02-03 | 2002-04-16 | International Business Machines Corporation | System and method for differential compression of data from a plurality of binary sources |
US5987525A (en) | 1997-04-15 | 1999-11-16 | Cddb, Inc. | Network delivery of interactive entertainment synchronized to playback of audio recordings |
US6202052B1 (en) | 1997-05-08 | 2001-03-13 | Simplification, Llc | Fully-automated system for tax reporting, payment and refund |
US5949044A (en) | 1997-06-13 | 1999-09-07 | Walker Asset Management Limited Partnership | Method and apparatus for funds and credit line transfers |
US20060190347A1 (en) | 1997-06-16 | 2006-08-24 | Vincent Cuervo | System and process for sales, validation, rewards and delivery of prepaid debit cards |
US6304886B1 (en) | 1997-06-19 | 2001-10-16 | International Business Machines Corporation | System and method for building a web site using specific interface |
US6061660A (en) | 1997-10-20 | 2000-05-09 | York Eggleston | System and method for incentive programs and award fulfillment |
US6535855B1 (en) | 1997-12-09 | 2003-03-18 | The Chase Manhattan Bank | Push banking system and method |
US8346663B2 (en) | 1998-01-30 | 2013-01-01 | Citicorp Development Center, Inc. | Method and system of contactless interfacing for smart card banking |
US6202933B1 (en) | 1998-02-19 | 2001-03-20 | Ernst & Young U.S. Llp | Transaction card and methods and apparatus therefor |
US6208973B1 (en) | 1998-02-27 | 2001-03-27 | Onehealthbank.Com | Point of service third party financial management vehicle for the healthcare industry |
US6055513A (en) | 1998-03-11 | 2000-04-25 | Telebuyer, Llc | Methods and apparatus for intelligent selection of goods and services in telephonic and electronic commerce |
US6636833B1 (en) | 1998-03-25 | 2003-10-21 | Obis Patents Ltd. | Credit card system and method |
US6064990A (en) | 1998-03-31 | 2000-05-16 | International Business Machines Corporation | System for electronic notification of account activity |
US20030171992A1 (en) | 1999-04-23 | 2003-09-11 | First Data Corporation | System and methods for redeeming rewards associated with accounts |
US6263447B1 (en) | 1998-05-21 | 2001-07-17 | Equifax Inc. | System and method for authentication of network users |
US6131811A (en) | 1998-05-29 | 2000-10-17 | E-Micro Corporation | Wallet consolidator |
US6799165B1 (en) * | 1998-07-28 | 2004-09-28 | Eimar M. Boesjes | Apparatus and methods for inventory, sale, and delivery of digitally transferable goods |
DE69932294T8 (de) | 1998-08-12 | 2007-10-25 | Nippon Telegraph And Telephone Corp. | Aufzeichnungsmedium mit darauf aufgezeichneten elektronischen Ticketdefinitionen und Verfahren und Vorrichtungen zum Verarbeiten elektronischer Tickets |
US7379901B1 (en) | 1998-09-11 | 2008-05-27 | Lv Partners, L.P. | Accessing a vendor web site using personal account information retrieved from a credit card company web site |
US7248855B2 (en) | 1998-09-15 | 2007-07-24 | Upaid Systems, Ltd. | Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account |
US6601761B1 (en) | 1998-09-15 | 2003-08-05 | Citibank, N.A. | Method and system for co-branding an electronic payment platform such as an electronic wallet |
US6317722B1 (en) | 1998-09-18 | 2001-11-13 | Amazon.Com, Inc. | Use of electronic shopping carts to generate personal recommendations |
US7617125B1 (en) | 1998-10-07 | 2009-11-10 | Paypal, Inc. | System and method for storage and retrieval of information subject to authorization by a data controller |
US6092053A (en) | 1998-10-07 | 2000-07-18 | Cybercash, Inc. | System and method for merchant invoked electronic commerce |
US7533064B1 (en) | 1998-10-07 | 2009-05-12 | Paypal Inc. | E-mail invoked electronic commerce |
US7337119B1 (en) | 1998-10-26 | 2008-02-26 | First Data Corporation | System and method for detecting purchasing card fraud |
US6473500B1 (en) | 1998-10-28 | 2002-10-29 | Mastercard International Incorporated | System and method for using a prepaid card |
US7379899B1 (en) | 1998-11-13 | 2008-05-27 | Nintendo Of America Inc. | Method and apparatus for verifying product sale transactions and processing product returns |
US7937325B2 (en) | 1998-12-08 | 2011-05-03 | Yodlee.Com, Inc. | Interactive bill payment center |
US7143358B1 (en) * | 1998-12-23 | 2006-11-28 | Yuen Henry C | Virtual world internet web site using common and user-specific metrics |
US7571139B1 (en) | 1999-02-19 | 2009-08-04 | Giordano Joseph A | System and method for processing financial transactions |
US7590575B2 (en) | 1999-03-08 | 2009-09-15 | Microsoft Corporation | Method and apparatus for converting, formatting, and displaying currency values |
US20040139004A1 (en) | 1999-04-08 | 2004-07-15 | Aceinc Pty Ltd. | Secure online commerce transactions |
CA2910997A1 (fr) | 1999-04-30 | 2000-11-09 | Paypal, Inc. | Systeme et procede d'echange electronique de valeurs entre des usagers distribues |
US6609113B1 (en) | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
US6385591B1 (en) | 1999-05-11 | 2002-05-07 | Jeffrey W. Mankoff | Method and system for electronic organization of coupons |
US7194437B1 (en) | 1999-05-14 | 2007-03-20 | Amazon.Com, Inc. | Computer-based funds transfer system |
US7685067B1 (en) | 1999-05-14 | 2010-03-23 | Amazon.Com, Inc. | Computer-assisted funds transfer system |
US7165041B1 (en) | 1999-05-27 | 2007-01-16 | Accenture, Llp | Web-based architecture sales tool |
DE19926472C2 (de) | 1999-06-10 | 2001-11-15 | Call A Bike Mobilitaetssysteme | Verfahren zum Übermitteln eines Codes |
US7593862B2 (en) | 1999-07-07 | 2009-09-22 | Jeffrey W. Mankoff | Delivery, organization, and redemption of virtual offers from the internet, interactive-TV, wireless devices and other electronic means |
WO2001008066A1 (fr) | 1999-07-26 | 2001-02-01 | Iprivacy Llc | Achat electronique de biens sur un reseau de communication comprenant une livraison physique tout en assurant la securite des informations privees et a caractere personnel |
EP1204940A4 (fr) | 1999-07-29 | 2004-11-03 | Privacash Com Inc | Procede et systeme servant a effectuer un achat anonyme sur internet |
US7644037B1 (en) | 1999-08-16 | 2010-01-05 | Vladimir Ostrovsky | Method and system for transferring electronic funds |
US6873974B1 (en) | 1999-08-17 | 2005-03-29 | Citibank, N.A. | System and method for use of distributed electronic wallets |
US7953671B2 (en) | 1999-08-31 | 2011-05-31 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
US7343351B1 (en) | 1999-08-31 | 2008-03-11 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
WO2001023998A1 (fr) | 1999-09-24 | 2001-04-05 | Phoenix Technologies Ltd. | Systeme logiciel de mise au point pour faciliter la selection de composants |
US8195565B2 (en) | 1999-11-05 | 2012-06-05 | Lead Core Fund, L.L.C. | Systems and methods for point of interaction based policy routing of transactions |
US8275704B2 (en) | 1999-11-05 | 2012-09-25 | Lead Core Fund, L.L.C. | Systems and methods for authorizing an allocation of an amount between transaction accounts |
US7899744B2 (en) | 1999-11-05 | 2011-03-01 | American Express Travel Related Services Company, Inc. | Systems and methods for approval of an allocation |
US8296228B1 (en) | 1999-11-22 | 2012-10-23 | Harry Thomas Kloor | Dual transaction authorization system and method |
US7603311B1 (en) | 1999-11-29 | 2009-10-13 | Yadav-Ranjan Rani K | Process and device for conducting electronic transactions |
US7966259B1 (en) | 1999-12-09 | 2011-06-21 | Amazon.Com, Inc. | System and methods for facilitating transactions on, and personalizing web pages of, third party web sites |
US7213005B2 (en) | 1999-12-09 | 2007-05-01 | International Business Machines Corporation | Digital content distribution using web broadcasting services |
US7167844B1 (en) | 1999-12-22 | 2007-01-23 | Accenture Llp | Electronic menu document creator in a virtual financial environment |
US20020019777A1 (en) | 1999-12-31 | 2002-02-14 | Schwab David Michael | Return of merchandize through third party locations |
US7366703B2 (en) | 2000-01-05 | 2008-04-29 | American Express Travel Related Services Company, Inc. | Smartcard internet authorization system |
US6516056B1 (en) | 2000-01-07 | 2003-02-04 | Vesta Corporation | Fraud prevention system and method |
AU2001227857A1 (en) * | 2000-01-14 | 2001-07-24 | Saba Software, Inc. | Method and apparatus for a business applications management system platform |
US6643652B2 (en) | 2000-01-14 | 2003-11-04 | Saba Software, Inc. | Method and apparatus for managing data exchange among systems in a network |
US7268668B2 (en) | 2003-05-09 | 2007-09-11 | American Express Travel Related Services Company, Inc. | Systems and methods for managing multiple accounts on a RF transaction instrument |
US7024383B1 (en) | 2000-01-31 | 2006-04-04 | Goldman, Sachs & Co. | Online sales risk management system |
AU2001234908A1 (en) | 2000-02-11 | 2001-08-20 | Marcio Marc Abreu | System and method for communicating product recall information, product warningsor other product-related information to users of products |
US8150767B2 (en) | 2000-02-16 | 2012-04-03 | Mastercard International Incorporated | System and method for conducting electronic commerce with a remote wallet server |
US20060178986A1 (en) | 2000-02-17 | 2006-08-10 | Giordano Joseph A | System and method for processing financial transactions using multi-payment preferences |
US20030018550A1 (en) | 2000-02-22 | 2003-01-23 | Rotman Frank Lewis | Methods and systems for providing transaction data |
AU2001239945A1 (en) | 2000-02-29 | 2001-09-12 | E-Scoring, Inc. | Systems and methods enabling anonymous credit transactions |
US7865414B2 (en) | 2000-03-01 | 2011-01-04 | Passgate Corporation | Method, system and computer readable medium for web site account and e-commerce management from a central location |
US20010037297A1 (en) | 2000-03-09 | 2001-11-01 | Mcnair Edward Parry | Bill paying with the aid of a scanner |
US6999943B1 (en) | 2000-03-10 | 2006-02-14 | Doublecredit.Com, Inc. | Routing methods and systems for increasing payment transaction volume and profitability |
EP1136931A1 (fr) | 2000-03-20 | 2001-09-26 | Roundit Inc. | Système d'incitation au patronage, et méthode de commerce au détail basée sur internet |
US7177848B2 (en) | 2000-04-11 | 2007-02-13 | Mastercard International Incorporated | Method and system for conducting secure payments over a computer network without a pseudo or proxy account number |
US8032453B2 (en) | 2000-04-14 | 2011-10-04 | Citicorp Development Center, Inc. | Method and system for notifying customers of transaction opportunities |
GB2361560B (en) | 2000-04-17 | 2002-12-18 | Robert Kaplan | Method and apparatus for transferring or receiving data via the internet securely |
KR20090116813A (ko) | 2000-04-24 | 2009-11-11 | 비자 인터내셔날 써비스 어쏘시에이션 | 온라인 지불인 인증 서비스 |
US20020082919A1 (en) | 2000-05-01 | 2002-06-27 | Michael Landau | System method and article of manufacture for affiliate tracking for the dissemination of promotional and marketing material via e-mail |
US6805288B2 (en) | 2000-05-15 | 2004-10-19 | Larry Routhenstein | Method for generating customer secure card numbers subject to use restrictions by an electronic card |
US7206847B1 (en) | 2000-05-22 | 2007-04-17 | Motorola Inc. | Smart card with back up |
BR0111249A (pt) | 2000-06-01 | 2003-12-23 | Worldcom Inc | Sistema e método para proporcionar serviços pré-pagos via um sistema de rede de protocolo da internet |
US7499872B1 (en) | 2000-06-02 | 2009-03-03 | Tuition Fund, Llc | Methods and systems for applying rebates to higher education |
WO2001095266A2 (fr) | 2000-06-06 | 2001-12-13 | March Albert D | Systeme et procede permettant de transferer des fonds |
US7996259B1 (en) | 2000-06-07 | 2011-08-09 | Perfect Web Technologies, Inc. | Method for developing electronic documents providing e-commerce tools |
US7437293B1 (en) | 2000-06-09 | 2008-10-14 | Videa, Llc | Data transmission system with enhancement data |
GB2364482B (en) | 2000-06-30 | 2002-10-09 | Motorola Inc | Server-based electronic wallet system |
US7430537B2 (en) | 2000-07-10 | 2008-09-30 | Paypal, Inc. | System and method for verifying a financial instrument |
AU2001273334A1 (en) | 2000-07-11 | 2002-01-21 | Paypal, Inc | System and method for third-party payment processing |
US7359880B2 (en) | 2000-07-11 | 2008-04-15 | Abel Luther C | System and method for consumer control over card-based transactions |
US6666377B1 (en) | 2000-07-18 | 2003-12-23 | Scott C. Harris | Bar code data entry device |
EP1316168A4 (fr) | 2000-08-04 | 2006-05-10 | First Data Corp | Procede et systeme d'utilisation de communications electroniques pour un contrat electronique |
US7343335B1 (en) * | 2000-08-08 | 2008-03-11 | Ebay Inc. | Method for managing group finances via an electronic network |
US7209950B2 (en) | 2000-08-15 | 2007-04-24 | Zonamovil.Com, Inc. | Method and apparatus for a network independent short message delivery system |
US6938019B1 (en) | 2000-08-29 | 2005-08-30 | Uzo Chijioke Chukwuemeka | Method and apparatus for making secure electronic payments |
US7155411B1 (en) | 2000-09-28 | 2006-12-26 | Microsoft Corporation | Integrating payment accounts and an electronic wallet |
US7337144B1 (en) | 2000-09-28 | 2008-02-26 | Microsoft Corporation | Method and system for restricting the usage of payment accounts |
JP2002109098A (ja) | 2000-10-04 | 2002-04-12 | Fujitsu Ltd | 商品情報管理方法及び修理依頼方法 |
US7499889B2 (en) | 2000-10-23 | 2009-03-03 | Cyota Inc. | Transaction system |
US7844489B2 (en) | 2000-10-30 | 2010-11-30 | Buyerleverage | Buyer-driven targeting of purchasing entities |
WO2002039216A2 (fr) | 2000-11-03 | 2002-05-16 | Outlet Group, Llc | Procede et systeme d'une topographie commerciale integree et portail de reseau virtuel 3d |
US7016532B2 (en) | 2000-11-06 | 2006-03-21 | Evryx Technologies | Image capture and identification system and process |
US7398225B2 (en) | 2001-03-29 | 2008-07-08 | American Express Travel Related Services Company, Inc. | System and method for networked loyalty program |
US20070234224A1 (en) | 2000-11-09 | 2007-10-04 | Leavitt Joseph M | Method for developing and implementing efficient workflow oriented user interfaces and controls |
US7318049B2 (en) | 2000-11-17 | 2008-01-08 | Gregory Fx Iannacci | System and method for an automated benefit recognition, acquisition, value exchange, and transaction settlement system using multivariable linear and nonlinear modeling |
US6993507B2 (en) | 2000-12-14 | 2006-01-31 | Pacific Payment Systems, Inc. | Bar coded bill payment system and method |
US6934528B2 (en) | 2000-12-20 | 2005-08-23 | American Management Systems, Inc. | Method for creating self-built customer hierarchies |
US7941669B2 (en) | 2001-01-03 | 2011-05-10 | American Express Travel Related Services Company, Inc. | Method and apparatus for enabling a user to select an authentication method |
US6915279B2 (en) | 2001-03-09 | 2005-07-05 | Mastercard International Incorporated | System and method for conducting secure payment transactions |
US8595055B2 (en) | 2001-03-27 | 2013-11-26 | Points.Com | Apparatus and method of facilitating the exchange of points between selected entities |
US20060053056A1 (en) | 2001-03-29 | 2006-03-09 | American Express Marketing & Development Corporati | Card member discount system and method |
US20030014331A1 (en) | 2001-05-08 | 2003-01-16 | Simons Erik Neal | Affiliate marketing search facility for ranking merchants and recording referral commissions to affiliate sites based upon users' on-line activity |
US7028052B2 (en) | 2001-05-10 | 2006-04-11 | Equifax, Inc. | Systems and methods for notifying a consumer of changes made to a credit report |
WO2003001866A1 (fr) | 2001-06-27 | 2003-01-09 | Snapcount Limited | Traitement de transaction |
US20030020748A1 (en) * | 2001-06-29 | 2003-01-30 | Bitflash Graphics, Inc. | Method and system for displaying graphics information |
US7742984B2 (en) | 2001-07-06 | 2010-06-22 | Hossein Mohsenzadeh | Secure authentication and payment system |
US8346659B1 (en) | 2001-07-06 | 2013-01-01 | Hossein Mohsenzadeh | Secure authentication and payment system |
US20030014307A1 (en) | 2001-07-16 | 2003-01-16 | General Motors Corporation | Method and system for mobile commerce advertising |
US20030158811A1 (en) | 2001-07-18 | 2003-08-21 | Ventanex | System and method for rules based electronic funds transaction processing |
US6898598B2 (en) | 2001-08-09 | 2005-05-24 | International Business Machines Corporation | Smart receipt |
US7133862B2 (en) | 2001-08-13 | 2006-11-07 | Xerox Corporation | System with user directed enrichment and import/export control |
US8010605B2 (en) * | 2001-08-14 | 2011-08-30 | Imagitas, Inc. | System and method for sharing information among provider systems |
US8050997B1 (en) | 2001-08-23 | 2011-11-01 | Paypal Inc. | Instant availability of electronically transferred funds |
WO2003019854A1 (fr) | 2001-08-23 | 2003-03-06 | Efunds Corporation | Systeme et procede de protection de logiciel |
US7613640B2 (en) | 2001-08-29 | 2009-11-03 | Ebs Group Limited | Electronic trading system |
US7111789B2 (en) | 2001-08-31 | 2006-09-26 | Arcot Systems, Inc. | Enhancements to multi-party authentication and other protocols |
KR20010090081A (ko) | 2001-09-11 | 2001-10-18 | 엄기문 | 바코드 및 이동통신 단말기를 이용한 신용카드 결제시스템 및 신용카드 결제 방법 |
US20030080185A1 (en) | 2001-10-26 | 2003-05-01 | Werther Ellen R. | Money transfer method and system |
US8332275B2 (en) | 2001-10-31 | 2012-12-11 | Ebay Inc. | Method and apparatus to facilitate a transaction within a network-based facility |
US7958049B2 (en) | 2001-11-01 | 2011-06-07 | Metavante Corporation | System and method for obtaining customer bill information and facilitating bill payment at biller websites |
US20030101134A1 (en) | 2001-11-28 | 2003-05-29 | Liu James C. | Method and system for trusted transaction approval |
US7212979B1 (en) | 2001-12-14 | 2007-05-01 | Bellsouth Intellectuall Property Corporation | System and method for identifying desirable subscribers |
US6755342B1 (en) | 2001-12-31 | 2004-06-29 | Bellsouth Intellectual Property Corporation | Credit card validation for an interactive wireless network |
US20030135734A1 (en) | 2002-01-14 | 2003-07-17 | Fagan Robert H. | Secure mutual authentication system |
US20030135842A1 (en) | 2002-01-16 | 2003-07-17 | Jan-Erik Frey | Software development tool for embedded computer systems |
KR100432430B1 (ko) | 2002-02-01 | 2004-05-22 | 이효제 | 전자증권을 이용한 전자지불 시스템 및 그 방법 |
US7904360B2 (en) | 2002-02-04 | 2011-03-08 | Alexander William EVANS | System and method for verification, authentication, and notification of a transaction |
US7890393B2 (en) | 2002-02-07 | 2011-02-15 | Ebay, Inc. | Method and system for completing a transaction between a customer and a merchant |
CA2476646A1 (fr) | 2002-02-14 | 2003-08-21 | Zachary Pessin | Appareil et procede destines a un systeme financier reparti |
WO2003071495A1 (fr) | 2002-02-15 | 2003-08-28 | Coinstar, Inc. | Procedes et systemes d'echange et/ou de transfert de divers types de moyens de paiement |
US7343365B2 (en) | 2002-02-20 | 2008-03-11 | Microsoft Corporation | Computer system architecture for automatic context associations |
US7716141B2 (en) * | 2002-02-22 | 2010-05-11 | Dun And Bradstreet Corporation | Method for providing an industry report |
US6853386B1 (en) * | 2002-02-27 | 2005-02-08 | At&T Corp. | Method for generating contiguous cartograms |
CA2479179A1 (fr) | 2002-03-14 | 2003-09-25 | Euronet Worldwide, Inc. | Systeme et procede pour l'achat de biens et de services a travers des points d'acces a un reseau de donnees sur un reseau de points de vente |
US7107285B2 (en) * | 2002-03-16 | 2006-09-12 | Questerra Corporation | Method, system, and program for an improved enterprise spatial system |
GB2387929B (en) | 2002-03-18 | 2005-11-16 | Mainline Corporate Holdings | A tax voucher system |
US8352499B2 (en) | 2003-06-02 | 2013-01-08 | Google Inc. | Serving advertisements using user request information and user information |
AU2002247363A1 (en) | 2002-04-04 | 2003-10-20 | Catalina Marketing International, Inc. | Product recall using customer prior shopping history data |
US7707120B2 (en) | 2002-04-17 | 2010-04-27 | Visa International Service Association | Mobile account authentication service |
US20030200142A1 (en) | 2002-04-23 | 2003-10-23 | Heather Hicks | On-line employee incentive system |
US7200577B2 (en) | 2002-05-01 | 2007-04-03 | America Online Incorporated | Method and apparatus for secure online transactions |
US7680688B2 (en) | 2002-05-28 | 2010-03-16 | American Express Travel Related Services Company, Inc. | System and method for exchanging loyalty points for acquisitions |
US8209245B2 (en) | 2002-05-28 | 2012-06-26 | United Services Automobile Association | Electronic financial transaction warehouse |
AU2003243523B2 (en) | 2002-06-12 | 2008-04-10 | Cardinalcommerce Corporation | Universal merchant platform for payment authentication |
US7047041B2 (en) | 2002-06-17 | 2006-05-16 | Nokia Corporation | Method and device for storing and accessing personal information |
US7110980B2 (en) | 2002-06-21 | 2006-09-19 | American Express Bank Ltd. | System and method for facilitating electronic transfer of funds |
US7254548B1 (en) | 2002-07-10 | 2007-08-07 | Union Beach, L.P. | System and method for the administration of financial accounts using profiles |
US7784684B2 (en) | 2002-08-08 | 2010-08-31 | Fujitsu Limited | Wireless computer wallet for physical point of sale (POS) transactions |
US6873725B2 (en) | 2002-09-09 | 2005-03-29 | Coulter International Corp. | Simultaneous measurement and display of 3-D size distributions of particulate materials in suspensions |
US20050021492A1 (en) * | 2002-09-13 | 2005-01-27 | Aman Safaei | On-line sales analysis system and method |
US7424455B2 (en) | 2002-09-17 | 2008-09-09 | First Data Corporation | Method and systems for providing merchant services with right-time creation and updating of merchant accounts |
US7222363B2 (en) | 2002-10-18 | 2007-05-22 | American Express Travel Related Services Company, Inc. | Device independent authentication system and method |
US20040128197A1 (en) | 2002-10-23 | 2004-07-01 | Vayusa, Inc. | System and method of generating, distributing, and/or redeeming promotional offers using electronic devices |
SG172477A1 (en) | 2002-11-07 | 2011-07-28 | Planet Payment Inc | Time-of-transaction foreign currency conversion |
US7231354B1 (en) | 2002-11-12 | 2007-06-12 | Bellsouth Intellectual Property Corporation | Method, apparatus, and computer-readable medium for administering the implementation of product change notices |
US20040103037A1 (en) | 2002-11-26 | 2004-05-27 | Sears, Roebuck And Co. | Methods and apparatus for organizing retail product information |
US8090618B1 (en) * | 2002-12-12 | 2012-01-03 | Massive Incorporated | Online game commerce system |
US7571140B2 (en) | 2002-12-16 | 2009-08-04 | First Data Corporation | Payment management |
US20040122693A1 (en) | 2002-12-23 | 2004-06-24 | Michael Hatscher | Community builder |
US7015912B2 (en) * | 2003-01-13 | 2006-03-21 | Vendavo, Inc. | System and method for the visual display of data in an interactive zebra chart |
US20040138999A1 (en) | 2003-01-13 | 2004-07-15 | Capital One Financial Corporation | Systems and methods for managing a credit account having a credit component associated with healthcare expenses |
US20040254836A1 (en) | 2003-01-28 | 2004-12-16 | Emoke Barabas Jutka T. | Method & system for distribution & management of electronic vouchers via carrier applications |
JP4117550B2 (ja) | 2003-03-19 | 2008-07-16 | ソニー株式会社 | 通信システム、決済管理装置および方法、携帯情報端末および情報処理方法、並びにプログラム |
JP4241167B2 (ja) | 2003-04-24 | 2009-03-18 | ソニー株式会社 | プログラム、データ処理方法、およびデータ処理装置 |
US7827077B2 (en) | 2003-05-02 | 2010-11-02 | Visa U.S.A. Inc. | Method and apparatus for management of electronic receipts on portable devices |
US7268667B2 (en) | 2003-05-09 | 2007-09-11 | American Express Travel Related Services Company, Inc. | Systems and methods for providing a RF transaction device operable to store multiple distinct accounts |
US7895119B2 (en) | 2003-05-13 | 2011-02-22 | Bank Of America Corporation | Method and system for pushing credit payments as buyer initiated transactions |
US7689483B2 (en) | 2003-05-20 | 2010-03-30 | Amegy Bank of Texas | System to facilitate payments for a customer through a foreign bank, software, business methods, and other related methods |
EP1626368A4 (fr) | 2003-05-20 | 2008-10-15 | Sony Corp | Systeme fournisseur de contenu, dispositif et procede de traitement de donnees, et programme correspondant |
US8321267B2 (en) | 2003-06-30 | 2012-11-27 | Mindspark Interactive Network, Inc. | Method, system and apparatus for targeting an offer |
US20050004811A1 (en) | 2003-07-02 | 2005-01-06 | Babu Suresh Rangaswamy | Automated recall management system for enterprise management applications |
US7676432B2 (en) | 2003-07-08 | 2010-03-09 | Paybyclick Corporation | Methods and apparatus for transacting electronic commerce using account hierarchy and locking of accounts |
US20050015338A1 (en) | 2003-07-16 | 2005-01-20 | Lee Lawrence Weekhar | Electronic Statement Organizer with User Interface and Integrated Bill Payment |
US20050080821A1 (en) | 2003-07-21 | 2005-04-14 | Breil Peter D. | System and method for managing collections accounts |
GB0318000D0 (en) | 2003-07-31 | 2003-09-03 | Ncr Int Inc | Mobile applications |
US20090132347A1 (en) | 2003-08-12 | 2009-05-21 | Russell Wayne Anderson | Systems And Methods For Aggregating And Utilizing Retail Transaction Records At The Customer Level |
US7373669B2 (en) | 2003-08-13 | 2008-05-13 | The 41St Parameter, Inc. | Method and system for determining presence of probable error or fraud in a data set by linking common data values or elements |
JP2007504534A (ja) | 2003-08-26 | 2007-03-01 | ウェーブズ ライセンシング エルエルシー | 為替取引される通貨の投資信託の証券及びシステム |
US8156042B2 (en) | 2003-08-29 | 2012-04-10 | Starbucks Corporation | Method and apparatus for automatically reloading a stored value card |
US8572391B2 (en) | 2003-09-12 | 2013-10-29 | Emc Corporation | System and method for risk based authentication |
US20050065819A1 (en) | 2003-09-19 | 2005-03-24 | Schultz Pamela Lynn | Electronic reimbursement process for provision of medical services |
US7387238B2 (en) | 2003-10-14 | 2008-06-17 | Foss Jr Sheldon H | Customer enrollment in a stored value card program |
WO2005038627A2 (fr) | 2003-10-17 | 2005-04-28 | Nexxo Financial Corporation | Systemes et procedes pour effectuer des operations bancaires faisant appel a une carte a valeur stockee |
WO2005053271A2 (fr) | 2003-11-24 | 2005-06-09 | America Online, Inc. | Systemes et procedes pour communications authentifiees |
US20050137969A1 (en) | 2003-12-19 | 2005-06-23 | Dharmesh Shah | Secure financial transaction gateway and vault |
US8145898B2 (en) | 2003-12-23 | 2012-03-27 | Hewlett-Packard Development Company, L.P. | Encryption/decryption pay per use web service |
US6948656B2 (en) | 2003-12-23 | 2005-09-27 | First Data Corporation | System with GPS to manage risk of financial transactions |
US20050192895A1 (en) | 2004-02-10 | 2005-09-01 | First Data Corporation | Methods and systems for processing transactions |
US20070038515A1 (en) | 2004-03-01 | 2007-02-15 | Signature Systems Llc | Method and system for issuing, aggregating and redeeming merchant reward points with a credit card network |
KR100456601B1 (ko) | 2004-03-18 | 2004-11-10 | 엔에이치엔(주) | 게임 아이템 판매 등록 시스템 및 게임 아이템 판매 등록방법 |
US20060081714A1 (en) | 2004-08-23 | 2006-04-20 | King Martin T | Portable scanning device |
US20050220326A1 (en) | 2004-04-06 | 2005-10-06 | Rf Intelligent Systems, Inc. | Mobile identification system and method |
US20050234817A1 (en) | 2004-04-16 | 2005-10-20 | First Data Corporation | Methods and systems for private label transaction processing |
US8762283B2 (en) | 2004-05-03 | 2014-06-24 | Visa International Service Association | Multiple party benefit from an online authentication service |
US20050253840A1 (en) * | 2004-05-11 | 2005-11-17 | Kwon Ryan Y W | Method and system for interactive three-dimensional item display |
US20050254714A1 (en) | 2004-05-13 | 2005-11-17 | Ramakrishna Anne | Systems and methods for data transfer with camera-enabled devices |
US7798415B1 (en) | 2004-05-20 | 2010-09-21 | American Express Travel Realted Services Company, Inc. | Wireless transaction fobs and methods of using the same |
EP1817729A4 (fr) | 2004-06-25 | 2010-11-03 | Ian Charles Ogilvy | Procede, appareil et systeme de traitement de transactions |
US7546543B2 (en) | 2004-06-25 | 2009-06-09 | Apple Inc. | Widget authoring and editing environment |
US7827176B2 (en) | 2004-06-30 | 2010-11-02 | Google Inc. | Methods and systems for endorsing local search results |
US20060015399A1 (en) | 2004-07-13 | 2006-01-19 | Alberth William P Jr | Content distribution revenue sharing methods and devices therefore |
US7383231B2 (en) | 2004-07-19 | 2008-06-03 | Amazon Technologies, Inc. | Performing automatically authorized programmatic transactions |
US7413113B1 (en) | 2004-07-28 | 2008-08-19 | Sprint Communications Company L.P. | Context-based card selection device |
US7392222B1 (en) | 2004-08-03 | 2008-06-24 | Jpmorgan Chase Bank, N.A. | System and method for providing promotional pricing |
US7873911B2 (en) | 2004-08-31 | 2011-01-18 | Gopalakrishnan Kumar C | Methods for providing information services related to visual imagery |
US7506812B2 (en) | 2004-09-07 | 2009-03-24 | Semtek Innovative Solutions Corporation | Transparently securing data for transmission on financial networks |
US7870071B2 (en) | 2004-09-08 | 2011-01-11 | American Express Travel Related Services Company, Inc. | Systems, methods, and devices for combined credit card and stored value transaction accounts |
US20060163349A1 (en) | 2004-09-30 | 2006-07-27 | W5 Networks, Inc. | Wireless systems suitable for retail automation and promotion |
US8489583B2 (en) | 2004-10-01 | 2013-07-16 | Ricoh Company, Ltd. | Techniques for retrieving documents using an image capture device |
US9471332B2 (en) | 2004-10-19 | 2016-10-18 | International Business Machines Corporation | Selecting graphical component types at runtime |
US8204774B2 (en) | 2004-10-29 | 2012-06-19 | American Express Travel Related Services Company, Inc. | Estimating the spend capacity of consumer households |
US7606762B1 (en) | 2004-11-05 | 2009-10-20 | Rdm Corporation | System and method for providing a distributed decisioning environment for processing of financial transactions |
US8417633B1 (en) | 2004-11-08 | 2013-04-09 | Rockstar Consortium Us Lp | Enabling improved protection of consumer information in electronic transactions |
US7783539B2 (en) | 2004-11-08 | 2010-08-24 | First Data Corporation | Derivative currency-exchange transactions |
US20060129427A1 (en) | 2004-11-16 | 2006-06-15 | Health Dialog Services Corporation | Systems and methods for predicting healthcare related risk events |
US7958087B2 (en) | 2004-11-17 | 2011-06-07 | Iron Mountain Incorporated | Systems and methods for cross-system digital asset tag propagation |
US20080091616A1 (en) | 2004-12-15 | 2008-04-17 | Erich Helwin | Communication System And Method Using Visual Interfaces For Mobile Transactions |
US8224754B2 (en) | 2004-12-15 | 2012-07-17 | Microsoft Corporation | Generation, distribution and verification of tokens using a secure hash algorithm |
US8713000B1 (en) | 2005-01-12 | 2014-04-29 | Linkedin Corporation | Method and system for leveraging the power of one's social-network in an online marketplace |
US8700729B2 (en) | 2005-01-21 | 2014-04-15 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US7357310B2 (en) | 2005-03-11 | 2008-04-15 | Gerry Calabrese | Mobile phone charge card notification and authorization method |
US20060218153A1 (en) | 2005-03-28 | 2006-09-28 | Voon George H H | Building social networks using shared content data relating to a common interest |
US8060463B1 (en) | 2005-03-30 | 2011-11-15 | Amazon Technologies, Inc. | Mining of user event data to identify users with common interests |
US7527195B2 (en) | 2005-04-11 | 2009-05-05 | Bill Me Later, Inc. | Method and system for risk management in a transaction |
US7970671B2 (en) | 2005-04-12 | 2011-06-28 | Syncada Llc | Automated transaction processing system and approach with currency conversion |
US20100082480A1 (en) * | 2008-09-30 | 2010-04-01 | Jason Alexander Korosec | Payments with virtual value |
KR100662026B1 (ko) | 2005-05-13 | 2006-12-27 | (주)베스텍컴 | 네트워크를 통한 부가세 환급 처리 시스템 및 그 방법 |
US7401731B1 (en) | 2005-05-27 | 2008-07-22 | Jpmorgan Chase Bank, Na | Method and system for implementing a card product with multiple customized relationships |
US7343149B2 (en) | 2005-06-13 | 2008-03-11 | Lucent Technologies Inc. | Network support for credit card notification |
US7810720B2 (en) | 2005-06-13 | 2010-10-12 | Robert Lovett | Account payment using barcode information exchange |
US7290704B1 (en) | 2005-06-21 | 2007-11-06 | Robert Ball | Method and system relating to a multi-lateral trade engine for payment transactions |
US7742942B2 (en) | 2005-06-22 | 2010-06-22 | Excentus Corporation | System and method for discounting fuel |
AU2005334095A1 (en) | 2005-06-30 | 2007-01-11 | James M. Essig | Consumer-driven pre-production vaccine reservation system and methods of using a vaccine reservation system |
US7970626B2 (en) | 2005-07-08 | 2011-06-28 | Oltine Acquistitions NY LLC | Facilitating payments to health care providers |
US8335720B2 (en) | 2005-08-10 | 2012-12-18 | American Express Travel Related Services Company, Inc. | System, method, and computer program product for increasing inventory turnover using targeted consumer offers |
US20070038516A1 (en) | 2005-08-13 | 2007-02-15 | Jeff Apple | Systems, methods, and computer program products for enabling an advertiser to measure user viewing of and response to an advertisement |
US7756752B2 (en) * | 2005-08-22 | 2010-07-13 | Yahoo! Inc. | Customization of an online shopping experience |
US20070150413A1 (en) | 2005-08-29 | 2007-06-28 | Frederick Morgenstern | Apparatus and Method for Creating and Using Electronic Currency on Global Computer Networks |
US8166068B2 (en) | 2005-09-02 | 2012-04-24 | Qwest | Location based authorization of financial card transactions systems and methods |
US7584884B2 (en) | 2005-09-06 | 2009-09-08 | Capital One Financial Corporation | System and method for capturing sales tax deduction information from monetary card transactions |
US7660581B2 (en) | 2005-09-14 | 2010-02-09 | Jumptap, Inc. | Managing sponsored content based on usage history |
US8660862B2 (en) | 2005-09-20 | 2014-02-25 | Visa U.S.A. Inc. | Determination of healthcare coverage using a payment account |
WO2007086947A2 (fr) | 2005-09-23 | 2007-08-02 | Tap It Fame Inc. | Systèmes et procédés de commercialisation et de vente de multimédia |
US20070214078A1 (en) | 2005-09-28 | 2007-09-13 | Transpayment, Inc. | Bill payment apparatus and method |
US20080004116A1 (en) | 2006-06-30 | 2008-01-03 | Andrew Stephen Van Luchene | Video Game Environment |
US7672865B2 (en) * | 2005-10-21 | 2010-03-02 | Fair Isaac Corporation | Method and apparatus for retail data mining using pair-wise co-occurrence consistency |
US7819307B2 (en) | 2005-10-27 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Method and system for managing monetary value on a mobile device |
US7877790B2 (en) | 2005-10-31 | 2011-01-25 | At&T Intellectual Property I, L.P. | System and method of using personal data |
US7844490B2 (en) | 2005-11-02 | 2010-11-30 | Visa U.S.A. Inc. | Method and system for conducting promotional programs |
US8538875B2 (en) | 2005-11-04 | 2013-09-17 | Instamed Communications Llc | Process for linked healthcare and financial transaction initiation |
EP1955269A4 (fr) | 2005-12-02 | 2012-12-05 | Welcome Real Time Pte Ltd | Procédé et système pour retours autorisés |
US7711640B2 (en) | 2005-12-20 | 2010-05-04 | Bgc Partners, Inc. | Methods and apparatus for composite trading order processing |
US8352323B2 (en) | 2007-11-30 | 2013-01-08 | Blaze Mobile, Inc. | Conducting an online payment transaction using an NFC enabled mobile communication device |
US8290433B2 (en) | 2007-11-14 | 2012-10-16 | Blaze Mobile, Inc. | Method and system for securing transactions made through a mobile communication device |
US20070162369A1 (en) | 2006-01-09 | 2007-07-12 | Hardison Joseph H Iii | Internet-based method of and system for transfering and exercising monetary rights within a financial marketplace |
CA2640153A1 (fr) * | 2006-01-27 | 2007-08-09 | Spyder Lynk, Llc | Codage et decodage de donnees dans une image |
US8149771B2 (en) | 2006-01-31 | 2012-04-03 | Roundbox, Inc. | Reliable event broadcaster with multiplexing and bandwidth control functions |
US8345931B2 (en) | 2006-02-10 | 2013-01-01 | The Western Union Company | Biometric based authorization systems for electronic fund transfers |
KR100731809B1 (ko) | 2006-02-13 | 2007-06-22 | 삼성전자주식회사 | 이동통신 단말기 간의 착 발신 전환에 따른 과금 처리 방법 |
US7966239B2 (en) * | 2006-02-14 | 2011-06-21 | Leviathan Entertainment, Llc | Software-based commerce engine deployed in video game environment |
US8335822B2 (en) | 2006-03-13 | 2012-12-18 | Ebay Inc. | Peer-to-peer trading platform with search caching |
US8176416B1 (en) | 2006-03-17 | 2012-05-08 | Wells Fargo Bank, N.A. | System and method for delivering a device-independent web page |
US20070226152A1 (en) | 2006-03-21 | 2007-09-27 | Austin Jones | System and method for anonymous transactions and conveyances |
WO2008027620A1 (fr) | 2006-03-30 | 2008-03-06 | Obopay Inc. | Système de paiement mobile entre deux personnes |
US7996270B2 (en) | 2006-03-30 | 2011-08-09 | Ebay Inc. | Community based network shopping |
US8249965B2 (en) | 2006-03-30 | 2012-08-21 | Obopay, Inc. | Member-supported mobile payment system |
US7870121B2 (en) | 2008-01-15 | 2011-01-11 | Oracle International Corporation | Matching up XML query expression for XML table index lookup during query rewrite |
DE602006007804D1 (de) | 2006-03-31 | 2009-08-27 | Sony Deutschland Gmbh | Zusammensetzung die mindestens eine Art von Flüssigkristall enthält |
US8086535B2 (en) | 2006-04-04 | 2011-12-27 | Apple Inc. | Decoupling rights in a digital content unit from download |
US8028041B2 (en) | 2006-04-07 | 2011-09-27 | Ebay Inc. | Dynamic content for online transactions |
KR20070104087A (ko) | 2006-04-21 | 2007-10-25 | 주식회사 아이캐시 | 구매 인증 번호를 이용한 신용카드 회원에 대한 판매품목별 로열티 서비스 방법 및 시스템 |
EP2033350A2 (fr) | 2006-05-02 | 2009-03-11 | Broadon Communications Corp. | Procédé et gestion de contenu |
US20070267479A1 (en) | 2006-05-16 | 2007-11-22 | Chockstone, Inc. | Systems and methods for implementing parking transactions and other financial transactions |
US8016192B2 (en) | 2006-06-06 | 2011-09-13 | Motorola Mobility, Inc. | User-configurable priority list for mobile device electronic payment applications |
US8751672B2 (en) | 2006-06-21 | 2014-06-10 | Verizon Data Services Llc | Personal video channels |
US8290819B2 (en) | 2006-06-29 | 2012-10-16 | Microsoft Corporation | Electronic commerce transactions over a peer-to-peer communications channel |
US7644042B2 (en) | 2006-06-30 | 2010-01-05 | Amazon Technologies, Inc. | Managing transaction accounts |
US9135626B2 (en) | 2006-06-30 | 2015-09-15 | Nokia Technologies Oy | Advertising middleware |
US20080021829A1 (en) | 2006-07-06 | 2008-01-24 | Kranzley Arthur D | Rule-based selection of financial account for payment card transaction |
US8489067B2 (en) | 2006-07-06 | 2013-07-16 | Qualcomm Incorporated | Methods and systems for distribution of a mobile wallet for a mobile device |
US8160959B2 (en) | 2006-07-06 | 2012-04-17 | Firethorn Mobile, Inc. | Methods and systems for payment transactions in a mobile environment |
US7844530B2 (en) | 2006-07-31 | 2010-11-30 | Insight Catastrophe Solutions | Apparatuses, methods, and systems for providing a risk scoring engine user interface |
US20080034309A1 (en) | 2006-08-01 | 2008-02-07 | Louch John O | Multimedia center including widgets |
US8220047B1 (en) | 2006-08-09 | 2012-07-10 | Google Inc. | Anti-phishing system and method |
US7708194B2 (en) | 2006-08-23 | 2010-05-04 | Verizon Patent And Licensing Inc. | Virtual wallet |
US8078497B1 (en) | 2006-09-21 | 2011-12-13 | Google Inc. | Distinguishing search results associated with an electronic commerce system |
US20080077489A1 (en) | 2006-09-21 | 2008-03-27 | Apple Inc. | Rewards systems |
US7660749B2 (en) | 2006-09-29 | 2010-02-09 | Apple Inc. | Method, system, and medium for representing visitor activity in an online store |
US8056092B2 (en) | 2006-09-29 | 2011-11-08 | Clearspring Technologies, Inc. | Method and apparatus for widget-container hosting and generation |
US7802719B2 (en) | 2006-09-29 | 2010-09-28 | Sony Ericsson Mobile Communications Ab | System and method for presenting multiple transaction options in a portable device |
US8812351B2 (en) | 2006-10-05 | 2014-08-19 | Richard Zollino | Method of analyzing credit card transaction data |
WO2009099403A2 (fr) | 2006-10-23 | 2009-08-13 | Chipin Inc. | Procédé et système visant à disposer d’un gadget logiciel pour afficher des contenus multimédias |
US7565332B2 (en) | 2006-10-23 | 2009-07-21 | Chipin Inc. | Method and system for providing a widget usable in affiliate marketing |
EP2097864A4 (fr) | 2006-10-24 | 2011-10-05 | Mastercard International Inc | Procédé et appareil permettant l'envoi de messages de récompense, l'attribution de réductions et de primes à un point d'interaction |
US7941369B2 (en) | 2006-10-25 | 2011-05-10 | Joseph James Juras | Method of assisting a business in acquiring merchant services |
WO2008061002A2 (fr) | 2006-11-14 | 2008-05-22 | Networked Insights, Inc. | Procédé et système permettant d'identifier automatiquement les utilisateurs participant à une conversation électronique |
US8402356B2 (en) | 2006-11-22 | 2013-03-19 | Yahoo! Inc. | Methods, systems and apparatus for delivery of media |
US20090037255A1 (en) | 2006-12-06 | 2009-02-05 | Leo Chiu | Behavior aggregation |
US7878393B2 (en) | 2006-12-07 | 2011-02-01 | Moneygram International, Inc. | Method and apparatus for distribution of money transfers |
EP2177010B1 (fr) | 2006-12-13 | 2015-10-28 | Quickplay Media Inc. | Plate-forme multimédia mobile |
US8660899B2 (en) | 2006-12-19 | 2014-02-25 | Yahoo! Inc. | Transferring behavioral profiles anonymously across domains for behavioral targeting |
US20080154915A1 (en) | 2006-12-20 | 2008-06-26 | Microsoft Corporation | Network-based recommendations |
US10311427B2 (en) | 2006-12-29 | 2019-06-04 | Google Technology Holdings LLC | Method and system for monitoring secure application execution events during contactless RFID/NFC communication |
ES2319599B1 (es) | 2007-01-08 | 2010-01-26 | Guillermo Petri Larrea | Sistema reversible de seccionamiento en varias piezas de palas de aerogeneradores. |
US8452277B2 (en) | 2007-01-11 | 2013-05-28 | David A. Hurowitz | Data delivered to targeted mobile device |
US20080172331A1 (en) * | 2007-01-16 | 2008-07-17 | Graves Phillip C | Bill Payment Card Method and System |
US20080177574A1 (en) | 2007-01-22 | 2008-07-24 | Marcos Lara Gonzalez | Systems and Methods To Improve The Efficiencies Of Immunization Registries |
US20080177672A1 (en) | 2007-01-23 | 2008-07-24 | Robert Brunner | Method for managing liability |
US7676434B2 (en) | 2007-01-28 | 2010-03-09 | Bora Payment Systems, Llc | Payer direct hub |
US8694890B2 (en) * | 2007-01-31 | 2014-04-08 | Adobe Sytems Incorporated | Use of color in a site analysis report |
US7780522B2 (en) * | 2007-02-23 | 2010-08-24 | Cfph, Llc | Game at cash register |
US20080208704A1 (en) * | 2007-02-28 | 2008-08-28 | Wang Xiaochun Stanley | Methods to conduct sales of products or services over a communication network |
US20080208712A1 (en) * | 2007-02-28 | 2008-08-28 | Phil Yerkes | Computer based systems to conduct sales of products or services over a communication network |
US20080223918A1 (en) | 2007-03-15 | 2008-09-18 | Microsoft Corporation | Payment tokens |
US9524496B2 (en) | 2007-03-19 | 2016-12-20 | Hugo Olliphant | Micro payments |
US8499237B2 (en) | 2007-03-29 | 2013-07-30 | Hiconversion, Inc. | Method and apparatus for application enabling of websites |
US7962418B1 (en) | 2007-03-30 | 2011-06-14 | Amazon Technologies, Inc. | System and method of fulfilling a transaction |
US7779360B1 (en) * | 2007-04-10 | 2010-08-17 | Google Inc. | Map user interface |
US20080263460A1 (en) * | 2007-04-20 | 2008-10-23 | Utbk, Inc. | Methods and Systems to Connect People for Virtual Meeting in Virtual Reality |
US8131592B2 (en) | 2007-04-27 | 2012-03-06 | Sojern, Inc. | Method and system for providing targeted content with verification information |
US8688570B2 (en) | 2007-04-27 | 2014-04-01 | American Express Travel Related Services Company, Inc. | System and method for performing person-to-person funds transfers via wireless communications |
US20080272188A1 (en) | 2007-05-02 | 2008-11-06 | I4 Commerce Inc. | Distributed system for commerce |
GB2450193A (en) | 2007-06-12 | 2008-12-17 | Cvon Innovations Ltd | Method and system for managing credits via a mobile device |
US9483769B2 (en) | 2007-06-20 | 2016-11-01 | Qualcomm Incorporated | Dynamic electronic coupon for a mobile environment |
US7739169B2 (en) | 2007-06-25 | 2010-06-15 | Visa U.S.A. Inc. | Restricting access to compromised account information |
US7756755B2 (en) | 2007-06-28 | 2010-07-13 | Hewlett-Packard Devlopment Company, L.P. | Capturing and utilizing consumer purchase intent information |
US8327450B2 (en) | 2007-07-19 | 2012-12-04 | Wells Fargo Bank N.A. | Digital safety deposit box |
US8527404B2 (en) | 2007-07-19 | 2013-09-03 | First Data Corporation | Merchant-initiated adjustments |
US8151328B1 (en) | 2007-07-20 | 2012-04-03 | Sprint Communications Company L.P. | Accessing secure network areas by utilizing mobile-device authentication |
US7779161B2 (en) | 2007-07-24 | 2010-08-17 | Hiconversion, Inc. | Method and apparatus for general virtual application enabling of websites |
US8195233B2 (en) | 2007-07-30 | 2012-06-05 | Motorola Mobility, Inc. | Methods and systems for identity management in wireless devices |
US20090055757A1 (en) | 2007-08-20 | 2009-02-26 | International Business Machines Corporation | Solution for automatically generating software user interface code for multiple run-time environments from a single description document |
US8788278B2 (en) | 2007-08-28 | 2014-07-22 | Moneygram International, Inc. | Consumer database loyalty program for a money transfer system |
US7849014B2 (en) * | 2007-08-29 | 2010-12-07 | American Express Travel Related Services Company, Inc. | System and method for facilitating a financial transaction with a dynamically generated identifier |
US8667422B2 (en) | 2007-09-04 | 2014-03-04 | Apple Inc. | Graphical user interface with location-specific interface elements |
US8041338B2 (en) | 2007-09-10 | 2011-10-18 | Microsoft Corporation | Mobile wallet and digital payment |
US8341083B1 (en) | 2007-09-12 | 2012-12-25 | Devicefidelity, Inc. | Wirelessly executing financial transactions |
US20090076953A1 (en) | 2007-09-18 | 2009-03-19 | First Data Corporation | ATM/Debit Expedited Bill Payments |
US20090076934A1 (en) | 2007-09-19 | 2009-03-19 | Hamed Shahbazi | Personalized customer transaction system |
US8175235B2 (en) | 2007-09-27 | 2012-05-08 | Verizon Patent And Licensing Inc. | Lease model for avoiding permanent card locking |
US8249654B1 (en) | 2007-09-27 | 2012-08-21 | Sprint Communications Company L.P. | Dynamic smart card application loading |
US10679196B2 (en) | 2007-09-28 | 2020-06-09 | The Western Union Company | Bill payment aggregation service |
US7707113B1 (en) | 2007-09-28 | 2010-04-27 | Sprint Communications Company L.P. | Method and system for setting levels of electronic wallet security |
US8108261B2 (en) | 2007-10-01 | 2012-01-31 | Apple Inc. | Store affiliation system |
US8515840B2 (en) | 2007-10-02 | 2013-08-20 | American Express Travel Related Services Company, Inc. | Modular electronic wallet |
US20130304637A1 (en) | 2007-10-02 | 2013-11-14 | American Express Travel Related Services Company, Inc. | Fraud control integrated form filling tool |
US20090099925A1 (en) * | 2007-10-04 | 2009-04-16 | Mehta Kaushal N | Apparatus and Method for Virtual World Item Searching |
US20090096812A1 (en) * | 2007-10-12 | 2009-04-16 | Business Objects, S.A. | Apparatus and method for morphing data visualizations |
US20090106151A1 (en) | 2007-10-17 | 2009-04-23 | Mark Allen Nelsen | Fraud prevention based on risk assessment rule |
EP2212772A4 (fr) | 2007-10-17 | 2017-04-05 | VCVC lll LLC | Dispositif de recommandation de contenu à base de nlp |
US8565723B2 (en) | 2007-10-17 | 2013-10-22 | First Data Corporation | Onetime passwords for mobile wallets |
US8157178B2 (en) | 2007-10-19 | 2012-04-17 | First Data Corporation | Manufacturing system to produce contactless devices with switches |
US8214291B2 (en) | 2007-10-19 | 2012-07-03 | Ebay Inc. | Unified identity verification |
US20090112767A1 (en) | 2007-10-25 | 2009-04-30 | Ayman Hammad | Escrow system and method |
US7774076B2 (en) | 2007-10-29 | 2010-08-10 | First Data Corporation | System and method for validation of transactions |
MX2008014011A (es) | 2007-11-02 | 2009-05-26 | Citicorp Credit Services Inc | Metodos y sistemas para ajuste de intercambio. |
MX2008014010A (es) | 2007-11-02 | 2009-05-26 | Citicorp Credit Services Inc | Metodos y sistemas para gestion de cuentas de clientes de institucion financiera. |
US20090132366A1 (en) | 2007-11-15 | 2009-05-21 | Microsoft Corporation | Recognizing and crediting offline realization of online behavior |
US20090132403A1 (en) | 2007-11-21 | 2009-05-21 | Microsoft Corporation | Licensing interface for user generated content |
US20090132435A1 (en) | 2007-11-21 | 2009-05-21 | Microsoft Corporation | Popularity based licensing of user generated content |
US8924344B2 (en) | 2007-11-28 | 2014-12-30 | Microsoft Corporation | User profile replication |
US20090144104A1 (en) | 2007-11-30 | 2009-06-04 | Scott Kevin Johnson | System and Method of Selectively Notifying Consumers of Product Recalls |
US8145569B2 (en) | 2007-12-13 | 2012-03-27 | Google Inc. | Multiple party on-line transactions |
US8244590B2 (en) | 2007-12-21 | 2012-08-14 | Glyde Corporation | Software system for decentralizing ecommerce with single page buy |
US8192289B2 (en) | 2007-12-26 | 2012-06-05 | Scientific Games Holdings Limited | System and method for collecting and using player information |
US7837125B2 (en) | 2007-12-27 | 2010-11-23 | Apple Inc. | Methods and systems for encoding a magnetic stripe |
US8683486B2 (en) | 2007-12-28 | 2014-03-25 | Emulex Corporation | SAS expander based persistent connections |
US10262303B2 (en) | 2007-12-28 | 2019-04-16 | Mastercard International Incorporated | Methods and systems for applying a rewards program promotion to payment transactions |
US8214288B2 (en) | 2007-12-28 | 2012-07-03 | Ebay Inc. | System and method of a passphrase account identifier for use in a network environment |
US8224702B2 (en) | 2007-12-28 | 2012-07-17 | Ebay, Inc. | Systems and methods for facilitating financial transactions over a network |
US7958052B2 (en) | 2007-12-31 | 2011-06-07 | Mastercard International Incorporated | Methods and systems for cardholder initiated transactions |
US20090171760A1 (en) | 2007-12-31 | 2009-07-02 | Nokia Corporation | Systems and Methods for Facilitating Electronic Commerce |
US7734714B2 (en) | 2008-01-11 | 2010-06-08 | Spacecurve, Inc. | Spatial Sieve Tree |
US20090182664A1 (en) | 2008-01-15 | 2009-07-16 | Trombley Austin D | Integrating social networking with financial services |
US20090241159A1 (en) | 2008-03-18 | 2009-09-24 | Avaya Technology Llc | Open cable application platform set-top box (stb) personal profiles and communications applications |
US20090192935A1 (en) | 2008-01-30 | 2009-07-30 | Kent Griffin | One step near field communication transactions |
US11159909B2 (en) * | 2008-02-05 | 2021-10-26 | Victor Thomas Anderson | Wireless location establishing device |
US20090271283A1 (en) | 2008-02-13 | 2009-10-29 | Catholic Content, Llc | Network Media Distribution |
US8401900B2 (en) | 2008-02-14 | 2013-03-19 | At&T Intellectual Property I, Lp | System and method for presenting advertising data based on end user trick-play trend data |
US8521842B2 (en) | 2008-02-29 | 2013-08-27 | Microsoft Corporation | Delivering composite media to a client application |
US8554623B2 (en) * | 2008-03-03 | 2013-10-08 | Yahoo! Inc. | Method and apparatus for social network marketing with consumer referral |
US20100063903A1 (en) | 2008-03-10 | 2010-03-11 | Thayne Whipple | Hierarchically applied rules engine ("hare") |
US7707089B1 (en) | 2008-03-12 | 2010-04-27 | Jpmorgan Chase, N.A. | Method and system for automating fraud authorization strategies |
US20140207662A1 (en) * | 2008-03-13 | 2014-07-24 | Giftya Llc | System and method for managing gifts |
US8285643B2 (en) | 2008-06-12 | 2012-10-09 | Monncello Enterprises, LLC | System and method for processing gift cards |
US8060413B2 (en) | 2008-03-14 | 2011-11-15 | Research In Motion Limited | System and method for making electronic payments from a wireless mobile device |
US20090234751A1 (en) | 2008-03-14 | 2009-09-17 | Eric Chan | Electronic wallet for a wireless mobile device |
US8321338B2 (en) | 2008-03-21 | 2012-11-27 | First Data Corporation | Electronic network access device |
US9069575B2 (en) | 2008-03-25 | 2015-06-30 | Qualcomm Incorporated | Apparatus and methods for widget-related memory management |
EP2106108B1 (fr) | 2008-03-27 | 2013-08-21 | Motorola Mobility LLC | Procédé et appareil pour la sélection automatique d'une application dans un dispositif électronique à l'aide de plusieurs gestionnaires de découverte |
US7967196B1 (en) | 2008-03-28 | 2011-06-28 | Sprint Communications Company L.P. | Electronic wallet ready to pay timer |
US20090254535A1 (en) | 2008-04-02 | 2009-10-08 | International Business Machines Corporation | Search engine to improve product recall traceability activities |
US20090281904A1 (en) | 2008-04-02 | 2009-11-12 | Pharris Dennis J | Mobile telephone transaction systems and methods |
US8175979B2 (en) | 2008-04-02 | 2012-05-08 | International Business Machines Corporation | Method and system for anonymous electronic transactions using a mobile device |
US20090254471A1 (en) | 2008-04-03 | 2009-10-08 | Seidel Peter Stuart | Settlement of futures contracts in foreign currencies |
US20090271265A1 (en) | 2008-04-28 | 2009-10-29 | Cyndigo, Corp. | Electronic receipt system and method |
US7630937B1 (en) | 2008-04-30 | 2009-12-08 | Intuit Inc. | Method and system for processing a financial transaction |
US7890370B2 (en) * | 2008-04-30 | 2011-02-15 | Target Brands, Inc. | Using alerts to bring attention to in-store information |
US8180705B2 (en) | 2008-04-30 | 2012-05-15 | Intuit Inc. | Method and apparatus for initiating a funds transfer using a mobile device |
US20090276270A1 (en) | 2008-05-02 | 2009-11-05 | Rockwell Automation Technologies, Inc. | System configuration application and user interface |
US8209744B2 (en) | 2008-05-16 | 2012-06-26 | Microsoft Corporation | Mobile device assisted secure computer network communication |
AU2009249272B2 (en) | 2008-05-18 | 2014-11-20 | Google Llc | Secured electronic transaction system |
US20100004989A1 (en) | 2008-05-20 | 2010-01-07 | American Express Travel Related Services Company, Inc. | Systems, methods, apparatus and computer program products for interfacing payment systems to a network associated with a referral |
EP2728528A1 (fr) | 2008-05-30 | 2014-05-07 | MR.QR10 GmbH & Co. KG | Dispositif de serveur pour contrôler une transaction, entité principale et entité secondaire |
US20100106642A1 (en) | 2008-06-05 | 2010-04-29 | Namedepot.Com, Inc. | Method and system for delayed payment of prepaid cards |
US8117085B1 (en) | 2008-06-05 | 2012-02-14 | Amazon Technologies, Inc. | Data mining processes for supporting item pair recommendations |
US20090307140A1 (en) | 2008-06-06 | 2009-12-10 | Upendra Mardikar | Mobile device over-the-air (ota) registration and point-of-sale (pos) payment |
US8788350B2 (en) | 2008-06-13 | 2014-07-22 | Microsoft Corporation | Handling payment receipts with a receipt store |
US8195516B2 (en) | 2008-06-25 | 2012-06-05 | Visa U.S.A. Inc. | Generating retail sales report |
US20090327088A1 (en) | 2008-06-26 | 2009-12-31 | Utstarcom, Inc. | System and Method for performing International Transactions |
US20090327040A1 (en) * | 2008-06-30 | 2009-12-31 | Caterpillar Inc. | Systems and methods for identifying business opportunities |
US20100241507A1 (en) | 2008-07-02 | 2010-09-23 | Michael Joseph Quinn | System and method for searching, advertising, producing and displaying geographic territory-specific content in inter-operable co-located user-interface components |
US20100042456A1 (en) | 2008-07-07 | 2010-02-18 | Incentalign, Inc. | Integrated market-based allocation of resources within an enterprise |
US9824366B2 (en) | 2008-07-08 | 2017-11-21 | First Data Corporation | Customer pre-selected electronic coupons |
CN101625779A (zh) | 2008-07-11 | 2010-01-13 | 深圳富泰宏精密工业有限公司 | 移动终端及通过该移动终端进行信用卡消费的方法 |
US8295898B2 (en) | 2008-07-22 | 2012-10-23 | Bank Of America Corporation | Location based authentication of mobile device transactions |
US8285640B2 (en) | 2008-07-23 | 2012-10-09 | Ebay, Inc. | System and methods for facilitating fund transfers over a network |
US20100023386A1 (en) | 2008-07-23 | 2010-01-28 | Sol Avisar | Social networking platform for intellectual property assets |
US8229853B2 (en) | 2008-07-24 | 2012-07-24 | International Business Machines Corporation | Dynamic itinerary-driven profiling for preventing unauthorized card transactions |
US8227936B1 (en) | 2008-07-31 | 2012-07-24 | Bank Of America Corporation | Cash handling device having integrated uninterruptible power supply |
US20100036741A1 (en) | 2008-08-04 | 2010-02-11 | Marc Cleven | Application currency code for dynamic currency conversion transactions with contactless consumer transaction payment 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 |
US20100036775A1 (en) | 2008-08-08 | 2010-02-11 | Edens Corey D | Foreign currency gain/loss analysis for foreign currency exposure management |
US8744959B2 (en) | 2008-08-13 | 2014-06-03 | Moneygram International, Inc. | Electronic bill payment with variable payment options |
US8175975B2 (en) | 2008-08-18 | 2012-05-08 | Alcatel Lucent | IMS device operable for financial transaction authorization and ID cards display |
US8255324B2 (en) | 2008-09-02 | 2012-08-28 | Ebay Inc. | Systems and methods for facilitating financial transactions over a network with a gateway adapter |
US20100063873A1 (en) * | 2008-09-08 | 2010-03-11 | Elliot McGucken | Method for providing creator-centric region on displays, devices, and social networks where content owners can define rights and creating a novel rights and content repositor |
US20100076987A1 (en) | 2008-09-10 | 2010-03-25 | Benjamin Schreiner | Trust Profile Aggregation from Various Trust Record Sources |
US10970777B2 (en) | 2008-09-15 | 2021-04-06 | Mastercard International Incorporated | Apparatus and method for bill payment card enrollment |
US20100076873A1 (en) | 2008-09-22 | 2010-03-25 | Wachovia Corporation | Fee refund management |
US20100078471A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | System and method for processing peer-to-peer financial transactions |
US9026462B2 (en) | 2008-09-30 | 2015-05-05 | Apple Inc. | Portable point of purchase user interfaces |
US20100082490A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | Systems and methods for secure wireless transactions |
US8239276B2 (en) | 2008-09-30 | 2012-08-07 | Apple Inc. | On-the-go shopping list |
US10380573B2 (en) | 2008-09-30 | 2019-08-13 | Apple Inc. | Peer-to-peer financial transaction devices and methods |
US20100082485A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | Portable point of purchase devices and methods |
US20100078472A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | Group peer-to-peer financial transactions |
US20100082445A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | Smart menu options |
US8215546B2 (en) | 2008-09-30 | 2012-07-10 | Apple Inc. | System and method for transportation check-in |
US20100082455A1 (en) | 2008-09-30 | 2010-04-01 | Apple Inc. | Real-time bargain hunting |
US9037513B2 (en) | 2008-09-30 | 2015-05-19 | Apple Inc. | System and method for providing electronic event tickets |
US10026076B2 (en) | 2008-10-06 | 2018-07-17 | Mastercard International Incorporated | Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices |
KR101632438B1 (ko) | 2008-10-07 | 2016-06-21 | 삼성전자주식회사 | 사용자 맞춤형 휴대 광고 서비스를 제공하는 시스템 및 방법 |
US8429013B2 (en) * | 2008-10-15 | 2013-04-23 | Accenture Global Services Limited | Dynamic geo-location parameter for determining an impact of online behavior on offline sales |
US8606649B2 (en) * | 2008-10-31 | 2013-12-10 | Ellis Barlow Keener, JR. | Display of anomymous purchase information over the internet |
US20100119053A1 (en) | 2008-11-13 | 2010-05-13 | Buzzient, Inc. | Analytic measurement of online social media content |
US20100125492A1 (en) | 2008-11-14 | 2010-05-20 | Apple Inc. | System and method for providing contextual advertisements according to dynamic pricing scheme |
US20100125495A1 (en) | 2008-11-17 | 2010-05-20 | Smith Steven M | System and method of providing a mobile wallet at a mobile telephone |
US20100125803A1 (en) | 2008-11-17 | 2010-05-20 | Tyler Johnson | Online System for Communications Between Service Providers and Consumers |
US20100131569A1 (en) | 2008-11-21 | 2010-05-27 | Robert Marc Jamison | Method & apparatus for identifying a secondary concept in a collection of documents |
US20100131409A1 (en) * | 2008-11-22 | 2010-05-27 | Google Inc. | Identification verification with user challenge |
EP2189933A1 (fr) | 2008-11-24 | 2010-05-26 | Research in Motion | Système de paiement électronique incluant un serveur marchand et procédés correspondants |
US20120101881A1 (en) | 2008-11-25 | 2012-04-26 | Mary Theresa Taylor | Loyalty promotion apparatuses, methods and systems |
US20100130853A1 (en) * | 2008-11-25 | 2010-05-27 | General Electric Company | System for tracking object |
US8151336B2 (en) | 2008-12-10 | 2012-04-03 | At&T Intellectual Property Ii, Lp | Devices and methods for secure internet transactions |
US8225997B1 (en) | 2008-12-22 | 2012-07-24 | Sprint Communications Company L.P. | Single transit card to multiple rider trip methods and architecture |
US8376223B2 (en) | 2008-12-23 | 2013-02-19 | John S. Woronec | Method and apparatus for securely activating a credit card for a limited period of time |
US8200582B1 (en) | 2009-01-05 | 2012-06-12 | Sprint Communications Company L.P. | Mobile device password system |
US8145561B1 (en) | 2009-01-05 | 2012-03-27 | Sprint Communications Company L.P. | Phone usage pattern as credit card fraud detection trigger |
US20100174599A1 (en) | 2009-01-05 | 2010-07-08 | Apple Inc. | System and method for providing content associated with a product or service |
US8140418B1 (en) | 2009-01-09 | 2012-03-20 | Apple Inc. | Cardholder-not-present authorization |
US8255323B1 (en) | 2009-01-09 | 2012-08-28 | Apple Inc. | Motion based payment confirmation |
US8127982B1 (en) | 2009-01-09 | 2012-03-06 | Apple Inc. | Parental controls |
WO2010083454A2 (fr) | 2009-01-15 | 2010-07-22 | Visa U.S.A. Inc. | Incitations associées à des comptes financiers liés |
US8831976B2 (en) | 2009-01-22 | 2014-09-09 | Maritz Holdings Inc. | System and method for transacting purchases with a cash vendor using points and a virtual credit card |
US20100191770A1 (en) | 2009-01-27 | 2010-07-29 | Apple Inc. | Systems and methods for providing a virtual fashion closet |
US20100191622A1 (en) | 2009-01-28 | 2010-07-29 | Zvi Reiss | Distributed Transaction layer |
US8364587B2 (en) | 2009-01-28 | 2013-01-29 | First Data Corporation | Systems and methods for financial account access for a mobile device via a gateway |
US20100198626A1 (en) | 2009-02-04 | 2010-08-05 | Apple Inc. | Systems and methods for accessing shopping center services using a portable electronic device |
WO2010097711A2 (fr) | 2009-02-10 | 2010-09-02 | Homeatm | Appareil et procédé pour transactions commerciales utilisant un dispositif de communication |
US20100211499A1 (en) | 2009-02-13 | 2010-08-19 | Bank Of America Corporation | Systems, methods and computer program products for optimizing routing of financial payments |
US20100211452A1 (en) | 2009-02-16 | 2010-08-19 | D Angelo Giovanni | Digital voucher processing system |
US20100211863A1 (en) | 2009-02-19 | 2010-08-19 | Microsoft Corporation | Action-based pre-population of user profiles |
WO2010099345A2 (fr) * | 2009-02-25 | 2010-09-02 | Rumbafish Technologies, Inc. | Offre et système d'incitation basé sur un composant d'interface graphique |
US20100217682A1 (en) | 2009-02-26 | 2010-08-26 | Research In Motion Limited | System and method for capturing user inputs in electronic forms |
US20100223119A1 (en) | 2009-03-02 | 2010-09-02 | Yahoo! Inc. | Advertising Through Product Endorsements in Social Networks |
US8255278B1 (en) | 2009-03-23 | 2012-08-28 | United Services Automobile Association | Systems and methods for payment at a point of sale using a virtual check |
US20100241499A1 (en) * | 2009-03-23 | 2010-09-23 | Salvatore Crispo | Moneymail |
US8261977B2 (en) * | 2009-03-27 | 2012-09-11 | Mastercard International Incorporated | Methods and systems for using an interface and protocol extensions to perform a financial transaction |
US8799060B2 (en) | 2009-03-30 | 2014-08-05 | Transactis, Inc | Method for electronic coupon creation, deployment, transference, validation management, clearance, redemption and reporting system and and method for interactive participation of individuals and groups with coupons |
US8214292B2 (en) | 2009-04-01 | 2012-07-03 | American Express Travel Related Services Company, Inc. | Post-authorization message for a financial transaction |
US8209217B1 (en) * | 2009-04-17 | 2012-06-26 | Amazon Technologies, Inc. | Author-focused tools for scheduling an event associated with an author or with a work of the author |
US8423462B1 (en) | 2009-05-01 | 2013-04-16 | Amazon Technologies, Inc. | Real-time mobile wallet server |
US20100276484A1 (en) | 2009-05-01 | 2010-11-04 | Ashim Banerjee | Staged transaction token for merchant rating |
CA2739858C (fr) * | 2009-05-03 | 2017-07-11 | Logomotion, S.R.O. | Terminal de paiement utilisant un dispositif de communication mobile, tel qu'un telephone mobile, procede de transaction de paiement par debit direct |
US8355948B2 (en) * | 2009-05-05 | 2013-01-15 | Groupon, Inc. | System and methods for discount retailing |
US9767209B2 (en) | 2009-05-28 | 2017-09-19 | Apple Inc. | Search filtering based on expected future time and location |
US9135424B2 (en) | 2009-05-29 | 2015-09-15 | Paypal, Inc. | Secure identity binding (SIB) |
US20100306075A1 (en) | 2009-06-02 | 2010-12-02 | Apple Inc. | Systems and methods for accessing cruise services using a portable electronic device |
US20100312645A1 (en) | 2009-06-09 | 2010-12-09 | Boku, Inc. | Systems and Methods to Facilitate Purchases on Mobile Devices |
US8256671B2 (en) | 2009-06-09 | 2012-09-04 | Ebay Inc. | Progressive categoration and treatment of refund abusers |
US8191775B2 (en) | 2009-06-16 | 2012-06-05 | Ncr Corporation | Gift card account system and methods of a merchant processing a gift card |
US8244559B2 (en) | 2009-06-26 | 2012-08-14 | Microsoft Corporation | Cloud computing resource broker |
US20100332283A1 (en) | 2009-06-29 | 2010-12-30 | Apple Inc. | Social networking in shopping environments |
US8020763B1 (en) | 2009-06-30 | 2011-09-20 | Intuit Inc. | Method and system for assessing merchant risk during payment transaction |
US20110035594A1 (en) | 2009-07-27 | 2011-02-10 | Barbara Ann Fox | Apparatus and method for providing elective message tagging |
CN201532668U (zh) | 2009-08-12 | 2010-07-21 | 钒创科技股份有限公司 | 电子钱包装置 |
US20110047075A1 (en) | 2009-08-19 | 2011-02-24 | Mastercard International Incorporated | Location controls on payment card transactions |
US20110060663A1 (en) | 2009-09-10 | 2011-03-10 | Visa U.S.A. Inc. | System and Method of Providing Customer Purchase Propensity Information to Online Merchants |
US20110071843A1 (en) * | 2009-09-18 | 2011-03-24 | Michael Gilvar | Occurrence marketing tool |
US8214289B2 (en) | 2009-09-29 | 2012-07-03 | Ebay Inc. | Short codes for bill pay |
US20110082789A1 (en) | 2009-10-06 | 2011-04-07 | Apple Inc. | Vendor payment consolidation system |
US20110085667A1 (en) | 2009-10-09 | 2011-04-14 | Adgregate Markets, Inc. | Various methods and apparatuses for securing an application container |
US20110087534A1 (en) * | 2009-10-14 | 2011-04-14 | Wantsa Media (Canada), Inc. | Search queries and advertising platforms utilizing at least one social graph |
US8595058B2 (en) | 2009-10-15 | 2013-11-26 | Visa U.S.A. | Systems and methods to match identifiers |
US20110099057A1 (en) | 2009-10-22 | 2011-04-28 | Jet Lithocolor, Inc. | System and method for using a card having a 2d barcode to direct a consumer to content on a global communications network |
US20110137742A1 (en) * | 2009-12-09 | 2011-06-09 | Ebay Inc. | Payment using unique product identifier codes |
US8170921B2 (en) * | 2009-12-29 | 2012-05-01 | Ebay, Inc. | Dynamic hosted shopping cart |
US8640052B2 (en) | 2009-12-31 | 2014-01-28 | Verizon Patent And Licensing Inc. | User interface enhancements for media content access systems and methods |
CN101789151A (zh) | 2009-12-31 | 2010-07-28 | 中兴通讯股份有限公司 | 移动终端电子钱包的应用方法及移动终端 |
US8417575B2 (en) | 2010-01-19 | 2013-04-09 | Apple Inc. | On-device offline purchases using credits |
DE202011111062U1 (de) * | 2010-01-25 | 2019-02-19 | Newvaluexchange Ltd. | Vorrichtung und System für eine Digitalkonversationsmanagementplattform |
US8386327B2 (en) | 2010-01-29 | 2013-02-26 | Bank Of America Corporation | Online financial institution profile electronic checkout |
WO2011094734A2 (fr) * | 2010-02-01 | 2011-08-04 | Jumptap, Inc. | Système d'annonces publicitaires intégré |
US20110196724A1 (en) * | 2010-02-09 | 2011-08-11 | Charles Stanley Fenton | Consumer-oriented commerce facilitation services, applications, and devices |
US20110202406A1 (en) * | 2010-02-16 | 2011-08-18 | Nokia Corporation | Method and apparatus for distributing items using a social graph |
US8521124B2 (en) * | 2010-02-18 | 2013-08-27 | Verizon Patent And Licensing Inc. | Enhanced emergency services in fixed wireless networks |
US20110209049A1 (en) | 2010-02-23 | 2011-08-25 | Microsoft Corporation | Data binding for a web-based visual representation of a structured data solution |
US20110208629A1 (en) | 2010-02-25 | 2011-08-25 | Bank Of America Corporation | Customer account notification messages |
WO2011109428A1 (fr) * | 2010-03-01 | 2011-09-09 | Visa International Service Association | Appareils, procédés et systèmes d'analyse de stratégie d'investissement économétrique |
US20110218849A1 (en) | 2010-03-03 | 2011-09-08 | Rutigliano John R | Cloud platform for multiple account management & automated transaction processing |
US10621608B2 (en) * | 2010-03-05 | 2020-04-14 | Ethan Fieldman | Systems and methods for tracking referrals among a plurality of members of a social network |
US7971782B1 (en) | 2010-03-08 | 2011-07-05 | Apple Inc. | Multi-point transaction system |
US20110218870A1 (en) | 2010-03-08 | 2011-09-08 | Apple Inc. | Communication method for a roaming point-of-sale system |
US8282002B2 (en) | 2010-03-08 | 2012-10-09 | Apple Inc. | Multi-barcode scan process |
US9760885B1 (en) | 2010-03-23 | 2017-09-12 | Amazon Technologies, Inc. | Hierarchical device relationships for geolocation-based transactions |
US9922354B2 (en) | 2010-04-02 | 2018-03-20 | Apple Inc. | In application purchasing |
US8316046B2 (en) * | 2010-04-07 | 2012-11-20 | Apple Inc. | Journaling on mobile devices |
US8380177B2 (en) | 2010-04-09 | 2013-02-19 | Paydiant, Inc. | Mobile phone payment processing methods and systems |
US9558494B2 (en) | 2010-04-19 | 2017-01-31 | Tokenex, L.L.C. | Devices, systems, and methods for tokenizing sensitive information |
US20110276507A1 (en) * | 2010-05-05 | 2011-11-10 | O'malley Matthew Carl | System and method for recruiting, tracking, measuring, and improving applicants, candidates, and any resources qualifications, expertise, and feedback |
US8355987B2 (en) | 2010-05-06 | 2013-01-15 | Boku, Inc. | Systems and methods to manage information |
US8623376B2 (en) | 2010-05-14 | 2014-01-07 | Baxter International Inc. | Chimeric OspA genes, proteins, and methods of use thereof |
US8856901B2 (en) | 2010-05-26 | 2014-10-07 | Marcel Van Os | Digital handshake for authentication of devices |
US8069088B1 (en) | 2010-06-04 | 2011-11-29 | Google Inc. | Method and system for crediting a retailer for an internet purchase |
US20110320250A1 (en) * | 2010-06-25 | 2011-12-29 | Microsoft Corporation | Advertising products to groups within social networks |
US8442913B2 (en) | 2010-06-29 | 2013-05-14 | Visa International Service Association | Evolving payment device |
US8442914B2 (en) | 2010-07-06 | 2013-05-14 | Mastercard International Incorporated | Virtual wallet account with automatic-loading |
US8751395B2 (en) | 2010-08-03 | 2014-06-10 | Moneygram International, Inc. | Verification methods for fraud prevention in money transfer receive transactions |
US20120054049A1 (en) * | 2010-08-26 | 2012-03-01 | EPoST Systems, LLC. | Tracking chain-of-commerce data through point-of-sale transactions |
US20120136780A1 (en) * | 2010-08-27 | 2012-05-31 | Khalid El-Awady | Account number based bill payment platform apparatuses, methods and systems |
US20120150598A1 (en) * | 2010-09-02 | 2012-06-14 | Alfred William Griggs | Social retail referral control apparatuses, methods and systems |
US9558481B2 (en) | 2010-09-28 | 2017-01-31 | Barclays Bank Plc | Secure account provisioning |
US20120084135A1 (en) * | 2010-10-01 | 2012-04-05 | Smartslips Inc. | System and method for tracking transaction records in a network |
US20120089446A1 (en) * | 2010-10-07 | 2012-04-12 | Microsoft Corporation | Publishing Commercial Information in a Social Network |
US8458079B2 (en) | 2010-10-14 | 2013-06-04 | Morgan Stanley | Computer-implemented systems and methods for determining liquidity cycle for tradable financial products and for determining flow-weighted average pricing for same |
US20120124496A1 (en) | 2010-10-20 | 2012-05-17 | Mark Rose | Geographic volume analytics apparatuses, methods and systems |
WO2012057997A1 (fr) | 2010-10-29 | 2012-05-03 | Google Inc. | Incitations de partage multimédia |
US8424756B2 (en) | 2010-11-11 | 2013-04-23 | Apple Inc. | Combined business/gift card with redemption notification |
US9785988B2 (en) | 2010-11-24 | 2017-10-10 | Digital River, Inc. | In-application commerce system and method with fraud prevention, management and control |
US8312096B2 (en) | 2010-12-08 | 2012-11-13 | Google Inc. | Priority inbox notifications and synchronization for mobile messaging application |
US9691055B2 (en) | 2010-12-17 | 2017-06-27 | Google Inc. | Digital wallet |
US8352749B2 (en) | 2010-12-17 | 2013-01-08 | Google Inc. | Local trusted services manager for a contactless smart card |
US8621168B2 (en) | 2010-12-17 | 2013-12-31 | Google Inc. | Partitioning the namespace of a contactless smart card |
US8807440B1 (en) | 2010-12-17 | 2014-08-19 | Google Inc. | Routing secure element payment requests to an alternate application |
EP2656281A4 (fr) | 2010-12-20 | 2015-01-14 | Antonio Claudiu Eram | Système, procédé et appareil pour permettre des paiements mobiles et exécuter des commandes |
US20120173431A1 (en) | 2010-12-30 | 2012-07-05 | First Data Corporation | Systems and methods for using a token as a payment in a transaction |
US8195576B1 (en) | 2011-01-31 | 2012-06-05 | Bank Of America Corporation | Mobile transaction device security system |
WO2012106655A2 (fr) | 2011-02-05 | 2012-08-09 | Visa International Service Association | Appareils, procédés et systèmes de plateforme de liaison marchand-consommateur |
US8521607B2 (en) | 2011-02-22 | 2013-08-27 | Ricoh Company, Ltd. | Archiving system and process for transaction records |
WO2012118870A1 (fr) * | 2011-02-28 | 2012-09-07 | Visa International Service Association | Appareils, procédés et systèmes de transaction anonyme sécurisée |
US20120231844A1 (en) | 2011-03-11 | 2012-09-13 | Apriva, Llc | System and device for facilitating a transaction by consolidating sim, personal token, and associated applications for electronic wallet transactions |
US9760871B1 (en) | 2011-04-01 | 2017-09-12 | Visa International Service Association | Event-triggered business-to-business electronic payment processing apparatuses, methods and systems |
US8412630B2 (en) | 2011-04-15 | 2013-04-02 | Bank Of America Corporation | Social network payment settlement system |
US8943574B2 (en) | 2011-05-27 | 2015-01-27 | Vantiv, Llc | Tokenizing sensitive data |
EP2715633A4 (fr) | 2011-06-03 | 2014-12-17 | Visa Int Service Ass | Appareils, procédés et systèmes de sélection de carte de portefeuille virtuel |
US20120323664A1 (en) | 2011-06-16 | 2012-12-20 | Apple Inc. | Integrated coupon storage, discovery, and redemption system |
US8326769B1 (en) | 2011-07-01 | 2012-12-04 | Google Inc. | Monetary transfer in a social network |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
US20130054454A1 (en) | 2011-08-18 | 2013-02-28 | Thomas Purves | Wallet Service Enrollment Platform Apparatuses, Methods and Systems |
US20130030922A1 (en) | 2011-07-26 | 2013-01-31 | Google Inc. | System and method for syndicating a conversation |
US8412945B2 (en) | 2011-08-09 | 2013-04-02 | CloudPassage, Inc. | Systems and methods for implementing security in a cloud computing environment |
US20130041811A1 (en) * | 2011-08-11 | 2013-02-14 | Anh Vazquez | Unified payment service |
US20150154588A1 (en) | 2011-08-18 | 2015-06-04 | Visa International Service Association | Reversed User Account Generation 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 |
US10318941B2 (en) | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
US8180289B1 (en) | 2011-09-26 | 2012-05-15 | Google Inc. | Public kiosk providing near field communication services |
US8401904B1 (en) | 2011-11-13 | 2013-03-19 | Google Inc. | Real-time payment authorization |
US10096022B2 (en) | 2011-12-13 | 2018-10-09 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
US9953378B2 (en) | 2012-04-27 | 2018-04-24 | Visa International Service Association | Social checkout widget generation and integration apparatuses, methods and systems |
US8826143B2 (en) | 2012-03-14 | 2014-09-02 | International Business Machines Corporation | Central logout from multiple websites |
US9741045B1 (en) | 2012-03-16 | 2017-08-22 | Square, Inc. | Ranking of merchants for cardless payment transactions |
US20130346302A1 (en) | 2012-06-20 | 2013-12-26 | Visa International Service Association | Remote Portal Bill Payment Platform Apparatuses, Methods and Systems |
US20140172472A1 (en) | 2012-12-19 | 2014-06-19 | Amadeus S.A.S. | Secured payment travel reservation system |
US9940610B1 (en) | 2013-02-15 | 2018-04-10 | Amazon Technologies, Inc. | Payments portal |
US20140258110A1 (en) | 2013-03-11 | 2014-09-11 | Digimarc Corporation | Methods and arrangements for smartphone payments and transactions |
US20140281886A1 (en) | 2013-03-14 | 2014-09-18 | Media Direct, Inc. | Systems and methods for creating or updating an application using website content |
US20140282371A1 (en) | 2013-03-14 | 2014-09-18 | Media Direct, Inc. | Systems and methods for creating or updating an application using a pre-existing application |
US20160232515A1 (en) | 2013-09-20 | 2016-08-11 | Lucova Inc. | Systems and methods for facilitating mobile commerce interactions between customers and merchants |
US9430579B2 (en) | 2013-12-12 | 2016-08-30 | Axure Software Solutions, Inc. | Hybrid web publishing system |
US9558751B2 (en) | 2014-01-31 | 2017-01-31 | Sparcq, Inc. | Media content marking and tracking methods and apparatus |
WO2015142765A1 (fr) | 2014-03-17 | 2015-09-24 | Coinbase, Inc | Système informatique hôte pour bitcoins |
US20150347989A1 (en) | 2014-05-28 | 2015-12-03 | Cisco Technology, Inc. | Payment Gateway Interface |
CN104144207B (zh) | 2014-05-30 | 2016-09-07 | 腾讯科技(深圳)有限公司 | 界面加载方法和系统及装置 |
US9622142B2 (en) | 2014-08-25 | 2017-04-11 | International Business Machines Corporation | System and method en-route wireless network access |
US10083488B2 (en) | 2014-10-23 | 2018-09-25 | Salesforce.Com, Inc. | Purchasing contact information from an electronically displayed map |
US20170185989A1 (en) | 2015-12-28 | 2017-06-29 | Paypal, Inc. | Split group payments through a sharable uniform resource locator address for a group |
US10346829B2 (en) | 2015-12-30 | 2019-07-09 | Paypal, Inc. | Display of locally broadcasted uniform resource locators for checkout and payment |
US10360554B2 (en) | 2015-12-30 | 2019-07-23 | Paypal, Inc. | Generation of locally broadcasted uniform resource locators for checkout and payment |
US20170221062A1 (en) | 2016-01-28 | 2017-08-03 | Verifi, Inc. | Order insights system and method |
US10949822B2 (en) | 2016-03-25 | 2021-03-16 | Stripe Inc. | Methods and systems for providing payment interface services using a payment platform |
CA2970088C (fr) | 2016-09-30 | 2022-02-08 | The Toronto-Dominion Bank | Deviation de verrou de dispositif selon l'alerte |
-
2011
- 2011-10-20 US US13/278,166 patent/US20120124496A1/en not_active Abandoned
- 2011-10-20 US US13/278,173 patent/US20120215701A1/en not_active Abandoned
- 2011-10-20 US US13/278,163 patent/US20120123924A1/en not_active Abandoned
- 2011-10-20 WO PCT/US2011/057180 patent/WO2012054786A1/fr active Application Filing
- 2011-10-20 US US13/278,171 patent/US8571937B2/en active Active
- 2011-10-20 US US13/278,169 patent/US20120209677A1/en not_active Abandoned
- 2011-10-20 AU AU2011316955A patent/AU2011316955B2/en active Active
-
2013
- 2013-09-25 US US14/037,162 patent/US20140214653A1/en not_active Abandoned
- 2013-09-25 US US14/037,131 patent/US10688385B2/en active Active
- 2013-09-25 US US14/036,562 patent/US9757644B2/en active Active
-
2017
- 2017-01-09 AU AU2017200131A patent/AU2017200131A1/en not_active Abandoned
- 2017-09-11 US US15/701,391 patent/US10500481B2/en active Active
-
2018
- 2018-08-13 AU AU2018214967A patent/AU2018214967A1/en not_active Abandoned
-
2019
- 2019-11-26 US US16/696,662 patent/US11311797B2/en active Active
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010044774A1 (en) * | 2000-04-28 | 2001-11-22 | Tatsuya Sasazawa | Processing system and recording medium for economic data in a virtual space |
US20050177464A1 (en) * | 2000-06-19 | 2005-08-11 | E4X Inc. | System and method for multiple currency transactions |
US20030233286A1 (en) * | 2002-05-10 | 2003-12-18 | Hahn-Carlson Dean W. | Automated transaction processing system and approach |
US20070061250A1 (en) * | 2005-09-15 | 2007-03-15 | Itake Technology Co., Ltd. | System and method for virtual capital operation on the internet |
US20100216542A1 (en) * | 2005-10-14 | 2010-08-26 | Andrew Van Luchene | Agreements in video games permitting virtual and real world penalties obligations and remedies |
US20070087820A1 (en) * | 2005-10-14 | 2007-04-19 | Leviathan Entertainment, Llc | Financial institutions and instruments in a virtual environment |
US20070087822A1 (en) * | 2005-10-14 | 2007-04-19 | Leviathan Entertainment, Llc | Financing Options in a Virtual Environment |
US7645194B2 (en) * | 2005-10-14 | 2010-01-12 | Leviathan Entertainment, Llc | Financial institutions and instruments in a virtual environment |
US20080167965A1 (en) * | 2007-01-09 | 2008-07-10 | Von Nothaus Bernard | Apparatus, system, and method for extracting real world value from a virtual account |
US20100227675A1 (en) * | 2009-03-06 | 2010-09-09 | Zynga Game Network, Inc. | Virtual Playing Chips in a Multiuser Online Game Network |
US20110258031A1 (en) * | 2009-06-29 | 2011-10-20 | David Valin | Method and process for registration, creation and management of campaigns and advertisements in a network system |
US20110212762A1 (en) * | 2009-09-30 | 2011-09-01 | Matthew Ocko | Apparatuses, methods and systems for a multi-level in-game currency platform |
US20120005030A1 (en) * | 2010-07-04 | 2012-01-05 | David Valin | Apparatus for connecting Protect Anything Human Key identification mechanism to objects, content, and virtual currency for identification, tracking, delivery, advertising and marketing |
US20120022981A1 (en) * | 2010-07-20 | 2012-01-26 | Jared Morgenstern | Creation, redemption, and accounting in a virtual currency system |
Cited By (167)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9361616B2 (en) * | 2002-10-01 | 2016-06-07 | Dylan T X Zhou | One-scan and one-touch payment and buying using haptic control via messaging and calling multimedia system on mobile and wearable device, currency token interface, point of sale device, and electronic payment card |
US10504126B2 (en) | 2009-01-21 | 2019-12-10 | Truaxis, Llc | System and method of obtaining merchant sales information for marketing or sales teams |
US10594870B2 (en) | 2009-01-21 | 2020-03-17 | Truaxis, Llc | System and method for matching a savings opportunity using census data |
US9477730B2 (en) * | 2010-10-28 | 2016-10-25 | Microsoft Technology Licensing, Llc | Web services runtime for dataset transformation |
US20120109937A1 (en) * | 2010-10-28 | 2012-05-03 | Microsoft Corporation | Web services runtime for dataset transformation |
US20120150669A1 (en) * | 2010-12-13 | 2012-06-14 | Langley Garrett S | System and method for point of service payment acceptance via wireless communication |
US9292870B2 (en) * | 2010-12-13 | 2016-03-22 | Qualcomm Incorporated | System and method for point of service payment acceptance via wireless communication |
US11288661B2 (en) | 2011-02-16 | 2022-03-29 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
US11900359B2 (en) | 2011-07-05 | 2024-02-13 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US9704155B2 (en) | 2011-07-29 | 2017-07-11 | Visa International Service Association | Passing payment tokens through an hop/sop |
US11803825B2 (en) | 2011-08-18 | 2023-10-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US11397931B2 (en) | 2011-08-18 | 2022-07-26 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US11763294B2 (en) | 2011-08-18 | 2023-09-19 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
US11037138B2 (en) * | 2011-08-18 | 2021-06-15 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods, and systems |
US11354723B2 (en) | 2011-09-23 | 2022-06-07 | Visa International Service Association | Smart shopping cart with E-wallet store injection search |
US11170355B2 (en) * | 2011-10-31 | 2021-11-09 | Ncr Corporation | Techniques for mobile transaction processing |
US20140250013A1 (en) * | 2011-10-31 | 2014-09-04 | Ncr Corporation | Techniques for mobile transaction processing |
US10586250B1 (en) * | 2011-11-18 | 2020-03-10 | Amazon Technologies, Inc. | Incentivized crowd-source pricing |
US20150012414A1 (en) * | 2011-12-28 | 2015-01-08 | Rakuten, Inc. | Electronic money server, electronic money processing method, electronic money processing program product, and storage medium on which electronic money processing program product is stored |
US10262361B2 (en) * | 2011-12-28 | 2019-04-16 | Rakuten, Inc. | Electronic money server, electronic money processing method, electronic money processing program product, and storage medium on which electronic money processing program product is stored |
US20130179341A1 (en) * | 2012-01-06 | 2013-07-11 | Bruce Boudreau | Virtual wallet |
US11074218B2 (en) | 2012-02-02 | 2021-07-27 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia merchant analytics database platform apparatuses, methods and systems |
US11663578B2 (en) | 2012-02-17 | 2023-05-30 | Paypal, Inc. | Login using QR code |
US10963862B2 (en) | 2012-02-17 | 2021-03-30 | Paypal, Inc. | Login using QR code |
US10504103B2 (en) * | 2012-02-17 | 2019-12-10 | Paypal, Inc. | Login using QR code |
US20160162875A1 (en) * | 2012-02-17 | 2016-06-09 | Paypal, Inc. | Login using qr code |
US20150032816A1 (en) * | 2012-05-30 | 2015-01-29 | Sony Corporation | Information processing apparatus, information processing method, and recording medium |
US20130325701A1 (en) * | 2012-06-05 | 2013-12-05 | International Business Machines Corporation | E-currency validation and authorization services platform |
WO2013188820A3 (fr) * | 2012-06-15 | 2014-02-27 | Nyz Holdings Inc. | Appareil, procédés et produits manufacturés destinés à des transactions en monnaie virtuelle |
WO2013188820A2 (fr) * | 2012-06-15 | 2013-12-19 | Nyz Holdings Inc. | Appareil, procédés et produits manufacturés destinés à des transactions en monnaie virtuelle |
US10169787B2 (en) * | 2012-06-29 | 2019-01-01 | Paypal, Inc. | Method, medium, and system for session based shopping |
WO2014004342A2 (fr) * | 2012-06-29 | 2014-01-03 | Music One Live, Llc | Systèmes et procédés pour intégrer des ventes géolocalisées à des plateformes de média social |
US20140006206A1 (en) * | 2012-06-29 | 2014-01-02 | Ebay, Inc. | Shopping Assistive Device and Commerce Infrastructure |
WO2014004342A3 (fr) * | 2012-06-29 | 2014-04-03 | Music One Live, Llc | Systèmes et procédés pour intégrer des ventes géolocalisées à des plateformes de média social |
US9262739B2 (en) * | 2012-06-29 | 2016-02-16 | Paypal, Inc. | Method, medium, and system for session based shopping |
US10185954B2 (en) | 2012-07-05 | 2019-01-22 | Google Llc | Selecting a preferred payment instrument based on a merchant category |
US9251530B1 (en) * | 2012-08-31 | 2016-02-02 | Sprinklr, Inc. | Apparatus and method for model-based social analytics |
US9288123B1 (en) | 2012-08-31 | 2016-03-15 | Sprinklr, Inc. | Method and system for temporal correlation of social signals |
US10878444B2 (en) | 2012-08-31 | 2020-12-29 | Sprinklr, Inc. | Method and system for correlating social media conversions |
US10003560B1 (en) | 2012-08-31 | 2018-06-19 | Sprinklr, Inc. | Method and system for correlating social media conversations |
US9641556B1 (en) | 2012-08-31 | 2017-05-02 | Sprinklr, Inc. | Apparatus and method for identifying constituents in a social network |
US10489817B2 (en) | 2012-08-31 | 2019-11-26 | Sprinkler, Inc. | Method and system for correlating social media conversions |
US9959548B2 (en) | 2012-08-31 | 2018-05-01 | Sprinklr, Inc. | Method and system for generating social signal vocabularies |
US20140074655A1 (en) * | 2012-09-07 | 2014-03-13 | David Lim | System, apparatus and methods for online one-tap account addition and checkout |
US20140075329A1 (en) * | 2012-09-10 | 2014-03-13 | Samsung Electronics Co. Ltd. | Method and device for transmitting information related to event |
US9576282B2 (en) * | 2012-10-15 | 2017-02-21 | Bank Of America Corporation | Merchant category code (“MCC”) based acceptance cost recovery |
US20140108166A1 (en) * | 2012-10-15 | 2014-04-17 | Bank Of America Corporation | Merchant category code ("mcc") based acceptance cost recovery |
US10121268B2 (en) | 2012-12-04 | 2018-11-06 | Entit Software Llc | Displaying information technology conditions with heat maps |
US10318924B2 (en) * | 2012-12-18 | 2019-06-11 | salesforce.com,inc. | User interface date selectors for historical reports |
US20140173513A1 (en) * | 2012-12-18 | 2014-06-19 | Salesforce.Com, Inc. | User interface date selectors for historical reports |
US9799029B2 (en) * | 2012-12-31 | 2017-10-24 | Zukunftware, Llc | Securely receiving data input at a computing device without storing the data locally |
US20140188734A1 (en) * | 2012-12-31 | 2014-07-03 | Volker Neuwirth | Securely Receiving Data Input At A Computing Device Without Storing The Data Locally |
US9679284B2 (en) | 2013-03-04 | 2017-06-13 | Google Inc. | Selecting a preferred payment instrument |
US9092767B1 (en) | 2013-03-04 | 2015-07-28 | Google Inc. | Selecting a preferred payment instrument |
US10579981B2 (en) | 2013-03-04 | 2020-03-03 | Google Llc | Selecting a preferred payment instrument |
US10286298B1 (en) * | 2013-06-18 | 2019-05-14 | Electronic Arts Inc. | Dynamically adjusting virtual rewards presented in offers |
US11783417B1 (en) * | 2013-06-28 | 2023-10-10 | Gemini Ip, Llc | Systems for redeeming shares in an entity holding digital math-based assets |
US10325257B1 (en) | 2013-06-28 | 2019-06-18 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
US10068228B1 (en) | 2013-06-28 | 2018-09-04 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
US11087313B1 (en) * | 2013-06-28 | 2021-08-10 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US11423482B1 (en) * | 2013-06-28 | 2022-08-23 | Gemini Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
US10002389B1 (en) * | 2013-06-28 | 2018-06-19 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
US11568398B1 (en) * | 2013-06-28 | 2023-01-31 | Gemini Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
US10255635B1 (en) * | 2013-06-28 | 2019-04-09 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
US11580532B1 (en) | 2013-06-28 | 2023-02-14 | Gemini Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US10269009B1 (en) * | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US11017381B1 (en) | 2013-06-28 | 2021-05-25 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US9965804B1 (en) * | 2013-06-28 | 2018-05-08 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
US9965805B1 (en) * | 2013-06-28 | 2018-05-08 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
US11615404B1 (en) * | 2013-06-28 | 2023-03-28 | Gemini Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
US10984470B1 (en) * | 2013-06-28 | 2021-04-20 | Winklevoss Ip, Llc | Systems for redeeming shares in an entity holding digital math-based assets |
US10984472B1 (en) * | 2013-06-28 | 2021-04-20 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
US10354325B1 (en) | 2013-06-28 | 2019-07-16 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
US11928732B1 (en) * | 2013-06-28 | 2024-03-12 | Gemini Ip, Llc | Computer-generated graphical user interface |
US10929929B1 (en) * | 2013-06-28 | 2021-02-23 | Winklevoss Ip, Llc | Systems for purchasing shares in an entity holding digital math-based assets |
US11282139B1 (en) * | 2013-06-28 | 2022-03-22 | Gemini Ip, Llc | Systems, methods, and program products for verifying digital assets held in a custodial digital asset wallet |
US10650376B1 (en) | 2013-06-28 | 2020-05-12 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
US9898782B1 (en) * | 2013-06-28 | 2018-02-20 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
US9892460B1 (en) * | 2013-06-28 | 2018-02-13 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
US11164251B1 (en) * | 2013-06-28 | 2021-11-02 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
US11144903B2 (en) | 2013-09-02 | 2021-10-12 | Paypal, Inc. | Optimized multiple digital wallet presentation |
US11720875B2 (en) | 2013-09-02 | 2023-08-08 | Paypal, Inc. | Optimized multiple digital wallet presentation |
US10552818B2 (en) * | 2013-09-02 | 2020-02-04 | Paypal, Inc. | Optimized multiple digital wallet presentation |
US20150170112A1 (en) * | 2013-10-04 | 2015-06-18 | Erly Dalvo DeCastro | Systems and methods for providing multi-currency platforms comprising means for exchanging and interconverting tangible and virtual currencies in various transactions, banking operations, and wealth management scenarios |
US10528924B2 (en) * | 2013-11-22 | 2020-01-07 | International Business Machines Corporation | Self-aware token |
US20150149343A1 (en) * | 2013-11-22 | 2015-05-28 | International Business Machines Corporation | Self-aware token |
CN104657899A (zh) * | 2013-11-22 | 2015-05-27 | 国际商业机器公司 | 用于处理有自我意识的代币的方法和系统 |
US10726098B2 (en) * | 2014-01-23 | 2020-07-28 | Dror Samuel Brama | Method, system and program product for transferring genetic and health data |
US20190268238A1 (en) * | 2014-04-04 | 2019-08-29 | Carii, Inc | Methods, systems, and computer-readable media for providing community-based information networks |
US9483797B1 (en) * | 2014-04-21 | 2016-11-01 | Intuit Inc. | Method and system for recording a transaction using a dynamic user interface within an application |
US20150324828A1 (en) * | 2014-05-09 | 2015-11-12 | Myworld, Inc. | Commerce System and Method of Providing Communication Between Publishers and Intelligent Personal Agents |
US20150363769A1 (en) * | 2014-06-16 | 2015-12-17 | Bank Of America Corporation | Cryptocurrency Real-Time Conversion System |
US11875382B2 (en) * | 2014-06-19 | 2024-01-16 | Go Daddy Operating Company, LLC | Software application customized for target market |
US20210233112A1 (en) * | 2014-06-19 | 2021-07-29 | Go Daddy Operating Company, LLC | Software application customized for target market |
US20150371222A1 (en) * | 2014-06-19 | 2015-12-24 | Go Daddy Operating Company, LLC | Website content optimization for target market |
US20160012111A1 (en) * | 2014-07-10 | 2016-01-14 | Oracle International Corporation | Embedding analytics within transaction search |
US10585892B2 (en) | 2014-07-10 | 2020-03-10 | Oracle International Corporation | Hierarchical dimension analysis in multi-dimensional pivot grids |
US10606855B2 (en) * | 2014-07-10 | 2020-03-31 | Oracle International Corporation | Embedding analytics within transaction search |
US11379846B2 (en) * | 2014-09-29 | 2022-07-05 | Mastercard International Incorporated | Product authentication over a payment network |
US20160092875A1 (en) * | 2014-09-29 | 2016-03-31 | Mastercard International Incorporated | Product authentication over a payment network |
US9727655B2 (en) * | 2014-10-03 | 2017-08-08 | Throughtek Technology (Shenzhen) Co., Ltd. | Searching system, method and P2P device for P2P device community |
US20160098486A1 (en) * | 2014-10-03 | 2016-04-07 | Throughtek Technology (Shenzhen) Co., Ltd. | Searching system, method and p2p device for p2p device community |
US9690781B1 (en) * | 2014-10-17 | 2017-06-27 | James E. Niles | System for automatically changing language of an interactive informational display for a user by referencing a personal electronic device of the user |
JP2016126669A (ja) * | 2015-01-07 | 2016-07-11 | 株式会社イントラスト | 情報管理サーバ及びその方法 |
US20170310561A1 (en) * | 2015-01-08 | 2017-10-26 | Huawei Technologies Co., Ltd. | Network Control Method and Apparatus |
US10511494B2 (en) * | 2015-01-08 | 2019-12-17 | Huawei Technologies Co., Ltd. | Network control method and apparatus |
US10484376B1 (en) | 2015-01-26 | 2019-11-19 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
US11283797B2 (en) | 2015-01-26 | 2022-03-22 | Gemini Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
US10778682B1 (en) | 2015-01-26 | 2020-09-15 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
US11941008B2 (en) | 2015-02-08 | 2024-03-26 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
US11783323B1 (en) | 2015-03-16 | 2023-10-10 | Gemini Ip, Llc | Autonomous devices |
US10915891B1 (en) | 2015-03-16 | 2021-02-09 | Winklevoss Ip, Llc | Autonomous devices |
US11362814B1 (en) | 2015-03-16 | 2022-06-14 | Gemini Ip, Llc | Autonomous devices |
US10693632B1 (en) | 2015-03-16 | 2020-06-23 | Winklevoss Ip, Llc | Autonomous devices |
US10565750B2 (en) * | 2015-08-31 | 2020-02-18 | Accenture Global Solutions Limited | Intelligent visualization munging |
US10347019B2 (en) | 2015-08-31 | 2019-07-09 | Accenture Global Solutions Limited | Intelligent data munging |
US20170064398A1 (en) * | 2015-08-31 | 2017-03-02 | Verizon Patent And Licensing Inc. | Video on demand platform |
US9743146B2 (en) * | 2015-08-31 | 2017-08-22 | Verizon Patent And Licensing Inc. | Video on demand platform |
US20170061659A1 (en) * | 2015-08-31 | 2017-03-02 | Accenture Global Solutions Limited | Intelligent visualization munging |
US10331899B2 (en) | 2015-10-24 | 2019-06-25 | Oracle International Corporation | Display of dynamic contextual pivot grid analytics |
US10642990B2 (en) | 2015-10-24 | 2020-05-05 | Oracle International Corporation | Generation of dynamic contextual pivot grid analytics |
US10977639B2 (en) | 2016-01-25 | 2021-04-13 | Freelancer Technology Pty Limited | Adaptive gateway switching system |
USD822689S1 (en) * | 2016-02-14 | 2018-07-10 | Paypal, Inc. | Display screen or portion thereof with animated graphical user interface |
US11379911B2 (en) * | 2016-04-28 | 2022-07-05 | Tencent Technology (Shenzhen) Company Limited | System, method, and apparatus for supporting cash currency exchange |
US20180349987A1 (en) * | 2016-04-28 | 2018-12-06 | Tencent Technology (Shenzhen) Company Limited | System, method, and apparatus for supporting cash currency exchange |
JP6071025B1 (ja) * | 2016-08-27 | 2017-02-01 | 株式会社ギフトプライス | 商品代理購入装置 |
US10805238B1 (en) | 2016-09-23 | 2020-10-13 | Amazon Technologies, Inc. | Management of alternative resources |
US10666569B1 (en) * | 2016-09-23 | 2020-05-26 | Amazon Technologies, Inc. | Journal service with named clients |
US20180121260A1 (en) * | 2016-10-31 | 2018-05-03 | Intuit Inc. | Defining variability schemas in an application programming interface (api) |
US10636029B2 (en) | 2016-11-14 | 2020-04-28 | Bank Of America Corporation | System for priority presentation integration on third party systems for limiting resource disbursement |
US10922683B2 (en) | 2016-11-14 | 2021-02-16 | Bank Of America Corporation | System for priority presentation integration on third party systems for limiting resource disbursement |
WO2018132816A1 (fr) * | 2017-01-13 | 2018-07-19 | Skale Company | Procédé, appareil et support lisible par ordinateur pour classer des messages dans un réseau social sur la base d'une devise virtuelle |
US11379550B2 (en) * | 2017-08-29 | 2022-07-05 | Paypal, Inc. | Seamless service on third-party sites |
US20190130376A1 (en) * | 2017-10-31 | 2019-05-02 | Ncr Corporation | Voice-device aided operation |
US10630769B2 (en) * | 2017-12-26 | 2020-04-21 | Akamai Technologies, Inc. | Distributed system of record transaction receipt handling in an overlay network |
US11416924B2 (en) | 2018-01-12 | 2022-08-16 | Wells Fargo Bank, N.A. | Bill presentment based on a user learning style |
US11139955B1 (en) | 2018-02-12 | 2021-10-05 | Winklevoss Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US11200569B1 (en) | 2018-02-12 | 2021-12-14 | Winklevoss Ip, Llc | System, method and program product for making payments using fiat-backed digital assets |
US11308487B1 (en) | 2018-02-12 | 2022-04-19 | Gemini Ip, Llc | System, method and program product for obtaining digital assets |
US10373158B1 (en) | 2018-02-12 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
US11475442B1 (en) | 2018-02-12 | 2022-10-18 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
US10540654B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US11522700B1 (en) | 2018-02-12 | 2022-12-06 | Gemini Ip, Llc | Systems, methods, and program products for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US11909860B1 (en) | 2018-02-12 | 2024-02-20 | Gemini Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
US10540653B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
US11720887B1 (en) | 2018-03-05 | 2023-08-08 | Gemini Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
US11727401B1 (en) | 2018-03-05 | 2023-08-15 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US11017391B1 (en) | 2018-03-05 | 2021-05-25 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US10540640B1 (en) | 2018-03-05 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US11562333B1 (en) | 2018-03-05 | 2023-01-24 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US10929842B1 (en) | 2018-03-05 | 2021-02-23 | Winklevoss Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
US10373129B1 (en) | 2018-03-05 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US10438290B1 (en) | 2018-03-05 | 2019-10-08 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
US11334883B1 (en) | 2018-03-05 | 2022-05-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding and/or distributing collateral as a stable value token in the form of digital assets |
US11315107B2 (en) * | 2018-03-15 | 2022-04-26 | Jpmorgan Chase Bank, N.A. | Automated purchase card disable system and method |
US20190287094A1 (en) * | 2018-03-15 | 2019-09-19 | Jpmorgan Chase Bank, N.A. | Automated purchase card disable system and method |
US20200013049A1 (en) * | 2018-03-20 | 2020-01-09 | Carl B. Ingram | Coin-Basis application designed to calculate the basis of crypto currency |
WO2020061239A1 (fr) * | 2018-09-18 | 2020-03-26 | Mx Technologies, Inc. | Sous-comptes virtuels |
EP3779697A4 (fr) * | 2018-09-30 | 2021-07-28 | Advanced New Technologies Co., Ltd. | Procédé, dispositif et appareil de traitement de données |
US11176161B2 (en) | 2018-09-30 | 2021-11-16 | Advanced New Technologies Co., Ltd. | Data processing method, apparatus, and device |
US20200250658A1 (en) * | 2019-01-31 | 2020-08-06 | Fujitsu Limited | Information processing apparatus, information processing method, and computer-readable recording medium |
US11501370B1 (en) | 2019-06-17 | 2022-11-15 | Gemini Ip, Llc | Systems, methods, and program products for non-custodial trading of digital assets on a digital asset exchange |
US20210287200A1 (en) * | 2019-08-30 | 2021-09-16 | Advanced New Technologies Co., Ltd. | Recommending target transaction code setting region |
US11687911B2 (en) * | 2020-09-10 | 2023-06-27 | Block, Inc. | Application integration for contactless payments |
US11100490B1 (en) * | 2020-09-10 | 2021-08-24 | Square, Inc. | Application integration for contactless payments |
US20220076236A1 (en) * | 2020-09-10 | 2022-03-10 | Square, Inc. | Application integration for contactless payments |
US11544695B2 (en) | 2020-09-10 | 2023-01-03 | Block, Inc. | Transaction identification by comparison of merchant transaction data and context data |
Also Published As
Publication number | Publication date |
---|---|
US9757644B2 (en) | 2017-09-12 |
US10500481B2 (en) | 2019-12-10 |
US20200094133A1 (en) | 2020-03-26 |
US20140213344A1 (en) | 2014-07-31 |
US8571937B2 (en) | 2013-10-29 |
AU2011316955B2 (en) | 2016-12-01 |
US20120209677A1 (en) | 2012-08-16 |
AU2017200131A1 (en) | 2017-02-02 |
US20120124496A1 (en) | 2012-05-17 |
AU2011316955A1 (en) | 2013-05-30 |
AU2018214967A1 (en) | 2018-08-30 |
US20120215648A1 (en) | 2012-08-23 |
US20120215701A1 (en) | 2012-08-23 |
US20140222594A1 (en) | 2014-08-07 |
US10688385B2 (en) | 2020-06-23 |
WO2012054786A1 (fr) | 2012-04-26 |
US20180056179A1 (en) | 2018-03-01 |
US11311797B2 (en) | 2022-04-26 |
US20140214653A1 (en) | 2014-07-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11311797B2 (en) | Dynamic payment optimization apparatuses, methods and systems | |
US11900359B2 (en) | Electronic wallet checkout platform apparatuses, methods and systems | |
US20220253832A1 (en) | Snap mobile payment apparatuses, methods and systems | |
US10853797B2 (en) | Cloud-based virtual wallet NFC apparatuses, methods and systems | |
US10586227B2 (en) | Snap mobile payment apparatuses, methods and systems | |
US9773212B2 (en) | Secure anonymous transaction apparatuses, methods and systems | |
US8577803B2 (en) | Virtual wallet card selection apparatuses, methods and systems | |
US20140249999A1 (en) | Multiple Merchant Payment Processor Platform Apparatuses, Methods and Systems | |
US20120158589A1 (en) | Social Media Payment Platform Apparatuses, Methods and Systems | |
US20120316992A1 (en) | Payment privacy tokenization apparatuses, methods and systems | |
US20130159081A1 (en) | Bidirectional bandwidth reducing notifications and targeted incentive platform apparatuses, methods and systems | |
WO2013009660A1 (fr) | Appareils, procédés et systèmes de plate-forme d'incitation ciblée et à notifications réduisant la largeur de bande bidirectionnelle |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PLAYSPAN INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROSE, MARK;DUTTA, RAJIV;BAYER, LEX N.;SIGNING DATES FROM 20120106 TO 20120109;REEL/FRAME:027601/0915 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |