System, Device and Method for Executing a Digital Wallet Application

Abstract

The system comprises a user electronic device (200). A processor of the device (200) executes a digital wallet application associated with at least one digitised transaction card. The device (200) obtains user preference information in relation to the digital wallet application (S604); communicates the user preference information to a management server (300, S605); receives, from the management server (300), a notification command for the digital wallet application (S614). The notification command is determined according to the user preference information, and determines the audible and/or haptic feedback to be provided in relation to the digitised transaction card. The user electronic device (200) controls an audio and/or haptic output unit of the device to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command in response to the digitised transaction card being selected and/or used for a transaction.

Claims

1. A system comprising: a user electronic device comprising a communicator, an audio and/or haptic output unit, and a processor communicatively coupled to the communicator and the audio and/or haptic output unit, wherein the processor is operable to execute a digital wallet application, wherein the digital wallet application is associated with at least one digitised transaction card, and wherein the processor of the user electronic device is operable to: obtain user preference information in relation to the digital wallet application; control the communicator to communicate the user preference information to a management server; control the communicator to receive, from the management server, a notification command for the digital wallet application, the notification command being determined according to the user preference information, and the notification command determining the audible and/or haptic feedback to be provided in relation to the digitised transaction card, and control the audio and/or haptic output unit to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command received from the management server in response to the digitised transaction card being selected and/or a transaction being performed using the digitised transaction card.

2. The system of claim 1, wherein the digital wallet application is associated with a plurality of digitised transaction cards, and wherein notification commands are received for each of the digitised transaction cards according to the user preference information, and wherein different audible and/or haptic feedback is provided depending on which digitised transaction card is selected and/or used to perform a transaction.

3. The system of claim 2, wherein the digital wallet application, when executed, is arranged to display a plurality of graphic assets each associated with a different one of the digitised transaction cards, and in response to one of the digitised transaction cards being selected by the user, the processor of the user electronic device is operable to control the audio and/or haptic output unit to provide audible and/or haptic feedback according to the notification command associated with the selected digitised transaction card.

4. The system of claim 1, wherein the audio and/or haptic output unit comprises a vibration unit configured to vibrate the user electronic device, and wherein at least one of the frequency, amplitude and duration of the vibration is determined by the notification command.

5. The system of claim 1, wherein the audio and/or haptic output unit comprises a speaker configured to output an audible signal, and wherein at least one of the frequency, amplitude and duration of the audible signal is determined by the notification command.

6. The system of claim 1, wherein the user electronic device comprises a user input for receiving the user preference information.

7. The system of claim 1, wherein the audible and/or haptic feedback provided according to the notification command changes based on at least one of: the digitised transaction card; the status of the transaction; the value of the transaction; the cumulative value of transactions made during a predetermined time period; the number of transactions made during a predetermined time period; the frequency of transactions made within a predetermined time period; and whether the digitised transaction card is associated with a loyalty scheme.

8. The system of claim 1, wherein the audible and/or haptic feedback provided according to the notification command changes based on whether a predetermined threshold value has been exceeded in relation to at least one of: the cumulative value of transactions; the number of transactions; and the frequency of transactions.

9. The system of claim 1, wherein the user electronic device is operable to control the communicator to communicate transaction information to a transaction card server in response to a transaction being performed by the digitised transaction card associated with the digital wallet application, wherein the transaction card server is arranged to authorise the transaction in response to receiving the transaction information.

10. The system of claim 9, wherein the transaction card server is arranged to communicate an authorisation response to the management server, the authorisation response identifying at least the digitised transaction card that performed the transaction, and wherein the management server is arranged to communicate the notification command to the user electronic device based on the authorisation response received from the transaction card server and the user preference information received from the user electronic device.

11. The system of claim 1, wherein the notification command comprises an audio file and/or haptic file, and wherein the processor of the user electronic device is operable to store the audio file and/or haptic file in a memory of the user electronic device for subsequent use by the audio and/or haptic output unit.

12. The system of claim 1, wherein the processor of the user electronic device is operable to control the communicator to communicate the user preference information to the management server and an identifier for the digitised transaction card associated with the user preference information.

13. A method performed by a system comprising a user electronic device, the user electronic device comprising a communicator, an audio and/or haptic output unit, and a processor communicatively coupled to the communicator and the audio and/or haptic output unit, wherein the processor is operable to execute a digital wallet application, the digital wallet application is associated with at least one digitised transaction card, and wherein the method comprises: obtaining user preference information in relation to the digital wallet application; controlling the communicator to communicate the user preference information to a management server; controlling the communicator to receive; from the management server, a notification command, the notification command being determined according to the user preference information, and the notification command determining the audible and/or haptic feedback to be provided in relation to the digitised transaction card; and controlling the audio and/or haptic output unit to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command received from the management server in response to the digitised transaction card being selected and/or a transaction being performed using the digitised transaction card.

14. A user electronic device suitable for use with the system of claim 1, the user electronic device comprising a communicator, an audio and/or haptic output unit, and a processor communicatively coupled to the communicator and the audio and/or haptic output unit, wherein the processor is operable to execute a digital wallet application, the digital wallet application is associated with at least one digitised transaction card, and wherein the processor of the user electronic device is operable to: obtain user preference information in relation to the digital wallet application; control the communicator to communicate the user preference information to a management server; control the communicator to receive, from the management server, a notification command, the notification command being determined according to the user preference information, and the notification command determining the audible and/or haptic feedback to be provided in relation to the digitised transaction card; and control the audio and/or haptic output unit to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command received from the management server in response to the digitised transaction card being selected and/or a transaction being performed using the digitised transaction card.

15. A management server suitable for use with the system of claim 1, the management server comprising a communicator and a processor communicatively coupled to the communicator, wherein the communicator of the management server is operable to: receive user preference information from a user electronic device, and wherein the processor of the management server is operable to: determine a notification command according to the received user preference information, the notification command determining the audible and/or haptic feedback to be provided by the user electronic device in relation to a digitised transaction card associated with the digital wallet application; and communicate the notification command to the user electronic so that the user electronic device is operable to provide audible and/or haptic feedback according to the notification command.

Description

[0066] For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example only, to the accompanying diagrammatic drawings in which:

[0067] FIG. 1A shows a digital wallet application according to an existing implementation;

[0068] FIG. 1 B shows a schematic view of a system according to an existing implementation;

[0069] FIG. 2 shows an example system according to aspects of the present invention;

[0070] FIG. 3 shows an example system according to aspects of the present invention;

[0071] FIG. 4 shows an example user electronic device according to aspects of the present invention;

[0072] FIG. 5 shows an example management server according to aspects of the present invention;

[0073] FIG. 6 shows an example signal flow diagram according to aspects of the present invention; and

[0074] FIG. 7 shows an example system according to aspects of the present invention.

[0075] Referring to FIG. 2, there is shown a system 100 according to aspects of the present invention. The system 100 comprises a user electronic device 200 and a management server 300. The user electronic device 200 and management server 300 are communicatively coupled to one another, e.g. via a wireless communication connection, such that they may send and receive data from one another. The system 100 is configured to provide improved and securer point-of-sale feedback to digital wallet users.

[0076] The user electronic device 200 acts as a digital wallet. In particular, a digital wallet application and consumer application are both installed on the user electronic device 200, and are operable separately or in combination to output audible and/or haptic feedback according to user preference information. The consumer application is not required in all examples of the present invention as all functionality may be provided by the digital wallet application. The user preference information may be input to the consumer application or the digital wallet application by the user. The digital wallet and consumer applications are downloadable from an application store and/or content provider. For example, the content provider may comprise the Apple® Appstore® or Google® Play®. The consumer application may be incorporated into another application on the device. The functionality of the consumer application may be provided as a software developer's kit (SDK) so that the consumer application may be incorporated into another application such as a banking application.

[0077] FIG. 3 illustrates another representation of a system 100 according to the present invention. The system 100 comprises the user electronic device 200 and management server 300 also shown in FIG. 2. The system shown in FIG. 3 uses a communications network, such as a wide-area network, and in particular the Internet for example, which connects the various parties involved in the system and provides network infrastructure for the exchange of data. The user electronic device 200 is connected to the communications network in order to upload data for processing to the management server 300. The consumer application comprises an application interface that is used to gather data from the user, and to display data sent to the application by the management server 300 via a communications network. For example, the consumer application may gather transaction card information by capturing an image of a physical transaction card 70 using the device camera as shown in FIG. 3.

[0078] Data input to the consumer application by the user can be uploaded via the communications network to a centralized hub (e.g. the management server 300), where it can be managed and processed. The management server 300 may receive data sent via the communications network and provide data to other components connected to the communications network. The management server 300 comprises a communicator 301 shown in the form of a communications server, a processor/controller 305 and a memory/database 303. Data is received and processed at the management server 300 by the communications server 301, which is operatively coupled with the controller 305. The controller 305, in turn, is operatively coupled with the database 303. Data that is received by management server 300, or data that is of use for the operation of the management server 300, may be stored in the database 303. The management server 300 is external to the consumer application and acts as an on demand service.

[0079] Although not shown in FIG. 3, the management server 300 may further comprise an encryption module for encrypting data before it is communicated, a decryption module for decrypting encrypted data communicated to the management server, a user registration module for registering individual users and their associated devices, a user preferences module for processing the preferences selected by a user using the consumer application, and a notification module for generating signals and/or commands to be communicated to the electronic device during a transaction process.

[0080] In order to perform transactions, the user electronic device is configured to communicate with a point-of-sale (POS) terminal 25 associated with a particular merchant using NFC or other short-range wireless communication protocol. This communication is depicted by a dotted line in FIG. 3. FIG. 3 further shows at least one transaction card provider (PCP) 21 and at least one transaction card server, which is identified as a payment service provider (PSP) 23. The components are connected via the communications network. The user electronic device is separately or additionally configured to perform transactions online by communicating with a merchant server.

[0081] Referring to FIG. 4, there is shown a simplified schematic diagram of an example user electronic device 200 in accordance with the present invention. The user electronic device 200 comprises a communicator 201, a user interface 203, a memory/data store 205, a processor 207, and audio and/or haptic output unit 209. The memory 205 has stored thereon a digital wallet application. The processor 207 is communicatively coupled to the communicator 201, user interface 203, memory 205, and audio and/or haptic output unit 209. The audio and/or haptic output unit 209 may comprise a speaker such as a loudspeaker for providing audible feedback (e.g. audible notifications). Additionally or separately, the audio and/or haptic output unit 209 may comprise a vibration unit such as a vibration motor for providing feedback (e.g. notifications) in the form of vibrations.

[0082] The user interface 203 may comprise or be associated with a display. The user electronic device 200 may also comprise a camera. The communicator 201 is operable to facilitate exchange of data with other processing elements shown in FIGS. 2 and 3 via the communications network, or with the POS terminal via NFC. The user electronic device 200 may also operate a consumer application stored within the memory/data store 205, and is able to be run on command by the processor 207 in the conventional manner. The user interface 203 of the user electronic device 200 may be integral with a display of the user electronic device 200, and may be a presence sensitive display such as a touch screen in this embodiment. Typically the user electronic device 200 is a smartphone or tablet.

[0083] The digital wallet application comprises a digitised transaction card. The digital wallet application may also comprises a graphic asset associated with the digitised transaction card. The digital wallet application, when executed by the user electronic device 200 may be arranged to display the graphic asset associated with the digitised transaction card. For example, the user electronic device 200 may be arranged to display the graphic asset associated with digitised transaction card in the manner shown in FIG. 1A.

[0084] An object of the present invention is to provide a notification command to the user electronic device 200 such that the audio and/or haptic output unit 209 of the user electronic device 200 is able to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command.

[0085] In an example of this, the processor 207 of the user electronic device 200 obtains user preference information in relation to the digital wallet application. In one example of this, the user electronic device 200 receives a user command for selecting the user preference information. The user command may be provided by user input via the user interface 203 of the user electronic device 200. The user input may be provided via voice control.

[0086] The processor 207 of the user electronic device 200 controls the communicator 201 to communicate the user preference information to the management server 300.

[0087] The processor 207 of the user electronic device 200 controls the communicator 201 to receive, from the management server 300, a notification command (e.g. for the digital wallet application). The notification command is determined according to the user preference information. The notification command determines the audible and/or haptic feedback to be provided in relation to the digitised transaction card.

[0088] The processor 207 of the user electronic device 200 controls the audio and/or haptic output unit 209 to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command received from the management server 300 in response to the digitised transaction card being selected and/or a transaction being performed using the digitised transaction card.

[0089] Significantly, the user electronic device 200 provides audible and/or haptic feedback that is specific to the user. The feedback can be provided when the digitised transaction card is selected in the digital wallet application for the purposes of allowing the user to identify the digitised transaction card when visual inspection of the digital wallet application is not possible or not sufficient to identify the digitised transaction card. The feedback can be provided when the transaction is performed using the digitised transaction card so that the user receives and audible and/or haptic confirmation of the transaction. Based on the user preference information, the feedback can include information that is encoded in a user specific way and convey sensitive information to the user in a secure manner. The sensitive information includes the digitised transaction card; the status of the transaction; the value of the transaction; the cumulative value of transactions made during a predetermined time period; the number of transactions made during a predetermined time period; the frequency of transactions made within a predetermined time period; and whether the digitised transaction card is associated with a loyalty scheme.

[0090] Referring to FIG. 5, there is shown a simplified schematic diagram of an example management server 300 in accordance with the present invention. The management server 300 comprises a communicator 301, a memory 303 and a processor 305. The communicator 301 is in communication with the communicator 201 (FIG. 4) of the user electronic device 200. The processor 305 is communicatively coupled to the communicator 301 and memory 303.

[0091] The processor 305 of the management server 300 controls the communicator 301 to receive the user preference information from the user electronic device 200 (via the communicator 201). The processor 305 controls the communicator 301 to determine a notification command. The notification command is determined according to the user preference information. The processor 305 obtains the notification command, and controls the communicator 301 to communicate the notification command to the user electronic device 200.

[0092] The management server 300 may further comprise a user accounts module which is associated with a user accounts database. Together, the processor 305 and user accounts module may be configured to register individual users and their associated devices, to process the preferences selected by a user using the consumer application, to identify the user information initially, to pass the information to the user accounts database and to build a profile of the user based upon preference information.

[0093] The memory 303/database/data store of or associated with the management server 300 may comprise a user accounts database. The user accounts database may contain specific information relating to each user such as the digitised transaction cards and/or registered tokens for the digitised transaction cards, a user profile and enrolment information and the user's preference information.

[0094] The communicator 301 may also comprise or be associated with an encryption module for encrypting data before it is communicated, a decryption module for decrypting encrypted data communicated to the management server 300, and a notification module for generating signals and/or commands to be communicated to the electronic device.

[0095] Referring to FIG. 6, there is shown a signal flow diagram for an example process in accordance with the aspects of the invention. This process is for generating audible and/or haptic feedback in response to the user electronic device performing a transaction with a digitised transaction card.

[0096] In step S601 the user of the user electronic device 200 enrolls a transaction card. This may have already been performed, and is not required in all examples of the present invention.

[0097] If the user has enrolled a transaction card, step S602 is performed which involves identification information for the transaction card being transmitted to a management server 300 which in turn transmits information to the transaction card server 400 in step S603. In some examples, the identification information may be transmitted from the user electronic device 200 directly to the transaction card server 400 rather than via the management server 300. The transaction card server 400 may then provide a reference identifier for the transaction card and a graphic asset for the transaction card may also be transmitted to the user electronic device 200, but this is not essential for the present invention.

[0098] In step S604, the user electronic device 200 obtains user preference information.

[0099] In step 3605, the user preference information is transmitted to the management server 300.

[0100] In step 3606, the user electronic device 200 performs a transaction using the digital wallet application. The transaction involves communicating transaction card information to a merchant 500 as represented by step S607. The transaction card information may be transmitted via NFC to a payment terminal of the merchant 500 with NFC enabled. The merchant transmits a request to authorise the transaction to the transaction card server 400 in step S608. Of course, the transaction does not need to be performed via NFC, and can additionally or separately be performed online by communicating with a merchant server.

[0101] In step S609, the transaction card server 400 authorises the transaction. This may require that the transaction card server 400 communicates with additional entities. An authorisation response is transmitted to the merchant 500 in step S610. An authorisation response is transmitted from the merchant 500 to the user electronic device 200 in step S611. An authorisation response is transmitted from the transaction card server 400 to the management server 300 in step S612.

[0102] In step S613, in response to receiving the authorisation response, the management server 300 determines a notification command according to the user preference information received in step S605, The notification command may additionally be determined according to the authorisation response. The authorisation response may indicate whether the transaction was successful, and/or the amount of the transaction, and/or the merchant associated with the transaction. This information may be used along with the user preference information to determine the notification command.

[0103] In step S614 the notification command is transmitted to the user electronic device 200. In this way, the user electronic device 200 is able to provide audible and/or haptic feedback according to the notification command received from the management server 300 in response to transaction being performed with the merchant 500.

[0104] The example of FIG. 6 relates to providing audible and/or haptic feedback in response to the performance of a transaction. In other examples, such as where the audible and/or haptic feedback is provided in response to a digitised transaction card being selected in the digital wallet application, steps 606 to 612 are not required. Instead, the management server 300 may determine the notification command directly in response to receiving the user preference information and may then communication the notification command to the user electronic device 200.

[0105] Referring to FIG. 7, there is shown another example of a system 100 in accordance with the present invention. The system 100 comprises the user electronic device 200, the management server 300, the transaction card server 400, the tokenization platform 30, and the digital wallet application server 40.

[0106] A general example operation of the system 100 will now be described.

[0107] The initial process of downloading the application, installation on the user electronic device 200 and registration of a user will be described.

[0108] The user initially downloads the consumer application to their user electronic device 200 and installs the consumer application to allow the consumer application to interact with and control the user electronic device 200. The consumer application is stored in the device memory/database and may be sourced from an application store and/or content provider. For example, the content provider may comprise the Apple® Appstore® and/or may comprise a cloud computing provider.

[0109] After installation of the application, a user may register personal details using the consumer application interface. These details are used for identification purposes and for subsequent authentication requests. The consumer application encrypts and communicates the user details to the management server 300, which receives the details at communicator 301 (FIG. 5) via an application programming interface (API). The communicator 301 then decrypts the details and passes them to the processor 305 (FIG. 5) to allow a user profile to be created in the user accounts database. Although only a single user electronic device 200 is depicted here, it will be appreciated that more than one user electronic device 200 will be able to communicate with the management server 300 via the communications network at any time.

[0110] As the management server 300 is an on-demand service, the user electronic device 200 requires a connection to the communications network, such as an Internet connection, for the user to be able to interact fully with the consumer application. Where a user electronic device 200 cannot connect to the management server 300, then the application is still be able to perform much of its functionality with only locally cached media. It is noted however that changes to preferences are not saved to the relevant database and so these changes do not persist in such a situation.

[0111] When a connection to the communications network and connection to the management server 300 are established, the details are encrypted using an encryption module (not shown) and persisted in the user accounts database.

[0112] The process of enrolment of a user, and the process relating to the user's image preferences will now be described.

[0113] Having registered with the service, the user may enroll at least one transaction card used in their existing digital wallet application via the consumer application or directly from the digital wallet application if the consumer application is integrated with the digital wallet application. The consumer application may have the functionality to enroll the transaction card in the digital wallet application simultaneously and automatically.

[0114] To enroll the at least one transaction card, the user is typically required to input at least a Primary Account Number (PAN) for the card, and optionally may input an expiry date and security code. The encrypted card information is securely transferred from the device 200 to the tokenization platform 30 via the communications network. The transfer of transaction card data may be via the management server 300, although the management server 300 is typically not able to decrypt the encrypted card information, as this information may only be decrypted by the tokenization platform 30. The transaction card data may be transferred directly from the user electronic device 200 to the tokenization platform 30, or may be transferred via the transaction card server 400. The tokenization platform 30 may be part of or may be associated with the transaction card server 400.

[0115] The tokenization platform 30 decrypts the PAN and any other card information from which it generates a card identifier (CID). The PAN and other card information is then stored in a card data vault associated with the tokenization platform 30. The CID is a non-sensitive data equivalent used to refer to the card so that reference can be made to it without any sensitive information being transferred via non-encrypted communications. The tokenization platform 30/transaction card server 400 encrypts and securely returns the CID to the management server 300 and/or the user electronic device 200. [00116] The CID, at least, is subsequently transferred from the consumer application operating on the user electronic device 200 to the management server 300. At this point, the consumer application may communicate additional data such as user-specific data or assets, although it will be appreciated that this information may be communicated to the management server by the electronic device at any time.

[0116] The management server 300 confirms to the user electronic device 200 that the data has been received. A confirmation may be communicated to the user.

[0117] Once the management server 300 has received the CID at its communicator 301, the user accounts module of the management server 300 is configured to store the CID in the user accounts database for subsequent use.

[0118] The card enrolment process is then complete, and the user is prompted to either enroll more cards, in which case the process repeats until the user has finished enrolling transaction cards. A user can set their unique user preferences at any time after payment cards have been enrolled with the consumer application. The preferences are used to determine point-of sale feedback, and in particular, which audible and/or haptic feedback notifications will be generated and under which circumstances they will be performed. More specifically, the user can associate specific response profiles with specific meanings and these can be stored centrally on the management server. For example, the user can associate three different response profiles with three different feedback meanings such as the transaction status, the value of the transaction, and the number of different transactions made, amongst others as described above. The present invention is not limited to three different response profiles and more or fewer response profiles can be provided.

[0119] Response profiles can be created within the consumer application using a profile activity. This activity will provide user-selectable patterns of audible and/or haptic feedback that a user can associate with a given feedback (number of transactions, transaction amount threshold etc.)

[0120] The user input to the user electronic device 200 may be passed to a preferences module that is in communication with both a preferences database and a notifications module. In particular, the user electronic device 200 may encrypt the user preference information before communicating it to the management server 300, where it is passed from the communicator 301 to the processor 305. The processor 305 utilizes the preference information to update the user's profile in the user accounts database and to access or otherwise determine the relevant notification command that corresponds to the user's preference. If this is successful, the communicator 301 again issues a confirmatory response to the electronic device.

[0121] The management server 300 communicates updates to the user preference information and other metadata associated with the digitised transaction card to the transaction card server 400. The management server 300 is also configured to communicate with the consumer application to ensure that the correct notification files, such as sound files or vibration feedback signals are stored on the user electronic device 200 to enable quick recall when required. The sound files may be stored as WAV files for example. This means that the different audio and/or haptic feedbacks are pre-stored as files on the user electronic device 200, and when a particular notification command is received from the management server 300, the processor of the user electronic device 200 obtains the required file to generate the feedback according to the notification command.

[0122] The consumer application may also communicate with the transaction card server 400 to update metadata associated with the digitised transaction card so that when a transaction is made using that card, a chain of authorisation requests between the user electronic device 200, merchant 500, and transaction card server 400 takes place. In addition to these, the transaction card server 400 also communicates an authorisation response to the management server 300. This response is then communicated to the consumer application via the communications network to allow POS feedback to be implemented according to the user's indicated preferences. The communication of this authorisation response to the management server 300 allows the management server 300 to provide a custom notification to the user as opposed to the standard, non-customisable and non-specific feedback provided by the digital wallet application. Advantageously, the provision of a separate management server 300 to enact these notifications ensures that both the transaction made using the user electronic device 200 and the notification provided by the consumer application are as swift as possible and that there is no uncertainty about the information that has been communicated both ways.

[0123] The user preferences include the default transaction notification sound and default transaction vibration feedback associated with the digitised transaction card and the rules for generating notifications. For example, when a user uses the digital wallet application to make a number of transactions over a predetermined time period, a particular notification may be used when the user makes the ‘N.sup.th’ transaction and thereby reaches a threshold transaction. This threshold may be set by the merchant to identify when the user qualifies for a loyalty reward, or by the transaction card server or another entity to reward the customer for spending using their card or platform. In these examples, the threshold and cumulative transaction value would be calculated and compared by the management server following each transaction.

[0124] Separately or additionally, the user may predefine a transaction limit threshold and a specific notification that corresponds to an exceedance of this threshold. Such examples are beneficial in enabling a user to easily manage their finances.

[0125] Separately or additionally the notification may relate to an authorisation result. That is, the feedback may convey whether the transaction was successful.

[0126] In some embodiments, the frequency of transactions made within a particular predetermined time period may result in a specific notification, or the number of transactions made during that period may be associated with a notification. The notification may be particular to a specific merchant, transaction card server, other entity, or may be related to a transaction status.

[0127] In some embodiments the consumer application may ‘gamify’ the data, requiring the user to make specific transactions for a specific notification to be played or accessible.

[0128] It will be appreciated that multiple feedback notifications may be enacted simultaneously or consecutively if a number of rules or preferences have been set. That is a combination of multiple different audible and/or haptic outputs may be generated according to a notification command.

[0129] In some embodiments, once the user has set their user preferences, the user electronic device 200 may download notification data selected by the user from the management server 300 and store it in the user electronic device 200 memory for recall later. If the user preferences change, the notification data is replaced with new data. The notifications module is configured to prompt the device to access the data and communicate this following a transaction.

[0130] In some embodiments, the audible and/or haptic feedback may also be associated with an image displayed on the device display when a transaction has occurred.

[0131] In some embodiments, the audible and/or haptic feedback may be made by the consumer application. In some embodiments, the audible and/or haptic feedback may be made by the digital wallet application rather than the consumer application. In this case, the digital wallet may access the notification directly from the management server memory/database and stores it in the user electronic device 200 memory.

[0132] In summary, there is provided a system, device and method for executing a digital wallet application. The system comprises a user electronic device. A processor of the device executes a digital wallet application associated with at least one digitised transaction card. The device obtains user preference information in relation to the digital wallet application; communicates the user preference information to a management server; receives, from the management server, a notification command. The notification command is determined according to the user preference information, and determines the audible and/or haptic feedback to be provided in relation to the digitised transaction card. The user electronic device controls an audio and/or haptic output unit of the device to provide, when the digital wallet application is executed, audible and/or haptic feedback according to the notification command in response to the digitised transaction card being selected and/or used for a transaction.

[0133] At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware. Terms such as ‘component’, ‘module’ or ‘unit’ used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it will be appreciated that described features may be combined in any suitable combination. In particular, the features of any one example embodiment may be combined with features of any other embodiment, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the term “comprising” or “comprises” means including the component(s) specified but not to the exclusion of the presence of others.

[0134] Although a few preferred embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims.

[0135] Attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0136] All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive.

[0137] Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

[0138] The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed