WO2016132314A1 - Remotely configurable plastic card - Google Patents

Remotely configurable plastic card Download PDF

Info

Publication number
WO2016132314A1
WO2016132314A1 PCT/IB2016/050873 IB2016050873W WO2016132314A1 WO 2016132314 A1 WO2016132314 A1 WO 2016132314A1 IB 2016050873 W IB2016050873 W IB 2016050873W WO 2016132314 A1 WO2016132314 A1 WO 2016132314A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
user
configuration
system server
software
Prior art date
Application number
PCT/IB2016/050873
Other languages
French (fr)
Inventor
Yehuda YARIV
Original Assignee
Syncopa Labs Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Syncopa Labs Ltd. filed Critical Syncopa Labs Ltd.
Publication of WO2016132314A1 publication Critical patent/WO2016132314A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06KGRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/067Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
    • G06K19/07Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
    • G06K19/0701Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips at least one of the integrated circuit chips comprising an arrangement for power management
    • G06K19/0702Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips at least one of the integrated circuit chips comprising an arrangement for power management the arrangement including a battery
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06KGRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/06187Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with magnetically detectable marking
    • G06K19/06206Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with magnetically detectable marking the magnetic marking being emulated
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06KGRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/067Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
    • G06K19/07Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
    • G06K19/0723Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips the record carrier comprising an arrangement for non-contact communication, e.g. wireless communication circuits on transponder cards, non-contact smart cards or RFIDs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/355Personalisation of cards for use
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/355Personalisation of cards for use
    • G06Q20/3552Downloading or loading of personalisation data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/357Cards having a plurality of specified features
    • G06Q20/3576Multiple memory zones on card

Definitions

  • the invention relates to the replacement of plastic cards that implement Magnetic Stripe, Smart-card, RFID or Near Field Communications (NFC), by a new system that includes a new multi-purpose electronic card, and ways to automatically select its configurations.
  • plastic cards that implement Magnetic Stripe, Smart-card, RFID or Near Field Communications (NFC)
  • NFC Near Field Communications
  • Magnetic-Stripe Cards were invented by IBM in 1967, rolled out in the early 70 's, and globally accepted during the 80's. In 2011 alone, 6 billion bank cards around the world, along with transit tickets and other magnetic-stripe media, went through card readers some 50 billion times.
  • plastic cards are so popular, that most people have in their possession between 5 and 15 different cards. Cards can be credit, loyalty, rewards, membership, health, etc. The average number of only credit cards per person in the US is 3.75. Most of them are simple magnetic-stripe cards. The large number of cards in the wallet is due to the limited functionality of the existing cards. These kinds of limitations impose limitations also on the services that a card issuer can offer. For example - a credit card issuer cannot offer a service to open hotel rooms, although both credit card and hotel room- locks use similar cards. Credit cards, in particular, have also become a symbol of status. People are ready to pay extra for a Platinum card, many times due to the possibility to show this to friends.
  • Smart Card Technology emerged during the mid-1980s.
  • a smart card includes a small processor chip embedded within the plastic card, which enables some additional features like security (adding a Personal Identification Number (PIN) to the card) and tracking of card's activity.
  • PIN Personal Identification Number
  • the cards usually cannot be re-programmed by the user or serve any purpose other than what it was originally issued for. For example - a credit card is programmed by a card issuer and can only serve the purpose of a credit card.
  • a hotel room key card is programmed by the hotel receptionist during check-in and can only be used for opening the hotel's room.
  • Smartphones are becoming the focal point of our lives. We use them not only for communicating with other people, but play games, listen to music, read the news, watch movies, use it for work, navigate and much more.
  • Mobile wallets as ones installed on smartphones, are considered as a solution to the emerging need of using less plastic cards.
  • Some are related to technology, some business and some are related to user's behavior. Among them: Requires huge world-wide investment: Existing infrastructure of readers, applications and backbone is required to be upgraded to support NFC (Near Field Communication) and mobile wallets.
  • NFC Near Field Communication
  • a system for managing multiple services using a single multipurpose card comprising: at least one Service Provider configured to provide a card-implemented service; a System Server comprising a database comprising data pertaining to the at least one service provider and to at least one user; at least one configurable user's card; and at least one user electronic communication device running software configured to select a current configuration for the at least one user's card, the user's card communicating bi- directionally with the software; the system server communicating bi-directionally with the at least one Service Provider and with the at least one user electronic
  • the at least one Service Provider may comprise at least one of store, hotel, train station, security system, payment system and loyalty program.
  • the software may comprise: a system application configured to: receive signals from the user's card; transfer card identification data to the system server; receive data comprising encrypted card configuration from the System Server; send encrypted card configurations to the user's card; receive user data comprising user location; and send the user data to the system server; and a user application configured to: provide GUI for receiving user inputs and for selecting a configuration; and send user data comprising manual card configuration selection and user location to the system application.
  • the software may be configured to receive a signal comprising a card number from the user's card when taken out of pocket and to select appropriate user's card configuration according to user location and system data.
  • the user's card may comprise a light sensor; electronic components and a board.
  • the electronic components may comprise BLE (Bluetooth Low Energy) interface.
  • the board may be laid out at the upper part of the user's card and may be configured to be embedded in a standard card comprising at least one of: magnetic-stripe emulation; battery and NFC chip.
  • the battery may be configured to be charged by at least one of light, piezoelectric cells and RF signals from NFC (Near Field Communication) source.
  • NFC Near Field Communication
  • the user's card may comprise a memory configured to store various configurations.
  • the memory may comprise at least one security zone configured to store non- volatile and volatile information.
  • a method for automatic configuration of the card comprising: taking the card out of a pocket; sending a signal by the card to an electronic communication device; recognizing the card by a software installed on the electronic communication device; sending by the software to a system server at least one of a card number and an account unique ID; sending by the software to a system server current location; calculating by the system server a most appropriate card configuration; sending by the system server the most appropriate card configuration to the software; sending by the software the most appropriate card configuration to the card; and using the most appropriate card configuration.
  • a method for automatic configuration of the card comprising: continuously sending by a software installed on an electronic communication device one or more of a card number and an account unique ID; continuously sending by the software installed on the electronic communication device current location to the system server ; receiving by the system server the sent one or more of card number and account unique ID and the current location calculating by the system server a card configuration number based on the user location; sending by the system server the card configuration number to the software; and storing by the software the card configuration number.
  • the method may further comprise: sensing the card being taken out of pocket; sending a signal comprising the card number by the card to the software; recognizing the card by the software; sending by the software the stored card configuration number to the card; and using a configuration according to the stored card configuration number by the card.
  • Fig. 1 illustrates the present invention's system
  • Fig. 2 is a flowchart illustrating an example of usage of the system server
  • Fig. 3 illustrates an example of records stored at the server
  • Fig. 4 illustrates an example of the information transferred through the mobile device from the System Server to the card ;
  • Fig. 5 illustrates card's configurations
  • Fig. 6 illustrates system's card schematics
  • Fig. 7 illustrates system's card structure
  • Fig. 8 illustrates embedded system in a card
  • Fig. 9 shows a possible arrangement of memory inside the card
  • Fig. 10 illustrates EMV configuration selection
  • Fig. 11 illustrates EMV enable/disable by the system application
  • Fig. 12 is a flowchart illustrating the process of selecting card configuration by the system server.
  • Fig. 13 illustrates the configuration selection sequence performed by the system server
  • Fig. 14 is a flowchart illustrating the process of selecting card configuration by the system application.
  • Fig. 15 illustrates the configuration selection sequence performed by the system application
  • Fig. 16 is an example of WiFi signals measured inside store B
  • Fig. 17 is an example of the table that is stored on the server, following users purchases at a certain location
  • Fig. 18 shows an example for the measured value of certain parameter
  • Fig. 19 is a table illustrating the scores sent and presented to the user regarding his location in a certain store.
  • the present invention relates to the replacement of plastic cards that implement Magnetic Stripe, Smart-card, RFID or Near Field Communications (NFC) technologies, by a new system that includes a new multi-purpose electronic card that emulates prior art cards' functionality by electronics means.
  • the new card is connected via Bluetooth or other wireless connection to a mobile communication device such as a smartphone or other device such as computer, note-pad or any other device.
  • the mobile device connects the new card to the Internet and to a system server.
  • a server preferably a service provider's server can update data on the card and control it, via the system server and the mobile communication device, so that the new card according to the present invention is fully controlled and configurable by the service provider.
  • the new electronic card can be read by existing magnetic readers of e.g. chip card, RFID and NFC infrastructure.
  • the new card can be used in stores, hotels, train stations, security systems, payment systems, loyalty programs, etc. and utilize smartphone's and network capabilities for selecting configurations, updating data and serving multiple applications.
  • the invention relates to applications like credit/debit card payment, opening a hotel room, train and metro cards, gift cards, loyalty cards and any other application which requires the use of a plastic electronic card. All these applications can be consolidated into a single electronic card, connected to a smartphone via Bluetooth, and controlled by the smartphone and the server over the Internet.
  • the system server runs an application to automatically select the appropriate configuration of the card so that the user has no need to manually select a card configuration.
  • the user can select manually which configuration to use in any particular case, for example, a transportation card when the user is at a train station or a particular credit card when the user is at a store.
  • a service provider can build a database for providing various capabilities to users, for example using the location service of the smartphone (e.g. GPS, Wi-Fi) to provide indoor navigation service (in places like shopping malls, train stations, airport terminals, hotels, etc.); thus, the card is automatically configurated (according to the data stored at server) when approaching these points of interest .
  • the location service of the smartphone e.g. GPS, Wi-Fi
  • indoor navigation service in places like shopping malls, train stations, airport terminals, hotels, etc.
  • Service providers can utilize the system for providing enhanced loyalty programs for users and for small businesses like grocery shops and other stores.
  • the invention's technology enables multiple configurations and applications within a single card, links physical cards to mobile applications and provides interface for multiple services to configure the application and card.
  • the system does not require a physical card at all, only a mobile device.
  • This system functions the same as physical card based systems when appropriate mobile devices readers are available at service points of interest (e.g. NFC).
  • the System 100 (Fig. 1) disclosed in the present invention includes a System Server 110, at least one User 120 and at least one Service provider 130.
  • the Service provider 130 (may be a card provider or other service provider) communicates bi directionally with the System Server 110.
  • the System Server 110 comprises a database (not shown).
  • User 120 comprises two components:
  • Multipurpose "Plastic Card” (Card) 140.
  • a field programmable plastic card which can carry not only credit card information, but other programmable services as well. It emulates the magnetic-stripe and/or chip of existing cards and can be read by existing card readers, chip-and-pin readers, RFID and NFC infrastructure readers.
  • the Card includes Bluetooth Low Energy (LE) or Near Field Communication (NFC) technology to connect the card to a mobile device.
  • LE Bluetooth Low Energy
  • NFC Near Field Communication
  • Mobile device 150 a smartphone or other mobile communication device which comprises a System application 160, Application Programming Interface (API) 170 and at least one User application 180.
  • the User application 180 provides a GUI (graphical User Interface), which can be used for manual configuration selection and it communicates bi-directionally with API 170.
  • API 170 communicates bi directionally with System application 160.
  • API 170 is used for multiple services and applications, so that the same Card 140 can be used as credit, loyalty, access to hotel rooms, mass-transit systems, security badges and much more.
  • the API 170 runs on user's smartphone or other mobile communication device.
  • the API 170 enables the Service Provider 130 to provide his own user application 180 to the User 120 and to use the Mobile device 150 features such as security, location, graphical user interface and others.
  • System Server 110 receives from the user's smartphone 150 data relating to user's location, Card 140 configuration selections and preferences, in real time. It understands the behavior of users and can automatically select the best configuration to use for any particular case and service through System application 160.
  • the System Server 110 is located at the Service Provider 130 or elsewhere in the cloud.
  • the System Server 110 controls and manages the Card 140 through the system application 160, provides end-to-end security, gathers statistics and performs location algorithms so that all information that is transmitted from the Service Provider 130 to the card is current, managed and secured.
  • the Service Provider 130 can communicate with many system cards via a single system server.
  • the System Server 110 can store and manage information and communicate it with the Mobile device System application 160 to be converted into magnetic stripe, smart card chip or RFID.
  • System server
  • the system server is located at the provider's facilities or as a service in the cloud. Its purpose is to store and manage the information of all users' system cards and transfer it safely and securely to the cards when required.
  • the system server also performs off-line activities, such as mapping locations of merchants (some may function also as card providers) and following users' behavior.
  • the system server stores a database of merchants, locations and other information, which is entered by users and businesses to provide information required for smart and automatic card-selection.
  • the system server 110 runs computer software that provides the following services to the service provider: 1. Interface between the service provider and the user
  • the system server is the interface between the system application 160 and the service provider.
  • the server interfaces with the service provider program which creates the codes for opening the rooms.
  • Data can be entered to the system server manually through GUI, like web interface, by means of data base sharing or by providing an API to other applications.
  • Fig. 2 depicts an exemplary scenario of hotel key issuing:
  • the user books a hotel room via any mean 200.
  • the hotel issues a room key using the software provided by the vendor of the room locks or the hotel's system 210.
  • the vendor's or hotel's software installed at the hotel's computers, sends the key code to the system server 220.
  • User's card is updated by the system application 160 with the key code.
  • the user can use his card as a hotel key 240.
  • the system server maintains all the information that is stored in all cards. For example, if a card contains credit card information, and the service provider wishes to add information to the card, such as additional credit card number, the new information is added to the appropriate record at the system server and transferred securely to the appropriate card.
  • Fig. 3 shows an example of records 300 stored at the system server, plurality of users records who hold several membership programs (credit card, health card, loyalty card, etc.).
  • the system server depicted in Fig. 3, updates the card data of each user 320 via the internet cloud 310. 3. Convert users data to system
  • the card data is encrypted in ways which prevent any form of copying or altering the card, since it comprises also sensitive data, such as card number. No meaningful data is stored on the mobile device even though the mobile device relays the encrypted data from the system server to the Card.
  • - hotel key information which includes the room number and date and time of expiration
  • the encrypted information is sent to the user's mobile device, and is stored encrypted until it is downloaded to the card. This is the information that will be used by the magnetic-stripe emulator to open the door.
  • Additional information is also sent by the server to the mobile device, which includes, for example, the location of the hotel, expected dates of use, and any additional information that helps the mobile device determine which configuration should be available when the user approaches the hotel room.
  • the additional information may also include which security measures are required in order to enable the specific configuration. Such security measures may be a PIN code, fingerprints or any other security information that is available by the mobile device.
  • Fig. 4 there is an example of the information encrypted and transferred through the mobile device 420 from the System Server 400 to the card 440.
  • the information converted to system application data is for example, security level, hotel name and hotel location, which helps the system application select the appropriate card configuration.
  • the card data encrypted on the card is for example room number, checkout date and checkout time.
  • the card data is sent from the system server 400 through the mobile device 420 to the card 440.
  • the card sends a signal comprising the card number to the system application installed on the mobile device 420.
  • the system application sends the system server 400 the current location and card number.
  • the system server 400 calculates the most appropriate card configuration number and sends it to the system application.
  • the system application sends the most appropriate card configuration number to the card 440, which selects the appropriate card configuration. Finally, the card 440 is ready for use.
  • the system should know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a known location or another.
  • the system server is aware of a merchant B for the first time, located near a GPS location XXXYYY, with the recorded parameters of cellular, WiFi and others (given by the user's mobile device via user application or the merchant itself via the system server). The next user to make a purchase at the same store will already have the appropriate database information available, and the server will be able to select automatically the appropriate configuration.
  • Such auto-selection can be done based on various parameters: Location
  • a straight forward example may be: when a user makes a purchase at store A (for example -"Target”) the system server will automatically select the credit card associated with store A, and when the user makes a purchase at store B (for example "Walmart") then that system server will automatically select the credit card that is associated with store B, assuming that the user has both configurations available within the card configurations. No user intervention is required.
  • the system server uses algorithms to select the best suitable configuration, based not only on location, but also on date and time, currency conversion and other information that is available at the time of purchase or other use of the card.
  • the system server maintains user's preferences and combines them with the best configuration selection as described above.
  • the outcome is a score for each
  • the system server has means to input data from users or businesses regarding discounts and advantages to certain loyalty clubs. This information is transmitted to all relevant users' system applications and taken into account when paying at the business.
  • a user visits a certain gas station and notices a 10c discount per gallon for users of a certain loyalty club.
  • the user can publish this information on the system server and once other users are near that gas station their card will automatically select the preferred loyalty club, if it is available among their configurations.
  • a key factor of the system's acceptance by the market is its ability to generate revenues to its customers (service providers).
  • Service providers may have different revenue models. For example a credit card issuer may charge the other providers for any added record to a card, or charge the user per use of the card itself for anything that is not credit card.
  • the system server is able to provide information on use of the card, added records and any other information that may be relevant for the provider.
  • system server can also be owned by 3 rd parties who provide access to the system server for a fee or for another incentive.
  • a credit card issuer who owns a system server can provide access to 3 r parties who wish to provide other services, as described above.
  • API Application Programming Interface
  • a card may be attached to a single system server only or receive information from various system servers.
  • the system application runs on a mobile communication device (for e.g., smartphone or tablet) and includes the following tasks:
  • o Enable mobile device's security features when required, like PIN code or fingerprints.
  • GUI graphical user interface
  • sounds o Provide user's history.
  • Each use of the card can be related to a location, time, etc. and stored,
  • the system's application also provides an API for 3 rd parties to create their own user applications. Card's configuration selection
  • the system application is responsible for selecting the appropriate configuration on the card for the next transaction.
  • the card configuration can be selected manually by the user, via the GUI (of user application), or automatically by the system application, based on information from the system server, location, Wifi signals strength, cellular cell information or other beacon signals.
  • Manual configuration is selected via the GUI, which shows all the available configurations that are stored in the card.
  • the configurations include graphic presentation of the available configurations, similar to the ones illustrated in Fig. 5.
  • the system server may know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located at this moment. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a known location or another.
  • This information is sent to the system server by the system application.
  • the system server matches the information with payment information of that user, including stores name, and stores the information in a table that describes the stores name, location and the other available information.
  • the system server also records the user's decision on which card to use, in case the user manually selected a configuration. For example, if the user selected a certain credit card at that location, then the card data (type, vendor, loyalty, etc.) is stored and ranked for the future users.
  • This database is used for matching the best configuration per user, location and time, and also for actions like targeted advertising and statistics.
  • the system's card The System's Card 500 is a field programmable plastic card or module that can be integrated into a plastic card, which can be programmed in real-time from the cloud via user's mobile device.
  • the card comprises a BLE (Bluetooth Low Energy) interface 510, a controller 520 which translates the data and interfaces it to the appropriate card interface, a rechargeable energy harvesting system 530 (with loading means, such as a piezoelectric sensor 580) and various card interfaces - magnetic stripe 540, EMV chip 550, NFC contactless chip 560 and a light sensor 570 .
  • BLE Bluetooth Low Energy
  • controller 520 which translates the data and interfaces it to the appropriate card interface
  • a rechargeable energy harvesting system 530 with loading means, such as a piezoelectric sensor 580
  • various card interfaces - magnetic stripe 540 EMV chip 550, NFC contactless chip 560 and a light sensor 570 .
  • the light sensor 570 senses that it is out of the user's wallet and communicates wirelessly with the mobile device via BLE interface 510.
  • the card then receives from the system application the configuration for the next transaction and saves it until actual use at the Card reader, probably a few seconds later.
  • This configuration is the actual data or configuration to be used for the magnetic stripe 540, EMV chip 550 or contactless interface 560 of the card.
  • the multipurpose card of the present invention is implemented in a card module 710, designed so that it would be easy to integrate with standard credit cards 600 comprising EMV Chip 610.
  • the card module 710 comprises elctronic components 630 such as BLE and memory, Magnetic- Stripe emulation 620, Battery 640 and NFC Chip 650, laid out as a module located at the upper part of the card, so that it would be possible to embed it in a standard card during manufacturing.
  • elctronic components 630 such as BLE and memory, Magnetic- Stripe emulation 620, Battery 640 and NFC Chip 650, laid out as a module located at the upper part of the card, so that it would be possible to embed it in a standard card during manufacturing.
  • the card looks and feels exactly like a standard plastic magnetic-stripe card such as credit card.
  • the card communicates with an attached mobile device to receive its configurations, security messages and other data that is required for its operation.
  • the card uses standard BLE which is now available in most mobile devices and can communicate at up to 10 meters range, using extremely low energy.
  • a special encrypted communication protocol is used to eliminate any possibility of eavesdropping and/or theft of card's information.
  • the card contains memory which stores the various configurations and contains several "security zones", to enable non-volatile and volatile information to be stored. This is used to disable any access to the service provider data from the mobile device or from anywhere else. For example - credit cards data, which is secured and secret information, cannot be accessed from outside the card, except when the card is accessed by a card reader and the card is in the proximity of the Mobile device.
  • Fig. 9 shows an exemplary arrangement of memory inside the card. At the non-volatile memory are stored three credit card numbers, with different levels of security, defined by the number on the right of each record.
  • Level ' 1 ' means that proximity to mobile device is required.
  • Level '2' means that the user must enter a PIN code or fingerprints.
  • These levels can define, for example, which credit card number to use for different maximum expense levels that are allowed for each selected card.
  • the information on the non-volatile memory cannot be changed or manipulated by the System Server.
  • the volatile memory includes the records which are provided by the system server. These records are changeable. The amount of non-volatile and volatile memory, type of information and other data can be set by the service provider during initial programming of the card.
  • the system server converts the records stored in its memory to magnetic stripe, smart chip, RFID or Near Field Communication (NFC) encoded data.
  • NFC Near Field Communication
  • Selection of record is done by the mobile device, as described above, in accordance with the specific situation, location, type of reader and other information from the server.
  • the mobile device transmits to the card an instruction via system application to use record number 3, which is a credit card number with security level '2'.
  • the system module 710 always includes the magnetic stripe and NFC interfaces, which are completely flexible and configurable by the system.
  • the EMV chip is optional, and may support various configurations:
  • FIG. 10 illustrates the configuration selection transmitted from the system server A to the EMV chip E through the system application installed on mobile device B.
  • the selection of configuration by the system server A is done based on user's location, requirements and other parameters that may be used to select which credit card to use.
  • C is the card and D is the communication mean to the mobile device B (such as BLE).
  • Fig. 11 is an illustration of the enable/disable function of the EMV chip by the system application.
  • the EMV chip I is pre-loaded with the credit information credentials, same as today, and the system application installed on the mobile device F enables or disables the chip I.
  • G is the card and H is the communication mean to the mobile device F (such as BLE).
  • system server is used as a means for extra security of the EMV chip.
  • security capabilities for example, when the card is in proximity to the Mobile device then the EMV chip is enabled, and when the card is separated from the Mobile device then the EMV chip is disabled, thus the credit card is disabled.
  • system module 710 is used for anything that is not EMV compliant credit card.
  • the credit card is just the same as today, and the system is used for applications that require the magnetic stripe or NFC, though on the same card.
  • the card in order to preserve battery life the card is configured not to consume any power while it is inside user's wallet or pocket. It is assumed that while in the pocket or wallet, the card is in complete darkness, and therefore a light sensor can be used to determine if the card is out.
  • a light sensor is CPC 1822 from IXYS or similar.
  • the sensor should be sensitive enough so that even in minimal light conditions it will be able to determine that the card has been taken out of the pocket. As soon as the card is out of the pocket it may be turned on and initiate communication with the mobile device. Once paired, the first message is a "good-morning" message, which indicates to the mobile device that the card is out and ready for accepting data.
  • the card When the card is put back in the pocket it transmits to the mobile device a "good-night” message. If the card has sent a "good-morning" message, but is not responding within a given timeout, and a "good-night” message was not received yet, then the user will receive a warning message on his mobile device, with an indication of card is not seen or is out of range. Recharging the battery
  • the card When required to operate, the card is powered by a rechargeable flat battery. It is assumed that the card is used between two to five times per day, for a few seconds, while at all other times the card is idle.
  • the battery may be of a solid-state type, with "energy harvesting” capabilities. For example, “Enerchip” from Cymbet or “Thinergy” from Infinite Power Solutions.
  • the light and piezoelectric cells and NFC chip are the sources of energy for recharging the battery, and also the sensors that provide information about the card being out of the pocket or wallet.
  • the battery is able to power the Card for at least 4 years.
  • the system includes a system server, a user (comprising a card and a mobile device), and a service provider.
  • the service provider may install a system server and set-up users' accounts.
  • the users' accounts include a unique ID per user, which is in reference to the user's SIM card number, telephone number, ID number or a unique system card number.
  • Users may install the user application on their mobile device and pair the card with it. Once the card is paired users are able to input their data.
  • users can type in or scan the credit card numbers and other information they would like to include with the card. Users can also select their preferences and profile of usage of the card. For example - use of particular cards in a particular store, use cards in accordance with dates, time of day, location, etc.
  • the system application is constantly updating the system server regarding the current location in order to receive the most appropriate and up to date card configuration or card configuration number.
  • the process is as follows:
  • the system application sends the message
  • the system server receives the message
  • the system application receives the message "Use Configuration #5" or the message comprising the most appropriate configuration from the system server.
  • Mode #1 - Server selects configuration (fast communication)
  • a sequence of operations happens (Fig. 12, Fig. 13): At t 0 , the card senses that it has been taken out of the pocket and prepares itself for use. The card announces itself by sending a Bluetooth discover message to the system application installed on the mobile device. Once the system application recognizes the card, the card sends "GoodMorning+#CardNumber" to the system application through the Bluetooth interface 800.
  • the system application receives the GOOD MORNING message from the card, compares it to the card number that is stored locally and sends information to the system server.
  • the information contains the card number, a unique ID for the account and information regarding the current location 810.
  • Fig. 12 and 13 relate to the case where the configuration has already been downloaded to the card and only the configuration number to be used is sent.
  • the actual configuration (record) may be sent.
  • the system server sends the configuration number to the system application.
  • This message (“Use Configuration #5") may be encrypted 830.
  • the system application sends the selected configuration number to the card.
  • the mesasage may be encrypted, and no meaningful data is stored at the mobile device 840.
  • the card acknowledges the configuration ("Ack+#CardNumber"), decrypts the message and uses the appropriate configuration from the existing stored set of configurations 850.
  • the card After the card was used at the card reader, or when put back in the pocket or after a configurable time-out, the card sends a "Goodnight+#CardNumber" message to the system application 860. In mode# 1 ts-to ⁇ 3 sec, since this is the minimal time of taking the card out of the pocket, otherwise the card may not be ready to be used.
  • This mode can be used when network communication is constantly available and at good bandwidth and low delay, so that the system application is constantly updated with the required configuration for the card.
  • Mode #2 Application selects configuration (slow communication)
  • the card sends the message "GoodMorning+#CardNumber" to the system application 900.
  • the system application receives the message "GoodMorning+#CardNumber” and if communication with the server fails, sends the last selected configuration ("Use Configuration #5") to the card 910.
  • the selected configuration is encrypted, and no meaningful data is stored at the mobile device.
  • the card acknowledges the configuration ("Ack+#CardNumber"), decrypts the message and uses the appropriate configuration, from the existing stored set of configurations for the next transaction 920. After the card was used at the card reader, or when put back in the pocket or after a configurable time-out, the card sends a "Goodnight+#CardNumber" message to the system application 930.
  • the system server may know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located at this moment. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a location that is known to the server or not.
  • the System Application records data regarding the reception of various signals that are available for the mobile device at the moment of payment or close to it.
  • This information includes:
  • GPS information including location, time and current availability. If GPS signal is not available then the system server assumes that the user is indoors.
  • WiFi Access-Points names any available WiFi information like WiFi Access-Points names, signal strength, MAC addresses and channels (available in Android, Windows).
  • Cellular cells information including Cell ID (CID), UTRAN Cell ID (LCID) and signal strength.
  • CID Cell ID
  • LCID UTRAN Cell ID
  • signal strength signal strength
  • Fig. 16 shows an example of measured signals in a particular location, near or inside store B.
  • a few WiFi Access Points (1-3) are available and their signals are shown in a graph that describes their names, MAC addresses, channels and signal strength at that particular location.
  • This information is sent to the system server, together with the unique user ID and time of recording.
  • the system server matches the information with previous usage payment information of that user, such as what card configuration was used in this measured environment, and compares it also to other users' selected configurations for their cards in this particular measured environment.
  • the server stores the information in a table that describes the store name, if available, location and any other available information.
  • the server also records the user's decision on what card to use. For example, if the user selected a certain credit card at that location, then the card data (type, vendor, loyalty, etc.) is stored and ranked.
  • Fig. 17 is an example of a table stored on the system server, following users' purchases at a certain location.
  • the table in Fig. 17 refers to Users who paid at a Sheraton hotel in Manhattan.
  • Database is built on the fly, based on users selecting cards and configurations manually, until the system server recognizes the various parameters that existed at the time of purchase. These parameters are saved and compared every time any user makes a purchase or other card transaction. So, for example, when a user makes a payment at Sheraton in Manhattan, in the example above, the card transmits to the mobile device the moment of transaction. Measurements are taken at that moment, recorded by the mobile device, and transmitted back to the system server.
  • the system server is aware of "SHTN_5462”, located near a GPS location "Latitude : 40.725402
  • the system server integrates this data with the data that already exists on the server, by calculating means and variances of locations and measurements. For example:
  • a standard score ('Z' value) is calculated for each parameter, indicating the chance of a user to be within the vicinity of the parameter.
  • the system server created a 'z-value' graph of possible measurements for a certain parameter, say 'Latitude'.
  • a user sent a currently measured data, which is close, but not exactly the same data as the mean that was calculated for all previous users. This means that as far as this particular parameter goes there is a e.g. 25% chance that the user is in the same location as previous users. Let us define this location as "previously known location”. See example in Fig. 18.
  • the same calculation is done for additional locations in the vicinity of that location.
  • the calculated scores may be smaller, higher or the same.
  • the scores are then sent to the system application and can be presented to the user in a declining list based on the scores (Fig 19) so he can choose manually the card configuration.
  • Manual configuration is usually made when user location is uncertain.
  • the system assumes that the user is at the particular previously known location, and selects the card's configuration automatically.

Abstract

A system for managing multiple services using a single multipurpose card, comprising: at least one Service Provider configured to provide a card-implemented service; a System Server comprising a database comprising data pertaining to the at least one service provider and to at least one user; at least one configurable user's card; and at least one user electronic communication device running software configured to select a current configuration for the at least one user's card, the user's card communicating bi- directionally with the software; the system server communicating bi-directionally with the at least one Service Provider and with the at least one user electronic communication device.

Description

REMOTELY CONFIGURABLE PLASTIC CARD
TECHNOLOGY FIELD
The invention relates to the replacement of plastic cards that implement Magnetic Stripe, Smart-card, RFID or Near Field Communications (NFC), by a new system that includes a new multi-purpose electronic card, and ways to automatically select its configurations.
BACKGROUND
Magnetic-Stripe Cards were invented by IBM in 1967, rolled out in the early 70 's, and globally accepted during the 80's. In 2011 alone, 6 billion bank cards around the world, along with transit tickets and other magnetic-stripe media, went through card readers some 50 billion times.
60 years of plastic cards have established not only a huge infrastructure and related industries, but also marketing channels, used for advertising and branding, and even human behaviors that are related to the use of cards. No wonder that "VISA",
"MasterCard" and "American Express" are ranked among the most valuable global brands in 2015 (5th, 20th and 25th respectively). Much of it thanks to the fact that their cards and logos are in everyone's hands a few times every day.
The use of plastic cards is so popular, that most people have in their possession between 5 and 15 different cards. Cards can be credit, loyalty, rewards, membership, health, etc. The average number of only credit cards per person in the US is 3.75. Most of them are simple magnetic-stripe cards. The large number of cards in the wallet is due to the limited functionality of the existing cards. These kinds of limitations impose limitations also on the services that a card issuer can offer. For example - a credit card issuer cannot offer a service to open hotel rooms, although both credit card and hotel room- locks use similar cards. Credit cards, in particular, have also become a symbol of status. People are ready to pay extra for a Platinum card, many times due to the possibility to show this to friends. It seems that it would be hard for the credit issuers to give up such differentiation between cards. "Smart Card" Technology emerged during the mid-1980s. A smart card includes a small processor chip embedded within the plastic card, which enables some additional features like security (adding a Personal Identification Number (PIN) to the card) and tracking of card's activity. The newer technologies like Smart Card, RFID and NFC technologies, although add security and convenience, did not change the basic concept of the old magnetic-stripe card, which is programmed once by a provider, and read again and again by readers. The cards usually cannot be re-programmed by the user or serve any purpose other than what it was originally issued for. For example - a credit card is programmed by a card issuer and can only serve the purpose of a credit card. A hotel room key card is programmed by the hotel receptionist during check-in and can only be used for opening the hotel's room.
Smartphones are becoming the focal point of our lives. We use them not only for communicating with other people, but play games, listen to music, read the news, watch movies, use it for work, navigate and much more.
Mobile wallets, as ones installed on smartphones, are considered as a solution to the emerging need of using less plastic cards. However, there are still many issues that prevent mobile wallets from becoming the mainstream of payment. Some are related to technology, some business and some are related to user's behavior. Among them: Requires huge world-wide investment: Existing infrastructure of readers, applications and backbone is required to be upgraded to support NFC (Near Field Communication) and mobile wallets. There is no clear return on investment model for the merchants, which are required to make the investment.
Who owns the secured element? Cooperation between credit providers, mobile operators, smartphone manufacturers, operating system vendors and others is required in order to be able to load multiple card credentials and payment applications into a single smartphone, with a single secured element. Such cooperation is very hard to achieve. Security: Data from smartphones have the tendency to leak at some point. A single software glitch, a virus or other security leak may cause a large scale card information leak.
Is it really that convenient? In some cases, yes. However, would someone pause a telephone conversation, close a game or skip a text message in order to open a payment or mass-transit application, type-in a password, place the phone near an NFC reader for 10 seconds and wait for the transaction to complete?
Branding: It is hard to predict the effect of mobile wallets on the branding of payment- infrastructure companies like VISA and MasterCard®, or for other credit issuers and banks, which practically owned a space in our physical wallets, and were visible to us every time we needed to pay for something. With mobile wallets they might be hidden behind the provider of the wallet. In fact, for the interest of convenience, mobile payment may not even require us to open the wallet application, or turn on our smartphone. The application opportunity and competition: Once using smartphones it is extremely easy for users to install new applications and uninstall the ones that they don't use. This creates a whole new situation for credit issuers and banks, as it opens the door for new comers, even for specific tasks, like payment for taxi or for parking. The large banks will now also compete for screen real -estate rather than good service and financial benefits.
The latest developments in mobile payment capabilities via smartphones create new opportunities for the banking and payment industry, but at the same time it also introduces some threats and new requirements.
For these reasons we believe that a form of plastic cards will continue to exist for years to come, but combined with A system that can store multiple cards information, eliminate the need to carry multiple plastic cards, find out the best configuration based on location, etc. and used conveniently by many people can be extremely useful and provide a true added value for users and service providers. SUMMARY
According to an aspect of the present invention, there is provided a system for managing multiple services using a single multipurpose card, comprising: at least one Service Provider configured to provide a card-implemented service; a System Server comprising a database comprising data pertaining to the at least one service provider and to at least one user; at least one configurable user's card; and at least one user electronic communication device running software configured to select a current configuration for the at least one user's card, the user's card communicating bi- directionally with the software; the system server communicating bi-directionally with the at least one Service Provider and with the at least one user electronic
communication device.
The at least one Service Provider may comprise at least one of store, hotel, train station, security system, payment system and loyalty program.
The software may comprise: a system application configured to: receive signals from the user's card; transfer card identification data to the system server; receive data comprising encrypted card configuration from the System Server; send encrypted card configurations to the user's card; receive user data comprising user location; and send the user data to the system server; and a user application configured to: provide GUI for receiving user inputs and for selecting a configuration; and send user data comprising manual card configuration selection and user location to the system application.
The software may be configured to receive a signal comprising a card number from the user's card when taken out of pocket and to select appropriate user's card configuration according to user location and system data. The user's card may comprise a light sensor; electronic components and a board.
The electronic components may comprise BLE (Bluetooth Low Energy) interface. The board may be laid out at the upper part of the user's card and may be configured to be embedded in a standard card comprising at least one of: magnetic-stripe emulation; battery and NFC chip.
The battery may be configured to be charged by at least one of light, piezoelectric cells and RF signals from NFC (Near Field Communication) source.
The user's card may comprise a memory configured to store various configurations.
The memory may comprise at least one security zone configured to store non- volatile and volatile information.
According to another aspect of the present invention, there may be provided in a system for managing multiple services using a single multipurpose card comprising at least one encrypted configuration, a method for automatic configuration of the card, comprising: taking the card out of a pocket; sending a signal by the card to an electronic communication device; recognizing the card by a software installed on the electronic communication device; sending by the software to a system server at least one of a card number and an account unique ID; sending by the software to a system server current location; calculating by the system server a most appropriate card configuration; sending by the system server the most appropriate card configuration to the software; sending by the software the most appropriate card configuration to the card; and using the most appropriate card configuration. According to another aspect of the present invention, there may be provided in a system for managing multiple services using a single multipurpose card comprising at least one encrypted configuration, a method for automatic configuration of the card, comprising: continuously sending by a software installed on an electronic communication device one or more of a card number and an account unique ID; continuously sending by the software installed on the electronic communication device current location to the system server ; receiving by the system server the sent one or more of card number and account unique ID and the current location calculating by the system server a card configuration number based on the user location; sending by the system server the card configuration number to the software; and storing by the software the card configuration number. The method may further comprise: sensing the card being taken out of pocket; sending a signal comprising the card number by the card to the software; recognizing the card by the software; sending by the software the stored card configuration number to the card; and using a configuration according to the stored card configuration number by the card.
BRIEF DESCRIPTION OF THE DRAWINGS:
For better understanding of the invention and to show how the same may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings.
With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice. The present invention is illustrated by way of example in the accompanying drawings, in which similar references consistently indicate similar elements and in which:
Fig. 1 illustrates the present invention's system;
Fig. 2 is a flowchart illustrating an example of usage of the system server;
Fig. 3 illustrates an example of records stored at the server; Fig. 4 illustrates an example of the information transferred through the mobile device from the System Server to the card ;
Fig. 5 illustrates card's configurations; Fig. 6 illustrates system's card schematics;
Fig. 7 illustrates system's card structure;
Fig. 8 illustrates embedded system in a card;
Fig. 9 shows a possible arrangement of memory inside the card; Fig. 10 illustrates EMV configuration selection;
Fig. 11 illustrates EMV enable/disable by the system application;
Fig. 12 is a flowchart illustrating the process of selecting card configuration by the system server.
Fig. 13 illustrates the configuration selection sequence performed by the system server; Fig. 14 is a flowchart illustrating the process of selecting card configuration by the system application.
Fig. 15 illustrates the configuration selection sequence performed by the system application;
Fig. 16 is an example of WiFi signals measured inside store B; Fig. 17 is an example of the table that is stored on the server, following users purchases at a certain location;
Fig. 18 shows an example for the measured value of certain parameter; and
Fig. 19 is a table illustrating the scores sent and presented to the user regarding his location in a certain store. DETAILED DESCRIPTION OF THE INVENTION
The present invention relates to the replacement of plastic cards that implement Magnetic Stripe, Smart-card, RFID or Near Field Communications (NFC) technologies, by a new system that includes a new multi-purpose electronic card that emulates prior art cards' functionality by electronics means. The new card is connected via Bluetooth or other wireless connection to a mobile communication device such as a smartphone or other device such as computer, note-pad or any other device. The mobile device connects the new card to the Internet and to a system server. A server, preferably a service provider's server can update data on the card and control it, via the system server and the mobile communication device, so that the new card according to the present invention is fully controlled and configurable by the service provider. The new electronic card can be read by existing magnetic readers of e.g. chip card, RFID and NFC infrastructure. The new card can be used in stores, hotels, train stations, security systems, payment systems, loyalty programs, etc. and utilize smartphone's and network capabilities for selecting configurations, updating data and serving multiple applications.
Specifically, the invention relates to applications like credit/debit card payment, opening a hotel room, train and metro cards, gift cards, loyalty cards and any other application which requires the use of a plastic electronic card. All these applications can be consolidated into a single electronic card, connected to a smartphone via Bluetooth, and controlled by the smartphone and the server over the Internet. The system server runs an application to automatically select the appropriate configuration of the card so that the user has no need to manually select a card configuration.
According to embodiments of the present invention, the user can select manually which configuration to use in any particular case, for example, a transportation card when the user is at a train station or a particular credit card when the user is at a store.
By utilizing the new system a service provider can build a database for providing various capabilities to users, for example using the location service of the smartphone (e.g. GPS, Wi-Fi) to provide indoor navigation service (in places like shopping malls, train stations, airport terminals, hotels, etc.); thus, the card is automatically configurated (according to the data stored at server) when approaching these points of interest .
Service providers can utilize the system for providing enhanced loyalty programs for users and for small businesses like grocery shops and other stores. The invention's technology enables multiple configurations and applications within a single card, links physical cards to mobile applications and provides interface for multiple services to configure the application and card.
According to embodiments of the present invention, the system does not require a physical card at all, only a mobile device. This system functions the same as physical card based systems when appropriate mobile devices readers are available at service points of interest (e.g. NFC).
System overview
The System 100 (Fig. 1) disclosed in the present invention includes a System Server 110, at least one User 120 and at least one Service provider 130. The Service provider 130 (may be a card provider or other service provider) communicates bi directionally with the System Server 110. The System Server 110 comprises a database (not shown).
User 120 comprises two components:
1. Multipurpose "Plastic Card" (Card) 140. A field programmable plastic card which can carry not only credit card information, but other programmable services as well. It emulates the magnetic-stripe and/or chip of existing cards and can be read by existing card readers, chip-and-pin readers, RFID and NFC infrastructure readers. The Card includes Bluetooth Low Energy (LE) or Near Field Communication (NFC) technology to connect the card to a mobile device.
2. Mobile device (electronic communication device) 150- a smartphone or other mobile communication device which comprises a System application 160, Application Programming Interface (API) 170 and at least one User application 180. The User application 180 provides a GUI (graphical User Interface), which can be used for manual configuration selection and it communicates bi-directionally with API 170. API 170 communicates bi directionally with System application 160. API 170 is used for multiple services and applications, so that the same Card 140 can be used as credit, loyalty, access to hotel rooms, mass-transit systems, security badges and much more. The API 170 runs on user's smartphone or other mobile communication device. The API 170 enables the Service Provider 130 to provide his own user application 180 to the User 120 and to use the Mobile device 150 features such as security, location, graphical user interface and others. System Server 110 receives from the user's smartphone 150 data relating to user's location, Card 140 configuration selections and preferences, in real time. It understands the behavior of users and can automatically select the best configuration to use for any particular case and service through System application 160. The System Server 110 is located at the Service Provider 130 or elsewhere in the cloud.
The System Server 110 controls and manages the Card 140 through the system application 160, provides end-to-end security, gathers statistics and performs location algorithms so that all information that is transmitted from the Service Provider 130 to the card is current, managed and secured.
The Service Provider 130 can communicate with many system cards via a single system server.
The System Server 110 can store and manage information and communicate it with the Mobile device System application 160 to be converted into magnetic stripe, smart card chip or RFID. System server
The system server is located at the provider's facilities or as a service in the cloud. Its purpose is to store and manage the information of all users' system cards and transfer it safely and securely to the cards when required.
The system server also performs off-line activities, such as mapping locations of merchants (some may function also as card providers) and following users' behavior. The system server stores a database of merchants, locations and other information, which is entered by users and businesses to provide information required for smart and automatic card-selection.
The system server 110 runs computer software that provides the following services to the service provider: 1. Interface between the service provider and the user
As depicted in Fig. 1, the system server is the interface between the system application 160 and the service provider.
For example, if a card is used for opening hotel rooms, then the server interfaces with the service provider program which creates the codes for opening the rooms.
Data can be entered to the system server manually through GUI, like web interface, by means of data base sharing or by providing an API to other applications.
Fig. 2 depicts an exemplary scenario of hotel key issuing:
The user books a hotel room via any mean 200. The hotel issues a room key using the software provided by the vendor of the room locks or the hotel's system 210. Then, the vendor's or hotel's software, installed at the hotel's computers, sends the key code to the system server 220. User's card is updated by the system application 160 with the key code. Finally, the user can use his card as a hotel key 240.
2. Manage the information on the user's system card
The system server maintains all the information that is stored in all cards. For example, if a card contains credit card information, and the service provider wishes to add information to the card, such as additional credit card number, the new information is added to the appropriate record at the system server and transferred securely to the appropriate card.
Fig. 3 shows an example of records 300 stored at the system server, plurality of users records who hold several membership programs (credit card, health card, loyalty card, etc.). The system server, depicted in Fig. 3, updates the card data of each user 320 via the internet cloud 310. 3. Convert users data to system
The card data is encrypted in ways which prevent any form of copying or altering the card, since it comprises also sensitive data, such as card number. No meaningful data is stored on the mobile device even though the mobile device relays the encrypted data from the system server to the Card.
When data is entered into the system server, for example - hotel key information, which includes the room number and date and time of expiration, it is encrypted at the system server. The encrypted information is sent to the user's mobile device, and is stored encrypted until it is downloaded to the card. This is the information that will be used by the magnetic-stripe emulator to open the door.
Additional information is also sent by the server to the mobile device, which includes, for example, the location of the hotel, expected dates of use, and any additional information that helps the mobile device determine which configuration should be available when the user approaches the hotel room. The additional information may also include which security measures are required in order to enable the specific configuration. Such security measures may be a PIN code, fingerprints or any other security information that is available by the mobile device. In Fig. 4 there is an example of the information encrypted and transferred through the mobile device 420 from the System Server 400 to the card 440. The information converted to system application data is for example, security level, hotel name and hotel location, which helps the system application select the appropriate card configuration. The card data encrypted on the card is for example room number, checkout date and checkout time. The card data is sent from the system server 400 through the mobile device 420 to the card 440. When the card 440 is taken out of the pocket, the card sends a signal comprising the card number to the system application installed on the mobile device 420. The system application sends the system server 400 the current location and card number. The system server 400 calculates the most appropriate card configuration number and sends it to the system application. The system application sends the most appropriate card configuration number to the card 440, which selects the appropriate card configuration. Finally, the card 440 is ready for use.
Other types of data may require another set of parameters; therefore a standard interface is implemented for the system server to support various types of services. 4. Perform Store Positioning
In order to automatically decide which card configuration to use and be able to provide additional location-based services, the system should know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a known location or another.
For example, the system server is aware of a merchant B for the first time, located near a GPS location XXXYYY, with the recorded parameters of cellular, WiFi and others (given by the user's mobile device via user application or the merchant itself via the system server). The next user to make a purchase at the same store will already have the appropriate database information available, and the server will be able to select automatically the appropriate configuration.
5. Help Auto-Selecting of Card Configuration
In many cases users would prefer one configuration over another. For example, users who have loyalty cards of certain merchants would prefer to use the appropriate loyalty card at the merchant's store.
Such auto-selection can be done based on various parameters: Location
Type of detected reader (if available)
- Specific information from server
User's preferences
Best value (based on discounts or other value offered by merchants)
A straight forward example may be: when a user makes a purchase at store A (for example -"Target") the system server will automatically select the credit card associated with store A, and when the user makes a purchase at store B (for example "Walmart") then that system server will automatically select the credit card that is associated with store B, assuming that the user has both configurations available within the card configurations. No user intervention is required. The system server uses algorithms to select the best suitable configuration, based not only on location, but also on date and time, currency conversion and other information that is available at the time of purchase or other use of the card.
The system server maintains user's preferences and combines them with the best configuration selection as described above. The outcome is a score for each
configuration, which may be calculated in real-time or provided in advance to the system application at the mobile device.
6. The social loyalty club
The system server has means to input data from users or businesses regarding discounts and advantages to certain loyalty clubs. This information is transmitted to all relevant users' system applications and taken into account when paying at the business.
For example, a user visits a certain gas station and notices a 10c discount per gallon for users of a certain loyalty club. The user can publish this information on the system server and once other users are near that gas station their card will automatically select the preferred loyalty club, if it is available among their configurations.
7. Provide accounting information to the server operator
A key factor of the system's acceptance by the market is its ability to generate revenues to its customers (service providers).
Service providers may have different revenue models. For example a credit card issuer may charge the other providers for any added record to a card, or charge the user per use of the card itself for anything that is not credit card.
The system server is able to provide information on use of the card, added records and any other information that may be relevant for the provider.
It is likely that service providers like credit card issuers, large loyalty programs or hotel chains would prefer to own their own system server. However, the system server can also be owned by 3rd parties who provide access to the system server for a fee or for another incentive. For example, a credit card issuer who owns a system server can provide access to 3r parties who wish to provide other services, as described above.
An Application Programming Interface (API) is provided, so that customers (service providers) and 3rd parties will be able to write their own user applications and services, and interface with the system.
According to embodiments of the invention a card may be attached to a single system server only or receive information from various system servers.
System application
The system application runs on a mobile communication device (for e.g., smartphone or tablet) and includes the following tasks:
• Handle all communication with the card, via Bluetooth LE, NFC or other means, and with the server, via cellular, Wifi or other means, to enable secured connection between the system's server and card.
• System's card security:
o Communicate with the card to verify its proximity to the Mobile device and warn user when no proximity,
o Enable mobile device's security features, when required, like PIN code or fingerprints.
o Reply with a message to system server regarding security levels, o Use mobile device's location services and other means to enable or disable card configurations. For example - enable the hotel room key only when user is in the vicinity of the hotel,
o Provide services such as graphical user interface (GUI) and sounds, o Provide user's history. Each use of the card can be related to a location, time, etc. and stored,
o Enable profiling of usage; allow users to select which record to use based on dates, location, etc.
o Support indoor positioning for store location and card configuration.
The system's application also provides an API for 3rd parties to create their own user applications. Card's configuration selection
The system application is responsible for selecting the appropriate configuration on the card for the next transaction.
According to embodiments of the invention the card configuration can be selected manually by the user, via the GUI (of user application), or automatically by the system application, based on information from the system server, location, Wifi signals strength, cellular cell information or other beacon signals.
Manual configuration is selected via the GUI, which shows all the available configurations that are stored in the card. The configurations include graphic presentation of the available configurations, similar to the ones illustrated in Fig. 5.
In order to automatically suggest which card configuration to use and be able to provide additional location-based services, the system server may know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located at this moment. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a known location or another.
This information is sent to the system server by the system application. The system server matches the information with payment information of that user, including stores name, and stores the information in a table that describes the stores name, location and the other available information. The system server also records the user's decision on which card to use, in case the user manually selected a configuration. For example, if the user selected a certain credit card at that location, then the card data (type, vendor, loyalty, etc.) is stored and ranked for the future users.
This database is used for matching the best configuration per user, location and time, and also for actions like targeted advertising and statistics.
The system's card The System's Card 500, as illustrated in Fig. 6, is a field programmable plastic card or module that can be integrated into a plastic card, which can be programmed in real-time from the cloud via user's mobile device.
The card comprises a BLE (Bluetooth Low Energy) interface 510, a controller 520 which translates the data and interfaces it to the appropriate card interface, a rechargeable energy harvesting system 530 (with loading means, such as a piezoelectric sensor 580) and various card interfaces - magnetic stripe 540, EMV chip 550, NFC contactless chip 560 and a light sensor 570 .
Before each use, the light sensor 570 senses that it is out of the user's wallet and communicates wirelessly with the mobile device via BLE interface 510. The card then receives from the system application the configuration for the next transaction and saves it until actual use at the Card reader, probably a few seconds later. This configuration is the actual data or configuration to be used for the magnetic stripe 540, EMV chip 550 or contactless interface 560 of the card. According to some embodiments, as depicted in Figs. 7 and 8, the multipurpose card of the present invention is implemented in a card module 710, designed so that it would be easy to integrate with standard credit cards 600 comprising EMV Chip 610. The card module 710 comprises elctronic components 630 such as BLE and memory, Magnetic- Stripe emulation 620, Battery 640 and NFC Chip 650, laid out as a module located at the upper part of the card, so that it would be possible to embed it in a standard card during manufacturing.
From user's perspective the card looks and feels exactly like a standard plastic magnetic-stripe card such as credit card.
Communication
The card communicates with an attached mobile device to receive its configurations, security messages and other data that is required for its operation.
The card uses standard BLE which is now available in most mobile devices and can communicate at up to 10 meters range, using extremely low energy. A special encrypted communication protocol is used to eliminate any possibility of eavesdropping and/or theft of card's information.
The card memory
The card contains memory which stores the various configurations and contains several "security zones", to enable non-volatile and volatile information to be stored. This is used to disable any access to the service provider data from the mobile device or from anywhere else. For example - credit cards data, which is secured and secret information, cannot be accessed from outside the card, except when the card is accessed by a card reader and the card is in the proximity of the Mobile device. Fig. 9 shows an exemplary arrangement of memory inside the card. At the non-volatile memory are stored three credit card numbers, with different levels of security, defined by the number on the right of each record.
• Level '0' means that this record will be used if no response from mobile device is received.
· Level ' 1 ' means that proximity to mobile device is required.
• Level '2' means that the user must enter a PIN code or fingerprints.
These levels can define, for example, which credit card number to use for different maximum expense levels that are allowed for each selected card.
The information on the non-volatile memory cannot be changed or manipulated by the System Server.
The volatile memory includes the records which are provided by the system server. These records are changeable. The amount of non-volatile and volatile memory, type of information and other data can be set by the service provider during initial programming of the card. System card magnetic stripe, chip, RFID and NFC interface
The system server converts the records stored in its memory to magnetic stripe, smart chip, RFID or Near Field Communication (NFC) encoded data. When swiping the card in a magnetic reader, communicating with a reader via the smart-card chip or communicating with an NFC reader, the card sends a signal to the system application which further communicates with the system server; system server sends an instruction to the system application regarding the appropriate record
(configuration) and the system application converts it to the interface being used by the mobile device.
Selection of record is done by the mobile device, as described above, in accordance with the specific situation, location, type of reader and other information from the server.
For example, if the card is being accessed by a smart-chip reader, the user has entered a PIN code, then the mobile device transmits to the card an instruction via system application to use record number 3, which is a credit card number with security level '2'.
The system module 710 always includes the magnetic stripe and NFC interfaces, which are completely flexible and configurable by the system. The EMV chip is optional, and may support various configurations:
Credit information credentials are pre-loaded to the EMV chip by the credit-card issuer, same as standard credit cards today, along with other configurations for other services, and the system server selects which configuration to use in each case, but has no access to the configuration data. Once the configurations are burned on the chip, they are unchangeable. Fig. 10 illustrates the configuration selection transmitted from the system server A to the EMV chip E through the system application installed on mobile device B. The selection of configuration by the system server A is done based on user's location, requirements and other parameters that may be used to select which credit card to use. C is the card and D is the communication mean to the mobile device B (such as BLE).
Fig. 11 is an illustration of the enable/disable function of the EMV chip by the system application. The EMV chip I is pre-loaded with the credit information credentials, same as today, and the system application installed on the mobile device F enables or disables the chip I. G is the card and H is the communication mean to the mobile device F (such as BLE).
In this case system server is used as a means for extra security of the EMV chip. There are various options for defining the security capabilities, for example, when the card is in proximity to the Mobile device then the EMV chip is enabled, and when the card is separated from the Mobile device then the EMV chip is disabled, thus the credit card is disabled.
If there is no communication between the system server and the EMV chip, then system module 710 is used for anything that is not EMV compliant credit card. In this configuration the credit card is just the same as today, and the system is used for applications that require the magnetic stripe or NFC, though on the same card.
Sensing that the card is out of the pocket
According to embodiments of the present invention, in order to preserve battery life the card is configured not to consume any power while it is inside user's wallet or pocket. It is assumed that while in the pocket or wallet, the card is in complete darkness, and therefore a light sensor can be used to determine if the card is out. An example for a light sensor is CPC 1822 from IXYS or similar.
The sensor should be sensitive enough so that even in minimal light conditions it will be able to determine that the card has been taken out of the pocket. As soon as the card is out of the pocket it may be turned on and initiate communication with the mobile device. Once paired, the first message is a "good-morning" message, which indicates to the mobile device that the card is out and ready for accepting data.
When the card is put back in the pocket it transmits to the mobile device a "good-night" message. If the card has sent a "good-morning" message, but is not responding within a given timeout, and a "good-night" message was not received yet, then the user will receive a warning message on his mobile device, with an indication of card is not seen or is out of range. Recharging the battery
When required to operate, the card is powered by a rechargeable flat battery. It is assumed that the card is used between two to five times per day, for a few seconds, while at all other times the card is idle. The battery may be of a solid-state type, with "energy harvesting" capabilities. For example, "Enerchip" from Cymbet or "Thinergy" from Infinite Power Solutions.
It is possible to recharge these batteries by several means, such as:
• Light, using photovoltaic cells
• Pressure or movement, using piezo-electric cells
· RF signals from NFC (Near Field Communication) source
Or all of the above combined.
Therefore, the light and piezoelectric cells and NFC chip are the sources of energy for recharging the battery, and also the sensors that provide information about the card being out of the pocket or wallet. In one embodiment of the present invention, the battery is able to power the Card for at least 4 years.
Data Flow
1. Before operation
As described above, the system includes a system server, a user (comprising a card and a mobile device), and a service provider. The service provider may install a system server and set-up users' accounts. The users' accounts include a unique ID per user, which is in reference to the user's SIM card number, telephone number, ID number or a unique system card number.
Users may install the user application on their mobile device and pair the card with it. Once the card is paired users are able to input their data. At the user application, users can type in or scan the credit card numbers and other information they would like to include with the card. Users can also select their preferences and profile of usage of the card. For example - use of particular cards in a particular store, use cards in accordance with dates, time of day, location, etc.
All the information is transmitted and stored at the system server, under user's unique record.
The system application is constantly updating the system server regarding the current location in order to receive the most appropriate and up to date card configuration or card configuration number. The process is as follows:
1. The system application sends the message
"Hello+#CardNumber+#UniqueID+#Location" to the system server. This message can be sent several times, at given times or locations, as configured by the user application.
2. The system server receives the message
"Hello+#CardNumber+#UniqueID+#Location" from the system application, calculates the most appropriate configuration or card configuration number based on the Location of the user and sends the encrypted message "Use Configuration #5" (assuming that Configuration #5 is the best to use at that location and time) or a message comprising the most appropriate configuration to the system application.
3. The system application receives the message "Use Configuration #5" or the message comprising the most appropriate configuration from the system server.
2. During operation
According to embodiments of the invention, there are two possible modes for selecting appropriate card configuration or configuration number, depending on the
communication speed between the system server and mobile device: Mode #1 - Server selects configuration (fast communication)
When a user takes a system card out of his pocket, a sequence of operations happens (Fig. 12, Fig. 13): At t0, the card senses that it has been taken out of the pocket and prepares itself for use. The card announces itself by sending a Bluetooth discover message to the system application installed on the mobile device. Once the system application recognizes the card, the card sends "GoodMorning+#CardNumber" to the system application through the Bluetooth interface 800.
At ti, the system application receives the GOOD MORNING message from the card, compares it to the card number that is stored locally and sends information to the system server. The information contains the card number, a unique ID for the account and information regarding the current location 810.
At t2jthe system server receives the message
"Hello+#CardNumber+#UniqueID+#Location" from the system application and calculates the most appropriate configuration or most appropriate configuration number for the card 820. Fig. 12 and 13 relate to the case where the configuration has already been downloaded to the card and only the configuration number to be used is sent.
In alternative embodiments, the actual configuration (record) may be sent.
At t3, after calculation of the most appropriate configuration number, the system server sends the configuration number to the system application. This message ("Use Configuration #5") may be encrypted 830.
At , the system application sends the selected configuration number to the card. The mesasage may be encrypted, and no meaningful data is stored at the mobile device 840.
At t¾, the card acknowledges the configuration ("Ack+#CardNumber"), decrypts the message and uses the appropriate configuration from the existing stored set of configurations 850.
After the card was used at the card reader, or when put back in the pocket or after a configurable time-out, the card sends a "Goodnight+#CardNumber" message to the system application 860. In mode# 1 ts-to<3 sec, since this is the minimal time of taking the card out of the pocket, otherwise the card may not be ready to be used.
This mode can be used when network communication is constantly available and at good bandwidth and low delay, so that the system application is constantly updated with the required configuration for the card.
Mode #2 - Application selects configuration (slow communication)
In case of slow communication to the system server, or otherwise as preferred by the service provider, it is possible for the system application at the mobile device to select the appropriate configuration number for the Card, as shown in Fig. 14, Fig. 15:
At to, after being taken out of the pocket and connecting via the Bluetooth interface, the card sends the message "GoodMorning+#CardNumber" to the system application 900.
At ti the system application receives the message "GoodMorning+#CardNumber" and if communication with the server fails, sends the last selected configuration ("Use Configuration #5") to the card 910. The selected configuration is encrypted, and no meaningful data is stored at the mobile device.
At t2jthe card acknowledges the configuration ("Ack+#CardNumber"), decrypts the message and uses the appropriate configuration, from the existing stored set of configurations for the next transaction 920. After the card was used at the card reader, or when put back in the pocket or after a configurable time-out, the card sends a "Goodnight+#CardNumber" message to the system application 930.
In mode#2 t2-t <3 sec, since this is the minimal time of taking the card out of the pocket, otherwise the card may not be ready to be used.
Perform store positioning based on payment In order to suggest which card configuration to use and be able to provide additional location-based services, the system server may know where, or inside which merchant, train station, hotel, airport gate, etc. the user is located at this moment. It is not necessary to know the exact location of the users and merchants, but instead, it is required to be able to know if the user is currently inside a location that is known to the server or not.
When the card is taken out of user's pocket or he uses his mobile device to perform payment or another action which requires the use of NFC, or a plastic card, the System Application records data regarding the reception of various signals that are available for the mobile device at the moment of payment or close to it.
This information includes:
• GPS information, including location, time and current availability. If GPS signal is not available then the system server assumes that the user is indoors.
• Any available WiFi information like WiFi Access-Points names, signal strength, MAC addresses and channels (available in Android, Windows).
• iBeacon, if available ( for iPhones).
• Cellular cells information, including Cell ID (CID), UTRAN Cell ID (LCID) and signal strength.
• Indoor positioning data, if available.
· QR code, if available.
• Users can add information as a free text or selected from a list of possible names for the location.
Fig. 16 shows an example of measured signals in a particular location, near or inside store B. A few WiFi Access Points (1-3) are available and their signals are shown in a graph that describes their names, MAC addresses, channels and signal strength at that particular location.
This information is sent to the system server, together with the unique user ID and time of recording. The system server matches the information with previous usage payment information of that user, such as what card configuration was used in this measured environment, and compares it also to other users' selected configurations for their cards in this particular measured environment. The server stores the information in a table that describes the store name, if available, location and any other available information.
If the user manually selected a card configuration, then the server also records the user's decision on what card to use. For example, if the user selected a certain credit card at that location, then the card data (type, vendor, loyalty, etc.) is stored and ranked.
Detailed Data
Fig. 17 is an example of a table stored on the system server, following users' purchases at a certain location.
The table in Fig. 17 refers to Users who paid at a Sheraton hotel in Manhattan. Some of the findings are:
Two of them paid with an American Express card provided by SPG, and one paid with a MasterCard, provided by Poalim Bank.
One user added a comment - "Sheraton Manhattan"
Most users received WiFi access points at similar signal strengths and were connected to the same cellular cell.
Database is built on the fly, based on users selecting cards and configurations manually, until the system server recognizes the various parameters that existed at the time of purchase. These parameters are saved and compared every time any user makes a purchase or other card transaction. So, for example, when a user makes a payment at Sheraton in Manhattan, in the example above, the card transmits to the mobile device the moment of transaction. Measurements are taken at that moment, recorded by the mobile device, and transmitted back to the system server.
In present example, the system server is aware of "SHTN_5462", located near a GPS location "Latitude : 40.725402 | Longitude : -73.989489", with the recorded parameters of cellular, WiFi and others, as described. Location Description
Once data is added to the system server, the system server integrates this data with the data that already exists on the server, by calculating means and variances of locations and measurements. For example:
• User 1 GPS location: Latitude : 40.725405 | Longitude : -73.989487
• User 2 GPS location: Latitude : 40.725407 | Longitude : -73.989483
• User 3 GPS location: Latitude : 40.725402 | Longitude : -73.989489 - Mean: Latitude : 40.725405 | Longitude : -73.989486
Variance: Latitude : 4.33 | Longitude : 6.33
A similar process is done for all measurable parameters - GPS, Cellular Signal Strength, WiFi, iBecon.
When a system application sends information to the system server, a standard score ('Z' value) is calculated for each parameter, indicating the chance of a user to be within the vicinity of the parameter.
For example, the system server created a 'z-value' graph of possible measurements for a certain parameter, say 'Latitude'. A user sent a currently measured data, which is close, but not exactly the same data as the mean that was calculated for all previous users. This means that as far as this particular parameter goes there is a e.g. 25% chance that the user is in the same location as previous users. Let us define this location as "previously known location". See example in Fig. 18.
A similar calculation is done for all parameters and then the system calculates a final score of the chance that the user is within a certain previously known location. The calculation is a simple average of all scores.
For example:
Average (Latitude, Longitude, cell sig. strength, Wifi, iBeacon): 0.25 + 0.2 + 0.31 + 0.4 + 0.1
= 0.252
This means that there is a 25.2% chance that the user is within this particular previously known location.
The same calculation is done for additional locations in the vicinity of that location. The calculated scores may be smaller, higher or the same.
The scores are then sent to the system application and can be presented to the user in a declining list based on the scores (Fig 19) so he can choose manually the card configuration. Manual configuration is usually made when user location is uncertain.
If the score of the location is higher than a predefined threshold (which can be defined by the system operator), then the system assumes that the user is at the particular previously known location, and selects the card's configuration automatically.

Claims

A system for managing multiple services using a single multipurpose card, comprising:
at least one Service Provider configured to provide a card-implemented service;
a System Server comprising a database comprising data pertaining to said at least one service provider and to at least one user;
at least one configurable user's card; and
at least one user electronic communication device running software configured to select a current configuration for said at least one user's card, said user's card communicating bi-directionally with said software;
said system server communicating bi-directionally with said at least one Service Provider and with said at least one user electronic communication device.
The system of claim 1, wherein said at least one Service Provider comprises at least one of store, hotel, train station, security system, payment system and loyalty program. 3. The system of claim 1, wherein said software comprises:
a system application configured to:
receive signals from said user's card;
transfer card identification data to said system server;
receive data comprising encrypted card configuration from said System Server;
send encrypted card configurations to said user's card;
receive user data comprising user location; and
send said user data to said system server;
and
a user application configured to:
provide GUI for receiving user inputs and for selecting a configuration; and send user data comprising manual card configuration selection and user location to said system application.
The system of claim 1, wherein said software is configured to receive a signal comprising a card number from said user's card when taken out of pocket and to select appropriate user's card configuration according to user location and system data.
5. The system of claim 1, wherein said user's card comprises a light sensor;
electronic components and a board.
6. The system of claim 5, wherein said electronic components comprises BLE (Bluetooth Low Energy) interface.
7. The system of claim 5, wherein said board is laid out at the upper part of said user's card and is configured to be embedded in a standard card comprising at least one of:
magnetic-stripe emulation; battery and NFC chip.
8. The system of claim 7, wherein said battery is configured to be charged by at least one of light, piezoelectric cells and RF signals from NFC (Near Field Communication) source.
9. The system of claim 1, wherein said user's card comprises a memory configured to store various configurations.
10. The system of claim 9, wherein said memory comprises at least one security zone configured to store non-volatile and volatile information.
11. In a system for managing multiple services using a single multipurpose card comprising at least one encrypted configuration, a method for automatic configuration of said card, comprising:
- taking said card out of a pocket;
sending a signal by said card to an electronic communication device;
- recognizing said card by a software installed on said electronic
communication device;
sending by said software to a system server at least one of a card number and an account unique ID;
sending by said software to a system server current location;
- calculating by said system server a most appropriate card configuration; sending by said system server said most appropriate card configuration to said software;
sending by said software said most appropriate card configuration to said card; and
- using said most appropriate card configuration.
12. In a system for managing multiple services using a single multipurpose card comprising at least one encrypted configuration, a method for automatic configuration of said card, comprising:
- continuously sending by a software installed on an electronic communication device one or more of a card number and an account unique ID;
- continuously sending by said software installed on said electronic
communication device current location to said system server ;
- receiving by said system server said sent one or more of card number and account unique ID and said current location ;
- calculating by said system server a card configuration number based on said user location;
sending by said system server said card configuration number to said software; and
storing by said software said card configuration number.
13. The method of claim 12, further comprising:
sensing said card being taken out of pocket;
sending a signal comprising said card number by said card to said software; - recognizing said card by said software;
sending by said software said stored card configuration number to said card; and
- using a configuration according to said stored card configuration number by said card.
PCT/IB2016/050873 2015-02-20 2016-02-18 Remotely configurable plastic card WO2016132314A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562118475P 2015-02-20 2015-02-20
US62/118,475 2015-02-20

Publications (1)

Publication Number Publication Date
WO2016132314A1 true WO2016132314A1 (en) 2016-08-25

Family

ID=56689209

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2016/050873 WO2016132314A1 (en) 2015-02-20 2016-02-18 Remotely configurable plastic card

Country Status (1)

Country Link
WO (1) WO2016132314A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116170794A (en) * 2023-04-25 2023-05-26 深圳市微付充科技有限公司 Online idle issuing system and method for smart card

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120074232A1 (en) * 2010-03-02 2012-03-29 Douglas Spodak Portable e-wallet and universal card
US20140172700A1 (en) * 2012-12-19 2014-06-19 Nxp B.V. Digital wallet device for virtual wallet
US20140291406A1 (en) * 2013-04-02 2014-10-02 Tnt Partners, Llc Programmable Electronic Card and Supporting Device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120074232A1 (en) * 2010-03-02 2012-03-29 Douglas Spodak Portable e-wallet and universal card
US20140172700A1 (en) * 2012-12-19 2014-06-19 Nxp B.V. Digital wallet device for virtual wallet
US20140291406A1 (en) * 2013-04-02 2014-10-02 Tnt Partners, Llc Programmable Electronic Card and Supporting Device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116170794A (en) * 2023-04-25 2023-05-26 深圳市微付充科技有限公司 Online idle issuing system and method for smart card
CN116170794B (en) * 2023-04-25 2023-08-08 深圳市微付充科技有限公司 Online idle issuing system and method for smart card

Similar Documents

Publication Publication Date Title
US11354644B2 (en) Systems and methods to generate a location dependent alert in a mobile device of a user
US20200342499A1 (en) Preference-Driven Advertising Systems and Methods
US20200250673A1 (en) Configuring Verification Information At Point-of-Sale Devices
US10043175B2 (en) Enhanced near field communications attachment
US11436578B2 (en) Interactive gratuity platform
US11620654B2 (en) Methods and apparatus for conducting secure magnetic stripe card transactions with a proximity payment device
US20200051073A1 (en) System and method for enhanced token-based payments
US20170061404A1 (en) System and Method to Personalize Products and Services
US20150154634A1 (en) Method and system for implementing transactions and promotional offers
US20130092741A1 (en) Wireless smart card and integrated personal area network, near field communication and contactless payment system
US10482440B1 (en) Simulating NFC experience
US20170161709A1 (en) Method and system to organize and manage transactions
CN103778533A (en) System for performing payment in mobile terminal
EP3084702A1 (en) A system and method for enhanced token-based payments
US20230045879A1 (en) Preference-driven advertising systems and methods
WO2016132314A1 (en) Remotely configurable plastic card
AU2015358442B2 (en) Methods and apparatus for conducting secure magnetic stripe card transactions with a proximity payment device
CA3050132C (en) Enhanced near field communications attachment
KR20170040558A (en) System for processing offline payment, method of processing offline payment based on secondary authentication using motion pattern and apparatus for the same
KR101740727B1 (en) Method, apparatus and computer program for generating magnetic stripe information
KR20170119276A (en) Server system of accumulating changes in mobile phone
Carvalho et al. A Value Framework for Mobile Payment with Examples from Selected Asian Countries

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16752018

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16752018

Country of ref document: EP

Kind code of ref document: A1