Patent Grant
11961147
This invention relates to magnetic cards and devices and associated payment systems.
Systems and methods are provided for allowing a user to select an additional service to be performed in addition to the payment of goods with a payment card or other device (e.g., a mobile telephonic device, a tablet computer device, or another electronic device). A card, or other device, may include one or more buttons. A user may associate an additional service to a button of a card at any time. At the time of purchase, information indicative of the button that the user selected may be passed to a point-of-sale system with a user's payment information. Such data may be, for example, communicated through a merchant acquirer's network to a processing facility. The processing facility may, for example, authorize a payment transaction and forward the information indicative of the button a user selected and the identity of a user to a remote facility. Such a remote facility may, for example, forward at least some of such information, as well as additional information, to a third party application such that the third party application enacts the additional feature desired by the user.
Such an additional feature may include, for example, a game action in an online game by a game application, a check-in operation at a location by a check-in application, redemption of a coupon or voucher by a third party application, accumulation of loyalty points by a third party loyalty application, rating of a transaction or location by a rating application, any combination of such features, or any additional feature.
Selection of an application may be provided, for example, by a Graphical User Interface (GUI) provided on a computing device (e.g., a mobile telephonic device) as a software application for that device or via the internet or an intranet through a web browser. Such a selection may be provided with a non-powered card such that a single feature may be associated with a card for a period of time. Such a selection may be associated to an option (e.g., a button) on a powered card or other device (e.g., a mobile telephonic device) such that the user may associate different features with different options (e.g., different buttons). Accordingly, for example, a user may receive a powered card, or other device, in the mail and use his/her web browser to associate different additional features to different buttons. The user may then utilize the card in a store and press a button in order to select that feature. A card, or other device, may download information (e.g., via a wireless communication such as a light or electromagnetic communication) such that the card, or other device, displays information next to an option indicative of the application (e.g., “Redeem LivingSocial Voucher” or “Facebook Like”). Alternatively, no download may be provided and no additional information may be displayed such that a user's card, or other device, includes a generic descriptor (e.g., “credit” and “application,” or “application 1” and “application 2,” or “debit” and “application 1” and “application 2”).
A remote facility may also receive additional information other than just a user identifier and information indicative of the option selected by a user (or that the user made a payment). Such additional information may be, for example, the type of merchant (e.g., a retail merchant or a gas merchant), the location of a merchant (e.g., the zip code of a merchant), the type of transaction (e.g., online or in-store purchase), the name of the merchant (e.g., “Amazon.com,” or “Walmart”), the amount of the transaction (e.g., $10.25), and any other information. Such a remote facility may forward such information to a third party application in addition to information generated by the remote facility (e.g., a second user identifier such that different identifiers are used with the facility sending payment information and the third party application).
An ecosystem may be provided in which a development kit is available for third parties to develop applications for payment cards or other devices. A GUI may be provided where a user can select different third party applications to be associated with a user's payment. The third party applications may need to be approved by an administrator before being accessible by a GUI. Different categories of third party applications may be provided on the GUI (e.g., a coupon category, a check-in category, a games category, a financial management tools category). The development kit may provide the ability for a third party application to, for example, receive user identification numbers and other information (e.g., merchant name and location) and provide particular information back (e.g., within a period of time) to a remote facility.
Information received from a third party application may include, for example, information indicative that the user was properly identified and a service was performed (e.g., “check-in completed,” “information added to financial management service.”). Such information may be provided back to an issuing bank, processor, or other service provider such that the information may be displayed on a user's bill statement. Additional information may also be provided that may change the way a transaction is authorized or settled.
Additional information received from a third party may be utilized to change the way a transaction is authorized or settled. For example, a third party may provide a user with the ability to pre-purchase a voucher to a particular store (e.g., a particular barber in a particular zip code). A user may associate this third party service to a button on the user's card. A user may make a purchase at this barber multiple times during a year on the user's credit account. The user may, at one such purchase, press the button associated with the desire to use the third party service and redeem a voucher the user already purchased or acquired. Information indicative of the user's desire to utilize such a service may be communicated to a point-of-sale terminal via a communications device located on the card (e.g., a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip (e.g., an EMV chip, or any other communications device). The transaction may be authorized using the user's payment account if, for example, the user has enough funds associated with that account (e.g., a credit or debit account). The third party service provider may then determine the user had a pre-paid voucher for the transaction and may return to the card issuer, processor, or other party information indicative that the user's bill is to be adjusted by the amount of the voucher. Before, or after, settlement occurs a user's bill may show a statement credit in the amount of the voucher. A remote facility may perform such a data exchange as well as any associated value exchange. For example, the remote facility may, for a fee (e.g., a percentage of a transaction or a fixed fee), provide value from the third party service provider to the card issuer or processor (e.g., via an ACH or other type of monetary transaction). Alternatively, for example, the remote facility may provide the desired value to the card issuer, processor, or other party and demand the associated value be paid to the remote facility by the third party application within a period of time (e.g., three days). Information provided by a third party application to a remote facility may include an identifier indicative of the third party application, an identifier indicative of the user, an identifier indicative of the type of service provided by the third party application, an identifier indicative of the transaction with which further action by the third party application is desired, an amount of a post-statement credit that is to be applied for a particular transaction, and amount of a post-settlement credit that is to be applied for a particular transaction, an amount of a pre-settlement credit that is to be applied for a particular transaction, an amount of a credit that is to be applied during an authorization, an additional fee that is supposed to be added to a statement for an additional service (e.g., a fee-based financial management tool service), and any other information desired by the third party service provider, processor, card issuer, remote facility, device provider, or any other entity (e.g., a card network).
Information indicative of a button press, or use of a card, that triggers a feature may be provided in a payment message utilized at authorization or at settlement. Furthermore, the service provider may return information in a period of time that permits actions to be performed pre-authorization or pre-settlement.
The payment actions may be determined, for example, via a user interaction with the card. Particularly, for example, a user may press a button on the card, from a group of buttons, that is associated with the third party feature. Such third party features may be unique from the features provided to the user via the third parties non-payment card or device services. Accordingly, a user may obtain the benefit of the whimsical and festive nature of a unique feature every time the user makes a payment. Information indicative of feature selection may be provided, for example, via an output device operable to be read by a card reader. For example, the feature may be provided by a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip, or any other type of card reader. For online purchases, for example, a display may be provided on the card and a user selection may cause a particular number (e.g., a particular code) to be displayed on the card. Such a code may be entered into a text box on a website at checkout and may be representative of the user's desired feature. Accordingly, the feature may be communicated to a remote server such that the feature may be performed in the third party service on behalf of the user. The code may additionally provide the benefits of a security code and may be entered with a payment card number (e.g., a credit or debit card number) at online or in-store checkout.
Rewards may be awarded based on the amount of a purchase. Such rewards may be associated with a third party service or a card issuer, device or card provider, or other entity. For example, an amount of game currency may be awarded by a game provider at every purchase instead of a card issuer providing an amount of points, miles, or cashback to a user. Alternatively, for example, a user may earn both rewards from a card issuer as well as rewards from a third party service provider. A user may select, via, for example, physical buttons on the card or virtual buttons on a capacitive-sensitive display of a mobile telephonic device, the type of feature the user desires. Multiple features may be provided from a particular third party service provider. For example, a game service provider may provide a feature associated with one game action and another feature associated with another game action.
A card may include a dynamic magnetic communications device. Such a dynamic magnetic communications device may take the form of a magnetic encoder or a magnetic emulator. A magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium. A magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.
All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display). Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch-screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch. Accordingly, a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode.
A card may include a number of output devices to output dynamic information. For example, a card may include one or more RFIDs or IC chips to communicate to one or more RFID readers or IC chip readers, respectively. A card may include devices to receive information. For example, an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively. A device for receiving wireless information signals may be provided. A light sensing device or sound sensing device may be utilized to receive information wirelessly. A card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device). The central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device). A processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip. The processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card.
A card may be provided with a button in which the activation of the button causes a code to be communicated through a dynamic magnetic stripe communications device (e.g., the subsequent time a read-head detector on the card detects a read-head). The code may be indicative of, for example, a feature (e.g., a payment feature). The code may be received by the card via manual input (e.g., onto buttons of the card) or via a wireless transmission (e.g., via light, electromagnetic communications, sound, or other wireless signals). A code may be communicated from a webpage (e.g., via light and/or sound) to a card. A card may include a display such that a received code may be visually displayed to a user. In doing so, the user may be provided with a way to select, and use, the code via both an in-store setting (e.g., via a magnetic stripe reader) or an online setting (e.g., by reading the code from a display and entering the code into a text box on a checkout page of an online purchase transaction). A remote server, such as a payment authorization server, may receive the code and may process a payment differently based on the code received. For example, a code may be a security code to authorize a purchase transaction. A code may provide a payment feature such that a purchase may be made with points, debit, credit, installment payments, or deferred payments via a single payment account number (e.g., a credit card number) to identify a user and a payment feature code to select the type of payment a user desires to utilize.
A dynamic magnetic stripe communications device may include a magnetic emulator that comprises an inductor (e.g., a coil). Current may be provided through this coil to create an electromagnetic field operable to communicate with the read-head of a magnetic stripe reader. The drive circuit may fluctuate the amount of current travelling through the coil such that a track of magnetic stripe data may be communicated to a read-head of a magnetic stripe reader. A switch (e.g., a transistor) may be provided to enable or disable the flow of current according to, for example, a frequency/double-frequency (F2F) encoding algorithm. In doing so, bits of data may be communicated.
Electronics may be embedded between two layers of a polymer (e.g., a PVC or non-PVC polymer). One or more liquid polymers may be provided between these two layers. The liquid polymer(s) may, for example, be hardened via a reaction between the polymers (or other material), temperature, or via light (e.g., an ultraviolet or blue spectrum light) such that the electronics become embedded between the two layers of the polymer and a card is formed.
A payment card or other device may receive information indicative of a feature desired to be added by a user. The payment card may communicate information indicative of the feature with payment card data associated with the card or a user selection. The payment data and feature information may be routed, for example, to an authorization server. The authorization server may authorize payment and, based on the authorized payment, communicate the feature information to a remote server. The remote server may utilize this remote information to impact a third party service. The feature information may, for example, be routed before the payment card data reaches an authorization server. At merchant settlement, charge backs for a purchase associated with a game action may cause the feature to be reversed or a different feature to be implemented (e.g., a removal of rewards earned at authorization). The feature may be implemented at settlement upon confirmation that, for example, no chargeback was associated with the payment transaction.
A financial management system may be implemented to control the accounting of transactions processed by a remote facility. The financial management system may include a financial processor that may render an accounting programming language (APL) interface onto a graphical user interface. Appropriate selection of entries via the APL may cause executable code to be generated and then executed by the financial processor to effect the accounting of transactions processed by a financial processor. Alternatively, appropriate selection of entries via the APL may be accessed by executable applications already running on the financial processor to effect the accounting of transactions processed by a financial processor.
The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:
The selection of a feature may or may not have a cost associated with it. If a cost is associated with the feature, for example, the cost may be added to a customer's statement (e.g., added to a credit or debit purchase) for a particular transaction. A fixed-fee or variable-fee (e.g., a percentage of the transaction) may then be removed from the fee charged to the user and distributed among particular parties (e.g., distributed among the card issuer and/or device provider). The remainder of the fee may be provided, for example, to the third party service provider. A cost may be associated with a feature selection, but may not be a cost to a user. Instead, for example, the cost may be a cost to a third party service provider. The cost may be provided, for example, to other entities such as, for example, the device provider, card issuer, card processor (which may be the same, for example, as the card issuer), or any other entity (e.g., card network).
Architecture 150 may be utilized with any card. Architecture 150 may include processor 120. Processor 120 may have on-board memory for storing information (e.g., financial features). Any number of components may communicate to processor 120 and/or receive communications from processor 120. For example, one or more displays (e.g., display 140) may be coupled to processor 120. Persons skilled in the art will appreciate that components may be placed between particular components and processor 120. For example, a display driver circuit may be coupled between display 140 and processor 120. Memory 142 may be coupled to processor 120. Memory 142 may include data, for example, that is unique to a particular card. Memory 142 may include any type of data. For example, memory 142 may store discretionary data codes associated with buttons of a card (e.g., card 100 of
A card may include, for example, any number of light sensors. Light sensors may be utilized such that a display screen, or other light emitting device, may communicate information to light sensors 127 via light.
Any number of reader communication devices may be included in architecture 150. For example, IC chip 152 may be included to communicate information to an IC chip reader. IC chip 152 may be, for example, an EMV chip. As per another example, RFID 151 may be included to communicate information to an RFID reader. A magnetic stripe communications device may also be included to communicate information to a magnetic stripe reader. Such a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader. Different electromagnetic signals may be communicated to a magnetic stripe reader to provide different tracks of data. For example, electromagnetic field generators 170, 180, and 185 may be included to communicate separate tracks of information to a magnetic stripe reader. Such electromagnetic field generators may include a coil wrapped around one or more materials (e.g., a soft-magnetic material and a non-magnetic material). Each electromagnetic field generator may communicate information serially to a receiver of a magnetic stripe reader for particular magnetic stripe track. Read-head detectors 171 and 172 may be utilized to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). This sensed information may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader. Accordingly, a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time. Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 152, and electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers). Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180, and 185.
Architecture 150 may also include, for example, a light sensor. Architecture 150 may receive information from a light sensor. Processor 120 may determine information received by a light sensor.
A user may associate a card, such as a powered or non-powered card, with an application manager for managing third party service features. Such an application manager may be provided, for example, on a remote facility and displayed on a graphical user interface to allow a user to change the third party service features associated with a card. In this manner, a user may utilize a GUI to be provided with an ecosystem of applications and may, for example, select, at any time, a particular feature to associate with a card or a card button. Persons skilled in the art will appreciate that a default feature may be provided or that a number of features provided by a card issuer or entity may be provided in addition to third party service features. For example, a card issuer may provide a card with a default on one button for credit and a default for a second button as decoupled debit. A user may press the first button to perform a credit transaction. A user may press the other button to perform a decoupled debit transaction.
Virtual card 212 may be provided as a representation of a user's physical card associated with an application manager. A user may be provided with the ability to change between multiple physical cards and configure the features associated with those multiple physical cards. Accordingly, virtual card 212 may be provided with indicia 213 in the configuration of, and indicative of, one physical button associated with a user's physical card and virtual card 212 may be provided with indicia 214 in the configuration of, and indicative of, another physical button associated with a user's physical card. Fields 215 and 216 may include the features associated with each button. Accordingly, a user may, for example, view virtual card 212 in order to refresh the user's memory on the features associated with the physical buttons on a user's physical card (not shown). GUI 201 may be, for example, provided as an application for a device (e.g., a portable computing device or a mobile telephonic device) or retrieved information from a web browser. Text 211 may, for example, identify the user associated with virtual card 212 and the corresponding physical card (not shown).
A list of applications may be provided on a card. Such applications may provide features for a third party service provider. A user may, for example, select that different applications be associated with a particular card or a particular button on a card. For example, selection 231 may associate application 222 to the physical button of a card associated with virtual button 213. Selection 232 may associate application 224 to the physical button of a card associated with virtual button 214. In doing so, a user may change the features of a card by using GUI 201. A physical card (not shown) may communicate information indicative of the button that was pressed with other payment data (e.g., an account number, security code, and other data). For example, information indicative of the button that was pressed may be included in discretionary data of a payment message. A payment message may be, for example, one or more tracks of magnetic stripe data (e.g., communicated from a dynamic magnetic stripe communications device), an RFID message (e.g., an NFC message from a radio frequency antenna), or an exposed IC chip message (e.g., an EMV message) from an exposed IC chip. Such information may be passed to a card issuer or processor from a point-of-sale and any intermediary devices (e.g., a merchant acquirer processing server) and the information may be passed to a remote facility (e.g., a facility providing an application manager) such that the remote facility may determine the button that was pressed by a user. This remote facility may, in turn, retrieve information associated with the third party feature (or a feature of a card issuer, processor, application manager provider, or any entity) and forward information to that feature provider such that the feature may be performed. Additional information may be returned to the entity that provided the information indicative of the button the user pressed. Persons skilled in the art will appreciate that if, for example, a non-powered card is utilized then information indicative that a purchase was made may be provided to an application manager provider such that the application manager provider can initiate the desired feature for the non-powered card. For non-powered cards, for example, features may be associated with different types of purchases such as, for example, one feature may be provided for a particular merchant type (e.g., a game feature for gas purchases) and another feature may be provided for a different merchant type (e.g., a reward feature for transportation purchases). Features may be associated with other characteristics of a purchase such as, for example, a purchase above a particular amount (e.g., at or above $100) or a purchase below a particular amount (e.g., below $100). Such additional feature selections may be provided, for example, for powered cards and devices.
GUI 201 may be provided, for example, on a card issuer's website such as, for example, on a bill statement web page. GUI 201 may be provided, for example, above the bill statement or to the right of the bill statement. Accordingly, for example, a user may utilize the application manager to manage application features when the user is logged into his/her account. Similarly, a third party service provider may utilize GUI 201 as part of a user's administration or experience of that third party service. Accordingly, for example, a user's profile page for a third party service may include GUI 201. In this manner, application manager provider may provide web-code that retrieves GUI 201 from a remote facility managed by the application manager provider. Selection 241 may be utilized by a user to check for updates (e.g., confirm that a feature was changed or if any updates are present). Selection 242 may be utilized to explain the functionality of a particular application feature. Selection 243 may be utilized for additional selection options. Scroll tool 244 may be used, for example, to scroll through a list of applications and selection options.
A card may be provided with one button for a particular payment account (e.g., credit) and one button for a changeable feature. Accordingly, a user may, for example, only need to remember one feature associated with a card. A credit account may include rewards such as points, cashback, or miles from the card issuer. Accordingly, pushing the payment account button may earn the user such rewards. Pushing the changeable feature button may, alternatively, for example, not earn the user such rewards and may instead initiate a changeable feature. In doing so, for example, the cost of providing a card may be reduced in that the cost of rewards for the card may be reduced. A feature may include, for example, a feature from the card issuer, such as the ability for a user to earn a particular amount of points (e.g., 100) for a particular dollar amount added to a purchase (e.g., $1).
An application associated with a changeable feature button may, for example, initiate a financial transaction (e.g., a piggyback transaction) to occur in addition to a purchase transaction being initiated by a card or device. For example, a changeable feature button may be pressed and associated payment information may be communicated that may cause a third party to charge additional funds as a second transaction (e.g., a piggyback transaction) that may be associated with a first transaction. Accordingly, for example, a customer may receive goods and/or services from the third party once the piggyback transaction settles in addition to any goods and/or services that may have been purchased by the customer during the first transaction. A remote processing facility may, for example, provide a configurable financial management system to manage the financial transactions that may be associated with an original purchase or action (e.g., piggyback transactions, statement credit transactions, return transactions, partial return transactions, adjustments and chargebacks).
A user may, for example, initiate a purchase transaction within network 312, such that the user may have requested additional functionality associated with the transaction. A user may, for example, complete a purchase transaction establishing a communication (e.g., an electromagnetic communication) between the user's payment device and a merchant's point-of-sale terminal where a payment message (e.g., a magnetic stripe payment message) may be communicated to complete the purchase transaction and additional information (e.g., information associated with a particular button on the user's payment device) may be communicated (e.g., communicated within discretionary data fields within the magnetic stripe message) to a network entity.
The payment message may be received by a network entity (e.g., an issuer and/or a processor) within network 312 to complete the requested purchase transaction. The network entity may, for example, forward a data string (e.g., data string 302) to processing facility 304 based on the requested purchase transaction. Data string 302 may, for example, contain data associated with the purchase transaction (e.g., payment account number, payment account holder's name, track data, merchant type, merchant location, types of goods purchased, amount of purchase, and transaction type).
Processing facility 304 may receive data string 302 and may process data string 302 (e.g., parse data string 302) to obtain individual data components contained within data string 302. Accordingly, for example, processing facility 304 may separate information pertaining to purchase authorization (e.g., payment account number and cardholder name) from information pertaining to, for example, the shopping habits of the user (e.g., merchant info, date/time of purchase, purchase type and purchase amount). Data string 302 may, for example, contain magnetic stripe data 342 (e.g., Track 1 data and Track 2 data). Data string 302 may, for example, contain a subset of magnetic stripe data (e.g., discretionary data fields contained within Track 1 and/or Track 2 data).
Mapping 306 may, for example, exist locally within processing facility 304. Mapping 306 may, for example, be accessed remotely by processing facility 304. Enhanced digital and/or physical security measures may be taken to protect the contents of mapping 306 from unauthorized access.
A data lookup function may be performed by processing facility 304, such that account identifying information (e.g., account number 330) may be provided to mapping 306. Mapping 306 may receive the account identifying information and may return a corresponding customer identification. For example, mapping 306 may be a database containing payment account numbers associated with one or more users. Each payment account number contained within mapping 306 may, for example, correlate to an associated customer ID (e.g., a token uniquely associated with the user).
Processing facility 304 may scrub data string 302 to remove sensitive information from data string 302. For example, sensitive information (e.g., account number 330 and account holder name 332) of data string 302 may be stripped by processing facility 304 and replaced with customer information received from mapping 306. Accordingly, for example, sensitive purchase account information associated with each data string 302 may be destroyed once data string 302 is correlated to its associated customer ID. In so doing, for example, a scrubbed and sanitized version of data string 302 may be stored within storage 308.
Processing facility 304 may retrieve scrubbed and sanitized information from storage 308. Storage 308 may, for example, exist locally within processing facility 304. Storage 308 may, for example, be accessed remotely by processing facility 304.
Processing facility 304 may retrieve information from storage 308 and may, for example, generate third-party data string 310 for delivery to third-party applications. Third-party data string 310 may, for example, contain information that may be value added to third-party applications and may be devoid of sensitive information associated with users.
Third-party data string 310 may, for example, contain third-party ID 350, which may be generated by processing facility 304 in response to information (e.g., discretionary data fields of track data 342) and user preference data 314. For example, track data 342 when construed in association with user preference data 314 may indicate which third-party application is to receive third-party data string 310. Accordingly, for example, processing facility 304 may generate third-party ID 350 in accordance with track data 342 and user preference data 314. Track data 342 in association with user preference data 314 may, for example, define what types and quantities of information are to be provided within third-party data string 310. Accordingly, for example, one or more data fields (e.g., data fields 354-360) may be populated within third-party data string 310 in accordance with track data 342 and associated user preference data 314. Merchant info 360 may be provided in greater detail (e.g., may include both the name and address of the merchant) as compared to merchant info 334 which may contain only general data about the merchant (e.g., name only).
Third-party data string 310 may, for example, contain customer ID 352, which may be generated by processing facility 304 in response to information (e.g., a unique customer token) that may be contained within storage 308. Customer ID 352 may, for example, depend at least in part upon which third-party application is to receive third-party data string 310 (e.g., as may be defined by third-party ID 350). For example, a user may be associated with several third-party applications. Accordingly, for example, one user may be associated with multiple customer IDs. In so doing, for example, third-party data string 310 may contain customer ID 352 that is different for each third-party ID 350, but nevertheless identifies the same user.
One of many third-party processors (e.g. third-party processor 316) may receive third-party data string 310. Customer ID 352 may uniquely identify which user may be associated with third-party data string 310. Accordingly, for example, third-party processor 316 may initiate one or more transactions on behalf of the user depending upon which of the one or more transactions the user has selected (e.g., as determined by user preference data within third-party database 318) to be associated with the transaction that caused data string 302 to be received by processing facility 304.
For example, a user may define user preference data (e.g., as may be stored within third-party database 318) to direct third-party processor 316 to charge additional funds against the user's payment account after third-party data string 310 is received. Such additional funds may, for example, be used to purchase goods and/or services that may be offered by a third party (e.g., a collection of sports memorabilia cards from UpperDeck). Accordingly, for example, upon receipt of third-party data string 310, third-party processor 315 may request processing facility 304 to process a payment for goods and/or services provided by the third party in accordance with configurable information (e.g., user configurable information within database 318).
Processing facility 406 may, for example, receive messages from payment network 404 (e.g., from a processor within payment network 404) that may be related to at least a portion of transactions conducted within payment network 404. Customers associated with processing facility 406 may, for example, elect to distribute at least a portion of data processed within payment network 404 with the various third-party applications of third-party network 422.
User preferences 408 may be selected by each customer to, for example, define what data, if any, may be provided to processing facility 406 by payment network 404. A customer may select (e.g., via user preferences 408) at least a portion of the data provided by payment network 404 to processing facility 406 that may be shared with third-party applications 410-420.
Network 424 (e.g., the internet) may be accessed by a user to define user preferences 408, which may determine how payment network 404, processing facility 406, third-party network 422, and third-party applications 410-420 interact for every transaction conducted by each user. A user may, for example, present a non-powered card to merchant terminal 402 to complete a particular purchase transaction. User preferences 408 may, for example, be defined by the user to allow details of such a transaction to be communicated by payment network 404 to processing facility 406, which may then share at least a portion of such details with one or more third-party applications 410-420. A customer may, for example, present a powered card to merchant 402 to complete a purchase transaction. Prior to presentment, the customer may have selected (e.g., via one or more button presses on the powered card) one or more additional actions to be taken besides the processing of a purchase transaction by payment network 404 in accordance with user preferences 408.
A user may, for example, press a button on a powered card that may be associated with communicating a payment message (e.g., a magnetic stripe message) to merchant terminal 402. Such a button press may, for example, further populate the magnetic stripe message (e.g., populate a discretionary data field within the magnetic stripe message) with a directive to share at least a portion of purchase transaction details conducted at merchant terminal 402 with a particular third-party application (e.g., merchant 420). User preferences 408 may, for example, be selected by the user to determine which actions are to be conducted by the third-party application.
A user may press a button on a powered card that in accordance with user preferences 408 may, for example, cause a data string to be communicated from payment network 404 (e.g., from a processor within payment network 404) to processing facility 406 that may contain details of a purchase transaction initiated at merchant terminal 402. Processing facility 406 may, for example, compare user information (e.g., payment account number and/or payment account holder's name) that may be contained within the data string to a user database to obtain a customer ID (e.g., a customer token) that may be associated with the user information. Sensitive information within the data string (e.g., payment account number and/or payment account holder's name) may be replaced with the customer token and then stored either locally within processing facility 406 or remotely.
The data string, for example, may further contain information that may be indicative of which button was pressed on the powered card before being presented to merchant terminal 402. Using the button press information in addition to user preferences 408, processing facility 406 may populate a third-party message with details that may be communicated to a third-party application (e.g., merchant 420).
As per an example, a user may elect to share certain transaction information with merchant 420 each time a certain button is pressed on the user's powered card before presentment to merchant terminal 402 for payment. Such information may include, for example, merchant information (e.g., merchant's address), date/time information of the purchase, amount of the purchase, type of purchase made, and any other information (e.g., the customer ID associated with the customer's merchant account) that may be selected by the user via user preferences 408. Accordingly, for example, the selected information may be automatically gathered by processing facility 406, populated within a third-party message and communicated to merchant 420 via third-party network 422 (e.g., the internet).
Upon receipt of the third-party message, merchant 420 may initiate a second transaction (e.g., a piggyback transaction or statement credit transaction). The second transaction may be communicated to processing facility 406 via third-party network (e.g., the internet) and processed by processing facility 406 accordingly. Financial details associated with the second transaction may be processed by financial processor 428, which may be operating within processing facility 406 or may be remote to processing facility 406.
Accounting GUI 432 and financial processor 428 may, for example, combine to provide an accounting programming language (APL) interface that may be used to develop a financial management system. Such a financial management system may process financial transactions received by processing facility 406 (e.g., payment transactions communicated by payment network 404 and third-party network 422) and may provide the proper accounting mechanisms that affect the various accounts (e.g., revenue and expense accounts) and account types (e.g., debit and credit account types).
Receiver 504 may receive an advice message from payment processor 560 that may contain certain details about a purchase transaction (e.g., merchant type, merchant location, time of day, amount spent) and may further contain magnetic stripe information (e.g., Track 1 and Track 2 data). Alternatively, magnetic stripe information provided by the advice message may contain only a subset of Track 1 and Track 2 data (e.g., only the discretionary data fields of Track 1 and/or Track 2).
Replier 512 may provide status updates to payment processor 560 to, for example, relay to payment processor 560 that receiver 504 is operational during periods of non-activity (e.g., during a period where a lack of purchase transactions are being processed by a payment processor 560). Receiver 504 may, for example, receive the advice message via a network connection (e.g., a socket connection via SSL or TLS) from payment processor 560. Receiver 504 may, for example, comprise two or more receivers which may receive advice messages from two or more socket connections (e.g., via two or more payment processors 560).
Advice messages received by receiver 504 may be written to queue 506 (e.g., a transactional queue). Accordingly, receiver 504 may receive many advice messages and each advice message may be properly queued for processing within queue 506 without danger of being lost or destroyed. Alternatively, for example, queue 506 may be comprised of multiple queues (e.g., three non-transactional queues). The non-transactional queues may include a primary queue, a backup queue and a completed queue. Accordingly, advice messages may be written by receiver 504 to both the primary and backup queues for redundancy, while the completed queue may be reserved for tracking completion status of advice message processing. Once an advice message is processed (e.g., by parser 510), it may be written to the completed queue. Once written, both the completed advice message and its counterparts in both the primary and backup queues may be erased (e.g., by integrity checker 508) to free space in the queues for processing of subsequent advice messages.
A time-out period may exist within the primary and/or redundant queues, such that if a period of time expires (e.g., 1-2 minutes) before advice message processing completes, then integrity checker 508 may rewrite the uncompleted advice message from the backup queue back into the primary queue. In so doing, the possibility of ignoring an advice message may be minimized (e.g., decreased to zero).
Parser 510 may, for example, include one or more parsers that may pull advice messages from queue 506. Additional instances of parser 510 may, for example, be created so as to provide enough processing power to handle all advice messages received. Advice messages may be pulled from a single queue (e.g., the primary queue of queue 506), such that each parser 510 may request an advice message from queue 506 and queue 506 may provide the next available advice message to the requesting parser 510. Parsers 510 process each advice message by parsing individual data components from the advice message into an internal object that may be more easily manipulated. Parsers 510 may, for example, remove sensitive information from each advice message (e.g., payment account number and payment account holder's name) and may replace the sensitive advice message with unique user identifiers. Parsed and sanitized advice messages may be written to queue 514 (e.g., a 3-stage, non-transactional queue structure) which may be processed by event generator 516. Parsed and sanitized advice messages may be written from event generator 516 into queue 518 (e.g., a 3-stage, non-transactional queue structure) and processed by data processor 520 for long-term storage within data warehouse 522.
Once an advice message is fully parsed, the advice message may be written into the completed queue of queue 506 and a parsed advice message (or a variation of a parsed advice message) may be written to replier 512 as a reply message (e.g., an advice reply message). The advice reply message may then be communicated to payment processor 560 to confirm that advice message parsing is complete (e.g., enough of the original advice message may be repeated within the advice reply message to insure to payment processor 560 that the advice message has been properly processed).
Integrity checker 508 may detect that parsing and sanitizing of an advice message is completed by inspecting the contents of the completed queue of queue 506 against the contents of the primary queue of queue 506. When a match exists, integrity checker 508 may delete the advice message from both the primary queue and the completed queue of queue 506.
Parsed and sanitized advice messages (e.g., trevents generated by event generator 516) may be stored within database 528 via queue 524 (e.g., a 3-stage, non-transactional queue structure) by event writer 526. Each trevent stored within database 528 may, for example, be directed to a third-party application (e.g., a social network application, a coupon application, a gaming application, and/or a merchant). Third-party feeder 530 may search database 528 for trevents that have yet to be communicated to a third-party application. Once found, third-party trevents may be queued within queue 532 (e.g., a 3-stage, non-transactional queue structure) and distributed to third-party applications via third-party distributor 534. Trevents may be provided to third-party application(s) (e.g., third-party 552) via a number of communication mechanisms (e.g., via a socket port, a web service, or a web address) of network 554 (e.g., the internet).
The third-party application(s) may then acknowledge receipt of the trevents via API 536. API 536 may, for example, comprise web servers. Alternatively, API 536 may comprise a web address that may communicate data via “post” operations and “get” operations.
Third-party applications may, for example, report the completion of processing of a particular trevent via API 536. For example, a third-party trevent may comprise checking a user in at a particular coffee shop using a payment transaction conducted by the user at the coffer shop. Accordingly, for example, a third-party application may complete processing of a trevent once the transaction and appearance of the user at the coffee shop is reported to a social network of the user's choosing (e.g., Facebook or Twitter).
Third-party applications may, for example, request financial transactions (e.g., piggybacks, statement credits, returns, partial returns, adjustments, and chargebacks) via API 536. Financial transaction requests may be queued within queue 538 (e.g., a 3-stage, non-transactional queue structure) for processing by third-party processor 540 and queued within queue 542 (e.g., a 3-stage, non-transactional queue structure) for processing by third-party services 548 and/or merchant acquirer (MA) processor 544.
As per an example, a user may indicate (e.g., via a web-based application management tool) that purchases made with the user's card or device after a particular button was pressed on that card or device may cause a message to be routed to a third-party application (e.g., UpperDeck) for additional functionality. A user may, for example, indicate (e.g., via a web-based application management tool) that additional payment functionality may, for example, cause the third-party application to request that a separate transaction (e.g., a piggyback transaction) be conducted. Accordingly, for example, upon the initial payment transaction request by a user at a merchant's point-of-sale terminal, a message may be communicated to a third-party application and a piggyback transaction may be automatically requested by the third-party application based upon the user's preferences (e.g., as may be preselected via a web-based application management tool).
Such a piggyback transaction may include a second purchase transaction, where the third-party may sell goods to the user for value based upon the occurrence of the first purchase transaction. Accordingly, for example, the third party may request (e.g., via the piggyback transaction) that the user's card be charged an additional amount equal to the second purchase transaction amount.
Settlement files may, for example, be received regularly (e.g., nightly) by settlement receiver 530 from a network entity (e.g., payment processor 560). Such settlement files may, for example, result from financial transactions conducted during a time period (e.g., during a daytime period) and such financial transactions may include one or more of piggybacks, statement credits, returns, partial returns, adjustments, and chargebacks or any other transaction type. Such settlement files may, for example, be compared against authorization messages or their sanitized equivalent messages (e.g., trevent messages stored within database 528) to reconcile each authorization message received from a network entity (e.g., payment processor 560) with a corresponding settlement message.
If the purchase transaction was initiated with a card or device that was previously selected by the user to invoke additional payment functionality (e.g., via a web-based application management tool), then in step 616, a network entity (e.g., the payment processor that authorized the purchase transaction in step 613) may communicate an authorization advice message (e.g., communicated only if the purchase transaction was authorized) to a remote facility.
The authorization advice message may provide details of the purchase transaction, such as personal account number, cardholder name, merchant ID, purchase amount, Track 1 data, Track 2 data, and purchase date/time. The remote facility may sanitize the advice message (e.g., as in step 617) by replacing sensitive information (e.g., personal account number and cardholder name) with a unique cardholder identifier (e.g., a cardholder identifier that is also unique to a particular third party) to create a message (e.g., as in step 618 that contains a trevent ID that is uniquely associated to the purchase transaction authorized in step 613) that may be communicated to that third party (e.g., as in step 619).
In step 621 of sequence 620, a transaction request (e.g., a transaction request having the same trevent ID as the trevent received by the third party in step 619) may be provided by a third party and received by a remote facility (e.g., via an application programming interface provided to third-party applications by the remote facility). Persons skilled in the art will appreciate that third-party applications need not be executed remotely from the remote facility, but rather may be hosted within the remote facility itself. Persons skilled in the art will further appreciate that transactions of step 621 may include other transaction types, such as settlement transactions, piggyback transactions, statement credits, returns, partial returns, adjustments, chargebacks, or any other type of transaction.
The transaction request may be queued within the remote facility for processing (e.g., as in step 622). A third-party processor within the remote facility may receive the transaction request and may direct the request to an appropriate processor (e.g., to a merchant acquirer processor via a queue as in step 623) within the remote facility. The merchant acquirer processor may retrieve the transaction request from the queue, recognize that the transaction is a piggyback transaction, and may generate a piggyback message to be communicated to a merchant acquirer for processing (e.g., as in step 624). Accordingly, for example, the remote facility may act as if it is a merchant, since the piggyback message may be formed with payment information (e.g., a personal account number that may belong to the user who purchased goods in step 611) and may be processed by a network entity (e.g., a merchant acquirer assigned to the remote facility). In so doing, the merchant acquirer may process the transaction (e.g., as in step 625) for the remote facility by charging the user of step 611 for the piggyback charges initiated in step 621.
A temporary database within the remote facility may, for example, contain third-party transactions (e.g., all completed piggyback transactions requested by third parties) that may need additional processing. For example, each third-party requested piggyback transaction may incur fees that may need to be distributed to network entities (e.g., merchant acquirers and issuers). In addition, the remote facility may retain a certain portion of such fees earned through facilitation of the third-party transactions. Accordingly, for example, a financial management system may be provided to allow programming of such functionality via an accounting programming language (APL) interface.
For each trevent 710, one or more accounting procedures may be implemented by financial processor 704. Each accounting procedure may be defined (e.g., defined via a graphical user interface of APL interface 706). Accordingly, an accounting professional may interact with APL interface 706 to define each accounting procedure by programming values of accounting variables associated with each entity that may be involved with each trevent contained within database 708.
For example, third parties associated with each trevent may expect to receive compensation (e.g., a percentage of each piggyback transaction processed by the remote facility) and may expect to accrue expenses associated with such transactions (e.g., a percentage of the transaction amount paid to the remote facility). As per another example, issuers of cards or devices used by users to invoke additional payment functionality may expect to accrue expenses (e.g., a percentage of each transaction paid to the remote facility). Other network entities (e.g., a merchant acquirer associated with the remote facility) may expect to receive compensation (e.g., a flat rate and a percentage of each transaction) that may be paid to the merchant acquirer by the remote facility.
For each trevent received within database 708, financial processor 704 may retrieve the trevent for processing. In accordance with accounting rules specified (e.g., by an accounting professional via APL interface 706), financial processor 704 may perform processing steps on each trevent to generate proper entries to accounts (e.g., revenue and expense accounts) and may store those entries within accounting database 702. Each entry within database 702 may be settled after a period of time has transpired. For example, fees associated with each entry may be settled in multiple parts (e.g., two parts) where a percentage of a value of an account may be settled after a period of time (e.g., 45 days from initiation of the trevent) and the remainder of the value of the account may be settled after a period of time (e.g., 90 days from initiation of the trevent).
GUI 800 may display at least a portion of elements of accounting programming language (APL) interface 802. APL interface 802 may, therefore, facilitate account management programming by a lay person who may be unfamiliar with accounting programming languages (e.g., C, ABLE or COBOL) and/or accounting procedures. Accordingly, for example, a code generation application (not shown) may access variables defined by APL interface 802 and may build executable code (e.g., machine language executable by a financial processor) with each selection made by the user of APL interface 802. In so doing, the user may select the desired function and variable values via APL interface 802 and code representative of such selections may be automatically generated and/or utilized by a financial processor to implement the user's selections. Alternatively, executable code may already exist and variable values defined within APL interface 802 may provide input to the executable code to perform the accounting calculations and functions as defined by APL interface 802.
Slide bar 806 may be used to access event types 804. An input event (e.g., a mouse-over, mouse click, or a touch of a display that is displaying GUI 800) may select a particular event type within pull-down menu 804. Account type selections 808, 816, 824 and 832 may be programmed to identify the account types that may be associated with each respective entity (e.g., bank 810/834 and third-party 818/826). Textual input boxes 810-814 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 808. Textual input boxes 818-822 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 816. Textual input boxes 826-830 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 824. Textual input boxes 834-838 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 832.
A settlement transaction may be selected from within pull-down menu 804 and entities (e.g., issuer 810/834 and third party 818/826) may be programmed to be associated with such a selection. Accordingly, for example, settlement trevents accessed from a database of a remote facility may be processed in accordance with the parameters/values programmed by APL interface 802.
Based upon retrieving a settlement trevent from a database of the remote facility and based upon the programming parameters/values of APL interface 802, for example, a financial processor (not shown) may calculate at least a portion of the settlement transaction as debit 812 of amount 814 (e.g., an amount calculated as a percentage of a transaction amount) to the remote facility's accounts receivable 808 that may be associated with issuer 810 (e.g., the issuer of the card or device used to complete a purchase transaction). Similarly, for example, a financial processor (not shown) may calculate at least a portion of the settlement transaction as credit 836 of amount 838 (e.g., an amount calculated as a percentage of a transaction amount) to the remote facility's revenue account 832 that may be associated with issuer 834 (e.g., the issuer of the card or device used to complete a purchase transaction).
In addition, for example, a financial processor (not shown) may calculate at least a portion of the settlement transaction as credit 828 of amount 830 (e.g., an amount calculated as a percentage of a transaction amount) to the remote facility's accounts payable 824 that may be associated with third party 826 (e.g., UpperDeck). Similarly, for example, a financial processor (not shown) may calculate at least a portion of the settlement transaction as debit 820 of amount 822 (e.g., an amount calculated as a percentage of a transaction amount) to the remote facility's expense account 816 that may be associated with third party 818 (e.g., UpperDeck).
At settlement, for example, calculated revenue may be recorded as a payment to the remote facility from an issuer as a percentage of approximately 0.40% to 0.60% (e.g., approximately 0.50%) of the purchase transaction. For example, a $100 purchase transaction completed by a card or device issued by an issuer may result in a payment to the remote facility by the issuer (e.g., 0.50% of a $100 transaction equaling $0.50 is paid to the remote facility by the issuer) as may be recorded by the financial processor (not shown).
Similarly, calculated expenses may be recorded as a payment to a third party from the remote facility as a percentage of approximately 0.20% to 0.30% (e.g., approximately 0.25%) of the purchase transaction. For example, a $100 purchase transaction completed by a card or device may result in a payment to a third party by the remote facility (e.g., 0.25% of a $100 transaction equaling $0.25 is paid to third party 818 by the remote facility) as may be recorded by the financial processor (not shown).
A financial processor (not shown) may calculate and record an expense that may be paid by the remote facility to a third party in a single payment. Alternatively, a financial processor (not shown) may calculate and record an expense that may be paid by the remote facility to a third party in multiple payments (e.g., as a two-part payment). One payment may, for example, be paid by the remote facility as a percentage of an expense (e.g., 95% of the expense) to the third party within a time period (e.g., within 45 days from the purchase transaction). Another payment may, for example, be paid by the remote facility as a percentage of an expense (e.g., 5% of the expense) to the third party within another time period (e.g., within 90 days from the purchase transaction).
Persons skilled in the art will appreciate that certain fields within APL interface 802 may be programmable by a user and other fields (e.g., fields related to programmable fields) may not be programmable by the user, but rather may be status update fields that may be updated by a financial processor (not shown). Persons skilled in the art will appreciate that certain fields (e.g., textual input boxes) may instead by implemented as, for example, pull-down menus with scroll bars as may be necessary for a given application.
Slide bar 906 may be used to access event types 904. An input event (e.g., a mouse-over, mouse click, or a touch of a display that is displaying GUI 900) may select a particular event type within pull-down menu 904. Account type selections 908, 916, 924 and 932 may be programmed to identify the account types that may be associated with each respective entity (e.g., merchant acquirer 910 and third-party 918/926/934). Account status areas 940, 942 and 944 may or may not be programmed to identify expense accounts that may be associated with fees charged by other entities (e.g., a merchant acquirer, a payment network such as VISA or MasterCard, and an issuing bank). For example, account status areas 940-944 may represent fees incurred by a merchant acquirer and associated entities, where the amount of such expenses may or may not be programmable via APL interface 902.
Textual input boxes 910-914 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 908. Textual input boxes 918-922 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 916. Textual input boxes 926-930 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 924. Textual input boxes 934-938 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 932.
A piggyback transaction may be selected from within pull-down menu 904 and entities (e.g., merchant acquirer 910 and third-party 918/926/934) may be programmed to be associated with such a selection. Accordingly, for example, piggyback trevents accessed from a database of a remote facility may be processed in accordance with the parameters/values programmed by APL interface 902.
Based upon retrieving a piggyback trevent from a database of the remote facility and based upon the programming parameters/values of APL interface 902, for example, a financial processor (not shown) may calculate at least a portion of the piggyback transaction as debit 912 of amount 914 (e.g., a piggyback transaction amount minus fees associated with the piggyback transaction) to the remote facility's accounts receivable 908 that may be associated with merchant acquirer 910 (e.g., the merchant acquirer of the remote facility that is requesting a piggyback transaction). In so doing, for example, the remote facility may be acting as a merchant. Accordingly, for example, the remote facility may require a merchant acquirer to process the piggyback transaction, where expenses associated with the piggyback transaction may include: a percentage fee (e.g., 10% of the piggyback transaction amount) charged by the merchant acquirer as displayed in account status area 940; a flat fee (e.g., $0.10) charged by the network (e.g., VISA) as displayed in account status area 942; and a percentage fee (e.g., 3% of the piggyback transaction amount) charged by the issuing bank as displayed in account status area 944. Similarly, for example, a financial processor (not shown) may calculate at least a portion of the piggyback transaction as credit 936 of amount 938 (e.g., 100% of the piggyback transaction) to the remote facility's revenue account 932 that may be associated with third party 934 (e.g., UpperDeck).
In addition, for example, a financial processor (not shown) may calculate at least a portion of the piggyback transaction as credit 928 of amount 930 (e.g., a percentage of a piggyback transaction amount) to the remote facility's accounts payable 924 that may be associated with third party 926 (e.g., UpperDeck). Similarly, for example, a financial processor (not shown) may calculate at least a portion of the piggyback transaction as debit 920 of amount 922 (e.g., a percentage of a piggyback transaction amount) to the remote facility's expense account 916 that may be associated with third party 918 (e.g., UpperDeck).
A piggyback transaction may, for example, be an additional charge to a user's account that is requested by the user via the user's application manager (e.g., the user's web-based application manager) after the user initiates a purchase transaction with his or her card or device. An amount of the piggyback transaction may, for example, be transferred from the user's issuing bank to the remote facility's merchant acquirer. The merchant acquirer may deduct associated fees and may instruct the merchant acquirer's bank to pay the remote facility the remaining portion. For example, a $2 piggyback transaction may result in a payment to the remote facility by the merchant acquirer's bank in an amount equal to the piggyback transaction amount (e.g., $2.00) minus the amount of the merchant acquirer's fees (e.g., a 10% merchant acquirer fee of $0.20, a flat $0.10 issuer fee, and a 3% issuer fee of $0.06) for a total amount paid to the remote facility of $1.64 as may be indicated by amount 914.
Similarly, expenses may be recorded as a payment to third party 918 from the remote facility as a percentage of approximately 60% to 80% (e.g., approximately 70%) of the piggyback transaction amount. For example, a $2 piggyback transaction amount may result in a payment to third party 918 by the remote facility (e.g., 70% of a $2 transaction equaling $1.40 is paid to third party 918 by the remote facility) as may be recorded by the financial processor (not shown).
A financial processor (not shown) may calculate and record an expense that may be paid by the remote facility to a third party in a single payment. Alternatively, a financial processor (not shown) may calculate and record an expense that may be paid by the remote facility to a third party in multiple payments (e.g., as a two-part payment). One payment may, for example, be paid by the remote facility as a percentage of an expense (e.g., 95% of the expense) to the third party within a time period (e.g., within 45 days from the purchase transaction). Another payment may, for example, be paid by the remote facility as a percentage of an expense (e.g., 5% of the expense) to the third party within another time period (e.g., within 90 days from the purchase transaction).
Persons skilled in the art will appreciate that certain fields within APL interface 902 may be programmable by a user and other fields (e.g., fields related to programmable fields) may not be programmable by the user, but rather may be status update fields that may be updated by a financial processor (not shown). Persons skilled in the art will appreciate that certain fields (e.g., textual input boxes) may instead by implemented as, for example, pull-down menus with scroll bars as may be necessary for a given application.
A piggyback transaction may result in another transaction (e.g., a settlement transaction) and may be processed by a remote facility as a settlement transaction. Accordingly, for example, the remote facility may additionally earn a percentage of the piggyback transaction (e.g., 0.5% of the piggyback transaction amount) upon processing of the piggyback transaction as a subsequent settlement transaction.
Slide bar 1006 may be used to access event types 1004. An input event (e.g., a mouse-over, mouse click, or a touch of a display that is displaying GUI 1000) may select a particular event type within pull-down menu 1004. Account type selections 1008 and 1032 may be programmed to identify the account types that may be associated with each respective entity (e.g., third-party 1010/1034). Account status areas 1040, 1042 and 1044 may or may not be programmed to identify expense accounts that may be associated with fees charged by other entities (e.g., a merchant acquirer, a payment network such as VISA or MasterCard, and an issuing bank). For example, account status areas 1040-1044 may represent fees incurred by a remote facility's merchant acquirer and associated entities, where the amount of such expenses may or may not be programmable via APL interface 1002.
Textual input boxes 1010-1014 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 1008. Textual input boxes 1034-1038 may define programmable accounting parameters and/or programmable values that may be associated with the account type programmed in textual input box 1032.
A statement credit transaction may be selected from within pull-down menu 1004 and entities (e.g., third-party 1010/1034) may be programmed to be associated with such a selection. Accordingly, for example, statement credit trevents accessed from a database of a remote facility may be processed in accordance with the parameters/values programmed by APL interface 1002.
Based upon retrieving a statement credit trevent from a database of the remote facility and based upon the programming parameters/values of APL interface 1002, for example, a financial processor (not shown) may calculate at least a portion of the statement credit transaction as debit 1012 of amount 1014 (e.g., a percentage of a statement credit transaction amount minus fees associated with the statement credit transaction) to the remote facility's accounts receivable 1008 that may be associated with third party 1010 (e.g., the third party providing the statement credit). The expenses associated with the statement credit transaction may include: a percentage fee (e.g., 10% of the statement credit transaction amount) charged by the remote facility's merchant acquirer as reflected in status area 1040; a flat fee (e.g., $0.10) charged by the network (e.g., VISA) (e.g., as reflected in status area 1042); and a percentage fee (e.g., 3% of the statement credit transaction amount) charged by the issuing bank (e.g., as reflected in status 1044). Similarly, for example, a financial processor (not shown) may calculate at least a portion of the statement credit transaction as credit 1036 of amount 1038 (e.g., 30% of the statement credit transaction) to the remote facility's revenue account 1032 that may be associated with third party 1034 (e.g., the third party providing the statement credit).
A statement credit transaction may, for example, be a credit, requested by the user, that is applied to a user's account via appropriate selections within the user's application manager after the user initiates a purchase transaction with the selected third party. A purchase transaction with a third party providing the statement credit may qualify for the statement credit if the transaction amount is an amount that qualifies for the statement credit. For example, a third party (e.g., Giant Eagle) may provide a statement credit (e.g., a statement credit for $50 worth of gas) if the user first spends a minimum amount (e.g., $100) at Giant Eagle.
Once the initial purchase amount (e.g., $100 purchase at Giant Eagle) and the subsequent purchase of the credit amount (e.g., $50 worth of gas at GetGo) have been settled, an amount (e.g., a percentage of the statement credit transaction) may, for example, be transferred from the third party that is providing the statement credit (e.g., Giant Eagle) to the remote facility's merchant acquirer. The merchant acquirer may deduct associated fees and may instruct the merchant acquirer's bank to pay the remote facility the remaining portion. For example, a $50 statement credit transaction may result in a payment to the remote facility by the merchant acquirer's bank in an amount equal to a percentage approximately between 20% and 40% (e.g., approximately equal to 30%) of the statement credit transaction amount minus the amount of the merchant acquirer's fees (e.g., a 10% merchant acquirer fee of $5, a flat $0.10 issuer fee, and a 3% issuer fee of $1.50) for a total amount paid to the remote facility of $8.40 as may be indicated by amount 1014.
Persons skilled in the art will appreciate that certain fields within APL interface 1002 may be programmable by a user and other fields (e.g., fields related to programmable fields) may not be programmable by the user, but rather may be status update fields that may be updated by a financial processor (not shown). Persons skilled in the art will appreciate that certain fields (e.g., textual input boxes) may instead by implemented as, for example, pull-down menus with scroll bars as may be necessary for a given application.
Other accounting transactions may be accounted for by a financial management system. For example, an annual fee bounty transaction may be processed to generate annual fee revenue to a remote facility as may be paid by the issuing bank. As per another example, an acquisition bounty transaction may be processed to generate revenue to a remote facility if a user makes at least one purchase within a time period (e.g., a remote facility may earn a $75 acquisition fee if a user makes a purchase with a card or device within 120 days of activation). An acquisition bounty transaction may generate reduced revenue if a user makes at least one purchase within another time period (e.g., a remote facility may earn a $50 acquisition fee if a user makes a purchase with a card or device between 120-240 days of activation).
Receiver 1104 may receive an advice message from payment processor 1160 that may contain certain details about a purchase transaction (e.g., merchant type, merchant location, time of day, amount spent) and may further contain magnetic stripe information (e.g., Track 1 and Track 2 data). Alternatively, magnetic stripe information provided by the advice message may contain only a subset of Track 1 and Track 2 data (e.g., only the discretionary data fields of Track 1 and/or Track 2).
Replier 1112 may provide status updates to payment processor 1160 to, for example, relay to payment processor 1160 that receiver 1104 is operational during periods of non-activity (e.g., during a period where a lack of purchase transactions are being processed by payment processor 1160). Receiver 1104 may, for example, receive the advice message via a network connection (e.g., a socket connection via SSL or TLS) from payment processor 1160. Receiver 1104 may, for example, comprise two or more receivers which may receive advice messages from two or more socket connections (e.g., via two or more payment processors 1160).
Advice messages received by receiver 1104 may be written to queue 1106 (e.g., a transactional queue). Accordingly, receiver 1104 may receive many advice messages and each advice message may be properly queued for processing within queue 1106 without danger of being lost or destroyed. Alternatively, for example, queue 1106 may be comprised of multiple queues (e.g., three non-transactional queues). The non-transactional queues may, for example, include a primary queue, a backup queue and a completed queue. Accordingly, advice messages may be written by receiver 1104 to both the primary and backup queues for redundancy, while the completed queue may be reserved for tracking completion status of advice message processing. Once an advice message is processed (e.g., by parser 1110), it may be written to the completed queue. Once written, both the completed advice message and its counterparts in both the primary and backup queues may be erased (e.g., by integrity checker 1108) to free space in the queues for processing of subsequent advice messages.
A time-out period may exist within the primary and/or redundant queues, such that if a period of time expires (e.g., 1-2 minutes) before advice message processing completes, then integrity checker 1108 may rewrite the uncompleted advice message from the backup queue back into the primary queue. In so doing, the possibility of ignoring an advice message may be minimized (e.g., decreased to zero).
Parser 1110 may, for example, include one or more parsers that may pull advice messages from queue 1106. Additional instances of parser 1110 may, for example, be created so as to provide enough processing power to handle all advice messages received. Advice messages may be pulled from a single queue (e.g., the primary queue of queue 1106), such that each parser 1110 may request an advice message from queue 1106 and queue 1106 may provide the next available advice message to the requesting parser 1110. Parsers 1110 may process each advice message by parsing individual data components from the advice message into internal objects that may be more easily manipulated. Parsers 1110 may, for example, remove sensitive information from each advice message (e.g., payment account number and payment account holder's name) and may replace the sensitive information with unique user identifiers. Parsed and sanitized advice messages may be written to queue 1114 (e.g., a 3-stage, non-transactional queue with integrity checker 1162) which may be processed by event generator 1116. Parsed and sanitized advice messages may be written from event generator 1116 into queue 1118 (e.g., a 3-stage, non-transactional queue with integrity checker 1164) and processed by data processor 1120 for long-term storage within data warehouse 1122.
Once an advice message is fully parsed, the advice message may be written into the completed queue of queue 1106 and a parsed advice message (or a variation of a parsed advice message) may be written to replier 1112 as a reply message (e.g., an advice reply message). The advice reply message may then be communicated to payment processor 1160 to confirm that advice message parsing is complete (e.g., enough of the original advice message may be repeated within the advice reply message to insure to payment processor 1160 that the advice message has been properly processed).
Alternately, for example, receiver 1104 may itself parse individual data components from the advice message prior to writing the parsed message to primary and backup queues 1106. Additionally, for example, receiver 1104 may provide the parsed message to replier 1112. In so doing, parser 1110 may not be required to communicate with replier 1112 at all. Instead, the parsed message may be communicated to replier 1112 by receiver 1104 and replier 1112 may communicate the advice reply message to payment processor 1160 based on the parsed message received from receiver 1104.
Integrity checker 1108 may detect that parsing and sanitizing of an advice message is completed by inspecting the contents of the completed queue of queue 1106 against the contents of the primary queue of queue 1106. When a match exists, integrity checker 1108 may delete the advice message from both the primary queue and the completed queue of queue 1106.
Parsed and sanitized advice messages (e.g., trevents generated by event generator 1116) may be stored within database 1128 via queue 1124 (e.g., a 3-stage, non-transactional queue with integrity checker 1174) by event writer 1126. Each trevent stored within database 1128 may, for example, be directed to a third-party application (e.g., a social network application, a coupon application, a gaming application, and/or a merchant). Third-party feeder 1130 may search database 1128 for trevents that have yet to be communicated to a third-party application. Once found, third-party trevents may be queued within queue 1132 (e.g., a 3-stage, non-transactional queue with integrity checker 1168) and distributed to third-party applications via third-party distributor 1134. Event writer 1126 may, for example, write trevents directly into queue 1132 instead of, or in addition to, writing trevents into database 1128. Accordingly, for example, an optimized trevent flow may result, where third-party feeder 1130 may provide a fail-safe mechanism. Trevents may be provided to third-party application(s) (e.g., third-party 1152) via a number of communication mechanisms (e.g., via a socket port, a web service, or a web address) of network 1154 (e.g., the Internet).
The third-party application(s) may then acknowledge receipt of the trevents via API 1136. API 1136 may, for example, comprise web servers. Alternatively, API 1136 may comprise a web address that may communicate data via “post” operations and “get” operations.
Third-party applications may, for example, report the completion of processing of a particular trevent via API 1136. For example, a third-party trevent may comprise checking a user in at a particular coffee shop using a payment transaction conducted by the user at the coffee shop. Accordingly, for example, a third-party application may complete processing of a trevent once the transaction and appearance of the user at the coffee shop is reported to a social network of the user's choosing (e.g., Facebook or Twitter).
Third-party applications may, for example, request financial transactions (e.g., piggybacks, statement credits, adjustments, and chargebacks) via API 1136. Financial transaction requests may be queued within queue 1138 (e.g., a 3-stage, non-transactional queue with integrity checker 1170) for processing by third-party processor 1140 and queued within queue 1142 (e.g., a 3-stage, non-transactional queue with integrity checker 1172) for processing by third-party services 1148 and/or merchant acquirer (MA) processor 1144.
As per an example, a user may indicate (e.g., via a web-based application management tool) that purchases made with the user's card or device after a particular button was pressed on that card or device may cause a message to be routed to a third-party application (e.g., UpperDeck) for additional functionality. A user may, for example, indicate (e.g., via a web-based application management tool) that additional payment functionality may, for example, cause the third-party application to request that a separate transaction (e.g., a piggyback transaction) be conducted. Accordingly, for example, upon the initial payment transaction request by a user at a merchant's point-of-sale terminal, a message may be communicated to a third-party application and a piggyback transaction may be automatically requested by the third-party application based upon the user's preferences (e.g., as may be preselected via a web-based application management tool).
Such a piggyback transaction may include a second purchase transaction, where the third-party may sell goods to the user for value based upon the occurrence of the first purchase transaction. Accordingly, for example, the third party may request (e.g., via the piggyback transaction) that the user's card be charged an additional amount equal to the second purchase transaction amount.
Settlement files may, for example, be received regularly (e.g., nightly) by settlement receiver 1130 from a network entity (e.g., payment processor 1160). Such settlement files may, for example, result from financial transactions conducted during a time period (e.g., during a daytime period) and such financial transactions may include one or more of piggybacks, statement credits, returns, partial returns, adjustments, and chargebacks or any other transaction type. Such settlement files may, for example, be compared against authorization messages or their sanitized equivalent messages (e.g., trevent messages stored within database 1128) to reconcile each authorization message received from a network entity (e.g., payment processor 1160) with a corresponding settlement message.
Persons skilled in the art will also appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways then those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.
This application claims the benefit of U.S. Provisional Patent Application No. 61/624,377, titled “CARDS, DEVICES, SYSTEMS, AND METHODS FOR FINANCIAL MANAGEMENT SERVICES,” filed Apr. 15, 2012, which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4353064 | Stamm | Oct 1982 | A |
| 4394654 | Hofmann-Cerfontaine | Jul 1983 | A |
| 4614861 | Pavlov et al. | Sep 1986 | A |
| 4667087 | Quintana | May 1987 | A |
| 4701601 | Francini et al. | Oct 1987 | A |
| 4720860 | Weiss | Jan 1988 | A |
| 4786791 | Hodama | Nov 1988 | A |
| 4791283 | Burkhardt | Dec 1988 | A |
| 4797542 | Hara | Jan 1989 | A |
| 5038251 | Sugiyama et al. | Aug 1991 | A |
| 5168520 | Weiss | Dec 1992 | A |
| 5237614 | Weiss | Aug 1993 | A |
| 5276311 | Hennige | Jan 1994 | A |
| 5347580 | Molva et al. | Sep 1994 | A |
| 5361062 | Weiss et al. | Nov 1994 | A |
| 5412199 | Finkelstein et al. | May 1995 | A |
| 5434398 | Goldberg | Jul 1995 | A |
| 5434405 | Finkelstein et al. | Jul 1995 | A |
| 5465206 | Hilt | Nov 1995 | A |
| 5478994 | Rahman | Dec 1995 | A |
| 5479512 | Weiss | Dec 1995 | A |
| 5484997 | Haynes | Jan 1996 | A |
| 5485519 | Weiss | Jan 1996 | A |
| 5585787 | Wallerstein | Dec 1996 | A |
| 5591949 | Bernstein | Jan 1997 | A |
| 5608203 | Finkelstein et al. | Mar 1997 | A |
| 5623552 | Lane | Apr 1997 | A |
| 5638374 | Heath | Jun 1997 | A |
| 5655102 | Galles | Aug 1997 | A |
| 5657388 | Weiss | Aug 1997 | A |
| 5834747 | Cooper | Nov 1998 | A |
| 5834756 | Gutman et al. | Nov 1998 | A |
| 5856661 | Finkelstein et al. | Jan 1999 | A |
| 5864623 | Messina et al. | Jan 1999 | A |
| 5907142 | Kelsey | May 1999 | A |
| 5913203 | Wong et al. | Jun 1999 | A |
| 5937394 | Wong et al. | Aug 1999 | A |
| 5955021 | Tiffany, III | Sep 1999 | A |
| 5956699 | Wong et al. | Sep 1999 | A |
| 6025054 | Tiffany, III | Feb 2000 | A |
| 6045043 | Bashan et al. | Apr 2000 | A |
| 6076163 | Hoffstein et al. | Jun 2000 | A |
| 6085320 | Kaliski | Jul 2000 | A |
| 6095416 | Grant et al. | Aug 2000 | A |
| 6130621 | Weiss | Oct 2000 | A |
| 6145079 | Mitty et al. | Nov 2000 | A |
| 6157920 | Jakobsson et al. | Dec 2000 | A |
| 6161181 | Haynes, III et al. | Dec 2000 | A |
| 6176430 | Finkelstein et al. | Jan 2001 | B1 |
| 6182894 | Hackett et al. | Feb 2001 | B1 |
| 6189098 | Kaliski | Feb 2001 | B1 |
| 6199052 | Mitty et al. | Mar 2001 | B1 |
| 6202055 | Houvener | Mar 2001 | B1 |
| 6206293 | Gutman et al. | Mar 2001 | B1 |
| 6240184 | Huynh et al. | May 2001 | B1 |
| 6241153 | Tiffany, III | Jun 2001 | B1 |
| 6256873 | Tiffany, III | Jul 2001 | B1 |
| 6269163 | Rivest et al. | Jul 2001 | B1 |
| 6286022 | Kaliski et al. | Sep 2001 | B1 |
| 6308890 | Cooper | Oct 2001 | B1 |
| 6313724 | Osterweil | Nov 2001 | B1 |
| 6389442 | Yin et al. | May 2002 | B1 |
| 6393447 | Jakobsson et al. | May 2002 | B1 |
| 6397194 | Houvener | May 2002 | B1 |
| 6411715 | Liskov et al. | Jun 2002 | B1 |
| 6422462 | Cohen | Jul 2002 | B1 |
| 6446052 | Juels | Sep 2002 | B1 |
| 6460141 | Olden | Oct 2002 | B1 |
| 6549912 | Chen | Apr 2003 | B1 |
| 6592044 | Wong et al. | Jul 2003 | B1 |
| 6607127 | Wong | Aug 2003 | B2 |
| 6609654 | Anderson et al. | Aug 2003 | B1 |
| 6625598 | Kraffert | Sep 2003 | B1 |
| 6631849 | Blossom | Oct 2003 | B2 |
| 6655585 | Shinn | Dec 2003 | B2 |
| 6681988 | Stack et al. | Jan 2004 | B2 |
| 6704714 | O'Leary | Mar 2004 | B1 |
| 6705520 | Pitroda et al. | Mar 2004 | B1 |
| 6721763 | Pekowski | Apr 2004 | B1 |
| 6755341 | Wong et al. | Jun 2004 | B1 |
| 6764005 | Cooper | Jul 2004 | B2 |
| 6769618 | Finkelstein | Aug 2004 | B1 |
| 6805288 | Routhenstein et al. | Oct 2004 | B2 |
| 6811082 | Wong | Nov 2004 | B2 |
| 6813354 | Jakobsson et al. | Nov 2004 | B1 |
| 6817532 | Finkelstein | Nov 2004 | B2 |
| 6873974 | Schutzer | Mar 2005 | B1 |
| 6902116 | Finkelstein | Jun 2005 | B2 |
| 6968319 | Remington | Nov 2005 | B1 |
| 6970070 | Juels et al. | Nov 2005 | B2 |
| 6980969 | Tuchler et al. | Dec 2005 | B1 |
| 6985583 | Brainard et al. | Jan 2006 | B1 |
| 6991155 | Burchette, Jr. | Jan 2006 | B2 |
| 7013030 | Wong et al. | Mar 2006 | B2 |
| 7035443 | Wong | Apr 2006 | B2 |
| 7039223 | Wong | May 2006 | B2 |
| 7044394 | Brown | May 2006 | B2 |
| 7050997 | Wood, Jr. | May 2006 | B1 |
| 7051929 | Li | May 2006 | B2 |
| 7083094 | Cooper | Aug 2006 | B2 |
| 7100049 | Gasparini et al. | Aug 2006 | B2 |
| 7100821 | Rasti | Sep 2006 | B2 |
| 7111172 | Duane et al. | Sep 2006 | B1 |
| 7114652 | Moullette et al. | Oct 2006 | B2 |
| 7136514 | Wong | Nov 2006 | B1 |
| 7140550 | Ramachandran | Nov 2006 | B2 |
| 7163153 | Blossom | Jan 2007 | B2 |
| 7195154 | Routhenstein | Mar 2007 | B2 |
| 7197639 | Juels et al. | Mar 2007 | B1 |
| 7219368 | Juels et al. | May 2007 | B2 |
| 7225537 | Reed | Jun 2007 | B2 |
| 7225994 | Finkelstein | Jun 2007 | B2 |
| 7246752 | Brown | Jul 2007 | B2 |
| 7298243 | Juels et al. | Nov 2007 | B2 |
| 7334732 | Cooper | Feb 2008 | B2 |
| 7337326 | Palmer et al. | Feb 2008 | B2 |
| 7346775 | Gasparini et al. | Mar 2008 | B2 |
| 7356696 | Jakobsson et al. | Apr 2008 | B1 |
| 7357319 | Lin et al. | Apr 2008 | B1 |
| 7359507 | Kaliski | Apr 2008 | B2 |
| 7360688 | Harris | Apr 2008 | B1 |
| 7363494 | Brainard et al. | Apr 2008 | B2 |
| 7380710 | Brown | Jun 2008 | B2 |
| 7398253 | Pinnell | Jul 2008 | B1 |
| 7404087 | Teunen | Jul 2008 | B2 |
| 7424570 | D'Albore et al. | Sep 2008 | B2 |
| 7427033 | Roskind | Sep 2008 | B1 |
| 7430537 | Templeton | Sep 2008 | B2 |
| 7454349 | Teunen et al. | Nov 2008 | B2 |
| 7461250 | Duane et al. | Dec 2008 | B1 |
| 7461399 | Juels et al. | Dec 2008 | B2 |
| 7472093 | Juels | Dec 2008 | B2 |
| 7472829 | Brown | Jan 2009 | B2 |
| 7478062 | Ansley | Jan 2009 | B2 |
| 7494055 | Fernandes et al. | Feb 2009 | B2 |
| 7502467 | Brainard et al. | Mar 2009 | B2 |
| 7502933 | Jakobsson et al. | Mar 2009 | B2 |
| 7503485 | Routhenstein | Mar 2009 | B1 |
| 7505937 | Dilip | Mar 2009 | B2 |
| 7505938 | Lang | Mar 2009 | B2 |
| 7516492 | Nisbet et al. | Apr 2009 | B1 |
| 7523301 | Nisbet et al. | Apr 2009 | B2 |
| 7526576 | Bank | Apr 2009 | B2 |
| 7530495 | Cooper | May 2009 | B2 |
| 7532104 | Juels | May 2009 | B2 |
| 7543739 | Brown et al. | Jun 2009 | B2 |
| 7546274 | Ingram | Jun 2009 | B2 |
| 7559464 | Routhenstein | Jul 2009 | B2 |
| 7562221 | Nystrom et al. | Jul 2009 | B2 |
| 7562222 | Gasparini et al. | Jul 2009 | B2 |
| 7575154 | Rothschild | Aug 2009 | B2 |
| 7577687 | Bank | Aug 2009 | B2 |
| 7580898 | Brown et al. | Aug 2009 | B2 |
| 7580970 | Bank | Aug 2009 | B2 |
| 7584153 | Brown et al. | Sep 2009 | B2 |
| 7591426 | Osterweil et al. | Sep 2009 | B2 |
| 7591427 | Osterweil | Sep 2009 | B2 |
| 7602904 | Juels et al. | Oct 2009 | B2 |
| 7611049 | Drummond | Nov 2009 | B2 |
| 7631804 | Brown | Dec 2009 | B2 |
| 7639537 | Sepe et al. | Dec 2009 | B2 |
| 7641124 | Brown et al. | Jan 2010 | B2 |
| 7660902 | Graham et al. | Feb 2010 | B2 |
| 7707177 | Bank | Apr 2010 | B2 |
| 7708190 | Brandt | May 2010 | B2 |
| 7742984 | Mohsenzadeh | Jun 2010 | B2 |
| 7784687 | Mullen et al. | Aug 2010 | B2 |
| 7793851 | Mullen | Sep 2010 | B2 |
| 7797207 | Dilip | Sep 2010 | B1 |
| 7805376 | Smith | Sep 2010 | B2 |
| 7819321 | Faith | Oct 2010 | B2 |
| 7828207 | Cooper | Nov 2010 | B2 |
| 7828220 | Mullen | Nov 2010 | B2 |
| 7831636 | Wietlisbach | Nov 2010 | B2 |
| 7890423 | Czyzewski | Feb 2011 | B2 |
| 7896242 | Rothschild | Mar 2011 | B2 |
| 7931195 | Mullen | Apr 2011 | B2 |
| 7954705 | Mullen | Jun 2011 | B2 |
| 7967214 | Landau | Jun 2011 | B2 |
| D643063 | Mullen et al. | Aug 2011 | S |
| 8011577 | Mullen et al. | Sep 2011 | B2 |
| 8020775 | Mullen et al. | Sep 2011 | B2 |
| 8046256 | Chien | Oct 2011 | B2 |
| 8066191 | Cloutier et al. | Nov 2011 | B1 |
| D651237 | Mullen et al. | Dec 2011 | S |
| D651238 | Mullen et al. | Dec 2011 | S |
| 8074877 | Mullen et al. | Dec 2011 | B2 |
| 8083141 | Courtright | Dec 2011 | B1 |
| D651644 | Mullen et al. | Jan 2012 | S |
| D652075 | Mullen et al. | Jan 2012 | S |
| D652076 | Mullen et al. | Jan 2012 | S |
| D652448 | Mullen et al. | Jan 2012 | S |
| D652449 | Mullen et al. | Jan 2012 | S |
| D652450 | Mullen et al. | Jan 2012 | S |
| D652867 | Mullen et al. | Jan 2012 | S |
| D653288 | Mullen et al. | Jan 2012 | S |
| 8095440 | Barry | Jan 2012 | B2 |
| 8116453 | Shnowske | Feb 2012 | B2 |
| 8172148 | Cloutier et al. | May 2012 | B1 |
| 8185404 | McDaniel | May 2012 | B1 |
| D665022 | Mullen et al. | Aug 2012 | S |
| D665447 | Mullen et al. | Aug 2012 | S |
| D666241 | Mullen et al. | Aug 2012 | S |
| 8275312 | Fisher | Sep 2012 | B2 |
| 8282007 | Cloutier et al. | Oct 2012 | B1 |
| 8286876 | Mullen et al. | Oct 2012 | B2 |
| D670329 | Mullen et al. | Nov 2012 | S |
| D670330 | Mullen et al. | Nov 2012 | S |
| D670331 | Mullen et al. | Nov 2012 | S |
| D670332 | Mullen et al. | Nov 2012 | S |
| D670759 | Mullen et al. | Nov 2012 | S |
| 8302872 | Mullen | Nov 2012 | B2 |
| 8317752 | Cozmi | Nov 2012 | B2 |
| D672389 | Mullen et al. | Dec 2012 | S |
| 8322623 | Mullen et al. | Dec 2012 | B1 |
| D674013 | Mullen et al. | Jan 2013 | S |
| 8346659 | Mohsenzadeh | Jan 2013 | B1 |
| 8348172 | Cloutier et al. | Jan 2013 | B1 |
| 8365148 | Millmore | Jan 2013 | B2 |
| D676904 | Mullen et al. | Feb 2013 | S |
| 8382000 | Mullen et al. | Feb 2013 | B2 |
| 8393545 | Mullen et al. | Mar 2013 | B1 |
| 8393546 | Yen et al. | Mar 2013 | B1 |
| 8413892 | Mullen et al. | Apr 2013 | B2 |
| 8424773 | Mullen et al. | Apr 2013 | B2 |
| 8433657 | Dinan | Apr 2013 | B2 |
| 8459548 | Mullen et al. | Jun 2013 | B2 |
| D687094 | Mullen et al. | Jul 2013 | S |
| 8479220 | Wilkins | Jul 2013 | B2 |
| 8485437 | Mullen et al. | Jul 2013 | B2 |
| 8485446 | Mullen et al. | Jul 2013 | B1 |
| 8511574 | Yen et al. | Aug 2013 | B1 |
| 8517276 | Mullen et al. | Aug 2013 | B2 |
| 8523059 | Mullen et al. | Sep 2013 | B1 |
| 8561894 | Mullen et al. | Oct 2013 | B1 |
| 8567679 | Mullen et al. | Oct 2013 | B1 |
| 8573503 | Cloutier et al. | Nov 2013 | B1 |
| 8577804 | Bacastow | Nov 2013 | B1 |
| 8579203 | Lambeth et al. | Nov 2013 | B1 |
| 8590796 | Cloutier et al. | Nov 2013 | B1 |
| 8595064 | Hagy | Nov 2013 | B1 |
| 8602312 | Cloutier et al. | Dec 2013 | B2 |
| 8606712 | Choudhuri | Dec 2013 | B2 |
| 8608083 | Mullen et al. | Dec 2013 | B2 |
| 8622289 | Outwater | Jan 2014 | B2 |
| 8622309 | Mullen et al. | Jan 2014 | B1 |
| 8626705 | Barrett | Jan 2014 | B2 |
| 8628022 | Rhoades et al. | Jan 2014 | B1 |
| 8660926 | Wehunt | Feb 2014 | B1 |
| 8668143 | Mullen et al. | Mar 2014 | B2 |
| 8676659 | Shnowske | Mar 2014 | B1 |
| 8676708 | Honey | Mar 2014 | B1 |
| 8700527 | Dolphin | Apr 2014 | B2 |
| 8706699 | Chase | Apr 2014 | B2 |
| 8727219 | Mullen | May 2014 | B1 |
| 8733638 | Mullen et al. | May 2014 | B2 |
| 8738451 | Ahlers | May 2014 | B2 |
| 8746579 | Cloutier et al. | Jun 2014 | B1 |
| 8756162 | Brunet | Jun 2014 | B2 |
| 8757483 | Mullen et al. | Jun 2014 | B1 |
| 8757499 | Cloutier et al. | Jun 2014 | B2 |
| 8788382 | Monk | Jul 2014 | B2 |
| 8814050 | Mullen et al. | Aug 2014 | B1 |
| 8827153 | Rhoades et al. | Sep 2014 | B1 |
| 8875999 | Mullen et al. | Nov 2014 | B2 |
| 8881989 | Mullen et al. | Nov 2014 | B2 |
| 8888009 | Mullen | Nov 2014 | B1 |
| 8903093 | Kim | Dec 2014 | B2 |
| 8903740 | Vonog | Dec 2014 | B2 |
| 8930265 | Blackhurst | Jan 2015 | B2 |
| 8931703 | Mullen et al. | Jan 2015 | B1 |
| 8935186 | Dinan | Jan 2015 | B2 |
| 8939357 | Perry | Jan 2015 | B1 |
| 8943557 | Kelley | Jan 2015 | B2 |
| 8944333 | Mullen et al. | Feb 2015 | B1 |
| 8960545 | Batra | Feb 2015 | B1 |
| 8972224 | Dempster | Mar 2015 | B2 |
| 8973824 | Mullen et al. | Mar 2015 | B2 |
| 9004368 | Mullen et al. | Apr 2015 | B2 |
| 9010630 | Mullen et al. | Apr 2015 | B2 |
| 9053398 | Cloutier | Jun 2015 | B1 |
| 9064194 | Bohac, Jr. | Jun 2015 | B1 |
| 9064255 | Mullen et al. | Jun 2015 | B1 |
| 9071543 | Plamondon | Jun 2015 | B2 |
| 9106414 | Laves | Aug 2015 | B2 |
| 9165292 | Aguilar | Oct 2015 | B2 |
| 9165295 | Kim | Oct 2015 | B2 |
| 9224144 | Smith | Dec 2015 | B2 |
| 9245410 | Anderson | Jan 2016 | B2 |
| 9292843 | Mullen et al. | Mar 2016 | B1 |
| 9299227 | Billett | Mar 2016 | B2 |
| 9306666 | Zhang et al. | Apr 2016 | B1 |
| 9329619 | Cloutier | May 2016 | B1 |
| 9349089 | Rhoades et al. | May 2016 | B1 |
| 9361569 | Mullen et al. | Jun 2016 | B2 |
| 9373069 | Cloutier et al. | Jun 2016 | B2 |
| 9373119 | Salesky | Jun 2016 | B2 |
| 9384438 | Mullen et al. | Jul 2016 | B2 |
| 9396470 | Gannon | Jul 2016 | B2 |
| 9405984 | Irwin, Jr. | Aug 2016 | B2 |
| 9496991 | Plamondon | Nov 2016 | B2 |
| 9507667 | Scott | Nov 2016 | B1 |
| 9542675 | Hammad | Jan 2017 | B2 |
| 9547816 | Mullen et al. | Jan 2017 | B2 |
| 9619741 | Rigatti | Apr 2017 | B1 |
| 9639796 | Mullen et al. | May 2017 | B2 |
| 9646240 | Mullen et al. | May 2017 | B1 |
| 9652436 | Yen et al. | May 2017 | B1 |
| 9665879 | Aloni | May 2017 | B2 |
| 9684861 | Mullen et al. | Jun 2017 | B2 |
| 9684899 | Mohsenzadeh | Jun 2017 | B1 |
| D792511 | Mullen et al. | Jul 2017 | S |
| D792512 | Mullen et al. | Jul 2017 | S |
| D792513 | Mullen et al. | Jul 2017 | S |
| 9697454 | Mullen et al. | Jul 2017 | B2 |
| 9704088 | Mullen et al. | Jul 2017 | B2 |
| 9704089 | Mullen et al. | Jul 2017 | B2 |
| 9710745 | O'Shea | Jul 2017 | B1 |
| 9721201 | Mullen et al. | Aug 2017 | B1 |
| 9721425 | Irwin, Jr. | Aug 2017 | B2 |
| 9727813 | Mullen et al. | Aug 2017 | B2 |
| 9734669 | Mullen | Aug 2017 | B1 |
| 9773212 | Hammad | Sep 2017 | B2 |
| 9792592 | Delolme | Oct 2017 | B2 |
| 9805297 | Mullen et al. | Oct 2017 | B2 |
| 9818125 | Mullen et al. | Nov 2017 | B2 |
| 9836680 | Cloutier | Dec 2017 | B1 |
| 9852368 | Yen et al. | Dec 2017 | B1 |
| 9852428 | King | Dec 2017 | B2 |
| 9875437 | Cloutier et al. | Jan 2018 | B2 |
| 9881245 | Rhoades et al. | Jan 2018 | B1 |
| 9881306 | Gannon | Jan 2018 | B2 |
| 9916992 | Mullen et al. | Mar 2018 | B2 |
| 9928456 | Cloutier et al. | Mar 2018 | B1 |
| 9934669 | Hwang | Apr 2018 | B2 |
| 9953255 | Yen et al. | Apr 2018 | B1 |
| 9965757 | Bhinder | May 2018 | B2 |
| 10022884 | Cloutier | Jul 2018 | B1 |
| 10032100 | Mullen et al. | Jul 2018 | B2 |
| 10032156 | Al-Sahli | Jul 2018 | B2 |
| 10049385 | Killoran, Jr. | Aug 2018 | B2 |
| 10055614 | Cloutier et al. | Aug 2018 | B1 |
| 10062024 | Bohac, Jr. | Aug 2018 | B1 |
| 10095970 | Mullen | Oct 2018 | B1 |
| 10095974 | Mullen et al. | Oct 2018 | B1 |
| 10127550 | Mohsenzadeh | Nov 2018 | B2 |
| 10169692 | Mullen et al. | Jan 2019 | B2 |
| 10169693 | Batra | Jan 2019 | B1 |
| 10176419 | Cloutier et al. | Jan 2019 | B1 |
| 10176423 | Mullen et al. | Jan 2019 | B1 |
| 10181097 | Mullen et al. | Jan 2019 | B1 |
| 10198687 | Mullen et al. | Feb 2019 | B2 |
| 10223631 | Mullen et al. | Mar 2019 | B2 |
| 10255545 | Mullen et al. | Apr 2019 | B2 |
| 10275582 | Carlson | Apr 2019 | B2 |
| 10318980 | Crowe | Jun 2019 | B2 |
| 10325199 | Mullen et al. | Jun 2019 | B2 |
| 10402897 | Czyzewski | Sep 2019 | B1 |
| 10430704 | Mullen et al. | Oct 2019 | B2 |
| 10430845 | Koretz | Oct 2019 | B2 |
| 10467521 | Mullen et al. | Nov 2019 | B2 |
| 10482363 | Cloutier et al. | Nov 2019 | B1 |
| 10496918 | Mullen et al. | Dec 2019 | B2 |
| 10504105 | Mullen et al. | Dec 2019 | B2 |
| 10552883 | Yoder | Feb 2020 | B2 |
| 10579920 | Mullen et al. | Mar 2020 | B2 |
| 10657588 | Stewart | May 2020 | B2 |
| 10693263 | Mullen et al. | Jun 2020 | B1 |
| 10936926 | Rhoades et al. | Mar 2021 | B1 |
| 10948964 | Cloutier | Mar 2021 | B1 |
| 10997489 | Mullen et al. | May 2021 | B2 |
| 11062195 | Mullen | Jul 2021 | B2 |
| 11144909 | Mullen et al. | Oct 2021 | B1 |
| 11238329 | Mullen et al. | Feb 2022 | B2 |
| 20010034702 | Mockett et al. | Oct 2001 | A1 |
| 20010047335 | Arndt et al. | Nov 2001 | A1 |
| 20020059114 | Cockrill et al. | May 2002 | A1 |
| 20020082989 | Fife et al. | Jun 2002 | A1 |
| 20020096570 | Wong et al. | Jul 2002 | A1 |
| 20020120583 | Keresman, III et al. | Aug 2002 | A1 |
| 20030034388 | Routhenstein et al. | Feb 2003 | A1 |
| 20030052168 | Wong | Mar 2003 | A1 |
| 20030057278 | Wong | Mar 2003 | A1 |
| 20030116635 | Taban | Jun 2003 | A1 |
| 20030139985 | Hollar | Jul 2003 | A1 |
| 20030152253 | Wong | Aug 2003 | A1 |
| 20030163287 | Vock et al. | Aug 2003 | A1 |
| 20030173409 | Vogt et al. | Sep 2003 | A1 |
| 20030179909 | Wong et al. | Sep 2003 | A1 |
| 20030179910 | Wong | Sep 2003 | A1 |
| 20030226899 | Finkelstein | Dec 2003 | A1 |
| 20040035942 | Silverman | Feb 2004 | A1 |
| 20040039635 | Linde et al. | Feb 2004 | A1 |
| 20040128195 | Sorem | Jul 2004 | A1 |
| 20040133787 | Doughty | Jul 2004 | A1 |
| 20040162732 | Rahim et al. | Aug 2004 | A1 |
| 20040172535 | Jakobsson | Sep 2004 | A1 |
| 20040177045 | Brown | Sep 2004 | A1 |
| 20050043997 | Sohata et al. | Feb 2005 | A1 |
| 20050060261 | Remington | Mar 2005 | A1 |
| 20050080747 | Anderson et al. | Apr 2005 | A1 |
| 20050086160 | Wong et al. | Apr 2005 | A1 |
| 20050086177 | Anderson et al. | Apr 2005 | A1 |
| 20050116026 | Burger et al. | Jun 2005 | A1 |
| 20050119940 | Concilio et al. | Jun 2005 | A1 |
| 20050154643 | Doan et al. | Jul 2005 | A1 |
| 20050223392 | Cox | Oct 2005 | A1 |
| 20050228959 | D'Albore et al. | Oct 2005 | A1 |
| 20060000900 | Fernandes et al. | Jan 2006 | A1 |
| 20060037073 | Juels et al. | Feb 2006 | A1 |
| 20060041759 | Kaliski et al. | Feb 2006 | A1 |
| 20060085328 | Cohen et al. | Apr 2006 | A1 |
| 20060091223 | Zellner et al. | May 2006 | A1 |
| 20060161435 | Atef et al. | Jul 2006 | A1 |
| 20060163353 | Moulette et al. | Jul 2006 | A1 |
| 20060174104 | Crichton et al. | Aug 2006 | A1 |
| 20060196931 | Holtmanns et al. | Sep 2006 | A1 |
| 20060256961 | Brainard et al. | Nov 2006 | A1 |
| 20070034700 | Poidomani et al. | Feb 2007 | A1 |
| 20070114274 | Gibbs et al. | May 2007 | A1 |
| 20070124321 | Szydlo | May 2007 | A1 |
| 20070129955 | Dalmia et al. | Jun 2007 | A1 |
| 20070152070 | D'Albore | Jul 2007 | A1 |
| 20070152072 | Frallicciardi et al. | Jul 2007 | A1 |
| 20070153487 | Frallicciardi et al. | Jul 2007 | A1 |
| 20070174614 | Duane et al. | Jul 2007 | A1 |
| 20070192215 | Taylor et al. | Aug 2007 | A1 |
| 20070241183 | Brown et al. | Oct 2007 | A1 |
| 20070241201 | Brown et al. | Oct 2007 | A1 |
| 20070256123 | Duane et al. | Nov 2007 | A1 |
| 20070192249 | Biffle et al. | Dec 2007 | A1 |
| 20070291753 | Romano | Dec 2007 | A1 |
| 20080005510 | Sepe et al. | Jan 2008 | A1 |
| 20080008315 | Fontana et al. | Jan 2008 | A1 |
| 20080008322 | Fontana et al. | Jan 2008 | A1 |
| 20080010675 | Massascusa et al. | Jan 2008 | A1 |
| 20080016351 | Fontana et al. | Jan 2008 | A1 |
| 20080019507 | Fontana et al. | Jan 2008 | A1 |
| 20080028447 | O'Malley et al. | Jan 2008 | A1 |
| 20080029607 | Mullen | Feb 2008 | A1 |
| 20080035738 | Mullen | Feb 2008 | A1 |
| 20080040271 | Hammad et al. | Feb 2008 | A1 |
| 20080040276 | Hammad et al. | Feb 2008 | A1 |
| 20080054068 | Mullen | Mar 2008 | A1 |
| 20080054079 | Mullen | Mar 2008 | A1 |
| 20080054081 | Mullen | Mar 2008 | A1 |
| 20080058016 | Di Maggio et al. | Mar 2008 | A1 |
| 20080059379 | Ramaci et al. | Mar 2008 | A1 |
| 20080065555 | Mullen | Mar 2008 | A1 |
| 20080096326 | Reed | Apr 2008 | A1 |
| 20080126398 | Cimino | May 2008 | A1 |
| 20080128515 | Di Iorio | Jun 2008 | A1 |
| 20080148394 | Poidomani et al. | Jun 2008 | A1 |
| 20080201264 | Brown et al. | Aug 2008 | A1 |
| 20080209550 | Di Iorio | Aug 2008 | A1 |
| 20080288699 | Chichierchia | Nov 2008 | A1 |
| 20080294930 | Varone et al. | Nov 2008 | A1 |
| 20080302869 | Mullen | Dec 2008 | A1 |
| 20080302876 | Mullen | Dec 2008 | A1 |
| 20080302877 | Musella et al. | Dec 2008 | A1 |
| 20090013122 | Sepe et al. | Jan 2009 | A1 |
| 20090036147 | Romano | Feb 2009 | A1 |
| 20090046522 | Sepe et al. | Feb 2009 | A1 |
| 20090048916 | Nuzum et al. | Feb 2009 | A1 |
| 20090106159 | Delolme et al. | Apr 2009 | A1 |
| 20090108064 | Fernandes et al. | Apr 2009 | A1 |
| 20090150237 | Gupta et al. | Jun 2009 | A1 |
| 20090150295 | Hatch et al. | Jun 2009 | A1 |
| 20090152365 | Li et al. | Jun 2009 | A1 |
| 20090159663 | Mullen et al. | Jun 2009 | A1 |
| 20090159667 | Mullen et al. | Jun 2009 | A1 |
| 20090159668 | Mullen et al. | Jun 2009 | A1 |
| 20090159669 | Mullen et al. | Jun 2009 | A1 |
| 20090159670 | Mullen et al. | Jun 2009 | A1 |
| 20090159671 | Mullen et al. | Jun 2009 | A1 |
| 20090159672 | Mullen et al. | Jun 2009 | A1 |
| 20090159673 | Mullen et al. | Jun 2009 | A1 |
| 20090159680 | Mullen et al. | Jun 2009 | A1 |
| 20090159681 | Mullen et al. | Jun 2009 | A1 |
| 20090159682 | Mullen et al. | Jun 2009 | A1 |
| 20090159688 | Mullen et al. | Jun 2009 | A1 |
| 20090159689 | Mullen et al. | Jun 2009 | A1 |
| 20090159690 | Mullen et al. | Jun 2009 | A1 |
| 20090159696 | Mullen | Jun 2009 | A1 |
| 20090159697 | Mullen et al. | Jun 2009 | A1 |
| 20090159698 | Mullen et al. | Jun 2009 | A1 |
| 20090159699 | Mullen et al. | Jun 2009 | A1 |
| 20090159700 | Mullen et al. | Jun 2009 | A1 |
| 20090159701 | Mullen et al. | Jun 2009 | A1 |
| 20090159702 | Mullen | Jun 2009 | A1 |
| 20090159703 | Mullen et al. | Jun 2009 | A1 |
| 20090159704 | Mullen et al. | Jun 2009 | A1 |
| 20090159705 | Mullen et al. | Jun 2009 | A1 |
| 20090159706 | Mullen et al. | Jun 2009 | A1 |
| 20090159707 | Mullen et al. | Jun 2009 | A1 |
| 20090159708 | Mullen et al. | Jun 2009 | A1 |
| 20090159709 | Mullen | Jun 2009 | A1 |
| 20090159710 | Mullen et al. | Jun 2009 | A1 |
| 20090159711 | Mullen et al. | Jun 2009 | A1 |
| 20090159712 | Mullen et al. | Jun 2009 | A1 |
| 20090159713 | Mullen et al. | Jun 2009 | A1 |
| 20090160617 | Mullen et al. | Jun 2009 | A1 |
| 20090198617 | Soghoian | Aug 2009 | A1 |
| 20090242648 | Di Sirio et al. | Oct 2009 | A1 |
| 20090244858 | Di Sirio et al. | Oct 2009 | A1 |
| 20090253460 | Varone et al. | Oct 2009 | A1 |
| 20090255996 | Brown et al. | Oct 2009 | A1 |
| 20090290704 | Cimino | Nov 2009 | A1 |
| 20090303885 | Longo | Dec 2009 | A1 |
| 20090308921 | Mullen | Dec 2009 | A1 |
| 20100198574 | Veller | Aug 2010 | A1 |
| 20110028184 | Cooper | Feb 2011 | A1 |
| 20110272465 | Mullen et al. | Nov 2011 | A1 |
| 20110272466 | Mullen et al. | Nov 2011 | A1 |
| 20110272467 | Mullen et al. | Nov 2011 | A1 |
| 20110272471 | Mullen | Nov 2011 | A1 |
| 20110272472 | Mullen | Nov 2011 | A1 |
| 20110272473 | Mullen et al. | Nov 2011 | A1 |
| 20110272474 | Mullen et al. | Nov 2011 | A1 |
| 20110272475 | Mullen et al. | Nov 2011 | A1 |
| 20110272476 | Mullen et al. | Nov 2011 | A1 |
| 20110272477 | Mullen et al. | Nov 2011 | A1 |
| 20110272478 | Mullen | Nov 2011 | A1 |
| 20110272479 | Mullen | Nov 2011 | A1 |
| 20110272480 | Mullen et al. | Nov 2011 | A1 |
| 20110272481 | Mullen et al. | Nov 2011 | A1 |
| 20110272482 | Mullen et al. | Nov 2011 | A1 |
| 20110272483 | Mullen et al. | Nov 2011 | A1 |
| 20110272484 | Mullen et al. | Nov 2011 | A1 |
| 20110276380 | Mullen et al. | Nov 2011 | A1 |
| 20110276381 | Mullen et al. | Nov 2011 | A1 |
| 20110276416 | Mullen et al. | Nov 2011 | A1 |
| 20110276424 | Mullen | Nov 2011 | A1 |
| 20110276425 | Mullen | Nov 2011 | A1 |
| 20110276436 | Mullen et al. | Nov 2011 | A1 |
| 20110276437 | Mullen et al. | Nov 2011 | A1 |
| 20110278364 | Mullen et al. | Nov 2011 | A1 |
| 20110282753 | Mullen et al. | Nov 2011 | A1 |
| 20110284632 | Mullen et al. | Nov 2011 | A1 |
| 20110284640 | Mullen et al. | Nov 2011 | A1 |
| 20120028702 | Mullen et al. | Feb 2012 | A1 |
| 20120037709 | Cloutier et al. | Feb 2012 | A1 |
| 20120158654 | Behren | Jun 2012 | A1 |
| 20120185397 | Levovitz | Jul 2012 | A1 |
| 20120197708 | Mullen et al. | Aug 2012 | A1 |
| 20120209744 | Mullen et al. | Aug 2012 | A1 |
| 20120254037 | Mullen | Oct 2012 | A1 |
| 20120254038 | Mullen | Oct 2012 | A1 |
| 20120285972 | Fu | Nov 2012 | A1 |
| 20120286037 | Mullen et al. | Nov 2012 | A1 |
| 20120286928 | Mullen et al. | Nov 2012 | A1 |
| 20120286936 | Mullen et al. | Nov 2012 | A1 |
| 20120290449 | Mullen et al. | Nov 2012 | A1 |
| 20120290472 | Mullen et al. | Nov 2012 | A1 |
| 20120318871 | Mullen et al. | Dec 2012 | A1 |
| 20120326013 | Cloutier et al. | Dec 2012 | A1 |
| 20130020396 | Mullen et al. | Jan 2013 | A1 |
| 20130217152 | Mullen et al. | Aug 2013 | A1 |
| 20130282573 | Mullen et al. | Oct 2013 | A1 |
| 20130282575 | Mullen et al. | Oct 2013 | A1 |
| 20140054384 | Cloutier et al. | Feb 2014 | A1 |
| 20150186766 | Mullen et al. | Jul 2015 | A1 |
| 20160162713 | Cloutier et al. | Jun 2016 | A1 |
| 20160180209 | Mullen et al. | Jun 2016 | A1 |
| 20160239735 | Mullen et al. | Aug 2016 | A1 |
| 20160283837 | Mullen et al. | Sep 2016 | A1 |
| 20160307085 | Mullen et al. | Oct 2016 | A1 |
| 20160335529 | Mullen et al. | Nov 2016 | A1 |
| 20160342876 | Mullen et al. | Nov 2016 | A1 |
| 20160342877 | Mullen et al. | Nov 2016 | A1 |
| 20160342878 | Mullen et al. | Nov 2016 | A1 |
| 20160342879 | Mullen et al. | Nov 2016 | A1 |
| 20160342880 | Mullen et al. | Nov 2016 | A1 |
| 20170286817 | Mullen et al. | Oct 2017 | A1 |
| 20170300796 | Mullen et al. | Oct 2017 | A1 |
| 20180012226 | Phillips | Jan 2018 | A1 |
| 20180053079 | Cloutier et al. | Feb 2018 | A1 |
| 20180060881 | Mullen et al. | Mar 2018 | A1 |
| 20180151391 | Mullen et al. | May 2018 | A1 |
| 20190026613 | O'Shea | Jan 2019 | A1 |
| 20190042903 | Cloutier et al. | Feb 2019 | A1 |
| 20190065928 | Mullen et al. | Feb 2019 | A1 |
| 20190197387 | Mullen et al. | Jun 2019 | A1 |
| 20190340484 | Mullen et al. | Nov 2019 | A1 |
| 20200051050 | Liu | Feb 2020 | A1 |
| 20200074555 | Cruttenden | Mar 2020 | A1 |
| 20200082383 | Mullen et al. | Mar 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 05210770 | Aug 1993 | JP |
| WO9852735 | Nov 1998 | WO |
| WO0247019 | Jun 2002 | WO |
| WO06066322 | Jun 2006 | WO |
| WO06080929 | Aug 2006 | WO |
| WO06105092 | Oct 2006 | WO |
| WO06116772 | Nov 2006 | WO |
| WO08064403 | Jun 2008 | WO |
| Entry |
|---|
| U.S. Appl. No. 60/594,300, Poidomani et al. |
| U.S. Appl. No. 60/675,388, Poidomani et al. |
| The Bank Credit Card Business. Second Edition, American Bankers Association, Washington, D.C., 1996. |
| A Day in the Life of a Flux Reversal. http://www.phrack/org/issues.html?issue=37&id=6#article. As viewed on Apr. 12, 2010. |
| Dynamic Virtual Credit Card Numbers. http://homes.cerias.purdue.edu/˜jtli/paper/fc07.pdf. As viewed on Apr. 12, 2010. |
| English translation of JP 05210770 A. |
| Number | Date | Country | |
|---|---|---|---|
| 61624377 | Apr 2012 | US |
