Simplifying affiliated transactions through an auto-populating web page sub-window

• US 20060230135A1
• Filed: 04/12/2005
• Published: 10/12/2006
• Est. Priority Date: 04/12/2005
• Status: Abandoned Application

• Current Assignee: CollegeNET Incorporated
• Original Assignee: CollegeNET Incorporated
• Inventors: Houston, Ben C., Wolfston, James H.
• Application Number:
  US11/105,214
• Publication Number:
  US 20060230135A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A transaction web page method provides a transaction web page from a first server at a first service address to a user client computer where user-specific transaction information is incorporated into the web page in connection with a first transaction. A transaction sub-window is provided from the first service address in connection with a second transaction that is separate and distinct from the first transaction. The transaction sub-window is rendered adjacent to the transaction web page and is auto-populated with user-specific transaction information from the transaction web page. Upon user activation of the second transaction, transaction information for the second transaction is transmitted to a second server that is at a second service address that is different from the first server service address to provide processing of the second transaction

Claims

1. A transaction web page method for a transaction web page provided from a first server at a first service address to a user client computer where user-specific transaction information is incorporated into the web page in connection with a first transaction, the improvement comprising:

providing from the first service address a transaction sub-window in connection with a second transaction that is separate and distinct from the first transaction;

rendering the transaction sub-window adjacent to the transaction web page, the transaction sub-window being auto-populated with user-specific transaction information from the transaction web page; and

transmitting transaction information for the second transaction to a second server at a second service address that is different from the first service address to provide financial processing of the second transaction.

2. The method of claim 1 in which following user activation of the second transaction the transaction sub-window is closed and the user is automatically returned to the transaction web page with its user-specific transaction information.

3. The method of claim 1 in which the first server provides no financial processing of the second transaction with respect to the user-specific transaction information.

4. The method of claim 1 in which the second transaction includes a donation to a charitable organization.

5. The method of claim 4 further comprising providing the user a suggested amount for the second transaction.

6. The method of claim 1 in which the transaction sub-window is rendered to overlap at least a portion of the transaction web page.

7. The method of claim 1 in-which the transaction sub-window is auto-populated with user-specific transaction information that includes user financial information.

8. The method of claim 1 in which the transaction sub-window is auto-populated with user-specific transaction information that includes user identifying information.

9. The method of claim 1 in which the second server is operated by an application service provider on behalf of a separate entity that is a party to the second transaction.

10. In a computer readable medium, transaction web page software for a transaction web page provided from a first server at a first service address to a user client computer where user-specific transaction information is incorporated into the web page in connection with a first transaction, comprising:

software for providing from the first service address a transaction sub-window in connection with a second transaction that is separate and distinct from the first transaction;

software for rendering the transaction sub-window adjacent to the transaction web page, the transaction sub-window being auto-populated with user-specific transaction information from the transaction web page; and

software for transmitting transaction information for the second transaction to a second server at a second service address that is different from the first service address to provide processing of the second transaction.

11. The medium of claim 10 further comprising software for closing the transaction sub-window and returning the user to the transaction web page with its user-specific transaction information following user activation of the second transaction.

12. The medium of claim 10 in which the second transaction includes a donation to a charitable organization.

13. The medium of claim 10 further comprising software for providing the user a suggested amount for the second transaction.

14. The medium of claim 10 further comprising software for rendering the transaction sub-window to overlap at least a portion of the transaction web page.

15. The medium of claim 10 further comprising software for auto-populating the transaction sub-window with user-specific transaction information that includes user financial information.

16. The medium of claim 10 further comprising software for auto-populating the transaction sub-window with user-specific transaction information that includes user identifying information.

17. In a computer readable medium, transaction web page software for a transaction web page provided from a first server at a first service address to a user client computer in connection with a first transaction, comprising:

software for providing from the first service address a transaction sub-window in connection with a second transaction that is separate and distinct from the first transaction;

software for rendering the transaction sub-window adjacent to the transaction web page;

software for auto-populating the transaction sub-window or the transaction web page with user-specific transaction information that is incorporated into the transaction sub-window or the transaction web page, respectively;

software for transmitting transaction information for the first transaction to the first server; and

software for transmitting transaction information for the second transaction to a second server at a second service address that is different from the first service address to provide processing of the second transaction.

18. The medium of claim 17 further comprising software for rendering the transaction sub-window to overlap at least a portion of the transaction web page.

19. The medium of claim 17 further comprising software for closing the transaction sub-window and returning the user to the transaction web page with its user-specific transaction information following user activation of the second transaction.