Mobile payment management

• US 10,387,868 B2
• Filed: 11/17/2014
• Issued: 08/20/2019
• Est. Priority Date: 01/09/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Wentker, David, Wong, Erick, Diebert, Doug, Shenker, Gavin
• Primary Examiner(s): Sheikh, Asfand M
• Application Number:
  US14/543,608
• Publication Number:
  US 20150066670A1
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3221 Access to banking information through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3229 Use of the SIM of a M-device as secure element
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3267 In-app payments
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 30/0224 based on user history
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04M 15/83 Notification aspects
• CPC Class Codes: H04M 15/8355 after the end of the communication
• CPC Class Codes: H04M 15/84 Types of notifications
• CPC Class Codes: H04M 15/844 Message, e.g. SMS
• CPC Class Codes: H04M 15/85 characterised by the type of condition triggering a notification
• CPC Class Codes: H04M 15/852 Low balance or limit reached
• CPC Class Codes: H04M 15/854 : Available credit
• CPC Class Codes: H04M 15/881 : for continuing the call beyond the limit using allow grace
• CPC Class Codes: H04M 15/93 : using near field or similar technologies
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 88/02 : Terminal devices

Abstract

A method for managing mobile payments in a mobile phone. The method includes receiving data associated with a plurality of issuer specific payment services at a mobile phone, selecting one of the issuer specific payment services, and conducting a transaction using the phone.

Claims

1. A method comprising:

provisioning, by an over-the-air (OTA) service provider computer to a secure element of a mobile phone, issuer specifications for OTA service activation of a plurality of issuer specific payment applications by sending data, associated with the plurality of issuer specific payment applications associated with a plurality of issuer specific payment services provided by a plurality of issuers, to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal;

provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of an issuer specific mobile application on the mobile phone, an account management event,

wherein the mobile phone comprises the secure element storing the plurality of issuer specific payment applications, and a plurality of issuer specific mobile applications stored outside of the secure element, wherein the plurality of issuer specific payment applications stored on the secure element and the plurality of issuer specific mobile applications stored outside of the secure element are linked with unique application identifiers,

wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of issuer specific payment applications and balance information for at least one of the plurality of issuer specific payment applications linked to at least one of the issuer specific payment applications,

wherein a unique application identifier is unique to a first issuer specific payment application of the plurality of issuer specific payment applications and a first issuer specific mobile application of the plurality of issuer specific payment applications that is linked to the first issuer specified payment application so that the issuer specific mobile application stored in the secure element is used with the first issuer specific payment application in order to conduct a transaction; and

sending a plurality of messages from the plurality of issuers to the plurality of issuer specific mobile applications on the mobile phone,

wherein the plurality of messages are formatted and supplied by a messaging service provider to the plurality of issuers, and wherein the messaging service provider is configured to provide at least one of an alert application programming interface, a reporting web interface and a testing hub.

2. The method of claim 1 wherein sending the data associated with the plurality of issuer specific payment applications and sending the plurality of messages are conducted by a mobile operator.

3. The method of claim 1 wherein the messages in the plurality of messages pass through a messaging gateway.

4. The method of claim 1 wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message.

5. The method of claim 1 further comprising, formatting the plurality of messages prior to sending the plurality of messages.

6. The method of claim 1 wherein the messages are SMS messages.

7. The method of claim 1 wherein the issuer specific payment applications respectively perform different sets of issuer specific services.

8. The method of claim 1 wherein the mobile phone is able to communicate via near field communications (NFC) with the contactless reader in the point of sale terminal.

9. The method of claim 1 wherein the mobile phone is able to communicate via near field communications (NFC) with the contactless reader in the point of sale terminal to conduct a payment transaction with the point of sale terminal, the point of sale terminal being at a merchant.

10. The method of claim 1 further comprising:

conducting a payment transaction at the point of sale terminal with the mobile phone using near field communications (NFC).

11. The method of claim 1, wherein the secure element comprises one of embedded hardware, a removable universal subscriber identity module (USIM), and a removable secure digital (SD) card.

12. The method of claim 1, wherein an offer message, comprising one of a coupon, a discount, or a promotion selected by a user, is received and stored in an offer repository of the mobile phone.

13. The method of claim 1, wherein the plurality of issuer specific mobile applications stored outside of the secure element are configured to register payment reminders.

14. The method according to claim 1, wherein the over-the-air (OTA) service provider computer is further configured to perform at least one of loading, installing, personalizing, locking, unlocking and removing one or more of the plurality of issuer specific payment applications on the secure element.

15. The method according to claim 1, further comprising:

receiving an offer message, comprising one of a coupon, a discount, or a promotion selected by a user;

storing the offer message in an offer repository of the mobile phone; and

in response to expiry of the coupon, the discount, or the promotion, deleting the coupon, the discount, or the promotion from the offer repository of the mobile phone.

16. A server computer comprising:

a processor; and

a computer readable medium coupled to the processor, wherein the computer readable medium comprises code executable by the processor to implement a method comprising;

provisioning, by an over-the-air (OTA) service provider computer to a secure element of a mobile phone, issuer specifications for OTA service activation of a plurality of issuer specific payment applications by sending data associated with the plurality of issuer specific payment applications associated with a plurality of issuer specific payment services provided by a plurality of issuers to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal;

provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of an issuer specific mobile application on the mobile phone, an account management event,

wherein the mobile phone comprises the secure element storing the plurality of issuer specific payment applications, and a plurality of issuer specific mobile applications stored outside of the secure element, wherein the plurality of issuer specific payment applications stored on the secure element and the plurality of issuer specific mobile applications stored outside of the secure element are linked with unique application identifiers,

wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of issuer specific payment applications and balance information for at least one of the plurality of issuer specific payment applications linked to at least one of the issuer specific payment applications,

wherein a unique application identifier is unique to a first issuer specific payment application of the plurality of issuer specific payment applications and a first issuer specific mobile application of the plurality of issuer specific payment applications that is linked to the first issuer specified payment application so that the issuer specific mobile application stored in the secure element is used with the first issuer specific payment application in order to conduct a transaction; and

sending a plurality of messages from the plurality of issuers to the plurality of issuer specific mobile applications on the mobile phone,

wherein the plurality of messages are formatted and supplied by a messaging service provider to the plurality of issuers, and wherein the messaging service provider is configured to provide at least one of an alert application programming interface, a reporting web interface and a testing hub.

17. The server computer of claim 16 wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message.

18. A system comprising:

a first server computer comprising a first processor and a first computer readable medium comprising code, executable by the first processor to format a plurality of messages from a plurality of issuers; and

a second server computer coupled to the first server computer, wherein the second server computer is an over-the-air (OTA) service provider computer, the second server computer comprising a second processor, and a second computer readable medium coupled to the second processor, wherein the second computer readable medium comprises code executable by the second processor to implement a method comprising;

provisioning to a secure element of a mobile phone issuer specifications for OTA service activation of a plurality of issuer specific payment applications by sending data associated with the plurality of issuer specific payment applications associated with a plurality of issuer specific payment services to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal;

provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of an issuer specific mobile application on the mobile phone, an account management event,

wherein the mobile phone comprises the secure element storing the plurality of issuer specific payment applications, and a plurality of issuer specific mobile applications stored outside of the secure element, wherein the plurality of issuer specific payment applications stored on the secure element and the plurality of issuer specific mobile applications stored outside of the secure element are linked with unique application identifiers,

wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of issuer specific payment applications and balance information for at least one of the plurality of issuer specific payment applications linked to at least one of the issuer specific mobile applications,

wherein a unique application identifier is unique to a first issuer specific payment application of the plurality of issuer specific payment applications and a first issuer specific mobile application of the plurality of issuer specific payment applications that is linked to the first issuer specified payment application so that the issuer specific mobile application stored in the secure element is used with the first issuer specific payment application when conducting a transaction; and

sending the plurality of messages from the plurality of issuers to the plurality of issuer specific mobile applications on the mobile phone,

wherein the plurality of messages are formatted and supplied by a messaging service provider to the plurality of issuers, and wherein the messaging service provider is configured to provide at least one of an alert application programming interface, a reporting web interface and a testing hub.

19. The system of claim 18 wherein the first server computer is operated by a messaging service provider and the second server computer is operated by a mobile network operator.

20. The system of claim 18 wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message.

21. The system of claim 18 further comprising:

the mobile phone in communication with the second server computer.