Browse Prior Art Database

Enterprise Payment Gateway

IP.com Disclosure Number: IPCOM000198378D
Publication Date: 2010-Aug-05

Publishing Venue

The IP.com Prior Art Database

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 4

E N T E R P R I S E P A Y M E N T G A T E W A Y

Author: Corey Farrell

Currently, the mechanism for performing payment processing involves direct integration between billing systems and web properties to external payment clearing houses. This creates a tightly integrated architecture that is individual for each integration. Further, there are several cost implications to a provider for integration based upon the business agreements with external third parties. For each integration, there is a separate solution and in many cases the utilization of different clearing houses. For every change made by the provider, whether that be a business rule change or a system change, modification of the existing payment interfaces that exist for each integration is often required. With the payment processing landscape evolving to support services like PayPal™, Google checkout™, gift cards, and prepay, in addition to the traditional clearinghouse software like FDMS1

The current thinking behind payment processing is direct integration for each system requiring payment processing. Examples include monthly billing systems (i.e. AMDOCS

and Paymentech™, the landscape is changing.

          ), etc. Also, there are relationships with multiple payment clearinghouse vendors due to the existence of multiple billers. See the example in Figure 1.


(i.e., Fandango®3

1 First Data® Merchant Services; http://www.fdms.com

2 http://www.amdocs.com

3 http://www.fandango.com

P a g e | 1 1701 John F. Kennedy Blvd., Philadelphia, PA 19103

2), web properties

[This page contains 14 pictures or other non-text objects]

Page 2 of 4

FIGURE 1: CURRENT CARD PROCESSING STATE

The Payment Gateway, which may be a software application, will enable payment processing across multiple application types, for multiple payment processing types, that will also allow for business rules to be implemented quickly and independently. The payment gateway will also allow for integration into eWallet® software that may be used in the future. The Payment Gateway will have
a Web Service entry point (Payment Service) that can be incorporated into the Enterprise Service Platform or any other service oriented architecture (SOA) implementation. The Gateway will be based upon a configurable rules engine to determine the proper routing for the payments sent to it. It will allow one time payments (i.e., micropayments) to be sent as well as batch payments (i.e., monthly invoicing) that need to be cleared all at once. The Payment Gateway can also allow for real time credit card authorization and also interface to other back office components to allow for prepay and real-time top-u...