System and method for processing electronic payments

• US 20060248009A1
• Filed: 05/02/2005
• Published: 11/02/2006
• Est. Priority Date: 05/02/2005
• Status: Abandoned Application

• Current Assignee: Fidelity Information Services, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Fidelity Information Services, LLC (Fidelity National Information Services Incorporated)
• Inventors: Hennel, Ronald V., Rumpler, Andrew M., Brennan, Matthew P., Hicks, Sydney Smith
• Application Number:
  US11/120,267
• Publication Number:
  US 20060248009A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• 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/0425 the cheque being electronic only
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• 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 20/403 Solvency checks

Abstract

A payments gateway operable to receive a payments file from an originating entity. The payments gateway then invokes a policy associated with the originating entity, with the policy comprising references to at least a subset of a plurality of receiving entities. The payments file is parsed into a plurality of payment records, with each record associated with a particular one of the plurality of receiving entities. The payments gateway identifies a first receiving entity associated with one of the payment records and referenced in the policy and automatically provides a dashboard view to the identified receiving entity with the dashboard view presenting information on the one or more associated payment records.

Claims

1. A payments gateway operable to:

receive a payments file from an originating entity;

invoke a policy associated with the originating entity, the policy comprising references to at least a subset of a plurality of receiving entities;

parse the payments file into a plurality of payment records, each record associated with a particular one of the plurality of receiving entities;

identify a first receiving entity associated with one of the payment records and referenced in the policy; and

automatically provide a dashboard view to the identified receiving entity, the dashboard view presenting information on the one or more associated payment records.

2. The payments gateway of claim 1, further operable to automatically provide a second dashboard view to the originating entity, the second dashboard view presenting a plurality of metrics associated with the received payments file.

3. The payments gateway of claim 2, the invoked policy further comprising references to a plurality of thresholds and the payments gateway further operable to:

determine the metrics of the payments file upon receipt; and

compare a first of the determined metrics to an associated first of the referenced thresholds.

4. The payments gateway of claim 3, further operable to modify one of the referenced thresholds based on an associated one of the determined metrics.

5. The payments gateway of claim 3, further operable communicate an alert message to the originating entity when one of the metrics is outside the associated threshold.

6. The payments gateway of claim 3, further operable communicate an alert message to one of the receiving entities when one of the metrics is outside the associated threshold.

7. The payments gateway of claim 6, the alert message comprising one of an email message, a Short Messaging Service (SMS) message, a fax message, an automated phone message, or an EDI formatted message.

8. The payments gateway of claim 3, the metrics comprising:

general item volume metric;

general receipt time of payments file metric;

geographical-based metric;

channel-based metric;

high dollar item metric;

high dollar deposit by receiving entity;

high dollar deposit by channel;

transmission failure metric;

transmission speed metric; and

one of a plurality of service level agreement parameters.

9. The payments gateway of claim 2, the originating entity comprising one of a plurality of related stores.

10. The payments gateway of claim 9, the second dashboard view secured from access by the remaining related stores.

11. The payments gateway of claim 9, the payments gateway comprising a first payments gateway, associated with a corporate headquarters, and communicably coupled with a second payments gateway associated with a financial institution.

12. The payments gateway of claim 1, the payments file in a first of a plurality of formats and the payments gateway further operable to:

identify a first of a plurality of channels associated with the payments file based on the first receiving entity;

generate a second payments file in a second of the plurality of formats including at least a subset of the payments records, the second format determined based on the identified first channel; and

communicate the second payments file to a financial institution for deposit in an account associated with the first receiving entity.

13. The payments gateway of claim 12, further operable to:

invoke a second policy associated with the first receiving entity;

identify the first channel using the invoked second policy; and

execute a least cost routing process for the second payments file based on the invoked policy.

14. The payments gateway of claim 13, the payments file in a first of a plurality of formats and the payments gateway and wherein the payments gateway operable to execute the least cost routing process based on the invoked policy comprises the payments gateway operable to invoke a plurality of business rules associated with the first receiving entity and wherein the payments gateway operable to generate the second payments file in the second of the plurality of formats including at least a subset of the payments records comprises the payments gateway operable to:

generate a third payments file in the second format based on the invoked business rules, the third payments file including a portion of the subset of payment records; and

generate a fourth payments file in a third of the plurality of formats based on the invoked business rules, the fourth payments file including a second portion of the subset of payment records.

15. The payments gateway of claim 12, further

operable to:

invoke a second policy associated with the first receiving entity;

identify an Enterprise Resource Planning (ERP) module associated with the first receiving entity based on the invoked policy;

generate an ERP receivables file based on the second payments file and the identified ERP module, the ERP receivables file compatible with the ERP module; and

communicate the ERP receivables file to the receiving entity.

16. The payments gateway of claim 1, the dashboard view presenting the payments records associated with the first receiving entity and allowing the first receiving entity to drill down on each presented payment record.

17. The payments gateway of claim 16, each presented payments record associated with the following drill down information:

scheduled time of payment;

actual time of payment;

amount of payment;

invoice number; and

items included in invoice.

18. The payments gateway of claim 1, further operable to perform duplicate processing on the received payments file.

19. The payments gateway of claim 1, further operable to:

monitor access of the dashboard view by the first receiving entity;

automatically generate a bill for the monitored access; and

communicate the bill to the first receiving entity via a network connection.

20. The payments gateway of claim 1, the payments file in one of a plurality of formats comprising:

X9.37;

ACH;

X12;

flat file;

XML;

SWIFT;

EDI FACT;

a propriety format;

ACH-CCD; and

ACH-CTX.

21. The payments gateway of claim 1, each payment record comprising an electronic check image generated from a paper check at the originating entity, each electronic check image operable to generate an image replacement document (IRD).

22. A method for centralized processing of electronic payments comprising:

receiving a payments file from an originating entity at a payments gateway;

invoking a policy associated with the originating entity, the policy comprising references to at least a subset of a plurality of receiving entities;

parsing the payments file into a plurality of payment records, each record associated with a particular one of the plurality of receiving entities;

identifying a first receiving entity associated with one of the payment records and referenced in the policy; and

automatically providing a dashboard view to the identified receiving entity, the dashboard view presenting information on the one or more associated payment records.

23. The method of claim 22, further comprising automatically providing a second dashboard view to the originating entity, the second dashboard view presenting a plurality of metrics associated with the received payments file.

24. The method of claim 23, wherein the invoked policy comprises references to a plurality of thresholds and the method further comprising:

determining the metrics of the payments file upon receipt; and

comparing a first of the determined metrics to an associated first of the referenced thresholds.

25. The method of claim 24, further comprising modifying one of the referenced thresholds based on an associated one of the determined metrics.

26. The method of claim 24, further comprising communicating an alert message to the originating entity when one of the metrics is outside the associated threshold.

27. The method of claim 25, further comprising communicating an alert message to one of the receiving entities when one of the metrics is outside the associated threshold.

28. The method of claim 26, the alert message comprising one of an email message, a Short Messaging Service (SMS) message, a fax message, an automated phone message, or an EDI formatted message.

29. The method of claim 24, wherein the metrics comprise:

general item volume metric;

general receipt time of payments file metric;

geographical-based metric;

channel-based metric;

high dollar item metric;

high dollar deposit by receiving entity;

high dollar deposit by channel;

transmission failure metric;

transmission speed metric; and

one of a plurality of service level agreement parameters.

30. The method of claim 23, the originating entity comprising one of a plurality of related stores.

31. The method of claim 30, the second dashboard view secured from access by the remaining related stores.

32. The method of claim 30, the payments gateway comprising a first payments gateway, associated with a corporate headquarters, and communicably coupled with a second payments gateway associated with a financial institution.

33. The method of claim 22, the payments file in a first of a plurality of formats and the method further comprising:

identifying a first of a plurality of channels associated with the payments file based on the first receiving entity;

generating a second payments file in a second of the plurality of formats including at least a subset of the payments records, the second format determined based on the identified first channel; and

communicating the second payments file to a financial institution for deposit in an account associated with the first receiving entity.

34. The method of claim 22, the payments file in a first of a plurality of formats and the method further comprising:

invoking a second policy associated with the first receiving entity;

identifying the first channel using the invoked second policy; and

executing a least cost routing process for the second payments file based on the invoked policy.

35. The method of claim 34, wherein executing the least cost routing process based on the invoked policy comprises invoking a plurality of business rules associated with the first receiving entity and wherein generating the second payments file in the second of the plurality of formats including at least a subset of the payments records comprises:

generating a third payments file in the second format based on the invoked business rules, the third payments file including a portion of the subset of payment records; and

generating a fourth payments file in a third of the plurality of formats based on the invoked business rules, the fourth payments file including a second portion of the subset of payment records.

36. The method of claim 22, further comprising:

invoking a second policy associated with the first receiving entity;

identifying an Enterprise Resource Planning (ERP) module associated with the first receiving entity based on the invoked policy;

generating an ERP receivables file based on the payments file and the identified ERP module, the ERP receivables file compatible with the ERP module; and

communicating the ERP receivables file to the receiving entity.

37. The method of claim 22, the dashboard view presenting the payments records associated with the first receiving entity and allowing the first receiving entity to drill down on each presented payment record.

38. The method of claim 37, wherein each presented payments record associated with the following drill down information comprises:

scheduled time of payment;

actual time of payment;

amount of payment;

invoice number; and

items included in invoice.

39. The method of claim 22, further comprising performing duplicate processing on the received payments file.

40. The method of claim 22, further comprising:

monitoring access of the dashboard view by the first receiving entity;

automatically generating a bill for the monitored access; and

communicating the bill to the first receiving entity via a network connection.

41. The method of claim 22, the payments file in one of a plurality of formats comprising:

X9.37;

ACH;

X12;

flat file;

XML;

SWIFT;

EDIFACT;

a propriety format;

ACH-CCD; and

ACH-CTX.

42. The method of claim 22, each payment record comprising an electronic check image generated from a paper check at the originating entity and the method further comprising generating an image replacement document (IRD) based on one of the electronic check images.

43. The method of claim 22, wherein receiving the payments file from the originating entity at the payments gateway comprises:

receiving a plurality of physical checks from the originating entity;

generating an electronic payment for each of the physical checks; and

loading the electronic payments at the payments gateway.

44. A method for processing electronic payments at a corporate headquarters, comprising:

receiving a payments file from a store associated with the corporate headquarters, the payments file including a plurality of electronic payments to at least one receiving entity;

generating a first dashboard view for the store, the dashboard view presenting a plurality of transmission metrics;

generating a second dashboard view for a first of the one or more receiving entities, the second dashboard view providing a plurality of electronic payment information and operable to allow drill downs on the information;

generating an Enterprise Resource Planning (ERP) receivables file based on the payments file and the first receiving entity;

communicating the ERP receivables file to the first receiving entity; and

communicating the payments file to a financial institution for payment processing.