TH45703A - Systems and processes for making transactions And remote payment in real time by mobile phone. - Google Patents

Abstract

DC60 (28/09/43) Systems and processes for processing payments and transactions between payers (13) and payees (27, 29, 14, 14a, 13a, 46), along with the system. It uses the first server (20) connected to the telecommunication mechanism (18, 19, 28, 47) with the first storage mechanism (22) containing information about Each participating payer (13) consisting of At the very least, the phone number to be accessed, at the very least, the terms of authorization to authorize the transaction and the security conditions that accompany Phone numbers to be accessed As well as Each payee's accessible identification code - a second (21) storage engine containing information. The second category refers to the type of digital mobile phone (16, 41) that belongs to the number. Each telephone - a selection mechanism (20h) for verifying one telecommunication device (18, 19) attached. Communicate with A digital mobile phone (16, 41) identified by Telephone numbers that can be accessed through the service The telecommunication field is compatible with the type of digital mobile phone (16, 41) as specified, systems and processes for processing payments and transactions between payer (13) and payee ( 27, 29, 14, 14a, 13a, 46) equipped with the first server (20) connected to the telecommunication mechanism (18, 19, 28, 47) with the first storage mechanism. (22) containing information about Each participating payer (13) consisting of At the very least, the phone number to be accessed, at the very least, the terms of authorization to authorize the transaction and the security conditions that accompany Phone numbers to be accessed As well as Each payee's accessible identification code - a second (21) storage engine containing information. The second category refers to the type of digital mobile phone (16, 41) that belongs to the number. Each telephone - a selection mechanism (20h) for verifying one telecommunication device (18, 19) attached. Communicate with A digital mobile phone (16, 41) identified by Telephone numbers that can be accessed through the service Telecommunication compatible with the specified type of digital mobile phone (16, 41)

Claims (46)

1. A system for processing payments and transactions between payers (13) and payees (27, 29, 14, 14a, 13a, 46) coupled with a system that uses at least one type of communication via a digital mobile phone, in which the system consists of - a T1 server (20) that is connected to telecommunication mechanisms (18, 19, 28, 47) that contain a T1 data storage mechanism (22) and include an account management mechanism (20e) that processes the T1 data of each participating payer's account (13) and the T2 data of each participating payee's account (27, 29, 14, 14a, 40, 46), in which - telecommunication mechanisms (18, 19, 28, 47) selectively communicate with The first server (20) contains a digital mobile unit (16) identified by the access telephone number of the participating payer (13), and contains a communication terminal (15, 15a, 27, 29, 41, 46) identified by the access identification code of the participating payee (27, 29, 14, 14a, 40, 46), where the telecommunication mechanism (18, 19, 28, 47) shall consist of one telecommunication device (18, 19) as follows: - The first data storage mechanism (22) shall contain first information about each participating payer (13), which shall contain at least the access telephone number, at least the pre-established authorization conditions to allow at least one transaction which requires payment from the participating payer's account (13), and at least the security conditions which are only associated with the participating payer's telephone number (13), as well as some second information about With each participating payee (27, 29, 14, 14a, 40, 46), which contains at least one access identification code, Server One (20) consists of: - The first validation mechanism (20a) to verify in the storage mechanism (22) that the first message received via the telecommunication mechanism (18, 19, 28, 47) contains the access telephone number of the participating payer (13) and the access identification code of the participating payee (27, 29, 14, 14a, 40, 46), whereby the first validation mechanism (20a) generates the first acceptance message when it detects the access identification code and the access telephone number; - The second validation mechanism (20b) to verify in the storage mechanism (22) that the authorization request received via the telecommunication mechanism (18, 19, 28, 47) in addition to the number - The third validation mechanism (20c) checks in the first data storage mechanism (22) whether the security parameters received via the telecommunication mechanism (18,19) meet the security conditions associated with the accessible telephone number detected by the first validation mechanism. The third validation mechanism (20c) generates a third acceptance message when it detects that the security parameters meet the security conditions associated with the accessible telephone number. - The authorization mechanism (20d) authorizes the account management mechanism (20e), upon authorization request, to process debits in the participating payer's account (13) and to process corresponding credits in the account. The participating payees (27, 29, 14, 14a, 40, 46) have a length equal to the first, second, and third acceptance messages that have been generated. The rejection message generation mechanism (20f) generates a rejection message when at least one acceptance message has not been generated, and for transmitting the rejection message to the telecommunication mechanisms (18, 19, 28, 47). The confirmation message generation mechanism (20g) generates at least one confirmation message when at least one acceptance message has been generated, and for transmitting such confirmation messages to the telecommunication mechanisms (18, 19, 28, 47) and selective transmission of the confirmation message to the mobile phone (16, 41) identified by the telephone number provided in the first message and to the communication terminals (15, 15a, 27, 29, 41, 46) identified by the code. The grantable access number mechanism (21) contains at least one first piece of information referring to each payer's grantable access number (13) and at least one second piece of information referring to the type of digital mobile phone (16, 41) that owns each phone number. The selection mechanism (20h) checks in the aforementioned second piece of information mechanism (21) which the second piece of information corresponds to the digital mobile phone unit (16, 41) identified by the grantable access number and selects one telecommunication device (18, 19) which will communicate with the digital mobile phone (16, 41) identified by the grantable access number using the telecommunication service available to the type of digital mobile phone (16, 41) identified in the second piece of information. 2. The system, pursuant to claim 1, whereby the access identification codes for each payee (27, 29, 14, 14a, 40, 46) will be selected from telephone numbers, associated telephone numbers, internet codes, internet access codes, email addresses, and codes dependent on email addresses. 3. The system under claim 1, in which the first validation mechanism will verify the payer's (13) access telephone number from the codes received via the telecommunication mechanisms (18, 19, 28, 47) which are used in place of the said access telephone number and are included in the first data storage mechanism (22). 4. The system, pursuant to claim 1, whereby a second acceptance message shall instruct the telecommunications mechanism (18, 19) to transmit to the payer's mobile phone (16) (13) identified by the provided telephone number, whereby the first confirmation message shall contain a request to transmit security parameters which shall be verified by a third validation mechanism (20c) against security conditions. 5. The system, pursuant to claim 4, whereby the second acceptance message continues, shall instruct the telecommunication mechanism (18, 19, 28, 47) to communicate with the communication terminal (15, 15a, 27, 29, 46) identified by the access identification code detected by the first validation mechanism (20a) to transmit a second confirmation message which will confirm the generation of the first acceptance message. 6. The system, pursuant to claim 1, whereby a third acceptance message generated by the third validation mechanism (20c) shall instruct the telecommunication mechanisms (18, 19, 28, 47) to communicate with the communication terminals (15, 15a, 27, 29, 46) identified by the access identifier detected by the first validation mechanism (20a) to transmit a third confirmation message which will confirm the generation of the third acceptance message. 7. The system, pursuant to claim 1 or 6, where a third acceptance message is generated by the third validation mechanism (20c), shall instruct the telecommunication mechanism (18, 19) to communicate with the mobile phone (16) identified by the access telephone number detected by the first validation mechanism (20a) to transmit a fourth confirmation message which will confirm the generation of the third acceptance message. 8. The system, pursuant to claim 1, 6 or 7, where a third acceptance statement is generated by the third validation mechanism (20c), shall instruct the account handling mechanism (20e) to process the debit in the payer's account (13) and process the corresponding credit in the payee's account (27, 29, 14, 14a, 40, 46). 9. The system pursuant to claim 1 or 8, in which the account management mechanism (20e) shall control at least one of the first intermediary accounts of the payee (27, 29, 14, 14a, 40, 46), each of which is contained in the first data storage mechanism (22) and in which each credit is made. 10. The system under claim 9, in which the account management mechanism (20e) contains a first-stage transmission mechanism for passing such credits to the administration and management server (23), which contains the payee's data warehouse (25), in which every credit made for the benefit of each payee (27, 29, 14, 14a, 46) is stored, whereby the administration and management server (23) moves the credits contained in the data warehouse (25) to the finance section, which manages the financial accounts of each payee. 11. The system under claim 1 or 8, in which the account management mechanism (20e) controls a second intermediate account selected from the payer's prepaid, real-time debit, and post-payment accounts (13). 12. The system under claim 11, in which the prepaid account controlled by the accounting management mechanism (20e) contains an electronic wallet previously created in the first data storage mechanism (22) for each buyer (13). 13. The system, pursuant to claim 1, whose authorization request contains information relating to the transaction value and whose authorization conditions are established before being verified by the second validation mechanism (20b), will select from the available balance, the maximum credit limit and the combination of that portion created for each individual payer account (13). 14. The system, pursuant to claim 8, in which the account management mechanism (20e) contains a second transmission mechanism for passing such debits to the administration and management server (23), which contains the payer's data warehouse (24), in which every debit made against each individual payer (13) is stored, whereby the administration and management server (23) moves the credits contained in the payer's data warehouse (24) to the finance section, which manages the financial accounts of each individual payer. 15. The system, pursuant to claim 1, where security conditions are verified by a third-party verification mechanism (20c), is a secret identification code which the payer (13) will know and which will be stored in a first-party data storage mechanism (22). 16. The system, pursuant to claim 15, whereby a third validation mechanism (20c) directly verifies whether the security parameter contains a secret identifier. 17. The system, pursuant to claim 15, whereby a third authentication mechanism (20c) checks whether the security parameters contain the encrypted result of the self-authentication (33) performed locally on the mobile phone (16), after a direct entry (6) of the cryptographic ID is entered into the mobile phone by the payer (13), relying on the decryption mechanism to decrypt the encrypted result based on the cryptographic ID stored in the first data storage mechanism (22). 18. The system, pursuant to claim 4, whereby the first message, verified by the first validation mechanism (20a), is received by the telecommunication terminal (15, 15a, 27, 41, 46), a second acceptance message instructs the telecommunication mechanism (18, 19) to establish a communication with the mobile phone (16) for requesting the payer (13) identified by the access telephone number to pass security parameters. 19. The system, pursuant to claim 4, whereby the first message, verified by the first validation mechanism (20a), is received by the payer's mobile phone (16) (13), a second acceptance message shall instruct the telecommunications mechanism (18, 19) to transmit the message to that mobile phone (16), which will then request the payer (13), identified by the provided access telephone number, to transmit security parameters. 20. The system, pursuant to claims 4, 18 or 19, where a second acceptance message remains, shall instruct the telecommunications mechanism (18, 19) to transmit at least the transaction value and the identity of the payee which shall be transmitted concurrently with the request message. Security conditions. 21. The system under Claim 1, in which the first server (20) will process the first message, which will also contain the identification of the email address for which the payee (27) provides the software file, and in which the confirmation message generation mechanism (20 g) will also generate a confirmation message containing the decryption code for the software file received from the payee (27) on the first server (20), and such confirmation message will continue to be transmitted to the payer's mobile phone (16) (13). 22. The system, pursuant to claim 1, in which the first server (20) continues to contain the first detection mechanism (20i) for detecting the first order for prepaid purchases and the billing code generation mechanism (20j), and in which the confirmation message generation mechanism (20g) continues to generate an additional confirmation message containing the billing code, which is then transmitted to the payer's mobile phone (16) (13) and to the payee's communication terminals (15, 15a, 27, 29, 46) (14, 14a, 27, 29, 46). 23. The system, pursuant to claim 1, shall continue to contain a first data storage mechanism (22) which, taking into account each payee (14a, 46), shall continue to contain a third data accompanying the second data and which shall contain information about the product or service corresponding to each authorized transaction, and which the first server (20) shall continue to contain a second detection mechanism (20k) for detecting a second order to self-manage delivery in accordance with the authorized transaction and received by the communication terminal (15a), which is the payee's mobile phone (14a), a delivery code generation mechanism (201) for generating a delivery code that identifies at least the product or service to be delivered, and an identity message generation mechanism (20m) that identifies such product or service, and which a confirmation message generation mechanism (20g) shall continue to generate an additional message containing the delivery code, whereby such additional message is passed to the payer's mobile phone (16) (13) and to the payee's mobile phone (15a) (14a), and the identifying message which is passed at least Finally, the information is sent to the payer's mobile phone (16) along with a request to transmit security parameters and a delivery management processing mechanism (20n) which, when a third verification mechanism (20c) has verified that the security parameters meet the security conditions coupled with the payer's mobile phone (13), generates an entry unit in the delivery note database (37). 24. The system under claim 1, in which the first data storage mechanism (22) shall continue to consist of a fourth data set accompanying the second data set, and which shall consist of a reference code which shall identify at least one payee's product or service (14a, 46), as well as the price accompanying each product or service. 25. The system, pursuant to claim 24, where the fourth piece of information still consists of the first selectable telephone number which contains one such reference code and the corresponding payee identification code (14, 46) and which will constitute the access identification code. 26. The system, pursuant to claim 24 or 25, whereby the fourth piece of information shall still consist of an access identifier in the form of a telephone number for accessing the payee (16, 46), accompanied by at least one menu containing product or service reference codes identified in order by each such reference code and the price of such product or service. 27. The system under claim 1, in which the access identifier is a telephone number, provides access to the second menu of the access identifiers in order of the participating payees (14a, 46), and in which the first data storage mechanism (22) continues to contain the fifth data accompanying the second data and contains the reference code identifying each payee's product or service (14a, 46) as well as the price accompanying each product or service. 28. The system, pursuant to claim 27, where the fifth data still consists of one selectable telephone number containing one such reference code and the corresponding payee identification code (14, 46), which will constitute an access identification code. 29. The system, pursuant to claim 27 or 28, whereby the fifth data still contains an access identifier in the form of the payee's telephone number (14, 46), accompanied by at least one menu containing product or service reference codes identified by order by each such reference code and each such product or service price. 30. The system, pursuant to claim 1, shall, in the first data storage mechanism (22), consist of a number of vending machine identifiers (29), each of which shall include a digital mobile phone portion (29a) in the form of a communication terminal identified by the mobile phone number in the form of an access identifier, an authorization code accompanying each vending machine access identifier, an activation code for activating the vending machine (29) accompanied by each authorization code which activates the vending machine to accept a request from the payer (13) identified by the access phone number, and whereby the confirmation message generation mechanism (20g) shall generate this message when the first, second and third validation mechanisms (20a, 20b, 20c) have generated the first, second and third acceptance messages respectively, and shall transmit a confirmation message which shall contain at least the vending machine activation code and the access phone number of the payer's (16) mobile phone. 31. The system, pursuant to claim 30, in which the confirmation message generation mechanism (20g) establishes communication between the payer's mobile phone (13) and the vending machine (29) for a pre-established period during which the payer (13) can send, via Server One (20), a selection message to the vending machine (29), which server (20) still contains an inactivation detection mechanism (200) for detecting inactivation of the vending machine (29). 32. The system, pursuant to claim 31, whereby the authorization conditions accompanying the access telephone number of each vending machine shall be a direct authorization code, which establishes a maximum limit selected based on economic value and the number of payment requests accepted within a specific timeframe for requests made from the same mobile phone, and whereby the confirmation message generation mechanism (20g) shall generate a direct confirmation message when the authorization code is detected. 33. The system, according to claim 30, which, when the mechanism generates a confirmation message (20g) on the first server (20), closes communication with the vending machine (29) after having sent a confirmation message, allows the payer (13) to make a selection directly from the vending machine's selection display mechanism. 34. The system, pursuant to claims 30, 31, 32 or 33, where the first server (20) continues to contain a recording mechanism (20p) coupled with an authorization mechanism (20d) for recording transactions recorded on each vending machine (29). 35. The system, pursuant to claim 1, shall continue to include an auxiliary validation mechanism (20a) which, coupled with an optional mechanism (20h), shall verify that the access identifier verified by the first validation mechanism (20a) in the first message received from the payer (13), identified by the first access telephone number and which request the transaction verified by the second validation mechanism (20b), corresponds to the second access telephone number from the digital mobile access telephone number (41) containing the first data stored in the first data storage mechanism (22), and that the first message identifies the second access telephone number as the payee's identity (40). The auxiliary validation mechanism (20q) shall generate a fourth acceptance message upon detecting that the second access telephone number corresponds to the payee (40), and that such fourth acceptance message can be processed by the confirmation message generation mechanism (20g), and that the generation mechanism The negation message (20f) will generate a negation message when the fourth message has not been generated. 36. The system, pursuant to claim 35, which the Verification Message Generation Mechanism (20g), upon detecting the first, second, third, and fourth acceptance messages, generates the first Verification Message containing the Payee Identity (13), the Transaction Identity, and the Recipient Compliance Request (40) specified in the first message. The Compliance Request contains a request for the transmission of security parameters and transmits the Verification Message to the Recipient's (40) mobile phone (41) specified by the second access telephone number via the telecommunication mechanism (18, 19) selected by the selection mechanism. In addition, the third validation mechanism (20c) checks whether the security parameters transmitted from the mobile phone (41) in response to the Compliance Request meet the security conditions associated with the second access telephone number. The third validation mechanism (20c) generates the fifth acceptance message when the parameters meet the requirements. Under these security conditions, the authorization mechanism (20e) will allow the account management mechanism (20d) to operate once the fifth acceptance message has been generated. The confirmation message generation mechanism (20g) will generate and transmit the second confirmation message to the payer's mobile phone (16) and to the payee's mobile phone (41). 37. The system, as specified in any of Claims 1, 35 or 36, in which each first server (20) contains each second data enclosed in the second data storage mechanism (21) and which refers to the type of digital mobile phone corresponding to each individual payer's access number (13) and each individual payee's access number (40), where the latter is a digital mobile phone number, is the first identifying code which is typical of the International Mobile Device Identifier (IMEI). 38. The system, pursuant to claim 37, consists of a first server (20) containing a query mechanism (20r) for querying at least one Traveler Location Register (VLR) which contains the first register associated with a telephone with an IMEI, which corresponds to each accessible telephone number, and a recalibration mechanism (20s) for recalibrating such second data in the second data storage mechanism (21) by comparing each IMEI queried by the first query mechanism (20r) with each IMEI typical of the IMEI associated with each accessible telephone number as contained in the second data storage mechanism (21). 39. The system, pursuant to claim 38, which the first query mechanism (20r) retrieves the IMEI code associated with each accessible telephone number from the Device Identifier (EIR) register, which contains the combination of each accessible telephone number and the IMEI code corresponding to each accessible telephone number, and which receives such combination from each traveler's location register as adjusted by that traveler's location register. 40. The system, pursuant to claim 38 or 39, in which the first query mechanism (20r) retrieves the IMEI code associated with each accessible telephone number from the unstructured supplemental service data (USSD) register containing the location of each traveler within the mobile switching center (MSC) that has issued such framework, has inserted the IMEI code associated with the corresponding accessible telephone number for the user who initiated such framework. 41. The system, pursuant to claim 38, in which the first query mechanism (20r) retrieves the IMEI code associated with each accessible telephone number through a program that integrates the traveler's location register and the aforementioned query mechanism (20r). 42. The system, pursuant to claim 37, shall have a first server (20) containing a second query mechanism (20t) for querying the IMEI code corresponding to each accessible telephone number in the call data register (CDR) of the mobile network operator's database, relating each telephone number that initiated the call data register containing the terminal IMEI code due to the call that originated from this section. The aforementioned second recombination mechanism (20u) shall recombine the aforementioned second data in the second data storage mechanism (21) by comparing each IMEI code queryed by the second query mechanism (20t) with each typical IMEI code associated with each accessible telephone number, which is located in each second data storage mechanism (21). 43. The system, pursuant to claim 37, whereby the second data still contains at least one piece of information indicating the communication capability selected from the capabilities of the wireless application layer (WAR) application layer (WAR) application layer (WAR) processing component, the capabilities of the USSD (Unconfigured Service Data) processing component, and a combination of those components of each digital mobile phone identified by its IMEI code and associated with the provided telephone number. 44. The system, pursuant to claim 37, shall have a first server (20) containing a third query mechanism (20v) for querying the mobile network operator's database registers, which each mobile switching center (MSC) immediately transmits each USSD frame or voice call addressed to a specific telephone number whose registered correspondence is the number being called or initiating the USSD frame containing the terminal's IMEI code, in which such call or frame is initiated by this section in relation to the IMEI code corresponding to each accessible telephone number, and a third recombination mechanism (20w) for recombining such data in the second database mechanism (21) based on the comparison of IMEI codes queried by the third query mechanism (20v) with each IMEI code corresponding to the accessible telephone number in each second database mechanism. 45. The process for processing payments and transactions between payers (13) and payees (27, 29, 14, 14a, 13a, 40, 46) that use a system that is limited in any of the preceding rights. 46. The process under claim 45, which includes: - selectively receiving the first message containing the payer's (13) mobile phone number or payee's identification code (27, 29, 14, 14a, 13a, 40, 46) via the telecommunication mechanism (18, 19, 28, 47) in the payment and transaction center (17); and also - receiving the purchase amount or code identifying the product or service in the payment and transaction center (17); - verifying that the first message originated from the payer (13) identified by the payee's (27, 29, 14, 14a, 13a, 40, 46) access telephone number; - verifying that the transaction conditions requested in the first message meet the transaction criteria stored in the first data storage mechanism (22); - verifying the type of digital mobile phone associated with the number. The telephone accessed in the second data storage mechanism (21) and the selection of one telecommunication device (18, 19) for communication with the digital mobile phone (16) identified by the accessed telephone number via a telecommunication service compatible with the type of digital mobile phone (16) identified by the accessed telephone number - an "online" check in the first data storage mechanism (22) that the payer (13) has a usable balance in the electronic wallet file previously created in the transaction and payment center (17) - a request for the payer (13) identified in the first message, when the transaction conditions are met and there is a sufficient usable balance to allow the transaction, to bring the security parameters to the mobile phone (16) identified in the first message and to transmit these security parameters - a check in the first data storage mechanism (22) that the security parameters The security introduced and transmitted by the payer's mobile phone (16) is subject to the security conditions transferred to that mobile phone (16) alone; the authorization and execution of the requested transaction when the security parameters meet the security conditions; the transmission of confirmation that the transaction has been executed to the payer's mobile phone (16) and to the payee (27, 29, 14, 14a, 13a, 40, 46).