Patent Description:
The present disclosure relates generally to point of sale technology and, more specifically, to an exemplary system and method for handling rejection of a card presented at a point of sale device.

Account-linked cards have become commonplace, as many individuals use account-linked cards such as those for access to credit or debit accounts, membership club accounts, rewards accounts, parking facilities, secured buildings, accounts at banking institutions, accounts for mass transportation and other types of accounts. Account-linked cards are frequently used with card readers or devices equipped with card readers, some of which require the account holder to insert the account-linked card containing information on a magnetic strip or embedded memory into the card reader. After the card has been read and authenticated, the account holder may be able to carry out a variety of transactions or inquiries. However, on occasion an account holder may have his or her card rejected after submission to a card reader at a point of sale system, resulting in inconvenience and potential embarrassment to the account holder. Card rejection may happen for a number of reasons, such as, for example, expiration of the account, insufficient funds, etc..

<CIT> describes a real-time payment authorization.

<CIT> describes a wireless smart card configured for contactless payment transactions, methods for contactless transactions using the wireless smart card and a system for contactless transactions using the wireless smart card.

<CIT> describes apparatus and methods for effecting digital transactions, including both financial and non-financial transactions.

<CIT> describes electronic transaction cards (e-cards) automatically reporting transaction attempts to the bank card customer's consumer electronics (CE) device.

<CIT> describes a method and system for performing secure transactions either in a regular or virtual store.

<CIT> describes a system and method for processing financial transactions using multiple financial accounts.

<CIT> describes card processing methods and systems.

<CIT> describes methods and systems for depositing funds onto NFC smart cards for use during the offline processing of purchases.

<CIT> describes a method and system for authenticating cardholders while carrying out credit card transactions.

Thus, it may be beneficial to provide exemplary systems and methods which allow users to handle card rejection in a rapid and straightforward manner to overcome at least some of the deficiencies described herein.

Aspects of the disclosed technology include systems and methods for transaction processing control. Transaction processing control may be provided in the context of providing account information, including handling requests to select and provide a second account number via a mobile device in communication with a rejected card such that the rejected card need not be removed from the point of sale device and a second card need not be submitted to the point of sale device. In this way, a second account number may be rapidly provided in a secure manner without having to store multiple account numbers on the card. This provides an advantage over use of a card storing multiple account numbers, since loss or theft of such a card having multiple account numbers would present heightened risk to a user by exposing multiple accounts, rather than a single account, to a thief or other party possessing the card.

According to a first aspect of the disclosed technology there is provided a point of sale device according to claim <NUM>. Embodiments of the present disclosure provide a point of sale device, comprising: a card reader configured to read account information from an inserted card, the account information including an inserted card account number that is stored on the inserted card; a communications interface that is configured for data communication with an authorization network; and a processor connected to the card reader and the communications interface, the processor configured to: receive the account information from the card reader; communicate the inserted card account number via the authorization network to determine whether a transaction associated with the inserted card is authorized; receive an authorization response, the authorization response including a rejection notification if the transaction is not authorized; transmit the rejection notification to a mobile device, the mobile device in data communication with the inserted card via a wireless connection; receive a second account number that is stored on the mobile device; and communicate the second account number via the authorization network to determine whether the transaction associated with the second account number is authorized.

According to an alternative first aspect of the disclosed technology there is provided a point of sale device according to claim <NUM>.

According to a second aspect of the disclosed technology there is provided a payment card according to claim <NUM>. Embodiments of the present disclosure provide a payment card, comprising: memory configured to store a first account number; a contact pad configured to, when the payment card is inserted into a point of sale device, transmit the account number to a card reader of the point of sale device and to receive a transaction rejection response if a transaction associated with the first account number is rejected; and a wireless communication interface configured for data communication with a mobile device; wherein, the transaction rej ection response, upon receipt via the contact pad, is transmitted to the mobile device, thereby causing the mobile device to transmit a second account number stored on the mobile device in a manner that enables the second account number to be used to process the transaction instead of the first account number.

According to a third aspect of the disclosed technology there is provided a method for transaction processing control according to claim <NUM>. Embodiments of the present disclosure provide a method for transaction processing control, comprising: receiving, at a card reader of a point of sale device via a contact pad on a payment card in communication with the card reader, a first account number associated with the payment card; transmitting, via a communications interface, a first transaction authorization request that includes the first account number and a transaction amount to an authorization network; receiving, via the communications interface, a transaction rejection from the authorization network, said transaction rejection responsive to the first transaction authorization request; transmitting information indicating the transaction rejection to the contact pad on the payment card via the card reader; receiving, at the card reader of the point of sale device via the contact pad on the payment card, a second account number that is not associated with the payment card, said second account number being stored on a mobile device in wireless communication with the payment card; and transmitting, via a communications interface, a second transaction authorization request that includes the second account number and the transaction amount to an authorization network.

Further features of the disclosed design, and the advantages offered thereby, are explained in greater detail hereinafter with reference to specific example embodiments described below and illustrated in the accompanying drawings.

The following description of embodiments provides non-limiting representative examples referencing numerals to particularly describe features and teachings of different aspects of the invention. The embodiments described should be recognized as capable of implementation separately, or in combination, with other embodiments from the description of the embodiments. A person of ordinary skill in the art reviewing the description of embodiments should be able to learn and understand the different described aspects of the invention. The description of embodiments should facilitate understanding of the invention to such an extent that other implementations, not specifically covered but within the knowledge of a person of skill in the art having read the description of embodiments, would be understood to be consistent with an application of the invention.

Exemplary embodiments of the disclosed systems and methods provide for transaction processing control through the interaction of a point of sale device, an account-linked card, and a mobile device to provide a second account number upon rejection, at a point of sale, of an account associated with the account-linked card. Benefits of the disclosed technology may include improved data security for account information, improved fraud prevention, and improved user experience.

<FIG> shows a diagram illustrating a transaction processing control system <NUM> according to one or more example embodiments. As discussed further below, system <NUM> may include point of sale (POS) device <NUM>, account linked card <NUM>, mobile device <NUM>, and server <NUM>. Mobile device <NUM> may communicate with POS device <NUM> via short-range wireless communication field <NUM>, which may include Bluetooth, near field communication (NFC), or RFID. In some embodiments, Mobile device <NUM> may communicate with POS device <NUM> through server <NUM> via network <NUM>. In some embodiments, POS device <NUM> may communicate with transaction authorization network <NUM> through server <NUM> via network <NUM>. In some embodiments, POS device <NUM> may communicate with transaction authorization network <NUM> via network <NUM> or another network (not shown) without going through server <NUM>. Mobile device <NUM> may communicate with account linked card <NUM> via short-range wireless communication field <NUM>, which may include Bluetooth, NFC, or RFID. Although <FIG> illustrates certain components connected in certain ways, system <NUM> may include additional or multiple components connected in various ways via one or more networks.

System <NUM> may include one or more point of sale (POS) devices <NUM>. POS device <NUM> may be a terminal, ATM, kiosk, and/or another device in which a user inserts an account-linked card or other form of identification card and/or information card into a card reader. POS device <NUM> obtains account and/or card information from the card and transmits the information to card authorization network <NUM> for authorization of the requested transaction. Additional features that may be included in a POS device, such as point of sale (POS) device <NUM>, are further described below with reference to <FIG>.

System <NUM> may include one or more account-linked cards <NUM>. Account-linked card <NUM> may be a smart card or another type of card (including, e.g., a contactless card) configured for inserting, swiping, tapping etc. in or near POS device <NUM> (which may have a card reader for that purpose). Account-linked card <NUM> may be associated with an account holder or user. Account-linked card <NUM> may contain information regarding an account, including account number and/or other information regarding the account and card, such as, for example, account identification information (e.g., account number, account owner identification number, account owner name and contact information), account characteristics (e.g., type of account,), card issuer, etc. An account may be maintained by (or on behalf of) and/or relate to any one or more of a variety of entities, such as, for example (and without limitation) a bank, merchant, online retailer, service provider, merchandizer, manufacturer, social media provider, provider or promoter of sporting or entertainment events, hotel chain, etc. Additional features that may be included in an account-linked card, such as account-linked card <NUM>, are further described below with reference to <FIG>.

System <NUM> may include one or more mobile devices, such as mobile device <NUM>, which may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a thin client, a fat client, an Internet browser, or other device. A mobile device, such as mobile device <NUM>, may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple's iOS® operating system, any device running Microsoft's Windows® Mobile operating system, any device running Google's Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device. Additional features that may be included in a mobile device, such as mobile device <NUM>, are further described below with reference to <FIG>.

System <NUM> may include one or more servers <NUM>. In some example embodiments, server <NUM> may include one or more processors (such as, e.g., a microprocessor) which are coupled to memory. Server <NUM> may be configured as a central system, server or platform to control and call various data at different times to execute a plurality of workflow actions. Server <NUM> may be a dedicated server computer, such as bladed servers, or may be one or more personal computers, laptop computers, notebook computers, palm top computers, network computers, mobile devices, or any processor-controlled device capable of supporting the features of server <NUM>.

Server <NUM> may be configured for data communication (such as, e.g., via a connection) with POS device <NUM>. Connections between POS device <NUM> and server <NUM> may be made via any communications line, link or network, or combination thereof, wired and/or wireless, suitable for communicating between these components. Such network may include network <NUM> and/or one or more networks of same or similar type as those described herein with reference to network <NUM>. In some example embodiments, connections between POS device <NUM> and server <NUM> may include a corporate LAN.

Server <NUM> may be configured for data communication (such as, e.g., via a connection) with one or more other devices of system <NUM> via network <NUM>. For example, mobile device <NUM> may communicate with POS device <NUM> through server <NUM> via network <NUM>. Similarly, POS network <NUM> may communicate with authorization network <NUM> through server <NUM> via network <NUM>.

Authorization network <NUM> may include one or more parties that may be in the chain of communication for a transaction authorization request that is sent upon a user's attempt to use an account-linked card for a transaction. Such parties may include a merchant or processing bank (such as, e.g., a bank associated with the point of sale merchant), credit card company or association (such as, e.g., Visa, MasterCard, American Express, etc.), card issuer (e.g., bank issuing the credit card to the user). A transaction request initiated at point of sale device <NUM> may be transmitted with accompanying card and/or account information for processing to authorization network <NUM> for authorization of the transaction. A transaction request may be authorized, or rejected, or subject of other status, and the result may be transmitted back to POS device <NUM>.

Network <NUM> may include one or more of a wireless network, a wired network or any combination of wireless network and wired network, and may be configured to connect, for purposes of data communication, one or more devices in system <NUM>, including, for example, POS device <NUM>, mobile device <NUM>, server <NUM>, and/or authorization network <NUM> (as discussed above, some communications with POS device <NUM> may occur through server <NUM>). For example, network <NUM> may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a Global System for Mobile Communication, a Personal Communication Service, a Personal Area Network, Wireless Application Protocol, Multimedia Messaging Service, Enhanced Messaging Service, Short Message Service, Time Division Multiplexing based systems, Code Division Multiple Access based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE <NUM>. 11b, <NUM>. <NUM>, <NUM>. 11n and <NUM>, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi, and/or the like.

In addition, network <NUM> may include, without limitation, telephone lines, fiber optics, IEEE Ethernet <NUM>, a wide area network, a wireless personal area network, a LAN, or a global network such as the Internet. In addition, network <NUM> may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network <NUM> may further include one network, or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. Network <NUM> may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network <NUM> may translate to or from other protocols to one or more protocols of network devices. Although network <NUM> is depicted as a single network, it should be appreciated that according to one or more example embodiments, network <NUM> may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, corporate networks, such as credit card association networks, a LAN, and/or home networks.

Communication between devices may include any methods used for data communication over a network, including, for example, a text message, an e-mail, or other messaging techniques appropriate in a network-based configuration. Communication methods may include an actionable push notification with an application stored on mobile device <NUM>.

<FIG> is a diagram illustrating components of a point of sale (POS) device <NUM> used in a transaction control system according to one or more example embodiments. POS device <NUM> may be POS device <NUM> described above with reference to <FIG>. POS device <NUM> may include card reader <NUM>, visual display <NUM>, application <NUM> processor <NUM>, memory <NUM>, and communications interface <NUM>. It is understood that not all embodiments include every component shown in <FIG>. It is also understood that, while <FIG> depicts a single instance of each component, embodiments may contain multiple instances of any components.

Card reader <NUM> may be configured to read and authenticate an account-linked card, such as account-linked card <NUM>. Card reader <NUM> may include a card sensor to detect the presence of a card within the card reader. Card reader <NUM> may be in data communication with other components of POS device <NUM>, including processor <NUM>, memory <NUM>, and/or communications interface <NUM>.

Visual display <NUM> may include any type of device for presenting visual information such as a computer monitor, video monitor, a flat panel display, touch screen display, or a mobile device screen, and may include technology such as, for example, liquid crystal display, light-emitting diode (LED) display, plasma panel, and/or a cathode ray tube display technology.

Application <NUM> may include a software application or executable program code stored in memory <NUM> to be executed on processor <NUM>, and be configured to carry out features described herein for any of the POS devices described herein. Application <NUM> may be configured, for example, to transmit and/or receive data with other devices via communications interface <NUM> of POS device <NUM>. For example, application <NUM> may be configured to initiate or respond to one or more requests and/or to send or receive messages, such as requests or messages involving card <NUM> and/or mobile device <NUM>. Application <NUM> may also be configured to provide a user interface via visible display <NUM>. Further features carried out by application <NUM> are described below with reference to <FIG>.

Processor <NUM> may include one or more processing devices such as a microprocessor, RISC processor, ASIC, etc., and may include associated processing circuitry. Processor <NUM> may include, or be connected to, memory (such as memory <NUM>) storing executable instructions and/or data, as may be necessary or appropriate to control, operate or interface with the other features of POS device <NUM>, including application <NUM> or any other applications running on POS device <NUM>. Processor <NUM> (including any associated processing circuitry) may contain additional components including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein.

Memory <NUM> may include read-only memory, write-once read-multiple memory and/or read/write memory, e.g., RAM, ROM, and EEPROM, including any combination thereof. Memory <NUM> may store executable instructions and/or data, as may be necessary or appropriate to control, operate or interface with the other features of POS device <NUM>, including any applications running on POS device <NUM>.

Communications interface <NUM> may include wired or wireless data communication capability. These capabilities may support data communication with a wired or wireless communication network, including the Internet, a wide area network (WAN), a local area network (LAN), a wireless personal area network, a wide body area network, a cellular network, a telephone network, any other wired or wireless network for transmitting and receiving a data signal, or any combination thereof (including, e.g., a WiFi network). Communications interface <NUM> may support communication via a short-range wireless communication field, such as Bluetooth, NFC, or RFID, and may include a reader, such as a NFC reader. Communications interface <NUM> may be configured to communicate with mobile device <NUM> over a network and protocol common to both devices. Communications interface <NUM> may be configured to communicate with account-linked card <NUM> via contact pin of card <NUM> or via a short-range wireless communication field, such as Bluetooth, NFC, or RFID.

Communications between POS device <NUM> and other devices may be encrypted or decrypted using any suitable cryptographic method. In some embodiments, processor <NUM> may encrypt data (e.g., account data) prior to transmitting data to other devices, using any suitable cryptographic method.

POS device <NUM> may also include an input / output device (not shown), which may include any device for inputting information or data, such as, e.g., a key pad, keyboard, electronic pen, touch screen display, etc., and may also include output devices providing information or alerts. In some embodiments, the input / output device may be incorporated in whole or in part with visual display <NUM> (such as, e.g., a touch screen display).

<FIG> illustrates an account-linked card <NUM> used in a transaction processing control system according to one or more example embodiments. Account-linked card <NUM> may be a payment card, such as a credit card, debit card, or gift card, issued or activated by a service provider. Card <NUM> may be account-linked card <NUM> described above with reference to <FIG>. A service provider or card association name or identifier <NUM> may be displayed on the front or back of card <NUM>. In some embodiments, card <NUM> may be a contactless card. Card <NUM> may include a substrate <NUM>, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Card <NUM> may include identification information such as cardholder name <NUM> and/or account number <NUM> displayed on the front and/or back of the card; an expiration date may also be displayed on the front and/or back of the card. Card <NUM> may also include contact pad <NUM>. It is understood that not all embodiments include every feature shown in <FIG>.

<FIG> is a diagram illustrating components of an account linked card <NUM> used in a transaction processing control system according to one or more example embodiments. Account-linked card <NUM> may include some or all features described above with reference to <FIG>, and may include contact pad <NUM>, memory <NUM> and communications interface <NUM>. It is understood that not all embodiments include every component shown in <FIG>. It is also understood that, while <FIG> depicts a single instance of each component, embodiments may contain multiple instances of any components.

Contact pad <NUM> may be configured to establish contact with another communication device, such as POS device <NUM>, or a user device, smart phone, laptop, desktop, tablet computer, or any other device having an appropriate card reader. Contact pad <NUM> may include a pin to provide power (e.g., DC voltage) enabling electronic operation of other components (such as, e.g., memory <NUM> or communications interface <NUM>) of card <NUM>.

Memory <NUM> may include a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM. Memory <NUM> may be configured to store card data <NUM>, one or more applets <NUM>, and one or more tokens <NUM>.

Card data <NUM> may include data such as, e.g., account number, expiration date, and/or an identifier for the account holder or user for the specific account associated with a specific card <NUM>. Card data <NUM> would not include data relating to other accounts or cards.

Applet <NUM> may comprise one or more software applications configured to execute on a processor, such as a Java Card applet that may be executable on a contactless card. However, it is understood that applet <NUM> is not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory. Applet <NUM> may be configured to respond to one or more requests, such as near field data exchange requests from a client device, including requests from a device having a reader such as a mobile device NFC reader. Applet <NUM> may be configured to read (or write) data, including card data <NUM> and/or token <NUM>, from (or to) memory <NUM> and provide the data, in response to a request.

Token <NUM> may include a unique alphanumeric identifier assigned to a user of card <NUM>, and the identifier may distinguish the user of card <NUM> from other users. In some example embodiments, token <NUM> may include a key unique to the user or customer with which card <NUM> is associated. Token <NUM> may be used to verify the identity of the account holder or user associated with the card, or may be used to increase security through token authorization.

Communications interface <NUM> may support communication via a short-range wireless communication field, such as Bluetooth, NFC, or RFID. Card <NUM> may also include one or more antennas (not shown) connected to communications interface <NUM> to provide connectivity with a short-range wireless communications field.

Card <NUM> may include a processor (such as microprocessor, RISC processor, ASIC, etc.,) and/or processing circuitry for storing and processing information, an antenna and/or other components (not shown), any of which may be incorporated within or near contact pad <NUM>. Such processor may include, or be connected to, memory storing executable instructions and/or data, as may be necessary or appropriate to control, operate or interface with other components or features of system <NUM>.

Card <NUM> may also include a magnetic strip or tape, which may be located on the back of the card (not shown). The magnetic strip or tape may store card data, such as account number, expiration date, etc. for the account linked to the specific card, but would not store data for any other accounts.

In a non-claimed embodiment, account-linked card <NUM> may be a contactless card configured to communicate with POS device <NUM> via near field communication (NFC). In a non-claimed embodiment, card <NUM> may be configured to swipe in POS device <NUM>. In these and some other embodiments, card <NUM> may include a battery (not shown) contained within the card, such that the battery would provide power (e.g., DC voltage) when power is not supplied to card <NUM> via contact pad <NUM>, enabling electronic operation of components (such as, e.g., memory <NUM> or communications interface <NUM>) of card <NUM>.

In some embodiments, communications between account-linked card <NUM> and other devices may be may be encrypted or decrypted using any suitable cryptographic method. In some embodiments, data on card <NUM> (e.g., card data <NUM> and/or token <NUM>) may be stored in encrypted form, using any suitable cryptographic method.

<FIG> is a diagram illustrating components of a mobile device <NUM> used in a transaction processing control system according to one or more example embodiments. Mobile device <NUM> may be mobile device <NUM>, described above with reference to <FIG>. Mobile device <NUM> may include application <NUM>, processors <NUM>, memory <NUM>, and communications interface <NUM>. It is understood that not all embodiments include every component shown in <FIG>. It is also understood that, while <FIG> depicts a single instance of each component, embodiments may contain multiple instances of any components.

Application <NUM> may include a software application or executable program code stored in memory <NUM> to be executed on processor <NUM>, and be configured to carry out features described herein for any of the mobile devices described herein. Application <NUM> may be configured, for example, to transmit and/or receive data with other devices via communications interface <NUM> of mobile device <NUM>. For example, application <NUM> may be configured to initiate or respond to one or more requests and/or to send or receive messages, such as requests or messages involving POS device <NUM> and/or card <NUM>. Application <NUM> may also be configured to provide a user interface via a display (not shown) for a user of the mobile device. Further features carried out by application <NUM> are described below with reference to <FIG>.

In an example embodiment, application <NUM> may be launched in response to a tap action between card <NUM> and mobile device <NUM>. As used herein, a tap action may include tapping card <NUM> against a screen or other portion of mobile device <NUM> (or vice-versa). However, a tap action is not limited to a physical tap, and may include other gestures, such as, e.g., a wave or other movement of card <NUM> in the vicinity of mobile device <NUM> (or vice-versa).

Processor <NUM> may include one or more processing devices such as a microprocessor, RISC processor, ASIC, etc., and may include associated processing circuitry. Processor <NUM> may include, or be connected to, memory (such as memory <NUM>) storing executable instructions and/or data, as may be necessary or appropriate to control, operate or interface with the other features of mobile device <NUM>, including application <NUM>. Processor <NUM> (including any associated processing circuitry) may contain additional components including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein.

Memory <NUM> may include a read-only memory, write-once read-multiple memory and/or read/write memory, e.g., RAM, ROM, and EEPROM, and may store code comprising application <NUM>. Memory <NUM> may store data including account data for one or more additional accounts (such as other account-linked cards) associated with a user.

Communications interface <NUM> may include wired or wireless data communication capability. These capabilities may support data communication with a wired or wireless communication network, including the Internet, a wide area network (WAN), a local area network (LAN), a wireless personal area network, a wide body area network, a cellular network, a telephone network, any other wired or wireless network for transmitting and receiving a data signal, or any combination thereof (including, e.g., a WiFi network). Communications interface <NUM> may support communication via a short-range wireless communication field, such as Bluetooth, NFC, or RFID, and may include a reader, such as a NFC reader. Communications interface <NUM> may be configured to communicate with POS device <NUM> over a network and protocol common to both devices. Communications interface <NUM> may be configured to communicate with account-linked card <NUM> via a short-range wireless communication field, such as Bluetooth, NFC, or RFID.

Mobile device <NUM> may also include a display (not shown). Such display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, or a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.

Mobile device <NUM> may also include one or more device inputs (not shown). Such inputs may include any device for entering information into the mobile device that is available and supported by the mobile device <NUM>, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder, or camcorder. The device inputs may be used to enter information and interact with the mobile device <NUM> and, by extension, with the systems described herein.

Communications between mobile device <NUM> and other devices may be encrypted or decrypted using any suitable cryptographic method. In some embodiments, processor <NUM> may encrypt data (e.g., account data) prior to transmitting data to other devices, using any suitable cryptographic method. In some embodiments, account data stored in memory <NUM> may be stored in encrypted form, using any suitable cryptographic method.

<FIG> is a flowchart illustrating a method of transaction processing control <NUM> according to one or more example embodiments, with reference to components and features described above including but not limited to the figures and associated description. Transaction processing control method <NUM> may be carried out by POS device <NUM> (e.g., by application <NUM> executing on POS device <NUM>).

At block <NUM>, POS device <NUM> may receive (e.g., via a card reader such as card reader <NUM> described above in <FIG> for POS device <NUM>) first account data, the first account associated with a first card. First account data may include a first account number; first account data may include additional information relating to the first card, including expiration date, security code, or other account information. First account data may be stored on the first payment card. The first card may be inserted (or swiped, etc.) in POS device <NUM>. The first card may be account-linked card <NUM> and may be associated with a user; use of the first card may be related to a user transaction. The first card may be a payment card (such as, e.g., a credit card or debit card).

At block <NUM>, POS device <NUM> may transmit to a card authorization network (e.g., authorization network <NUM>) a first transaction authorization request. The first transaction authorization request may include first account data and a transaction amount.

At block <NUM>, POS device <NUM> may receive from the card authorization network (e.g., authorization network <NUM>) a transaction rejection notification in response to the first transaction authorization request. The rejection notification may indicate that the first card associated with the first account has been rejected, and/or that the transaction with the first account data is not authorized.

At block <NUM>, POS device <NUM> may transmit to the first card (e.g., card <NUM>) via a card reader (e.g., card reader <NUM> described above in <FIG> for POS device <NUM>) information regarding the transaction rejection. The transmitted transaction rejection information may include a request for information regarding a second account associated with the user. In an embodiment, POS device <NUM> may transmit the transaction rejection information to mobile device <NUM>.

At block <NUM>, POS device <NUM> may receive second account data associated with the user. The second account is not associated with the rejected first card. The second account may be associated with a second card (such as, e.g., a payment card). Second account data may include a second account number; second account data may include additional information relating to the second card, including expiration date, security code, or other account information. In some embodiments, second account data may be received (e.g., via a card reader such as card reader <NUM> described above in <FIG> for POS device <NUM>) from card <NUM>; card <NUM> may communicate with mobile device <NUM> to obtain the second account data. In some embodiments, POS device <NUM> may receive second account data directly from mobile device <NUM> rather than through card <NUM>.

At block <NUM>, POS device <NUM> may transmit to a card authorization network (e.g., authorization network <NUM>) a second transaction authorization request. The second transaction authorization request may include second account data and the transaction amount.

A response to the second transaction authorization request may be received from the card authorization network. The response may indicate approval or rejection of the second transaction authorization request.

If the second transaction authorization request is approved (e.g. the second account data is accepted and the transaction thereby authorized), the transaction may be completed. In some embodiments, POS device <NUM> may indicate, via a display on the POS device, that the transaction was authorized using the second account number.

If the second transaction authorization request is rejected (e.g. the second account data is rejected), the process outlined above for <FIG> may be repeated by requesting third account data and submitting a third transaction authorization request.

<FIG> is a flowchart illustrating a method of transaction processing control <NUM> according to one or more example embodiments, with reference to components and features described above including but not limited to the figures and associated description. Transaction processing control method <NUM> may be carried out by mobile device <NUM> (e.g., by application <NUM> executing on mobile device <NUM>). Application <NUM> may be activated (e.g., launched) by the user, or automatically, such as, for example, upon receipt of a card rejection notice or other notification from server <NUM>, or via detection of account-linked card <NUM> (e. g, entry of account-linked card <NUM> within a short-range wireless communication field, such as Bluetooth, NFC, or RFID).

At block <NUM>, mobile device <NUM> may receive information regarding a transaction rejection notification, including a request for second account data. The second account data may be associated with a second payment card. Second account data is not stored on the first payment card at the time the request for second account data is received.

At block <NUM>, mobile device <NUM> may determine parameters relating to selection of a second account for the transaction. Selection parameters may include one or more of card type (e.g., credit or debit); card issuer / card network (such as, e.g., Visa, MasterCard, or American Express); merchant; rewards program; product; card balance; transaction amount; available credit; etc. Selection parameters may include a list of cards or accounts ranked by the user. Parameters to be considered for a particular transaction may be based on the received transaction rejection information. For example, the first account, having been rejected, would be ineligible for selection as the second account. As another example, if the transaction rejection information indicates that the vendor does not accept American Express cards, selection parameters to be considered may include card issuer / card network. As another example, if the transaction rejection information indicates that the vendor does not accept credit cards, selection parameters to be considered may include may include card type. Other examples of transaction rejection information that may inform selection of the second account include insufficient credit, inactive card or account, or no rewards available.

At block <NUM>, mobile device <NUM> may identify eligible second accounts based on selection parameters. For example, if selection parameters include card issuer / card network but excluding American Express (because the vendor does not accept American Express), only available MasterCard or Visa card accounts may be eligible for the second account. As another example, if selection parameters include card type but excluding credit (because the vendor does not accept credit cards), only available debit card accounts may be eligible for the second account. As another example, only those accounts having available credit sufficient to cover the transaction amount may be eligible.

At block <NUM>, mobile device <NUM> may select a second account from eligible accounts based on selection parameters. For example, if one eligible account has a rewards program and other eligible accounts do not, the account with the rewards program may be selected as the second account. As another example, if one eligible account has a rewards program that prioritizes the particular merchant or product that is the subject of the transaction, that account may be selected, as the second account, over other eligible accounts that may only have a generic, non-prioritized rewards program. As another example, a second account may be selected from an eligible account having the lowest balance. As another example, a second account may be selected from an eligible account ranked higher than other eligible accounts by the user. In some embodiments, selection of a second account may be based on a list of eligible accounts without considering other selection parameters. In an embodiment, mobile device <NUM> may display a list of eligible accounts to the user and prompt the user to enter a selection.

At block <NUM>, mobile device <NUM> may transmit account data for the selected second account to card <NUM>. In an embodiment, mobile device <NUM> may transmit account data for the selected second account to POS device <NUM>.

The description of embodiments in this disclosure provides non-limiting representative examples referencing figures and numerals to particularly describe features and teachings of different aspects of the disclosure. The embodiments described should be recognized as capable of implementation separately, or in combination, with other embodiments from the description of the embodiments. A person of ordinary skill in the art reviewing the description of embodiments should be able to learn and understand the different described aspects of the disclosure. The description of embodiments should facilitate understanding of the disclosure to such an extent that other implementations, not specifically covered but within the knowledge of a person of skill in the art having read the description of embodiments, would be understood to be consistent with an application of the disclosure.

Throughout the specification and the claims, the following terms take at least the meanings explicitly associated herein, unless the context clearly dictates otherwise. The term "or" is intended to mean an inclusive "or. " Further, the terms "a," "an," and "the" are intended to mean one or more unless specified otherwise or clear from the context to be directed to a singular form.

In this description, numerous specific details have been set forth. It is to be understood, however, that implementations of the disclosed technology may be practiced without these specific details. References to "some examples," "other examples," "one example," "an example," "various examples," "one embodiment," "an embodiment," "some embodiments," "example embodiment," "various embodiments," "one implementation," "an implementation," "example implementation," "various implementations," "some implementations," etc., indicate that the implementation(s) of the disclosed technology so described may include a particular feature, structure, or characteristic, but not every implementation necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrases "in one example," "in one embodiment," or "in one implementation" does not necessarily refer to the same example, embodiment, or implementation, although it may.

As used herein, unless otherwise specified the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

While certain implementations of the disclosed technology have been described in connection with what is presently considered to be the most practical and various implementations, it is to be understood that the disclosed technology is not to be limited to the disclosed implementations, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claim 1:
A point of sale device (<NUM>, <NUM>), comprising:
a card reader (<NUM>) configured to read account information from an inserted card (<NUM>), wherein the inserted card (<NUM>) includes a contact pad (<NUM>) that is configured to communicate with the card reader (<NUM>), the account information including a first account number that is stored on the inserted card;
a communications interface (<NUM>) that is configured for data communication with an authorization network (<NUM>); and
a processor (<NUM>) connected to the card reader (<NUM>) and the communications interface (<NUM>), the processor (<NUM>) configured to:
receive (<NUM>) the account information from the inserted card via the card reader;
communicate (<NUM>) the first account number via the authorization network to determine whether a transaction associated with the inserted card is authorized;
receive (<NUM>) an authorization response, the authorization response including a rejection notification if the transaction is not authorized;
transmit (<NUM>) the rejection notification to a mobile device via the card reader and inserted card in a manner that enables the inserted card to transmit the rejection notification to the mobile device via a wireless connection, wherein the wireless connection uses a short-range wireless communications field;
wherein the inserted card (<NUM>) includes a wireless interface that is configured to communicate with the mobile device via the wireless connection;
receive (<NUM>) a second account number that is stored on the mobile device via the wireless connection to the inserted card and the card reader; and
communicate (<NUM>) the second account number via the authorization network to determine whether the transaction associated with the second account number is authorized.