IN-MARKET PERSONALIZATION OF PAYMENT DEVICES

• US 20160026998A1
• Filed: 10/02/2015
• Published: 01/28/2016
• 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,916,576 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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

Described are methods and systems for remotely personalizing a payment device. In an embodiment, a trusted service provider (TSP) personalization server receives a payment device personalization request from a remote personalization device (RPD), determines that a hardware security token (HST) permits issuance of the payment device, and transmits a personalization data request to an issuer. The TSP personalization server then receives the requested personalization data from a Mobile Over-the-Air Provisioning Service (MOTAPS) server, generates session keys, converts data from the MOTAPS server into payment device application process data unit (APDU) data, and then transmits the personalization data and APDU data to the RPD to load onto a payment device.

Claims

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

receiving, by a trusted service provider (TSP) personalization server computer from a remote personalization device (RPD), a payment device personalization request for personalizing a particular type of payment device;

determining, by the TSP personalization server computer, that a hardware security token (HST) associated with the RPD permits issuance of the particular type of payment device;

transmitting, by the TSP personalization server computer to an issuer server computer, a personalization data request;

receiving, by the TSP personalization server computer from a Mobile Over-the-Air Provisioning Service (MOTAPS) server computer, the requested personalization data;

generating, by the TSP Personalization Server computer in concert with a Hardware Security Module (HSM), session keys;

converting, by the TSP personalization server computer using the session keys, data from the MOTAPS server computer into payment device application process data unit (APDU) data; and

transmitting, by the TSP personalization server computer to the RPD, the APDU data and the personalization data for loading onto a payment device.

2. The method of claim 1, further comprising receiving, by the TSP personalization server computer from the RPD, a confirmation response confirming that the payment device has been personalized.

3. The method of claim 1, further comprising determining, by the TSP personalization server computer, prior to transmitting the request for personalization data, that security checks concerning the RPD failed;

and

transmitting, by the TSP personalization server computer to the RPD, a payment device personalization request denied message.

4. The method of claim 1, further comprising requiring, by the TSP personalization server computer, prior to transmitting the request for personalization data, that security checks indicate that a valid RPD made the personalization request.

5. The method of claim 1, further comprising, determining, prior to generating the session keys by the TSP personalization server computer, that the requested personalization data failed to arrive from the MOTAPS server computer within a predetermined period of time;

and

transmitting, by the TSP personalization server computer to the RPD, a payment device personalization request denied message.

6. The method of claim 1, further comprising receiving, by the TSP personalization server computer from the RPD, a confirmation message confirming that the payment device has been personalized and that the RPD performed at least one additional required function before issuing the payment device to a consumer.

7. The method of claim 6, wherein the at least one additional required function comprises testing the payment device.

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

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

12. The method of claim 1, wherein the payment device comprises a non-card form factor device.

13. The method of claim 1, wherein the payment device comprises a proximity payment device.

8. The method of 6, wherein the at least one additional required function comprises enabling the payment device.

9. The method of 6, wherein the at least one additional required function comprises loading value on the payment device.

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

a Mobile Over-the-Air Provisioning Service (MOTAPS) server computer;

a trusted service provider (TSP) personalization server computer operatively coupled to the MOTAPS server computer, the TSP personalization server computer receiving personalization data from the MOTAPS server computer and transmitting personalization data and instructions;

a hardware security module (HSM) operatively coupled to the TSP personalization server computer;

an issuer server computer operably coupled to at least one of the MOTAPS server computer and the TSP personalization server computer;

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

a remote personalization device (RPD) operably coupled to the service provider server computer, the RPD receiving a request from a consumer to provide a personalized payment device to the consumer;

and wherein the TSP personalization server computer;

receives a payment device personalization request for personalizing a particular type of payment device from the RPD;

determines that a hardware security token (HST) associated with the RPD permits issuance of the particular type of payment device;

transmits a personalization data request to the issuer server computer;

receives the requested personalization data from the MOTAPS server computer;

generates session keys in concert with the HSM;

converts data from the MOTAPS server computer into payment device application process data unit (APDU) data using the session keys; and

transmits the APDU data and the personalization data to the RPD for loading onto a payment device.

15. The system of claim 14, wherein, subsequent to transmitting the APDU data and the personalization data to the RPD, the TSP personalization server receives a confirmation response from the RPD confirming that the payment device has been personalized.

16. The system of claim 14, 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.

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

18. The system of claim 14, 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;

a communication link operably connected 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.

19. The system of claim 18, 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.

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

21. The system of claim 14, 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.

22. The system of claim 14, wherein the TSP personalization server computer is operated on behalf of a financial institution that issued a payment card account to a consumer.