IPC분류정보
국가/구분 |
United States(US) Patent
등록
|
국제특허분류(IPC7판) |
|
출원번호 |
US-0469997
(2012-05-11)
|
등록번호 |
US-RE44669
(2013-12-24)
|
발명자
/ 주소 |
|
출원인 / 주소 |
|
대리인 / 주소 |
|
인용정보 |
피인용 횟수 :
9 인용 특허 :
16 |
초록
▼
When purchasing an item or service, a user enters a PIN enter their mobile communication device and send the PIN, e.g., via text message to a payment authority. The payment authority authenticates the user using at least the PIN and the mobile communication device identifier associated with the user
When purchasing an item or service, a user enters a PIN enter their mobile communication device and send the PIN, e.g., via text message to a payment authority. The payment authority authenticates the user using at least the PIN and the mobile communication device identifier associated with the user's mobile communication device. If the user is authenticated, then the payment authority will send a transaction code back to the user, which will be displayed on the user's mobile communication device. The user can then provide the transaction code to the merchant. The merchant can enter the transaction code into the Merchant's point of sale system and complete the transaction.
대표청구항
▼
1. A secure wireless payment transaction system, comprising: at least one processor; anda memory connected with the at least one processor, the memory containing a plurality of program instructions that cause the at least one processor to: receive a Personal identification Number (PIN) in a message
1. A secure wireless payment transaction system, comprising: at least one processor; anda memory connected with the at least one processor, the memory containing a plurality of program instructions that cause the at least one processor to: receive a Personal identification Number (PIN) in a message that is sent from a mobile communication device;receive a mobile communication device identifier identifying the mobile communication device with the message;authenticate a transaction based on the PIN and the mobile communication device identifier;generate a transaction code if the transaction is authenticated;return the transaction code to the mobile communication device;receive a transaction amount, a merchant identifier, and the transaction code from a merchant's Point of Sale (POS) system;approve the transaction based on the merchant identifier, the transaction amount, and recognition of the transaction code, wherein, in causing the at least one processor to approve the transaction, the plurality of program instructions cause the at least one processor to determine whether a user account associated with the transaction contains sufficient funds to cover the transaction amount; andtransmit an approval code to the POS system when the transaction is approved. 2. The secure wireless payment transaction system of claim 1, wherein the mobile communication device identifier is a Mobile Identification Number (MIN) associated with the mobile communication device. 3. The secure wireless payment transaction system of claim 1, wherein the transaction code is a 4 digit code. 4. The secure wireless payment transaction system of claim 1, wherein the transaction code is a 8 digit code. 5. The secure wireless payment transaction system of claim 1, wherein the transaction code includes blanks that are to be filled in using digits known to a user and to the secure wireless payment transaction system. 6. The secure wireless payment transaction system of claim 1, wherein the length of the transaction code is variable. 7. The secure wireless payment transaction system of claim 1, wherein the plurality of program instructions cause the at least one processor to relay the message from a message authority to a payment authority. 8. The secure wireless payment transaction system of claim 7, wherein the message authority provides a digital certificate to the payment authority, and wherein the payment authority uses the digital certificate to authenticate the transaction. 9. The secure wireless payment transaction system of claim 7, wherein the payment authority uses a network identifier associated with the message authority to authenticate the transaction. 10. The secure wireless payment transaction system of claim 1, wherein the plurality of program instructions cause the at least one processor to store the approval code, merchant ID, and transaction amount and to generate settlement instructions for the transaction. 11. The secure wireless payment transaction system of claim 10, wherein the plurality of program instructions cause the at least one processor to execute the settlement instructions. 12. The secure wireless payment transaction system of claim 1, wherein the message is a text message. 13. The secure wireless payment transaction system of claim 1, wherein the message is a Short Message Service (SMS) message. 14. The secure wireless payment transaction system of claim 13, wherein the SMS message is sent to the secure wireless payment transaction system via a short code. 15. The secure wireless payment transaction system of claim 1, wherein the plurality of program instructions cause the at least one processor to return a real time account balance with the transaction code. 16. The secure wireless payment transaction system of claim 1, wherein the transaction code remains valid for a predetermined period of time, after which the transaction code is no longer valid. 17. A method for secure wireless transaction, comprising: receiving a Personal identification Number (PIN) in a message that is sent from a mobile communication device;receiving a mobile communication device identifier identifying the mobile communication device with the message;authenticating a transaction based on the PIN and the mobile communication device identifier;generating a transaction code if the transaction is authenticated; andreturning the transaction code to the mobile communication device;receiving a transaction amount, a merchant identifier, and the transaction code from a merchant's Point of Sale (POS) system;approving the transaction based on the merchant identifier, the transaction amount, and recognition of the transaction code, the approving including determining whether a user account associated with the transaction contains sufficient funds to cover the transaction amount; and transmitting an approval code to the POS system when the transaction is approved. 18. The method of claim 17, wherein receiving a mobile communication device identifier comprises receiving a Mobile Identification Number (MIN) associated with the mobile communication device. 19. The method of claim 17, wherein generating a transaction code comprises generating a 4 digit code. 20. The method of claim 17, wherein generating a transaction code comprises generating a 8 digit code. 21. The method of claim 17, wherein generating a transaction code comprises generating a transaction code that includes blanks that are to be filled in using digits known to a user and to a secure wireless payment transaction system. 22. The method of claim 17, wherein the length of the transaction code is variable. 23. The method of claim 17, further comprising receiving a digital certificate, and wherein authenticating the transaction further comprises authenticating the transaction based on the digital certificate. 24. The method of claim 17, wherein the transaction is authenticated using a network identifier associated with a message authority that relays the message. 25. The method of claim 17, further comprising storing the approval code, merchant ID, and transaction amount and generating settlement instructions for the transaction. 26. The method of claim 25, further comprising executing the settlement instructions. 27. The method of claim 17, further comprising returning a real time account balance with the transaction code. 28. The method of claim 17, wherein the transaction code remains valid for a predetermined period of time, after which the transaction code is no longer valid. 29. A method of conducting a transaction, comprising: authenticating an identity of a user of a mobile device at a payment authority server system;issuing a perishable transaction code from the payment authority server system to the mobile device in response to the authentication of the identity of the user;receiving the perishable transaction code, a transaction amount, and a merchant identifier from a Point of Sale (POS) system associated with a merchant;approving the transaction at the payment authority server system based on the merchant identifier, the transaction amount, a determination that the perishable transaction code issued to the user has been received at the POS system, and a determination that the user has sufficient funding for the transaction; andenabling a completion of the transaction between an account associated with the user and an account associated with the merchant in response to the determination that the perishable transaction code issued to the user has been received at the POS system. 30. The method of claim 29, wherein the authenticating the identity of the user comprises: receiving a user identifier provided by the user from the mobile device. 31. The method of claim 30, wherein the user identifier comprises a Personal Identification Number (PIN). 32. The method of claim 29, wherein the perishable transaction code received at the payment authority server system comprises: a first portion comprising at least one character specific to the user; anda second portion comprising at least one character generated specifically for the transaction. 33. The method of claim 29, further comprising: determining whether a period of validity for the perishable transaction code has expired;wherein the enabling the completion of the transaction is further based on a determination that the period of validity for the perishable transaction code has not expired. 34. The method of claim 29, further comprising: communicating with an external financial institution to receive a real-time balance for an account associated with the user. 35. The method of claim 29, further comprising: generating settlement instructions for the transaction. 36. A payment authority server system comprising: at least one processor; andat least one memory communicatively coupled with the at least one processor; the at least one memory comprising executable code that, when executed by the at least one processor, causes the at least one processor to: authenticate an identity of a user of a mobile device at a payment authority server system;issue a perishable transaction code from the payment authority server system to the mobile device in response to the authentication of the identity of the user;receive the perishable transaction code, a transaction amount, and a merchant identifier from a Point of Sale (POS) system associated with a merchant;approve the transaction at the payment authority server system based on the merchant identifier, the transaction amount, a determination that the perishable transaction code issued to the user has been received at the POS system, and a determination that the user has sufficient funding for the transaction; andenable a completion of the transaction between an account associated with the user and an account associated with the merchant in response to the determination that the perishable transaction code issued to the user has been received at the point-of-sale device. 37. The payment authority server system of claim 36, wherein the executable code is further configured to: receive a user identifier provided by the user from the mobile device. 38. The payment authority server system of claim 37, wherein the user identifier comprises a Personal Identification Number (PIN). 39. The payment authority server system of claim 36, wherein the received perishable transaction code comprises: a first portion comprising at least one character specific to the user; anda second portion comprising at least one character generated specifically for the transaction. 40. The payment authority server system of claim 36, wherein the executable code further comprises code that causes the at least one processor to: determine whether a period of validity for the perishable transaction code has expired;wherein the enabling the completion of the transaction is further based on a determination that the period of validity for the perishable transaction code has not expired. 41. The payment authority server system of claim 36, wherein the executable code further comprises code that causes the at least one processor to: communicate with an external financial institution to receive a real-time balance for an account associated with the user. 42. The payment authority server system of claim 36, wherein the executable code further comprises code that causes the at least one processor to: generate settlement instructions for the transaction.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.