SERIAL NUMBER AND PAYMENT DATA BASED PAYMENT CARD PROCESSING

• US 20090144205A1
• Filed: 05/29/2008
• Published: 06/04/2009
• Est. Priority Date: 11/29/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: HURRY, SIMON J.
• Granted Patent: US 9,349,127 B2
• Time in Patent Office: Days
• US Class Current: 705/75
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02
• CPC Class Codes: H04N 21/2542 for selling goods, e.g. TV shopping payment schemes, payment architectures or payment protocols for electronic shopping systems G06Q20/12
• CPC Class Codes: H04N 21/2543 Billing , e.g. for subscription services payment schemes, architectures or protocols G06Q20/00; e-commerce G06Q30/00; arrangements for billing for the use of broadcast information or broadcast-related information H04H60/21
• CPC Class Codes: H04N 21/4182 for identification purposes, e.g. storing user identification data, preferences, personal settings or data restricting access to computer systems by authenticating users using a predetermined code in combination with an additional device, e.g. dongle or smart card G06F21/123
• CPC Class Codes: H04N 21/42684 Client identification by a unique number or address, e.g. serial number, MAC address, socket ID network arrangements, protocols or services for addressing or naming H04L61/00
• CPC Class Codes: H04N 21/47815 Electronic shopping payment schemes, payment architectures or payment protocols for electronic shopping systems G06Q20/12

Abstract

A server is operable to receive a media device identifying number (ID) and establish an association between a media device and a payment account and, in one embodiment, supports at least one of payment authorization and payment clearing based at least in part on the media device ID and the payment account. A network and system includes a payment card processor server that is operable to receive a payment authorization request and to determine if an authorized media device generated a purchase selection message and to determine to approve a received payment authorization request based, in part, if the media device was authorized for the purchase selection based upon a received media device ID.

Claims

1. A payment card company server, comprising:

a communication module coupled to at least one communication network;

a processing module coupled to the communication module;

memory coupled to the processing module; and

wherein the processing module, in cooperation with the communication module, is operable to;

receive a payment authorization request message originated by a merchant server, wherein the payment authorization request message including a payment authorization request that is based on a purchase selection message originated by a media device and includes user payment account information corresponding to a user payment account;

receive a media device ID corresponding to the media device that originated the purchase selection message;

determine whether the media device ID corresponds to an authorized media device having an established association with the user payment account; and

validate the payment authorization request based in part on determining that the media device ID corresponds to the authorized media device.

2. The payment card company server of claim 1 wherein the payment authorization request includes user payment account information that was included within the purchase selection message.

3. The payment card company server of claim 2 wherein the processing module is operable to:

additionally determine whether the media device is authorized to originate the purchase selection message with the user account information at time of generation of the purchase selection message; and

place an authorization hold on an amount based upon an amount specified in the received payment authorization message.

4. The payment card company server of claim 1 wherein the processing module is further operable to, when the payment card company server is not operating as a financial institution issuer server:

determine the financial institution issuer server corresponding to the user payment account; and

transmit, in cooperation with the communication module, a payment card issuer payment authorization request message that includes the payment authorization request to the financial institution issuer server when the media device ID corresponds to the authorized media device.

5. The payment card company server of claim 1 wherein the processing module is further operable, in cooperation with the communication module, to transmit an approval indication message to approve the payment authorization request based at least in part on determining that the media device ID corresponds to the authorized media device.

6. The payment card company server of claim 1 wherein the processing module is operable to:

retrieve an authorized media device ID from the user payment account information; and

compare the authorized media device ID to the media device ID to determine whether the media device ID corresponds to an authorized media device.

7. The payment card company server of claim 1 wherein the processing module is further operable:

retrieve from memory an authorized media device ID; and

compare the authorized media device ID to the media device ID to determine whether the media device ID corresponds to an authorized media device.

8. The payment card company server of claim 7 wherein the processing module is further operable to:

receive the authorized media device ID prior to receiving the payment authorization request message; and

store the authorized media device ID in the memory.

9. The payment card company server of claim 1 wherein the processing module is further operable to:

select an encryption key based upon the media device ID;

decrypt a portion of the user payment information using the selected encryption key; and

determine that the media device ID corresponds to the authorized media device having the established association with the user payment account when the user payment account information is successfully decrypted using the selected encryption key.

10. The payment card company server of claim 9 further including logic to store encryption keys in relation to authorized media device IDs.

11. The payment card company server of claim 1 wherein the processing module is further operable to receive the media device ID with the payment authorization request message.

12. The payment card company server of claim 1 wherein the processing module is further operable to:

receive the media device ID with transaction identification information; and

associate the media device ID with the corresponding payment authorization request based on the transaction identification information.

13. A method for approving a payment authorization request, comprising:

receiving a first payment authorization request message that includes a payment authorization request originated by a merchant server, an amount, and user payment account information corresponding to a user payment account, wherein the payment authorization request that is based on a purchase selection message originated by a media device;

receiving a media device ID corresponding to the media device that originated the purchase selection message;

determining whether the media device ID corresponds to an authorized media device having an established association with the user payment account;

validating the payment authorization request based in part on determining that the media device ID corresponds to the authorized media device; and

transmitting a second payment authorization request to a financial institution issuer server.

14. The method of claim 13 further including:

determining a financial institution issuer server corresponding to the user payment account; and

transmitting the second payment card issuer payment authorization request message that includes the payment authorization request to the financial institution issuer server when the media device ID corresponds to the authorized media device.

15. The method of claim 13 further including:

transmitting, based at least in part on whether the media device ID corresponds to the authorized media device, an approval indication message to approve the payment authorization request; and

placing an authorization hold on an amount based upon an amount specified in the received payment authorization message.

16. The method of claim 13 further including:

retrieving an authorized media device ID from the user payment account information; and

comparing the authorized media device ID to the media device ID to determine whether the media device ID corresponds to an authorized media device.

17. The method of claim 13 further including:

retrieving from memory an authorized media device ID; and

comparing the authorized media device ID to the media device ID to determine whether the media device ID corresponds to an authorized media device.

18. The method of claim 13 further including:

selecting an encryption key based upon the media device ID;

decrypting a portion of the user payment information using the selected encryption key; and

determining that the media device ID corresponds to the authorized media device having the established association with the user payment account when the user payment account information is successfully decrypted using the selected encryption key.

19. A method, comprising:

receiving a first payment authorization request message that includes a payment authorization request that is based on a purchase selection message and wherein the payment authorization request message that further includes user payment account information for a user payment account;

receiving a media device ID, the media device ID corresponding to a media device that transmitted the purchase selection message; and

determining whether the media device ID is for an authorized media device having an established association with the user payment account by one of;

comparing the received media device ID to an authorized media device ID transmitted within the user payment account information;

comparing the received media device ID to an authorized media device ID stored in memory;

or

selecting an encryption key based on the received media device ID and successfully decrypting an encrypted portion of the user payment account information using the selected encryption key whereby only an encryption key that corresponds to an authorized media device is operable to successfully decrypt the encrypted portion of the user payment account information.

20. The method of claim 19 further including transmitting a second payment authorization request message to a financial institution issuer server of a payment card company if the media device ID corresponds to the authorized media device.

21. The method of claim 19 further including:

receiving and storing the authorized media device ID;

subsequently receiving the media device ID and the payment authorization request message;

comparing the media device ID to the authorized media device ID; and

determining that the media device ID corresponds to the authorized media device.

22. The method of claim 19 further including:

establishing an encrypted communication link with one of a media server, the media device, or a smart card installed within the media device; and

receiving the authorized media device ID and corresponding user payment account information through the established encrypted communication link.

23. The method of claim 22 further including storing the authorized media device ID.

24. The method of claim 22 further including:

selecting, receiving or determining an encryption key for decrypting at least a portion of the user payment account information; and

storing the encryption key in relation to the authorized media device ID to create an association between the encryption key and the authorized media device.

25. The method of claim 24 further including:

selecting an encryption key of a plurality of encryption keys based upon the received media device ID; and

decrypting the encrypted portion of the user payment account information.