US20150278816A1 - Online payment transfer and identity management system and method - Google Patents

Online payment transfer and identity management system and method Download PDF

Info

Publication number
US20150278816A1
US20150278816A1 US14/737,087 US201514737087A US2015278816A1 US 20150278816 A1 US20150278816 A1 US 20150278816A1 US 201514737087 A US201514737087 A US 201514737087A US 2015278816 A1 US2015278816 A1 US 2015278816A1
Authority
US
United States
Prior art keywords
payment
funds
payee
ccf
remote system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/737,087
Inventor
Jack Fleishman
Zack Fuerstenberg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CERTAPAY Inc
Acxsys Corp
Original Assignee
CERTAPAY Inc
Acxsys Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CA002332656A priority Critical patent/CA2332656A1/en
Priority to US10/470,094 priority patent/US7844546B2/en
Priority to PCT/CA2002/000107 priority patent/WO2002059847A1/en
Priority to US12/954,814 priority patent/US9159058B2/en
Priority to CA2332656 priority
Application filed by CERTAPAY Inc, Acxsys Corp filed Critical CERTAPAY Inc
Priority to US14/737,087 priority patent/US20150278816A1/en
Assigned to CERTAPAY INC. reassignment CERTAPAY INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FLEISHMAN, JACK, FUERSTENBERG, ZACK
Assigned to ACXSYS CORPORATION reassignment ACXSYS CORPORATION CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: CERTAPAY INC.
Publication of US20150278816A1 publication Critical patent/US20150278816A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/023Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] characterized in that the neutral party is a clearing house
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108Remote banking, e.g. home banking
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/223Payment schemes or models based on the use of peer-to-peer networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/381Currency conversion
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, 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
    • G06Q20/401Transaction verification
    • G06Q20/4014Identity check for transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2115Third party

Abstract

A payment transfer method for transferring funds from a payer to payee is provided, including designating a payee and specifying a payment amount and an account; debiting the funds from the account and crediting a first trust account; and identifying the payee by verifying responses received in response to one or more challenge-response questions defined by the payer. If the one or more responses are verified, a second trust account may be debited and a payee account credited with the payment amount. The first and second trust accounts may then be reconciled. There is also provided a payment transfer facility for transferring funds, comprising an application server for storing payment data relating to a transfer of funds and a notification server for providing a notification of the transfer of funds.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of application Ser. No. 12/954,814, filed Nov. 26, 2010, which is a continuation of application Ser. No. 10/470,094, filed Mar. 24, 2004 (now U.S. Pat. No. 7,844,546), which is a national stage application from PCT/CA02/00107, filed Jan. 25, 2002, which claims priority from Canadian Patent Application No. 2,332,656, filed Jan. 26, 2001, the entireties of which are incorporated herein by reference.
  • FIELD OF INVENTION
  • 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.
  • BACKGROUND OF THE INVENTION
  • 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 full 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.
  • SUMMARY OF THE INVENTION
  • 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:
  • 1. Accesses the online banking service;
  • 2. Selects a recipient from a list of past payees or enters new recipient information to create a new payee;
  • 3. Specifies a payment amount, the account from which to draw the funds, and optionally an expiry date and a personalized message to the recipient; and
  • 4. Confirms the transaction to authorize the bank to draw the funds, following which notification is sent to the recipient advising of payment with referrals to various methods of collection; and
  • 5. Receives a confirmation message when the recipient accepts the payment.
  • The recipient may:
  • 1. “Web enable” an existing account or open online banking services;
  • 2. Deposit the payment into any bank account;
  • 3. Deposit the funds into a credit card account;
  • 4. Request delivery of a paper check; or
  • 5. Receive funds directly if the online banking service is an ATM.
  • 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.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • In drawings which illustrate by way of example only a preferred embodiment of the invention,
  • FIG. 1 is a block diagram illustrating a real-time clearing network for P2P payments according to the invention,
  • FIG. 2 is a block diagram illustrating the payor-payee relationship in the network of FIG. 1,
  • FIG. 3 is a block diagram illustrating user and data interfaces according to the invention,
  • FIGS. 4 a and 4 b are block diagrams illustrating an online P2P payment transaction where both payer and payee bank at a partner financial institution,
  • FIGS. 5 a and 5 b are block diagrams illustrating an offline P2P payment transaction where the payee does not bank at a partner financial institution,
  • FIG. 6 is a graph illustrating account netting at a partner financial institution,
  • FIG. 7 is a flow diagram illustrating the navigation path for an online P2P payment transaction where both payer and payee bank at a partner financial institution,
  • FIG. 8 is a block diagram illustrating an identity management system according to the invention,
  • FIGS. 9 a and 9 b are diagrammatic illustrations of a sequence of user interfaces for a payer sending a payment,
  • FIG. 10 is a diagrammatic illustration of a sample of a message to a payee,
  • FIG. 11 is a diagrammatic illustration of user interfaces for payee identity authentication,
  • FIG. 12 is a diagrammatic illustration of a user interface for a payee retrieving a payment,
  • FIG. 13 is a table illustrating user notifications generated according to the invention,
  • FIG. 14 is a table illustrating a request/response message set in the interaction between the CCF and a partner financial institution,
  • FIG. 15 is a table illustrating a sample message sets,
  • FIG. 16 is a block diagram illustrating a preferred security system for the CCF, and
  • FIG. 17 is a block diagram illustrating the relationship between logical service items in the system of the invention.
  • FIG. 18 is a block diagram illustrating an online P2P payment where the payee receives payment at an ATM.
  • FIG. 19 is a block diagram illustrating an online P2P payment between businesses.
  • FIG. 20 is a block diagram illustrating an online P2P payment between a customer and a retailer.
  • FIG. 21 is a block diagram illustrating a network for P2P payments between a payor and a payee in different jurisdictions according to the invention.
  • DETAILED DESCRIPTION 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 fund 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 FIG. 1, through industry-standard messaging adaptors. The CCF manages the status and accounting mechanisms to ensure that users at each end of a payment transfer are validated and notified throughout each step of the transaction. The CCF features a secure, open front-end to allow users that do not currently bank at partner institutions to “catch” payments using offline mechanisms that can reach and credit most accounts. If payees do not wish to receive payment electronically, they can request a check mailed to their address or, if receiving payment at an automated teller machine (ATM), they can obtain the funds directly.
  • 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.
  • FIG. 1 illustrates an Application Service Provider Model which allows financial institutions to rapidly deploy P2P payments on their appropriate delivery channel (Online Banking, ATM, Wireless, etc.) To maximize security and to minimize the risk of fraud, payments are always initiated from within the authenticated layer of a partner financial institution's delivery channel. As a result, each payment that enters the system for delivery originates from a trusted source. As shown in FIGS. 1 and 2, payees can receive their funds through the originating institution 101 (Payee #1 201) or at another affiliated partner 102 (Payee #2 202). Alternatively, customers banking at unaffiliated financial institutions (Payee #3 203) can request payment through offline disbursement mechanisms offered at a secure Web site 300 powered by the CCF 100. Partner financial institutions thus become a secure, real-time clearing network for P2P payments.
  • The architecture of the invention, illustrated in FIG. 3, consists of data and user interfaces that facilitate the movement of money between customers. Behind the scenes, a secure CCF Web site 300 allows partner institutions to manage security, marketing and customer support centrally through sophisticated administrative and reporting tools.
  • 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 FIGS. 4 a and 4 b. Accounts are held for each currency supported by the system. As a result, no exchange of funds between partner institutions is necessary to settle individual payments between customers 410, 415. Instead, payments are executed by transferring funds from a customer's account 404 to the consolidation trust account 401 at the originating institution 101. If the payee 415 is a customer at a partner institution 102, receipt of funds is accomplished by transferring monies in real-time from the consolidation trust account 402 at the payee's institution to the customer's account 405. Funds are available to the payee 415 for collection immediately after payment notification is sent. Collection may be effected by a withdrawal from an ATM.
  • 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 FIGS. 5 a and 5 b. The invention also offers the option of a payee 415 requesting delivery of a paper check by traditional mail for a nominal processing fee deducted directly from the amount they are receiving. Batch file payments are securely transferred to processing agencies on a nightly basis. EFT, ACH and credit card disbursements typically take between one to four business days while check delivery takes from five to seven business days for North American delivery.
  • 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 FIG. 6.
  • 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:
  • a) Daily reconciliation between the CCF 100 and its partner institutions: The CCF 100 matches transactions in its journal against those tracked by each partner institution and then reports any exceptions. Exception reports are investigated and addressed to ensure that accounts are balanced.
  • b) Daily settlement reporting for partner institutions. The CCF 100 calculates monetary obligations of each partner institution to all other partner institutions in the network based on the origin and destination of completed payments. Each partner institution is provided with a detail list of all corresponding payments as well as a summary of monies owed to the other partners. Partner institutions settle with each other outside of the CCF 100 by using existing large value fund transfer mechanisms available in their jurisdiction.
  • c) Feed the CCF's 100 finance and accounting systems: The transaction journal generates a number of accounting and control system reports.
  • d) Provide audit reports: Where an audit is required, the CCF 100 uses the transaction journal to generate accounting reports for all finds that have yet to be disbursed. The CCF 100 also retains historical records to facilitate account investigations.
  • e) Exception reporting: Partner institutions can send their client fund transaction log (covering activity in their consolidation trust accounts) to the CCF 100 to match these against the transaction journal for inconsistencies. If the two reports do not balance, an exception report is generated so that the situation can be investigated immediately and corrected if necessary.
  • 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.
  • FIG. 7 illustrates the payer and payee navigation paths where both payer 410 and payee 415 are existing clients with Web banking privileges at partner financial institutions.
  • As shown in FIG. 8, the invention provides an identity management system that leverages secure payment relationships between remote consumers. Each customer (payer 410 or payee 415) is granted a unique identity that is assigned when he or she first registers with the service. A payer 410 can establish a list of recurring personal payees 415 as required. While payee records are immediately added to the CCF database, they are not authenticated until they correctly answer one or more challenge-response questions defined by the payer and after successfully logging onto his or her institution's online banking service or other delivery channel 815. This process establishes both the payee and the specific “channel” where the payee has opted to deposit funds. If a customer wishes to credit an account at another institution on a subsequent transaction, the customer must re-authenticate with the original challenge-response questions before that new “channel” is secured. The challenge-response questions may include the input of a secret code provided by the payer 410 to the payee 415. In another embodiment, identity management is handled entirely by the authentication procedures of the partner institutions, thus allowing the institutions to manage the risk of fraud entirely by implementing their own security standards without the use of a payer-defined challenge-response question.
  • The identity management aspect of the invention provides the following advantages:
  • a) Increased system security: Customer account information from partner institutions is never stored at the CCF facility. The CCF 100 completes all processing against its own internal IDs, which are established when each customer auto-enrolls to send payments. Each CCF internal ID is referenced against an institution's customer user ID for message synchronization.
  • b) Transaction tracing: The CCF 100 holds a unique identifier for each customer it encounters. The CCF layers contact information for each customer identity in its database to facilitate notifications and authorizations. Each identity is cross-referenced back to the partner institutions' customer IDs to facilitate transactions, reporting, support and tracking without compromising personal information.
  • c) Enhanced consumer experience: The identity management model of the invention enables customers to retain “trusted” payment relationships to simplify future payments. These payee relationships are delivered on demand to a partner's system to encourage quick re-use of the “trusted” payee for subsequent transactions, thereby enhancing the user experience. These payee relationships can be deployed to other bank channels, such as WAP-enabled phones, through the message interface, to launch subsequent payments first established through a partner's Web banking service.
  • d) The consumer is validated on each channel before moving funds: Since the payment system offers customers a variety of mechanisms for “catching” payments, one may choose an account at a different partner institution into which funds are deposited on a subsequent visit. In this case, the payment system again asks the same challenge-response questions before validating the new payment channel, at which point the new account is deemed “trusted” and added to the consumer's identity.
  • 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) Institution-controlled security parameters: Each institution can define security parameters that govern transactions originating from their banking service. These default parameters include transaction limits, daily transaction limits per customer and the maximum number of days before an unretrieved payment is sent back to the payer for recrediting.
  • b) Initiation of payments: All payments originate from within an authenticated banking environment (for example, web, telephone, wireless network, ATM, or another access point to banking services) at a partner financial institution. One can initiate an email payment only when logged on, ensuring that such transactions are validated back to customer bank accounts at partner institutions.
  • c) Receiving payments: The recipient must authenticate and correctly answer one or more challenge-response questions before the retrieval of funds is allowed. The partner institution controls the number and type of challenge-response questions the payee must answer before the relationship is authenticated.
  • d) Audit trail: A detailed audit trail records all pending and historical payments.
  • e) Transaction integrity: The CCF's transaction management service guarantees that database transactions are completed accurately. If any one operation fails, the entire set of operations is rolled back. A global transaction identifier is created when a client application initiates a transaction. The transaction service monitors participants for failures and inactivity. Records accessed during a transaction are locked until its completion. A rollback procedure is executed when a transaction must be stopped due to unexpected client termination, server/network failure or other events that may interrupt end-to-end completion of the transaction. This procedure checks recently active transactions and then determines whether it should be rolled back or committed.
  • 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:
  • a) Undeliverable payments: If the payer specifies an invalid email address and the resulting notification bounces back to the server, the payer is automatically contacted and presented the option to re-credit his or her account or correct the recipient's email address to resend the payment notification.
  • b) Unretrieved (or expired) payments: With the CCF's back-office administration tool, affiliate institutions can each define a maximum period of time before a payment expires if uncollected by a payee. On a daily basis, the system will run a task to detect all expired payments. Notifications are sent to the payer and payee indicating expiration. The payer is then presented with the option to send it again or transfer the funds back into a specified account.
  • c) Cancelled payments: At any time before retrieval, the payer 410 can cancel a payment. After logging on to the originating Web banking facility or other delivery channel, the payer 410 simply cancels the payment transaction by indicating the account to be credited and sending an optional memo indicating why the payment was cancelled. The institution's banking service then sends a message to the CCF 100 containing the payment reference number. The CCF 100 will verify that the payee 415 has not retrieved the funds and the system will change the payment status to ‘Cancelled’ while sending notification to the payee 415.
  • d) Rejected payments: The payee 415 can reject a payment transaction from within the authenticated Web banking environment of an affiliate institution or upon authentication at the CCF Web site 300. If the payment is rejected, an email is sent to the payer 410 with instructions to log on to his or her Web banking facility or other delivery channel to select an account to re-credit the funds.
  • e) Invalid account information: If payees 415 select an offline electronic method to catch a payment, there exists the potential that incorrect account information might have been entered despite the processes performed at the interface layer. Transactions that cannot be completed through the ACH/EFT/RPS processing facilities are returned to the CCF 100. The payee 415 is then notified of the problem and given an opportunity to re-enter the account information or specify an alternate means of retrieval. If the subsequent attempts fail to deposit the funds into the payee's designated account, the funds are returned to the payer and both parties are appropriately notified.
  • f) Reconciliation process: On a daily basis, each partner institution 101, 102, 103 sends a file containing all transfers to and from the partner's consolidation trust accounts. Payment reference numbers are reconciled against information stored at the CCF 100.
  • With reference to FIGS. 7, 9 a and 18, a P2P payment may take place as follows:
  • 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 FIG. 18), or other means at 701 in FIG. 7. The customer selects 702 the payment feature 902 from the financial institution's menu of services and chooses from their list of prior payees. To enter a new recipient, the customer is prompted to enter the payee's name and e-mail address 703, if notification of the payment is to be delivered by e-mail to the payee. The customer specifies 704 payment amount, the account from which to draw the funds are specified, and optionally an expiry date and a personalized message to the recipient as shown at 910. To add an additional security measure to validate the recipient before fluids are disbursed, the customer can create one or more challenge-response questions and provide the requisite answers as shown at 911 in FIG. 9 b. Referring to FIG. 18, If the customer 1801 logs on using an ATM, these payment details are communicated from the ATM to the ATM switch 1802. As well, the customer is authenticated using the institution's security standards; where the customer logs onto an ATM, authentication of the customer is handled by the ATM switch 1802 in communication with the host system 1803 of the banking service. The payment details are communicated by the ATM switch 1802 to the CCF 100 (not shown in FIG. 18), which assigns a unique payment reference number and communicates this number to the ATM switch 1802. The ATM switch 1802 then communicates with the host system 1803, and the customer's account is debited for the payment and the financial institution's trust suspense account is correspondingly credited. The ATM switch 1802 communicates with the ATM to cause the ATM to provide a receipt to the customer 1801, which includes the payment reference number, then communicates the successful completion of this portion of the transaction to the CCF 100. Notification is delivered to the recipient announcing the payment 721.
  • 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 FIG. 10. The payment's originating institution may promote its services through banner advertisements in the body of the message. The invention provides multiple options for retrieving finds, as shown in 1103 in FIG. 11.
  • 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 FIG. 11, optionally identifies the payment by reference number and answer the challenge-response question if it is the first payment from that particular sender. This validates the relationship between both parties. The recipient may choose to log onto their online bank account 723 using another communications protocol, such as via a wireless network, telephone, or ATM.
  • 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 FIG. 12. To facilitate this process, the CCF Web site provides all appropriate links and information. Currently, the enrollment process for acquiring online banking services at a financial institution can take anywhere from a few minutes to a few weeks, especially if passwords must be issued by mail. In the case of a delay, the CCF will hold the payment for the appropriate number of days; customers must wait for their account to be activated at a partner institution. An e-mail reminder is sent to the customer to activate the service and retrieve their funds.
  • 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 funds are disbursed. Once the funds credit or disbursement is completed, the CCF 100 is informed of the successful completion. The funds may be advanced immediately by the recipient's institution, because the funds 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 FIGS. 4 b and 5 b, provides information to both parties regarding the status of a payment transaction. Each of the messages is based on a standard template, so that the payee receives the same message irrespective of the originating partner institution. Notifications have multilingual capabilities. FIG. 13 shows options 1301 for end-user notifications generated by the system of the invention.
  • 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 FIG. 19. The business customer 1901 logs onto its partner institution's online banking service 1902 and enters invoice data either manually or by importing a payment file 1903 from a third party accounting tool. The partner institution transfers the payment details 1904 to the CCF 100, which assigns a tracking number and optionally a universal resource locator (URL). The payment details are stored by the CCF 100, which then notifies the customer (payer) 1950 of the invoice. Preferably, the invoice is delivered by e-mail 1908 and directs the customer 1950 to its partner institution's online banking service 1951. The customer may choose to approve payment immediately, or may choose to view additional information regarding the invoice if such information is available (for example, through the URL or another hyperlink) When the payment is approved, the CCF 100 completes the payment in the manner described above and issues a receipt 1905, 1955 to both parties. The business customer can then log onto its institution's online banking service 1902 to collect the funds and optionally export transaction statements 1906 to a third party accounting tool.
  • In another embodiment, shown in FIG. 20, no invoice is issued to the customer 2001, but the customer initiates the payment as part of a retail transaction in an online environment. For example, in a web-based auction, the customer clicks on a “pay me” link appearing in a vendor's auction listing 2002. Clicking on this link passes payment details 2003 to the CCF 100, together with a token identifying the vendor 2050 and an optional return URL. In the meantime, the customer is referred to a partner institution, approves the transaction, and the payment is completed as generally described above.
  • 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.
  • Referring to FIG. 21, an international CCF site 2101 is primarily responsible for coordinating the exchange of data between the regional CCF sites. The international CCF also maintains a global directory of affiliated institutions. A foreign exchange (FX) facility 2110 maintains a database of exchange rates 2111 and manages currency exchange transactions, and maintains trust accounts 2115, 2120 in each jurisdiction in the local currency.
  • 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 CCF 2101. With reference to FIG. 21, 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.
  • Access to functions beneath the user interface layer is provided utilizing a request/response XML-based message set. All communications are encrypted and signed. FIG. 14 illustrates high-level interaction between a partner institution's middleware 1401 and the CCF facility 1410 to reconcile a payment to a new payee. FIG. 15 shows a number of possible message sets 1501 and explains how they are used to facilitate P2P payments. Each message set consists of a request initiated by a partner institution's middleware and a response returned by the CCF 100. These messages invoke additional system processes at the CCF 100.
  • 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 FIG. 16, provides performance, security, availability and scalability. The invention delivers protection from unauthorized external or internal access by implementing several industry standard mechanisms including: multi-layer firewall structure 1610 a, 1610 b; secure access lockdown of Web servers 1612 and mail servers 1615; extensive intrusion detection; documentation security and escalation procedures. The invention supports a cluster server architecture designed to provide maximum fault tolerance, performance and scalability.
  • 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 returns 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 FIG. 17, that are physically distributed through several redundant, fault-tolerant and balanced implementation systems. Presentation logic is the link between the client interface and the business logic. Using JavaBean and Servlet specifications, the presentation logic components communicate with the business logic components (EJBs) 1703 a, 1703 b, 1703 c . . . 1703 n. The presentation logic 1701 is based on the concept of heterogeneous client interfaces, allowing both browser and non-browser interfaces to communicate with the CCF 100. The messaging layer 1702 is the link between the partner institution and the business logic. This layer consists of a number of Java servlets 1702 a, 1702 b, 1702 c . . . 1702 n responsible for parsing and validating XML messages and the invocation of appropriate business components. Business logic is processed by a distributed middleware server with enabled clustering and object caching based on the Enterprise JavaBean standard. Both business logic and functional rules are maintained in a series of session beans and entity beans that are located on networked systems. Enterprise JavaBeans (EJBs) communicate with the associated data media and apply any relevant business rules. Data media and its associated transactions are maintained in an enterprise database system supporting both the encryption of resident data and the features that promote redundancy and reliability.
  • 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.
  • Java Beans
  • 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 HOP
  • RMI-IIOP provides developers an implementation of the Java RMI API over the Object Management Group's industry-standard Internet Inter-Orb Protocol (HOP). It allows developers to write remote interfaces between clients and servers and implement them using Java technology and the Java RMI APIs.
  • XML
  • 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.

Claims (1)

1. A method, comprising:
storing, at a central system, first payment data relating to at least one transfer of funds to a payee, the first payment data comprising a payment amount and payee data, the first payment data being received from a first remote system and being associated with a payer account of a payer maintained by the first remote system, the first remote system using a first security infrastructure to control access by the payer to the first remote system to initiate the at least one transfer of funds, the first payment data being defined after access by the payer to the first remote system to initiate the at least one transfer of funds is granted and prior to storage of said first payment data;
generating, by the central system, a transaction identifier and associating the transaction identifier with the first payment data;
determining, at the central system, whether the payee data is authenticated and stored at the central system;
initiating a transmission of a notification of the at least one transfer of funds to a communication address identified by the payee data, the notification including the transaction identifier;
receiving, from a user communication device associated with the payee, a communication associated with the transaction identifier;
after receiving the communication from the user communication device, in a transmission to the user communication device, directing a browser executing on the user communication device to a website associated with a second remote system to complete the at least one transfer of funds;
receiving, at the central system, second payment data from the second remote system, the second remote system using a second security infrastructure to control access by the payee to the second remote system in relation to the at least one transfer of funds, the second payment data being received after access by the payee to the second remote system is granted, the first and second security infrastructures and access to the first remote system and the second remote system being controlled independently of the central system;
in a further transmission, providing information about the transfer of funds, including an identifier of the payer and the payment amount, to the second remote system; and
transmitting verification of the at least one transfer of funds for receipt by the second remote system if the payee data is thus authenticated.
US14/737,087 2001-01-26 2015-06-11 Online payment transfer and identity management system and method Abandoned US20150278816A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CA002332656A CA2332656A1 (en) 2001-01-26 2001-01-26 Online payment transfer and identity management system and method
US10/470,094 US7844546B2 (en) 2001-01-26 2002-01-25 Online payment transfer and identity management system and method
PCT/CA2002/000107 WO2002059847A1 (en) 2001-01-26 2002-01-25 Online payment transfer and identity management system and method
US12/954,814 US9159058B2 (en) 2001-01-26 2010-11-26 Online payment transfer and identity management system and method
CA2332656 2011-01-26
US14/737,087 US20150278816A1 (en) 2001-01-26 2015-06-11 Online payment transfer and identity management system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/737,087 US20150278816A1 (en) 2001-01-26 2015-06-11 Online payment transfer and identity management system and method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/954,814 Continuation US9159058B2 (en) 2001-01-26 2010-11-26 Online payment transfer and identity management system and method

Publications (1)

Publication Number Publication Date
US20150278816A1 true US20150278816A1 (en) 2015-10-01

Family

ID=4168195

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/470,094 Active 2025-05-16 US7844546B2 (en) 2001-01-26 2002-01-25 Online payment transfer and identity management system and method
US12/954,814 Active US9159058B2 (en) 2001-01-26 2010-11-26 Online payment transfer and identity management system and method
US14/737,087 Abandoned US20150278816A1 (en) 2001-01-26 2015-06-11 Online payment transfer and identity management system and method

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/470,094 Active 2025-05-16 US7844546B2 (en) 2001-01-26 2002-01-25 Online payment transfer and identity management system and method
US12/954,814 Active US9159058B2 (en) 2001-01-26 2010-11-26 Online payment transfer and identity management system and method

Country Status (6)

Country Link
US (3) US7844546B2 (en)
AU (1) AU2002227835B2 (en)
CA (1) CA2332656A1 (en)
GB (1) GB2389443B (en)
MX (1) MXPA03006777A (en)
WO (1) WO2002059847A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3392815A4 (en) * 2015-12-17 2018-10-24 Alibaba Group Holding Limited Method for performing inter-system service operation, service platform, and target system
RU2682426C1 (en) * 2018-05-31 2019-03-19 Публичное Акционерное Общество "Сбербанк России" (Пао Сбербанк) METHOD AND SYSTEM FOR TRANSMITTING INFORMATION ON p2p TRANSFER
EP3467741A1 (en) * 2017-10-09 2019-04-10 Mastercard International Incorporated A system and method for performing peer to peer transfers

Families Citing this family (144)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2360635A3 (en) 1999-04-30 2013-04-10 PayPal, Inc. System and method for electronically exchanging value among distributed users
US8025212B2 (en) 1999-10-26 2011-09-27 The Western Union Company Cash payment for remote transactions
US7958027B2 (en) * 2001-03-20 2011-06-07 Goldman, Sachs & Co. Systems and methods for managing risk associated with a geo-political area
US20040143446A1 (en) * 2001-03-20 2004-07-22 David Lawrence Long term care risk management clearinghouse
US8121937B2 (en) 2001-03-20 2012-02-21 Goldman Sachs & Co. Gaming industry risk management clearinghouse
US20030233319A1 (en) * 2001-03-20 2003-12-18 David Lawrence Electronic fund transfer participant risk management clearing
US7146338B2 (en) 2001-06-28 2006-12-05 Checkfree Services Corporation Inter-network financial service
US8407143B2 (en) * 2002-03-27 2013-03-26 The Western Union Company International negotiable instrument payment
EP1490815A4 (en) * 2002-03-27 2006-09-06 First Data Corp Worldwide cash vendor payment
US7979348B2 (en) 2002-04-23 2011-07-12 Clearing House Payments Co Llc Payment identification code and payment system using the same
US20040054696A1 (en) * 2002-09-13 2004-03-18 Sheinis Joseph Igor System and method for using proxies
US7664698B2 (en) * 2002-09-30 2010-02-16 Ifedayo Udiani Simplified internet payment, security, & tax administration protocol (SIPSTAP)
US8447630B2 (en) * 2004-02-26 2013-05-21 Payment Pathways, Inc. Systems and methods for managing permissions for information ownership in the cloud
US7945511B2 (en) * 2004-02-26 2011-05-17 Payment Pathways, Inc. Methods and systems for identity authentication
DE10310100A1 (en) * 2003-03-06 2004-09-23 Daniel Freitag A method for electronic, automatic execution of a transfer
IL155050D0 (en) * 2003-03-24 2003-10-31 Supercom Ltd System and method for monitoring, controlling and reporting access and attendance and behavior
AU2003903229A0 (en) * 2003-06-25 2003-07-10 Ewise Systems Pty Ltd A system and method for facilitating on-line payment
US20050071247A1 (en) * 2003-09-16 2005-03-31 Karin Kelley Integrated transportation method and system
US7395319B2 (en) * 2003-12-31 2008-07-01 Checkfree Corporation System using contact list to identify network address for accessing electronic commerce application
US8725607B2 (en) 2004-01-30 2014-05-13 The Clearing House Payments Company LLC Electronic payment clearing and check image exchange systems and methods
US8015110B2 (en) * 2004-03-29 2011-09-06 Heartland Payment Systems, Inc. System and method of aggregating multiple transactions over network-based electronic payment transaction processing system
US8442953B2 (en) 2004-07-02 2013-05-14 Goldman, Sachs & Co. Method, system, apparatus, program code and means for determining a redundancy of information
US8996481B2 (en) 2004-07-02 2015-03-31 Goldman, Sach & Co. Method, system, apparatus, program code and means for identifying and extracting information
US8510300B2 (en) 2004-07-02 2013-08-13 Goldman, Sachs & Co. Systems and methods for managing information associated with legal, compliance and regulatory risk
US8762191B2 (en) 2004-07-02 2014-06-24 Goldman, Sachs & Co. Systems, methods, apparatus, and schema for storing, managing and retrieving information
US8016185B2 (en) * 2004-07-06 2011-09-13 Visa International Service Association Money transfer service with authentication
US7856384B1 (en) * 2004-07-14 2010-12-21 Yahoo! Inc. Systems and methods for providing security in international money exchanges
EP1810159A2 (en) * 2004-09-07 2007-07-25 Iconix, Inc. User interface and anti-phishing functions for an anti-spam micropayments system
US7487213B2 (en) * 2004-09-07 2009-02-03 Iconix, Inc. Techniques for authenticating email
US8407140B2 (en) * 2004-10-29 2013-03-26 Wells Fargo Bank, N.A. Global remittance platform
US7246741B2 (en) * 2005-03-21 2007-07-24 Netbank Method and system for processing a financial transaction
US20060271629A1 (en) * 2005-05-26 2006-11-30 Macdowell Alexander D Distributed Challenge and Response Recognition System
CN101563704B (en) * 2005-11-03 2012-07-04 支付途径股份有限公司 Methods and systems for identity authentication
DE102005054170A1 (en) * 2005-11-14 2007-05-24 Pintango Gmbh Procedure for processing payments via the Internet
NL1030506C2 (en) * 2005-11-24 2007-05-25 Paydutch Holding B V System for setting up a transaction between at least two parties via a network of computers and a method.
US20070162388A1 (en) * 2006-01-09 2007-07-12 Ncr Corporation Method and system for automated teller machine configuration
US7873573B2 (en) 2006-03-30 2011-01-18 Obopay, Inc. Virtual pooled account for mobile banking
CA2647636A1 (en) * 2006-03-30 2008-03-06 Obopay Inc. Mobile person-to-person payment system
US7848997B2 (en) * 2006-04-06 2010-12-07 Omx Technology Ab Securities settlement system
US20070250437A1 (en) * 2006-04-06 2007-10-25 Omx Technology Ab Securities settlement system
US20070265984A1 (en) * 2006-04-24 2007-11-15 Prakash Santhana Financial transaction using mobile devices
KR20130055700A (en) * 2006-07-06 2013-05-28 퀄컴 인코포레이티드 Methods and systems for financial transactions in a mobile environment
US9911114B2 (en) 2006-07-06 2018-03-06 Qualcomm Incorporated Methods and systems for making a payment via a stored value card in a mobile environment
US20080027874A1 (en) * 2006-07-26 2008-01-31 Monseignat Bernard De System and method for facilitating secure transactions over communication networks
US8909553B2 (en) * 2006-09-06 2014-12-09 Transaction Wireless, Inc. Payment card terminal for mobile phones
US20080071664A1 (en) * 2006-09-18 2008-03-20 Reuters America, Inc. Limiting Counter-Party Risk in Multiple Party Transactions
CN101154283A (en) * 2006-09-29 2008-04-02 阿里巴巴公司 System and method for implementing payment
US7739193B2 (en) * 2006-12-27 2010-06-15 Sap Ag Paying multiple payees through integration of a third-party on-line payment system with an enterprise information technology system
US20080162340A1 (en) * 2006-12-27 2008-07-03 Robert Zimmer Integrating enterprise information technology systems with a third-party on-line payment system
US20080288400A1 (en) 2007-04-27 2008-11-20 Cashedge, Inc. Centralized Payment Method and System for Online and Offline Transactions
US8161540B2 (en) * 2007-07-27 2012-04-17 Redshift Internetworking, Inc. System and method for unified communications threat management (UCTM) for converged voice, video and multi-media over IP flows
WO2009018443A1 (en) * 2007-07-31 2009-02-05 City National Bank Systems and methods for processing banking transactions
US8768853B2 (en) * 2007-10-05 2014-07-01 Ebay Inc. Secondary identification for remittance delivery
US8730946B2 (en) * 2007-10-18 2014-05-20 Redshift Internetworking, Inc. System and method to precisely learn and abstract the positive flow behavior of a unified communication (UC) application and endpoints
US8176001B2 (en) * 2007-10-18 2012-05-08 Redshift Internetworking, Inc. System and method for detecting spam over internet telephony (SPIT) in IP telecommunication systems
US20090106118A1 (en) * 2007-10-19 2009-04-23 Ebay Inc Payment using funds pushing
US8185457B1 (en) * 2007-10-25 2012-05-22 United Services Automobile Association (Usaa) Transaction risk analyzer
US8249985B2 (en) * 2007-11-29 2012-08-21 Bank Of America Corporation Sub-account mechanism
SE532268C2 (en) * 2007-12-04 2009-11-24 Accumulate Ab Method for secure transactions
US8306912B2 (en) * 2007-12-19 2012-11-06 Metabank Private label promotion card system, program product, and associated computer-implemented methods
WO2009124262A1 (en) 2008-04-04 2009-10-08 Metabank System, program product and method for performing an incremental automatic credit line draw using a prepaid card
WO2009140512A1 (en) 2008-05-14 2009-11-19 Metabank Loading a loan on a pre-paid card
US8055557B2 (en) * 2007-12-21 2011-11-08 Metabank Transfer account systems, computer program products, and associated computer-implemented methods
US8589295B2 (en) 2007-12-21 2013-11-19 Metabank Transfer account systems, computer program products, and associated computer-implemented methods
US8175962B2 (en) 2008-12-18 2012-05-08 Metabank Computerized extension of credit to existing demand deposit accounts, prepaid cards and lines of credit based on expected tax refund proceeds, associated systems and computer program products
US8108279B2 (en) 2007-12-21 2012-01-31 Metabank Computer-implemented methods, program product, and system to enhance banking terms over time
US8090649B2 (en) 2008-12-18 2012-01-03 Metabank Computerized extension of credit to existing demand deposit accounts, prepaid cards and lines of credit based on expected tax refund proceeds, associated systems and computer program products
US8069085B2 (en) * 2007-12-21 2011-11-29 Metabank System, program product, and associated methods to autodraw for micro-credit attached to a prepaid card
SG154345A1 (en) * 2008-01-09 2009-08-28 Banking Comp Services Private Electronic payment method of presentation to an automated clearing house (ach)
US20090204498A1 (en) * 2008-02-08 2009-08-13 Scott Galit Government Targeted-Spending Stimulus Card System, Program Product, And Computer-Implemented Methods
US20090228307A1 (en) * 2008-03-03 2009-09-10 Trent Sorbe Person-To-Person Lending Program Product, System, And Associated Computer-Implemented Methods
WO2009124264A1 (en) 2008-04-04 2009-10-08 Metabank System, program product, and method for debit card and checking account autodraw
US8401938B1 (en) 2008-05-12 2013-03-19 The Pnc Financial Services Group, Inc. Transferring funds between parties' financial accounts
US8538879B2 (en) 2008-05-14 2013-09-17 Metabank System, program product, and computer-implemented method for loading a loan on an existing pre-paid card
US8751385B1 (en) 2008-05-15 2014-06-10 The Pnc Financial Services Group, Inc. Financial email
US8187972B2 (en) * 2008-07-01 2012-05-29 Teledyne Scientific & Imaging, Llc Through-substrate vias with polymer fill and method of fabricating same
US8751379B1 (en) * 2008-08-04 2014-06-10 United Services Automobile Association (Usaa) Mobile money transfers
US20100042539A1 (en) * 2008-08-18 2010-02-18 Sanjeev Dheer Money Movement Network Hub System
FR2935515B1 (en) * 2008-09-01 2015-12-25 Caisse Nationale Des Caisses D Epargne Et De Prevoyance Method and system for secure communication and sending of information, and assembly for transmitting information between a sender and a recipient.
US8403211B2 (en) 2008-09-04 2013-03-26 Metabank System, program product and methods for retail activation and reload associated with partial authorization transactions
WO2010028266A1 (en) 2008-09-04 2010-03-11 Metabank System, program product and methods for retail activation and reload associated with partial authorization transactions
US8024242B2 (en) 2008-09-04 2011-09-20 Metabank System, method, and program product for foreign currency travel account
CN102216948A (en) * 2008-09-12 2011-10-12 尼古拉斯·伯宰 Money transfer system and method
US7594821B1 (en) 2008-09-17 2009-09-29 Yazaki North America, Inc. Sealing gap formed by assembled connector parts
US20100082466A1 (en) * 2008-09-26 2010-04-01 Mark Carlson Beneficiary initiated p2p, p2b payment model
US8371502B1 (en) 2008-10-28 2013-02-12 Metabank Shopping center gift card offer fulfillment machine, program product, and associated methods
US8108977B1 (en) 2008-10-31 2012-02-07 Metabank Machine, methods, and program product for electronic order entry
US7827108B2 (en) * 2008-11-21 2010-11-02 Visa U.S.A. Inc. System and method of validating a relationship between a user and a user account at a financial institution
US9213965B1 (en) 2008-11-26 2015-12-15 Metabank Machine, methods, and program product for electronic inventory tracking
US8117097B2 (en) * 2008-12-10 2012-02-14 Citizens Financial Group, Inc. Method and system for identifying fraudulent account activity
US8965798B1 (en) * 2009-01-30 2015-02-24 The Pnc Financial Services Group, Inc. Requesting reimbursement for transactions
US8286863B1 (en) 2009-02-04 2012-10-16 Metabank System and computer program product to issue a retail prepaid card including a user-designed external face using a chit and related computer implemented methods
CN101877679B (en) * 2009-04-30 2013-01-23 国际商业机器公司 Method and system used for processing email
US8271362B2 (en) * 2009-06-22 2012-09-18 Mastercard International, Inc. Methods and apparatus for providing centralized web services for funds transfer system
US20110082737A1 (en) 2009-09-28 2011-04-07 Crowe Andrew B Computer-implemented methods, computer program products, and systems for management and control of a loyalty rewards network
US20110184840A1 (en) * 2010-01-27 2011-07-28 Ebay Inc. Systems and methods for facilitating account verification over a network
US8791949B1 (en) 2010-04-06 2014-07-29 The Pnc Financial Services Group, Inc. Investment management marketing tool
US8780115B1 (en) 2010-04-06 2014-07-15 The Pnc Financial Services Group, Inc. Investment management marketing tool
US8417614B1 (en) 2010-07-02 2013-04-09 The Pnc Financial Services Group, Inc. Investor personality tool
US8423444B1 (en) 2010-07-02 2013-04-16 The Pnc Financial Services Group, Inc. Investor personality tool
US20120078765A1 (en) * 2010-09-27 2012-03-29 Ebay Inc. Instant Financial Account Verification Using Direct Connect Data Communication Protocol And Open Financial Exchange Data-Stream Format
US20120173409A1 (en) * 2010-12-30 2012-07-05 Ebay Inc. Real-time global fund transfers
US8306914B2 (en) * 2011-01-07 2012-11-06 American Express Travel Related Services Company, Inc. Offsite financial account onboarding
US8751381B2 (en) 2011-02-23 2014-06-10 Mastercard International Incorporated Demand deposit account payment system
US9852470B1 (en) 2011-02-28 2017-12-26 The Pnc Financial Services Group, Inc. Time period analysis tools for wealth management transactions
US9665908B1 (en) 2011-02-28 2017-05-30 The Pnc Financial Services Group, Inc. Net worth analysis tools
US8374940B1 (en) 2011-02-28 2013-02-12 The Pnc Financial Services Group, Inc. Wealth allocation analysis tools
US8321316B1 (en) 2011-02-28 2012-11-27 The Pnc Financial Services Group, Inc. Income analysis tools for wealth management
WO2012120011A1 (en) * 2011-03-07 2012-09-13 Giori Roberto System and method for providing and transferring fungible electronic money
US9098831B1 (en) 2011-04-19 2015-08-04 The Pnc Financial Services Group, Inc. Search and display of human resources information
US10417618B2 (en) * 2011-05-12 2019-09-17 Moneygram International, Inc. Methods and system for utilizing cash with online activities
US9971587B2 (en) * 2011-07-29 2018-05-15 Glory Global Solutions (International) Limited System and method for validating a controller for an automated banking machine using a displayed indicia
US8515870B2 (en) * 2011-09-06 2013-08-20 Rawllin International Inc. Electronic payment systems and supporting methods and devices
US10366390B2 (en) 2011-09-23 2019-07-30 Visa International Service Association Automatic refresh authorization for expired payment transaction authorizations
US10169812B1 (en) 2012-01-20 2019-01-01 The Pnc Financial Services Group, Inc. Providing financial account information to users
US8930267B1 (en) * 2012-08-27 2015-01-06 Jpmorgan Chase Bank, N.A. Automated transactions clearing system and method
US10096008B2 (en) * 2012-09-10 2018-10-09 Mastercard International Incorporated Methods and systems for processing electronic disbursements
US8732079B1 (en) * 2012-12-10 2014-05-20 Bank Of America Corporation Cloud-based data augmentation
US8762272B1 (en) 2012-12-27 2014-06-24 Google Inc. Management of emails containing payments
US10282712B2 (en) * 2013-02-07 2019-05-07 Jpmorgan Chase Bank, N.A. Integrated electronic disbursement and cash flow management system and method
US9449321B2 (en) 2013-03-15 2016-09-20 Square, Inc. Transferring money using email
US9536232B2 (en) 2013-03-15 2017-01-03 Square, Inc. Transferring money using email
US20140310171A1 (en) * 2013-04-12 2014-10-16 Bank Of America Corporation Certified person-to-person payment system
US20140337207A1 (en) * 2013-04-28 2014-11-13 Tencent Technology (Shenzhen) Company Limited Method, device, server, and system for making payment with a messaging application on a mobile device
US20140358781A1 (en) * 2013-05-28 2014-12-04 Gary David Zeigler System and method for authenticating and securing online purchases
US20150066719A1 (en) * 2013-08-30 2015-03-05 Yodlee, Inc. Financial Account Authentication
US9165291B1 (en) 2013-10-15 2015-10-20 Square, Inc. Payment transaction by email
US9934493B2 (en) 2014-01-13 2018-04-03 Bank Of America Corporation Real-time transactions for a virtual account
USD769274S1 (en) 2014-04-21 2016-10-18 Square, Inc. Display screen with a graphical user interface
US9563758B2 (en) * 2014-05-12 2017-02-07 International Business Machines Corporation Increasing security of a device and/or system via questioning about a characteristic of the device and/or system
WO2015176105A1 (en) * 2014-05-18 2015-11-26 Eftsure Pty Ltd Online payment authentication method & system
US20150363778A1 (en) * 2014-06-16 2015-12-17 Bank Of America Corporation Cryptocurrency electronic payment system
WO2016005937A2 (en) * 2014-07-09 2016-01-14 Vineet Katial A method and system for processing invoices for a user
WO2016061349A1 (en) * 2014-10-15 2016-04-21 Mastercard International Incorporated Bottom of the pyramid pay method and system
US10373134B1 (en) 2014-12-15 2019-08-06 Wells Fargo Bank, N.A. Scrub and match and payee account match
US10210499B1 (en) 2014-12-15 2019-02-19 Wells Fargo Bank, N.A. Global cache tool systems and methods for adding new payees
US10164932B2 (en) * 2015-01-30 2018-12-25 Loturas Incorporated Communication system and server facilitating message exchange and related methods
US10410194B1 (en) 2015-08-19 2019-09-10 Square, Inc. Customized tipping flow
US10127532B1 (en) 2015-08-19 2018-11-13 Square, Inc. Customized transaction flow
WO2017160660A2 (en) * 2016-03-15 2017-09-21 Visa International Service Association Validation cryptogram for interaction
US20180068304A1 (en) * 2016-09-08 2018-03-08 Modopayments, Llc COIN Operated Digital Payments Hub
USD837227S1 (en) 2016-09-12 2019-01-01 Square, Inc. Display screen with graphical user interface for a mobile device
US9881296B1 (en) * 2016-09-12 2018-01-30 Square, Inc. Processing a mobile payload
EP3502994A1 (en) * 2017-12-22 2019-06-26 Mastercard International Incorporated Method and system for trusted notifications

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5650604A (en) * 1995-02-22 1997-07-22 Electronic Data Systems Corporation System and method for electronic transfer of funds using an automated teller machine to dispense the transferred funds
US5677955A (en) * 1995-04-07 1997-10-14 Financial Services Technology Consortium Electronic funds transfer instruments

Family Cites Families (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4823264A (en) * 1986-05-27 1989-04-18 Deming Gilbert R Electronic funds transfer system
US4960981A (en) * 1989-01-17 1990-10-02 Moneyfax, Inc. Method of and system for electronic funds transfer via facsimile machines
US5326960A (en) * 1992-11-25 1994-07-05 Tannenbaum David H Currency transfer system and method
US5350906A (en) * 1992-11-25 1994-09-27 Brody Bill E Currency transfer system and method using fixed limit cards
US5557518A (en) * 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
US5590196A (en) * 1994-10-06 1996-12-31 Connotech Experts Conseils Inc. Secure payment method using facsimile
KR19990028355A (en) * 1995-07-06 1999-04-15 가나이 쓰도무 Electronic money transfer system
US5659165A (en) * 1995-07-24 1997-08-19 Citibank. N.A. Customer-directed, automated process for transferring funds between accounts via a communications network
US5825003A (en) * 1995-07-24 1998-10-20 Citicorp Development Center Customer-directed, automated process for transferring funds between accounts using a holding account and local processing
US5699528A (en) * 1995-10-31 1997-12-16 Mastercard International, Inc. System and method for bill delivery and payment over a communications network
US5757917A (en) * 1995-11-01 1998-05-26 First Virtual Holdings Incorporated Computerized payment system for purchasing goods and services on the internet
US5897621A (en) * 1996-06-14 1999-04-27 Cybercash, Inc. System and method for multi-currency transactions
US5884290A (en) 1996-10-22 1999-03-16 Unisys Corporation Method of transferring funds employing a three-node real-time electronic interlock
US5937396A (en) * 1996-12-04 1999-08-10 Konya; Arpad System for ATM/ATM transfers
US5963647A (en) * 1997-02-14 1999-10-05 Citicorp Development Center, Inc. Method and system for transferring funds from an account to an individual
US5949044A (en) * 1997-06-13 1999-09-07 Walker Asset Management Limited Partnership Method and apparatus for funds and credit line transfers
US5974146A (en) * 1997-07-30 1999-10-26 Huntington Bancshares Incorporated Real time bank-centric universal payment system
US7747523B2 (en) * 1998-03-30 2010-06-29 Cohen Morris E Internet-based financial vehicles
US6173272B1 (en) 1998-04-27 2001-01-09 The Clearing House Service Company L.L.C. Electronic funds transfer method and system and bill presentment method and system
AU1069500A (en) * 1998-11-18 2000-06-05 Marc V. Wintriss A method and apparatus for facilitating business transactions over a network by providing a reliable verification source
US6609113B1 (en) * 1999-05-03 2003-08-19 The Chase Manhattan Bank Method and system for processing internet payments using the electronic funds transfer network
WO2000075889A2 (en) * 1999-06-08 2000-12-14 Perez Eduardo J Automatic teller machine
US7395241B1 (en) * 2000-01-19 2008-07-01 Intuit Inc. Consumer-directed financial transfers using automated clearinghouse networks
US8706627B2 (en) * 2000-02-10 2014-04-22 Jon Shore Apparatus, systems and methods for wirelessly transacting financial transfers , electronically recordable authorization transfers, and other information transfers
US7366695B1 (en) * 2000-02-29 2008-04-29 First Data Corporation Electronic purchase method and funds transfer system
US7454376B1 (en) * 2000-07-21 2008-11-18 Argenbright Stephen G Online investment trust creation and management
AU8542201A (en) * 2000-08-11 2002-02-25 John J Loy Trade receivable processing method and apparatus
US7206768B1 (en) * 2000-08-14 2007-04-17 Jpmorgan Chase Bank, N.A. Electronic multiparty accounts receivable and accounts payable system
AU9060501A (en) * 2000-08-31 2002-03-13 Atm Direct Inc System and method for online atm transaction with digital certificate
US7415442B1 (en) * 2000-09-26 2008-08-19 Integrated Technological Systems, Inc. Integrated technology money transfer system
US20020052841A1 (en) * 2000-10-27 2002-05-02 Guthrie Paul D. Electronic payment system
US20030046224A1 (en) * 2001-08-30 2003-03-06 Mujtaba M. Shahid Method and apparatus for handling monetary transactions
MXPA04004951A (en) * 2001-11-26 2004-08-11 Epacific Inc Systems and methods for fund transfers.
US8407143B2 (en) * 2002-03-27 2013-03-26 The Western Union Company International negotiable instrument payment
US7280981B2 (en) * 2002-08-27 2007-10-09 Visa U.S.A. Inc. Method and system for facilitating payment transactions using access devices
US20040138991A1 (en) * 2003-01-09 2004-07-15 Yuh-Shen Song Anti-fraud document transaction system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5650604A (en) * 1995-02-22 1997-07-22 Electronic Data Systems Corporation System and method for electronic transfer of funds using an automated teller machine to dispense the transferred funds
US5677955A (en) * 1995-04-07 1997-10-14 Financial Services Technology Consortium Electronic funds transfer instruments

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3392815A4 (en) * 2015-12-17 2018-10-24 Alibaba Group Holding Limited Method for performing inter-system service operation, service platform, and target system
EP3467741A1 (en) * 2017-10-09 2019-04-10 Mastercard International Incorporated A system and method for performing peer to peer transfers
WO2019074686A1 (en) * 2017-10-09 2019-04-18 Mastercard International Incorporated A system and method for performing peer to peer transfers
RU2682426C1 (en) * 2018-05-31 2019-03-19 Публичное Акционерное Общество "Сбербанк России" (Пао Сбербанк) METHOD AND SYSTEM FOR TRANSMITTING INFORMATION ON p2p TRANSFER

Also Published As

Publication number Publication date
GB2389443A (en) 2003-12-10
US20040148252A1 (en) 2004-07-29
CA2332656A1 (en) 2002-07-26
US20110125644A1 (en) 2011-05-26
GB2389443B (en) 2004-10-06
MXPA03006777A (en) 2005-04-08
WO2002059847A1 (en) 2002-08-01
WO2002059847B1 (en) 2002-09-19
GB0319878D0 (en) 2003-09-24
AU2002227835B2 (en) 2007-09-13
US9159058B2 (en) 2015-10-13
US7844546B2 (en) 2010-11-30

Similar Documents

Publication Publication Date Title
Neuman et al. Requirements for network payment: the NetCheque perspective
US8468092B2 (en) Method and system for processing internet payments using the electronic funds transfer network
US8793185B1 (en) System and method for securing information distribution via email
US7797233B2 (en) Methods and systems for processing, accounting, and administration of stored value cards
US6932268B1 (en) Dual mode credit card based payment technique
RU2438172C2 (en) Method and system for performing two-factor authentication in mail order and telephone order transactions
CA2366517C (en) Person-to-person, person-to-business, business-to-person, and business-to-business financial transaction system
AU754886B2 (en) A virtual private lock box
AU764816B2 (en) Methods and systems for carrying out directory-authenticated electronic transactions including contingency-dependent payments via secure electronic bank drafts
CN102844776B (en) Return to the channel of disbursement of the limited proxy dynamic value used
US7689487B1 (en) Computer-assisted funds transfer system
JP6294056B2 (en) Decentralized capital system method, system, computer system, non-volatile computer readable medium, computer readable medium
US10387879B2 (en) Payment identification code and payment system using the same
US8676674B2 (en) Peer-to-peer and group financial management systems and methods
JP3315126B2 (en) Trust agent for open electronic commerce
JP3190882B2 (en) Open network sales systems and methods
AU2001248198B2 (en) A method and system for a virtual safe
US7269256B2 (en) Electronic-monetary system
AU2001251286B2 (en) System, method and apparatus for international financial transactions
US8814039B2 (en) Methods for processing a payment authorization request utilizing a network of point of sale devices
US7788172B2 (en) Inter-network electronic billing
US20040039692A1 (en) On-line payment system
US6594647B1 (en) Real time bank-centric universal payment system
US20020087467A1 (en) Online purchasing method
US20020087344A1 (en) System and method for collecting information to facilitate enrollment in an electronic funds transfer program

Legal Events

Date Code Title Description
AS Assignment

Owner name: ACXSYS CORPORATION, CANADA

Free format text: CHANGE OF NAME;ASSIGNOR:CERTAPAY INC.;REEL/FRAME:035940/0408

Effective date: 20031023

Owner name: CERTAPAY INC., CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FLEISHMAN, JACK;FUERSTENBERG, ZACK;REEL/FRAME:035825/0194

Effective date: 20040318

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION