Secure authorizations using independent communications and different one-time-use encryption keys for each party to a transaction
IPC분류정보
국가/구분
United States(US) Patent
등록
국제특허분류(IPC7판)
G07D-011/00
G06Q-020/40
G06Q-020/38
G06Q-020/36
출원번호
US-0539190
(2014-11-12)
등록번호
US-9569776
(2017-02-14)
발명자
/ 주소
Carrott, Richard F.
출원인 / 주소
BENEDORTSE LLC
대리인 / 주소
Gibb & Riley, LLC
인용정보
피인용 횟수 :
0인용 특허 :
21
초록▼
A registered provider device encrypts provider input related to a transaction between the provider device and one of many registered user devices to create an encrypted one-time-use provider code (the encryption is performed using an encryption key produced, in part, using a uniquely sequenced numbe
A registered provider device encrypts provider input related to a transaction between the provider device and one of many registered user devices to create an encrypted one-time-use provider code (the encryption is performed using an encryption key produced, in part, using a uniquely sequenced number generated by a sequencer maintained by the provider device). Similarly, the user device encrypts user input to create an encrypted one-time-use user code using an encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by the user device. The provider and user devices independently transmit their different encrypted one-time-use codes to an intermediate entity, which decrypts the encrypted codes. This decryption is performed using one-time-use encryption keys produced using sequencers maintained by the intermediate entity, and this decryption generates an authorization request. The intermediate entity obtains an authorization decision regarding the authorization request from the authorization entity.
대표청구항▼
1. A system comprising: an intermediate entity maintaining duplicate sequencers used in producing one-time-use encryption keys for registered user devices and registered provider devices,said intermediate entity causing a provider device, of said registered provider devices, to encrypt provider inpu
1. A system comprising: an intermediate entity maintaining duplicate sequencers used in producing one-time-use encryption keys for registered user devices and registered provider devices,said intermediate entity causing a provider device, of said registered provider devices, to encrypt provider input related to a transaction between said provider device and a user device, of said registered user devices, to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said provider device,said intermediate entity causing said user device to encrypt user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said user device,said provider sequencer and said user sequencer separately producing different encryption keys for said transaction, said provider device using said uniquely sequenced number generated by said provider sequencer to produce said encrypted one-time-use provider code for said transaction, and said user device using said uniquely sequenced number generated by said user sequencer to produce said encrypted one-time-use user code for said transaction,said provider sequencer and said user sequencer being separately synchronized with corresponding ones of said duplicate sequencers maintained by said intermediate entity, such that said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and said provider sequencer and said user sequencer produce different encryption keys for a given transaction,said provider sequencer, said user sequencer, and said duplicate sequencers producing different one-time-use encryption keys for each different transaction to prevent any one-time-use encryption key from being used for different transactions,said intermediate entity causing said provider device to independently transmit said encrypted one-time-use provider code to said intermediate entity for an authorization of said transaction, and said user device to independently transmit said encrypted one-time-use user code to said intermediate entity for said authorization of said transaction, such that said provider device only provides an encrypted provider half of said transaction to said intermediate entity and said user device only provides an encrypted user half of said transaction to said intermediate entity,said intermediate entity decrypting said encrypted one-time-use provider code and decrypting said encrypted one-time-use user code using one-time-use encryption keys independently produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity,said intermediate entity decrypting said encrypted one-time-use provider code and decrypting said encrypted one-time-use user code to produce unencrypted provider input related to said transaction and unencrypted user input related to said transaction;said intermediate entity combining said unencrypted provider input related to said transaction and said unencrypted user input related to said transaction to generate a single authorization request for said transaction,said intermediate entity obtaining an authorization decision regarding said single authorization request from an authorization entity, andsaid intermediate entity outputting said authorization decision. 2. The system according to claim 1, said intermediate entity comprising: a financial institution; a financial clearing house; a resource controller; and/or a verification entity, said provider device comprising a device operated by: a merchant, a resource storage entity, an access control agent, and/or a communications entity, andsaid user device comprising a device operated by: a customer, a consumer, an organization, and/or an individual. 3. The system according to claim 1, said user devices and said provider devices each only maintaining a unique individual sequencer, and said user devices and said provider devices not having access to sequencers of other user devices or other provider devices. 4. The system according to claim 1, said intermediate entity securely maintaining personal financial information of a user operating said user device, said intermediate entity preventing said user device from maintaining said personal financial information. 5. The system according to claim 1, said encrypted one-time-use provider code and said encrypted one-time-use user code being devoid of personal financial information of a user operating said user device. 6. A system comprising: an intermediate entity maintaining duplicate sequencers used in producing one-time-use encryption keys for registered user devices and registered provider devices,said intermediate entity being operatively connected to a provider device, of said registered provider devices, and a user device, of said registered user devices,said intermediate entity causing said provider device to supply a unique transaction number to said user device,said unique transaction number being related to a transaction between said provider device and said user device,said provider device supplying a different unique transaction number for each different transaction,said intermediate entity causing said provider device to encrypt provider input related to said transaction to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said provider device,said intermediate entity causing said provider device to independently transmit said encrypted one-time-use provider code and said unique transaction number only to said intermediate entity for an authorization of said transaction,said intermediate entity causing said user device to encrypt user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said user device,said intermediate entity causing said user device to independently transmit said encrypted one-time-use user code and said unique transaction number only to said intermediate entity for an authorization of said transaction, such that said provider device only provides an encrypted provider half of said transaction to said intermediate entity and said user device only provides an encrypted user half of said transaction to said intermediate entity,said provider sequencer and said user sequencer separately producing different encryption keys for said transaction, said provider device using said uniquely sequenced number generated by said provider sequencer to produce said encrypted one-time-use provider code for said transaction, and said user device using said uniquely sequenced number generated by said user sequencer to produce said encrypted one-time-use user code for said transaction,said provider sequencer and said user sequencer being separately synchronized with corresponding ones of said duplicate sequencers maintained by said intermediate entity, such that said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and said provider sequencer and said user sequencer produce different encryption keys for a given transaction,said provider sequencer, said user sequencer, and said duplicate sequencers producing different one-time-use encryption keys for each different transaction to prevent any one-time-use encryption key from being used for different transactions,said intermediate entity independently generating said one-time-use provider encryption key and said one-time-use user encryption key using corresponding ones of said duplicate sequencers maintained by said intermediate entity,said intermediate entity decrypting said encrypted one-time-use provider code using said one-time-use provider encryption key produced by said intermediate entity and decrypting said encrypted one-time-use user code using said one-time-use user encryption key produced by said intermediate entity to generate unencrypted provider input and unencrypted user input,said intermediate entity combining said unencrypted provider input and unencrypted user input into a single authorization request,said intermediate entity securely sending said single authorization request to an authorization entity,said authorization entity providing an authorization decision regarding said single authorization request to said intermediate entity, andsaid intermediate entity outputting said authorization decision to complete or decline said transaction. 7. The system according to claim 6, said provider device supplying said unique transaction number to said user device by at least one of: displaying a computer-readable code on a display of said provider device readable by an optical device of said user device;displaying a human-readable code on said display of said provider device positioned to be readable by a user, said user entering said human-readable code into said user device;wirelessly transmitting a code using a wireless device of said provider device capable of wirelessly communicating with a wireless device of said user device; andinternally communicating said unique transaction number from a first application operating on said user device to a second application operating on said user device. 8. The system according to claim 6, said user devices and said provider devices each only maintaining a unique individual sequencer, and said user devices and said provider devices not having access to sequencers of other user devices or other provider devices. 9. The system according to claim 6, said intermediate entity securely maintaining personal financial information of a user operating said user device, said intermediate entity preventing said user device from maintaining said personal financial information. 10. The system according to claim 6, said encrypted one-time-use provider code and said encrypted one-time-use user code being devoid of personal financial information of a user operating said user device. 11. A method comprising: maintaining, by an intermediate entity, duplicate sequencers used in producing one-time-use encryption keys for registered user devices and registered provider devices;causing, by said intermediate entity, a provider device, of said registered provider devices, to encrypt provider input related to a transaction between said provider device and a user device, of said registered user devices, to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said provider device;causing, by said intermediate entity, said user device to encrypt user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said user device;causing, by said intermediate entity, said provider device to independently transmit said encrypted one-time-use provider code to said intermediate entity for an authorization of said transaction, and said user device to independently transmit said encrypted one-time-use user code to said intermediate entity for said authorization of said transaction, such that said provider device only provides an encrypted provider half of said transaction to said intermediate entity and said user device only provides an encrypted user half of said transaction to said intermediate entity;decrypting, by said intermediate entity, said encrypted one-time-use provider code and decrypting said encrypted one-time-use user code using said one-time-use encryption keys produced by said intermediate entity using corresponding ones of said duplicate sequencers maintained by said intermediate entity to produce unencrypted provider input related to said transaction and unencrypted user input related to said transaction;combining, by said intermediate entity, said unencrypted provider input related to said transaction and said unencrypted user input related to said transaction to generate a single authorization request for said transaction;obtaining, by said intermediate entity, an authorization decision regarding said single authorization request from an authorization entity; andoutputting, by said intermediate entity, said authorization decision,said provider sequencer and said user sequencer separately producing different encryption keys for said transaction, said provider device using said uniquely sequenced number generated by said provider sequencer to produce said encrypted one-time-use provider code for said transaction, and said user device using said uniquely sequenced number generated by said user sequencer to produce said encrypted one-time-use user code for said transaction,said provider sequencer and said user sequencer being separately synchronized with corresponding ones of said duplicate sequencers maintained by said intermediate entity, such that said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and said provider sequencer and said user sequencer produce different encryption keys for a given transaction, andsaid provider sequencer, said user sequencer, and said duplicate sequencers producing different one-time-use encryption keys for each different transaction to prevent any one-time-use encryption key from being used for different transactions. 12. The method according to claim 11, said intermediate entity comprising: a financial institution; a financial clearing house; a resource controller; and/or a verification entity, said provider device comprising a device operated by: a merchant, a resource storage entity, an access control agent, and/or a communications entity, andsaid user device comprising a device operated by: a customer, a consumer, an organization, and/or an individual. 13. The method according to claim 11, said user devices and said provider devices each only maintaining a unique individual sequencer, and said user devices and said provider devices not having access to sequencers of other user devices or other provider devices. 14. The method according to claim 11, further comprising: securely maintaining, by said intermediate entity, personal financial information of a user operating said user device; andpreventing, by said intermediate entity, said user device from maintaining said personal financial information. 15. The method according to claim 11, said encrypted one-time-use provider code and said encrypted one-time-use user code being devoid of personal financial information of a user operating said user device. 16. A method comprising: establishing accounts of registered users through registered user devices and registered providers through registered provider devices, using an intermediate entity;maintaining, by said intermediate entity, duplicate sequencers used in producing one-time-use encryption keys for said registered user devices and said registered provider devices,causing, by said intermediate entity, a provider device of said registered provider devices to supply a unique transaction number to a user device of said registered user devices, said unique transaction number being related to a transaction between said provider device and said user device, said provider device supplying a different unique transaction number for each different transaction,causing, by said intermediate entity, said provider device to encrypt provider input related to said transaction to create an encrypted one-time-use provider code using a one-time-use provider encryption key produced, in part, using a uniquely sequenced number generated by a provider sequencer maintained by said provider device,causing, by said intermediate entity, said provider device to independently transmit said encrypted one-time-use provider code and said unique transaction number only to said intermediate entity for an authorization of said transaction,causing, by said intermediate entity, said user device to encrypt user input related to said transaction to create an encrypted one-time-use user code using a one-time-use user encryption key produced, in part, using a uniquely sequenced number generated by a user sequencer maintained by said user device,causing, by said intermediate entity, said user device to independently transmit said encrypted one-time-use user code and said unique transaction number only to said intermediate entity for an authorization of said transaction, such that said provider device only provides an encrypted provider half of said transaction to said intermediate entity and said user device only provides an encrypted user half of said transaction to said intermediate entity, said provider sequencer and said user sequencer separately producing different encryption keys for said transaction, said provider device using said uniquely sequenced number generated by said provider sequencer to produce said encrypted one-time-use provider code for said transaction, and said user device using said uniquely sequenced number generated by said user sequencer to produce said encrypted one-time-use user code for said transaction, said provider sequencer and said user sequencer being separately synchronized with corresponding ones of said duplicate sequencers maintained by said intermediate entity, such that said provider sequencer is synchronized with a corresponding duplicate sequencer maintained by said intermediate entity and said user sequencer is synchronized with a different duplicate sequencer maintained by said intermediate entity, and said provider sequencer and said user sequencer produce different encryption keys for a given transaction, said provider sequencer, said user sequencer, and said duplicate sequencers producing different one-time-use encryption keys for each different transaction to prevent any one-time-use encryption key from being used for different transactions,independently generating, by said intermediate entity, said one-time-use provider encryption key and said one-time-use user encryption key using corresponding ones of said duplicate sequencers maintained by said intermediate entity,decrypting, by said intermediate entity, said encrypted one-time-use provider code using said one-time-use provider encryption key produced by said intermediate entity and decrypting said encrypted one-time-use user code using said one-time-use user encryption key produced by said intermediate entity to generate unencrypted provider input and unencrypted user input,combining, by said intermediate entity, said unencrypted provider input and unencrypted user input into a single authorization request,securely sending, by said intermediate entity, said single authorization request to an authorization entity,obtaining, by said intermediate entity, an authorization decision regarding said single authorization request from an authorization entity; andoutputting, by said intermediate entity, said authorization decision to complete or decline said transaction. 17. The method according to claim 16, said causing said provider device to supply said unique transaction number to said user device comprising at least one of: causing said provider device to display a computer-readable code on a display of said provider device readable by an optical device of said user device;causing said provider device to display a human-readable code on said display of said provider device positioned to be readable by a user, said user entering said human-readable code into said user device;causing said provider device to wirelessly transmit a code using a wireless device of said provider device capable of wirelessly communicating with a wireless device of said user device; andcausing said provider device to internally communicate said unique transaction number from a first application operating on said user device to a second application operating on said user device. 18. The method according to claim 16, said user devices and said provider devices each only maintaining a unique individual sequencer, and said user devices and said provider devices not having access to sequencers of other user devices or other provider devices. 19. The method according to claim 16, further comprising: securely maintaining, by said intermediate entity, personal financial information of a user operating said user device; andpreventing, by said intermediate entity, said user device from maintaining said personal financial information. 20. The method according to claim 16, said encrypted one-time-use provider code and said encrypted one-time-use user code being devoid of personal financial information of a user operating said user device.
연구과제 타임라인
LOADING...
LOADING...
LOADING...
LOADING...
LOADING...
이 특허에 인용된 특허 (21)
Bhagavatula,Ravishankar S.; Balasubramanian,Chandra S.; Sherwin,Francis M.; Keresman, III,Michael A.; Bowman,Jeffry J., Centralized identity authentication for electronic communication networks.
Franklin D. Chase ; Rosen Daniel ; Benaloh Josh ; Simon Daniel R., Electronic online commerce card with customer generated transaction proxy number for online transactions.
Nobrega,Ryan J.; Valloppillil,Vinod V., Method and apparatus for performing a credit based transaction between a user of a wireless communications device and a provider of a product or service.
Turgeon,Paul Charles, System and method for providing secure services over public and private networks using a removable portable computer-readable storage.
James Mi ; Vishesh Parikh ; Albert Teng, System and method for using internet based caller ID for controlling access to an object stored in a computer.
Ginter Karl L. ; Shear Victor H. ; Sibert W. Olin ; Spahn Francis J. ; Van Wie David M., Systems and methods for secure transaction management and electronic rights protection.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.