Electronic payment risk processing

• US 20020087468A1
• Filed: 12/28/2000
• Published: 07/04/2002
• Est. Priority Date: 12/28/2000
• Status: Abandoned Application

• Current Assignee: Checkfree Services Corporation (Fiserv Incorporated)
• Original Assignee: Checkfree Services Corporation (Fiserv Incorporated)
• Inventors: Ganesan, Ravi, Renshaw, Timothy Scott, Kight, Peter, Lyda, Paul J., Moenickheim, Peter, Ward, Cheryl
• Application Number:
  US09/749,595
• Publication Number:
  US 20020087468A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/24 Credit schemes, i.e. "pay after"
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A system and method for processing electronic payment requests. A request to make a payment for a network user is received over a network. The request includes information identifying the network user. All user identifiers associated with the network user are determined. Then, information about previous payments made for the network user is processed. This information about previous payments is based upon the determined identifiers. This processing determines if the request will be honored. A notification of the decision to honor or not to honor the request is then transmitted.

Claims

1. A method for ameliorating financial risk in providing electronic payment services, comprising:

receiving, via a network, a request to execute a payment on behalf of a network user associated with two or more user identifiers, the request including a first user identifier;

processing previous requests executed on behalf of the network user, each previous request including one of the two or more user identifiers, to determine if the request will be accepted for execution; and

if the determination is to accept the request for execution, directing a debit from an account associated with the network user.

2. A method for processing electronic payment requests, comprising:

receiving, via a network, a request to execute a payment on behalf of a network user, the request including a user identifier associated with the network user;

identifying all user identifiers associated with the network user;

processing previously executed payments associated with each identified user identifier to determine if the request will be accepted for execution; and

transmitting, via the network, the determination.

3. The method of claim 2, wherein:

the determination is transmitted to the network user; and

the transmission is a real-time transmission.

4. The method of claim 2, further comprising:

determining a total monetary value of previously executed payments executed in one or more time periods;

determining if the total monetary value of previously executed payments executed in the one or more time periods exceeds one or more threshold values; and

if the determination is the total monetary value of previously executed payments executed in the one or more time periods does exceed one or more threshold values, not accepting the request for execution.

5. The method of claim 4, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more threshold values and the one or more time periods is based upon the identity of the sponsor.

6. The method of claim 4, further comprising:

determining if the total monetary value of previously executed payments in the one or more time periods in combination with an amount of the payment exceeds one or more threshold values; and

if so determined, not accepting the request for execution.

7. The method of claim 2, further comprising:

determining a total number of previously executed payments executed in one or more time periods;

determining if the total number of previously executed payments executed in the one or more time periods exceeds one or more values; and

if the determination is the total number of previously executed payments executed in the one or more time periods does exceed one or more values, not accepting the request for execution.

8. The method of claim 7, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more values and the one or more time periods is based upon the identity of the sponsor.

9. The method of claim 2, wherein the payment is one of (1) a payment of a bill, (2) a gift, (3) a payment for the purchase of goods or services made via the network, and (4) a payment for goods or services purchased from an Internet auction.

10. The method of claim 2, if the determination is to accept the request for execution, further comprising:

directing a debit from an account associated with the network user at a first time; and

directing a credit to a payee at a second time;

wherein the second time is subsequent to the first time; and

wherein a time period between the first time and the second time is a determined time period.

11. The method of claim 10, further comprising:

processing previously executed payments associated with each identified user identifier to determine the time period.

12. The method of claim 10, further comprising:

determining the time period based upon at least one of (1) an amount of the payment, (2) the identity of the network user, (3) an association maintained by the network user, and (4) payments previously executed on behalf of the network user.

14. The method of claim 13, wherein the determined time period is determined based upon at least one of (1) the identity of the network user, (2) an amount of the payment, (3) an association maintained by the network user, and (4) payments previously executed on behalf of the network user.

15. The method of claim 13, wherein the request includes a user identifier associated with the network user, further comprising:

identifying all user identifiers associated with the network user;

processing previously executed payments associated with each identified user identifier to determine the period.

16. The method of claim 15, further comprising:

determining a total monetary value of previously executed payments executed in one or more time periods; and

determining if the total monetary value of previously executed payments executed in the one or more time periods exceeds one or more threshold values to determine the period.

17. The method of claim 16, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more threshold values and the one or more time periods is based upon the identity of the sponsor.

18. The method of claim 16, further comprising:

determining if the total monetary value of previously executed payments in the one or more time periods in combination with an amount of the payment exceeds one or more threshold values to determine the period.

19. The method of claim 15, further comprising:

determining a total number of previously executed payments executed in one or more time periods; and

determining if the total number of previously executed payments executed in the one or more time periods exceeds one or more values to determine the period.

20. The method of claim 19, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more values and the one or more time periods is based upon the identity of the sponsor.

13. A method for processing a payment request, comprising:

receiving a request via a network to execute a payment to a payee on behalf of a network user;

determining a time period for crediting the payee subsequent to debiting an account associated with the network user;

directing a debit from the network user account at a first time, the first time beginning the determined time period; and

directing a credit to the payee at a second time, the second time at the end of the determined time period.

21. A system for processing payment requests, comprising:

a communications port configured to receive and to transmit information via a network;

a memory configured to store a plurality of user identifiers associated with a plurality of network users and information associated with previously executed payments on behalf of the plurality of network users, the information associated with each previously executed payment including a user identifier; and

a processor in communication with the communications port and the memory and configured to (1) receive a request to execute a payment on behalf of one of the plurality of network users, the request including a user identifier associated with the network user, (2) identify all user identifiers associated with the network user stored in the memory, (3) identify previously executed payments associated with each identified user identifier stored in the memory, (4) determine if the request will be accepted for execution based upon the identified previously executed payments, and (5) cause a notice of the determination to be transmitted.

22. The system of claim 21, wherein the processor is further configured to cause the notice to be transmitted to the network user in real-time.23. The system of claim 21, wherein the processor is further configured to (1) determine a total monetary value of previously executed payments in one or more time periods, (2) determine if this total exceeds one or more threshold values, and (3) if the determination is this total does exceed one or more threshold values, determine not to accept the request for execution.

24. The system of claim 23, wherein:

the user identifier included in the request is also associated with a sponsor; and

at least one of the one or more threshold values and the one or more time periods is based upon the identity of the sponsor.

25. The system of claim 23, wherein the processor is further configured to (1) determine if the total monetary value of previously executed payments executed in the one or more time periods in combination with an amount of the payment exceeds one or more threshold values, and (2) if so, determine not to accept the request for execution.

26. The system of claim 21, wherein the processor is further configured to (1) determine a total number of previously executed payments executed in one or more time periods, (2) determine if the total number of previously executed payments executed in the one or more time periods, plus the present request, exceeds one or more values, and (3) if the determination is the total number of previously executed payments executed in the one or more time periods, plus the present request, does exceed one or more values, determine not to accept the request for execution.

27. The system of claim 26, wherein:

the user identifier included in the request is also associated with a sponsor; and

at least one of the at least one values and the one or more time periods is based upon the identity of the sponsor.

28. The system of claim 21, wherein the payment is one of (1) a payment of a bill, (2) a gift, (3) a payment for the purchase of goods or services made via the network, and (4) a payment for goods or services purchased from an Internet auction.

29. The system of claim 21, wherein:

if the processor determines to accept the request for execution, the processor is further configured to (1) direct a debit from an account associated with the network user at a first time, and (2) direct a credit to a payee at a second time;

the second time is subsequent to the first time; and

a time period between the first time and the second time is a determined time period.

30. The system of claim 29, wherein the processor is further configured to determine the time period based upon the identified previously executed payments.

31. The system of claim 29, wherein the processor is further configured to determine the time period based upon at least one of (1) an amount of the payment, (2) the identity of the network user, (3) an association maintained by the network user, and (4) payments previously executed on behalf of the network user.

32. A system for processing a payment request, comprising:

a communications port configured to receive and to transmit information via a network;

a memory configured to store information associated with network users and associated with transactions executed on behalf of network users, each transaction associated with a user identifier; and

a processor in communication with the communications port and the memory and configured to (1) receive a request to execute a payment on behalf of a network user, (2) determine, based upon information stored in the memory, a time period between a debit from an account associated with the network user and a credit a payee, (3) direct a debit from the account associated with the network user at a first time, the first time beginning the determined time period, and (4) direct a credit to the payee at a second time, the second time at the end of the determined time period.

33. The system of claim 32, wherein the payee is also a network user.

34. The system of claim 32, wherein the processor is further configured to determine the period based upon at least one of (1) the identity of the network user, (2) an amount of the payment, (3) an association maintained by the network user, and (4) payments previously executed on behalf of the network user.

35. The system of claim 32, wherein:

the request includes a user identifier associated with the network user;

the processor is further configured to (1) identify all user identifiers associated with the network user, (2) identify all transactions associated with the identified user identifiers, and (3) determine the period based upon the identified transactions.

36. The system of claim 35, wherein the processor is further configured to:

determine a total monetary value of the identified transactions executed in one or more time periods; and

determine if the total monetary value of the identified transactions executed in the one or more time periods, plus a monetary value of the request, exceeds one or more threshold values to determine the period.

37. The system of claim 36, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more threshold values and the one or more time period is based upon the identity of the sponsor.

38. The system of claim 35, wherein the processor is further configured to:

determine a total number of identified transactions executed in one or more time periods; and

determine if the total number of identified transactions executed in the one or more time periods, plus the present request, exceeds one or more threshold values to determine the period.

39. The system of claim 38, wherein:

the user identifier included with the request is also associated with a sponsor; and

at least one of the one or more threshold values and the one or more time periods is based upon the identity of the sponsor.

40. A system for ameliorating financial risk in providing electronic payment services, comprising:

a communications port configured to receive and to transmit information via a network;

a memory configured to store information associated with previous payment requests executed on behalf of a network user; and

a processor in communication with the communications port and the memory configured to (1) receive a request to execute a payment on behalf of a network user associated with two or more user identifiers, the request including a first user identifier, (2) processing the information associated with previous payment requests stored in the memory, each previous payment request stored in the memory including one of the two or more user identifiers, to determine if the request will be accepted for execution, and (3) if the determination is to accept the request for execution, to direct a debit from an account associated with the network user.