A payment device, method, and apparatus configured to determine the form factor of the payment device used in a financial transaction, without requiring a different primary account number for each payment device form factor.
1. Field of the Invention
Aspects of the present invention relate in general to financial services. Aspects include a payment form factor identification apparatus, system, method and computer-readable storage medium configured to identify the form factor of a payment device.
2. Description of the Related Art
Traditionally, when a consumer cardholder makes a purchase from a merchant, a payment card, such as a debit, credit or charge card, can be used to pay for the transaction. Such payment cards are identified by their unique primary account number (PAN). When multiple cards are issued to an account holder, these cards all share the same primary account number. For example, a husband, wife and child may all share multiple Visa™ cards with the same primary account number, and receive a single consolidated bill. While it may be convenient for a customer to be sent a single bill, purchases made by husband, wife, and child are mixed together on the same bill, and there is no way to identify who made each purchase. The mixing of purchases leads to confusion on who made each purchase, and may also mask fraudulent charges to the account.
Moreover, new form factors of payment devices, such as cell phones, key fobs, and the like are also issued with the same primary account number. As these purchases are made with the same primary account number, it is impossible to identify which payment device was used to pay for a purchase.
Embodiments of the invention include a system and method configured to identify the payment form factor used in a payment transaction. Despite the fact that the industry does not capture or utilize such information, one aspect of the invention includes the insight that tracking the form factor used would be useful. Moreover, the embodiments of the invention are fully compatible with existing payment card/device implementations, and do not require a different primary account number for each form factor. In one embodiment, a card transceiver/scanner is configured to receive transaction data from the payment device in a financial transaction. The transaction data including a form factor indicator embedded within. A form factor identifier, coupled to the card transceiver/scanner, is configured to parse the form factor indicator from the transaction data. A data processor either transmits the form factor indicator to a payment processor via a network interface, or stores the form factor indicator in a form factor log database.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates an embodiment of a system configured to identify the payment form factor used in a payment transaction.
FIG. 2 flowcharts a method embodiment configured to identify the payment form factor used in a payment transaction.
FIG. 3 is table showing a device indicator value embodiment configured to identify the payment form factor used in a payment transaction.
FIG. 4 is a table illustrating track 2 of a card embodiment configured to identify the payment form factor used in a payment transaction.
FIG. 5 illustrates a device configured to identify the payment form factor used in a payment transaction.
Although the payment card industry does not currently capture or utilize form factor information, one aspect of the present includes the insight that tracking the form factor used in a financial transaction would be useful to consumers, card issuers, and card payment processors. First, card holders will be able to more easily identify and verify payment transactions through form factor used, identifying fraudulent transactions.
For the purposes of this document, a financial transaction is any operation involving a payment device, whether a payment, reimbursement, or any other interaction using a payment device. Financial transactions may be credit, debit, or charge transactions.
As the embodiments of the invention are fully compatible with existing payment card/device implementations, and they do not require a different primary account number for each payment device form factor.
Embodiments of the present invention include a system, method, and computer-readable storage medium configured to identify the form factor of a payment device used in a financial transaction without requiring a different primary account number for each payment device form factor. Other embodiments of the present invention may include remote terminals configured to capture, encode, or record the form factor information.
Turning to FIG. 1, this figure depicts system 1000, configured to identify the form factor of a payment device used in a financial transaction, constructed and operative in accordance with an embodiment of the present invention. In this example, payment device 100 is may be any credit, debit, or charge device. Examples include, but are not limited to a standard payment device 100a, a radio frequency or “contactless” payment device 100b, a mobile phone device 100c, a mini-card 100d, micro tag 100e, payment fob, or any other payment device known in the art. It is understood that embodiments of the present invention may be extended to identify and track future payment devices.
When the consumer uses the payment device 100 at a merchant 1100 to pay for a product or service, the merchant 1100 contacts an acquirer 1300 (for example, a commercial bank) via a network 1200 to determine whether the consumer is credit worthy or the account has sufficient funds on the card to pay for the transaction. The acquirer 1300 forwards the details of the payment transaction to a payment processor 1400 or payment card issuing bank 1500 (“the issuer”) for processing.
The merchant 1100 may comprised a point-of-sale read/writer device 1110. Examples of such devices include, but are not limited to: payment terminals, card readers, scanners, cash registers, and the like. In some embodiments of the present invention, a point-of sale reader may substitute for a read/write device 1110. Internal details of point-of-sale read/writer device 1110 are discussed at FIG. 5 below.
A merchant’s private network 1120 connects the point-of-sale read/writer 1110 to a merchant central computer 1130. In some instances, a list of fraudulent cards may be stored at a hotlist storage database 1140.
Payment processor 1400 may be any payment network known in the art. Examples of payment networks include: Visa™, MasterCard™, and American Express™.
Issuer 1500 may be any financial institution that issues the payment device 100.
Embodiments will now be disclosed with reference to a block diagram of an exemplary point-of-sale read/writer device 1110 of FIG. 5, constructed and operative in accordance with an embodiment of the present invention. Point-of-sale read/writer device 1110 may run a multi-tasking operating system (OS) and include at least one processor or central processing unit (CPU) 5100. Processor 5100 may be any central processing unit, microprocessor, micro-controller, computational device or circuit known in the art.
It is well understood by those in the art, that the functional elements of FIG. 5 may be implemented in hardware, firmware, or as software instructions and data encoded on a computer-readable storage medium 5300. As shown in FIG. 5, processor 5100 is functionally comprised of a point-of-sale engine 5110 and data processor 5102. Point-of-sale engine 5110 may further comprise: transaction validator 5112 and form factor identifier 5114. These structures may be implemented as hardware, firmware, or software encoded on a computer readable medium, such as storage media 5300.
Data processor 5102 interfaces with storage medium 5300, card transceiver/scanner 5200 and network interface 5400. The data processor 5102 enables processor 5100 to locate data on, read data from, and writes data to, these components.
Card transceiver/scanner 5200 may be any component known in the art capable of read/writing data to or from payment devices 100. For example, for conventional credit card 100a or mini-card 100d embodiments, card transceiver/scanner 5200 may read or write to a magnetic strip. Embodiments that communicate with a contactless card 100b, mobile phone 100c, and micro tag/key fob 100e include a wireless transceiver.
Network interface 5400 may be any data port as is known in the art for interfacing, communicating or transferring data across a computer network, examples of such networks include Transmission Control Protocol/Internet Protocol (TCP/IP), Ethernet, Fiber Distributed Data Interface (FDDI), token bus, or token ring networks. Network interface 5400 allows point-of-sale read/writer device 1110 to communicate with issuer 1500, and may allow communication with acquirer 1300.
Computer-readable storage medium 5300 may be a conventional read/write memory such as a magnetic disk drive, floppy disk drive, compact-disk read-only-memory (CD-ROM) drive, digital versatile disk (DVD) drive, high definition digital versatile disk (HD-DVD) drive, magneto-optical drive, optical drive, flash memory, memory stick, transistor-based memory or other computer-readable memory device as is known in the art for storing and retrieving data. Significantly, computer-readable storage medium 5300 may be remotely located from processor 5100, and be connected to processor 5100 via a network such as a local area network (LAN), a wide area network (WAN), or the Internet. In addition, as shown in FIG. 5, storage media 5300 may also contain form factor log database 5310. Note that in some embodiments, form factor log database may be located at merchant central computer 1130, payment processor 1400, or issuer 1500. The function of these structures may best be understood with respect to FIGS. 2-4, as described below.
We now turn our attention to method or process embodiments of the present invention, FIG. 2. It is understood by those known in the art that instructions for such method embodiments may be stored on their respective computer-readable memory and executed by their respective processors.
FIG. 2 flowcharts a process 2000 in which point-of-sale read/writer device 1110 is configured to identify the payment form factor used in a payment transaction, constructed and operative in accordance with an embodiment of the present invention. The process begins when the financial transaction starts. At block 2002, point-of-sale read/writer device 1110 receives transaction data (also known as “track 2 equivalent data”) from the payment device 100. The transaction data is received as part of an authorization request, as a customer uses payment device 100 to pay for a financial transaction. The data is received via card transceiver/scanner 5200 and includes information such as the primary account number (PAN). Usually, a payment device’s Primary Account Number is either a 15 or 16 digit number. The first six digits of a Visa™ or MasterCard™ Primary Account Number identifies the card issuer banking institution 1400 and is known as the “Bank Identification Number” or “BIN.” In some embodiments, such as debit transactions, the authorization request may also contain a user verification identifier, such as the customer’s personal identification number (PIN) or biometric information.
At decision block 2004, transaction validator 5112 determines whether the data was received via a wireless (contactless) interface. Such interfaces are also known as “paywave” reception. If the payment device is not contactless, process 2000 continues at block 2006. If contactless, the process flow continues at block 2016.
For the purposes of this example embodiment, non-contactless payment devices 100 are assumed to be encoded with a static magnetic stripe. The magnetic stripe is encoded with an embodiment of track 2 equivalent data, as shown in FIG. 4. As shown in FIG. 4, track 2 equivalent data 4000 includes the primary account number (usually 15-16 digits, but up to 19 digits), a separator (one character) a payment device expiration date (4 digits), a service code (3) digits), and pin verification data. In contactless embodiments, the track 2 equivalent data may also include issuer discretionary data. Traditionally, the issuer discretionary data included a dynamic card verification value code, a one character PIN Verification Key Indicator, and other unused data positions. However, embodiments of the present invention the issuer discretionary data includes a form factor indicator (shown as the “contactless indicator”) to be encoded where traditionally unused data positions exist.
FIG. 3 illustrates a table showing a device indicator value 3000 embodiment configured to identify the payment form factor used in a payment transaction, constructed and operative in accordance with an embodiment of the present invention. As shown, device indicator value 3000 reserves values contemplating use of full-size standard non-contactless payment cards 100a, a full-size contactless payment card 100b, a standard non-contactless mini card 100d, a contactless mini-card, a micro tag 100e, mobile device 100c, and alternate card users. It is understood that device indicator value 3000 embodiments may include some or all of such form factors.
Returning to FIG. 2, at block 2006, transaction validator 5112 verifies the transaction field’s card verification value (CVV) code.
The card verification value is an authentication procedure established by credit card companies to further efforts towards reducing fraud for transactions. It consists of requiring a card holder to enter the CVV number in at transaction time to verify that the card is on hand. The CVV code is a security feature for “card not present” transactions (e.g., Internet transactions), and now appears on most (but not all) major credit and debit cards. This new feature is a three- or four-digit code which provides a cryptographic check of the information embossed on the card. Therefore, the CVV code is not part of the card number itself. The CVV code helps ascertain that the customer placing the order actually possesses the credit/debit card and that the card account is legitimate. Each credit card company has its own name for the CVV code, but it functions the same for all major card types. (VISA refers to the code as “CVV2,” MasterCard calls it “CVC2,” and American Express calls it “CID.”)
Merchant 1100, and, in turn, acquirer 1300 seek authorization before performing the transaction.
If the transaction fields are not valid, as determined by decision block 2008, the transaction is denied, and a message is sent to merchant 1100, block 2026.
At block 2010, form factor identifier 5114 determines the location of the device indicator information 3000 from the track 2 equivalent data 4000. The form factor information is read and logged at form factor log database 5310, and forwarded to the issuer at block 2014. Process 2000 the ends.
At block 2016, contactless payment devices are addressed. Such unlike devices with static magnetic strips, contactless devices have dynamic card verification values (DCVV). In such embodiments, a new verification number is generated after each transaction.
If the transaction fields are not valid, as determined by decision block 2018, the transaction is denied, and a message is sent to merchant 1100, block 2026.
At block 2020, form factor identifier 5114 determines the location of the form factor information from the track 2 equivalent data. The form factor information is read from the device indicator value 3000 and is logged, block 2022, and forwarded to the issuer at block 2024. Process 2000 the ends.
The previous description of the embodiments is provided to enable any person skilled in the art to practice the invention. The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.