The invention relates to a method and system for group based transactions. More particularly, the invention relates to a method and system for authorizing a transaction or activity by one or more members of a group of mobile users.

BACKGROUND

Existing cellular or wireless communication systems provide limited group capabilities that typically include email, chat and conference calls. However, such systems do not provide for the formation of a group of mobile users. Moreover, existing systems do not allow for group decisions in the authorization and the execution of tasks. Grouping of mobile user's is a great way to view, coordinate, share, conduct, and authenticate transactions in a peer-driven manner. Unfortunately, only limited group capabilities are supported on mobile devices.

While mobile commerce and mobile banking are desirable tools, there exists security concerns in the execution of such transactions, and instances of fraud in mobile-based transactions are a constant concern. Banks and other financial institutions are still exploring the use of mobile commerce to allow their customers to conduct transactions, e.g. purchasing products and services, remitting money via mobile phones and other forms of mobile commerce. Conventional systems provide for authentication of a single mobile user which may not be fully secure and may lead to fraudulent transactions.

BRIEF DESCRIPTION OF DRAWEVGS

The following is a brief description of the preferred embodiments with reference to the accompanying drawings. It is to be understood that the features illustrated in and described with reference to the drawings are not to be construed as limiting of the scope of the invention. In the accompanying drawings:

Figure 1 is a schematic illustration of a group transaction system in accordance with an embodiment of the invention.

Figure 2a illustrates a message format for creation of a group in accordance with an embodiment of the invention.

Figure 2b illustrates an 'add member' message format sent by the transaction system in accordance with an embodiment of the invention.

Figure 2c illustrates an 'add member response' to the transaction system in accordance with an embodiment of the invention.

Figure 2d illustrates a message format for 'Add group' sent by the transaction system to the mobile client in accordance with an embodiment of the invention.

Figure 2e shows a message format for the 'Add group response' sent by the mobile client in accordance with an embodiment of the invention.
Figure 3 illustrates a menu flow of creating and managing a group by way of a specific example in accordance with an embodiment of the invention.

Figure 4 illustrates a message format for deleting a group in accordance with an embodiment of the invention.

Figure 5 illustrates a way to create a group through a web link in accordance with an embodiment of the invention.

Figure 6 illustrates a menu flow of creating and managing group task/activity in accordance with an embodiment of the invention.

Figure 7 illustrates a way of adding a group task/activity from a mobile client in accordance with an embodiment of the invention.

Figure 8 illustrates a way of creating a group task/activity by a mobile user in accordance with an embodiment of the invention.

SUMMARY

A transaction system for authorizing a transaction is disclosed. The transaction system comprising a contents database configured to store details of a group of users, such user
details including a mobile communication identifier for each member of the group. The transaction system further comprising a transaction database for storing transaction details for the group of users, such transaction details including details of transactions completed and pending. The transaction system further comprising a mobile interface configured to communicate with a plurality of mobile communication devices and a transaction processor operatively communicating with the contents database, the transaction database and the mobile interface wherein the transaction system configured to receive a transaction authorization request from a mobile communication device of a user, the user a member of the group of users, transmit the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received and authorize the transaction at the transaction system on receiving transaction approval from such other member.

In accordance with an aspect, the transaction system receives a transaction authorization request from a mobile communication device of a user. The user is a member of a group of users registered with the transaction system, such registration including a mobile communication identifier for each member of the group. The transaction request is transmitted for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received. The transaction is authorised at the transaction system on receiving transaction approval from such other member.

DETAILED DESCRIPTION

For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

It will be understood by these skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the invention and are not intended to be restrictive thereof throughout the patent specification, a convention employed is that in the appended drawings, like numerals denote like components.

Reference throughout this specification to "one embodiment" "an embodiment" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in one embodiment', "in an embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

The invention relates to a system and method for group transactions wherein a plurality of mobile users may form a group. Tasks to be executed by the group may be authorized by one or more members of the group depending on the desired authority and clearance of each user.

A task may be initiated by any member of the group. A task may be created by a member of the group or can be pushed by a third-party server over the air to the mobile device of the user. A task so initiated may require authentication from other group members. On receiving authentication from one or more group members, the task may be authorized.

A third-party may be an independent institution facilitating transactions over a communication channel. A third-party may be linked with a transaction system, to authenticate and verify users and transactions on behalf of the third-party.

Figure 1 illustrates a group transaction system in accordance with an embodiment. The group transaction system includes a contents database, a transaction database, a switch, a mobile interface, and a transaction processor. The contents database, transaction database, and the mobile interface are controlled by the transaction processor. A mobile client is in communication with the group transaction system.

A mobile client may be present on the mobile device of the user or reside in a SIM card. The mobile client is in communication with the group transaction system for upgrades, alerts and processing of these transactions. In accordance with an embodiment, the mobile device of the user is equipped with a mobile client and adapted to receive and display data contents such as web pages, applets, menus, etc. The mobile client may be an application software or a web browser or dynamic menus built specifically for mobile devices. The mobile client can be downloaded from the World Wide Web or may be provided as functionality on the SIM card or can be pushed by the group transaction system (i.e. server) onto the mobile device of the user.

In accordance with an aspect, the mobile client is a small application and may be easily stored on the SIM card or the storage area of the mobile device and may be provided with interfaces for the operating system of the mobile device.

The mobile client enables seamless communication between the mobile device and the group transaction system regardless of underlying Communications protocols. The group transaction system can identify mobile device capabilities and can cause data contents to be adapted to accommodate display and input limitations of mobile device.

In accordance with an embodiment, the mobile client also provides an advanced, customized searching capability. Searches of various types can be executed including searches based on keywords, names, local context relevant to the person conducting the search, categories, and so on. The mobile client may be linked to the World Wide Web to enable the searching capabilities of the mobile user.

The content database holds details of the mobile user and the groups. These details include name of the mobile user, mobile number of the user, name of the group, number of members in group, etc.

The transaction database holds details of the transaction for a group of mobile users. These details include nature of transaction, number of users authenticated, creator of the transaction, status, etc.

Transaction Processor of the group transaction system manages the transaction with the mobile users and other entities. Transaction processor processes the requests from the mobile users to create a group. Transaction Processor is responsible for all the processing of any transaction or activities generated by the mobile users. Transaction processor is in communication with the mobile client via a Mobile Interface

The Mobile Interface may include a security protocol that performs security related and data integrity related checks on the content and transaction details. The security protocol may be SSL (Secure Socket Layer), TLS (Transport Layer Security), PPP (Point-to-Point protocol) or any other protocol known in the art.

In order to create a group, the mobile user invokes the mobile client on his mobile device. The mobile user may create a group of other mobile user's. The mobile user request to create a group may include some inputs or parameters. The inputs or parameters may include a group name, number of users, name and phone numbers of each users, financial instrument details, etc. After filling all the required details, the inputs or parameters are checked by the Mobile Interface and passed to the transaction processor for execution. The transaction processor creates a group and stores the details of the group including the inputsand parameters in the Contents Database. The new group will be displayed in the mobile client residing in the mobile device of the user.

The Group Transaction System will inform all the proposed members of the group about formation of a new group. A request will be sent by the Transaction Processor to the proposed members of the group via an SMS. The proposed members may or may not accept this invitation. After a few or all of the proposed users have accepted this invitation, the Transaction processor will execute the updates and store this Information in the Contents Database. The transaction processor will automatically add a new group on the mobile client on the mobile phone of the newly added members.

The proposed members may have to enter a security password or in another way authenticate their identity (e.g. biometric authentication) in order to accept/decline the invitation of a new group.

A password is an input secret entry, such as an alphanumeric string that is used for authentication transaction by the mobile user. The password may be a 4 digit or more digit personal Identification number, a security code, biometric Information of the user or any combination thereof A password may be generated for each member of the group during registration.

The members of the group may access the menus or the browser on the mobile client and initiate a group transaction or activity. Any member of the group may initiate the transaction or activity. As the transaction or activity is invoked, the mobile client sends the request to the Transaction Processor via Mobile Interface. The transaction processor processes the request and sends an alert generally in form of an SMS to all the members of the group, informing them about a new transaction or activity. The other members of the group may have to accept or decline this invitation of a group transaction. The transaction may or may not include due dates, expiry dates, etc.

The transaction processor may manage the status of the transaction or activity. The status of the transaction may be 'pending' or 'completed' or 'drenched'. The status of the transaction may be 'pending', if some or all users of the group are still to either authorize or decline this activity. The status of the transaction may be 'completed', if all the users or some users have either authorized or declined the group transaction. The status of the transaction may be considered 'declined', if one or more users have declined the group transaction.

The transaction processor records the details of the transaction in the transaction database. The transaction processor may send an authentication request to the mobile device of the members of the group via the mobile interface. The authentication request may be in the form of a SMS. The members may enter their password number or any other security code (which the mobile users have registered with the third-party) to authenticate the group transaction or activity. The password may be verified by the mobile client or the group transaction system. The transaction processor verifies authenticity of response entered by the members of the group and authorizes a group transaction or activity. The transaction processor records the details of the transaction in the transaction database.

The transaction or activity may be a financial transaction or may be an activity or a task such as a newsletter sign-up, an online blog, a brochure request, a poll, loan approval, sending wishes like flowers, gifts, payment of bills, etc.

In accordance with an embodiment, a method of authenticating and authorizing ownership of a mobile user is described. A mobile user registers a financial instrument with a transaction system and submits the instrument details such as the card number, date of expiry, card verification code and/ or any password of their choice. This financial instrument is to be linked to a mobile communication identifier such as but not limited to a mobile phone number. The details of such a mobile device are also provided by the user to the transaction system.

In accordance with an embodiment, a method of authenticating a financial transaction by more than one member of the group is discussed. In case of a financial transaction, after the Transaction System has successfully verified the transaction, the Transaction processor sends an SMS to all the members of the group confirming the new transaction and asking for an authentication of the new transaction. The members may enter their password or security code on their mobile device or otherwise authenticate their identity (e.g. biometric authentication) to authorize the transaction. The mobile client or the transaction system may perform some checks on the password. The transaction processor may match the password with the name of the user and their mobile number and once successfully matched; the transaction processor stores the Information about the successful transaction in the transaction database. The transaction processor informs the financial institution, such as a bank, about a successful verification and transaction via the switch.

The switch communicates between the Group Transaction System and the financial institution. The switch may check the data integrity of the sensitive information being passed onto the financial institution.

The financial institution charges the financial instrument and issues a payment authorisation and sends it back to the switch that in turn forwards the status of the payment authorisation to the transaction processor. The transaction processor processes the payment authorisation and if successful, informs the members of the group about the successful transaction.

By way of a specific example, the method of creating a group by mobile client is described. The mobile user may access the mobile client on his mobile device and may create a group by accessing My Group-> Create Group and enter the group Name, number of members in that group. Then an SMS is sent to the transaction system requesting creation of a group. Figure 2a illustrates a message format for creation of a group. The mobile user may provide details such as group name and number of members in the group. The mobile client may add details to the response sent by the mobile user such as server ID (SID), Application Version number (AVN), Transaction Identifier (TID), Key Version (KV) and Checksum (CHKSUM) and send it to the transaction system.

The server ID (SID), Application Version number (AVN), Transaction Identifier (TID), Key Version (KV) and Checksum (CHKSUM) are headers of the message format. They are internally added by the mobile client.

The transaction system then creates a dynamic byte code menu based on the details sent by the mobile user. Figure 2b illustrates an 'Add Member' message format sent by the transaction system in a dynamic menu format. This message may ask the mobile user to provide details of the names and phone numbers of the proposed members of the group.

Figure 2c illustrates an 'Add Member Response' message sent by the mobile user. This message may include name and phone number of the first member, name and phone number of the second member, and so on.

The mobile client may add details to the response sent by the mobile user such as server ID (SID), Application Version number (AVN), Transaction Identifier (TID), Key Version (KV) and Checksum (CHKSUM) and send it to the transaction system. Once the transaction system receives the 'Add Members Response' message, the transaction system then sends an 'Add Group' message to the mobile client that adds a group to its group list storage space.

Figure 2d illustrates a message format for 'Add group' sent by the transaction system to the mobile client. This message will save or create the group on the mobile client.

Figure 2e shows a message format for an 'Add Group Response' sent by the mobile client to the transaction system. The transaction system may execute the response and store in its database (may include the following details such as server ID (SID), Application Version number (AVN), Transaction Identifier (TID), Key Version (KV) and Checksum (CHKSUM)).The mobile users may see the Group "name" by viewing My Group → View Group.

Figure 3 illustrates a menu flow of creating and managing a group by way of a specific example. The menu shows the step wise process to create a group. The menu also provides for viewing the groups. When user select the My group→view group option, the mobile client shows the list of group already added. Once the mobile user clicks on one of the group present in the list, a display text with the list of members added is shown on the screen.

The mobile user may also have an access to a group services by accessing My Group→ Group Services. The mobile user can create and manage group services and activities task with this option.

The mobile user may delete the groups added/configuration on the mobile client by clicking, My Group ^Delete Groups. Figure 4 illustrates the message format for deleting a group. The group may get deleted by sending an SMS with the Group Name to the transaction system. The mobile client may add details to the response sent by the mobile user such as server ID (SID), Application Version number (AVN), Transaction Identifier (TID), Key Version (KV) and Checksum (CHKSUM) and send it to the transaction system. The transaction system replies with the plain text SMS that the group "name" is successfully deleted. The group may be deleted either by the creator of the group, one or all members of the group.

In accordance with an alternate embodiment of the invention, the mobile users may create a group by a User Interface on a web link or a web page. Figure 5 illustrates a way to create a group through a web link or a web page. The mobile user logs on to the web link or web page and requests to add a group. The 'Add group' requests goes to the transaction system for processing and the transaction system updates the mobile client on the mobile device of the user. The transaction system responds to the 'add group' request by a message that is shown on the user interface on the web link or web page .

The mobile user can manage the group on the user interface on the web link or web page and can also manage the service which he wants to add to My Group. The mobile user may also create customized group services on the web link.

In accordance with an alternate embodiment of the invention, merchants and smaller institutions that need group authentication may create a group from the transaction system directly through the mobile client on their mobile devices. The mobile user may send a simple SMS to add a group. This message may be a simple SMS with the details of the group for e.g. group name, name and phone numbers of members, etc.

In accordance with an embodiment of the invention, the mobile user can create and manage a task or activity by selecting My Group-Group Services. Figure 6 illustrates a menu for creating and managing group tasks or activities. The 'group services' option may consist of the list of tasks or activities available, the 'create services' option, list of tasks or activities already enrolled by the mobile user, managing these tasks or activities, etc. The mobile user may use 'what's new' option to check the available tasks or activities for group task or activity. The mobile users may click on 'create service' option to create a customized group task/activity.

Figure 7 illustrates a way of adding a group task or activity from the mobile client. The mobile user may add a group task or activity by clicking on My Group→Group Service-→what's new. This option displays the pre defined tasks or activities on the network available for group task or activity. The mobile user sends a request SMS to the transaction system. The transaction system creates a Dynamic byte code message containing the list of available tasks or activities and sends it to the mobile client by SMS. The mobile user selects an appropriate task or activity and sends a request. The transaction system responds to the request by adding the requested task or activity. The mobile user may request for the task or activity again, if the access was denied in previous attempts.

Figure 8 illustrates a way of creating a group task or activity by a mobile user. The mobile user may create a group task or activity by clicking on My Group→Group Service→Create Service. This option helps the mobile user to create a task or activity and define its work flow. The mobile user sends a request SMS to the transaction system. The transaction system creates a Dynamic byte code message and sends it to the mobile user by SMS. The mobile user defines the task or activity and decides the sequence of events of the task or activity and sends the request. The transaction system responds to the request by creating the requested task or activity. The mobile user can request for the creation of the task or activity again, if the creation was denied in previous attempts.

The newly added task or activity may be viewed by clicking on My Group→ Group Service→ Task 'number' or 'name'. The mobile user can select the task or activity that the user wishes to execute and follow the sequence of events for the task or activity. For example, if the task is to send a SMS to all in the fliend list of the user. The user will select the service → enter his message → select the group → send SMS.

Once the task or activity is added, the delete option will appear for that task or activity. The mobile user can click on the delete option to delete the selected task/activity.

The transaction may be a task to be executed. In accordance with an embodiment, a task is generated by the user on the mobile client. A task may include some parameters such as task ID, an alert, status, task details, etc. Such parameters may be set by the user, may be provided to the user by the mobile client, or may be partly provided to the user by the mobile client. The user may define some of the parameters of the task like task details, alert, time of action etc. The remaining parameters like status, task ID, etc are set by the mobile client. The alert may include a date or time or other parameters by which a task may be triggered. The task details include details regarding the nature of the task, the steps to be executed and the method or mode of execution of the task. For example, in the case of payment of a bill, the task details may include the biller, the bill number, the amount due, the last date of payment, financial instrument to be used for payment of bill, etc.

On receiving details for a task desired to be generated by the user, the mobile client may send a request to the Transaction System to generate an executable code for the task. The parameters are checked by the Mobile interface and passed to the Transaction Processor. The Transaction Processor processes the request and may keep a copy of the task details in the Transaction Database.

The Transaction system generates the executable code for the task, and sends the executable code to the mobile client. The mobile client stores the code to generate a task on the mobile client. After generation, the task and its details are available on the mobile client of the mobile device. The task details may be stored in the mobile client or any location in the memory of the mobile device.

The user may modify or manage the task details (those defined by the mobile user) on the mobile client without requiring an update from the Transaction System. For example, a task may be defined by the user on the mobile client to pay a bill. The mobile client may store the task details including the biller, card, amount of bill, etc. The user could change the card/account they want to pay a bill with on the mobile client without communicating with the Transaction System. This creates more ease and flexibility for the user to update the task details rather than a system that stores the task details on the Transaction System.

The mobile client monitors the tasks and informs the user on the mobile device about an event (like due date for a task, etc) by means of an alert. An alert may be an alarm or a message activated by the mobile client on a pre-defined date or time for informing the user about the task. The user can change the date and time of the alert on the mobile client.

Alerts can be defined by the mobile user on the mobile client or the Transaction system. An alert may be configured to invoke a task or an alert may include action instructions such that, the alert may direct the mobile client or the Transaction System or a third-party to perform a task. The alert may remind the mobile user of a pending task nearing its due date and may also include an executable instruction for the transaction. By way of example, in case of the alert defined by a third-party for the payment of a bill, an Interactive alert may be generated that may guide the user in executing the task. The alert message may inform the user about an un-paid bill, and on receiving an indication for payment, may ask the mobile user to select the card for payment, etc. After the user has selected the card, the message may ask the mobile user to click on a 'PAY' button to confirm the transaction, post which payment instruction may pass from the Transaction System to the third-party for execution. The third-party executes the payment instruction and informs the Transaction System about a successful payment. The Transaction System informs the mobile client of a successful payment and the mobile client may remove the task from the 'pending task' inbox. The completed task may be stored in the memory of the mobile client.

All created tasks may be stored in the mobile client. The pending tasks may be in a separate 'pending tasks' inbox. The completed tasks may be kept in the 'completed tasks' inbox or moved to the history of the mobile client. The user may also log onto the 'pending task' inbox and execute a task. Alliteratively, the user may set an alert for reminding the user about the pending tasks.

According to an embodiment, storing task data on the mobile client may have some security benefits. The user can only view or modify the task data upon successful authentication. The mobile client may ask the user for a PASSWORD to view or modify the task details. After providing the PASSWORD, the user can view or change the details of the task.

In accordance with an alterative embodiment, a third-party may also send a pre-defined task including an alert to a mobile client via a Transaction System. The third-party sends the task to the Transaction System and then the Transaction System pushes the task to the mobile client on the mobile device.

The mobile device is any device used for communication over a wireless communication network and includes a mobile phone, a smart phone, a Personal Digital Assistant (PDA) or a pager. The mobile communication identifier is a mobile number or a mobile device number.

SPECIFIC EMBODIMENTS ARE DESCRIBED BELOW

A method of authorizing a transaction at a transaction system comprising receiving at the transaction system a transaction authorization request from a mobile communication device of a user, the user a member of a group of users registered with the transaction system, such registration including a mobile communication identifier for each member of the group, transmitting the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received and authorizing the transaction at the transaction system on receiving transaction approval from such other member.

Such method(s) of authorizing a transaction at a transaction system, wherein the request for approval of transaction is transmitted to all members of the group other than the member from which the transaction authorization request is received.

Such method(s) of authorizing a transaction at a transaction system, further comprising authorizing the transaction at the transaction system on receiving transaction approval from at least one member to which the request for approval of transaction is transmitted.
Such method(s) of authorizing a transaction at a transaction system, further comprising generating a password for each member of the group during registration of the group of users.

Such method(s) of authorizing a transaction at a transaction system, further comprising authorizing the transaction at the transaction system on receiving transaction approval from least one member to which the request for approval of transaction is transmitted when such transaction approval is confirmed with the password for such member.

Such method(s) of authorizing a transaction at a transaction system, further comprising registering a financial instrument for conducting financial transactions for the group of users,

Such method(s) of authorizing a transaction at a transaction system, further comprising transmitting details of the financial instrument to a financial institution for executing the transaction after authorizing the transaction at the transaction system.

Such method(s) of authorizing a transaction at a transaction system, further comprising receiving details of the transaction created by a member of the group of users using a
crier application on the mobile communication device of the user.

Such method(s) of authorizing a transaction at a transaction system, further comprising receiving details of the transaction created by a third party system and transmitting transaction details to at least one member of the group of users.

Such method(s) of authorizing a transaction at a transaction system, further comprising transmitting to all members of the group the transaction details received from a third part system for a member of the group.

Such method(s) of authorizing a transaction at a transaction system, wherein the moil communication identifier is a mobile number or a mobile device number.

Such method(s) of authorizing a transaction at a transaction system, further comprising generating an executable code for the transaction and transmitting the executable code to the mobile communication device of the user.

Such method(s) of authorizing a transaction at a transaction system, flirter comprising generating a transaction and transmitting the transaction details to at least one member of the group of users.

FURTHER SPECIFIC EMBODIMENTS ARE DESCRIBED BELOW

A transaction system comprising a contents database configured to store details of a group of users, such user details including a mobile communication identifier for each member of the group, a transaction database for storing transaction details for the group of users, such transaction details including details of transactions completed and pending, a mobile interface configured to communicate with a plurality of mobile communication devices and a transaction processor operatively communicating with the contents database, the transaction database and the mobile interface wherein the transaction system configured to receive a transaction authorization request from a mobile communication device of a user, the user a member of the group of users; transmit the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received; and authorize the transaction at the transaction system on receiving transaction approval from such other member.

Such transaction system(s), configured to transmit via the mobile interface the request for approval of transaction to all members of the group other than the member from which the transaction authorization request is received.

Such transaction system(s), further configured to authorize the transaction at the transaction system on receiving via the mobile interface transaction approval from at least one member to which the request for approval of transaction is transmitted.

Such transaction system(s), further configured to generate a password for each member of the group during registration of the group of users and to store the password in the contents database.

Such transaction system(s), further configured to authorize the transaction at the transaction system on receiving via the mobile interface transaction approval from at least one member to which the request for approval of transaction is transmitted when such transaction approval is confirmed with the password for such member.
Such transaction system(s), further configured to register a financial instrument for conducting financial transactions for the group of users and to store the financial instrument in the contents database.

Such transaction system(s), further comprising a switch to transmit details of the financial instrument to a financial institution for executing the transaction after authorizing the transaction at the transaction system.

Such transaction system(s), further configured to receive via the mobile interface details of the transaction created by a member of the group of users using a client application on the mobile communication device of the user and to store the transaction details in the transaction database.

Such transaction systems(s), further comprising a third party interface configured to receive details of the transaction created by a third party system, store transaction details in the transaction database and transmit via the mobile interface transaction details to at least one member of the group of users.

Such transaction system(s), further configured to transmit via the mobile interface to all members of the group the transaction details received from a third party system for a member of the group.

Such transaction system(s), further configured to general executable code for the transaction and transmitting the executable code to the mobile communication device of the user.

Such transaction system(s), configured to generate a transaction and transmit the transaction details to at least one member of the group of users.

A mobile client system for a mobile communication device comprising an interface configured to communicate with a mobile interface of a transaction system, the transaction system comprising a contents database configured to store details of a group of users, such user details including a mobile communication identifier for each member of the group, a transaction database for storing transaction details for the group of users, such transaction details including details of transactions completed and pending, a mobile interface configured to communicate with a plurality of mobile communication devices; and a transaction processor operatively communicating with the contents database, the transaction database and the mobile interface wherein the transaction system configured to receive a transaction authorization request from a mobile communication device of a user, the user a member of the group of users; transmit the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received and authorize the transaction at the transaction system on receiving transaction approval from such other member, the mobile client configured to create a transaction, store a transaction and to receive transactions from the transaction system.

While specific language has been used to describe the invention, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the system in order to implement the inventive concept as taught herein.

WE CLAIM:

1. A method of authorizing a transaction at a transaction system comprising:

receiving at the transaction system a transaction authorization request from a mobile
communication device of a user, the user a member of a group of users registered with the transaction system, such registration including a mobile communication identifier for each member of the group;

transmitting the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received; and

authorizing the transaction at the transaction system on receiving transaction approval from such other member.

2. A method of authorizing a transaction at a transaction system as claimed in claim 1 wherein the request for approval of transaction is transmitted to all members of the group other than the member from which the transaction authorization request is received.

3. A method of authorizing a transaction at a transaction system as claimed in claim 2 further comprising authorizing the transaction at the transaction system on receiving transaction approval from at least one member to which the request for approval of transaction is transmitted.

4. A method of authorizing a transaction at a transaction system as claimed in claim 1 further comprising generating a password for each member of the group during registration of the group of users.

5. A method of authorizing a transaction at a transaction system as claimed in claim 4 further comprising authorizing the transaction at the transaction system on receiving transaction approval from at least one member to which the request for approval of
transaction is transmitted when such transaction approval is confirmed with the password for such member.

6. A method of authorizing a transaction at a transaction system as claimed in claim 1 further comprising registering a financial instrument for conducting financial transactions for the group of users.

7. A method of authorizing a transaction at a transaction system as claimed in claim 6 further comprising transmitting details of the financial instrument to a financial institution for executing the transaction after authorizing the transaction at the transaction system.

8. A method of authorizing a transaction at a transaction system as claimed in claim 1 further comprising receiving details of the transaction created by a member of the group of users using a client application on the mobile communication device of the user.

9. A method of authorizing a transaction at a transaction system as claimed in claim 8 further comprising generating an executable code for the transaction and transmitting the executable code to the mobile communication device of the user.

10. A method of authorizing a transaction at a transaction system as claimed in claim 1 further comprising receiving details of the transaction created by a third party system and transmitting transaction details to at least one member of the group of users.

11. A method of authorizing a transaction at a transaction system as claimed in claim 1 further comprising generating a transaction and transmitting the transaction details to at least one member of the group of users.

12. A method of authorizing a transaction at a transaction system as claimed in claim 10 or 11 further comprising transmitting to all members of the group the transaction details.

13. A transaction system comprising:

a contents database configured to store details of a group of users, such user details including a mobile communication identifier for each member of the group;

a transaction database for storing transaction details for the group of users, such transaction details including details of transactions completed and pending;

a mobile interface configured to communicate with a plurality of mobile communication devices; and

a transaction processor operatively communicating with the contents database, the transaction database and the mobile interface;

wherein the transaction system configured to receive a transaction authorization request from a mobile communication device of a user, the user a member of the group of users; transmit the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received; and authorize the transaction at the transaction system on receiving transaction approval from such other member.

14. A transaction system as claimed in claim 13 configured to transmit via the mobile interface the request for approval of transaction to all members of the group other than the member from which the transaction authorization request is received.

15. A transaction system as claimed in claim 14 further configured to authorize the transaction at the transaction system on receiving via the mobile interface transaction approval from at least one member to which the request for approval of transaction is transmitted.

16. A transaction system as claimed in claim 13 further configured to generate a password for each member of the group during registration of the group of users and to store the password in the contents database.

17. A transaction system as claimed in claim 16 further configured to authorize the transaction at the transaction system on receiving via the mobile interface transaction
approval from at least one member to which the request for approval of transaction is transmitted when such transaction approval is confirmed with the password for such member.

18. A transaction system as claimed in claim 13 further configured to register a financial instrument for conducting financial transactions for the group of users and to store the financial instrument in the contents database.

19. A transaction system as claimed in claim 18 further comprising a switch to transmit details of the financial instrument to a financial institution for executing the transaction after authorizing the transaction at the transaction system.

20. A transaction system as claimed in claim 13 further configured to receive via the mobile interface details of the transaction created by a member of the group of users using a client application on the mobile communication device of the user and to store the transaction details in the transaction database.

21. A transaction system as claimed in claim 20 further configured to generate executable code for the transaction and transmitting the executable code to the mobile communication device of the user.

22. A transaction system as claimed in claim 13 further comprising a third party interface configured to receive details of the transaction created by a third party system, store transaction details in the transaction database and transmit via the mobile interface transaction details to at least one member of the group of users.

23. A transaction system as claimed in claim 13 configured to generate a transaction and transmit the transaction details to at least one member of the group of users.

24. A transaction system as claimed in claim 22 or 23 further configured to transmit via the mobile interface to all members of the group the transaction details received from a third party system for a member of the group.

25. A mobile client system for a mobile communication device comprising an interface configured to communicate with a mobile interface of a transaction system, the transaction system comprising a contents database configured to store details of a group of users, such user details including a mobile communication identifier for each member of the group; a transaction database for storing transaction details for the group of users, such transaction details including details of transactions completed and pending; a mobile interface configured to communicate with a plurality of mobile communication devices; and a transaction processor operatively communicating with the contents database, the transaction database and the mobile interface;

wherein the transaction system configured to receive a transaction authorization request from a mobile communication device of a user, the user a member of the group of users; transmit the transaction request for approval to at least one member of the group of users, such at least one member being a member other than the member from which the transaction authorization request is received; and authorize the transaction at the transaction system on receiving transaction approval from such other member;

the mobile client configured to create a transaction, store a transaction and to receive transactions from the transaction system.

26. A method of authorizing a transaction at a transaction system substantially as herein described with reference to and as illustrated by the accompanying figures.

27. A transaction system substantially as herein described with reference to and as illustrated by the accompanying figures.