IN-MARKET PERSONALIZATION OF PAYMENT DEVICES

• US 20130067216A1
• Filed: 10/07/2011
• Published: 03/14/2013
• Est. Priority Date: 09/14/2011
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Tanner, Colin, Evans, Paul Michael, Smith, Theresa L.
• Granted Patent: US 9,172,539 B2
• Time in Patent Office: Days
• US Class Current: 713/155
• CPC Class Codes: G06Q 20/18 involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
• CPC Class Codes: G06Q 20/354 Card activation or deactivation
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G06Q 20/3558 Preliminary personalisation for transfer to user
• CPC Class Codes: G06Q 2220/10 Usage protection of distributed data files
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Systems and methods for remotely personalizing payment devices for consumers are described. In an embodiment, a system includes a MOTAPS server computer that provides data preparation functions and a trusted service provider (TSP) personalization server computer. The system also includes a service provider computer operably coupled to the TSP personalization server computer, and a remote personalization device (RPD) operably coupled to the service provider computer. The RPD transmits personalization requests, receives personalization data, and personalizes a payment device before providing the personalized payment device to a consumer.

Claims

1. A system for remotely personalizing payment devices for consumers, comprising:

a MOTAPS server computer providing data preparation functionality using a two key-zone process;

a trusted service provider (TSP) personalization server computer operatively coupled to the MOTAPS server, the TSP personalization server computer operable to receive personalization data and to transmit personalization data and instructions;

a service provider server computer operably coupled to the TSP server computer; and

a remote personalization device (RPD) operably coupled to the service provider server computer, the RPD operable to transmit personalization requests to the service provider server computer, to receive personalization data from the service provider server computer, and to personalize a payment device before providing the personalized payment device to a consumer;

wherein the TSP personalization server communicates with the MOTAPS server computer and the service provider server computer to securely provide personalization data and instructions to the RPD during the personalization process, and that operates to update at least one database concerning data associated with the personalized proximity device.

2. The system of claim 1, further comprising an Issuer Server computer operably coupled to at least one of the MOTAPS server computer and the TSP server computer.

3. The system of claim 1, further comprising a hardware security module (HSM) operatively coupled to the TSP personalization server computer, wherein the HSM functions to generate session keys for use during personalization.

4. The system of claim 3, wherein the HSM is coupled to the TSP personalization server computer via a dedicated local area network.

5. The system of claim 1, further comprising a hardware security token (HST) operably coupled to the RPD, the HST storing at least one cryptographic key required to authenticate the RPD to the TSP Personalization Server computer.

6. The system of claim 5, wherein the HST further comprises volatile memory for storing the at least one cryptographic key so that a power loss terminates a personalization session.

7. The system of claim 1, wherein the RPD is a kiosk comprising:

a housing;

a user interface located on an outside portion of the housing that is accessible to a consumer;

a card reader operably coupled to the user interface, the card reader also located on an outside portion of the housing that is accessible to a consumer;

a central processing unit (CPU) within the housing and operably coupled to the user interface and to a communication link, wherein the communication link provides for communications between the CPU and the service provider server computer;

a hardware security token (HST) operably coupled to the CPU; and

a dispenser means for at least one of dispensing a personalized payment device to a consumer or retaining a faulty payment device.

8. The system of claim 7, wherein the dispenser means comprises:

a payment device reader operably coupled to the CPU;

a payment device storage and feed mechanism for transporting a stored payment device to the payment device reader;

a faulty payment device storage bin; and

a payment device dispenser.

9. The system of claim 7, wherein the CPU and the HST are housed within a secure enclosure within the housing.

10. The system of claim 1, wherein the TSP Personalization server computer is located within a secure hosting facility.

11. The apparatus of claim 1, wherein the RPD comprises at least one of a kiosk, a desk top unit, or an industrial unit for personalizing payment devices in a batch mode.

12. A method of remotely personalizing a payment device, comprising:

receiving, by a TSP Personalization Server computer, a payment device personalization request from a remote personalization device (RPD);

transmitting commands in order to obtain payment device data to identify an Issuers'"'"' personalization key and to obtain diversification data for generating a diversified personalization key;

receiving, from the RPD, the requested payment device data and diversification data;

generating, by the TSP Personalization Server computer in concert with a Hardware Security Module (HSM), session keys required to convert data from a MOTAPS into a payment device application process data unit (APDU);

transmitting the APDU and personalization data to the RPD for loading onto a payment device associated with the RPD; and

receiving a response from the RPD confirming that the payment device has been personalized.

13. The method of claim 12, further comprising receiving, by the TSP Personalization Server computer from the RPD, a confirmation message that the RPD performed additional required functions comprising at least one of testing the payment device, enabling the payment device, loading value on the payment device, and issuing the payment device to a consumer.

14. The method of claim 12, wherein the payment device personalization request from the RPD comprises RPD identification data, proximity device data, personalization data and consumer identification data.

15. The method of claim 14, further comprising, prior to transmitting commands in order to obtain payment device data, determining, based on the RPD identification data, that a hardware security token is permitted to issue the payment device.

16. The method of claim 14, further comprising, prior to transmitting commands in order to obtain payment device data, determining that security checks performed on the consumer identification data have been passed.

17. The method of claim 12, further comprising, prior to generating session keys, requesting personalization data from an Issuer Server computer.

18. The method of claim 12, further comprising at least one of updating a RPD database, transmitting a status update to a MOTAPS server, and updating a payment device database.

19. The method of claim 12, wherein the payment device comprises at least one of a non-card form factor device and a card that includes at least one of a magnetic stripe or a proximity circuit.