System and method for transferring transaction data between mobile devices

Abstract

A computer-implemented method for communicating transaction data between mobile devices is provided, including: registering account data associated with a merchant account as corresponding to short message service (SMS) device data associated with a point of sale (POS) device and registering account data associated with a user account as corresponding to SMS device data associated with a user device; receiving transaction data associated with a transaction from the POS device via an SMS communication connection, verifying that the POS device and the user device are registered; in response to determining that an account balance of the user account is greater than a transaction authorization limit, sending a first confirmation message associated with the transaction to the user device via the SMS communication connection to confirm the transaction; and in response to receiving a first confirmation response associated with the transaction via the SMS communication connection, processing the transaction data.

Description

Technical Field

[0001] This disclosure generally relates to transaction processing, and in some non-limiting aspects or embodiments, to systems, methods, and computer program products for transmitting transaction data between mobile devices. Background Technology

[0002] Mobile point-of-sale (POS) systems have been developed to enable individuals to process payment transactions. For example, a mobile POS system can connect to mobile devices such as tablets or smartphones, which are configured to connect via wired or wireless data connections (e.g., ...). Third-generation (3G) mobile networks, fourth-generation (4G) mobile networks, etc., transmit information to and from the Internet. Such mobile POS systems can read information from credit or debit cards and, in response, transmit this information, along with other transaction-specific data, to a remote system for processing via wired or wireless data connections.

[0003] However, similar to traditional POS systems, once a mobile POS system reads information from a credit or debit card, the transaction can be finalized by having the buyer, holding the card, enter additional requested information (e.g., a personal identification number (PIN) and / or signature) using their mobile device. Therefore, once payment information is transmitted to the POS terminal, communication with the buyer, particularly via the mobile device, can be limited. For example, transaction service providers, issuing institutions, and acquiring institutions may rely solely on information received at the mobile POS terminal while the buyer is present to verify the accuracy of the credit or debit card information. This reliance can increase transaction processing time, both at the POS terminal (while waiting for additional input from the user) and while the transaction service provider processes the transaction. Summary of the Invention

[0004] Therefore, systems, apparatuses, products, devices and / or methods for transmitting transaction data between mobile devices are disclosed that overcome some or all of the shortcomings of the prior art.

[0005] According to a non-limiting aspect or embodiment, a computer-implemented method for transmitting transaction data between mobile devices is provided, which may include: registering account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device using at least one processor; registering account data associated with a user account as corresponding to SMS device data associated with a user device using at least one processor; receiving transaction data associated with a transaction from the POS device via an SMS communication connection using at least one processor, the transaction data including: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verifying that the POS device and the user device are registered using at least one processor; based on determining using at least one processor that the account balance of the user account is greater than the transaction value, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection using at least one processor to confirm the transaction; and processing the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via an SMS communication connection using at least one processor.

[0006] In some non-limiting aspects or embodiments, the computer-implemented method may include: sending a second confirmation message associated with the transaction to the user device using at least one processor based on determining that the transaction authorization limit is greater than an authorization limit threshold; and confirming, using at least one processor, that the second confirmation response is valid before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0007] According to some non-limiting aspects or embodiments, registering account data associated with the account as corresponding to SMS device data associated with the user device may include registering confirmation data associated with the confirmation of the transaction using at least one processor, the confirmation data corresponding to the SMS device data associated with the user device.

[0008] In some non-limiting aspects or embodiments, the computer-implemented method may include determining, using at least one processor, that the second confirmation response message indicates that the transaction is valid, based on a comparison between the second confirmation response message and confirmation data corresponding to SMS device data associated with the user device received during the registration of the account data associated with the account.

[0009] According to some non-limiting aspects or embodiments, verifying that the POS device and the user device are registered may include: using at least one processor to determine that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and using at least one processor to determine that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0010] In some non-limiting aspects or embodiments, the computer-implemented method may include: sending a transaction parameter confirmation message using at least one processor based on receiving transaction data associated with the transaction; and sending a pre-authorization message associated with the transaction using at least one processor based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0011] According to some non-limiting aspects or embodiments, the computer-implemented method may include: based on receiving transaction data associated with the transaction, sending a pre-authorization request message associated with the transaction using at least one processor; and based on receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, sending a message associated with the transaction to the POS device using at least one processor, the message indicating that the transaction has not been authorized.

[0012] In some non-limiting aspects or embodiments, verifying that the POS device and the user device are registered may include, based on determining that at least one of the POS device and the user device is not registered, using at least one processor to send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0013] According to a non-limiting aspect or embodiment, a system for transmitting transaction data between mobile devices is provided, which may include: at least one processor programmed or configured to: register account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device; register account data associated with a user account as corresponding to SMS device data associated with a user device; receive transaction data associated with a transaction from the POS device via an SMS communication connection, the transaction data including: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verify that the POS device and the user device are registered; based on determining, using at least one processor, that the account balance of the user account is greater than the transaction value, send a first confirmation message associated with the transaction to the user device via the SMS communication connection to confirm the transaction using at least one processor; and process the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via the SMS communication connection using at least one processor.

[0014] In some non-limiting aspects or embodiments, the at least one processor may be further programmed or configured to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction authorization limit is greater than the authorization limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving the second confirmation response message associated with the transaction.

[0015] According to some non-limiting aspects or embodiments, when account data associated with the account is registered as corresponding to SMS device data associated with the user device, the at least one processor may be programmed or configured to register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with the user device.

[0016] In some non-limiting aspects or embodiments, the at least one processor may be further programmed or configured to determine, based on a comparison of the second confirmation response message with confirmation data corresponding to the SMS device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates the transaction is valid.

[0017] According to some non-limiting aspects or embodiments, the at least one processor may be further programmed or configured to: determine that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0018] In some non-limiting aspects or embodiments, the at least one processor may be further programmed or configured to: send a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and send a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0019] According to some non-limiting aspects or embodiments, the at least one processor may be further programmed or configured to: send a pre-authorization request message associated with the transaction based on receiving transaction data associated with the transaction; and send a message associated with the transaction to the POS device in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, the message indicating that the transaction has not been authorized.

[0020] In some non-limiting aspects or embodiments, when verifying that the POS device and the user device are registered, the at least one processor may be programmed or configured to: based on determining that at least one of the POS device and the user device is not registered, send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0021] According to a non-limiting aspect or embodiment, a computer program product for transmitting transaction data between mobile devices is provided. The computer program product includes at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium including one or more instructions, which, when executed by at least one processor, cause the at least one processor to perform the following operations: registering account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device; registering account data associated with a user account as corresponding to SMS device data associated with a user device; and receiving transaction data associated with a transaction from the POS device via an SMS communication connection, the transaction data including... The process includes: SMS device data associated with the POS device, SMS device data associated with the user device, and parameter data associated with the transaction initiated by the POS device, the parameter data including a transaction value; verifying that the POS device and the user device are registered; based on determining that the user account's balance is greater than the transaction value using at least one processor, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection using at least one processor to confirm the transaction; and processing the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via an SMS communication connection using at least one processor.

[0022] In some non-limiting aspects or embodiments, the one or more instructions may further cause the at least one processor to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction authorization limit is greater than the authorization limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving the second confirmation response message associated with the transaction.

[0023] According to some non-limiting aspects or embodiments, one or more instructions that cause the at least one processor to register account data associated with the account as corresponding to SMS device data associated with the user device cause the at least one processor to perform the following operation: register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with the user device.

[0024] In some non-limiting aspects or embodiments, the one or more instructions may further cause the at least one processor to determine, based on a comparison of the second confirmation response message with confirmation data corresponding to the SMS device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates that the transaction is valid.

[0025] According to some non-limiting aspects or embodiments, the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered may cause the at least one processor to perform the following operations: determine that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0026] In some non-limiting aspects or embodiments, the one or more instructions may further cause the at least one processor to perform the following operations: sending a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and sending a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0027] According to some non-limiting aspects or embodiments, the one or more instructions may further cause the at least one processor to perform the following operations: based on receiving the transaction data associated with the transaction, send a pre-authorization request message associated with the transaction; and in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, send a message associated with the transaction to the POS device, the message indicating that the transaction has not been authorized.

[0028] In some non-limiting aspects or embodiments, the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered may cause the at least one processor to send a message associated with the transaction indicating that the at least one of the POS device and the user device is not registered, based on the determination that at least one of the POS device and the user device is not registered.

[0029] Further non-limiting aspects or embodiments are set forth in the following numbered clauses:

[0030] Clause 1: A computer-implemented method for transmitting transaction data between mobile devices, the computer-implemented method comprising: registering account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device using at least one processor; registering account data associated with a user account as corresponding to SMS device data associated with a user device using at least one processor; receiving transaction data associated with a transaction from the POS device via an SMS communication connection using at least one processor, the transaction data including: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verifying that the POS device and the user device are registered using at least one processor; based on determining using at least one processor that the account balance of the user account is greater than the transaction value, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection using at least one processor to confirm the transaction; and processing the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via an SMS communication connection using at least one processor.

[0031] Clause 2: The computer-implemented method according to Clause 1 further includes: sending a second confirmation message associated with the transaction to the user device using at least one processor based on determining that the transaction authorization limit is greater than an authorization limit threshold; and confirming that the second confirmation response is valid using at least one processor and before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0032] Clause 3: A computer-implemented method according to Clause 1 or 2, wherein registering account data associated with the account as corresponding to SMS device data associated with the user device further comprises: registering confirmation data associated with the confirmation of the transaction using at least one processor, the confirmation data corresponding to the SMS device data associated with the user device.

[0033] Clause 4: A computer-implemented method according to any one of Clauses 1 to 3, further comprising: determining, using at least one processor, that the second confirmation response message indicates that the transaction is valid, based on a comparison between the second confirmation response message and confirmation data corresponding to SMS device data associated with the user device received during the registration of the account data associated with the account.

[0034] Clause 5: A computer-implemented method according to any one of Clauses 1 to 4, wherein verifying that the POS device and the user device are registered further comprises: determining, using at least one processor, that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and determining, using at least one processor, that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0035] Clause 6: A computer-implemented method according to any one of Clauses 1 to 5, further comprising: sending a transaction parameter confirmation message using at least one processor based on receiving transaction data associated with the transaction; and sending a pre-authorization message associated with the transaction using at least one processor based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0036] Clause 7: A computer-implemented method according to any one of Clauses 1 to 6, further comprising: based on receiving transaction data associated with the transaction, sending a pre-authorization request message associated with the transaction using at least one processor; and in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, sending a message associated with the transaction to the POS device using at least one processor, the message indicating that the transaction has not been authorized.

[0037] Clause 8: A computer-implemented method according to any one of Clauses 1 to 7, wherein verifying that the POS device and the user device are registered further comprises: based on determining that at least one of the POS device and the user device is not registered, using at least one processor to send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0038] Clause 9: A system for transmitting transaction data between mobile devices, the system comprising: at least one processor programmed or configured to: register account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device; register account data associated with a user account as corresponding to SMS device data associated with a user device; receive transaction data associated with a transaction from the POS device via an SMS communication connection, the transaction data including: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verify that the POS device and the user device are registered; based on determining, using at least one processor, that the account balance of the user account is greater than the transaction value, send a first confirmation message associated with the transaction to the user device via the SMS communication connection to confirm the transaction using at least one processor; and process the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via the SMS communication connection using at least one processor.

[0039] Clause 10: The system according to Clause 9, wherein the at least one processor is further programmed or configured to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction authorization limit is greater than an authorization limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0040] Clause 11: The system according to Clause 9 or 10, wherein, when account data associated with the account is registered as corresponding to SMS device data associated with the user device, the at least one processor is programmed or configured to: register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with the user device.

[0041] Clause 12: In any one of Clauses 9 to 11, the at least one processor is further programmed or configured to determine, based on a comparison of the second confirmation response message with confirmation data corresponding to SMS device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates that the transaction is valid.

[0042] Clause 13: A system according to any one of Clauses 9 to 12, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: determine that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0043] Clause 14: The system according to any one of Clauses 9 to 13, wherein the at least one processor is further programmed or configured to: send a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and send a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0044] Clause 15: The system according to any one of Clauses 9 to 14, wherein the at least one processor is further programmed or configured to: send a pre-authorization request message associated with the transaction based on receiving transaction data associated with the transaction; and send a message associated with the transaction to the POS device in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, the message indicating that the transaction has not been authorized.

[0045] Clause 16: A system according to any one of Clauses 9 to 15, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: based on determining that at least one of the POS device and the user device is not registered, send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0046] Clause 17: A computer program product for transmitting transaction data between mobile devices, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, the one or more instructions, when executed by at least one processor, causing the at least one processor to: register account data associated with a merchant account as corresponding to Short Message Service (SMS) device data associated with a point-of-sale (POS) device; register account data associated with a user account as corresponding to SMS device data associated with a user device; and receive transaction data associated with a transaction from the POS device via an SMS communication connection, the transaction data including: data related to the POS device... The transaction data includes the SMS device data associated with the OS device, the SMS device data associated with the user device, and parameter data associated with the transaction initiated by the POS device, the parameter data including the transaction value; verifying that the POS device and the user device are registered; based on determining that the user account's balance is greater than the transaction value using at least one processor, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection using at least one processor to confirm the transaction; and processing the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via an SMS communication connection using at least one processor.

[0047] Clause 18: The computer program product according to Clause 17, wherein the one or more instructions further cause the at least one processor to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction authorization limit is greater than the authorization limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving the second confirmation response message associated with the transaction.

[0048] Clause 19: A computer program product pursuant to Clause 17 or 18, wherein one or more instructions causing the at least one processor to register account data associated with the account as corresponding to SMS device data associated with the user device cause the at least one processor to perform the following operation: register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with the user device.

[0049] Clause 20: A computer program product pursuant to any one of Clauses 17 to 19, wherein one or more instructions further cause the at least one processor to: determine, based on a comparison of the second confirmation response message with confirmation data corresponding to the SMS device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates that the transaction is valid.

[0050] Clause 21: A computer program product pursuant to any one of Clauses 17 to 20, wherein the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered cause the at least one processor to perform the following operations: determine that the SMS device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the SMS device data associated with the user device corresponds to the account data associated with the user account.

[0051] Clause 22: A computer program product according to any one of Clauses 17 to 21, wherein the one or more instructions further cause the at least one processor to: send a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and send a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0052] Clause 23: A computer program product according to any one of Clauses 17 to 22, wherein the one or more instructions further cause the at least one processor to: send a pre-authorization request message associated with the transaction based on receiving transaction data associated with the transaction; and send a message associated with the transaction to the POS device in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, the message indicating that the transaction has not been authorized.

[0053] Clause 24: A computer program product pursuant to any one of Clauses 17 to 23, wherein the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered cause the at least one processor to perform the following operation: based on determining that at least one of the POS device and the user device is not registered, send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0054] Clause 25: A computer-implemented method for transmitting transaction data between mobile devices, the computer-implemented method comprising: registering account data associated with a merchant account as corresponding device data associated with a mobile point-of-sale (POS) device using at least one processor; registering account data associated with a user account as corresponding e-wallet device data associated with a user device using at least one processor; receiving transaction data associated with a transaction from the POS device via a data connection using at least one processor, the transaction data including: the device data associated with the POS device, the e-wallet device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verifying that the POS device and the user device are registered using at least one processor; based on determining using at least one processor that the account balance of the user account is greater than the transaction value, sending a first confirmation message associated with the transaction to the user device via a data connection using at least one processor to confirm the transaction; and processing the transaction data using at least one processor based on receiving a first confirmation response message associated with the transaction from the user device via a data connection using at least one processor.

[0055] Clause 26: The computer-implemented method according to Clause 25 further includes: sending a second confirmation message associated with the transaction to the user device using at least one processor based on determining that the transaction value is greater than an authorization limit threshold; and confirming, using at least one processor, that the second confirmation response is valid before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0056] Clause 27: A computer-implemented method according to Clause 25 or 26, wherein registering account data associated with the account as corresponding to e-wallet device data associated with the user device further comprises: registering confirmation data associated with confirmation of the transaction using at least one processor, the confirmation data corresponding to the e-wallet device data associated with the user device.

[0057] Clause 28: A computer-implemented method according to any one of Clauses 25 to 27, further comprising: determining, using at least one processor, that the second confirmation response message indicates that the transaction is valid, based on a comparison between the second confirmation response message and confirmation data corresponding to the e-wallet device data associated with the user device received during the registration of the account data associated with the account.

[0058] Clause 29: A computer-implemented method according to any one of Clauses 25 to 28, wherein verifying that the POS device and the user device are registered further comprises: determining, using at least one processor, that the e-wallet device data associated with the POS device corresponds to the account data associated with the merchant account; and determining, using at least one processor, that the e-wallet device data associated with the user device corresponds to the account data associated with the user account.

[0059] Clause 30: A computer-implemented method according to any one of Clauses 25 to 29, further comprising: sending a transaction parameter confirmation message using at least one processor based on receiving transaction data associated with the transaction; and sending a pre-authorization message associated with the transaction using at least one processor based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0060] Clause 31: A computer-implemented method according to any one of Clauses 25 to 30, further comprising: based on receiving transaction data associated with the transaction, sending a pre-authorization request message associated with the transaction using at least one processor; and in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, sending a message associated with the transaction to the POS device using at least one processor, the message indicating that the transaction has not been authorized.

[0061] Clause 32: A computer-implemented method according to any one of Clauses 25 to 31, wherein verifying that the POS device and the user device are registered further comprises: based on determining that at least one of the POS device and the user device is not registered, using at least one processor to send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0062] Clause 33: A system for transmitting transaction data between mobile devices, the system comprising: at least one processor programmed or configured to: register account data associated with a merchant account as corresponding to device data associated with a mobile point-of-sale (POS) device; register account data associated with a user account as corresponding to e-wallet device data associated with a user device; receive transaction data associated with a transaction from the POS device via a data connection, the transaction data including: the device data associated with the POS device, the e-wallet device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verify that the POS device and the user device are registered; based on determining that the user account's account balance is greater than the transaction value, send a first confirmation message associated with the transaction to the user device via the data connection to confirm the transaction; and process the transaction data based on receiving a first confirmation response message associated with the transaction from the user device via the data connection.

[0063] Clause 34: In the system according to Clause 33, wherein the at least one processor is further programmed or configured to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction value is greater than an authorized limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0064] Clause 35: In a system pursuant to Clause 33 or 34, wherein when account data associated with the account is registered as corresponding to e-wallet device data associated with the user device, the at least one processor is programmed or configured to: register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the e-wallet device data associated with the user device.

[0065] Clause 36: In a system pursuant to any one of Clauses 33 to 35, wherein the at least one processor is further programmed or configured to: determine, based on a comparison of the second confirmation response message with confirmation data corresponding to the e-wallet device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates that the transaction is valid.

[0066] Clause 37: A system according to any one of Clauses 33 to 36, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: determine that the e-wallet device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the e-wallet device data associated with the user device corresponds to the account data associated with the user account.

[0067] Clause 38: A system according to any one of Clauses 33 to 37, wherein the at least one processor is further programmed or configured to: send a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and send a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0068] Clause 39: A system according to any one of Clauses 33 to 38, wherein the at least one processor is further programmed or configured to: send a pre-authorization request message associated with the transaction based on receiving transaction data associated with the transaction; and send a message associated with the transaction to the POS device in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, the message indicating that the transaction has not been authorized.

[0069] Clause 40: A system pursuant to any one of Clauses 33 to 39, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: based on determining that at least one of the POS device and the user device is not registered, send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0070] Clause 41: A computer program product for transmitting transaction data between mobile devices, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, the one or more instructions, when executed by at least one processor, causing the at least one processor to perform the following operations: registering account data associated with a merchant account as corresponding to device data associated with a mobile point-of-sale (POS) device; registering account data associated with a user account as corresponding to e-wallet device data associated with a user device; receiving transaction data associated with a transaction from the POS device via a data connection, the transaction data including: the device data associated with the POS device, the e-wallet device data associated with the user device, and parameter data associated with the transaction, the transaction being initiated by the POS device, the parameter data including a transaction value; verifying that the POS device and the user device are registered; sending a first confirmation message associated with the transaction to the user device via the data connection to confirm the transaction based on determining that the account balance of the user account is greater than the transaction value; and processing the transaction data based on receiving a first confirmation response message associated with the transaction from the user device via the data connection.

[0071] Clause 42: The computer program product according to Clause 41, wherein one or more instructions further cause the at least one processor to: send a second confirmation message associated with the transaction to the user device based on determining that the transaction value is greater than an authorized limit threshold; and confirm that the second confirmation response is valid before processing the transaction data based on receiving a second confirmation response message associated with the transaction.

[0072] Clause 43: A computer program product pursuant to Clause 41 or 42, wherein one or more instructions causing the at least one processor to register account data associated with the account as corresponding to e-wallet device data associated with the user device cause the at least one processor to perform the following operation: register confirmation data associated with the confirmation of the transaction, the confirmation data corresponding to the e-wallet device data associated with the user device.

[0073] Clause 44: A computer program product pursuant to any one of Clauses 41 to 43, wherein one or more instructions further cause the at least one processor to determine, based on a comparison of the second confirmation response message with confirmation data corresponding to the e-wallet device data associated with the user device received during the registration of the account data associated with the account, that the second confirmation response message indicates that the transaction is valid.

[0074] Clause 45: A computer program product pursuant to any one of Clauses 41 to 44, wherein the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered cause the at least one processor to: determine that the e-wallet device data associated with the POS device corresponds to the account data associated with the merchant account; and determine that the e-wallet device data associated with the user device corresponds to the account data associated with the user account.

[0075] Clause 46: A computer program product pursuant to any one of Clauses 41 to 45, wherein the one or more instructions further cause the at least one processor to: send a transaction parameter confirmation message based on receiving transaction data associated with the transaction; and send a pre-authorization message associated with the transaction based on receiving a transaction parameter confirmation response message indicating that the transaction is authorized.

[0076] Clause 47: A computer program product according to any one of Clauses 41 to 46, wherein the one or more instructions further cause the at least one processor to: send a pre-authorization request message associated with the transaction based on receiving transaction data associated with the transaction; and send a message associated with the transaction to the POS device in response to receiving a pre-authorization response message associated with the transaction indicating that the transaction has not been authorized, the message indicating that the transaction has not been authorized.

[0077] Clause 48: A computer program product pursuant to any one of Clauses 41 to 47, wherein the one or more instructions that cause the at least one processor to verify that the POS device and the user device are registered cause the at least one processor to perform the following operation: based on determining that at least one of the POS device and the user device is not registered, send a message associated with the transaction indicating that at least one of the POS device and the user device is not registered to the at least one of the POS device and the user device.

[0078] These and other features and characteristics of this disclosure, as well as the operational methods and manufacturing economies of combinations of related structural elements and parts, will become more apparent when considered in conjunction with the accompanying drawings, all of which form part of this specification, wherein similar reference numerals in the drawings denote corresponding parts. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to be limiting of this disclosure. As used in the specification and claims, unless the context clearly specifies otherwise, the singular forms “a” and “say” include plural indicators. Attached Figure Description

[0079] Additional advantages and details of this disclosure are explained in more detail below with reference to exemplary embodiments illustrated in the accompanying drawings, in which:

[0080] Figure 1 This is a diagram of a non-limiting embodiment of a system for transmitting transaction data between mobile devices;

[0081] Figure 2 yes Figure 1 A diagram illustrating a non-limiting embodiment of the components of one or more devices;

[0082] Figure 3A and 3B It is a flowchart of the process used to transfer transaction data between mobile devices;

[0083] Figure 4 yes Figure 3A and 3B The diagram shows a non-limiting aspect of the process or an embodiment of the scheme.

[0084] Figure 5A and 5B yes Figure 3A and 3B The diagram shows a non-limiting aspect of the process or an embodiment of the scheme; and

[0085] Figure 6A and 6B yes Figure 3A and 3B The diagram illustrates a non-limiting aspect of the process or an embodiment of the scheme. Detailed Implementation

[0086] For descriptive purposes, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and their derivatives are intended to refer to the orientation of this disclosure as shown in the accompanying drawings. However, it should be understood that this disclosure may take various alternative variations and sequences of steps, except where explicitly specified otherwise. It should also be understood that the specific apparatus and processes illustrated in the drawings and described in the following description are merely exemplary embodiments or aspects of this disclosure. Therefore, unless otherwise indicated, specific dimensions and other physical characteristics associated with the embodiments or aspects of the embodiments disclosed herein should not be considered limiting.

[0087] The aspects, components, elements, structures, actions, steps, functions, instructions, etc., used herein should not be construed as critical or essential unless explicitly stated otherwise. Furthermore, as used herein, the article “a” is intended to include one or more items and is interchangeable with “one or more” and “at least one.” Additionally, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and is interchangeable with “one or more” or “at least one.” Where only one item is desired, the term “a” or similar language is used. Also, as used herein, the terms “having” and similar expressions are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.”

[0088] As used herein, the terms "communication" and "transmission" can refer to the receiving, accepting, sending, transmitting, providing, etc., of data (e.g., information, signals, messages, instructions, commands, etc.). Communication between one unit (e.g., a device, system, component of a device or system, combination thereof, etc.) and another unit means that the first unit is able to receive information directly or indirectly from and / or send (e.g., transmit) information to the other unit. This can refer to a direct or indirect connection that is inherently wired and / or wireless. Furthermore, although the transmitted information may be modified, processed, relayed, and / or routed between the first and second units, the two units can also communicate with each other. For example, the first unit can communicate with the second unit even if it passively receives information and does not actively send information to the second unit. As another example, the first unit can communicate with the second unit if at least one intermediate unit (e.g., a third unit located between the first and second units) processes information received from the first unit and sends the processed information to the second unit. In some non-limiting embodiments, a message can refer to a network data packet (e.g., a data packet, etc.) that includes data.

[0089] As used herein, the terms “issuer,” “issuer institution,” “issuer bank,” or “payment device issuer” can refer to one or more entities that provide accounts for payment transactions, such as credit card payment transactions and / or debit card payment transactions, to individuals (e.g., users, customers, etc.). For example, an issuer institution may provide a customer with an account identifier, such as a primary account number (PAN), that uniquely identifies one or more accounts associated with said customer. In some non-limiting embodiments, an issuer may be associated with a bank identification number (BIN) that uniquely identifies an issuer institution. As used herein, “issuer system” can refer to one or more computer systems operated by or on behalf of an issuer, such as a server executing one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing transactions.

[0090] As used herein, the term "account identifier" may include one or more types of identifiers associated with an account (e.g., a PAN associated with an account, a card number associated with an account, a payment card number associated with an account, a token associated with an account, etc.). In some non-limiting embodiments, the issuer may provide an account identifier (e.g., a PAN, a token, etc.) to a user (e.g., an account holder) that uniquely identifies one or more accounts associated with that user. The account identifier may be embodied in a payment device (e.g., a physical instrument used for making payment transactions, such as a payment card, credit card, debit card, gift card, etc.) and / or may be electronic information transmitted to the user, which the user can use for electronic payment transactions. In some non-limiting embodiments, the account identifier may be an original account identifier, wherein the original account identifier is provided to the user when an account associated with the account identifier is created. In some non-limiting embodiments, the account identifier may be a supplementary account identifier, which may include an account identifier provided to the user after the original account identifier has been provided to the user. For example, a supplementary account identifier may be provided to the user if the original account identifier has been forgotten, stolen, etc. In some non-limiting embodiments, the account identifier may be directly or indirectly associated with an issuing authority, such that the account identifier may be a token mapped to a PAN or other type of account identifier. The account identifier may be any combination of alphanumeric characters, characters, and / or symbols, etc.

[0091] As used herein, the term "token" can refer to an account identifier used as a substitute for or replacement of another account identifier (e.g., a PAN). A token can be associated with a PAN or another original account identifier in one or more data structures (e.g., one or more databases, etc.) such that the token can be used for payment transactions without directly using the original account identifier. In some non-limiting embodiments, an original account identifier such as a PAN can be associated with multiple tokens for different individuals or purposes. In some non-limiting embodiments, a token can be associated with a PAN or other account identifiers in one or more data structures such that the token can be used for transactions without directly using an account identifier such as a PAN. In some examples, an account identifier such as a PAN can be associated with multiple tokens for different uses or purposes.

[0092] As used herein, the term "merchant" can refer to one or more entities (e.g., operators of retail businesses) that provide goods and / or services and / or access to goods and / or services to users (e.g., customers, consumers) based on transactions such as payment transactions. As used herein, "merchant system" can refer to one or more computer systems operated by or on behalf of a merchant, such as servers executing one or more software applications. As used herein, the term "product" can refer to one or more goods and / or services provided by a merchant.

[0093] As used herein, "point-of-sale (POS) device" can refer to one or more devices that a merchant can use to conduct transactions (e.g., payment transactions) and / or process transactions. For example, a POS device may include one or more client devices. Alternatively or additionally, a POS device may include peripheral devices, card readers, scanning devices (e.g., barcode scanners), Communication receivers, near field communication (NFC) receivers, radio frequency identification (RFID) receivers and / or other contactless transceivers or receivers, contact-based receivers, payment terminals, etc. As used herein, the term "POS system" can refer to one or more client devices and / or peripheral devices used by a merchant to conduct transactions. For example, a POS system may include one or more POS devices, and / or other similar devices that can be used to conduct payment transactions. In some non-limiting embodiments, a POS system (e.g., a merchant POS system) may include one or more server computers programmed or configured to process online payment transactions via web pages, mobile applications, etc.

[0094] As used herein, the term "transaction service provider" can refer to an entity that receives transaction authorization requests from merchants or other entities and, in some cases, provides payment guarantees through an agreement between the transaction service provider and the issuing authority. For example, a transaction service provider may include a payment network, such as... American Or any other entity that processes transactions. As used herein, "trading service provider system" can refer to one or more computer systems operated by or on behalf of a trading service provider, such as a trading service provider system executing one or more software applications. A trading service provider system may include one or more processors, and in some non-limiting embodiments, may be operated by or on behalf of a trading service provider.

[0095] As used herein, the term "acquiring party" can refer to an entity authorized and approved by a transaction service provider to initiate transactions (e.g., payment transactions) involving payment devices associated with the transaction service provider. As used herein, the term "acquiring party system" can also refer to one or more computer systems, computer devices, etc., operated by or on behalf of the acquiring party. Transactions that an acquiring party can initiate may include payment transactions (e.g., purchases, Original Credit Transactions (OCT), Account Funds Transactions (AFT), etc.). In some non-limiting embodiments, the acquiring party may be authorized by the transaction service provider to contract with merchants or service providers to initiate transactions involving payment devices associated with the transaction service provider. The acquiring party may contract with payment service providers to enable them to provide sponsorships to merchants. The acquiring party may monitor the compliance of payment service providers in accordance with transaction service provider regulations. The acquiring party may conduct due diligence on payment service providers and ensure that appropriate due diligence occurs before contracting with sponsored merchants. The acquiring party may be responsible for all transaction service provider programs operated or sponsored by the acquiring party. The acquiring party may be responsible for the actions of its payment service provider, merchants sponsored by the payment service provider, etc. In some non-limiting embodiments, the acquiring party may be a financial institution, such as a bank.

[0096] As used herein, the term "payment gateway" can refer to an entity and / or a payment processing system operated by or on behalf of such an entity (e.g., a merchant service provider, payment service provider, payment servicer, payment servicer contracted with an acquirer, payment aggregator, etc.) that provides payment services (e.g., transaction service provider payment services, payment processing services, etc.) to one or more merchants. Payment services may be associated with the use of portable financial devices managed by a transaction service provider. As used herein, the term "payment gateway system" can refer to one or more computer systems, computer devices, servers, server clusters, etc., operated by or on behalf of a payment gateway.

[0097] As used herein, the terms “e-wallet,” “e-wallet mobile application,” and “digital wallet” can refer to one or more electronic devices configured to initiate and / or conduct transactions (e.g., payment transactions, electronic payment transactions, etc.), including one or more software applications. For example, an e-wallet may include a user device (e.g., a mobile device) executing the application and server-side software and / or a database for maintaining and providing the user device with data to be used during payment transactions. As used herein, the term “e-wallet provider” can include an entity that provides and / or maintains e-wallets and / or e-wallet mobile applications for users (e.g., customers). Examples of e-wallet providers include, but are not limited to, Google Wallet. TMAndroid Apple and Samsung In some non-limiting examples, a financial institution (e.g., an issuing institution) may be an e-wallet provider. As used herein, the term "e-wallet provider system" may refer to one or more computer systems, computer devices, servers, server groups, etc., operated by or on behalf of an e-wallet provider.

[0098] As used herein, the term "payment device" can refer to payment cards (such as credit or debit cards), gift cards, smart cards, smart media, pay cards, healthcare cards, wristbands, machine-readable media containing account information, keychain devices or pendants, RFID transponders, retailer discount or membership cards, etc. Payment devices may include volatile or non-volatile memory to store information (e.g., account identifiers, account holder's name, etc.).

[0099] As used herein, the term "computing device" can refer to one or more electronic devices configured to communicate directly or indirectly with or through one or more networks. A computing device can be a mobile or portable computing device, a desktop computer, a server, etc. Furthermore, the term "computer" can refer to any computing device that includes the necessary components for receiving, processing, and outputting data, and typically includes a display, processor, memory, input devices, and network interfaces. A "computing system" can include one or more computing devices or computers. An "application" or "application programming interface" (API) refers to computer code or other data ordered on a computer-readable medium that can be executed by a processor to facilitate interaction between software components, such as interaction between a client-side front-end and / or a server-side back-end for receiving data from a client. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUIs) with which a user can interact directly or indirectly (e.g., via a keyboard, mouse, touchscreen, etc.). Furthermore, multiple computers communicating directly or indirectly in a networked environment, such as servers or other computerized devices, such as an autonomous vehicle including a vehicle computing system, can constitute a "system" or "computing system."

[0100] As used herein, the terms "client" and "client device" can refer to one or more computing devices, such as processors, storage devices, and / or similar computer components that access services available from a server. In some non-limiting embodiments, "client device" can refer to one or more devices that facilitate payment transactions, such as POS devices and / or POS systems used by merchants. In some non-limiting embodiments, a client device can include electronic devices configured to communicate with one or more networks and / or facilitate payment transactions, such as, but not limited to, one or more desktop computers, one or more portable computers (e.g., tablet computers), one or more mobile devices (e.g., cellular phones, smartphones, PDAs, wearable devices such as watches, glasses, lenses, and / or clothing), and / or other similar devices. Furthermore, "client" can also refer to an entity that owns, utilizes, and / or operates a client device to facilitate payment transactions with a transaction service provider, such as a merchant.

[0101] As used herein, the term "server" may refer to one or more computing devices, such as processors, storage devices, and / or similar computer components, that communicate with client devices and / or other computing devices via networks such as the Internet or private networks, and in some examples, facilitate communication between other servers and / or client devices.

[0102] As used herein, the term "system" may refer to one or more computing devices or combinations of computing devices, such as, but not limited to, processors, servers, client devices, software applications, and / or other similar components. Furthermore, as used herein, references to "server" or "processor" may refer to the server and / or processor previously stated to perform the preceding steps or functions, different servers and / or processors, and / or combinations of servers and / or processors. For example, as used in the specification and claims, a first server and / or first processor stated to perform a first step or function may refer to the same or different servers and / or processors stated to perform a second step or function.

[0103] Improved systems, methods, and computer program products are provided for transmitting transaction data between mobile devices. In some non-limiting embodiments, user devices and POS devices may register with a transaction service provider system to enable the system to coordinate transactions between them. Among other steps, registration may include identifying a mapping between account data associated with an account (e.g., a consumer's or merchant's account) and device data associated with the device (e.g., a user device or a POS device). In this example, device data may include a unique device identifier (e.g., a phone number, a Media Access Control (MAC) address, etc.) associated with account data registered to the device by the transaction service provider system. Therefore, in situations where user devices or POS devices cannot communicate with each other (e.g., where one or another computing device can only communicate during a transaction via SMS messaging services while the other can only communicate via a data connection), the transaction service provider system can act as an intermediary and facilitate communication between them. This reduces and / or eliminates the need to revert to traditional transaction processing techniques (e.g., using banknotes and / or other paper-based financial instruments that may be more prone to misplacement, misreading, etc.) and allows for faster and more secure access to the systems used to execute transactions (e.g., transaction service provider systems).

[0104] Now for reference Figure 1 A diagram is shown of a system 100 for transmitting transaction data between mobile devices according to a non-limiting embodiment. Figure 1 As shown, system 100 includes user device 102, point-of-sale (POS) device 104, merchant system 106, payment gateway system 108, acquiring system 110, transaction service provider system 112, issuer system 114, and communication network 116. User device 102, POS device 104, merchant system 106, payment gateway system 108, acquiring system 110, transaction service provider system 112, and / or issuer system 114 can communicate via communication network 116 and / or one or more wired connections, wireless connections, or a combination of wired and wireless connections. Although Figure 1 All components of system 100 that communicate with communication network 116 are shown, but it should be understood that multiple communication networks may be used, and some components may not communicate through the same network.

[0105] User device 102 may include a computing device configured to communicate with POS device 104, merchant system 106, payment gateway system 108, acquirer system 110, transaction service provider system 112, and / or issuer system 114 via communication network 116 and / or other networks. User device 102 may be configured to communicate via short-range wireless communication connections (e.g., NFC communication connections, RFID communication connections, etc.). The user device 102 may send and / or receive data to and / or from the POS device 104 via a short message service (SMS) communication connection (e.g., a communication connection for sending and / or receiving SMS messages) and / or a data connection (e.g., a 2G, 3G, 4G, LTE network, etc., for sending and / or receiving data messages such as, but not limited to, Multimedia Messaging Service (MMS) messages). In some non-limiting embodiments, the user device 102 may be associated with a user (e.g., an individual operating the device). In some non-limiting embodiments, the user device 102 may be a payment device configured to communicate with the POS device 104 via a short-range wireless communication connection.

[0106] POS device 104 may include a computing device configured to communicate with user device 102, merchant system 106, payment gateway system 108, acquiring system 110, transaction service provider system 112, and / or issuing system 114 via communication network 116 and / or other networks. POS device 104 may be configured to send and / or receive data to and / or from user device 102 via a short-range wireless communication connection. In some non-limiting embodiments, POS device 104 may be configured to transmit data to and / or from user device 102, merchant system 106, payment gateway system 108, and / or transaction service provider system 112 via a Short Message Service (SMS) communication connection and / or data connection. In some non-limiting embodiments, POS device 104 may be associated with a merchant as described herein.

[0107] Merchant system 106 may include one or more computing devices configured to communicate with user device 102, POS device 104, payment gateway system 108, acquiring system 110, transaction service provider system 112, and / or issuing system 114 via communication network 116 and / or other networks. For example, merchant system 106 may include one or more computing devices configured to send and / or receive data to and / or from user device 102 and / or POS device 104 via communication network 116, such as servers, server groups, client devices, client device groups, and / or other similar devices. In some non-limiting embodiments, POS device 104 may be part of merchant system 106. In some non-limiting embodiments, merchant system 106 may be associated with a merchant as described herein.

[0108] Payment gateway system 108 may include one or more computing devices configured to communicate with user device 102, POS device 104, merchant system 106, acquiring system 110, transaction service provider system 112, and / or issuing system 114 via communication network 116 and / or other networks. For example, payment gateway system 108 may include servers, server clusters, and / or other similar devices. In some non-limiting embodiments, payment gateway system 108 may be configured to send and / or receive data to and / or from user device 102, POS device 104, and / or transaction service provider system 112 via SMS communication connections and / or data connections. In some non-limiting aspects or embodiments, payment gateway system 108 may be associated with a payment gateway as described herein.

[0109] Acquiring system 110 may include one or more computing devices configured to communicate with user device 102, POS device 104, merchant system 106, payment gateway system 108, transaction service provider system 112, and / or issuer system 114 via communication network 116 and / or other networks. For example, acquiring system 110 may include servers, server clusters, and / or other similar devices. In some non-limiting aspects or embodiments, acquiring system 110 may be associated with an acquiring party as described herein.

[0110] Transaction service provider system 112 may include one or more computing devices configured to communicate with user device 102, POS device 104, merchant system 106, payment gateway system 108, acquirer system 110, and / or issuer system 114 via communication network 116 and / or other networks. For example, transaction service provider system 112 may include servers (e.g., transaction processing servers), server clusters, and / or other similar devices. In some non-limiting aspects or embodiments, transaction service provider system 112 may be associated with a transaction service provider as described herein. In some non-limiting embodiments, transaction service provider system 112 may be configured to transmit data to and / or from user device 102, POS device 104, and / or payment gateway system 108 via SMS communication connections and / or data connections.

[0111] The issuer system 114 may include one or more computing devices capable of communicating with the user device 102, POS device 104, merchant system 106, payment gateway system 108, acquirer system 110, and / or transaction service provider system 112 via communication network 116 and / or other networks. For example, the issuer system 114 may include servers, server clusters, and / or other similar devices. In some non-limiting embodiments, the issuer system 114 may be associated with an issuing institution that issues payment accounts and / or instruments (e.g., credit accounts, debit accounts, credit cards, debit cards, etc.) to users (e.g., users associated with user device 102).

[0112] The communication network 116 may include one or more wired and / or wireless networks. For example, the communication network 116 may include cellular networks (e.g., Long Term Evolution (LTE) networks, third-generation (3G) networks, fourth-generation (4G) networks, Code Division Multiple Access (CDMA) networks, etc.), Public Land Mobile Networks (PLMN), Local Area Networks (LAN), Wide Area Networks (WAN), Metropolitan Area Networks (MAN), telephone networks (e.g., Public Switched Telephone Networks (PSTN), private networks, ad hoc networks, the Internet, the Internet, fiber-optic networks, cloud computing networks, etc.), and / or combinations of some or all of these or other types of networks.

[0113] Provided as an example Figure 1 The number and arrangement of systems, devices, and networks are shown. Additional systems, devices, and / or networks may exist, as may fewer systems, devices, and / or networks, different systems, devices, and / or networks, or networks that are integrated with... Figure 1 The systems, devices, and / or networks shown are arranged in different ways. Furthermore, they can be implemented within a single system or a single device. Figure 1 The two or more systems or devices shown, or Figure 1 The single system or device shown may be implemented as multiple distributed systems or devices. Alternatively, a group of systems or a group of devices of system 100 (e.g., one or more systems, one or more devices) may perform one or more functions described as being performed by another group of systems or another group of devices of system 100.

[0114] In some non-limiting aspects or embodiments, transaction data associated with a transaction may include transaction parameters associated with the transaction, such as a payment transaction initiated and / or conducted using a computing device (e.g., via an internet browser on the computing device), an e-wallet application, etc. Non-limiting examples of transaction parameters include: e-wallet card data associated with a payment device and / or account identifier; decision data associated with a decision (e.g., a decision to approve or reject a transaction authorization request); authorization data associated with an authorization response (e.g., an approved spending limit, an approved transaction value, etc.); PAN; authorization code (e.g., a PIN, a password, etc.); data associated with the transaction amount (e.g., an approved limit, a transaction value, etc.); data associated with the transaction date and time; data associated with a currency exchange rate; data associated with a merchant type (e.g., goods, groceries, fuel, etc.); data associated with the country of the acquiring institution; data associated with an identifier of the country associated with the payment device or account; data associated with a response code; data associated with a merchant identifier (e.g., a merchant name, a merchant location, etc.); data associated with the currency type corresponding to funds stored in association with the PAN; etc.

[0115] Now for reference Figure 2 The diagram illustrates example components of device 200. Device 200 may correspond to one or more devices of user device 102, one or more devices of POS device 104, one or more devices of merchant system 106, one or more devices of payment gateway system 108, one or more devices of acquiring system 110, one or more devices of transaction service provider system 112, one or more devices of issuing system 114, and / or one or more devices of communication network 116. In some non-limiting aspects or embodiments, one or more devices of user device 102, one or more devices of POS device 104, one or more devices of merchant system 106, one or more devices of payment gateway system 108, one or more devices of acquiring system 110, one or more devices of transaction service provider system 112, one or more devices of issuing system 114, and / or one or more devices of communication network 116 may include at least one device 200 and / or at least one component of device 200. Figure 2 As shown, the device 200 may include a bus 202, a processor 204, a memory 206, a storage component 208, an input component 210, an output component 212, and a communication interface 214.

[0116] Bus 202 may include components that enable communication between components of device 200. In some non-limiting aspects or embodiments, processor 204 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 204 may include processors (e.g., central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), etc.), microprocessors, digital signal processors (DSPs), and / or any processing component that can be programmed to perform functions (e.g., field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), etc.). Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by processor 204.

[0117] Storage component 208 may store information and / or software associated with the operation and use of device 200. For example, storage component 208 may include hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.), compressed optical disk (CD), digital versatile optical disk (DVD), floppy disk, cassette tape, magnetic tape and / or another type of computer-readable medium, and corresponding drives.

[0118] Input component 210 may include components that allow device 200 to receive information, such as via user input (e.g., touchscreen display, keyboard, keypad, mouse, buttons, switches, microphone, camera, etc.). Alternatively, input component 210 may include sensors for sensing information (e.g., Global Positioning System (GPS) components, accelerometers, gyroscopes, actuators, etc.). Output component 212 may include components that provide output information from device 200 (e.g., display, speaker, one or more light-emitting diodes (LEDs), etc.).

[0119] Communication interface 214 may include transceiver components (e.g., transceiver, separate receiver and transmitter, etc.) that enable device 200 to communicate with other devices, for example, via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 214 may allow device 200 to receive information from another device and / or provide information to another device. For example, communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, etc. Interfaces, cellular network interfaces, etc.

[0120] Apparatus 200 can perform one or more processes described herein. Apparatus 200 can perform these processes based on processor 204 executing software instructions stored in a computer-readable medium, such as memory 206 and / or storage component 208. Computer-readable medium (e.g., non-transient computer-readable medium) is defined herein as a non-transient memory device. A memory device includes memory space located within a single physical storage device or memory space extending across multiple physical storage devices.

[0121] Software instructions may be read from another computer-readable medium or from another device into memory 206 and / or storage component 208 via communication interface 214. When executed, the software instructions stored in memory 206 and / or storage component 208 may cause processor 204 to perform one or more processes described herein. Alternatively or additionally, hard-wired circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments or aspects described herein are not limited to any particular combination of hardware circuitry and software.

[0122] The memory 206 and / or storage component 208 may include a data storage device or one or more data structures (e.g., a database). The device 200 is capable of receiving information from the data storage device or one or more data structures in the memory 206 and / or storage component 208, storing information in the data storage device or one or more data structures, transmitting information to the data storage device or one or more data structures, or searching for information stored therein. For example, the information may include encrypted data, input data, output data, transaction data, account data, or any combination thereof.

[0123] Provided as an example Figure 2 The number and arrangement of components are shown. In some non-limiting aspects or embodiments, device 200 may include components related to... Figure 2 The components shown are those that are additional, fewer, different, or arranged differently compared to other components. Alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

[0124] Now for reference Figure 3A and 3B And continue to refer to Figure 1 A flowchart of a process 300 for transferring transaction data between mobile devices is shown. In some non-limiting embodiments, user device 102, POS device 104, and / or transaction service provider system 112 (see [link to documentation]) Figure 1The device may (e.g., wholly or partially) perform one or more steps and / or operations associated with process 300. In some non-limiting embodiments, another device or group of devices, separate from or including the merchant system 106, payment gateway system 108, acquiring system 110, and / or issuing system 114, may (e.g., wholly or partially) perform one or more of the steps and / or operations associated with process 300. In some non-limiting embodiments, user device 102 may be used as a POS device as described herein, and / or POS device 104 may be used as a user device as described herein.

[0125] As described herein, the phrase "push payment" can refer to a payment initiated by a first device (e.g., user device 102, POS device 104, etc.) to transfer funds from an account associated with the first device to an account associated with a second device (e.g., another of user device 102, POS device 104, etc.). Similarly, as described herein, the phrase "pull payment" can refer to a payment initiated by a first device (e.g., user device 102, POS device 104, etc.) to transfer funds from an account associated with a second device (e.g., another of user device 102, POS device 104, etc.) to an account associated with the first device. Therefore, in some non-limiting embodiments, both user device 102 and / or POS device 104 can initiate push or pull payments.

[0126] like Figure 3AAs shown, in step 302, process 300 may include registering user device 102 and POS device 104. In some non-limiting embodiments, transaction service provider system 112 may register user device 102 and POS device 104. For example, transaction service provider system 112 may receive account data associated with a user account (e.g., credit account, debit account, currency associated with a credit or debit account, etc.) and device data associated with user device 102 from user device 102, the device data including a unique device identifier (e.g., telephone number, Media Access Control (MAC) address, etc.). Similarly, transaction service provider system 112 may receive account data associated with a merchant account and device data associated with POS device 104 from POS device 104. In some non-limiting embodiments, a user owning user device 102 and / or a merchant associated with POS device 104 may (e.g., using user device 102, POS device 104, and / or another computing device capable of initiating a telephone call) initiate a telephone call to transaction service provider system 112 to register user device 102 and / or POS device 104. In such an example, the transaction service provider system 112 can receive account data and a unique device identifier from the user device 102 and / or the POS device 104 based on the input provided by the user and / or the merchant to the user device 102 and / or the POS device 104.

[0127] In some non-limiting embodiments, the transaction service provider system 112 may receive confirmation data associated with transaction confirmation from the user device 102 and / or the POS device 104. This confirmation data includes a unique verification code (e.g., a Personal Identification Number (PIN), a reservation code (e.g., a Card Verification Code (CVC), etc.), data associated with a Consumer Device Cardholder Verification Method (CDCVM), etc.). In this example, the transaction service provider system 112 may later compare the data received from the user device 102 and / or the POS device 104 during the transaction with the confirmation data received during the registration of the user device 102 and / or the POS device 104 to determine whether the individual operating the user device 102 and / or the POS device 104 is authorized to do so, and thus determine whether the transaction is valid. In some non-limiting embodiments, the transaction service provider system 112 may register an application with the user device 102 and / or the POS device 104. For example, the transaction service provider system 112 may register the application before or after the application is installed on the user device 102 and / or the POS device 104, and the application may be used to facilitate the transfer of data between the user device 102 and / or the POS device 104 during a transaction as described herein.

[0128] In some non-limiting embodiments, user device 102 and / or POS device 104 may register with issuer system 114. For example, an individual may provide device data associated with a user device to issuer system 114 (e.g., in person, via telephone call, etc.). In this example, issuer system 114 may associate the device data associated with the user device with account data associated with a user account. Alternatively, an individual may provide device data associated with a POS device to issuer system 114 (e.g., in person, via telephone call, etc.). In this example, issuer system 114 may associate the device data associated with the POS device with account data associated with a merchant account. In such examples, an individual registering device data with issuer system 114 may also register confirmation data associated with transaction confirmation with issuer system 114. Alternatively, issuer system 114 may associate the device data of user device 102 and / or POS device 104 with account tokens corresponding to user accounts and / or merchant accounts, respectively.

[0129] In some non-limiting embodiments, the transaction service provider system 112 may store account data associated with a user account in relation to device data associated with user device 102. Alternatively, in some non-limiting embodiments, the transaction service provider system 112 may store account data associated with a merchant account in relation to device data associated with POS device 104. Since account data is stored in relation to device data of both user device 102 and POS device 104, the transaction service provider system 112 can determine that account data associated with a user account corresponds to device data associated with the user device, and / or account data associated with a merchant account corresponds to device data associated with POS device 104. In some non-limiting embodiments, the transaction service provider system 112 may send an account token corresponding to a user's account data to user device 102, and / or send an account token corresponding to a merchant's account data to POS device 104.

[0130] like Figure 3AFurther, in step 304, process 300 may include receiving transaction data associated with the transaction. In some non-limiting embodiments, the transaction service provider system 112 may receive transaction data associated with the transaction from user device 102 and / or POS device 104. Transaction data associated with the transaction may include: device data associated with the device sending the transaction data (e.g., user device 102, POS device 104, etc.), device data associated with the device corresponding to the account to which funds are to be transferred (e.g., user device 102, POS device 104, etc.), and / or parameter data associated with the transaction (e.g., description of the purchased goods and / or services, value of the purchased goods and / or services, transaction value, etc.). In some non-limiting embodiments, user device 102 and / or POS device 104 may generate transaction data based on input received from user device 102 and / or POS device 104. In some non-limiting embodiments, user device 102 and / or POS device 104 may generate SMS messages and / or data messages and send them to the transaction service provider system 112. For example, user device 102 and / or POS device 104 may generate SMS messages and / or data messages and send them to transaction service provider system 112, wherein the SMS messages and / or data messages include transaction data associated with the transaction. In this example, user device 102 and / or POS device 104 may send SMS messages and / or data messages to transaction service provider system 112 via SMS communication connection and / or data communication, respectively.

[0131] In some non-limiting embodiments, before the transaction service provider system 112 receives transaction data, user device 102 and / or POS device 104 may communicate with each other via a short-range wireless communication connection and / or via a communication network 116 to exchange transaction data associated with the transaction. For example, user device 102 may establish a short-range wireless communication connection with POS device 104, and after establishment, send device data associated with user device 102 and / or transaction parameters associated with the transaction to POS device 104. In some non-limiting embodiments, user device 102 and / or POS device 104 may determine that another user device 102 and / or POS device 104 has not registered with the transaction service provider system 112. For example, user device 102 and / or POS device 104 may determine that another user device 102 and / or POS device 104 has not registered with the transaction service provider system 112 by sending transaction data associated with the transaction to the transaction service provider system 112. In this example, user device 102 and / or POS device 104 may receive a message from transaction service provider system 112 indicating that user device 102 and / or POS device 104 have not registered with transaction service provider system 112.

[0132] In some non-limiting embodiments, the transaction service provider system 112 may determine that a device associated with a transaction has not registered with the transaction service provider system 112 (e.g., user device 102 and / or POS device 104 has not registered with the transaction service provider system 112). For example, the transaction service provider system 112 may determine that user device 102 and / or POS device 104 has not registered with the transaction service provider system 112, and based on said determination, send a transaction-related message to user device 102 and / or POS device 104 to indicate that user device 102 and / or POS device 104 has not registered with the transaction service provider system 112. In some non-limiting embodiments, the transaction service provider system 112 may send a message including instructions on how to register with the transaction service provider system 112 based on the determination that the device has not registered with the transaction service provider system 112.

[0133] In some non-limiting embodiments, the transaction service provider system 112 may determine that an account corresponds to a transaction. For example, the transaction service provider system 112 may determine that an account corresponds to a transaction based on transaction data associated with the transaction received from the user device 102 or the POS device 104. In this example, the transaction service provider system 112 may determine that transaction authorization restrictions (e.g., the upper limit on the amount of funds that can be used to process a transaction) apply to the transaction.

[0134] like Figure 3AFurther, in step 306, process 300 may include determining whether there are sufficient funds to satisfy the transaction. In some non-limiting embodiments, the transaction service provider system 112 may determine whether there are sufficient funds to satisfy the transaction based on determining that a transaction authorization limit applies to the transaction. In some non-limiting embodiments, in order to determine that a transaction authorization limit applies to the transaction, the transaction service provider system 112 may send a pre-authorization request message to the issuer system 114 requesting the transaction authorization limit for the transaction, and may receive a pre-authorization response message including the transaction authorization limit based on sending the pre-authorization request message. Alternatively or additionally, sending a transaction-related pre-authorization request message to the issuer system 114 may cause the issuer system 114 to send a pre-authorization response message including an indication of the amount of funds available for the transaction. If the transaction service provider system 112 determines that there are sufficient funds to satisfy the transaction (e.g., the transaction authorization limit is greater than the transaction amount; "Yes" at step 306), a first confirmation message associated with confirmation of the transaction data may be sent. Alternatively, if the transaction service provider system 112 determines that there are insufficient funds to satisfy the transaction (e.g., the transaction authorization limit is less than the transaction amount; "No" at step 306), the transaction service provider system 112 may terminate the transaction in step 307. In some non-limiting embodiments, the transaction service provider system 112 may send a message indicating that the transaction has been terminated to the user device 102 and / or the POS device 104.

[0135] like Figure 3AFurther, in step 308, process 300 may include sending a first confirmation message associated with confirmation of transaction data associated with the transaction. In some non-limiting embodiments, the transaction service provider system 112 may send a first confirmation message associated with confirmation of the transaction to confirm that the transaction data is correct. For example, the transaction service provider system 112 may send a first confirmation message to user device 102 and / or POS device 104 to confirm that the transaction data is correct. In this example, user device 102 and / or POS device 104 may display prompts indicating whether the individual and / or merchant have entered transaction data correctly or incorrectly via user device 102 and / or POS device 104, respectively. For example, when the transaction service provider system 112 receives transaction data from POS device 104 associated with a transaction requesting the transfer of funds from an account associated with user device 102 to an account associated with POS device 104 (e.g., initiating a request to withdraw payment), the transaction service provider system 112 may generate a first confirmation message associated with confirmation of the transaction and send the first confirmation message to user device 102 to confirm that the transaction data is correct. Alternatively, for example, when the transaction service provider system 112 receives transaction data from the user device 102 associated with a transaction requesting the transfer of funds from an account associated with the user device 102 to an account associated with the POS device 104 (e.g., initiating a push payment request), the transaction service provider system 112 may generate a first confirmation message associated with the confirmation of the transaction and send the first confirmation message to the POS device 104 to confirm that the transaction data is correct. In some non-limiting embodiments, the transaction service provider system 112 may send the first confirmation message as an SMS message and / or a data message to the user device 102 and / or the POS device 104, respectively, via an SMS communication connection and / or data communication.

[0136] In some non-limiting embodiments, a first confirmation response message associated with the confirmation of a transaction may be generated. For example, user device 102 and / or POS device 104 may generate a first confirmation response message associated with the confirmation of a transaction. In this example, user device 102 and / or POS device 104 may generate the first confirmation response message associated with the transaction based on an indication that the received transaction data is correct or incorrect. In such an example, user device 102 and / or POS device 104 may send the first confirmation response message to transaction service provider system 112.

[0137] like Figure 3AFurther, in step 310, process 300 may include receiving a first confirmation response message. In some non-limiting embodiments, the transaction service provider system 112 may receive the first confirmation response message, which indicates whether the transaction data is correct and, consequently, whether the transaction has been approved. In this example, the first confirmation message may be sent to the transaction service provider system 112 by the user device 102 or the POS device 104. In some non-limiting embodiments, the user device 102 or the POS device 104 may send the first confirmation response message as an SMS message and / or a data message to the transaction service provider system 112 via an SMS communication connection and / or data communication, respectively.

[0138] like Figure 3A Further, in step 312, process 300 may include determining whether the first confirmation response message confirms the transaction. In some non-limiting embodiments, the transaction service provider system 112 may determine that the first confirmation response message confirms the transaction. In some non-limiting embodiments, the transaction service provider system 112 may generate a message associated with the transaction based on the determination that the first confirmation response message confirms the transaction. For example, the transaction service provider system 112 may generate a message associated with the transaction indicating whether the transaction has been approved or not, and after generation, the message may be sent to the user device 102 and / or the POS device 104. As further shown in FIG3, in step 313, process 300 may include terminating the transaction. In some non-limiting embodiments, the transaction service provider system 112 may terminate the transaction based on the first confirmation response message.

[0139] like Figure 3B As shown, in step 314, process 300 may include determining whether a transaction is a high-value transaction. In some non-limiting embodiments, the transaction service provider system 112 may determine that a transaction is a high-value transaction (e.g., the transaction is associated with a transaction amount greater than a predetermined value). For example, in some non-limiting embodiments, the transaction service provider system 112 may determine that a transaction is a high-value transaction based on transaction parameters included in transaction data associated with the transaction. In some non-limiting embodiments, the transaction service provider system 112 may determine that a transaction is a high-value transaction based on receiving a first confirmation response message.

[0140] In some non-limiting embodiments, a second confirmation message may be generated associated with the transaction to confirm the identity of the individual operating the device during the transaction. For example, transaction service provider system 112 may generate the second confirmation message. In some non-limiting embodiments, transaction service provider system 112 may generate the second confirmation message based on determining that the transaction is a high-value transaction. In one such example, POS device 104 may send transaction data associated with a transaction requesting the transfer of funds from an account associated with a user to an account associated with a merchant (e.g., a pull request), and based on the received transaction data, transaction service provider system 112 may generate a second confirmation message to send to user device 102 to confirm the identity of the user operating user device 102. In another example, when user device 102 sends transaction data associated with a transaction requesting the transfer of funds from a user account to a merchant account (e.g., a push request), transaction service provider system 112 may generate a second confirmation message to send to user device 102 to confirm the identity of the individual operating user device 102.

[0141] In some non-limiting embodiments, the transaction service provider system 112 may generate a second confirmation message based on determining that one or more transactions that are not high-value transactions have been processed. For example, the transaction service provider system 112 may determine that one or more transactions processed within a predetermined period up to the current transaction meet a transaction threshold amount (e.g., a transaction amount less than, equal to, or greater than a predetermined amount). When the transaction service provider system 112 determines that one or more transactions processed within the predetermined period up to the current transaction meet the transaction threshold amount, the transaction service provider system 112 may generate a second confirmation message and send it to the user device 102 and / or the POS device 104. When the transaction service provider system 112 determines that one or more transactions processed within the predetermined period up to the current transaction do not meet the transaction threshold amount, the transaction service provider system 112 may not generate a second confirmation message.

[0142] In some non-limiting embodiments, the second confirmation message may include a request for data associated with the authentication of an individual. For example, the second confirmation message may include a request for data associated with the authentication of an individual operating a device that sends transaction data to the transaction service provider system 112. Alternatively, the second confirmation message may include a request for data associated with the authentication of an individual operating another device involved in the transaction (e.g., where the first device is POS device 104, which sends a request for funds from an account associated with a second device, such as user device 102), the second confirmation message may include a request for data associated with the authentication of an individual operating another device (e.g., user device 102). In some non-limiting embodiments, sending a request for data associated with the authentication of an individual may cause the receiving device to generate Consumer Device Cardholder Authentication Method (CDCVM) data and send the CDCVM data to the transaction service provider system 112. For example, the transaction service provider system 112 may send a request for data associated with the authentication of an individual operating user device 102. In this example, user device 102 may generate CDCVM data (e.g., the individual's fingerprint, password, etc.) associated with the identity of the individual operating user device 102. User device 102 can send CDCVM data to transaction service provider system 112 to verify the identity of the individual operating user device 102. Similarly, in some non-limiting embodiments, transaction service provider system 112 can send a request for data associated with the authentication of the individual operating POS device 104. In this example, POS device 104 can generate CDCVM data associated with the identity of the individual operating POS device 104. POS device 104 can send the CDCVM data to transaction service provider system 112 to verify the identity of the individual operating POS device 104.

[0143] like Figure 3BFurther, in step 316, process 300 may include sending a second confirmation message. In some non-limiting embodiments, the transaction service provider system 112 may send the second confirmation message associated with the transaction to user device 102 and / or POS device 104. In some non-limiting embodiments, user device 102 and / or POS device 104 may receive input and may generate confirmation data associated with the confirmation of the transaction based on the input. User device 102 and / or POS device 104 may then generate a second confirmation response message associated with the transaction, and the second confirmation response message may include confirmation data associated with the confirmation of the transaction. In some non-limiting embodiments, the transaction service provider system 112 may send the second confirmation message as an SMS message and / or data message to user device 102 and / or POS device 104 via SMS communication connection and / or data communication, respectively.

[0144] In some non-limiting embodiments, the confirmation data associated with transaction confirmation may include data associated with the identity of the individual operating the device. For example, in some non-limiting embodiments, the confirmation data may include data received as input at user device 102 and / or POS device 104, which may be used to identify the individual operating user device 102 and / or POS device 104. For a detailed description of verifying individual identity, please refer to PCT patent application No. PCT / GB2019 / 051011, filed April 5, 2019, the disclosure of which is incorporated herein by reference in its entirety.

[0145] In some non-limiting embodiments, sending the second confirmation message may include initiating a telephone call between the transaction service provider system 112 and the user device 102. For example, when the user device 102 and / or the POS device 104 are configured to communicate via an SMS communication connection, the transaction service provider system 112 may enable a telephone call (e.g., an automated call) to be initiated to the user device 102 and / or the POS device 104 to receive confirmation data associated with the confirmation of the transaction. In this example, the individual operating the user device 102 may communicate with the transaction service provider system 112 to provide confirmation data associated with the confirmation of the transaction to the transaction service provider system 112.

[0146] like Figure 3BFurther, in step 318, process 300 may include receiving a second confirmation response message associated with the transaction to confirm the transaction. In some non-limiting embodiments, the transaction service provider system 112 may receive the second confirmation response message from the user device 102 or the POS device 104. In this example, the second confirmation response message may include confirmation data associated with the confirmation of the transaction. In some non-limiting embodiments, the user device 102 or the POS device 104 may send the second confirmation response message as an SMS message and / or a data message to the transaction service provider system 112 via an SMS communication connection and / or data communication, respectively.

[0147] like Figure 3B Further, in step 320, process 300 may include determining whether a second confirmation response message associated with the transaction indicates that the transaction is valid. In some non-limiting embodiments, the transaction service provider system 112 may determine whether the second confirmation response indicates that the transaction is valid based on comparing the confirmation data included in the second confirmation response message with confirmation data received during the registration of the device sending the second confirmation response message. For example, to determine that the second confirmation response message is valid, the transaction service provider system 112 may compare the confirmation data included in the second confirmation response message received from user device 102 or POS device 104 with confirmation data received during the registration of user device 102 and / or POS device 104, respectively.

[0148] like Figure 3B Further, in step 321, process 300 may include terminating the transaction. In some non-limiting embodiments, the transaction service provider system 112 may terminate the transaction based on determining whether the transaction is valid. In this example, determining whether the transaction is valid may include comparing the confirmation data included in the second confirmation response message with confirmation data received during the registration of the device sending the second confirmation response. When the transaction service provider system 112 determines that the transaction is invalid, the transaction service provider system 112 may terminate the transaction.

[0149] In some non-limiting embodiments, the transaction service provider system 112 may resend the second confirmation message to the user device 102 and / or the POS device 104. For example, the transaction service provider system 112 may resend the second confirmation message to the user device 102 and / or the POS device 104 based on a determination of whether the transaction is valid based on the second confirmation response. In this example, the transaction service provider system 112 may receive another second confirmation response message and may determine whether the transaction is valid based on said other second confirmation response message.

[0150] As further shown in Figure 3, in step 322, process 300 may include processing a transaction. In some non-limiting embodiments, transaction service provider system 112 may process the transaction. For example, transaction service provider system 112 may process the transaction based on transaction data associated with the transaction. In this example, when processing a transaction, transaction service provider system 112 may generate an authorization request message associated with transaction authorization and send the authorization request message to issuer system 114 after generation. Issuer system 114 may generate an authorization response message including an indication of whether the transaction has been approved or not in response to receiving the authorization request message, and send the authorization response message to transaction service provider system 112.

[0151] As further shown in Figure 3, in step 324, process 300 may include sending a transaction confirmation message, which indicates whether the transaction was successfully processed or not. In some non-limiting embodiments, the transaction service provider system 112 may send the transaction confirmation message to the user device 102 and / or the POS device 104. For example, the transaction service provider system 112 may send the transaction confirmation message to the user device 102 and / or the POS device 104 based on receiving an authorization response message. The transaction confirmation message may indicate whether the transaction was approved or not. In some non-limiting embodiments, the transaction service provider system may send the transaction confirmation message as an SMS message and / or a data message to the user device 102 and / or the POS device 104 via an SMS communication connection and / or data communication, respectively.

[0152] In some non-limiting embodiments, electronic receipts can be sent. For example, POS device 104 can send an electronic receipt to user device 102. In this example, POS device 104 can send an electronic receipt after successfully processing a transaction. POS device 104 can send electronic receipts to an e-wallet on user device 102, and / or send electronic receipts from an e-wallet on POS device 104 and / or from an application running on POS device 104 to an application running on user device 102. In some non-limiting embodiments, when applications are installed on user device 102 and POS device 104 to manage the transfer of transaction data between the mobile devices, the applications can be configured to automatically send and / or receive electronic receipts after successfully processing a transaction.

[0153] In some non-limiting embodiments, the transaction service provider system 112 may send historical transaction data associated with one or more historical transactions to the user device 102 and / or the POS device 104. For example, in some non-limiting embodiments, the user device 102 and / or the POS device 104 may receive input indicating a request for historical transaction data associated with one or more historical transactions (e.g., one or more transactions used by the user device 102 and / or the POS device 104 to facilitate transactions). In some non-limiting embodiments, the user device 102 and / or the POS device 104 may send a request to the transaction service provider system 112 to cause the transaction service provider system 112 to send historical transaction data to the user device 102 and / or the POS device 104. Upon receipt, the user device 102 and / or the POS device 104 may display the historical transaction data associated with one or more transactions on the output components of the user device 102 and / or the POS device 104. In some non-limiting embodiments, the request may include a request for historical transaction data associated with one or more historical transactions, wherein the device requesting the historical transaction data is not a direct party (e.g., one or more POS devices 104 operating under the merchant's control, such as POS devices 104 assigned to one or more employees of the merchant). In some non-limiting embodiments, the transaction service provider system may send historical transaction data associated with one or more historical transactions to user device 102 and / or POS device 104 by including the historical transaction data associated with one or more historical transactions in SMS messages and / or data messages, which are sent to user device 102 and / or POS device 104 via SMS communication connections and / or data communications, respectively.

[0154] In some non-limiting embodiments, the transaction service provider system 112 may maintain reports on behalf of the POS device 104. For example, the transaction service provider system 112 may store data associated with one or more transactions processed using the POS device 104. In this example, the transaction service provider system 112 may generate one or more reports based on the data associated with the one or more processed transactions and send the reports to the POS device 104 and / or the merchant system 106 so that merchants operating the POS device 104 and / or the merchant system 106 can track payments for accounting purposes, as evidence of business activity when applying for credit, for use in trend analysis, and so on. In some non-limiting embodiments, another POS device 104a may maintain historical transaction data on behalf of one or more POS devices 104, and / or may generate one or more reports based on the historical transaction data of one or more POS devices 104.

[0155] Now for reference Figure 4 An embodiment 400 of a non-limiting example of a process for transmitting transaction data between mobile devices is shown. Figure 4 As shown, implementation scheme 400 includes user device 102, POS device 104, transaction service provider system 112 and issuer system 114.

[0156] like Figure 4 As indicated by reference numeral 402, user device 102 may register with transaction service provider system 112. During registration, user device 102 may send account data associated with the user account and device data associated with user device 102 to transaction service provider system 112. In response, transaction service provider system 112 may store the account data associated with the user account and the device data associated with user device 102 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, user device 102 may send confirmation data associated with confirmation of a transaction corresponding to user device 102, and the confirmation data may include a unique confirmation code. In some non-limiting embodiments, user device 102 may be used to initiate a telephone call to register with transaction service provider system 112 (e.g., via an automated registration system configured to receive account data via audio and / or digital input provided by the user at user device 102). In some non-limiting embodiments, in response to receiving account data associated with a user account and device data associated with user device 102, transaction service provider system 112 may generate and send an account token (e.g., as data or via telephone call), and the account token may be linked to the user account and the device data associated with user device 102. In some non-limiting embodiments, transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to user device 102.

[0157] like Figure 4As indicated by reference numeral 404, POS device 104 can register with transaction service provider system 112. During registration, POS device 104 may send account data associated with a merchant account and device data associated with POS device 104 to transaction service provider system 112. In response, transaction service provider system 112 may store the account data associated with the merchant account and the device data associated with POS device 104 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, POS device 104 may send confirmation data associated with confirmation of a transaction corresponding to POS device 104, the confirmation data including a unique confirmation code. In some non-limiting embodiments, POS device 104 may be used to initiate a telephone call to register with transaction service provider system 112 (e.g., via an automated registration system configured to receive account data via audio and / or digital input provided by a user at POS device 104). In some non-limiting embodiments, in response to receiving account data associated with a merchant account and device data associated with POS device 104, transaction service provider system 112 may generate and send an account token (e.g., as data or via telephone call), and the account token may be linked to the merchant account and the device data associated with POS device 104. In some non-limiting embodiments, transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to POS device 104.

[0158] Continue to refer to Figure 4 Referring to reference numerals 402 and 404, the transaction service provider system 112 can generate an account token for each device during registration. The account token can be linked to the account data of each corresponding device. In some non-limiting embodiments, the transaction service provider system 112 can provide confirmation data associated with the confirmation of a transaction to the user device 102 and / or the POS device 104 (e.g., the transaction service provider system 112 can generate confirmation data and send it to the user device 102 and / or the POS device 104).

[0159] like Figure 4As indicated by reference numeral 406, the transaction service provider system 112 can receive transaction data associated with a transaction from the POS device 104. The transaction data may include device data associated with the user device 102, device data associated with the POS device 104, and transaction parameters associated with the transaction from the POS device 104. The transaction service provider system 112 can generate a pre-authorization request message associated with the transaction based on the transaction data associated with the transaction. In some non-limiting embodiments, the transaction service provider system 112 can determine whether the POS device 104 and / or the user device 102 are registered, and if not registered, the transaction service provider system 112 can send a message to the POS device 104 and / or the user device 102 to prompt for registration.

[0160] like Figure 4 As shown by reference numeral 408, the transaction service provider system 112 may send a parameter confirmation message, including data associated with one or more parameters of a transaction, to the POS device 104 to verify the accuracy of the transaction parameters. For example, the transaction service provider system 112 may send the parameter confirmation message to the POS device 104 based on receiving transaction data associated with the transaction. In this example, the parameter confirmation message may request the return of a parameter confirmation response message indicating whether the transaction parameters associated with the transaction are accurate to the transaction service provider system 112.

[0161] like Figure 4 As indicated by reference numeral 410, the transaction service provider system 112 can receive a transaction parameter confirmation response message from the POS device 104. For example, the POS device 104 can generate a transaction parameter confirmation response message based on the received transaction parameter confirmation message, the transaction confirmation response message indicating whether the transaction parameters associated with the transaction are accurate. In some non-limiting embodiments, the transaction parameter confirmation response message can be generated based on input received at the POS device 104.

[0162] like Figure 4 As shown by reference numeral 412, the transaction service provider system 112 may send a pre-authorization request message to the issuer system 114. For example, in order to determine whether a transaction is permissible (e.g., there are sufficient funds to satisfy the transaction), the transaction service provider system 112 may send a pre-authorization request message to cause the issuer system 114 to generate a pre-authorization response message associated with the transaction, the pre-authorization response indicating whether there are sufficient funds to satisfy the transaction.

[0163] like Figure 4As shown by reference numeral 414, the transaction service provider system 112 receives a pre-authorization response message associated with a transaction. The pre-authorization response message may indicate whether there are sufficient funds to fulfill the transaction. In some non-limiting embodiments, the transaction service provider system 112 may generate a first confirmation message associated with the transaction based on the pre-authorization response message. In some non-limiting embodiments, when the pre-authorization response message indicates insufficient funds, the transaction service provider system 112 may send a message indicating insufficient funds to fulfill the transaction to the user device 102 and / or the POS device 104.

[0164] like Figure 4 As indicated by reference numeral 416, the transaction service provider system 112 may send a first confirmation message associated with a transaction to the user device 102 to confirm the transaction parameters. In some non-limiting embodiments, the transaction service provider system 112 may send the first confirmation message to the user device 102 via an SMS communication connection or a data connection. The user device 102 may generate a first confirmation response based on the first confirmation message. For example, the user device 102 may generate a display based on the first confirmation message to prompt the user to input an indication that the transaction has been accepted or not accepted. The user device 102 may receive input indicating that the transaction has been accepted or not accepted, and generate a first confirmation response message based on said input.

[0165] like Figure 4 As shown by reference numeral 418, the transaction service provider system 112 can receive a first confirmation response message. For example, user device 102 can send a first confirmation response message based on the user receiving input at user device 102 indicating acceptance of the transaction. In an example where the first confirmation response message indicates that the transaction has not been accepted, the transaction service provider system 112 can send a message indicating that the transaction has not been accepted to POS device 104.

[0166] like Figure 4 As indicated by reference numeral 420, the transaction service provider system 112 can determine that a transaction is a high-value transaction. For example, the transaction service provider system 112 can determine that a transaction is a high-value transaction based on transaction parameters of the transaction data. When a transaction is determined to be a high-value transaction (e.g., the transaction value is greater than or equal to a predetermined threshold), the transaction service provider system 112 can generate a second confirmation message associated with the transaction. Alternatively, when a transaction is determined to be a low-value transaction (e.g., the transaction value is less than or equal to a predetermined threshold), implementation 400 can proceed to reference numeral 426 and send an authorization request message to the issuer system 114.

[0167] like Figure 4As shown by reference numeral 422, the transaction service provider system 112 can send a second confirmation message to the user device 102. The transaction service provider system 112 can send the second confirmation message to the user device 102 based on determining that the transaction is a high-value transaction. The second confirmation message can be configured to cause the user device 102 to generate a second confirmation response message including confirmation data associated with the confirmation of the transaction. The user device 102 can generate the confirmation data associated with the confirmation of the transaction based on input received at the user device 102 (e.g., the input may include a unique confirmation code).

[0168] like Figure 4 As indicated by reference numeral 424, the transaction service provider system 112 can receive a second confirmation response message from the user device 102. For example, in some non-limiting embodiments, the transaction service provider system 112 may receive a second confirmation response message including confirmation data associated with confirmation of the transaction. The transaction service provider system 112 may determine that the confirmation data matches confirmation data corresponding to the user device 102 received during the registration of the user device 102 with the transaction service provider system. The transaction service provider system 112 may then generate an authorization request message associated with the transaction based on the transaction data, and then determine that the confirmation data matches confirmation data corresponding to the user device 102 received during the registration of the user device 102.

[0169] like Figure 4 As shown by reference numeral 426, the transaction service provider system 112 can send an authorization request message to the issuer system 114. In some non-limiting embodiments, the issuer system 114 can generate an authorization response message based on receiving the authorization request message.

[0170] like Figure 4 As indicated by reference numeral 428, the transaction service provider system 112 can receive an authorization response message from the issuer system 114. The authorization response message can indicate whether the transaction has been approved or not. In some non-limiting embodiments, when a transaction is determined to be a low-value transaction, an authorization request message can be generated based on the determination that the transaction is a low-value transaction, without requiring the transaction service provider system 112 to send a second confirmation message and receive a second confirmation response. In some non-limiting embodiments, the transaction service provider system 112 can send a message indicating whether the transaction has been approved or not to the user device 102 and / or the POS device 104.

[0171] Now for reference Figure 5A and 5B An embodiment 500 of a non-limiting example of a process for transmitting transaction data between mobile devices is shown. Figure 5A and 5BAs shown, implementation scheme 500 includes user device 102, POS device 104, transaction service provider system 112 and issuer system 114.

[0172] like Figure 5A As indicated by reference numeral 502, user device 102 may register with transaction service provider system 112. During registration, user device 102 may send account data associated with a user account and device data associated with user device 102 to transaction service provider system 112. In response, transaction service provider system 112 may store the account data associated with the user account and the device data associated with user device 102 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, user device 102 may send confirmation data associated with confirmation of a transaction corresponding to user device 102, the confirmation data including a unique confirmation code. In some non-limiting embodiments, user device 102 may be used to make a telephone call to register with transaction service provider system 112. In some non-limiting embodiments, in response to receiving account data associated with a user account and device data associated with user device 102, transaction service provider system 112 may generate an account token and send the account token (e.g., as data or via telephone call), the account token being linked to the user account and the device data associated with user device 102. In some non-limiting embodiments, the transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to the user device 102.

[0173] like Figure 5AAs indicated by reference numeral 504, POS device 104 can register with transaction service provider system 112. During registration, POS device 104 can send account data associated with a merchant account and device data associated with POS device 104 to transaction service provider system 112. In response, transaction service provider system 112 can store the account data associated with the merchant account and the device data associated with POS device 104 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, POS device 104 can send confirmation data associated with confirmation of a transaction corresponding to POS device 104, the confirmation data including a unique confirmation code. In some non-limiting embodiments, POS device 104 can be used to make a telephone call to register with transaction service provider system 112. In some non-limiting embodiments, in response to receiving account data associated with a merchant account and device data associated with POS device 104, transaction service provider system 112 can generate and send an account token (e.g., as data or via telephone call), and the account token can be linked to the merchant account and the device data associated with POS device 104. In some non-limiting embodiments, the transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to the POS device 104.

[0174] like Figure 5A As indicated by reference numeral 506, user device 102 can send transaction data associated with a transaction to transaction service provider system 112. For example, user device 102 can send transaction data to transaction service provider system 112 to initiate a transaction, the transaction data including device data associated with POS device 104, device data associated with user device 102, and transaction parameters associated with the transaction. Transaction service provider system 112 can generate a pre-authorization request associated with the transaction based on the transaction data received from user device 102.

[0175] like Figure 5AAs indicated by reference numeral 508, the transaction service provider system 112 may send a first confirmation message to the user device 102 to confirm a transaction (e.g., a push payment to withdraw funds from a user account corresponding to the user device 102 and transfer them to a merchant account corresponding to the POS device 104). The user device 102 may generate a first confirmation response message based on the first confirmation message, the first confirmation response message including data associated with an indication of whether the transaction was approved or not. For example, in some non-limiting embodiments, the user device 102 may generate a display based on the first confirmation message to allow the user to input an indication that the transaction was approved or not. The user device 102 may receive input and generate a first confirmation response message based on said input, including data indicating that the transaction was approved or not.

[0176] like Figure 5A As shown by reference numeral 510, the transaction service provider system 112 receives a first confirmation response message. For example, user device 102 may send the first confirmation response based on input received by the user at user device 102 indicating whether to accept or reject the transaction.

[0177] like Figure 5A As indicated by reference numeral 512, the transaction service provider system 112 may send a pre-authorization request message to the issuer system 114. For example, in order to determine whether a transaction can be processed (e.g., whether there are sufficient funds in the account to satisfy the transaction), the transaction service provider system 112 may send a pre-authorization request message to cause the issuer system 114 to generate a pre-authorization response message indicating whether there are sufficient funds in the account associated with the user device 102 to satisfy the transaction.

[0178] like Figure 5A As shown by reference numeral 514, the transaction service provider system 112 receives a pre-authorization response message, which includes data indicating whether the transaction has been approved or not. The transaction can be terminated when the pre-authorization response message indicates that there are insufficient funds to fulfill the transaction. In some non-limiting embodiments, when the pre-authorization response message indicates that there are insufficient funds to fulfill the transaction, the transaction service provider system 112 can send a message to the user device 102, the message including data indicating that there are insufficient funds to fulfill the transaction.

[0179] like Figure 5A As indicated by reference numeral 516, the transaction service provider system 112 can determine that a transaction is a high-value transaction. For example, the transaction service provider system 112 can determine that a transaction is a high-value transaction based on transaction parameters in the transaction data. Alternatively, when a transaction is determined to be a low-value transaction, implementation 500 can proceed to reference numeral 522 and send an authorization request message to the issuer system 114.

[0180] like Figure 5B As shown by reference numeral 518, the transaction service provider system 112 can send a second confirmation message to the user device 102. The transaction service provider system 112 can send the second confirmation message to the user device 102 to cause the user device 102 to generate a second confirmation response message including confirmation data associated with the confirmation of the transaction. The user device 102 can generate the confirmation data associated with the confirmation of the transaction based on input received at the user device 102 (e.g., input of a unique confirmation code).

[0181] like Figure 5B As indicated by reference numeral 520, the transaction service provider system 112 can receive a second confirmation response message from the user device 102. For example, the transaction service provider system 112 can receive a second confirmation response message from the user device 102 that includes confirmation data associated with the confirmation of a transaction. The transaction service provider system 112 can determine that the confirmation data matches confirmation data received during the registration of the user device 102 with the transaction service provider system corresponding to the user device 102. The transaction service provider system 112 can generate an authorization request message associated with the transaction based on the transaction data associated with the transaction and the determination that the second confirmation response message includes confirmation data that matches the confirmation data received during the registration of the user device 102 corresponding to the user device 102.

[0182] like Figure 5B As shown by reference numeral 522, the transaction service provider system 112 can send an authorization request message to the issuer system 114, the authorization request message being based on transaction data associated with the transaction. In some non-limiting embodiments, the issuer system 114 can generate an authorization response message based on the authorization request.

[0183] like Figure 5B As indicated by reference numeral 524, the transaction service provider system 112 can receive an authorization response message from the issuer system 114. For example, the transaction service provider system 112 can receive an authorization response message from the issuer system 114 indicating whether the transaction has been accepted or not. In some non-limiting embodiments, when a transaction is determined to be a low-value transaction, an authorization request message can be generated based on the determination that the transaction is a low-value transaction, without requiring the transaction service provider system 112 to send a second confirmation message and receive a second confirmation response message.

[0184] like Figure 5BAs shown by reference numeral 526, a payment confirmation message can be sent to user device 102. For example, transaction service provider system 112 can send a payment confirmation to user device 102, the payment confirmation message including data associated with an indication of whether the transaction has been approved or not. User device 102 can display an indication that the transaction has been processed and approved or not based on the receipt of the payment confirmation message.

[0185] like Figure 5B As shown by reference numeral 528, the transaction service provider system 112 can send a payment confirmation message to the POS device 104. For example, the transaction service provider system 112 can send a payment confirmation to the POS device 104, the payment confirmation message including data associated with an indication of whether the transaction has been approved or not. The POS device 104 can display an indication that the transaction has been processed and approved or not based on the received payment confirmation message.

[0186] Now for reference Figure 6A and 6B An embodiment 600 of a non-limiting example of a process for transmitting transaction data between mobile devices is shown. Figure 6A and 6B As shown, implementation scheme 600 includes user device 102, POS device 104, transaction service provider system 112 and issuer system 114.

[0187] like Figure 6AAs indicated by reference numeral 602, user device 102 may register with transaction service provider system 112. During registration, user device 102 may send account data associated with a user account and device data associated with user device 102 to transaction service provider system 112. In response, transaction service provider system 112 may store the account data associated with the user account and the device data associated with user device 102 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, user device 102 may send confirmation data associated with confirmation of a transaction corresponding to user device 102, the confirmation data including a unique confirmation code. In some non-limiting embodiments, user device 102 may be used to make a telephone call to register with transaction service provider system 112. In some non-limiting embodiments, in response to receiving account data associated with a user account and device data associated with user device 102, transaction service provider system 112 may generate and send an account token (e.g., as data or via telephone call), and the account token may be linked to the user account and the device data associated with user device 102. In some non-limiting embodiments, the transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to the user device 102.

[0188] like Figure 6A As indicated by reference numeral 604, POS device 104 can register with transaction service provider system 112. During registration, POS device 104 can send account data associated with a merchant account and device data associated with POS device 104 to transaction service provider system 112. In response, transaction service provider system 112 can store the account data associated with the merchant account and the device data associated with POS device 104 in association with each other (e.g., in the database of transaction service provider system 112). Alternatively or additionally, POS device 104 can send confirmation data associated with confirmation of a transaction corresponding to POS device 104, the confirmation data including a unique confirmation code. In some non-limiting embodiments, POS device 104 can be used to initiate a telephone call to register with transaction service provider system 112. In some non-limiting embodiments, in response to receiving account data associated with a merchant account and device data associated with POS device 104, transaction service provider system 112 can generate an account token and send the account token (e.g., as data or via telephone call), the account token being linked to the merchant account and the device data associated with POS device 104. In some non-limiting embodiments, the transaction service provider system 112 may send confirmation data associated with the confirmation of a transaction to the POS device 104.

[0189] like Figure 6A As indicated by reference numeral 606, user device 102 can transmit transaction data associated with a transaction to POS device 104 via a short-range wireless communication connection, an SMS communication connection, and / or a data connection. The transaction data may include device data associated with user device 102 and / or transaction parameters associated with the transaction. In some non-limiting embodiments, user device 102 and / or POS device 104 may determine that user device 102 and / or POS device 104 is not configured to exchange transaction data, and upon this determination, a display may be generated indicating that the device is not configured to exchange transaction data (e.g., the device has an incompatible e-wallet application installed therein).

[0190] like Figure 6A As shown by reference numeral 608, the POS device 104 can send transaction data to the transaction service provider system 112. For example, the POS device 104 can send transaction data, including device data associated with the user device 102, device data associated with the POS device 104, and / or transaction parameters associated with the transaction. The transaction service provider system 112 can generate a first confirmation message based on the received transaction data.

[0191] like Figure 6A As indicated by reference numeral 610, the transaction service provider system 112 can send a first confirmation message to the user device 102. The user device 102 can generate a display based on the first confirmation message and can receive input indicating whether the transaction has been confirmed or not based on the display. The user device 102 can generate a first confirmation response message indicating whether the transaction has been confirmed or not based on the received input.

[0192] like Figure 6A As indicated by reference numeral 612, user device 102 may send a first confirmation response message to transaction service provider system 112. Transaction service provider system 112 may determine whether a transaction has been confirmed or not based on the first confirmation response message. Transaction service provider system 112 may generate a pre-authorization request message based on the first confirmation response message and / or transaction data.

[0193] like Figure 6A As shown by reference numeral 614, the transaction service provider system 112 can send a pre-authorization request message to the issuer system 114. The issuer system 114 can generate a pre-authorization response message based on the pre-authorization request message.

[0194] like Figure 6A As shown by reference numeral 616, the transaction service provider system 112 can receive a pre-authorization response message from the issuer system 114.

[0195] like Figure 6A As indicated by reference numeral 618, the transaction service provider system 112 can determine whether a transaction is a high-value transaction. For example, when a transaction is determined to be a high-value transaction, the transaction service provider system 112 can generate and send a second confirmation message. Alternatively, when a transaction is determined to be a low-value transaction, the transaction service provider system 112 can process the transaction (see [reference numeral]). Figure 6B (Ref. reference numbers 624-630).

[0196] like Figure 6B As indicated by reference numeral 620, the transaction service provider system 112 can send a second confirmation message to the user device 102. The user device 102 can generate a display and receive input based on the generated display, the input including confirmation data associated with the confirmation of the transaction.

[0197] like Figure 6B As shown by reference numeral 622, the transaction service provider system 112 can receive a second confirmation response from the user device 102. The transaction service provider system 112 can determine whether a transaction is valid based on the second confirmation response message, and can generate an authorization request message in response to determining that the transaction is valid.

[0198] like Figure 6B As shown by reference numeral 624, the transaction service provider system 112 can send an authorization request message to the issuer system 114. The issuer system 114 can determine whether the transaction is authorized and can generate an authorization response message based on the determination.

[0199] like Figure 6B As shown by reference numeral 626, the transaction service provider system 112 can receive an authorization response message from the issuer system 114.

[0200] like Figure 6B As shown by reference numeral 628, the transaction service provider system 112 can send a payment confirmation message to the user device 102, the payment confirmation message including data associated with an indication of whether the transaction has been approved or not.

[0201] like Figure 6B As shown by reference numeral 630, the transaction service provider system 112 can send a payment confirmation message to the POS device 104, the payment confirmation message including data associated with an indication of whether the transaction has been approved or not.

[0202] Although examples have been described in detail based on aspects or embodiments currently considered most practical and preferred for illustrative purposes, it should be understood that such details are for the purposes described only, and the principles described herein are not limited to the disclosed aspects or embodiments, but are instead intended to cover modifications and equivalent arrangements falling within the spirit and scope of the appended claims. For example, it should be understood that this disclosure contemplates, where possible, that one or more features of any embodiment may be combined with one or more features of any other embodiment.

Claims

1. A computer-implemented method for communicating transaction data between mobile devices, the computer-implemented method comprising: receiving, with at least one processor, account data associated with a merchant account and device data associated with a point-of-sale (POS) device from the POS device, wherein the device data associated with the POS device includes short message service (SMS) device data associated with the POS device; registering, with at least one processor, the account data associated with a merchant account as corresponding to the SMS device data associated with a POS device in an application hosted by a transaction service provider system; receiving, with at least one processor, account data associated with a user account and device data associated with a user device from the user device, wherein the device data associated with the user device includes SMS device data associated with the user device; registering, with at least one processor, the account data associated with a user account as corresponding to the SMS device data associated with a user device in an application hosted by a transaction service provider system; receiving, with at least one processor, transaction data associated with a transaction from the POS device via an SMS communication connection, the transaction data comprising: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction initiated by the POS device, the parameter data including a transaction value, verifying, with at least one processor, the POS device and the user device are registered in response to receiving the SMS device data associated with a POS device and the SMS device data associated with a user device in an application hosted by a transaction service provider system; transmitting, with at least one processor, a transaction parameter confirmation message to the POS device based on receiving the transaction data; receiving, with at least one processor, a transaction parameter confirmation response message from the POS device; transmitting, with at least one processor, a pre-authorization request message to an issuer server in response to receiving the transaction parameter confirmation response message from the POS device; receiving, with at least one processor, a pre-authorization response message from the issuer server, the pre-authorization response message including an indication that an account balance based on the user account is greater than the transaction value; transmitting, with at least one processor, a first confirmation message associated with the transaction to the user device via the SMS communication connection to confirm the transaction based on receiving the pre-authorization response message including the indication; and receiving a first confirmation response message from the user device via the SMS communication connection, and processing, with at least one processor, the transaction data based on receiving the first confirmation response message.

2. The computer-implemented method of claim 1, further comprising: transmitting, with at least one processor, a second confirmation message associated with the transaction to the user device based on determining a transaction authorization limit is greater than an authorization limit threshold; and ​ confirm, with at least one processor and prior to processing the transaction data, that the second confirmation response is valid based on receiving a second confirmation response message associated with the transaction.

3. The computer-implemented method of claim 2, wherein registering account data associated with a user account as corresponding to SMS device data associated with the user device further comprises: registering, with at least one processor, confirmation data associated with a confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with a user device.

4. The computer-implemented method of claim 3, further comprising: determining, with at least one processor, that the second confirmation response message indicates that the transaction is valid based on a comparison of the second confirmation response message to the confirmation data corresponding to the SMS device data associated with a user device received during registration of the account data associated with the user account.

5. The computer-implemented method of claim 1, wherein verifying that the POS device and the user device are registered further comprises: determining, with at least one processor, that the SMS device data associated with the POS device corresponds to the account data associated with a merchant account; and determining, with at least one processor, that the SMS device data associated with the user device corresponds to the account data associated with a user account.

6. The computer-implemented method of claim 1, wherein verifying that the POS device and the user device are registered further comprises: based on determining that at least one of the POS device and the user device is not registered, sending, with at least one processor, a message to the at least one of the POS device and the user device associated with the transaction indicating that the at least one of the POS device and the user device is not registered.

7. A system for communicating transaction data between mobile devices, the system comprising: at least one processor programmed or configured to: receive, from a point of sale (POS) device, account data associated with a merchant account and device data associated with the POS device, wherein the device data associated with the POS device includes short message service (SMS) device data associated with the POS device; register the account data associated with a merchant account as corresponding to SMS device data associated with a POS device in an application hosted by a transaction service provider system; receive, from a user device, account data associated with a user account and device data associated with a user device, wherein the device data associated with a user device includes SMS device data associated with a user device; register the account data associated with a user account as corresponding to SMS device data associated with a user device in an application hosted by a transaction service provider system; receive, from the POS device via an SMS communication connection, transaction data associated with a transaction, the transaction data including: the SMS device data associated with the POS device, the SMS device data associated with the user device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction initiated by the POS device, the parameter data including a transaction value, in response to receiving the SMS device data associated with the POS device and the SMS device data associated with the user device in an application hosted by a transaction service provider system, verifying that the POS device and the user device are registered; based on receiving the transaction data, transmitting a transaction parameter confirmation message to the POS device; receiving a transaction parameter confirmation response message from the POS device; in response to receiving the transaction parameter confirmation response message from the POS device, transmitting a pre-authorization request message to an issuer server; receiving a pre-authorization response message from the issuer server, the pre-authorization response message including an indication that an account balance based on a user account is greater than the transaction value; based on receiving the pre-authorization response message including the indication, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection to confirm the transaction; receiving a first confirmation response message from the user device via the SMS communication connection, and based on receiving the first confirmation response message, processing the transaction data.

8. The system of claim 7, wherein the at least one processor is further programmed or configured to: based on determining that a transaction authorization limit is greater than an authorization limit threshold, send a second confirmation message associated with the transaction to the user device; and based on receiving a second confirmation response message associated with the transaction, confirming that the second confirmation response is valid prior to processing the transaction data.

9. The system of claim 8, wherein, when registering account data associated with the user account as corresponding to SMS device data associated with the user device, the at least one processor is programmed or configured to: register confirmation data associated with a confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with the user device.

10. The system of claim 9, wherein the at least one processor is further programmed or configured to: based on a comparison of the second confirmation response message to the confirmation data corresponding to the SMS device data associated with the user device received during registration of the account data associated with the user account, determine that the second confirmation response message indicates that the transaction is valid.

11. The system of claim 7, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: determine that the SMS device data associated with the POS device corresponds to the account data associated with a merchant account; and determine that the SMS device data associated with the user device corresponds to the account data associated with a user account.

12. The system of claim 7, wherein, when verifying that the POS device and the user device are registered, the at least one processor is programmed or configured to: based on determining that at least one of the POS device and the user device is unregistered, sending a message associated with the transaction to the at least one of the POS device and the user device indicating that the at least one of the POS device and the user device is unregistered.

13. A computer program product for communicating transaction data between mobile devices, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions, which, when executed by at least one processor, cause the at least one processor to perform the following operations: receiving, from a point of sale (POS) device, account data associated with a merchant account and device data associated with the POS device, wherein the device data associated with the POS device comprises short message service (SMS) device data associated with the POS device; registering, in an application hosted by a transaction service provider system, the account data associated with a merchant account as corresponding to the SMS device data associated with a POS device in the application; receiving, from a user device, account data associated with a user account and device data associated with the user device, wherein the device data associated with the user device comprises SMS device data associated with the user device; registering, in an application hosted by a transaction service provider system, the account data associated with a user account as corresponding to the SMS device data associated with a user device; receiving, from the POS device via an SMS communication connection, transaction data associated with a transaction, the transaction data comprising: the SMS device data associated with the POS device, the SMS device data associated with the user device, and parameter data associated with the transaction, the transaction initiated by the POS device, the parameter data comprising a transaction value, in response to receiving the SMS device data associated with a POS device and the SMS device data associated with a user device, verifying, in an application hosted by a transaction service provider system, that the POS device and the user device are registered; based on receiving the transaction data, communicating a transaction parameter confirmation message to the POS device; receiving, from the POS device, a transaction parameter confirmation response message; in response to receiving the transaction parameter confirmation response message from the POS device, transmitting a pre-authorization request message to an issuer server; receiving, from the issuer server, a pre-authorization response message comprising an indication that an account balance based on the user account is greater than the transaction value; based on receiving the pre-authorization response message comprising the indication, sending a first confirmation message associated with the transaction to the user device via an SMS communication connection to confirm the transaction; receiving, from the user device via the SMS communication connection, a first confirmation response message, and based on receiving the first confirmation response message, processing the transaction data.

14. The computer program product of claim 13, wherein the one or more instructions further cause the at least one processor to perform the following operations: based on determining that the transaction authorization limit is greater than the authorization limit threshold, sending a second confirmation message associated with the transaction to the user device; and based on receiving a second confirmation response message associated with the transaction, confirming that the second confirmation response is valid prior to processing the transaction data.

15. The computer program product of claim 14, wherein the one or more instructions that cause the at least one processor to register account data associated with a user account as corresponding to SMS device data associated with the user device cause the at least one processor to: register confirmation data associated with a confirmation of the transaction, the confirmation data corresponding to the SMS device data associated with a user device.

16. The computer program product of claim 15, wherein the one or more instructions further cause the at least one processor to: based on a comparison of the second confirmation response message to the confirmation data corresponding to the SMS device data associated with a user device received during registration of the account data associated with the account, determine that the second confirmation response message indicates that the transaction is valid.

Images