System and method for electronically facilitating, recording, and tracking transactions

• US 20070208816A1
• Filed: 02/02/2007
• Published: 09/06/2007
• Est. Priority Date: 02/03/2006
• Status: Abandoned Application

• Current Assignee: CIBERNET Corp. (Syniverse Corp.)
• Original Assignee: CIBERNET Corp. (Syniverse Corp.)
• Inventors: Lustgarten, Paul, Potter, David, Hansen, Kenneth, Baldwin, Michael, Orellana, Uriel, Sorace, Anthony
• Application Number:
  US11/701,532
• Publication Number:
  US 20070208816A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04L 12/1831 Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]

Abstract

A method to facilitate a transaction using an instant messaging client comprising, receiving a formatted transaction request from the client via a messaging protocol, identifying a recipient and transaction information, facilitating the transaction and sending a notification of completion of the transaction via the messaging protocol.

Claims

1. A method for processing a transaction initiated using a messaging client, comprising:

receiving a request in an intermediate protocol identifying a recipient and including transaction information, wherein the request originates from the messaging client in a messaging protocol supported by the messaging client and is translated into the intermediate protocol by an interface;

sending a confirmation request to the messaging client, via the interface, wherein the confirmation request includes a request for confirmation of the requested transaction and wherein the confirmation request is translated by the interface from the intermediate protocol into the messaging protocol supported by the client;

facilitating the requested transaction in response to a confirmation of the requested transaction; and

sending notification of completion of the requested transaction to the messaging client, via the interface, wherein the notification is translated by the interface from the intermediate protocol to the messaging protocol supported by the messaging client.

2. The method of claim 1, further comprising determining whether the recipient has an account.

3. The method of claim 2, further comprising notifying the recipient that an account must be created prior to completion of the transaction.

4. The method of claim 1, wherein the messaging protocol is an instant messaging protocol.

5. The method of claim 1, wherein the intermediary protocol is encoded text over internet protocol.

6. The method of claim 1, wherein the intermediary protocol is Unicode text over internet protocol.

7. The method of claim 1, wherein the receiving a request and sending confirmation steps are performed via an instant messaging protocol and the sending notification step is performed via e-mail.

8. The method of claim 1, wherein the receiving request and sending confirmation steps are performed via a Short Message Service (SMS) messaging protocol and the sending notification step is performed via electronic mail (e-mail).

9. The method of claim 1, wherein the messaging client is one of an instant messaging client or a Short Message Service (SMS) client.

10. The method of claim 1, wherein the messaging client includes one of a buddy list or a contact list.

11. The method of claim 1, wherein the messaging client is an instant messaging client, the messaging protocol is an EXtensible Messaging and Presence Protocol (XMPP) and the intermediate protocol is an American Standard Code for Information Interchange (ASCII) Text Over Transmission Control Protocol/Internet Protocol (TCPIP).

12. The method of claim 1, wherein the messaging client is a Short Message Service (SMS) client, the messaging protocol is an SMS protocol and the intermediate protocol is an American Standard Code for Information Interchange (ASCII) Text Over Transmission Control Protocol/Internet Protocol (TCPIP).

13. The method of claim 1, the facilitating step further comprising interacting with a third party network to facilitate the transaction.

14. The method of claim 1, wherein the transaction is a financial transaction and includes a transfer of funds from a source account to a destination account.

15. The method of claim 14, wherein the financial transaction is one of a loan transaction, bill transaction, a voucher transaction or a tax payment transaction.

16. The method of claim 14, wherein the source and destination accounts include one or more of a bill pay sub-account, loan sub-account, voucher sub-account and tax sub-account.

17. A method to initiate a financial transaction using a messaging client, comprising:

receiving a financial transaction request, wherein the financial transaction request identifies a recipient and an amount of a transaction;

formatting the financial transaction request using the messaging client into a first format according to a messaging protocol and sending the formatted financial transaction request;

receiving a confirmation request for the financial transaction in the first format;

formatting the confirmation request using the messaging client into a Graphical User Interface (GUI) format and displaying the confirmation request;

receiving input corresponding to the confirmation request via the messaging client;

formatting the received input into the first format using the messaging client and sending the input to the confirmation request; and

receiving and formatting a notification of completion of the transaction in the GUI format and displaying the notification.

18. The method of claim 17, further comprising connecting to a server.

19. The method of claim 18, further comprising, receiving user identification information via a GUI, formatting user identification information into the first format and sending the formatted user identification information to the server for authentication.

20. The method of claim 17, wherein the messaging client is an instant messaging client and the first format is based on an EXtensible Messaging and Presence Protocol (XMPP).

21. The method of claim 17, wherein the messaging client is a Short Message Service (SMS) client and the first format is based on a Short Message Service (SMS) protocol.

22. A method to facilitate a transaction initiated using a messaging client, comprising:

receiving a transaction request in a first format according to a messaging protocol from the messaging client;

formatting the transaction request into a second format and sending the formatted request to an intermediary server;

receiving a notification of completion of transaction from the intermediary server in the second format;

formatting the notification in the first format and sending the formatted notification to the messaging client.

23. The method of claim 22, wherein the first format is based on an EXtensible Messaging and Presence Protocol (XMPP).

24. The method of claim 22, wherein the first format is based on a Short Message Service (SMS) protocol.

25. The method of claim 22, wherein the second format is an American Standard Code for Information Interchange (ASCII) Text Over Transmission Control Protocol/Internet Protocol (TCPIP) format.

26. The method of claim 22, further comprising receiving a confirmation request from the intermediary server in the second format.

27. The method of claim 26, further comprising formatting and sending the confirmation request to the messaging client in the first format.

28. The method of claim 27, further comprising receiving a response to the confirmation request from the client in the first format.

29. The method of claim 28, further comprising formatting and sending the confirmation request to the intermediary server in the second format.

30. A method to facilitate a transaction initiated using a messaging client, comprising:

receiving a message in a first format according to a messaging protocol from the messaging client;

determining whether the message is a transaction request; and

formatting the message into a second format, if the message is a transaction request, and sending the formatted request to an interface.

31. The method of claim 30, wherein the first format is an instant messaging protocol and the second format is encoded text over internet protocol.

32. The method of claim 30, further comprising receiving a message from a server in the first format and forwarding the message to the messaging client.

33. The method of claim 30, further comprising receiving a message from a server in the second format, formatting the message into the first format and forwarding the message to the messaging client.