Account holder demand account update

• US 8,706,622 B2
• Filed: 08/05/2008
• Issued: 04/22/2014
• Est. Priority Date: 08/05/2008
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Winters, Michelle E., Samad, Lubna, DiGioacchino, Laura
• Primary Examiner(s): Badii, Behrang
• Assistant Examiner(s): GREENE, DANIEL LAWSON
• Application Number:
  US12/186,369
• Publication Number:
  US 20100036769A1
• Time in Patent Office: 2,086 Days
• Field of Search: 705/40
• US Class Current: 705/40
• 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/102 Bill distribution or payments
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Account holder identification is used to access and retrieve the account holder'"'"'s accounts and attributes thereof. A user interface receives a selected account for which merchants having conducted transactions on the selected account are retrieved and displayed on the user interface. The account holder selects which merchants are to receive updated attributes of the selected account, such as a new expiration, a new billing address, a new credit limit, a name change of the account holder, etc. Each user selected merchant is notified of the user selected attributes of the user selected account.

Claims

1. In a payment processing system with issuers issuing accounts to account holders, each said account having one or more attributes, and each of the account holders conducting transactions with respective merchants using corresponding accounts of the account holders, a method comprising:

receiving, at a computing device of a transaction handler, an identification of a first said account holder;

using the received identification, at the computing device, to retrieve from an account database data about a first said account of the first said account holder, wherein the data includes an indicator of the first said account and an attribute of the first said account;

using the indicator, at the computing device, to retrieve from a transaction database a transaction history of the first said account, wherein the transaction history includes a list of past completed transactions conducted on the first said account;

using the transaction history, at the computing device, to retrieve from a merchant database a list of a plurality of said merchants that have each engaged in at least one of the past transactions upon the first said account;

transmitting, at the computing device, the data retrieved from the account database and the list of the plurality of said merchants for rendition of each on a display;

receiving and storing, at the computing device;

an update of the attribute provided by the first said account holder; and

a selection of the first said account holder of at least one said merchant from among the list of the plurality of said merchants that is to receive the update of the attribute;

forming, at the computing device, a transmission for delivery to the issuer of the first said account, the transmission including;

the update of the attribute of the first said account provided by the first said account holder; and

a request for the issuer of the first said account to validate the update of the attribute;

receiving, at the computing device, a transmission from the issuer of the first said account including a validation of the update of the attribute; and

forming, at the computing device, a transmission including the corresponding said validated update of the attribute, wherein the update is for delivery to the selected at least one said merchant.

2. The method as defined in claim 1, further comprising sending a notice that the update of the attribute is to be stored by the selected at least one said merchant in a cards-on file storage device of the selected at least one said merchant.

3. The method as defined in claim 1, further comprising authenticating the identification prior to forming the transmission including the corresponding said validated update of the attribute.

4. The method as defined in claim 1, wherein the transaction database includes a plurality of transaction databases each corresponding to a different said transaction handler that processes at least one of the transactions of the corresponding said merchants upon the corresponding accounts of the account holders.

5. The method as defined in claim 1, wherein the first said account is among a plurality of said accounts each issued to the first said account holder by a different said issuer.

6. The method as defined in claim 1, wherein the merchant database includes a plurality of merchant databases each corresponding to a different said transaction handler that processes at least one of the transactions of the corresponding said merchants upon the corresponding accounts of the account holders.

7. The method as defined in claim 1, further comprising receiving and storing, at the computing device, an indication of the first said account holder of at least one said merchant from among the list of the plurality of said merchants that is not to receive the update to the attribute.

8. The method as defined in claim 1, further comprising receiving and storing, at the computing device, an instruction of the first said account holder to delay an effective date of the update.

9. The method as defined in claim 1, further comprising receiving, at the computing device, the update to the attribute from the issuer of the first said account.

10. The method as defined in claim 1, wherein:

receiving the identification;

using the received identification;

using the indicator;

using the transaction history;

transmitting the data retrieved;

receiving and storing the update of the attribute and the selection; and

forming the transmission for deliver to the issuer of the frist said account;

receiving the transmission from the issuer of the first said account; and

forming the transmission including the corresponding said validated update of the attribute, occur in succession in a batch process.

11. The method as defined in claim 1, wherein the update of the attribute and the selection are received from a POS terminal.

12. The method as defined in claim 1, further comprising receiving and storing, at the computing device, a selection of the first said account holder of a second said merchant that is not among the list of the plurality of said merchants.

13. The method as defined in claim 1, wherein the update of the attribute further comprises a change in mailing or billing address.

14. The method as defined in claim 1, further comprising:

transmitting, at the computing device, a list of accounts of the first said account holder for rendition on the display, wherein the list of accounts includes the first said account; and

receiving, at the computing device, a selection from the first said account holder of the first said account for updating.

15. The method as defined in claim 14, wherein the list of accounts is displayed in a pull down menu that can be scrolled by the first said account holder using a scroll bar.

16. The method as defined in claim 14, wherein the list of accounts is provided by the first said account holder to the transaction handler during a registration process.

17. The method as defined in claim 14, wherein the list of accounts is provided by one or more issuers to the transaction handler.

18. In a payment processing system with issuers issuing accounts to account holders, each said account having one or more attributes, and each of the account holders conducting transactions with respective merchants using corresponding accounts of the account holders, a method comprising:

receiving, at a computing device of a transaction handler, a first transmission including an identification of one said account holder and each corresponding indicator of a plurality of said accounts that are each issued to the one said account holder by a different said issuer;

using, at the computing device, each of the received said indicators to retrieve data about corresponding past said transactions conducted upon the plurality of said accounts issued to the one said account holder;

retrieving, at the computing device, a list of a plurality of said merchants that engaged in the past said transactions;

transmitting, at the computing device, information for rendition to the account holder via a user interface, the information including a query requesting the one said account holder;

to provide an update to an attribute of each of the plurality of said accounts;

to identify said merchants among the list of the plurality of said merchants that are to receive at least one said update; and

to identify said merchants among the list of the plurality of said merchants that are not to receive at least one said update;

receiving, at the computing device, a second transmission including at least one said update provided by the one said account holder, the identified said merchants that are to receive the at least one said update, and the identified said merchants that are not to receive the at least one said update;

forming, at the computing device, a third transmission for delivery to one said issuer, the transmission including;

the update to the attribute of a corresponding said account issued to the account holder by the one said issuer; and

a request for the one said issuer to validate the update to the corresponding said account;

receiving, at the computing device, a fourth transmission from the one said issuer including a validation of the update by the one said issuer; and

forming, at the computing device, a fifth transmission containing the validated said update for delivery to each identified said merchant that is to receive the validated said update.

19. The method as defined in claim 18, further comprising using, at the computing device, the identification to authenticate the account holder prior to forming the third transmission.

20. The method as defined in claim 18, wherein each said account is associated with a different said transaction handler that processes corresponding said transactions upon the each said account.

21. The method as defined in claim 18, further comprising receiving and storing, at the computing device, an instruction of the first said account holder to delay an effective date of at least one said update.

22. The method defined in claim 18, wherein the fourth transmission further includes another said update to another said attribute of the corresponding said account, wherein the another said update is:

provided by the one said issuer; and

is different from the update received in the second transmission.

23. A non-transitory computer readable medium comprising stored instructions that, when executed by a computing device perform the steps of:

receiving, in a batch process;

a selection from an account holder of at least one merchant from among a list of a plurality of said merchants; and

a request from the said account holder to update an attribute of each of a first account and a second account wherein the update is provided by the account holder, and wherein;

the first account;

is issued to the account holder by a first issuer; and

is associated with a first transaction handler that processes transactions upon the first account; and

the second account;

is issued to the account holder by a second issuer that is different from the first issuer; and

is associated with a second transaction handler that;

is different from the first transaction handler; and

processes transactions upon the second account;

forming a first transmission to each of the first issuer and the second issuer, each said first transmission including a request to validate the corresponding said update;

receiving validated corresponding said updates from each of the first issuer and the second issuer; and

for each received validated corresponding said update;

storing, at the computing device, the validated corresponding said update; and

notifying the at least one said merchant that the validated corresponding said update is to be stored by the at least one merchant in a cards-on-file storage device for use in a future transaction between the at least one merchant and the account holder.

24. The non-transitory computer readable medium as defined in claim 23, wherein the request further includes an indication of the account holder of at least one said merchant that is not to receive at least one of the updates.

25. The non-transitory computer readable medium as defined in claim 23, wherein the request further includes a request of the account holder to delay an effective date of at least one of the updates.

26. The non-transitory computer readable medium as defined in claim 23, wherein the computer readable medium comprises further stored instructions that, when executed by a computing device performs the step of further receiving at least one of the updates to the attribute from at least one of:

the first issuer; and

the second issuer.