PAYMENT ENTITY ACCOUNT SET UP FOR MULTIPLE PAYMENT METHODS

• US 20090112659A1
• Filed: 02/13/2008
• Published: 04/30/2009
• Est. Priority Date: 10/30/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: MULLEN, MATTHEW, MARCHETTI, JOHN N.
• Granted Patent: US 8,311,913 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 20/3572 Multiple accounts on card
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07F 7/10 together with a coded signal , e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data

Abstract

A method begins with a payment entity device receiving payables process data from a client device. The payables process data includes a list of a plurality of creditors and associated payment data, wherein, for a creditor of the plurality of creditors, the associated payment data includes at least one payment scheme for paying at least a portion of debt owed to the creditor via at least one of: a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account. The method continues with the payment entity device determining level of service for a client associated with the client device. The method continues with the payment entity device generating a payables profile for the client based on the payables process data in accordance with the level of service.

Claims

1. A method comprises:

receiving payables process data from a client device, wherein the payables process data includes a list of a plurality of creditors and associated payment data, wherein, for a creditor of the plurality of creditors, the associated payment data includes at least one payment scheme for paying at least a portion of debt owed to the creditor via at least one of;

a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account;

determining level of service for a client associated with the client device; and

generating a payables profile for the client based on the payables process data in accordance with the level of service.

2. The method of claim 1, wherein, when the level of service is a first level of service, the generating the payables profile for one of the plurality of creditors comprises:

storing identification information of the creditor; and

storing the at least one payment scheme for the debt owed to the creditor as the associated payment data.

3. The method of claim 1, wherein, when the level of service is a first level of service, the generating the payables profile for one of the plurality of creditors comprises:

storing identification information of the creditor;

storing a first payment scheme for a first portion of the debt owed to the creditor, wherein the first portion of the debt corresponds to at least one of;

individual transactions below a value threshold, individual transactions purchased via a first purchasing mechanism, and individual transactions corresponding to a first category of services or goods; and

storing a second payment scheme for a second portion of the debt owed to the creditor, wherein the second portion of the debt corresponds to at least one of;

individual transactions at or above the value threshold, individual transactions purchased via a second purchasing mechanism, and individual transactions corresponding to a second category of services or goods, wherein the at least one payment scheme includes the first and second payment schemes.

4. The method of claim 1, wherein the generating the payables profile for one of the plurality of creditors comprises at least one of:

storing a shipping payment scheme for paying shipping costs as part of the associated payment data; and

storing a tax payment scheme for paying taxes associated with goods or services received from the creditor as part of the associated payment data, wherein the at least one payment scheme includes the shipping and tax payment schemes.

5. The method of claim 1, wherein, when the level of service is a second level of service, the generating the payables profile for one of the plurality of creditors comprises:

generating payment program data that, at least, includes a payment program from a financial entity;

transmitting the payment program data to the client device;

storing at least one altered payment scheme in accordance with a selected payment program when a response from the client device indicates changing the associated payment data, wherein the selected payment program is a payment program selected from the payment program data;

storing the at least one payment scheme when a response from the client device to use the at least one payment scheme; and

storing identification information of the creditor.

6. The method of claim 1, wherein, when the level of service is a third level of service, the generating the payables profile for one of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the at least one payment scheme, generating at least one recommended altered payment scheme;

transmitting the at least one recommended altered payment scheme to the client device;

storing the at least one recommended altered payment scheme when a response from the client device to use the at least one recommended altered payment scheme;

storing the at least one payment scheme when a response from the client device to use the at least one payment scheme; and

storing identification information of the creditor.

7. The method of claim 1, wherein, when the level of service is a fourth level of service, the generating the payables profile for one of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the at least one payment scheme, generating at least one recommended altered payment scheme;

storing identification information of the creditor; and

storing the at least one recommended altered payment scheme.

8. The method of claim 1 further comprises:

receiving updated associated payment data for the creditor from the client device; and

updating the payables profile in accordance with the updated associated payment data.

9. The method of claim 1 further comprises when a first update service is enabled:

generating update payment program data that, at least, includes an updated or new payment program from a financial entity;

transmitting the updated payment program data to the client device; and

overwriting the at least one payment scheme with at least one updated payment scheme in accordance with a selected updated payment program when a response from the client device indicates updating the associated payment data, wherein the selected updated payment program is a payment program selected from the updated payment program data.

10. The method of claim 1 further comprises when a second update service is enabled:

generating updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the at least one payment scheme, generating at least one recommended updated payment scheme;

transmitting the at least one recommended updated payment scheme to the client device; and

overwriting the at least one payment scheme with the at least one recommended updated payment scheme when a response from the client device to use the at least one recommended updated payment scheme.

11. The method of claim 1 further comprises when a third update service is enabled:

generating updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of update or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the at least one payment scheme, generating at least one recommended updated payment scheme; and

overwriting the at least one payment scheme with the at least one recommended updated payment scheme.

12. An apparatus comprises:

a processing module; and

memory coupled to the processing module, wherein the processing module functions, at least partially based on operational instructions stored in the memory, to;

receive payables process data from a client device, wherein the payables process data includes a list of a plurality of creditors and associated payment data, wherein, for a creditor of the plurality of creditors, the associated payment data includes at least one payment scheme for paying at least a portion of debt owed to the creditor via at least one of;

a client credit card, a funds transfer, commercial paper, tangible consideration, and a debit account;

determine level of service for a client entity associated with the client device; and

generate a payables profile for the client entity based on the payables process data in accordance with the level of service.

13. The apparatus of claim 12, wherein, when the level of service is a first level of service, the processing module generates the payables profile for one of the plurality of creditors by:

storing identification information of the creditor; and

storing the at least one payment scheme for the debt owed to the creditor as the associated payment data.

14. The apparatus of claim 12, wherein, when the level of service is a first level of service, the processing module generates the payables profile for one of the plurality of creditors by:

storing identification information of the creditor;

storing a first payment scheme for a first portion of the debt owed to the creditor, wherein the first portion of the debt corresponds to at least one of;

individual transactions below a value threshold, individual transactions purchased via a first purchasing mechanism, and individual transactions corresponding to a first category of services or goods; and

storing a second payment scheme for a second portion of the debt owed to the creditor, wherein the second portion of the debt corresponds to at least one of;

individual transactions at or above the value threshold, individual transactions purchased via a second purchasing mechanism, and individual transactions corresponding to a second category of services or goods, wherein the at least one payment scheme includes the first and second payment schemes.

15. The apparatus of claim 12, wherein the processing module generates the payables profile for one of the plurality of creditors by at least one of:

storing a shipping payment scheme for paying shipping costs as part of the associated payment data; and

storing a tax payment scheme for paying taxes associated with goods or services received from the creditor as part of the associated payment data, wherein the at least one payment scheme includes the shipping and tax payment schemes.

16. The apparatus of claim 12, wherein, when the level of service is a second level of service, the processing module generates the payables profile for one of the plurality of creditors by:

generating payment program data that, at least, includes a payment program from a financial entity;

transmitting the payment program data to the client device;

storing at least one altered payment scheme in accordance with a selected payment program when a response from the client device indicates changing the associated payment data, wherein the selected payment program is a payment program selected from the payment program data;

storing the at least one payment scheme when a response from the client device to use the at least one payment scheme; and

storing identification information of the creditor.

17. The apparatus of claim 12, wherein, when the level of service is a third level of service, the processing module generates the payables profile for one of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the at least one payment scheme, generating at least one recommended altered payment scheme;

transmitting the at least one recommended altered payment scheme to the client device;

storing the at least one recommended altered payment scheme when a response from the client device to use the at least one recommended altered payment scheme;

storing the at least one payment scheme when a response from the client device to use the at least one payment scheme; and

storing identification information of the creditor.

18. The apparatus of claim 12, wherein, when the level of service is a fourth level of service, the processing module generates the payables profile for one of the plurality of creditors comprises:

generating payment program data that, at least, includes a plurality of payment programs from at least one financial entity;

comparing the at least one payment scheme with the plurality of payment programs;

when at least one of the plurality of payment programs compares favorably to the at least one payment scheme, generating at least one recommended altered payment scheme;

storing identification information of the creditor; and

storing the at least one recommended altered payment scheme.

19. The apparatus of claim 12, wherein the processing module further functions to:

receive updated associated payment data for the creditor from the client device; and

update the payables process data in accordance with the updated associated payment data.

20. The apparatus of claim 12, wherein the processing module further, when a first update service is enabled, to:

generate update payment program data that, at least, includes an updated or new payment program from a financial entity;

transmit the updated payment program data to the client device; and

overwrite the at least one payment scheme with at least one updated payment scheme in accordance with a selected updated payment program when a response from the client device indicates updating the associated payment data, wherein the selected updated payment program is a payment program selected from the updated payment program data.

21. The apparatus of claim 12, wherein the processing module further functions, when a second update service is enabled, to:

generate updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

compare the at least one payment scheme with the plurality of updated or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the at least one payment scheme, generate at least one recommended updated payment scheme;

transmit the at least one recommended updated payment scheme to the client device; and

overwrite the at least one payment scheme with the at least one recommended updated payment scheme when a response from the client device to use the at least one recommended updated payment scheme.

22. The apparatus of claim 12, wherein the processing module further functions, when a third update service is enabled, to:

generate updated payment program data that, at least, includes a plurality of updated or new payment programs from at least one financial entity;

compare the at least one payment scheme with the plurality of update or new payment programs;

when at least one of the plurality of updated or new payment programs compares favorably to the at least one payment scheme, generate at least one recommended updated payment scheme; and

overwrite the at least one payment scheme with the at least one recommended updated payment scheme.