Payment information technologies

• US 9,947,007 B2
• Filed: 01/27/2014
• Issued: 04/17/2018
• Est. Priority Date: 01/27/2013
• Status: Active Grant

• Current Assignee: Barry Greenbaum, Roman Tsibulevskiy
• Original Assignee: Barry Greenbaum, Roman Tsibulevskiy
• Inventors: Tsibulevskiy, Roman, Greenbaum, Barry
• Primary Examiner(s): Niquette, Robert R
• Assistant Examiner(s): Jacob, William J
• Application Number:
  US14/165,240
• Publication Number:
  US 20140214654A1
• Time in Patent Office: 1,541 Days
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/321 using wearable devices
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards

Abstract

A method includes maintaining first payment card information for a cardholder. The method includes processing a first card not present transaction between the cardholder and a merchant. The first transaction based at least in part on the first information. The method includes generating second payment card information for the cardholder. The second information replacing the first information for subsequent use via the cardholder. The method includes receiving an input from the cardholder. The input indicating the merchant. The input based at least in part on the second information replacing the first information. The method includes sending the second information to the merchant based at least in part on the input. The method includes processing a second card not present transaction between the cardholder and the merchant. The second transaction based at least in part on the second information after the sending.

Claims

1. A method of selectively updating cardholder payment information for card not present transactions, the method comprising:

sending, by a credit card issuer server, a set of processor-executable instructions to a merchant server hosting a first operating system and a first application, wherein the first application runs on the first operating system, wherein the set of processor-executable instructions configures the first application to receive a first credit card number after the merchant server executes the set of processor-executable instructions, wherein the credit card issuer server is remote from the merchant server;

processing, by the credit card issuer server, a plurality of card not present transaction messages comprising a plurality of merchant identifiers, wherein the merchant identifiers are distinct from each other, wherein the card not present transaction messages involve a second credit card number stored in a cardholder account record stored in a database accessible to the credit card issuer server;

deactivating, by the credit card issuer server, the second credit card number in the cardholder account record such that the second credit card number is transactionally unusable;

activating, by the credit card issuer server, based at least in part on the deactivating, a third credit card number stored in the cardholder account record such that the third credit card number is transactionally usable, wherein the third credit card number has same format as the first credit card number;

after the merchant server executes the set of processor-executable instructions;

accessing, by the credit card issuer server, a plurality of transaction records in the database, wherein the transaction records reference the merchant identifiers;

identifying, by the credit card issuer server, based at least in part on the accessing, a merchant identifier from the merchant identifiers based at least in part on a frequency of the card not present transaction messages associated with the merchant identifier, wherein the merchant identifier is associated with the merchant server;

serving, by the credit card issuer server, based at least in part on the identifying, a display of the merchant identifier in a graphical user interface of a second application running on a second operating system of a cardholder client associated with the cardholder account record, wherein the credit card issuer server is remote from the cardholder client, wherein the cardholder client includes a user input device, wherein the first application is distinct from the second application, wherein the first operating system is distinct from the second operating system;

receiving, by the credit card issuer server, an input from the cardholder client based at least in part on the display, wherein the input is indicative of the merchant identifier, wherein the input is via the user input device while the merchant identifier is displayed in the graphical user interface;

accessing, by the credit issuer server, based at least in part on the receiving, the third credit card number in the cardholder account record;

sending, by the credit card issuer server, the third credit card number to the merchant server based at least in part on the accessing the third credit card number;

processing, by the credit card issuer server, a card not present transaction message involving the third credit card number based at least in part on the sending the third credit card number such that the transaction records can be updated to reference the card not present transaction message, wherein the card not present transaction message is associated with the merchant identifier.

2. The method of claim 1, further comprising:

receiving, by the credit card issuer server, a message from the merchant server, wherein the message informs of a receipt of the third credit card number by the merchant server based at least in part on the sending.

3. The method of claim 1, further comprising:

receiving, by the credit card issuer server, a message from the merchant server, wherein the message informs of a storage of the third credit card number on a data store coupled to the merchant server.

4. The method of claim 1, wherein the input is indicative of the merchant identifier via at least one of an alphanumeric text, a voice, an image, a symbol, or a selection from a plurality of choices.

5. The method of claim 1, wherein the input is indicative of the merchant identifier via at least one of a text box, a combo box, a radio button, a check box, a split button, a slider, a list box, a spinner, a drop-down list, a control menu, a pie menu, or a ribbon presented in the graphical user interface.

6. The method of claim 1, wherein the sending of the third credit card number is without the merchant server being informed by the credit card issuer server of the sending the third credit card number prior to the sending of the third credit card number.

7. The method of claim 1, wherein the third credit card number is sent via at least one of alphanumeric, symbolic, audio, or video data.

8. The method of claim 1, wherein the third credit card number is sent in an amended manner.

9. The method of claim 1, wherein the sending of the third credit card number is via at least one of a browser-based email, a client-based email, an instant message, a text message, a short message service, a chat, a voice chat, a web conference, a physical snail mail, a telephone, a facsimile, a webpage, a social media post, a social media message, a module-to-module message, a hypertext transfer protocol, or a file transfer protocol.

10. The method of claim 1, wherein the sending of the third credit card number is without a message requesting the merchant server to update cardholder payment information.

11. The method of claim 1, further comprising:

providing, by the credit card issuer server, a hyperlink to the merchant server before the sending of the third credit card number, wherein the hyperlink is programmed to lead to a network page containing the third credit card number, wherein the sending of the third credit card number is based at least in part on activating the hyperlink based at least in part on the providing.

12. The method of claim 1, further comprising:

receiving, by the credit card issuer server, a preference list from the merchant server, wherein the preference list lists a preferred manner of sending the third credit card number, wherein the sending of the third credit card number is based at least in part on the preference list.

13. The method of claim 1, further comprising:

sending, by the credit card issuer server, a message to the cardholder client, wherein the message informs of the sending of the third credit card number.

14. The method of claim 1, wherein the sending of the third credit card number comprises sending non-payment information from the cardholder account record to the merchant server.

15. The method of claim 1, wherein the set of processor-executable instructions facilitates a storage of the third credit card number on a data store coupled to the merchant server.

16. A method of selectively updating cardholder payment information for card not present transactions, the method comprising:

sending, by a debit card issuer server, a set of processor-executable instructions to a merchant server hosting a first operating system and a first application, wherein the first application runs on the first operating system, wherein the set of processor-executable instructions configures the first application to receive a first debit card number after the merchant server executes the set of processor-executable instructions, wherein the debit card issuer server is remote from the merchant server;

processing, by the debit card issuer server, a plurality of card not present transaction messages comprising a plurality of merchant identifiers, wherein the merchant identifiers are distinct from each other, wherein the card not present transaction messages involve a second debit card number stored in a cardholder account record stored in a database accessible to the debit card issuer server;

deactivating, by the debit card issuer server, the second debit card number in the cardholder account record such that the second debit card number is transactionally unusable;

activating, by the debit card issuer server, based at least in part on the deactivating, a third debit card number stored in the cardholder account record such that the third debit card number is transactionally usable, wherein the third debit card number has same format as the first debit card number;

after the merchant server executes the set of processor-executable instructions;

accessing, by the debit card issuer server, a plurality of transaction records in the database, wherein the transaction records reference the merchant identifiers;

identifying, by the debit card issuer server, based at least in part on the accessing, a merchant identifier from the merchant identifiers based at least in part on a frequency of the card not present transaction messages associated with the merchant identifier, wherein the merchant identifier is associated with the merchant server;

serving, by the debit card issuer server, based at least in part on the identifying, a display of the merchant identifier in a graphical user interface of a second application running on a second operating system of a cardholder client associated with the cardholder account record, wherein the debit card issuer server is remote from the cardholder client, wherein the cardholder client includes a user input device, wherein the first application is distinct from the second application, wherein the first operating system is distinct from the second operating system;

receiving, by the debit card issuer server, an input from the cardholder client based at least in part on the display, wherein the input is indicative of the merchant identifier, wherein the input is via the user input device while the merchant identifier is displayed in the graphical user interface;

accessing, by the debit card issuer server, based at least in part on the receiving, the third debit card number in the cardholder account record;

sending, by the debit card issuer server, the third debit card number to the merchant server based at least in part on the accessing the third debit card number;

processing, by the debit card issuer server, a card not present transaction message involving the third debit card number based at least in part on the sending the third debit card number such that the transaction records can be updated to reference the card not present transaction message, wherein the card not present transaction message is associated with the merchant identifier.

18. The method of claim 16, wherein at least one of:

the input is indicative of the merchant identifier based at least in part on the input being received via at least one of a text box, a combo box, a radio button, a check box, a split button, a slider, a list box, a spinner, a drop-down list, a control menu, a pie menu, or a ribbon shown in the graphical user interface,

the sending of the third debit card number is without the merchant server being informed by the debit card issuer server of the sending the third debit card number prior to the sending of the third debit card number, or

the sending of the third debit card number is without a message requesting the merchant server to update cardholder payment information.

19. The method of claim 16, further comprising at least one of:

receiving, by the debit card issuer server, a message from the merchant server, wherein the message informs of a receipt of the third debit card number by the merchant server based at least in part on the sending,

receiving, by the debit card issuer server, a message from the merchant server, wherein the message informs of a storage of the third debit card number on a data store coupled to the merchant server, or

sending, by the debit card issuer server, a message to the client, wherein the message informs of the sending of the third debit card number.

20. The method of claim 16, wherein the set of processor-executable instructions facilitates a storage of the third debit card number on a data store coupled to the merchant server.

17. A method of selectively updating cardholder payment information for card not present transactions, the method comprising:

sending, by a payment card issuer server, a set of processor-executable instructions to a merchant server hosting a first operating system and a first application, wherein the first application runs on the first operating system, wherein the set of processor-executable instructions configures the first application to receive a first payment card number after the merchant server executes the set of processor-executable instructions, wherein the payment card issuer server is remote from the merchant server;

processing, by the payment card issuer server, a plurality of card not present transaction messages comprising a plurality of merchant identifiers, wherein the merchant identifiers are distinct from each other, wherein the card not present transaction messages involve a second payment card number stored in a cardholder account record stored in a database accessible to the payment card issuer server;

deactivating, by the payment card issuer server, the second payment card number in the cardholder account record such that the second payment card number is transactionally unusable;

activating, by the payment card issuer server, based at least in part on the deactivating, a third payment card number stored in the cardholder account record such that the payment card number is transactionally usable, wherein the third payment card number has same format as the first payment card number;

after the merchant server executes the set of processor-executable instructions;

accessing, by the payment card issuer server, a plurality of transaction records in the database, wherein the transaction records reference the merchant identifiers;

identifying, by the payment card issuer server, based at least in part on the accessing, a merchant identifier from the merchant identifiers based at least in part on at least one of a frequency of the card not present transaction messages, an amount per card not present transaction message from the card not present transaction messages, or a card not present total amount spent per merchant identifier from the card not present transaction messages, wherein the merchant identifier is associated with the merchant server;

serving, by the payment card issuer server, based at least in part on the identifying, a graphical output of the merchant identifier in a second application running on a second operating system of a client associated with the cardholder account record, wherein the client includes a user input device, wherein the first application is distinct from the second application, wherein the first operating system is distinct from the second operating system;

receiving, by the payment card issuer server, an input from the client based at least in part on the graphical output, wherein the input is indicative of the merchant identifier, wherein the input is via the user input device while the merchant identifier is graphically output in the second application;

accessing, by the payment card issuer server, based at least in part on the receiving, the third payment card number in the cardholder account record;

sending, by the payment card issuer server, the third payment card number to the merchant server based at least in part on the accessing;

processing, by the payment card issuer server, a card not present transaction message involving the third payment card number based at least in part on the sending the third payment card number such that the transaction records can be updated to reference the card not present transaction message, wherein the card not present transaction message is associated with the merchant server.