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

1. A supplemental financial transaction processing system for operation with a primary financial services system and providing financial transaction processing services to a client system which has established a secure session with the primary financial services system, the supplemental financial transaction processing system comprising:

a web services description language document made available to the primary financial services system, the web services description language document defining a data schema required for a transaction request and including definition of primary system defined transaction values which must be provided by the primary financial services system in the transaction request;

a transaction request received from the primary financial services system, the transaction request including a data structure comprising:

a financial institution identifier, the financial institution identifier identifying the primary financial services system which initiated the transaction request; and

at least one primary system defined transaction value;

a secure web services system, the secure web services system, receiving the transaction request and in response to receiving the transaction request:

assigns a unique redirect URL to the transaction request, the unique redirect URL being an exposed URL of the supplemental financial transaction system;

stores, in a redirect database, in association with the unique redirect URL, the primary system defined transaction value; and

returns the unique redirect URL to the primary financial services system; and

a web document object comprising:

the at least one primary system defined transaction value;

at least validation value;

user interface control script, the user interface control script comprising instructions which render, on the client system, controls for obtaining user entry of at least one client defined transaction value; and

validation control script, the validation control script determining that the transaction is valid by executing at least one validation rule comprising comparing the result of a mathematic function of the client defined transaction value to the validation value; and

transaction control script, the transaction control script comprising instructions which:

a) create a financial transaction, the financial transaction comprising the at least one primary system defined transaction value and the at least one client defined transaction value; and

b) post the financial transaction back to the supplemental transaction server only if the transaction is valid;

a supplemental transaction server, the supplemental transaction server:

providing the web document object to the client system in response to receiving a secure connection by the client system at the unique redirect URL;

receiving a post of the financial transaction from the client system; and

performing 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.

2. The supplemental financial transaction system of claim 1 , in which:

the client defined transaction value is a client defined date;

the validation value represents a date on which the financial transaction is executable, and

the financial transaction is valid only if the client defined date is a date on which the financial transaction is executable.

3. The supplemental financial transaction system of claim 1 , in which:

the client defined transaction value is a beneficiary bank code;

the validation value represents a valid digit length for a bank code; and

the financial transaction is valid only if the beneficiary bank code is the valid digit length.

4. The supplemental financial transaction system of claim 1 , in which:

the client defined transaction value is a beneficiary bank code; and

the validation value represents a valid check digit value, and

the financial transaction is valid only if a check digit value of the beneficiary bank code matches the valid check digit value.

5. The supplemental financial transaction system of claim 1 , in which:

the secure web services system further defines a time period for which the unique redirect URL is valid; and

the supplemental transaction server provides the web document object only in response to receiving a secure connection at the unique redirect URL during the time period defined by the secure web services system.

6. The supplemental financial transaction system of claim 5 , in which:

the client defined transaction value is a client defined date;

the validation value represents a date on which the financial transaction is executable, and

the financial transaction is valid only if the client defined date is a date on which the financial transaction is executable.

7. The supplemental financial transaction system of claim 5 , in which:

the client defined transaction value is a beneficiary bank code;

the validation value represents a valid digit length for a bank code; and

the financial transaction is valid only if the beneficiary bank code is the valid digit length.

8. The supplemental financial transaction system of claim 5 , in which:

the client defined transaction value is a beneficiary bank code; and

the validation value represents a valid check digit value, and

the financial transaction is valid only if a check digit value of the beneficiary bank code matches the valid check digit value.

9. A method of operating a supplemental financial transaction server with a primary financial services server to provide financial transaction processing services to a client system which has established a secure session with the primary financial services system, the method comprising:

a processor executing software code within the supplemental financial transaction server to make a web services description language document available to the primary financial services server, the web services description language document defining a data schema required for a transaction request and including definition of primary system defined transaction values which must be provided by the primary financial services server in the transaction request;

a processor executing software code within the primary financial services server to generate a transaction request for transmission from the primary financial services server to the supplemental financial transaction processing server, the transaction request comprising:

a financial institution identifier, the financial institution identifier identifying the primary financial services system; and

at least one primary system defined transaction value;

a processor executing software code within the supplemental financial transaction processing server, in response to receiving the transaction request:

assigning a unique redirect URL to the transaction request, the unique redirect URL being an exposed URL of the supplemental financial transaction system;

storing, in a redirect database, in association with the unique redirect URL, the primary system defined transaction value; and

returning the unique redirect URL to the primary financial services server;

generating a web document object comprising:

the at least one primary system defined transaction value;

at least validation value;

user interface control script, the user interface control script comprising instructions which render, on the client system, controls for obtaining user entry of at least one client defined transaction value; and

validation control script, the validation control script determining that the transaction is valid by executing at least one validation rule comprising comparing the result of a mathematic function of the client defined transaction value to the validation value; and

transaction control script, the transaction control script comprising instructions which:

a) create a financial transaction, the financial transaction comprising the at least one primary system defined transaction value and the at least one client defined transaction value; and

b) post the financial transaction back to the supplemental transaction server only if the transaction is valid;

providing the web document object to the client system in response to receiving a secure connection by the client system at the unique redirect URL;

receiving a post of the financial transaction from the client system; and

performing 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.

10. The method of claim 9 , in which:

the client defined transaction value is a client defined date;

the validation value represents a date on which the financial transaction is executable, and

the financial transaction is valid only if the client defined date is a date on which the financial transaction is executable.

11. The method of claim 9 , in which:

the client defined transaction value is a beneficiary bank code;

the validation value represents a valid digit length for a bank code; and

the financial transaction is valid only if the beneficiary bank code is the valid digit length.

12. The method of claim 9 , in which:

the client defined transaction value is a beneficiary bank code; and

the validation value represents a valid check digit value, and

the financial transaction is valid only if a check digit value of the beneficiary bank code matches the valid check digit value.

13. The method of claim 9 , in which:

the secure web services system further defines a time period for which the unique redirect URL is valid; and

the supplemental transaction server provides the web document object only in response to receiving a secure connection at the unique redirect URL during a limited time period following receipt of the transaction request.

14. The method of claim 13 , in which:

the client defined transaction value is a client defined date;

the validation value represents a date on which the financial transaction is executable, and

the financial transaction is valid only if the client defined date is a date on which the financial transaction is executable.

15. The method of claim 13 , in which:

the client defined transaction value is a beneficiary bank code;

the validation value represents a valid digit length for a bank code; and

the financial transaction is valid only if the beneficiary bank code is the valid digit length.

16. The method of claim 13 , in which:

the client defined transaction value is a beneficiary bank code; and

the validation value represents a valid check digit value, and

the financial transaction is valid only if a check digit value of the beneficiary bank code matches the valid check digit value.