Enhanced recipient notification

Abstract

Embodiments allow a first transfer application executing on a first user device to send funds along with supplemental data to a second transfer application executing on a second user device. The supplemental data includes one or more of text messages, audio content, video content, drawings, photos, multimedia files, etc. The application provider server of the first transfer application and / or the application provider server of the second transfer application does not support the transfer of the supplemental data. A processing computer positioned between the two transfer applications facilitates the transfer of supplemental data. When a fund transfer is processed by an authorized entity, the processing computer generates an enhanced notification including the supplemental data and transmits the enhanced notification directly to the second transfer application.

Description

[0001] Cross-reference to related applications

[0002] This application is a PCT application, which claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 390,287, filed on July 18, 2022, which is incorporated herein by reference. Background Art

[0003] Many money transfer applications allow users of the application (e.g., senders) to easily transact with other users of different applications (e.g., receivers). After a successful transaction, the receiver's money transfer application may receive transaction data about the transaction. However, the transaction data received by the receiver's money transfer application is usually limited, and only basic payment data such as the transaction amount and date are received. Therefore, even if the sender sends other supplementary data about the transaction (e.g., a message from the sender), the receiver cannot receive such data.

[0004] Embodiments of the present disclosure address this and other problems, individually and collectively. Summary of the invention

[0005] Embodiments allow a sender using a first transfer application executed on a user device of the sender to send funds and supplementary data to a recipient using a second transfer application executed on a user device of the recipient, wherein the second transfer application does not support the transmission of supplementary data (e.g., text messages, audio files, video files, multimedia files, photos, etc.). Embodiments provide a processing server for receiving and storing supplementary data from a sender via a first transfer application. The processing server operates with an authorized entity to complete a funds transfer using OCT processing. Once the OCT processing is approved by the authorized entity, the processing computer generates an enhanced notification message and transmits it to the second transfer application installed on the user device of the recipient. The enhanced notification message notifies the recipient of the funds transfer and the supplementary data provided by the sender. The second transfer application outputs the supplementary data on the user device of the recipient.

[0006] An embodiment provides a method performed by a processing computer. The method includes receiving a processing request message from a digital wallet provided on a first user device, the processing request message including supplementary data and transaction data elements about a transaction between a first user operating the first user device and a second user operating a second user device. The processing computer stores the supplementary data in a database as associated with the transaction data element; and transmits a push request message to an authorized entity computer holding an account of the second user, the push request message including the transaction data element without the supplementary data. The push request message conforms to a format that the authorized entity is configured to process. The method also includes receiving a push response message including the transaction data element from the authorized entity computer. The processing computer searches the database for the supplementary data using one or more of the transaction data elements received in the push response message, and identifies the supplementary data in the database based on a match between the one or more of the transaction data elements received in the push response message and one or more of the transaction data elements stored on the database. The method also includes retrieving the supplemental data corresponding to the matched transaction data element; generating a notification message including the supplemental data; and transmitting the notification message including the supplemental data to a digital wallet provided on the second user device. The supplemental data is output on the second user device in conjunction with a notification associated with the transaction.

[0007] An embodiment also provides a system, which includes: a processing computer including one or more processors; and a non-transitory computer-readable medium including codes executable by the one or more processors for performing the method described above.

[0008] According to various embodiments, a method includes receiving, by a first digital wallet application executed on a first user device, a notification message including supplementary data and a result of a money transfer transaction from a processing computer. A digital wallet provider server that manages the first digital wallet is unable to support the transmission of the supplementary data. The first digital wallet application displays a graphical user interface to display the result of the money transfer transaction; and outputs the supplementary data and displays the result of the money transfer transaction, wherein the supplementary data includes one or more of text data, image data, audio data, multimedia data, or data embedded in a machine-readable code.

[0009] A better understanding of the nature and advantages of embodiments of the present invention may be obtained by reference to the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1Two user devices storing one or more applications that interact through a processing computer are shown in accordance with various embodiments.

[0011] Figure 2 A flow chart illustrating the transmission of transaction data and supplemental data from a first money transfer application to a second money transfer application by a processing computer according to various embodiments.

[0012] Figure 3 Another flow chart illustrating the transmission of transaction data and supplemental data from a first money transfer application to a second money transfer application by a processing computer according to various embodiments.

[0013] Figure 4 An exemplary graphical user interface of a money transfer application executing on a user device and outputting supplemental data related to a transaction in accordance with various embodiments is shown.

[0014] Figure 5 Another exemplary graphical user interface of a money transfer application executing on a user device and outputting supplemental data related to a transaction in accordance with various embodiments is shown.

[0015] Figure 6 An exemplary graphical user interface of a money transfer application executing on a user device is shown including an exemplary visual cue for indicating received supplemental data related to a transaction in accordance with various embodiments.

[0016] Figure 7 A block diagram is shown of an exemplary user device in accordance with various embodiments.

[0017] Figure 8 A block diagram of an exemplary processing computer is shown in accordance with various embodiments. DETAILED DESCRIPTION

[0018] Embodiments allow a first digital wallet (e.g., a first money transfer application) executed on a first user device to send funds along with supplemental data to a second digital wallet (e.g., a second money transfer application executed on a second user device). For example, the supplemental data may include one or more of a text message, audio content, video content, a drawing, a photo, a multimedia file, etc. The supplemental data may be created on the first user device. According to various embodiments, the first digital wallet and the second digital wallet are managed by different wallet provider servers. The wallet provider servers of the first digital wallet and / or the second digital wallet do not support the transmission of the supplemental data. According to various embodiments, a processing computer located between the two money transfer applications (and the two wallet provider servers) facilitates the transmission of the supplemental data along with the funds. When an authorized entity processes a funds transfer, the processing computer generates an enhanced notification including the supplemental data and the transaction data. The processing computer transmits the enhanced notification to the second digital wallet, bypassing the wallet provider of the second digital wallet that may not support the transmission of the supplemental data.

[0019] In some embodiments, a first digital wallet executed on a user device of a sender may receive a digital tag of a recipient. The digital tag may represent a credential associated with the recipient. For example, the digital tag may be linked to a previously issued credential, such as a payment credential or a virtual credential issued by an authorized entity. Before contacting a processing computer regarding a funds transfer request (e.g., a transaction), the first digital wallet may transmit a message to a digital tag computer requesting the credential associated with the digital tag. The digital tag computer may return the credential to a first transfer application. The first transfer application may then generate a transfer request message including transfer data, the recipient's credential, and supplemental data. The transfer request message may also include the digital tag or other credentials of the sender.

[0020] Before discussing the embodiments of the present disclosure, some terms may be described in further detail.

[0021] A "user" may include an individual. In some embodiments, a user may be associated with one or more individual accounts and / or mobile devices. In some embodiments, a user may also be referred to as a cardholder, account holder, or consumer. A first user may be referred to as a sender, who may send funds to a second user, who may be referred to as a recipient.

[0022] A "user device" may be any suitable device with which a user can interact (e.g., a payment card, a mobile phone, a smart device). The user device may take any suitable form. Some examples of user devices include cards with magnetic stripes or contactless elements (e.g., including contactless chips and antennas) (e.g., payment cards such as credit cards, debit cards, and prepaid cards), cellular phones, PDAs, personal computers (PCs), tablet computers, wearable devices, etc. In some embodiments, where the user device is a mobile device, the mobile device may include input components (e.g., cameras, microphones, etc.), output components (e.g., displays, speakers, vibration mechanisms, etc.), memory, processors, computer-readable media, and any other suitable components.

[0023] An "authorizing entity" may be an entity that authorizes a request. Examples of an authorizing entity may be an issuer, a government agency, a document repository, an access administrator, etc. An "issuer" may generally refer to a commercial entity (e.g., a bank) that maintains a user account. An issuer may also issue a payment credential to a customer that is stored on a user device such as a cell phone, smart card, tablet computer, or laptop computer.

[0024] A "mobile device" (sometimes referred to as a mobile communication device) may include any suitable electronic device that a user can transport and operate, which may also provide remote communication capabilities with a network. A mobile communication device may communicate using a mobile phone (wireless) network, a wireless data network (e.g., 3G, 4G, or similar network), Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), Wi-Max, or any other communication medium that may provide access to a network (e.g., the Internet or a private network). Examples of mobile devices include mobile phones (e.g., cellular phones), PDAs, tablet computers, netbooks, laptop computers, wearable devices (e.g., watches), vehicles such as cars and motorcycles, personal music players, handheld dedicated readers, and the like. A mobile device may include any suitable hardware and software for performing such functions, and may also include multiple devices or components (e.g., when a device remotely accesses a network by being tethered to another device (i.e., using the other device as a modem), two devices used together may be considered a single mobile device).

[0025] A "digital wallet" may include an electronic device that allows a person to conduct e-commerce transactions. A digital wallet may store user profile information, payment credentials, bank account information, one or more digital wallet identifiers, etc., and may be used in a variety of transactions, such as, but not limited to, e-commerce, social networking, transfers / personal payments, mobile commerce, proximity payments, gaming, etc., for retail purchases, digital goods purchases, utility payments, purchases of games or game points from gaming websites, transfers of funds between users, etc. A digital wallet may be designed to simplify the purchase and payment process. A digital wallet may allow a user to load one or more payment cards onto a digital wallet to make payments without having to enter an account number or present a physical card. A digital wallet may be a money transfer application.

[0026] A "token" may be a substitute value for a credential. A token may be a string of numbers, letters, or any other suitable characters. Examples of tokens include payment tokens, access tokens, personal identification tokens, etc.

[0027] A “payment token” may include an identifier for a payment account that is a substitute for an account identifier such as a primary account number (PAN). For example, a payment token may include a series of alphanumeric characters that can be used as a substitute for an original account identifier. For example, the token “4900 0000 0000 0001” can be used in place of the PAN “4147 0900 0000 1234”. In some embodiments, a payment token may be “format-retained” and may have a digital format that conforms to account identifiers used in existing transaction processing networks (e.g., the ISO 8583 financial transaction message format). In some embodiments, a payment token may be used in place of a PAN to initiate, authorize, settle, or resolve a payment transaction, or to represent an original credential in other systems where an original credential would normally be provided. In some embodiments, a payment token may be generated so that recovery of the original PAN or other account identifier from the token value may not be derived computationally. Additionally, in some embodiments, the token format may be configured to allow an entity receiving the token to identify it as a token and to identify the entity that issued the token.

[0028] "Tokenization" is the process of replacing data with substitute data. For example, a payment account identifier (e.g., a primary account number (PAN)) can be tokenized by replacing the primary account identifier with a substitute symbol (e.g., a token) that can be associated with the payment account identifier. In addition, tokenization can be applied to any other information that can be replaced with a substitute value (i.e., a token). Tokenization improves transaction efficiency and security.

[0029] A "digital tag" may be a unique identifier used to facilitate transfers. A digital tag may be a set of alphanumeric characters associated with a user. A digital tag may be a payment tag that refers to a virtual credential issued by an authorized entity and linked to an account registered with a peer-to-peer application. The virtual credential may be in the form of a real payment credential, but unlike a real payment credential, it cannot be used to independently conduct a payment transaction.

[0030] A "transfer application" (e.g., a peer-to-peer application, a digital wallet application, etc.) accessed by a user operating a user device (e.g., installed, accessed via a web browser, etc.) may allow a user of the application to send transfers, receive transfers from other users of the application, or request transfers from other users of the application. The transfer application may be maintained, managed, and / or provided by an application provider server. For example, a first user may use a transfer application on his or her user device to generate a transfer request (e.g., request to receive $20 from a second user, request data from a second user, etc.). The transfer request may include a transfer amount and an alias associated with the second user. The alias may be a digital tag that uniquely identifies the second user in different transfer applications via a digital tag computer. In some embodiments, the digital tag may be a payment tag, and the digital tag computer may be a payment tag service computer. The digital tag may be issued by an authorized entity and registered with the digital tag computer for transfers.

[0031] Figure 1 Two user devices are shown, each storing one or more applications interacting through a processing computer according to various embodiments. In an exemplary person-to-person money transfer method, a first user 100 (e.g., a sender) may choose to send funds to a second user 120 (e.g., a receiver). The first user 100 may select one of a plurality of money transfer applications 104, 106, 108, 110 installed on the first user device 102 (e.g., one of a plurality of digital wallets) to conduct a transaction (e.g., transfer funds). The second user may select one of a plurality of money transfer applications 124, 126, 128, 130 installed on the second user device 122 (e.g., one of a plurality of digital wallets) to receive funds. The first money transfer application 104 used by the first user 100 may be different from the second money transfer application 124 used by the second user 120. That is, the first money transfer application 104 used by the first user 100 may be provided and / or managed by a first application provider server that is different from a second application provider server that manages the second money transfer application 124 used by the second user 120 .

[0032] In some embodiments, transactions may be simplified by using digital tags. The first transfer application 104 of the first user 100 may receive the digital tag of the second user 120. The first transfer application 104 may provide the digital tag to the digital tag computer 150, which may retrieve the credentials associated with the digital tag from the secure database 155. The digital tag computer 150 may return the credentials (for the second user 120) to the first transfer application 104.

[0033] In some embodiments, the digital tag computer 150 and the processing computer 160 may be part of the same transaction processing network 170, or may be managed by the same entity. The digital tag computer 150 and the processing computer 160 may exchange messages or data over an internal communication network, via a proprietary API, or the like.

[0034] The first user 100 may launch a first money transfer application 104 on the first user device 102. The first user 100 may enter transaction data, such as an account identifier or digital tag of the recipient, and an amount to be transferred to the first money transfer application 104. The first money transfer application 104 may allow the first user 100 to generate supplemental data that may be sent with the funds transfer. For example, the first user 100 may use the first user device to create a text message, an audio recording, a video message, etc. in conjunction with the transfer request.

[0035] During a money transfer transaction, the first money transfer application 104 of the first user 100 may transmit an enhanced money transfer message including transaction data and supplemental data to the processing computer 160. The supplemental data may include one or more of a text message, an audio file, a video file, a photo, a multimedia file, etc. generated by the first user 100 on the first user device 102. For example, the supplemental data may be generated by using an input member (e.g., a camera, a microphone, a physical or digital keyboard) of the first user device 102. The processing computer 160 may retrieve the supplemental data from the enhanced money transfer message and store the supplemental data at the database 165 as associated with an element of the transaction data. The processing computer 160 may later identify the supplemental data after querying the database 165 using one or more elements of the transaction data. After storing the supplemental data at the database 165, the processing computer 160 may return a confirmation message to the first money transfer application 104 indicating that the supplemental data has been received and stored, and the first money transfer application 104 may continue with the money transfer transaction.

[0036] After receiving the confirmation message from the processing computer 160, the first money transfer application 104 may transmit a money transfer message including only the money transfer data (but not the supplementary data) to a transmission computer (e.g., the bank of the first user 100). The transmission computer may then generate a push request message (e.g., an original credit transaction (OCT) message) including the transaction data, and send the push request message to an authorization computer (e.g., the bank of the second user) via the processing computer, where the authorization computer may notify the second money transfer application 124 of the second user 120 of the transaction data inside the push request message. The authorization computer also notifies the processing computer 160, which then extracts the supplementary data and transmits the supplementary data together with the money transfer data to the second money transfer application 124.

[0037] In some cases, the push request message has a predetermined format and, due to its size and format requirements, can only store transaction data without supplemental data (e.g., any sender messages). For example, a push request message may store only transaction data, such as the transaction amount, date, and name of the receiving user.

[0038] In an embodiment of the present invention, the second transfer application 124 of the second user 200 may receive both transaction data and supplementary data in a transaction such as a funds transfer transaction. For example, after the authorization computer authorizes the transaction, the processing computer 160 may receive a notification of the authorization of the transaction and the transaction data from the authorization computer. The processing computer 160 may then query the database 165 using one or more elements of the transaction data to identify the supplementary data. The processing computer 160 may retrieve the supplementary data from the database 165 and generate an enhanced notification message including the transaction data and the supplementary data. The processing computer 160 may transmit the enhanced notification message to the second transfer application 124 of the second user 120. The supplementary data may then be outputted by the second transfer application 124 on the second user device 122. The second user 120 may access both the transaction data and the supplementary data on the second user device 122.

[0039] In some embodiments, the processing computer 160 may assign a tag or identifier to the transaction after storing the supplemental data at the database 165. The tag or identifier may then be used to locate the supplemental data associated with the transaction. The identifier may be inserted into a data field of messages exchanged between the processing computer 160, the first transfer application 104, the second transfer application 124, the transmitting computer, and / or the authorizing computer.

[0040] Figure 2A flow chart showing the transmission of transaction data and supplementary data from a first transfer application to a second transfer application by a processing computer according to various embodiments. A sender 202, a first transfer application 204 managed by a first application provider server 224, a transmission computer 206, a digital tag computer 208, a processing computer 210, an authorized entity computer 212, and a second transfer application 214 managed by a second application provider server 226 are shown and are in operable communication with each other. The first transfer application 204 may be installed and executed on a first user device of the sender 202, and the second transfer application 214 may be installed and executed on a second user device of the recipient.

[0041] In some embodiments, the first money transfer application 204 (e.g., a digital wallet) may be associated with the processing computer 210 (e.g., connected via an API). The first money transfer application 204 may also be associated with the transmission computer 206 (e.g., an acquirer bank) and may communicate with the first application provider server computer 224 (e.g., a first digital wallet server). The recipient (e.g., a second user) and the second money transfer application 214 (e.g., a digital wallet) may be associated with the authorization computer 212 (e.g., an issuer bank). The authorization computer 212 may operate a second application provider server 226 (e.g., a second digital wallet server) associated with the second money transfer application 214. In some embodiments, the second application provider server 226 may be operated by an entity different from the entity operating the authorization computer 212. The digital tag computer 208 and the processing computer 210 may be operated by the same entity, or may exist in the same transaction processing network 170.

[0042] In step S202, the sender 202 may initiate a person-to-person funds transfer by inputting an account identifier, such as a digital tag, of the recipient in a first transfer application 204 executed on a user device of the sender 202. Embodiments are not limited to the use of digital tags and may also be performed with different types of account identifiers, such as a primary account number (PAN), a payment token, etc. The person-to-person funds transfer is used to send a payment to the recipient. The sender 202 may input other transaction data, such as a transaction amount, and supplementary data into the first transfer application 204. The supplementary data may include any content generated by the sender 202. For example, the supplementary data may include one or more of a text message, an audio file, a video file, a drawing, a photo, a multimedia file, etc.

[0043] According to some embodiments, when entering transaction data in the first money transfer application 204, the first money transfer application 204 may prompt the user to create supplementary data and / or add supplementary data to the transfer request. The first money transfer application 204 may guide the user to create supplementary data and associate the supplementary data with the transaction data through one or more GUIs.

[0044] When a digital tag is used, the recipient may have registered the digital tag with the digital tag computer 208 prior to the transaction. The digital tag may be linked to a payment credential (primary account number) or payment token in a database (e.g., secure database 155) accessible to the digital tag computer 208. In some embodiments, the secure database 155 can only be accessed by the digital tag computer 208.

[0045] When the transaction data input into the first money transfer application 204 includes a digital tag, steps S204 - S206 may be performed.

[0046] In step S204 , the first money transfer application 104 may send the digital tag to the digital tag computer 150 .

[0047] The digital tag computer may store a mapping between the digital tag of the second user and the credentials associated with the second user. In step S206, upon receiving the digital tag, the digital tag computer 208 may identify the credentials at the secure database and retrieve the credentials from the secure database. The digital tag computer 208 may then transmit the credentials to the first transfer application 204 provided on the first user device.

[0048] In step S208, the first money transfer application 204 may send a first message (e.g., a processing request message, an enhanced transaction request message) including transaction data elements and supplemental data about the transaction to the processing computer 210. The transaction data elements may include one or more of the following: a payment token or payment credential associated with the second user (e.g., including a credential retrieved from a digital tag computer or any other credential associated with the second user's account), an account identifier of the sender (e.g., a digital tag or other account identifier of the sender), a reference number of the sender, an acquiring bank identification number (BIN) and / or a merchant verification value (MVV), a date and time of the transaction, etc. The supplemental data may include one or more of a note from the sender (e.g., "Thanks for the dinner!"), an audio file, a video file, a drawing, a photo, a multimedia file, or data embedded in a machine-readable code, which may be arbitrary in nature.

[0049] In step S210, the processing computer 210 may parse the processing request message (e.g., the enhanced transaction request message) to identify one or more fields storing data. The processing computer 210 may identify a data field storing the supplemental data and one or more data fields storing the transaction data. The processing computer 210 retrieves the supplemental data to store the supplemental data as associated with the transaction data element at the database. The processing computer 210 stores the transaction data element and the supplemental data associated with the transaction data element in the database. The processing computer 210 transmits a confirmation message to the first transfer application 204 confirming receipt of the supplemental data and the transaction data element. In some embodiments, the confirmation message does not include the supplemental data now stored in the database.

[0050] In some embodiments, a push request message for transferring funds indicated in the processing request message to a recipient account may be generated by the transmitting computer and transmitted to the processing computer 210. Steps S212-S214 embody these steps.

[0051] In step S212, the first money transfer application 204 may cooperate with the transmission computer 206 to generate a money transfer request message in the API format, and send the money transfer request message in the API format to the processing computer 210. Step S212 may not be initiated before the first money transfer application 204 receives a confirmation message from the processing computer 210 confirming the receipt of the supplementary data and the transaction data element. For example, receiving the confirmation message from the processing computer 210 may be a prerequisite for the first money transfer application 204 to initiate the process of generating the push request message.

[0052] In step S214, the transmission computer 206 may generate a push request message. The push request message may be in ISO8583 format. In some embodiments, the push request message may be an original credit transaction (OCT) request message. The push request message may include a transaction data element. Due to the size limitations and industry standard formats of the push request message, the supplemental data element may not be included in the push request message (e.g., the ISO 8583 format does not allow or does not include a data field for accepting the supplemental data described herein). For example, the sender's remarks may be too large to be stored in ISO format. The push request message (excluding the supplemental data) may be sent from the transmission computer 206 to the processing computer 210.

[0053] In step S216, the processing computer 210 may verify the push request message. If the sender's account credentials are a payment token, the processing computer 210 detokenizes the payment token to obtain the payment credentials. If the first user's credentials include a digital tag, the processing computer 210 may communicate with the digital tag computer 208 to obtain the account credentials of the first user (e.g., sender 202). The digital tag computer 208 may store a mapping between the first user's digital tag and the credentials associated with the first user at a second database. The digital tag computer 208 may identify the credentials at a secure database, retrieve the credentials from the secure database, and transmit the credentials to the processing computer 210. Later, the transaction is settled using funds debited to an account associated with the first user's credentials.

[0054] The push request message may conform to the format that the authorized entity is configured to process. The format may not include a data field configured to store or transmit supplementary data. For example, the push request message may be in ISO format. In some embodiments, the push request message may be an OCT authorization request message. In some embodiments, the processing computer 210 may also generate a unique identifier (e.g., a transaction ID) for the transaction, and may include the unique identifier in the push request message transmitted to the authorized entity computer 212. The push request message may include payment credentials, a unique identifier, transaction data elements, but does not include supplementary data. The supplementary data may also be stored in a database as associated with the unique identifier. The processing computer 210 may then send the push request message to the authorized entity computer 212.

[0055] In step S218 , the authorization entity computer 212 may verify the push request message and authorize the transaction.

[0056] In step S220 , after authorizing the transfer, the authorizing entity computer 212 may credit the recipient account associated with the second transfer application 214 for the transaction and notify the second transfer application 214 of the payment transfer.

[0057] In step S222, the authorization entity computer 212 may generate a push response message. The push response message may include an indication of the funds deposited into the recipient's account, a unique identifier (if applicable), and a transaction data element. The authorization entity computer 212 may send the push response message to the processing computer 210. The push response message may be in ISO format. In some embodiments, the push response message may be an OCT authorization response message.

[0058] In step S224, the processing computer 210 may generate a transfer response message (e.g., a transfer completion notification message) including elements of the push response message. The transfer response message may be in ISO format. In some embodiments, the transfer response message may be an OCT response message. The processing computer 210 may transmit the transfer response message to the transmission computer 206.

[0059] In step S226, the processing computer 210 may search its database for the supplementary data from step S210 by matching the transaction data elements or unique identifiers in the push response message with the transaction data elements or unique identifiers stored in its database. For example, the payment token or payment voucher, the sender's digital tag, the sender's reference number, the acquirer BIN and / or MVV, the date and time of the transaction, etc. in the push transfer response message may be used to identify a match with the corresponding transaction data stored by the processing computer 210 in step S210. The processing computer 210 may then identify and retrieve the corresponding supplementary data associated with the stored transaction data from the database. The processing computer 210 may then generate a notification message (e.g., an enhanced notification message) including the transaction data and the supplementary data. The processing computer 210 may then send the notification message to the second transfer application 214 without passing through the authorization entity computer 222. In some embodiments, the second application provider server 226 may not support the transmission of supplementary data. The processing computer 210 sends the notification message to the second transfer application 214, bypassing the second application provider server 226 (e.g., the second digital server). Outputting the supplemental data on the second user device in conjunction with a notification associated with the transaction (hereinafter in conjunction with Figure 4-6 further discussed).

[0060] In step S228, the transmission computer 206 may notify the first money transfer application 204 that the payment transfer is successful. In step S230, the first money transfer application 204 may notify the sender 202 that the payment transfer is successful.

[0061] In step S232, funds may be settled between the transmission computer 206 and the authorization entity computer 212 via conventional payment settlement (eg, via the processing computer 160).

[0062] Figure 3 A flow diagram is shown for obtaining transaction data and supplemental data from a processing computer during a transaction in accordance with various embodiments.

[0063] The first money transfer application 204 (e.g., a digital wallet) may be associated with the processing computer 210 (e.g., connected via an API). The first money transfer application 204 provided on a first user device of a first user (e.g., sender 202) may be managed by a first application provider server 224. The second money transfer application 214 (e.g., a digital wallet) provided on a second user device of a second user (e.g., receiver) may be managed by a second application provider server 226.

[0064] In step S302, the sender 202 may initiate a person-to-person funds transfer to send a payment to the recipient by entering the recipient's account identifier (e.g., digital tag, payment token, alias) in the first transfer application 204. The sender 202 may enter other transaction data such as the transaction amount, as well as supplementary data such as the sender's notes, audio messages, video messages, multimedia messages, photos, etc.

[0065] In step S304, the first transfer application 204 may generate a transfer request message including transaction data (e.g., the recipient's account identifier, the transaction amount) and supplementary data. The transfer request message may be in an API format. In some embodiments, the transfer request message may include an OCT request message transmitted using an API format. The transaction data may include the sender's account identifier, the sender's reference number, the acquirer's BIN and / or MVV, the date and time of the transaction, etc. The supplementary data may include one or more of a text message, an audio file, a video file, a photo, a multimedia file, etc. that may be generated by the sender 202. The first transfer application 204 may send the transfer request message to the processing computer 210.

[0066] In step S306, the processing computer 210 may verify the transfer request message and, if necessary, perform one or more of the following: parse the digital tag of the recipient to obtain a payment token or payment credential linked to the digital tag; detokenize the payment token to obtain the payment credential. The processing computer 210 may parse the transfer request message to identify one or more fields storing data. The processing computer 210 may identify a data field storing supplementary data and one or more fields storing transaction data elements. The processing computer 210 may retrieve the supplementary data to store the supplementary data as associated with the transaction data element at a database. The processing computer 210 stores the transaction data element and the supplementary data associated with the transaction data element in the database.

[0067] Other digital tag payment processes can be found in PCT / US2021 / 030145 filed on April 30, 2021, which is incorporated herein by reference in its entirety.

[0068] The processing computer 210 may use the OCT request message to generate a push request message that does not include the supplemental data. The push request message may be in ISO format. In some embodiments, the push request message may be an OCT authorization request message that does not include the supplemental data. Due to size limitations and / or format requirements of the transfer request message, the push request message may include payment credentials, transaction data elements, but not the supplemental data. For example, the supplemental data may be too large to be stored in ISO format. In fact, the ISO format may not include a data field configured to store the supplemental data. The processing computer 210 may send the push request message to the authorization entity computer 212.

[0069] Optionally, in some embodiments, the processing computer 210 may also generate a unique identifier (eg, a transaction ID) associated with the transaction and the push request message. The push request message may include the unique identifier as well as the payment credentials, the transaction data elements, but not the supplemental data.

[0070] Steps S308 to S312 are similar to Figure 2 Steps S218 to S222 of the present invention are described above and will not be repeated here for the sake of brevity.

[0071] In step S314, the processing computer 210 may generate a transfer response message including elements of the push response message. The transfer response message may be in an API format. In some embodiments, the transfer response message may be an OCT response message. The processing computer 210 may send the transfer response message to the first transfer application 204 to notify the first transfer application 204 of the success of the transaction.

[0072] Steps S316 to S320 are similar to Figure 2 Steps S226, S230 and S232 are described above and will not be repeated here for the sake of brevity.

[0073] According to various embodiments, the supplementary data may be encrypted at the first transfer application and transmitted to the processing computer. The processing computer may not be granted the authority or ability to decrypt the supplementary data. Therefore, the processing computer may store the supplementary data at the database in encrypted form and transmit the supplementary data to the second transfer application in encrypted form. The first transfer application may share a decryption key with the second transfer application separately, or the second transfer application may be provided with a decryption key in advance for communications received from the first transfer application. The second transfer application may decrypt the encrypted supplementary data using the decryption key and output the decrypted supplementary data on the second user device.

[0074] In some embodiments, after successfully transmitting the supplemental data to the second money transfer application, the processing server may delete the supplemental data from the database.

[0075] Figure 4-5 An exemplary graphical user interface of a money transfer application executing on a recipient's user device and outputting supplemental data related to a transaction in accordance with various embodiments is shown.

[0076] like Figure 4 As shown in , a payment application 400 executed on a user device 402 of a recipient may display a graphical user interface showing a list of transactions including funds received and sent by a user. The user may provide user input to select a transaction 404 in the transaction to display additional information associated with the transaction. A second graphical user interface 406 may be displayed on the user device 402. The second graphical user interface 406 may include transaction elements, such as the identity of a sender 406A, a first transfer application 406B (which may be different from the payment application 400) used by the sender to send funds, an amount 406C received, and a time and date 406D of the transaction. In addition, the payment application 400 may also output the received supplementary data related to the selected transaction 404. For example, the supplementary data may be text 406F or graphic art that may be displayed on the second graphical user interface 406. In some embodiments, the supplementary data may include an audio file, a video file, or a multimedia file that may be played when the second graphical user interface 406 is displayed on the user device 402. The payment application 400 may be used to transfer funds and may include a widget 408 that initiates the transfer process.

[0077] Figure 5 A set of graphical user interfaces are shown that output supplemental data 500, 502 in various layouts.

[0078] Figure 6 An exemplary graphical user interface of a money transfer application executed on a user device according to various embodiments is shown, the exemplary graphical user interface including an exemplary visual cue for indicating received supplemental data associated with a transaction. The visual cue indicates the presence of supplemental data associated with a transaction displayed to the user as part of a list of transactions. For example, the graphical user interface may display a first transaction 610 showing a widget representing the sender and a brief summary of the transaction. The widget may include a visual cue 600 indicating the presence of supplemental data. Alternatively, a visual cue 604 may be displayed along with a summary of the transaction. Once the user selects the transaction, a second graphical user interface (e.g., Figure 4 and Figure 5 ), thereby showing all available transaction data and supplementary data associated with the transaction.

[0079] Figure 7 A block diagram is shown of an exemplary user device in accordance with various embodiments.

[0080] The user device 700 may include a processor 702 for processing the functions of the user device 700. The user device 700 may also include an input / output module 710, which includes elements coupled to the processor 702, such as a display, a speaker, a vibration mechanism, a camera, a microphone, a touch screen, a physical and / or digital keyboard, a biometric sensor, etc. According to various embodiments, the input / output module 710 can be used to create the supplemental data described herein. The user device 700 may also include a volatile memory 704 (e.g., RAM, DRAM, EEPROM, etc.) coupled to the processor 702, a non-transitory computer readable medium 708, a network interface 706, and a contactless element 718.

[0081] The computer-readable medium 708 may include one or more applications (e.g., a first transfer application 712 and a second transfer application 714). The computer-readable medium 708 may also include multiple functional modules, including an encryption module, a communication module, etc. The computer-readable medium 708 may include a communication module 716, which may include code that can be executed by the processor 702 to allow the user device 700 to communicate with other external devices.

[0082] The processor 702 may include any suitable data computing device or multiple data computing devices. The processor 702 is capable of interpreting code and executing instructions stored on the computer readable medium 708. The processor 702 may include a central processing unit (CPU) operating on a reduced instruction set, and may include a single-core or multi-core processor. The processor 702 may also include an arithmetic logic unit (ALU) and a cache memory.

[0083] In some embodiments, the contactless element 718 may be implemented in the form of a semiconductor chip (or other data storage element) having an associated wireless transmission (e.g., data transmission) element such as an antenna, etc. The contactless element can transmit and receive data using short-range wireless communication capabilities (e.g., NFC).

[0084] The computer-readable medium 708 may include code that can be executed by the processor 702 to implement the method of the embodiment. For example, the computer-readable medium 708 may include code that can be executed by the processor 702 to implement a method, the method comprising: receiving a notification message from a processing computer by a first digital wallet application 712 executed on the user device 700, the notification message including supplementary data and a result of a money transfer transaction, wherein the provider server managing the first digital wallet cannot support the transmission of the supplementary data; displaying a graphical user interface by the first digital wallet application 712 to display the result of the money transfer transaction; and outputting the supplementary data by the first digital wallet application 712 associated with the input / output module 710 of the user device 700 and displaying the result of the money transfer transaction, wherein the supplementary data includes one or more of text data, image data, audio data, multimedia data, or data embedded in a machine-readable code.

[0085] Figure 8 A block diagram illustrating an exemplary process in accordance with various embodiments.

[0086] The processing computer 800 includes a processor 802 for processing the functions of the processing computer 800. The processing computer 800 may also include a network interface 806, which may include an interface that may allow the processing computer 800 to communicate with an external device (e.g., an access device, an acquirer computer, an authorization entity, a money transfer application executed on a user device) and may be coupled to the processor 802. The processing computer 800 may also include a computer-readable medium 808 coupled to the processor 802.

[0087] The computer readable medium 810 may include a plurality of software modules. The modules may include a credential management module 808A, a data management module 808B, and a communication module 808C.

[0088] The credential management module 808A may include code executable by the processor 802 to retrieve, convert, and store account credentials, including digital tags, vouchers, real credentials, payment tokens.

[0089] The data management module 808B may include functions or codes executable by the processor 802 to parse, identify, store, retrieve, and match the supplemental data with transaction data received in a message associated with a money transfer request.

[0090] The communication module 808C may include code executable by the processor 802 to allow the processing computer 800 to communicate with other external entities.

[0091] The computer-readable medium 808 may include code that can be executed by the processor 802 to implement the method of the embodiment. For example, the computer-readable medium 808 may include code that can be executed by the processor 802 to implement a method, the method comprising: receiving a processing request message from a digital wallet provided on a first user device, the processing request message including supplementary data and transaction data elements regarding a transaction between a first user operating the first user device and a second user operating a second user device; storing the supplementary data in a database as associated with the transaction data elements; transmitting a push request message to an authorized entity computer that holds an account of the second user, the push request message including the transaction data elements without the supplementary data, wherein the push request message complies with a format that the authorized entity is configured to process; receiving a push response from the authorized entity computer A method of transmitting the supplementary data to a digital wallet provided on a second user device and sending a push response message to the digital wallet, wherein the push response message includes the transaction data element; searching for the supplementary data in a database using one or more transaction data elements among the transaction data elements received in the push response message; identifying the supplementary data in the database based on a match between the one or more transaction data elements among the transaction data elements received in the push response message and one or more transaction data elements stored in the database; retrieving the supplementary data corresponding to the matched transaction data elements; generating a notification message including the supplementary data; and transmitting the notification message including the supplementary data to a digital wallet provided on a second user device, wherein the supplementary data is output on the second user device in conjunction with a notification associated with the transaction.

[0092] The above-described embodiments have many technical advantages. For example, the embodiments allow the transmission of supplementary data (e.g., arbitrary, user-generated) data and transaction data between different transfer applications. The supplementary data may include text data, audio data, video data, multimedia data, etc. The transmission of such supplementary data is a technical improvement because current peer-to-peer funds transfer applications cannot transmit such data across their existing platforms. Cross-platform transfer (cross-transfer) application transactions rely on exchanged ISO messages. ISO messages or any other fixed format type messages do not have a dedicated data field for transmitting the supplementary data described herein. The embodiments provide a processing computer operating between separate transfer applications, the processing computer can retrieve and store supplementary data until the transaction is processed, and extract the supplementary data and re-associate the supplementary data with the transaction data before sending an enhanced notification (e.g., a notification including transaction data and supplementary data) directly to the transfer application executed on the recipient device.

[0093] It should be understood that the present invention as described above can be implemented in the form of control logic using computer software (stored in a tangible physical medium) in a modular or integrated manner. Based on the disclosure and the teachings provided herein, those of ordinary skill in the art will know and understand other ways and / or methods of implementing the present invention using hardware and a combination of hardware and software.

[0094] Any software component or function described in this application can be implemented as software code executed by a processor using any suitable computer language such as Java, C, C++, C#, Objective-C, Swift, or a scripting language such as Perl or Python using, for example, conventional or object-oriented techniques. The software code can be stored as a series of instructions or commands on a computer-readable medium for storage and / or transmission, and suitable media include random access memory (RAM), read-only memory (ROM), magnetic media such as a hard drive or floppy disk, or optical media such as a compact disk (CD) or a digital versatile disk (DVD), flash memory, etc. The computer-readable medium can be any combination of such storage devices or transmission devices.

[0095] Such programs can also be encoded and transmitted using carrier signals suitable for transmitting via wired networks, optical networks and / or wireless networks that meet multiple protocols, including the Internet. Therefore, the computer-readable medium according to an embodiment of the present invention can be created using data signals encoded with such programs. The computer-readable medium encoded with program code can be encapsulated with compatible devices or (for example, downloaded via the Internet) provided separately from other devices. Any such computer-readable medium can reside on or in a single computer product (for example, hard disk drive, CD or entire computer system), and can be present on or in different computer products in a system or network. The computer system can include a monitor, a printer, or other suitable displays for providing any result mentioned herein to the user.

[0096] The above description is illustrative rather than restrictive. After reading this disclosure, many variations of the present invention will become apparent to those skilled in the art. Therefore, the scope of the present invention should not be determined with reference to the above description, but should be determined with reference to the pending claims together with their full scope or equivalents.

[0097] One or more features of any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the present invention.

[0098] As used herein, the use of "a," "an," or "the" is intended to mean "at least one" unless clearly indicated to the contrary.

Claims

1. A method comprising: receiving, by a processing computer, a processing request message from a digital wallet provided on a first user device, the processing request message including supplemental data and transaction data elements regarding a transaction between a first user operating the first user device and a second user operating a second user device; storing, by the processing computer, the supplemental data in a database as associated with the transaction data element; transmitting, by the processing computer, a push request message to an authorized entity computer holding an account for the second user, the push request message including the transaction data element without the supplemental data, wherein the push request message conforms to a format that the authorized entity computer is configured to process; receiving, by the processing computer, a push response message including the transaction data element from the authorization entity computer; searching, by the processing computer, the database for the supplemental data using one or more of the transaction data elements received in the push response message; identifying, by the processing computer, the supplemental data in the database based on a match between the one or more of the transaction data elements received in the push response message and one or more of the transaction data elements stored in the database; retrieving, by said processing computer, said supplemental data corresponding to the matching transaction data element; generating, by the processing computer, a notification message including the supplemental data; as well as The notification message including the supplemental data is transmitted by the processing computer to a digital wallet provided on the second user device, wherein the supplemental data is output on the second user device in conjunction with a notification associated with the transaction.

2. The method of claim 1, wherein the supplemental data comprises one or more of text data, image data, audio data, multimedia data, or data embedded in a machine-readable code.

3. The method according to claim 1, wherein the digital wallet provided on the second user device is a second digital wallet managed by a second digital wallet server, wherein the first digital wallet provided on the first user device is managed by a first digital wallet server, and wherein the first digital wallet server is different from the second digital wallet server.

4. The method of claim 3, wherein at least one of the first digital wallet server or the second digital wallet server is unable to support transmission of the supplemental data, and wherein transmission by the processing computer of the notification message including the supplemental data to the digital wallet provided on the second user device bypasses the second digital wallet server. 5 . The method according to claim 3 , wherein the first digital wallet is a first money transfer application preconfigured on the first user device, and the second digital wallet is a second money transfer application.

6. The method according to claim 1, further comprising: parsing, by the processing computer, the processing request message to identify one or more fields storing data; identifying, by the processing computer, a data field storing the supplemental data; as well as The supplemental data is retrieved by the processing computer to store the supplemental data at the database as associated with the transaction data element.

7. The method according to claim 1, further comprising: storing, at a secure database, by a digital tag computer in communication with the processing computer, a mapping between the digital tag of the second user and credentials associated with the second user; receiving, by the digital tag computer, the digital tag of the second user from the digital wallet provided on the first user device; identifying, by the digital tag computer, at the secure database, the credential associated with the second user; retrieving, by the digital tag computer, the credential associated with the second user from the secure database; as well as The credential associated with the second user is transmitted by the digital tag computer to the digital wallet provided on the first user device, wherein the transaction data element received at the processing computer includes the credential associated with the second user.

8. The method according to claim 7, further comprising: storing, at a secure database, by a digital tag computer in communication with the processing computer, a first mapping between the digital tag of the first user and a first credential associated with the first user; receiving, by the digital tag computer, the digital tag of the first user from the processing computer; identifying, by the digital tag computer, the first credential at the secure database; retrieving, by the digital tag computer, the first credential from the secure database; and The first credential is transmitted by the digital tag computer to the processing computer, wherein the transaction is settled using funds debited to an account associated with the first credential.

9. The method according to claim 1, further comprising: Before the processing computer transmits the push request message to the authorization entity computer: transmitting, by the processing computer, a confirmation message confirming receipt of the supplemental data and the transaction data element to the digital wallet provided on the first user device, wherein the confirmation message does not include the supplemental data, wherein the digital wallet provided on the first user device provides the transaction data element to a transmitting computer, wherein the transmitting computer generates the push request message including the transaction data element; as well as The push request message is received by the processing computer from the transmitting computer, the push request message including the transaction data element without the supplemental data.

10. The method according to claim 1, further comprising: The processing computer generates a transfer response message; as well as The processing computer transmits the transfer response message to the digital wallet provided on the first user device, wherein the transfer response message is output on the first user device.

11. A system comprising: a processing computer comprising one or more processors; and a non-transitory computer readable medium comprising code executable by the one or more processors for performing steps comprising: receiving a processing request message from a digital wallet provided on a first user device, the processing request message including supplemental data and a transaction data element regarding a transaction between a first user operating the first user device and a second user operating a second user device; storing the supplemental data in a database in association with the transaction data element; transmitting a push request message to an authorized entity computer holding an account of the second user, the push request message including the transaction data element without the supplemental data, wherein the push request message conforms to a format that the authorized entity computer is configured to process; receiving a push response message including the transaction data element from the authorization entity computer; searching the database for the supplemental data using one or more of the transaction data elements received in the push response message; identifying the supplemental data in the database based on a match between the one or more of the transaction data elements received in the push response message and one or more of the transaction data elements stored in the database; retrieving the supplementary data corresponding to the matching transaction data element; generating a notification message including the supplementary data; as well as The notification message including the supplemental data is transmitted to a digital wallet provided on the second user device, wherein the supplemental data is output on the second user device in conjunction with a notification associated with the transaction.

12. The system of claim 11, wherein the supplemental data comprises one or more of text data, image data, audio data, multimedia data, or data embedded in a machine-readable code.

13. The system of claim 11, wherein the digital wallet provided on the first user device is associated with a first money transfer application managed by a first application provider server, and the digital wallet provided on the second user device is associated with a second money transfer application managed by a second application provider server, wherein the second money transfer application is unable to support transmission of the supplementary data, and wherein transmission of the notification message including the supplementary data by the processing computer to the second money transfer application bypasses the second application provider server.

14. The system of claim 11, wherein the code, when executed by the one or more processors of the processing computer, performs the steps, the steps further comprising: parsing the processing request message to identify one or more fields for storing data; Identify a data field storing the supplemental data; as well as The supplemental data is retrieved to be stored at the database in association with the transaction data element.

15. The system of claim 11, further comprising: a digital tag computer in communication with the processing computer and another non-transitory computer-readable medium, the other non-transitory computer-readable medium comprising code executable by the digital tag computer for: storing, at a secure database, a mapping between the digital tag of the second user and credentials associated with the second user; receiving the digital tag of the second user from the digital wallet provided on the first user device; identifying, at the secure database, the credentials associated with the second user; retrieving the credentials associated with the second user from the secure database; as well as The credentials associated with the second user are transmitted to the digital wallet provided on the first user device, wherein the transaction data element received at the processing computer includes the credentials associated with the second user.

16. The system of claim 15, wherein the code executable by the digital tag computer further performs the following operations: storing, at a secure database, a mapping between the digital tag of the first user and a first credential associated with the first user; receiving the digital tag of the first user from the processing computer; identifying the first credential at the secure database; retrieving the first credential from the secure database; as well as The first voucher is transmitted to the processing computer, wherein the transaction is settled using funds debited to an account associated with the first voucher.

17. The system of claim 11, wherein the code, when executed by the one or more processors of the processing computer, performs the steps, the steps further comprising: Before transmitting the push request message to the authorization entity computer: transmitting a confirmation message confirming receipt of the supplemental data and the transaction data element to the digital wallet provided on the first user device, wherein the confirmation message does not include the supplemental data, wherein the digital wallet provided on the first user device provides the transaction data element to a transmitting computer, wherein the transmitting computer generates the push request message including the transaction data element; as well as The push request message is received from the transmitting computer, the push request message including the transaction data element without the supplemental data.

18. The system of claim 11, wherein the code, when executed by the one or more processors of the processing computer, performs the steps, the steps further comprising: Generate a transfer response message; as well as The transfer response message is transmitted to the digital wallet provided on the first user device, wherein the transfer response message is output on the first user device.

19. A method comprising: receiving, by a first digital wallet application executed on a first user device, a notification message including supplemental data and a result of a money transfer transaction from a processing computer, wherein a digital wallet provider server managing the first digital wallet application is unable to support transmission of the supplemental data; Displaying, by the first digital wallet application, a graphical user interface to display the result of the transfer transaction; as well as The first digital wallet application outputs the supplementary data and displays the result of the money transfer transaction, wherein the supplementary data includes one or more of text data, image data, audio data, multimedia data, or data embedded in a machine-readable code.

20. The method according to claim 19, further comprising: Receiving, by the first digital wallet application, a user input selecting the transfer transaction; Retrieving, by the first digital wallet application, additional information associated with the money transfer transaction from the digital wallet provider server that manages the first digital wallet application; displaying, by the first digital wallet application, a subsequent graphical user interface to display the additional information received from the digital wallet provider server that manages the first digital wallet application; as well as The supplemental data received from the processing computer is output by the first digital wallet application and the additional information received from the digital wallet provider server that manages the first digital wallet application is displayed.

Images