Web-accessible payment processing system

• US 20090083179A1
• Filed: 04/18/2007
• Published: 03/26/2009
• Est. Priority Date: 04/18/2007
• Status: Abandoned Application

• Current Assignee: Klik Technologies Corp.
• Original Assignee: Klik Technologies Corp.
• Inventors: Lazarus, Gary, Gustave, Jonathan
• Application Number:
  US11/787,935
• Publication Number:
  US 20090083179A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 20/102 Bill distribution or payments

Abstract

A streamlined automated system for processing payments which is web-accessible by clients through an interactive website. The interactive website allows for clients to directly access a database containing payment information and thereby resolve any exception that may have occurred in the course of processing a payment. The system is additionally configured to adaptively learn and apply information. The system furthermore integrated to allow the input of data at various remote locations and features a novel method of allocating data fields for efficient data entry.

Claims

1. A remittance processing system in which payments are made by a payor to be credited to a specified account and remitted to at least one payee, said payment processing system comprising:

a data base comprising payment information;

software capable of detecting exceptions in said payment information based on set parameters;

said database being web-accessible by users.

2. The system of claim 1, wherein said database is accessible through an interactive website.

3. The system of claim 2, wherein said interactive website displays exceptions.

4. The system of claim 2, wherein said interactive website displays digital images of payment documents.

5. The system of claim 2, wherein access to said database is mediated by software applications.

6. The system of claim 5, wherein said software screens information inputted into the website before entering said inputted information into the database.

7. The system of claim 5, wherein said software screens information outputted from the database to said website.

8. The system of claim 2, wherein information displayed on said interactive website can be modified by a user.

9. The system of claim 8, wherein modifying information on said interactive website correspondingly modifies information on said database.

10. The system of claim 2, wherein fields on said interactive map to columns in said database.

11. The system of claim 10, wherein said fields and said columns map in a one-to-one correspondence.

12. The system of claim 5, wherein said fields and said columns map in a more than one-to-one correspondence.

13. The system of claim 2, wherein a said interactive website provides a plurality of options for addressing exceptions.

14. The system of claim 10, wherein said options are selected from the group consisting of “

accept”

“

reject”

“

split” and

“

modify.”

15. The system of claim 13, wherein said interactive website is configured to forward an exception to a second party, said second party being associated with said user.

16. The system of claim 13, wherein said interactive website is configured to allow a user to forward an exception back to the remittance facility.

17. The system of any of claims 15 or 16, wherein a user makes a selection on said interactive website to “

reject to management”

or “

reject to remittance facility.”

18. The system of claim 14, wherein said interactive website is configured to split one payment into at least two payments when a user selects said “

split”

option on said interactive website.

19. The system of claim 1, wherein said payment information is automatically entered into said database by a computer.

20. The system of claim 1, wherein said payment information is manually keyed into said database.

21. The system of claim 1, wherein said payment information comprises digital images of scanned documents.

22. The system of claim 21, wherein said documents comprise bank checks.

23. The system of claim 21, wherein said documents comprise payment vouchers.

24. The system of claim 1, wherein said software further comprises at least one parameter, said software being configured to generate an exception if said at least one parameter is not satisfied.

25. The system of claim 24, wherein said at least one parameter is specified by a user.

26. The system of claim 25, wherein said at least one parameter is selected from a menu on a website.

27. A remittance processing system being capable of adaptively learning information, said system comprising:

a database comprising payment information, said payment information comprising at least a bank DDA number representing a bank account to be debited and customer account information identifying a customer account;

said system storing at least one instance wherein a bank DDA number is used for making a payment for an account identified by particular customer account information;

software configured to automatically associate a bank DDA number with particular customer account information based on a stored instance wherein said DDA number was used to make a payment for an account identified by said particular customer account information.

28. The system of claim 27, wherein based only on said DDA number, said system automatically credits a payment to an account identified by said particular customer account information from a bank account represented by said DDA number.

29. The system of claim 27, wherein said system stores a plurality of instances wherein a bank DDA number was used in making a payment for an account identified by particular customer account information.

30. The system of claim 29, wherein based only on said DDA number, said system automatically credits a payment to an account identified by said particular customer account information from a bank account represented by said DDA number.

31. The system of claim 28, wherein said system does not automatically credit a payment based only on a DDA number when said DDA number is used to pay more than one account.

32. The system of claim 31, wherein said system is configured to never credit a payment based only on a DDA number.

33. A remittance processing system in which payments are made by a payor to be credited to a specified account and remitted to at least one payee, said payment processing system comprising:

a scanner to scan checks;

a data base comprising at least a digital image of a check;

wherein a portion of said digital image, said portion comprising an image of at least one of a currency (CAR) and legal (LAR) field of a check is electronically sent out for remote processing.

34. The system of claim 33, wherein said image is sent via an intranet connection.

35. The system of claim 33, wherein said image is sent via the Internet.

36. The system of claim 33, wherein two separate images are sent, one image comprising an image of the currency (CAR) field and one image comprising the legal (LAR) field of a check.

37. The system of claim 33, wherein said remote processing comprises a means to read images of handwritten information contained in said CAR/LAR fields and enter said information into a computer.

38. The system of claim 33, wherein at least two check data fields are entered into a database substantially simultaneously.

39. The system of claim 37, wherein said information entered into said computer is stored on a digital storage medium.

40. The system of claim 37, wherein said information entered into said computer is returned in the form of an electronic file.

41. The system of claim 40, wherein said electronic file automatically updates a database comprising payment information.

42. A remittance processing system in which payments are made by a payor to be credited to a specified account and remitted to at least one payee, said payment processing system comprising:

a scanner at a first location to scan at least one payment document containing payment information and create a digital image of said payment document;

said scanner configured to electronically send said digital image to a second location in a format that is compatible with or is translatable to be compatible with a reader at said second location;

wherein specialized computers at said second location automatically enter payment information from said digital image into a database.

43. The system of claim 42, wherein said payment document comprises a bank check.

44. The system of claim 42, wherein said payment document comprises a check voucher.

45. The system of claim 42, wherein said payment document comprises a stub containing credit or debit card account information.

46. The system of claim 42, wherein said payment information comprises at least one of a bank routing number and a direct deposit account (DDA) number.

47. The system of claim 42, wherein said payment information comprises at least one of credit and debit card account information.

48. The system of claim 42, wherein said first location comprises a vendor of goods.

49. The system of claim 42, wherein said first location comprises a vendor of services.

50. The system of claim 42, wherein said second location comprises a remittance processing facility.