CLIENT SUPPORTED MULTIPLE PAYMENT METHODS SYSTEM

• US 20090112658A1
• 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,937 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• 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/24 Credit schemes, i.e. "pay after"
• 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 by providing at least one account level preference of a plurality of account level preferences based on a level of subscription. The method continues by receiving a selection of one of the at least one of the account level preference to produce a selected account level preference. The method continues by generating payables process data in accordance with the selected account level preference. The payables process data includes a list of a plurality of creditors and associated payment data. 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 business credit card, a funds transfer, commercial paper, tangible consideration, and a debit account. The method continues by transmitting the payable process data to a payment entity device.

Claims

1. A method comprises:

providing at least one account level preference of a plurality of account level preferences based on a level of subscription;

receiving a selection of one of the at least one of the account level preference to produce a selected account level preference;

generating payables process data in accordance with the selected account level preference, 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 business credit card, a funds transfer, commercial paper, tangible consideration, and a debit account; and

transmitting the payable process data to a payment entity device.

2. The method of claim 1, wherein the generating payables process data comprises:

receiving identification information of the creditor;

receiving a specific payment scheme for the debt owed to the creditor as the associated payment data; and

storing the identification information and the specific payment scheme as part of the payable process data.

3. The method of claim 1, wherein the generating payables process data comprises:

receiving identification information of the creditor;

receiving 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;

receiving 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; and

storing the identification information, the first payment scheme, and the second payment scheme as part of the payable process data.

4. The method of claim 1, wherein the generating payables process data comprises at least one of:

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

receiving a tax payment scheme for paying taxes associated with goods or services received from the creditor as part of the associated payment data.

5. The method of claim 1, wherein the generating the payables process data comprises:

when the selected account level preference corresponds to a first account level preference;

determining an existing payment scheme for the creditor; and

utilizing the existing payment scheme as the associated payment data; and

when the selected account level preference corresponds to a second account level preference;

determining an existing payment scheme for the creditor;

initiating a comparison of payment program data with the existing payment scheme to determine whether one or more payment programs of the payment program data provides a more optimal payment solution than at least a portion of the existing payment scheme; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the existing payment scheme, replacing, in accordance with a replacement protocol, the at least a portion of the existing payment scheme in the payable process data with the one or more payment programs.

6. The method of claim 1, wherein the generating the payables process data comprises:

receiving a request to modify the payables process data, wherein the request includes an indication as to whether the modifying is adding a new creditor and its associated payment data, deleting an existing creditor and its associated payment data, or editing the associated payment data of an existing creditor; and

processing the request in accordance with the indication to produce the payables process data.

7. The method of claim 6, wherein the receiving the request comprises at least one of:

receiving the request via a graphical user interface; and

receiving the request from a payables program processing module, wherein the payables program processing module functions to;

evaluate payment program data with respect to existing payment schemes of the payable process data for a given creditor;

determine whether one or more payment programs of the payment program data provides a more optimal payment solution than at least a portion of the existing payment scheme; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the existing payment scheme, provide, in accordance with a replacement protocol, the one or more payment programs instead of the at least a portion of the existing payment scheme in the payable process data as at least part of the request.

8. A method comprises:

detecting activation of an auto payment processing trigger;

determining whether existing payables process data or altered payables processing data will be used for a present payment period when the auto payment processing trigger is activated;

generating accounts payable data for the present payment period when the existing payables process data is to be used;

generating altered accounts payable data for the present payment period when the altered payment process data is to be used; and

providing the accounts payable data or the altered accounts payable data to a payment entity device.

9. The method of claim 8, wherein the generating the altered accounts payable data comprises:

receiving alternate associated payment data for a creditor; and

replacing associated payment data of the creditor with the alternate associated payment data to produce the altered payment process data.

10. The method of claim 9, wherein the receiving the alternated associated payment data comprises at least one of:

receiving the alternate associated payment data via a graphical user interface; and

receiving the alternate associated payment data from a payables program processing module, wherein the payables program processing module functions to, for the present payment period;

evaluate payment program data with respect to existing payment schemes of the associated payment data of the creditor;

determine whether one or more payment programs of the payment program data provides a more optimal payment solution for the present payment period than at least a portion of the associated payment data; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the associated payment data, provide, in accordance with a replacement protocol, the one or more payment programs and a remaining portion of the associated payment data as the alternate associated payment data.

11. The method of claim 8 further comprises, for a creditor:

generating the accounts payable data to include at least one of;

one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date; and

generating the alternate accounts payable data to include at least one of;

alternate associated payment data, one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date.

12. A method comprises:

generating payables process data that 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 business credit card, a funds transfer, commercial paper, tangible consideration, and a debit account;

transmitting the payable process data to a payment entity device;

detecting activation of an auto payment processing trigger;

generating accounts payable data for a present payment when the activation of the auto payment processing trigger is detected; and

providing the accounts payable data to the payment entity device for payment in accordance with the payables process data.

13. The method of claim 12, wherein the generating payables process data comprises:

providing at least one account level preference of a plurality of account level preferences based on a level of subscription;

receiving a selection of one of the at least one of the account level preference to produce a selected account level preference;

generating the payables process data in accordance with the selected account level preference.

14. The method of claim 12, wherein the generating payables process data comprises:

receiving identification information of the creditor;

receiving 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;

receiving 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; and

storing the identification information, the first payment scheme, and the second payment scheme as part of the payable process data.

15. The method of claim 12, wherein the generating the payables process data comprises:

receiving a request to modify the payables process data, wherein the request includes an indication as to whether the modifying is adding a new creditor and its associated payment data, deleting an existing creditor and its associated payment data, or editing the associated payment data of an existing creditor; and

processing the request in accordance with the indication to produce the payables process data.

16. The method of claim 12, further comprises, for a creditor:

generating the accounts payable data to include at least one of;

one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date; and

generating the alternate accounts payable data to include at least one of;

alternate associated payment data, one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date.

17. An apparatus comprises:

a processing module; and

memory coupled to the processing module, wherein the processing module functions, at least partially in accordance with operating instructions stored in the memory, to;

provide at least one account level preference of a plurality of account level preferences based on a level of subscription;

receive a selection of one of the at least one of the account level preference to produce a selected account level preference;

generate payables process data in accordance with the selected account level preference, 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 business credit card, a funds transfer, commercial paper, tangible consideration, and a debit account; and

transmit the payable process data to a payment entity device.

18. The apparatus of claim 17, wherein the processing module functions to generate payables process data by:

receiving identification information of the creditor;

receiving 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;

receiving 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; and

storing the identification information, the first payment scheme, and the second payment scheme as part of the payable process data.

19. The apparatus of claim 17, wherein the processing module functions to generate the payables process data by:

when the selected account level preference corresponds to a first account level preference;

determining an existing payment scheme for the creditor; and

utilizing the existing payment scheme as the associated payment data; and

when the selected account level preference corresponds to a second account level preference;

determining an existing payment scheme for the creditor;

initiating a comparison of payment program data with the existing payment scheme for to determine whether one or more payment programs of the payment program data provides a more optimal payment solution than at least a portion of the existing payment scheme; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the existing payment scheme, replacing, in accordance with a replacement protocol, the at least a portion of the existing payment scheme in the payable process data with the one or more payment programs.

20. The apparatus of claim 17, wherein the processing module functions to generate the payables process data by:

receiving a request to modify the payables process data, wherein the request includes an indication as to whether the modifying is adding a new creditor and its associated payment data, deleting an existing creditor and its associated payment data, or editing the associated payment data of an existing creditor; and

processing the request in accordance with the indication to produce the payables process data.

21. The apparatus of claim 20, wherein the processing module functions to receive the request by at least one of:

receiving the request via a graphical user interface; and

receiving the request from a payables program processing module, wherein the payables program processing module functions to;

evaluate payment program data with respect to existing payment schemes of the payable process data for a given creditor;

determine whether one or more payment programs of the payment program data provides a more optimal payment solution than at least a portion of the existing payment scheme; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the existing payment scheme, provide, in accordance with a replacement protocol, the one or more payment programs instead of the at least a portion of the existing payment scheme in the payable process data as at least part of the request.

22. An apparatus comprises:

a processing module; and

memory coupled to the processing module, wherein the processing module functions, at least partially in accordance with operating instructions stored in the memory, to;

detect activation of an auto payment processing trigger;

determine whether existing payables process data or altered payables processing data will be used for a present payment period when the auto payment processing trigger is activated;

generate accounts payable data for the present payment period when the existing payables process data is to be used;

generate altered accounts payable data for the present payment period when the altered payment process data is to be used; and

provide the accounts payable data or the altered accounts payable data to a payment entity device.

23. The apparatus of claim 22, wherein the processing module functions to generate the altered accounts payable data by:

receiving alternate associated payment data for a creditor; and

replacing associated payment data of the creditor with the alternate associated payment data to produce the altered payment process data.

24. The apparatus of claim 23, wherein the processing module functions to receive the alternated associated payment data by at least one of:

receiving the alternate associated payment data via a graphical user interface; and

receiving the alternate associated payment data from a payables program processing module, wherein the payables program processing module functions to, for the present payment period;

evaluate payment program data with respect to existing payment schemes of the associated payment data of the creditor;

determine whether one or more payment programs of the payment program data provides a more optimal payment solution for the present payment period than at least a portion of the associated payment data; and

when the one or more payment programs of the payment program data provides a more optimal payment solution than the at least a portion of the associated payment data, provide, in accordance with a replacement protocol, the one or more payment programs and a remaining portion of the associated payment data as the alternate associated payment data.

25. The apparatus of claim 22, wherein the processing module further functions, for a creditor, to:

generate the accounts payable data to include at least one of;

one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date; and

generate the alternate accounts payable data to include at least one of;

alternate associated payment data, one or more invoice numbers, identification of the creditor, identification of one or more goods or services received from the creditor, payment amount for each of the one or more goods or services, and a payment date.