Bottomline Technologies (de) Inc.

Bottomline Technologies Limited

Eric Campbell

Maris Norbert Lemanis

Robert F Hoffman

Robert Maloney, Jr

Andrew Mintzer

Amy Beth Hoke

Michael Alan Vigue

Nicole Pierrette Dwyer

Nicholas Anthony Griffin

Vincent Bahl

Eve Renee Nebenhaus

A system and method is presented for receiving required information (i.e., clearing information) for performing a global electronic funds transfer. The system and method generates a form for receiving the clearing information from a user. The form includes clearing information fields that are each configured to accept an element of clearing information. The clearing information fields of the form are dynamically updated based on clearing information rules. The clearing information rules define a relationship between at least one of the clearing information fields and the clearing information received from the user. The dynamically updated form is provided to the user to input further clearing information.

System and method for collecting clearing information for implementing a global electronic funds transfer

A payment system executes payments from payers to vendors. An unattended interface system automates the uploading of payments file from each payer to the system. A web services transfer server performs the unattended transfer. Steps of a payment server generating an electronic funds transfer file with a group of fund transfer records for each payment represented by a record of the payment file. After the electronic funds transfer file is complete, the steps further comprise transferring the electronic fund transfer file to an electronic payment network for execution. Remittance records are transferred to the vendor utilizing an unattended transfer executed by the web services transfer server.

Integrated payment system

A method for automatically transferring a data file from a network drive of a client controlled local area network to a transfer server over the Internet comprises using a first workstation to configure event parameters within event tables of the transfer server. An unattended interface module executed by a processor of a second workstation obtains, from the transfer server, the event parameters stored in the event tables. The event parameters comprise a file name and a directory path. The file name identifies the data file to be uploaded. The directory path identifies an upload directory of the network drive. The second workstation periodically searches the upload directory and, upon locating a data file in the upload directory with the file name, transfers the data file to the transfer server over a secure connection established with the transfer server over the internet.

Transfer server of a secure system for unattended remote file and message transfer

A supplemental financial transaction processing system operates with a primary system to provide financial transaction processing services to a client system which has established a secure session with the primary system. A secure web services system receives a transaction request identifying the primary system and: i) assigns a unique redirect URL to the transaction request, and ii) returns the unique redirect URL to the primary system. The primary system provides the unique redirect URL to the client system. The supplemental transaction server: i) provides a web document object to the client system; ii) receives a post of the financial transaction from the client system; and iii) performs at least one of: i) writing the financial transaction to a transaction database; or ii) forwarding the financial transaction to a processing system distinct from the supplemental transaction processing system.

System and method for providing supplemental transaction processing services to users of a primary financial services system

A supplemental financial transaction processing system operates in conjunction with one or more primary financial services systems for purposes of providing supplemental financial transaction processing services to users of the primary financial services system. The supplemental financial transaction processing system comprises a secure web services system and a supplemental transaction server. The secure web services system comprises at least one financial transaction method available to the primary financial services system. Upon receipt of a method call for a financial transaction, the supplemental financial transaction processing system: i) associates a unique redirect URL to the method call; and ii) returns the unique redirect URL to the primary financial services system. The primary financial services system may then pass the unique redirect URL through a secure connection with its client. The supplemental transaction server, upon a client requesting an HTTPS connection to the unique redirect URL, verifies the validity of the unique redirect URL. If valid, a web document object is provided for rendering by the client. The web document object comprises: i) the financial institution defined transaction values (at least one); ii) user interface control script for rendering of controls for obtaining user entry of at least one client defined transaction value; and iii) transaction control script. The transaction control script comprises instructions for i) creating a financial transaction; ii) validating the financial transaction; and iii) posting the validated transaction back to the supplemental financial transaction server.

A system provides for the secure exchanging files with a remote transfer server over an open network such as the Internet. The system comprises a database storing file transfer parameters in association with identification of a remote file transfer client. The file transfer parameters include object destination parameters defining a processing call to a transfer server message queuing manager operating in conjunction with the transfer server. The processing call provides for delivery of the binary object to the transfer server message queuing manager in conjunction with a destination queue definition which provides for queuing the binary object within the defined queue for retrieval by a destination application. A transfer application coupled to the database comprises a plurality of file transfer methods available to remote file transfer clients making method calls thereto. The plurality of transfer methods comprise: i) an event definition method for providing to the remote transfer client the file transfer event parameters that are associated with the remote transfer client in response to receiving a method call from the remote transfer client; ii) an upload method for storing a binary object in a binary storage in response to receiving a method call from the remote transfer client that includes the binary object; and iii) a destination method for executing a processing call to the transfer server message queuing manager in response to receiving a method call from the remote transfer client that includes the object destination parameters, the processing call delivering the binary object from the binary storage to the transfer server method queuing manager in conjunction with the destination queue definition.

Secure transport gateway for message queuing and transport over an open network

A web server system provides for the secure exchanging files with a remote transfer server over an open network such as the Internet. The transfer server operates a plurality of transfer methods. Exemplary transfer methods comprise: i) a log-on method comprising steps for returning a session ID to an authenticated transfer client; ii) an active event keys method comprising steps for returning each of a plurality of event keys associated with the transfer client; iii) a read event method comprising steps for returning event parameters associated with an event key, iv) an upload method comprising steps for receiving and storing a binary object in an object storage and associating the binary object with an object ID value in an ownership table; v) a process binary object method comprising steps for determining data elements within the binary contents of the file an loading the data elements into an application table in accordance with the loading rules; and vi) a set owner method comprising steps for associating the identification of a second transfer client with the object ID value in the ownership table.

A web server system provides for the secure exchanging files with a remote transfer server over an open network such as the Internet. The transfer server operates a plurality of transfer methods. Exemplary transfer methods comprise: i) a log-on method operated comprising steps for returning a session ID to an authenticated transfer client; ii) an active event keys method comprising steps for returning each of a plurality of event keys associated with the transfer client; iii) a read event method comprising steps for returning event parameters associated with an event identified by its event key, iv) a create binary object event comprising steps for extracting data from an application database, storing a binary object of the extracted data, and recording the binary object in an ownership table, v) a check availability method for determining whether a binary object matching a class exists; and vi) an download method comprising steps for sending a message to the transfer client which includes a binary object identified in a request from the transfer client.

A transfer client system exchanges files with a transfer server over an open network such as the Internet. The transfer client comprises an upload directory for storing files for subsequent transfer to the transfer server, an authentication registry securely storing authentication credentials, and a transfer client. The transfer client sends a log-on message to a remote transfer server over a secure transport protocol logical connection established over the open network. The log-on message includes the authentication credentials. In response the transfer client receives a session ID from the remote transfer server. The transfer client then sends a read event message to the remote transfer server which includes Session ID obtained from the remote transfer server. In response the transfer client obtains event parameters which include identification of a file name and an upload directory path previously stored in an events parameter table. The transfer client searches the upload directory and makes a file upload method call included within a Simple Object Access Protocol message over a secure transport layer logical connection over the open network to provide, to the transfer server, the binary contents of a file matching the file name and located in the upload directory.

Transfer client of a secure system for unattended remote file and message transfer

A transfer client system exchanges files with a transfer server over an open network such as the Internet. The transfer client comprises a download directory for storing binary objects obtained from a transfer client server for subsequent retrieval by a local data processing system. The transfer client sends a log-on message to a remote transfer server over the open network, the log-on message including the authentication credentials. In response a session ID is obtained from the remote transfer server. The transfer client further sends a read event message to the remote transfer server over the open network, the read event message including the session ID. Event parameters are returned in response, the event parameters comprise identification of a file name and identification of the download directory. The transfer client sends a download message to the remote transfer server over the open network, the download message comprises the session ID and identification of a binary object. A message containing the binary object is returned in response to the file download message and the binary object is stored as a file in the download directory with the file name.

A system provides for the secure exchanging files with a remote transfer server over an open network such as the Internet. The system comprises a database with file transfer tables, a hypertext transport protocol (HTTP) server, and a web services server. The HTTP server is coupled to the database and provides web pages to an HTTP client to obtain file transfer event parameters and identification of a remote file transfer client to which the file transfer event parameters are associated. The file transfer event parameters are stored in the file transfer tables in association with the identification of the remote file transfer client. The web services server comprising a plurality of transfer methods. The transfer methods comprises: i) a method for associating a remote transfer client with a session ID; ii) a method for providing to the remote transfer client the file transfer event parameters that are associated with the remote transfer client in response to receiving a method call from the remote transfer client; and iii) a method call for executing a file exchange with the remote transfer client in response to receiving a method call from the remote transfer client that includes the file transfer parameters.

Secure web server system for unattended remote file and message transfer

An automated invoice management system includes a network circuit for communicating invoice transactions with a plurality of client systems. The automated invoice management system receives an import invoice transaction compliant with a first client transaction definition from a first client system. The import invoice transaction identifies a second client system and amounts due from a second client system associated with the second client. The import invoice transaction is translated to a normalized invoice transaction and the normalized transaction is translated to an export invoice transaction compliant with a second client transaction definition.

Automated invoice receipt and management system

A financial transaction system consistent with the invention allows clients of a financial institution to use a web-based workstation to interface with a plurality of back office systems within one or more financial institutions. In an exemplary embodiment, a financial transaction system comprises a hub server, a plurality of financial institutions, at least one web server, and at least one database server. The hub server receives data in the form of a plurality of disparately formatted instructions and communicates the instructions to the financial institutions, which are connected to the hub server for receiving the data and have a plurality of differing reception formats to receive the reformatted data. Data is transmitted between the web server and at least one user via a network interface, and between the web server and the hub server. The web server stores data and at least one application in an application database. Data is transmitted between the database server, the hub server, and the web server, and is stored in a hub database. The hub server maps data received from the financial institutions and loads it onto the hub database. The web server receives the mapped data from the hub database, transmits it onto the application database, and permits the user to manipulate it using the application. In another exemplary embodiment, a method of executing a financial transaction consistent with the present invention comprises the steps of receiving into an application database an instruction to execute a financial transaction from at least one user using an application, receiving the instruction into a hub database, reformatting the instruction, and routing the reformatted instruction to at least one financial institution.

Growing community of inventors

Rye, NH, United States of America

Eric Campbell