|Publication number||US7844546 B2|
|Application number||US 10/470,094|
|Publication date||Nov 30, 2010|
|Filing date||Jan 25, 2002|
|Priority date||Jan 26, 2001|
|Also published as||CA2332656A1, US9159058, US20040148252, US20110125644, US20150278816, WO2002059847A1, WO2002059847B1|
|Publication number||10470094, 470094, PCT/2002/107, PCT/CA/2/000107, PCT/CA/2/00107, PCT/CA/2002/000107, PCT/CA/2002/00107, PCT/CA2/000107, PCT/CA2/00107, PCT/CA2000107, PCT/CA200107, PCT/CA2002/000107, PCT/CA2002/00107, PCT/CA2002000107, PCT/CA200200107, US 7844546 B2, US 7844546B2, US-B2-7844546, US7844546 B2, US7844546B2|
|Inventors||Jack Fleishman, Zack Fuerstenberg|
|Original Assignee||Acxsys Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (30), Non-Patent Citations (2), Referenced by (28), Classifications (23), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to a system and method for online monetary transfers. In particular, the invention relates to an online payment and identity management system and method for delivering payments from a financial institution over a global computer network.
In the recent past a number of non-financial institution technology firms have bypassed banks by launching independent, Internet-based person-to-person (P2P) payment mechanisms. Most such services require consumers to register and debit a credit card or bank account before sending a payment. Recipients of payments receive email notifications with a specially coded link to register and authenticate before receiving several payment options, such as depositing into a bank or credit card account.
Due to consumer demand and the “viral” nature of these mechanisms (by compelling recipients to register in order to collect payments), uptake has been significant. Consumers want a convenient Internet mechanism to pay for online purchases and to replace “one-off” checks and cash payments, both domestically and internationally. For example, consider the millions of consumers who regularly wire money to family members that live abroad. For traditional financial institutions, the advent of P2P payments represents both a threat and an opportunity. Banks risk losing customer relationships to third-parties that will quickly try to expand their offerings into other traditional banking functions, competing with online checking accounts, business accounts and merchant payment services.
With non-bank start-ups acquiring P2P market share, banks risk never recouping their massive investments in online infrastructure. Once a non-bank has entered the P2P payment transfer market, there is an opportunity to go beyond free P2P payments and offer consumers a fill range of financial services, such as interest bearing sweep accounts, low-fee mutual funds and business accounts equipped to accept merchant payment.
Unlike other pure-play Internet banks, which have spent millions of dollars on advertising to promote their brands, non-bank P2P payment transfer firms have employed P2P payments to drive the initial adoption of their service and, in the process, have significantly reduced the average customer acquisition cost. Once a non-bank P2P provider makes inroads into a bank's customer relationships, it becomes easier to gain further ground. As a result, financial institutions face the danger of disintermediation by aggressive non-bank up-starts. Demand for such services has been so high that some banks are offering P2P payments to position themselves against third-parties and to acquire online customers. They include portals designed to aggressively capture new clients.
Competition with on-line banking services is arising from other payment providers in other forms as well, such as auction payments, online gift certificates, event, micropayments and stored-value, payment processing, global payments and specialty consumer payments. Most of these P2P payment services are positioned to operate outside of the traditional financial system. As such, consumers are forced to use third-party P2P services requiring personal financial information. This raises a number of privacy and security concerns. Moreover, poor performance by a non-bank third party (which is typically not regulated to the extent that banks and other financial institutions are) can undermine consumers' perception of the reliability of on-line financial service transactions generally.
Furthermore, consumers are suffering from password fatigue, and many are looking to simplify the manner in which day to day transactions and activities are conducted. Consumers look to their banks, which have already established the requisite credibility in financial dealings, to offer additional services from their core banking relationship.
The present invention provides a person-to-person (P2P) payment platform and identity management system which facilitates online banking by allowing bank customers to send and receive money in real-time, with no special registration requirement outside of the customers' existing banking relationship, and under the security, brand and control of their own respective banks.
The invention provides an invisible application service provider in the form of a central clearing facility (CCF) which coordinates and manages payments for customers, nationally and internationally, through partner financial institutions. According to the invention, customers send payments from within their online banking accounts, under their bank's existing authentication and security. Thus, customers can transfer money directly from an existing online banking offering without setting up separate accounts profiles and passwords. Customers trust banks to move money more securely than non-bank third-parties, and as such will more readily respond to a payment solution offered under their bank's security provisions.
The CCF is invisible, and effectively operates under the bank's brand so the bank retains the entire customer goodwill and developed brand recognition. In addition, each payment, in particular those delivered by e-mail, prompts recipients who don't bank online to sign up for their bank's Internet-based services to deposit payments directly into their accounts, thus increasing the bank's goodwill and facilitating the cross-selling of financial services. The e-mail payment option is a high-demand functionality that provides recognizable customer value and replaces customer inconvenience with real-time transactions and convenience to create more positive customer experiences. In addition to being able to initiate and receive payments using online banking services accessible via the web, customers can also utilize automated teller machines (ATMs), wireless networks, telephone, and any other access means provided by the financial institution to its customers.
In the preferred embodiment, to make a P2P payment the customer:
The recipient may:
The invention thus renders P2P payments under the control of the bank and eliminates the need for the bank's customers to use a third-party service. The bank controls all front-end consumer touchpoints including end-user communications. The bank also has the ability to control how P2P payment capability drives new revenue sources, cuts costs and increases market share, to create new revenue streams, reduce acquisition costs of new customers, increase marketing and cross-sell opportunities and reduce dependence on less efficient delivery channels.
The invention supports different frequencies of payment and multiple currencies, and can be deployed on all bank delivery channels, including wireless services. All of these services can generate new revenue opportunities for online business, complemented with tools that enable the bank to track and control usage.
The CCF's infrastructure is secure and scalable, able to employ the latest encryption technologies and security measures to deliver sound and secure transactions. The invention allows the bank to determine and configure a wide array of security parameters, such as maximum transaction limits, to suit each particular institution's risk tolerances. If payments are undeliverable or unretrieved, the sender can have the funds re-credited to their bank account or re-send the payment. A simple, yet robust data interface enables the bank's Internet service to connect quickly and securely to the CCF central facility with minimal diversion of its technical resources.
The invention thus builds on the bank's relationship with its client, by adding new functionality to block out third-party online financial service providers and strengthen the existing relationship. Moreover, the invention forecloses the need for account, ID, password and other inconvenient administrative requirements that third-party financial services providers must ask of consumers. The bank has the opportunity to leverage existing security and Internet payment infrastructures, replace consumer inconvenience with convenience and provide a facility for real-time email payments between customers of the same or different financial institutions.
The CCF can coordinate payment transactions between customers banking at both partner and non-partner financial institutions. It handles and stores all of the payment relationships among customers and manages the authentication and approval of fund disbursements to payment recipients.
In drawings which illustrate by way of example only a preferred embodiment of the invention,
The system and method of the invention enables customers of a financial institution having access to banking services over a global computer network such as the Internet to initiate electronic payments conveniently and securely from their financial institution's self-service delivery channels (Online banking service, ATM, Wireless, Telephone Banking) or the financial institution's branch. The invention provides financial institutions with an easy-to-integrate mechanism to facilitate and manage person-to-person (P2P) payments, leveraging existing find transfer mechanisms that reside in the middleware of a financial institution's banking service—the component that allows customers to move money between their own accounts—thereby avoiding significant back-end development. The invention extends an institution's existing infrastructure to facilitate funds transfers in and out of consolidation trust accounts established at partner financial institutions in each supported currency.
To process P2P payments, the invention helps partner institutions feed transaction interfaces with the appropriate account numbers, parameters and authorizations. “Netting” processes balance the positions of consolidation trust accounts across all partner financial institutions. As a result, a private, real-time clearing network is created among partner institutions to settle electronic payments initiated and caught by their customers. This allows financial institutions to maintain control over their user interface by communicating with a central clearing facility (CCF) 100, as shown in
The CCF is based on an application service provider model that uses industry-standard interfaces to integrate with partner financial institutions' existing systems. The invention acts as a common platform among banks, interacting with each to support the efficient exchange of P2P payments. The net result is one of ease and efficiency: each financial institution establishes a one-to-one relationship with the CCF, eliminating the prospect of integrating disparate systems.
The architecture of the invention, illustrated in
To enable the flow of funds between parties, according to the invention, consolidation trust accounts 401, 402 are established by each partner financial institution 101, 102, as shown in
A front-end Web service 103 allows a payee 415 banking at a non-affiliated institution to specify an offline mechanism for payment retrieval. The payee can select the transfer of funds to their accounts 503 at CPA and NACHA member institutions (through an EFT 501 and ACH 502 processor, respectively) or crediting to most common credit cards through a remittance processor or payment gateway, as shown in
All communication with “offline” consumers 415 include prompts to drive adoption of a partner institution's online banking service. Through a variety of precautionary measures, described below, the invention ensures the security and validity of all payment requests and disbursements and provides detailed reporting and transaction tracing to its partner banks.
To move money between customers, the invention leverages the existing internal funds transfer module utilized by institutions to facilitate customer transfers. With a few modifications, this piece of middleware (usually located on an application server) is enabled to execute transfers between a customer's account and a consolidation trust account for disbursements. The invention operates in reverse at the recipient's end. If a payee catches a payment at a partner institution, funds are immediately transferred from a consolidation trust account into the payee's own account.
To minimize liability, funds awaiting delivery are stored in accounts at partner institutions in each supported currency. The CCF 100 controls the acceptance and disbursement of funds in these accounts, but does not take direct ownership of the money. Instead, the trust accounts are actually internal or suspense accounts maintained by the partner institutions 101 102 103, who earn the float on the funds awaiting disbursement. The CCF 100 provides a detailed accounting of all the money flowing in and out of these accounts. The CCF 100 acts as a control point, approving financial transactions undertaken by partner institutions to move funds between customer and trust accounts in real-time.
The CCF network, acts as a netting center. Instead of settling each individual transaction, the CCF 100 becomes a virtual clearinghouse, adding and subtracting inter-partner payables and receivables and then providing the partner institutions with settlement instructions to balance the trust accounts 601, 602, 603, as shown in
This netting activity is captured by a robust, double-entry accounting system. A continuous transaction journal at the CCF 100 mirrors each of the trust accounts maintained at partner institutions to facilitate auditing and reporting. The system is designed for resilience and will catch accounting imbalances caused by the failure of one or more mid-operation system processes. The CCF 100 utilizes these accounting and reporting mechanisms to facilitate the following activities:
Where the payer 410 and payee 415 are located in different jurisdictions, requiring a currency exchange, the settlement procedure incorporates a foreign exchange facility which maintains trust accounts in each jurisdiction in the local currency.
As shown in
The identity management aspect of the invention provides the following advantages:
Through the identity management function, other fraud protection and security measures are employed by the payment system in addition to the authentication of payment relationships.
A number of measures ensure the security of customer data. The CCF 100 does not store a partner institution's customer account numbers. Data related to customers banking at unaffiliated institutions are stored in a secure database, which is located behind a firewall and encryption processes. Administrative user IDs and passwords are stored behind a firewall in an encrypted format. Administrative users can define multiple security groups and access restrictions in accordance to job function. Challenge-response questions provide an extra mechanism for authenticating the payee in addition to existing logon processes at the payee's own Web banking service. The network connecting partner institutions, administrative users and unaffiliated consumers is divided into several isolation and security zones with restricted access among zones. Industry-standard measures are used throughout the network to ensure security. Intrusion detection devices, traffic encryption, packet inspection and application proxies minimize risk to the network. All communications between the CCF 100 and its partner institutions take place over a dedicated line or VPN and are encrypted.
A number of exception processes and error handling mechanisms further ensure the CCF's integrity:
With reference to
To initiate a P2P payment, the customer logs onto the partner institution's online banking service 901 via the web, telephone, wireless network, ATM (as shown in
The recipient's personalized notification indicates the amount being paid, from whom, the name of the originating institution, as well as options for collection. In one embodiment, the notification takes the form of a personalized e-mail 1001 to the recipient, as shown in
If the recipient already banks online with a partner institution and has previously received an electronic payment via this system, the recipient may select from a list of payment options to log onto their online bank account straight from a link provided in the e-mail notification of payment at 1102 in
If the recipient banks online with a partner institution, but is receiving a P2P payment for the very first time, a link in the e-mail notification sends the customer to a directory of CCF partner institutions. Recipients can use their online banking service to instantly credit any of their accounts. The registration process is fully automated.
Recipients, who are not currently banking online, are prompted to either “Web enable” their existing accounts at a CCF partner institution (such as the sender's bank) or apply for an account with online access at another partner, as shown in 1201 in
The recipient then selects the account into which to deposit the funds 726. The institution validates the recipient's identity, and communicates the payment details to the CCF 100, which verifies the payment and issues permission to disburse the money. The financial institution then debits a suspense account, and credits the recipient's account for the payment. If the recipient chooses to receive the funds directly, a cash account is credited instead and the finds are disbursed. Once the funds credit or disbursement is completed, the CCF 100 is informed of the successful completion. The finds may be advanced immediately by the recipient's institution, because the finds have been guaranteed by the originating institution's verification of the identity of the sender.
The complete payment transaction is decentralized; the first component, the initiation of payment, is controlled by the sender's financial institution, and the second component of the transaction, the receipt of the payment, is controlled by the recipient's institution. It can also be seen that due to the authentication of each party to the transaction independently, by each party's own financial institution, the payer's identity does not need to be known by the payee in order to effect payment. The payer may use an alias or e-mail address only, if desired, in communication with the payee.
The funds may alternatively be deposited to a credit card or other bank account. To provide maximum payment reach, the CCF 100 processes payments to non-partner accounts on a fee-for-service basis. Recipients may opt to deposit the payment into a credit card or other bank account not sponsored by a partner institution. Recipients are directed to the CCF Web site 300, where they can register for the service. When registered, recipients specify a credit card or bank account into which to deposit the funds. Such requests are batched and sent each day to payment processing services to be credited via ACSS, ACH and RPS services.
Payment recipients who require a check or are uncomfortable making transactions online, can request the CCF 100 to issue a paper check for mail delivery. At every turn, payment recipients are prompted to use a partner institution to receive their funds. If they choose to receive a payment using a non-partner mechanism, the CCF 100 will facilitate the transaction through its Web site.
In a further embodiment, payments may be made to a recipient who does not have a bank account via an ATM and is not registered with the CCF 100. The ATM, rather than requiring a bank card to initiate any transaction, provides direct access to the menu option to receive a P2P payment. To verify the identity of the recipient, since there is no bank card authentication, preferably the recipient must at least respond to the challenge-response question 724 and/or provide the payment reference number. The ATM will communicate these payment details to the CCF 100, which will verify the payment and issue permission to disburse the money.
The CCF's notification server 550, shown in
Payments between businesses and businesses, or between businesses and customers, follow the same format as the payments described above. However, if a large number of payments are transacted, it becomes impracticable for a business to log on and collect each payment as they arrive. Instead, business customers of participating institutions may enroll in a commercial registry which provides a funds consolidation function.
Business customers who choose to participate in the commercial registry are first qualified for participation and enrolled by their institution. The institution in turn provides this certified business customer information to a CCF commercial registry, which is used to validate and certify the identity and contact information of the business company as a legitimate operating concern with a bona fide banking relationship when payment transactions are initiated. Preferably, this information will include the official name, address, and contact information of the business, trade name, and a verified e-mail address.
A subset of this financial institution-certified information is available to any individual or business that receives a payment request or wishes to originate a merchant payment to this business customer, which provides assurance that the funds are being directed to the appropriate recipient.
A business customer may generate a payment request for one of its own customers by delivering an invoice and directing the customer to access his or her own financial institution services to effect payment to the business as shown in
In another embodiment, shown in
When the payment is made, the business customer 2050 can choose to receive notification of each payment, and choose a deposit account and collect the funds. Alternatively, because it is impractical for the business customer to respond in this manner to a large number of payments, the payment system can be configured to consolidate funds by accumulating cleared payments, and then sweeping the accumulated funds into a default commercial account at the end of the period. The funds may be swept into the commercial account on a periodic basis, such as a daily basis, or once the accumulated funds reach a certain threshold value or the number of payments reaches a threshold number.
Business-to-business payments, for example, payment by a business customer to a supplier, may also be effected using this system. If the recipient business is also enrolled in the commercial registry, the CCF 100 will handle the payment using the funds consolidation method. To enable transactions between two or more payment systems, for example two domestic payment systems in a cross-border transaction, the financial institutions in each country are affiliated with a regional CCF 100 in that country. Customers in each country use their partner institution's authentication process to log into their selected delivery channel (Internet, telephone, ATM, wireless, etc.). Each regional CCF is responsible for storing, sending and receiving all payments which originate and terminate at that site. Only a limited amount of data is replicated between the regional sites when it is required to perform a function. Preferably, any replication is carried out based on an asynchronous remote XML request, which carries the data to be replicated. There is therefore no requirement for real time data synchronization between regional CCF sites.
For an international payment, the CCF switch 2130 at the point of origin of the payment queries the global directory to determine which institution 2141, 2142, 2143 and CCF regional switch 2140 has been designated by the recipient. If a currency exchange is required, the CCF switch at the point of origin also communicates with an FX facility to determine the exchange rate and book the currency exchange. The payment details are replicated by the regional CCF 2130 to the regional CCF 2140 of the recipient using an asynchronous messaging mechanism.
At the point of destination, the regional CCF 2140 delivers a payment notification to the intended recipient. The notification includes an encrypted payment reference number, which contains a payment identification code to identify the payment's point of origin. The notification directs the recipient to an affiliate institution to claim the payment. The recipient logs onto the selected banking service and receives the funds. Funds transfer occurs by means of transfers between suspense accounts and customer accounts, as described above.
Settlement between financial institutions takes place on a periodic basis, for example at the end of each business day. Based on agreed cut-off times, the CCF 2101 provides each member institution 2131, 2132, 2133, 2141, 2142, 2143 with reconciliation and settlement information. This data is used to reconcile transactions between the CCF 2101 and each institution, as well as to determine the institution's monetary obligations to other members in the network to effect settlement.
Where the institutions are located in different jurisdictions, settlement takes place between the originating and destination institutions using the exchange settlement facility's accounts in the jurisdiction of each institution 2115, 2120, based on settlement advice provided by the A9 CCF 2101. The international CCF site 2101 is networked to a number of regional CCF sites. The participating financial institutions (2131, 2132, 2133, 2141, 2142, 2143) in each region are connected to its corresponding regional switch 2130, 2140. Each of these institutions maintains a suspense account. The FX facility has an international site networked with local sites, which are in communication with each of the institutions in the same region. Each local FX site maintains a local currency settlement trust account 2115 2120 on behalf of the international CCF, through which all foreign exchange settlement will take place.
The networked CCFs provide settlement advice to the financial institutions so that the institutions may make aggregate transfers. These transfers are made to the local currency settlement trust accounts in the local currency, and not to the other institutions. Each transfer may be carried out by means of wire payment to provide finality of transfer. A10
Access to functions beneath the user interface layer is provided utilizing a request/response XML-based message set. All communications are encrypted and signed.
According to the invention, the use of specific delivery channels is left to the discretion of the partner institution. While the primary channel is online banking, the service can be extended to telephone banking and host-based ATMs.
Currently, consumers access Web banking services almost exclusively on a browser residing on a personal computer. As Internet-enabled appliances gain mass acceptance and continue to improve in terms of cost, connectivity, display, memory and processing capabilities, financial institutions will offer banking services through these devices. A single interface is required between the institution and the CCF 100 to support multiple Web-enabled devices. Java-based adapters allow institutions to communicate internally with other application servers that support specific devices.
Once financial institutions have implemented P2P payment capabilities on their Web banking service, they can utilize the message-based interface of the invention to support a synchronized, multi-channel delivery strategy to offer users of non-PC devices access to the same list of personal payees from their Web channel. Due to current data-entry interface limitations in mobile devices (such as WAP-enabled cell phones, ATMs and telephone banking VRUs), it may be more practical to display a customer's pre-existing list of personal payees through these channels. The identity management system of the invention has the capability to store lists of customers' established payment linkages from prior payment requests.
For example, a consumer wants to re-credit an acquaintance for picking up the dinner tab at a restaurant. This payee could log onto their institution's wireless banking service, select the payment recipient from his or her list of past personal payees and enter a monetary amount and a specific account from which to draw the funds. Upon receipt of the payment request, the CCF 100 immediately launches a payment notification and the recipient can authenticate to deposit the funds the next time he or she accesses email. Mobile P2P payments will help institutions extend their wireless banking platforms, increase adoption and leverage their investments in that channel.
Most banks currently offer some form of telephone banking service through an automated voice response unit (VRU). Typically, customers that authenticate with a PIN number can select and pay merchants from a previously determined personal list. A list of pre-existing personal payees stored by the CCF is akin to the merchant list concept in the previous example and can be presented on the VRU platform through the CCF's XML messaging interface.
Similarly to Web and telephone banking delivery, the institution can display a customer's existing list of personal payees on ATMs for convenient re-use by leveraging the messaging interface and identity management system of the invention.
A Web-based publishing tool is supplied with the administration suite enabling marketing managers at institutions to control the email banners that appear on these notifications. The CCF can send notifications to employees within partner institutions. Notification functionality is determined by the institution through the CCF's Web-based administration and reporting tools.
The invention provides a secure Web-based interface for staff at partner institutions to manage customer service, business planning, marketing and key system and security parameters. Different job categories allow bank staff varying levels of access to information and functions of the invention.
The financial institution's system security administrator possesses root-level access that grants privileges to other staff. This administrator can define and update certain system-wide security parameters that govern transactions originating from the institution's Web banking service. These parameters include maximum transaction limits, daily transaction limits per consumer and the maximum number of days before an unretrieved payment is sent back to the payer for re-crediting.
An institution's Web service channel manager can publish and update marketing messages that appear on CCF-triggered email payment notifications. As well, the channel manager can view all multilingual email templates delivered to customers to facilitate payments and direct customers to URLs that open online banking services or logon to existing accounts. This person can also view all system-generated business metric reports that yield rich statistics, such as payment volumes, customer activation levels, methods consumers use to catch payments, average payment amounts and the average time between payment initiation and final settlement.
Customer service representatives (CSRs) can make inquiries using transaction confirmation codes that facilitate payment tracing. The invention provides a complete audit trail for any activity related to a particular customer or payment transaction within a certain time period. CSRs can provide support by viewing payment-processing information. Detailed lists of system-generated messages (and explanations) as well as daily schedules for processing are some of the items that CSRs can access in responding to customer inquiries. The system also features CCF bulletin boards to publish messages that could impact upon customers' immediate use of the service.
The architecture of the invention, illustrated in
The invention uses XML based request/response messaging to exchange information with financial institutions. Each XML message consists of a standard header and variable body sections. The system is designed to support versioning and to be backwards compatible as new features are added or new means of access to online banking are provided to customers. For example, where an institution requests a payment transaction on behalf of its client the financial institution's own Internet banking application presents the appropriate form to the customer, gathers and validates the data entered by the customer and formats the XML request such as:
<?xml version = “1.0” encoding=“utf-8”?> <!DOCTYPE REQPMTBGRQ SYSTEM “file://reqpmtbgrq.dtd”> <CCFREQUEST> <MESSAGEHDR> <MESSAGETYPE>8</MESSAGEGETTYPE> <MESSAGETYPEVER>1.1</MESSAGETYPEVER> <FIID>10</FIID> <TRANTOKEN>X35JCBE</TRANTOKEN> </MESSAGEHDR> <MESSAGEBODY> <FIUSERID>56450983045034</FIUSERID> <CUSTOMERID>B7856434U4</CUSTOMERID> <CURRENCY>CAD</CURRENCY> <PMTAMOUNT>65.00</PMTAMOUNT> <EXPIRYDATE>2000-09-16-23:59:00.000000 </EXPIRYDATE> <MEMO>Here is the money I owe you for dinner. Thanks </MEMO> </MESSAGEBODY> </CCFREQUEST>
The invention executes the appropriate transaction and return a response to the Financial Institution using a similar format.
The preferred production system runs on a hardware platform under the Unix Operating System and uses commercially available and reliable Application and Database Management Software 1625, 1620. The system is housed in data center facility. The preferred embodiment of the invention employs Java 2 Enterprise Edition technology coupled with an enterprise relational database system using a clustered, fault-tolerant configuration which is both scalable and extensible, providing the ability to easily manage and update with additional features and services as required.
Applying multi-tier distributed design patterns, the invention is composed of four logical service items (presentation 1701, messaging 1702, business 1703 and data 1704), shown in
The following technologies may be employed in the implementation of the system and method of the invention:
Java 2 Standard Edition
Java™ 2Standard Edition (J2SE™) is a Web platform that enables rapid development and deployment of software applications across multiple operating systems and platforms with fewer defects than similar technologies. With significant performance gains and improved Web deployment mechanisms for enterprise, client-side Java applets and applications, J2SE Version 1.3 includes a new client Java virtual machine (JVM™), tuned libraries throughout the platform and enhancements to the Java Plug-in software for improved Web browser delivery.
Developed in collaboration with industry leaders, JavaBeans are a portable, platform-independent component model written in Java JavaBeans enable developers to write reusable components once and run them anywhere independent of platform.
Java 2 Enterprise Edition
The Java™ 2 Platform, Enterprise Edition (J2EE), defines the standard for developing multi-tier enterprise applications. J2EE simplifies enterprise applications by basing them on standardized, modular components, providing a complete set of services to those components and handling many application behavior details without complex programming. J2EE takes advantage of many Java 2 Platform, Standard Edition, such as “Write Once, Run Anywhere™” portability, JDBC™ API for database access, CORBA technology for interaction with existing enterprise resources and a security model that protects data even in Internet applications. Building on this base, Java 2, Enterprise Edition, adds full support for Enterprise JavaBeans™ components, Java Servlets API, JavaServer Pages™ and XML technology.
Java Server Pages
The JavaServer Pages™ technology provides a quick and simple way to create dynamic Web content while enabling rapid development of Web-based applications that are server- and platform-independent. The Java™ Servlet API provides Web application developers with a simple and consistent mechanism for extending Web server functionality.
Enterprise Java Beans
The Enterprise JavaBeans specification defines an API that helps developers create, deploy and manage cross-platform, component-based enterprise applications that work with systems currently in use.
Java Naming and Directory Interface
This provides uniform, industry-standard and seamless connectivity between the Java platform and one's business information assets, allowing developers to deliver Java applications with unified access to multiple naming and directory services across the enterprise.
Java Database Connectivity
This provides programmers with a uniform interface to a wide range of relational databases, as well as a common base upon which higher-level tools and interfaces can be built.
Java Messaging Services
This specification provides developers with a standard Java API for enterprise messaging services, such as reliable queuing, publishing and subscription communication and various aspects of push/pull technologies.
Remote Method Invocation Over IIOP
RMI-IIOP provides developers an implementation of the Java RMI API over the Object Management Group's industry-standard Internet Inter-Orb Protocol (IIOP). It allows developers to write remote interfaces between clients and servers and implement them using Java technology and the Java RMI APIs.
XML (eXtensible Markup Language) is a simplified subset of the Standard Generalized Markup Language (SGML, ISO 8879) that provides a file format for representing data, a schema for describing data structure and a mechanism for extending and annotating HTML with semantic information.
Secure Socket Layer API
Secure Sockets Layer (SSL) is the Internet security protocol for point-to-point connections. It provides protection against eavesdropping, tampering and forgery. Clients and servers establish a secure link, or “pipe,” across the Internet to protect information that is sent and received to ensure confidential, authentic and original information exchange.
Various embodiments of the present invention having been thus described in detail by way of example, it will be apparent to those skilled in the art that variations and modifications may be made without departing from the invention. The invention includes all such variations and modifications as fall within the scope of the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4823264||May 27, 1986||Apr 18, 1989||Deming Gilbert R||Electronic funds transfer system|
|US4960981||Jan 17, 1989||Oct 2, 1990||Moneyfax, Inc.||Method of and system for electronic funds transfer via facsimile machines|
|US5326960||Nov 25, 1992||Jul 5, 1994||Tannenbaum David H||Currency transfer system and method|
|US5350906||Nov 25, 1992||Sep 27, 1994||Brody Bill E||Currency transfer system and method using fixed limit cards|
|US5557518||Apr 28, 1994||Sep 17, 1996||Citibank, N.A.||Trusted agents for open electronic commerce|
|US5590196 *||Oct 6, 1994||Dec 31, 1996||Connotech Experts Conseils Inc.||Secure payment method using facsimile|
|US5659165||Jul 24, 1995||Aug 19, 1997||Citibank. N.A.||Customer-directed, automated process for transferring funds between accounts via a communications network|
|US5677955||Apr 7, 1995||Oct 14, 1997||Financial Services Technology Consortium||Electronic funds transfer instruments|
|US5699528 *||Oct 31, 1995||Dec 16, 1997||Mastercard International, Inc.||System and method for bill delivery and payment over a communications network|
|US5757917||Nov 1, 1995||May 26, 1998||First Virtual Holdings Incorporated||Computerized payment system for purchasing goods and services on the internet|
|US5825003||Feb 4, 1997||Oct 20, 1998||Citicorp Development Center||Customer-directed, automated process for transferring funds between accounts using a holding account and local processing|
|US5884290||Oct 22, 1996||Mar 16, 1999||Unisys Corporation||Method of transferring funds employing a three-node real-time electronic interlock|
|US5897621||Jun 14, 1996||Apr 27, 1999||Cybercash, Inc.||System and method for multi-currency transactions|
|US5937396||Dec 4, 1996||Aug 10, 1999||Konya; Arpad||System for ATM/ATM transfers|
|US5949044||Jun 13, 1997||Sep 7, 1999||Walker Asset Management Limited Partnership||Method and apparatus for funds and credit line transfers|
|US5963647 *||Jun 17, 1997||Oct 5, 1999||Citicorp Development Center, Inc.||Method and system for transferring funds from an account to an individual|
|US5974146||Jul 30, 1997||Oct 26, 1999||Huntington Bancshares Incorporated||Real time bank-centric universal payment system|
|US6039250||Jul 3, 1996||Mar 21, 2000||Hitachi, Ltd.||Electronic money sending system|
|US7206768 *||Aug 14, 2000||Apr 17, 2007||Jpmorgan Chase Bank, N.A.||Electronic multiparty accounts receivable and accounts payable system|
|US7366698 *||Dec 13, 2006||Apr 29, 2008||Jpmorgan Chase Bank, N.A.||Trade receivable processing method and apparatus|
|US7415442 *||Dec 27, 2001||Aug 19, 2008||Integrated Technological Systems, Inc.||Integrated technology money transfer system|
|US7454376 *||Jul 20, 2001||Nov 18, 2008||Argenbright Stephen G||Online investment trust creation and management|
|US20020052841 *||Apr 10, 2001||May 2, 2002||Guthrie Paul D.||Electronic payment system|
|US20020087467 *||Nov 15, 2001||Jul 4, 2002||Mascavage John Joseph||Online purchasing method|
|US20030149662 *||Feb 9, 2001||Aug 7, 2003||Jon Shore||Apparatus, systems and methods for wirelessly transacting financial transfers , electronically recordable authorization transfers, and other information transfers|
|CA2217593A1||Apr 8, 1996||Oct 10, 1996||John Doggett||Electronic funds transfer instruments|
|CA2227768A1||Jul 23, 1996||Feb 6, 1997||Citibank, N.A.||Customer-directed, automated system for transferring funds between accounts|
|CA2269618A1||Oct 21, 1997||Apr 30, 1998||Unisys Corp||Method of transferring funds employing a three-node real-time electronic interlock|
|WO2000030051A1||Nov 18, 1999||May 25, 2000||Wintriss Marc V||A method and apparatus for facilitating business transactions over a network by providing a reliable verification source|
|WO2000075889A2||Jun 7, 2000||Dec 14, 2000||Perez Eduardo J||Automatic teller machine|
|1||*||Karsten Schulz. (Aug. 1999). The future of digital cash. Banking Policy Report, 18(15/16), 8. Retrieved Jul. 16, 2010, from Banking Information Source.|
|2||Passas, Nikos, Informal Value Transfer Systems and Criminal Organizations: a study into so-called underground banking networks (see pp. 13-19).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8117097 *||Dec 9, 2009||Feb 14, 2012||Citizens Financial Group, Inc.||Method and system for identifying fraudulent account activity|
|US8306914 *||Jan 7, 2011||Nov 6, 2012||American Express Travel Related Services Company, Inc.||Offsite financial account onboarding|
|US8321316||Feb 28, 2011||Nov 27, 2012||The Pnc Financial Services Group, Inc.||Income analysis tools for wealth management|
|US8321517 *||Apr 30, 2010||Nov 27, 2012||International Business Machines Corporation||Method and system for processing emails|
|US8374940||Feb 28, 2011||Feb 12, 2013||The Pnc Financial Services Group, Inc.||Wealth allocation analysis tools|
|US8401938||May 12, 2008||Mar 19, 2013||The Pnc Financial Services Group, Inc.||Transferring funds between parties' financial accounts|
|US8417614||Jul 2, 2010||Apr 9, 2013||The Pnc Financial Services Group, Inc.||Investor personality tool|
|US8423444||Jul 2, 2010||Apr 16, 2013||The Pnc Financial Services Group, Inc.||Investor personality tool|
|US8732079 *||Dec 10, 2012||May 20, 2014||Bank Of America Corporation||Cloud-based data augmentation|
|US8751381||Feb 23, 2012||Jun 10, 2014||Mastercard International Incorporated||Demand deposit account payment system|
|US8751385||May 15, 2008||Jun 10, 2014||The Pnc Financial Services Group, Inc.||Financial email|
|US8762272 *||Dec 27, 2012||Jun 24, 2014||Google Inc.||Management of emails containing payments|
|US8780115||Apr 6, 2010||Jul 15, 2014||The Pnc Financial Services Group, Inc.||Investment management marketing tool|
|US8791949||Apr 6, 2010||Jul 29, 2014||The Pnc Financial Services Group, Inc.||Investment management marketing tool|
|US8793190||Oct 2, 2012||Jul 29, 2014||American Express Travel Related Services Company, Inc.||Offsite financial account onboarding|
|US9098831||Dec 13, 2011||Aug 4, 2015||The Pnc Financial Services Group, Inc.||Search and display of human resources information|
|US9563758 *||May 12, 2014||Feb 7, 2017||International Business Machines Corporation||Increasing security of a device and/or system via questioning about a characteristic of the device and/or system|
|US9582830||May 16, 2014||Feb 28, 2017||American Express Travel Related Services Company, Inc.||Offsite financial account onboarding|
|US20080082434 *||Sep 28, 2007||Apr 3, 2008||Alibaba.Com Corporation||System and Method for Making Payment|
|US20100145834 *||Dec 9, 2009||Jun 10, 2010||Citizens Financial Group, Inc.||Method and system for identifying fraudulent account activity|
|US20100281122 *||Apr 30, 2010||Nov 4, 2010||International Business Machines Corporation||Method and system for processing emails|
|US20110004547 *||Sep 13, 2010||Jan 6, 2011||Bank Of America Corporation||Mobile transactions using account aliases|
|US20110004550 *||Sep 13, 2010||Jan 6, 2011||Bank Of America Corporation||Customer on-boarding system|
|US20110010292 *||Sep 13, 2010||Jan 13, 2011||Bank Of America Corporation||Payment transactions using payee account aliases|
|US20110010293 *||Sep 13, 2010||Jan 13, 2011||Bank Of America Corporation||Account alias data repository|
|US20120179608 *||Jan 7, 2011||Jul 12, 2012||Serve Virtual Enterprises, Inc.||Offsite financial account onboarding|
|US20140074705 *||Sep 10, 2012||Mar 13, 2014||Deborah Kimberg||Methods and systems for processing electronic disbursements|
|US20150324561 *||May 12, 2014||Nov 12, 2015||International Business Machines Corporation||Increasing security of a device and/or system via questioning about a characteristic of the device and/or system|
|U.S. Classification||705/39, 705/44|
|International Classification||G06Q20/40, G06Q20/02, G06F21/00, G06Q20/10|
|Cooperative Classification||G06Q20/02, G06Q20/4014, G06Q20/108, G06Q20/023, G06Q20/10, G06Q20/223, G06F21/31, G06F2221/2115, G06Q20/40, G06Q20/04, G06Q20/381|
|European Classification||G06Q20/04, G06Q20/02, G06Q20/10, G06Q20/381, G06Q20/023, G06Q20/40|
|Mar 24, 2004||AS||Assignment|
Owner name: CERTAPAY INC., CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FLEISHMAN, JACK;FUERSTENBERG, ZACK;REEL/FRAME:015254/0278
Effective date: 20040318
|Oct 20, 2010||AS||Assignment|
Owner name: ACXSYS CORPORATION, CANADA
Free format text: CHANGE OF NAME;ASSIGNOR:CERTAPAY INC.;REEL/FRAME:025166/0300
Effective date: 20031023
|May 7, 2014||FPAY||Fee payment|
Year of fee payment: 4