SYSTEMS AND METHODS FOR PROCESSING PAYMENTS WITH PAYMENT REVIEW

• US 20140195432A1
• Filed: 02/17/2014
• Published: 07/10/2014
• Est. Priority Date: 07/06/2006
• Status: Abandoned Application

• Current Assignee: MoneyGram International Incorporated
• Original Assignee: MoneyGram International Incorporated
• Inventors: Gordon, Emiko, Lee, Dennis, Smith, Gordon L.B. Jr.
• Application Number:
  US14/182,166
• Publication Number:
  US 20140195432A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

Methods and systems of processing a plurality of payments. One method can include receiving the plurality of payments from a plurality of customers, the plurality of payments payable to at least one receiver, determining a first set of payments included in the plurality of payments to automatically accept based on validation parameters, determining a second set of payments included in the plurality of payments to reject based on the validation parameters, determining a third set of payments included in the plurality of payments to conditionally accept based on the validation parameters, and electronically prompting at least one user to accept or reject payments included in the third set of payments.

Claims

1. A payment management system configured to process payments, the payment management system comprising:

a processor configured to generate a user interface on a display, the user interface including

a business standards page configured to set a plurality of validation parameters;

a accept/reject transaction review criteria page configured to allow a user to select a plurality of transaction status search parameters; and

an accept/reject transaction report page configured to display a plurality of conditionally accepted payments and to receive an indication to accept or reject each of the plurality of conditionally accepted payments;

wherein the payment management system directs a payment processor to accept or reject the plurality of conditionally accepted payments based on the indications received.

2. The payment management system of claim 1, wherein the business standards page includes an accept/reject tool standards section including a validation selection mechanism for selecting an automatic action and a predetermined wait period.

3. The payment management system of claim 2, wherein the validation selection mechanism includes a drop-down box for selecting the automatic action.

4. The payment management system of claim 2, wherein the automatic action includes accepting and rejecting payments from a payer.

5. The payment management system of claim 2, wherein the validation selection mechanism includes a drop-down box for selecting the predetermined wait period.

6. The payment management system of claim 2, wherein the validation selection mechanism displays a plurality of users and includes a check box for each of the plurality of users, the check box enabling a user to accept and reject conditionally accepted payment for a payer.

7. The payment management system of claim 1, wherein the accept/reject transaction report page displays the plurality of conditionally accepted payments based on the transaction status search parameters.

8. The payment management system of claim 1, wherein the accept/reject transaction report page includes an accept transaction selection mechanism and a reject transaction selection mechanism for each of the plurality of conditionally accepted payments.

9. The payment management system of claim 8, wherein the accept transaction selection mechanism and the reject transaction selection mechanism are selectable buttons.

10. The payment management system of claim 8, wherein a reference number, a date/time stamp, a sender name, an amount, and an account number are displayed for each of the plurality of conditionally accepted payments.

11. The payment management system of claim 1, wherein the plurality of transaction status search parameters include at least one of a range of accounts, a range of payers, a location, a region, a division, a date range, a time range, a pending indication, a marked for processing indication, a processed indication, an accepted indication, a rejected indication, and a completed indication

12. A system for processing payments, the system comprising:

a payment manager including

a graphical user interface, the graphical user interface

receiving one or more validation parameters from a user, the payment manager sending the validation parameters to a payment processor,

displaying a plurality of conditionally accepted payments received from the payment processor, the plurality of conditionally accepted payments based on the sent validation parameters,

receiving an indication from the user to accept zero or more of the conditionally accepted payments,

receiving an indication from the user to reject zero or more of the conditionally accepted payments; and

a memory for storing the validation parameters,

wherein the payment manager directs the payment processor to accept and reject the conditionally accepted payments based on the indications received from the user.

13. The system of claim 12, wherein the plurality of conditionally accepted payments are filtered based on a user entered criteria, the filtered plurality of conditionally accepted payments being displayed on the graphical user interface.

14. The system of claim 13, wherein the user entered criteria includes at least one of a range of accounts, a range of payers, a location, a region, a division, a date range, a time range, a pending indication, a marked for processing indication, a processed indication, an accepted indication, a rejected indication, and a completed indication.

15. The system of claim 13, wherein the payment manager sends the filtered plurality of conditionally accepted payments to at least one of a printer and a file.

16. The system of claim 13, wherein the display of the filtered plurality of conditionally accepted payments is sorted.

17. The system of claim 16, wherein the display of the filtered plurality of conditionally accepted payments is sorted by at least one of a date range, a time range, and a payment amount.

18. The system of claim 12, wherein the validation parameters include at least one of a valid account number, an invalid account number, a valid payment amount, a number of days before automatic acceptance of a payment, and a number of days before automatic rejection of a payment.

19. The system of claim 12, wherein the graphical user interface displays a list of a plurality of users and a selection tool, the user uses the selection tool to select which of the plurality of users can accept and reject payments for a particular payer.

20. A method for processing payments, the method comprising:

receiving a plurality of validation parameters via a graphical user interface;

sending the validation parameters to a payment processor;

receiving data on a plurality of conditionally accepted payments from the payment processor, the plurality of conditionally accepted payments being conditionally accepted based on the validation parameters;

displaying a filtered set of the plurality of conditionally accepted payments;

receiving via the graphical user interface an indication of which of the filtered set of the plurality of conditionally accepted payments to accept;

receiving via the graphical user interface an indication of which of the filtered set of the plurality of conditionally accepted payments to reject; and

informing the payment processor which of the plurality of conditionally accepted payments to accept and which of the plurality of conditionally accepted payments to reject.

21. The method of claim 20, wherein the data includes a reference number, a time stamp, a payer name, a payment amount, and an account number.

22. The method of claim 20, wherein the plurality of conditionally accepted payments are filtered based on a user entered criteria.

23. The method of claim 22, wherein the user entered criteria includes at least one of a range of accounts, a range of payers, a location, a region, a division, a date range, a time range, a pending indication, a marked for processing indication, a processed indication, an accepted indication, a rejected indication, and a completed indication.

24. The method of claim 22, wherein the payment manager sends data on the filtered set of the plurality of conditionally accepted payments to at least one of a printer and a file.

25. The method of claim 22, wherein the display of the filtered set of the plurality of conditionally accepted payments is sorted.

26. The method of claim 25, wherein the display of the filtered set of the plurality of conditionally accepted payments is sorted by at least one of a date range, a time range, and a payment amount.

27. The method of claim 20, wherein the validation parameters include at least one of a valid account number, an invalid account number, a valid payment amount, a number of days before automatic acceptance of a payment, and a number of days before automatic rejection of a payment.

28. The method of claim 20, wherein the graphical user interface displays a list of a plurality of users and a selection tool, the user selects with the selection tool which of the plurality of users can accept and reject payments for a particular payer.