WO2017216672A1 - Method of providing a financial transaction - Google Patents
Method of providing a financial transaction Download PDFInfo
- Publication number
- WO2017216672A1 WO2017216672A1 PCT/IB2017/053285 IB2017053285W WO2017216672A1 WO 2017216672 A1 WO2017216672 A1 WO 2017216672A1 IB 2017053285 W IB2017053285 W IB 2017053285W WO 2017216672 A1 WO2017216672 A1 WO 2017216672A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- application programme
- financial transaction
- resource planning
- server
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 67
- 238000013439 planning Methods 0.000 claims abstract description 156
- 230000001105 regulatory effect Effects 0.000 claims description 8
- 238000012546 transfer Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 230000003993 interaction Effects 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 5
- 230000004044 response Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 8
- 238000003825 pressing Methods 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000002269 spontaneous effect Effects 0.000 description 2
- 230000001934 delay Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000035515 penetration Effects 0.000 description 1
- 230000002311 subsequent effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Each user makes use of a mobile device (1) including an resource planning application programme (ESAP) communicating over a network (3) with an first server (4) maintaining an first user database (5). The device of some of said users includes a financial transaction application programme (FTAP) communicating over a network with a second server (6) maintaining a second user database (7). A user of ESAP invites another user to participate in a group. A group member sets up an expense to be shared between group members. A settlement is initiated and the ESAP provides a summary of the due amounts among group members. The ESAP of a user which is also a user of the FTAP communicates with the second server which performs at least one financial transaction between said user and at least another user.
Description
METHOD OF PROVIDING A FINANCIAL TRANSACTION
The present invention relates to a method of settling a plurality of expenses among a plurality of users, whereby each user makes use of a respective mobile computing de- vice provided with a screen and including an resource planning application programme communicating over a network with an first server maintaining an first user database including identification details of a number of registered users of the resource planning application programme. US 2009/0327128 A1 discloses a system and method for managing allocation of funds between a plurality of entities. In example embodiments, details of a remuneration to the plurality of entities are received. The remuneration relates to at least one transaction. Funds associated with the remuneration are allocated among the plurality of entities to be remunerated based on at least a portion of the details of the remuneration. This sys- tern is not based on mobile computing devices.
US 2014/0108235 A1 discloses a system, method, and article of manufacture for settling payment. In various embodiments, the method may comprise creating a group comprising a plurality of transaction accounts associated with a shared financial obligation, and settling a plurality of records of charge (ROCs) corresponding to the shared financial obligation between each of the plurality of transaction accounts in the group. The method may further comprise transmitting one of a plurality of ROCs to a member associated with one of a plurality of transaction accounts in a group, and/or receiving an indication that one of the plurality of ROCs is subject to the shared financial obligation. Further, in various embodiments, the method may comprise creating a group in response to authentication of a plurality of members to a single web client, and/or creating the group in response to a group initiation event by a group initiator.
However, prior art systems and methods either do not offer the possibility to settle the shared expenses automatically by financial transactions or do require that all users have registered with a credit card or bank account for performing financial transactions. In the latter case, the general applicability and market penetration of such systems and methods are limited, because in many spontaneous situations, a random group of people will not be able to benefit from the system before one of more of the persons have registered with a credit card or bank account for performing financial transactions. Many people would prefer not to take the decision to perform such registration with their credit card
or bank account in a spontaneous situation, but would rather like to consider their choice later in a more quiet situation. A common situation could for instance be that a number of friends meet at a restaurant and want to split the bill. In this situation, if just one of the friends has not already registered with the system and does not want to do so sponta- neously, the group is prevented from using such a system.
The object of the present invention is to provide a more versatile method of settling a plurality of expenses among a plurality of users. The above object and advantages together with numerous other objects and ad-vantages, which will be evident from the description, are according to a first aspect obtained by:
A method of providing a financial transaction between a first financial account of a first user, and a second financial account of a second user,
the method comprising the steps of
providing a first mobile computing device, and a second mobile computing device, each of the first mobile computing device, and the second mobile computing device comprising a resource planning application programme and a financial transaction ap- plication programme,
the resource planning programme having a first security protocol for securing access to the resource planning programme, and the financial transaction programme having a second security protocol for securing access to the financial transaction programme, the first security protocol having a lower degree of security than the second security protocol,
the method further comprising the steps of
providing a first server for maintaining a first user database of registered users of the resource planning application programme,
providing a second server for maintaining a second user database of registered users of the financial transaction application programme, the second server being regulated by a financial regulatory authority,
the resource planning application programme communicating over a network with the first server for providing a substantially real-time text transmission between the first mobile computing device, and the second mobile computing device for determining an amount of money to be transferred between the first financial account and the second financial account in the financial transaction,
the resource planning application programme having a control element for initiating the financial transaction of the amount of money,
whereby upon user interaction with the control element the resource planning application programme calls the financial transaction application programme, and provides the amount of money as a string to the financial transaction application programme, the financial transaction application programme communicates over the network with the second server, and the second server transfers the amount of money between the first account and the second account. In this way a number of users may establish a messaging routine (thread of text strings), which circumvents the financial transaction application programme, and which is easier to gain access to, and which provides a faster communication between the users in order to more effectively determined an amount of money to be transferred between financial accounts of the users, i.e. a first user may send a text string to a second user and vice versa.
In the case that a server is regulated by a financial regulatory authority, the server is subject to comply with a directive defining certain security aspects of the server. These may be the physical location of the server, the physical access to the server, encryption level etc.
Substantially real-time text transmission means not withstanding inherent delays naturally occurring in a communication system such as mobile networks and the internet, i.e. from the time a transmission is transmitted from a first mobile computing device and until it is received by the second mobile computing device, not more than a minute has passed, preferably less than 30 seconds such as 15 seconds or 10 seconds or down to 5 seconds.
The resource planning application programme and the financial transaction application programme work together such that information is exchanged between the two. Only when an amount of money has been determined, is it necessary to provide access to the financial transaction programme in order to perform the financial transaction. The resource planning application programme works faster than the financial transaction application programme, but is not able to perform the financial transaction.
An application programme is to be understood in the usual sense of being a set of instructions stored in a memory and run as one or more instructions at a time in central processing unit. The financial transaction application programme may prompt a first user authentication in response to the resource planning application programme calling the financial transaction application programme.
The first user database constitutes a first backend server (a resource planning server), and it may comprise first user identification data including a user telephone number. The first user identification data may exclude a national identification number.
The second user database constitutes a second backend server (financial transaction server), and it may comprise second user identification data including an authentication string. The second user identification data may include a national identification number and/or the user telephone number.
The first security protocol may comprise prompting a second user authentication upon a first access to the resource planning application programme, and whereby a subse- quent access to the resource planning application programme being open.
The second user authentication may consist of the authentication string.
The first security protocol may comprise calling the financial transaction application pro- gramme for verifying the authentication string.
The first user identification data may be a subset of the second user identification data.
The first user identification data may be provided to the first server from the second server via the network.
The second security protocol may comprise a multi factor authentication.
The resource planning application programme may communicate with the first server with a first security level.
The financial transaction application programme may communicate with the second server with a second security level, the first security level being lower than the second security level. The first server having a first encryption level or the first server may be un-encrypted.
The second server may have a second encryption level, the first encryption level being lower than the second encryption level. The resource planning application programme may communicate with the first server at a first speed.
The financial transaction application programme may communicate with the second server at a second speed, the first speed being higher than the second speed.
The resource planning application programme may comprise a deadline for user interaction with the control element before the resource planning application programme deleting the amount of money having been determined by the resource planning application programme.
According to a second aspect of the invention, the respective mobile computing device of at least some of said users includes a financial transaction application programme communicating over a network with a second server maintaining a second user database including identification details of a number of registered users of the financial trans- action application programme, a registered user of the resource planning application programme invites by means of said programme at least one other registered user of the resource planning application programme to participate in an expense share group, at least one of said expense share group members sets up, by means of the resource planning application programme, an expense to be shared between at least some of said expense share group members, a settlement of expenses is initiated by means of the resource planning application programme by one of said expense share group members, the resource planning application programme of a user of the resource planning application programme provides a settle up summary of the respective due amounts to be paid or received by the respective expense share group members, and the resource planning application programme of at least one user which is also a user of the financial
transaction application programme communicates with the second server which performs at least one financial transaction between said user and at least one other registered user of the financial transaction application programme. In this way, users of both the resource planning application programme and the financial transaction application programme may easily share and settle expenses by means of direct financial transfer between their bank accounts. Nevertheless, users who prefer to only register with the resource planning application programme may also spontaneously participate in an expense share group without obligation to register with their credit card or bank account.
In an embodiment, said communication between the resource planning application programme of said least one user and the second server is performed over said network and via the first server.
In an embodiment, said communication between the resource planning application programme of said least one user and the second server is performed by that the resource planning application programme of said user calls the financial transaction application programme of said user, and said financial transaction application programme com- municates over said network with the second server.
In an embodiment, when the resource planning application programme calls the financial transaction application programme of said user, the screen of the respective mobile computing device of said user switches from displaying the resource planning applica- tion programme to displaying the financial transaction application programme. Thereby, the user may perform the financial transaction by using a well-known interface which is normally used for performing financial transactions.
In an embodiment, the first server communicates directly with the second server in order to enable said at least one financial transaction. This may improve performance as said communication does not have to be performed by mobile computing devices which may have limited processing capacity.
In an embodiment, before the at least one financial transaction is performed, relevant users are prompted on their respective mobile computing device by a respective direct message, such as a push message, from the second server, and said users accept the
transaction before it is performed. The acceptance may be performed by means of the resource planning application programme. Thereby, the user may perform the financial transaction by using a well-known interface which is normally used for performing financial transactions.
In an embodiment, all expense share group members are also users of the financial transaction application programme, and, in order to perform the settlement of expenses, the second server creates a temporary common account of the expense share group members, respective due amounts to be paid by respective expense share group mem- bers are paid to the temporary common account, and respective due amounts to be received by respective expense share group members are received from said account. Thereby, it may be achieved that, in order to perform the settlement of expenses, each user needs only pay or receive one amount as opposed to paying and/or receiving several amounts to/from several group members.
In an embodiment, when a settlement of expenses has been initiated, users are given a certain period of time within which to pay respective due amounts to the temporary common account, and if not all due amounts have been paid within said certain period of time, already paid amounts are paid back from the temporary common account to the respective users from which said respective amounts were received. Thereby it may achieved that users are urged to pay due amounts in time so that the settlement of expenses may be performed within a suitable time period. Users may be urged to do so due to the fact that they know other members would be unhappy if already paid amounts are returned and the process of settlement thereby would have to be resumed once again.
In an embodiment, a new user of the resource planning application programme which is already a registered user of the financial transaction application programme starts the resource planning application programme which is thereby displayed on the screen of the mobile computing device of said user, the resource planning application programme calls the financial transaction application programme, the screen of said mobile computing device switches from displaying the resource planning application programme to displaying the financial transaction application programme, said new user of the resource planning application programme logs in with the financial transaction application programme using an existing user profile, the financial transaction application programme calls the resource planning application programme, the screen of said mobile
computing device switches from displaying the financial transaction application programme to displaying the resource planning application programme, and said new user is registered as a user of the resource planning application programme by transferring identification details of said new user from the second user database to the first user database. Thereby, registration of said new user of the resource planning application programme may be facilitated as the user does not need to input registration details already known by the financial transaction application programme.
In an embodiment, the first server communicates directly with the second server in order to transfer identification details of said new user from the second user database to the first user database. This may improve performance as said communication does not have to be performed by mobile computing devices which may have limited processing capacity. In an embodiment, the resource planning application programme of at least one user which is not a user of the financial transaction application programme provides a settle up summary indicating for each expense share group member a number of due amounts to be paid to or received from respective other expense share group members. The provided settle up summary of the respective due amounts to be paid or received by the respective expense share group members may serve as a basis for the settlement between the group and users who did not register with the financial transaction application programme. Thereby, the settle up process may be facilitated.
In an embodiment, a new user of the resource planning application programme which is also not a registered user of the financial transaction application programme starts the resource planning application programme which is thereby displayed on the screen of the mobile computing device of said new user, said new user is registered as a user of the resource planning application programme by entering identification details of said new user into the resource planning application programme, and identification details of said new user are transferred from the resource planning application programme to the first user database.
In an embodiment, an overview of expense share groups is displayed on the screen of the mobile computing device of said at least one other user which has been invited to participate in said expense share group, and, in the display of said overview of expense share groups, said expense share group to which said user has been invited is provided
with a notification highlighting the pending invitation until said invitation has been accepted by said user. Thereby, the invitation of a new user to participate in said expense share group may be facilitated. In an embodiment, an overview of expense share groups is displayed on the screen of the mobile computing device of a registered user of the resource planning application programme, and, in the display of said overview of expense share groups, an expense share group in which a group member has initiated settlement of expenses is provided with a notification highlighting the pending settlement until said expenses have been settled. Thereby, the settle up process may be facilitated.
In an embodiment, said notification highlighting the pending settlement is provided with a counter indicating time left until settlement has to be finalised. Thereby, users may be urged to settle up within a reasonable time period.
In an embodiment, an overview of expense share groups is displayed on the screen of the mobile computing device of a registered user of the resource planning application programme, and, in the display of said overview of expense share groups, an expense share group in which settlement of expenses has been finalised is provided with a noti- fication highlighting that expenses have been settled.
In an embodiment, an expense share group thread is displayed on the screen of the mobile computing device of a member of said expense share group, said expense share group thread including a listing of expenses that have been set up by members of said expense share group.
In an embodiment, said expense share group thread includes messages and/or photos added by members of said expense share group. Thereby, communication among users about expenses and related events may be facilitated.
In an embodiment, a number of items such as expenses, text messages, voice messages or photos are added to said expense share group thread by members of said expense share group within a certain time period from each other, and said number of items are listed in said expense share group thread visually grouped together relative to other items of said expense share group thread, such as by being positioned relatively closer to each other. Thereby, a suitable overview is facilitated.
In an embodiment, said number of items listed in said expense share group thread visually grouped together includes only items added by the same member of said expense share group. Thereby, a chat-like communication between users may be facilitated without impairing the general overview. Said number of items are preferably provided with one single time stamp.
In an embodiment, in the display of said listing of items of said expense share group thread, an item which has been displayed on the respective mobile computing devices of each of the members of said expense share group is provided with a notification high- lighting that each of the members has seen the item. This lets the user know which is the last input every member of the group has seen. In an embodiment, the notification is only shown on the latest input seen by all.
In an embodiment, said expense share group thread includes a header, the header pref- erably including information such as the title of the group, the total amount of all shared expenses or the amount the member of said expense share group has to pay, in the case that the expenses have already been settled, or may expect to pay based on the expenses already set up, in the case that the expenses have not already been settled. In an embodiment, an expense details overview is displayed on the screen of the mobile computing device of a member of said expense share group, said expense details overview including at least an indication of an amount due and an indication of the member of said expense share group to which said amount is due, and said expense details overview preferably including a title of said expense.
In an embodiment, said expense details overview includes an indication of specific members of said expense share group, whereby said expense should be shared among said specific members. In an embodiment, a split expense overview is displayed on the screen of the mobile computing device of a member of said expense share group, said split expense overview includes an indication of specific members of said expense share group together with respective fields indicating the share of said expense that the respective specific members have to pay, and the share of said expense indicated in at least one of said fields is amended by said member of said expense share group.
The present invention further relates to a system for carrying out the method according to any one of the preceding claims, the system including a number of mobile computing devices each provided with a screen, an first server maintaining an first user database including identification details of a number of registered users of an resource planning application programme, a second server maintaining a second user database including identification details of a number of registered users of a financial transaction application programme, and a network, each mobile computing device including an resource planning application programme adapted to communicate over the network with the first server, and at least some of said mobile computing devices including a financial trans- action application programme adapted to communicate over the network with the second server. Thereby, the above-mentioned features may be obtained.
The invention will now be explained in more detail below by means of examples of embodiments with reference to the very schematic drawing, in which
Fig. 1 is an overview of an embodiment of a system for carrying out the method according to the invention of settling a plurality of expenses among a plurality of users;
Fig. 2 is a flowchart illustrating a method of on boarding a new user of an resource planning application programme;
Fig. 3 is a wireframe illustrating an overview of expense share groups and methods of notification of a user of the resource planning application programme; Fig. 4 is a wireframe illustrating an expense share group thread listing expenses set up by members of said expense share group;
Fig. 5 is a wireframe illustrating an expense share group details overview together with examples of different expense share group detail views;
Fig. 6 is a wireframe illustrating part of an expense share group settle up procedure;
Fig. 7 is a wireframe illustrating profile settings for a user of the resource planning application programme;
Fig. 8 is a flowchart illustrating an expense share group settle up initiation procedure; and
Fig. 9 is a flowchart illustrating an expense share group settle up receiving procedure.
Fig. 1 illustrates a system 28 according to the invention for providing a financial transaction between a first financial account of a first user, and a second financial account of a second user. The system comprises a number of mobile computing devices 1 (a first mobile computing device, and a second mobile computing device can be seen in fig. 1).
Each of the first mobile computing device, and the second mobile computing device comprises a resource planning application programme ESAP and a financial transaction application programme FTAP.
The resource planning application programme has a first security protocol for securing access to the resource planning programme, and the financial transaction programme has a second security protocol for securing access to the first financial transaction pro- gramme. The first security protocol has a lower degree of security than the second security protocol, i.e. upon a first access to the resource planning application programme, a user authentication is required, but afterwards the resource planning application programme is open for subsequent access (no user authentication being required). The first security protocol comprises a third party login module associated with a third party application programme. Thus, when installing the resource planning application programme, and opening the resource planning application programme for the first time, a window is opened prompting a user authentication for the third party application programme - in this case the third party application programme being the financial trans- action application programme. The user authentication corresponds to the user authentication for the financial transaction application programme. In this way, the financial transaction application programme verifies the user.
The system has a first server 4 for maintaining a first user database 5 of registered users of the resource planning application programme, and a second server 6 for maintaining
a second user database 7 of registered users of the financial transaction application programme, the second server being regulated by a financial regulatory authority.
The resource planning application programme communicates over a network 3 with the first server for providing a substantially real-time text transmission between the first mobile computing device, and the second mobile computing device for determining an amount of money to be transferred between the first financial account and the second financial account in the financial transaction, i.e. a user may send a text message to another user, and the two user may communicate back and forth in order to determine an amount of money to be transferred between them.
The resource planning application programme has a control element for initiating the financial transaction of the amount of money that has been determined. In fig. 1 the mobile computing device is depicted with a touch screen, and in such case the control element may be implemented as a button, whereby the user interacting constitutes pressing the button.
Upon user interaction with the control element the resource planning application programme calls the financial transaction application programme, and provides the amount of money as a string to the financial transaction application programme, i.e. the amount of money to be transferred between the financial accounts of the users is specified to the financial transaction programme. Additionally, the resource planning application programme informs the financial transaction application programme of the identity of the users whereby the financial transaction application programme can look up the financial accounts of the respective users. A suitable user identification may be a telephone number associating a user with a financial account, i.e. the second server has a list associating telephone numbers with financial accounts. A distribution of the telephone number between the first server and the second server allows the system to track the user, i.e. identify the user in both the resource planning application programme and the financial transaction programme.
The second user database comprises second user identification data including an authentication string constituting a password in the form of a pin code (a string of numerical characters), a national identification number, and a user telephone number, which may be looked up in the list.
After the financial transaction programme is called by the user, the financial transaction application programme communicates over the network with the second server, and the second server as a final step transfers the amount of money between the first account and the second account.
The financial transaction application programme prompts a first user authentication in response to the resource planning application programme calling the financial transaction application programme, i.e. the user is required to enter user authentication before the financial transaction application programme opens and proceeds.
The first user database comprises first user identification data including a user telephone number, which has been transferred from the second server. However, the first user identification data excludes users national identification numbers, which are not transferred to the first server from the second server, i.e. the first user identification data being a subset of the second user identification data.
The first security protocol comprises prompting a second user authentication upon a first access to the resource planning application programme, and whereby a subsequent access to the resource planning application programme being open. The second user authentication consists of the authentication string.
The first user identification data is provided to the first server from the second server via the network. The second security protocol comprises a multi factor authentication, i.e. to log in to the financial transaction application programme, the user needs the pin code in addition to a physical item. In this case the physical item is a telephone, which the user can be contacted on with the users telephone number. After an initial log in, the access to the financial transaction application programme may be more open, i.e. dispensing with the second factor authentication.
The resource planning application programme communicates with the first server with a first security level, and the financial transaction application programme communicating with the second server with a second security level, the first security level being lower than the second security level.
The first server having a first encryption level, i.e. the first server may be un-encrypted all together.
The second server has a second encryption level, the first encryption level being lower than the second encryption level.
The resource planning application programme communicates with the first server at a first speed, and the financial transaction application programme communicating with the second server at a second speed, the first speed being higher than the second speed.
The resource planning application programme comprises a deadline for user interaction with the control element before the resource planning application programme deletes the amount of money, which have previously been determined by the resource planning application programme via the users communication, i.e. if a user is to transfer an amount of money, and does not initiate the financial transaction via the control element before a certain time, the resource planning application programme resets itself.
The system 28 includes a number of mobile computing devices 1 each provided with a screen 2 and belonging to different users, an first server 4 maintaining an first user da- tabase 5 including identification details of a number of registered users of an resource planning application programme ESAP, a second server 6 maintaining a second user database 7 including identification details of a number of registered users of a financial transaction application programme FTAP, and a network 3. Each mobile computing device 1 includes an resource planning application programme ESAP adapted to com- municate over the network 3 with the first server 4, and at least some of said mobile computing devices 1 includes a financial transaction application programme FTAP adapted to communicate over the network 3 with the second server 6.
It is noted that in Fig. 1 , only one mobile computing device 1 belonging to one of said users is illustrated. Of course, in order to carry out the method according to the present invention, a number of mobile computing devices 1 are adapted to communicate over the network 3 with the second server 6 and/or the first server 4 . However, the mobile computing device 1 illustrated in Fig. 1 includes both an resource planning application programme ESAP and a financial transaction application programme FTAP. Said mobile computing device 1 is illustrated in two different situations; to the left, the mobile computing device 1 displays the resource planning application programme ESAP, and to the
right, the mobile computing device 1 displays the financial transaction application programme FTAP.
The mobile computing device 1 is a web client, typically in the form of a smart phone, a tablet computer, a laptop computer or the like, and the network 3 may be formed by several interconnected networks, and may typically include a wireless network, such as a cell phone network or a wireless local area network (WLAN), and/or other networks such as the internet and/or a local area network (LAN). In the specific case of the mobile computing devices 1 being smart phones or tablet computers, the resource planning application programme ESAP and the financial transaction application programme FTAP are so-called mobile apps.
The method according to the present invention of settling a plurality of expenses among a plurality of users is carried out in that each user makes use of a respective mobile computing device 1 provided with a screen 2 and including an resource planning application programme ESAP communicating over the network 3 with the first server 4 maintaining the first user database 5 including identification details of a number of registered users of the resource planning application programme ESAP. The respective mobile computing devices 1 of at least some of said users include also a financial transaction application programme FTAP communicating over the network 3 with the second server 6 maintaining the second user database 7 including identification details of a number of registered users of the financial transaction application programme FTAP.
A registered user of the resource planning application programme ESAP may by means of said programme invite one or more other registered users of the resource planning application programme to participate in an expense share group 8. Subsequently, by means of the resource planning application programme ESAP, at least one of said expense share group members sets up an expense 9 to be shared between at least some of said expense share group members. Later, one of said expense share group mem- bers may, by means of the resource planning application programme ESAP, initiate a settlement of expenses. Thereby, the resource planning application programme ESAP of said expense share group members may provide a settle up summary 10 of the respective due amounts to be paid or received by the respective expense share group members. The resource planning application programme ESAP of a user which is also a user of the financial transaction application programme FTAP may then communicate with the second server 6 which performs at least one financial transaction between said
user and at least one other registered user of the financial transaction application programme FTAP. The financial transaction application programme FTAP could for instance be a mobile app such as MobilePay (trademark registered by Danske Bank A/S). In an embodiment of the invention, said communication between the resource planning application programme ESAP of said least one user and the second server 6 is performed over said network 3 and via the first server 4.
In the embodiment illustrated in Fig. 1 , said communication between the resource plan- ning application programme ESAP of said least one user and the second server 6 is performed by that the resource planning application programme ESAP of said user calls the financial transaction application programme FTAP of said user, and said financial transaction application programme communicates over said network 3 with the second server 6. When the resource planning application programme ESAP calls the financial transaction application programme FTAP of said user, the screen 2 of the respective mobile computing device 1 of said user switches 11 from displaying the resource planning application programme ESAP to displaying the financial transaction application programme FTAP. In an embodiment of the invention, the first server 4 communicates directly with the second server 6 in order to enable said at least one financial transaction. When in this description it is mentioned that the first server 4 may communicate directly with the second server 6 this is meant to be understood so that said communication is performed directly between said servers 4, 6 as opposed to via an resource planning application programme ESAP and a financial transaction application programme FTAP included by a mobile computing device 1. Said communication may for instance be performed via a local network such as a LAN network. However, it could also be performed via the internet. In an embodiment of the invention, before the at least one financial transaction is performed, relevant users are prompted on their respective mobile computing device 1 by a respective direct message, such as a push message, from the second server 6, and said users accept the transaction before it is performed. The acceptance may be performed by means of the resource planning application programme. Thereby, the user may perform the financial transaction by using a well-known interface which is normally used for performing financial transactions.
In an embodiment of the invention, all expense share group members are also users of the financial transaction application programme FTAP, whereby, in order to perform the settlement of expenses, the second server 6 creates a temporary common account of the expense share group members, whereby respective due amounts to be paid by respective expense share group members are paid to the temporary common account, and whereby respective due amounts to be received by respective expense share group members are received from said account. Thereby, it may be achieved that, in order to perform the settlement of expenses, each user needs only pay or receive one amount as opposed to paying and/or receiving several amounts to/from several group members.
In an embodiment of the invention, when a settlement of expenses has been initiated, users are given a certain period of time within which to pay respective due amounts to the temporary common account, and if not all due amounts have been paid within said certain period of time, already paid amounts are paid back from the temporary common account to the respective users from which said respective amounts were received. Thereby it may achieved that users are urged to pay due amounts in time so that the settlement of expenses may be performed within a suitable time period. Users may be urged to do so due to the fact that they know other members would be unhappy if already paid amounts are returned and the process of settlement thereby would have to be resumed once again.
Fig. 2 illustrates an embodiment of the method according to the invention for on boarding a new user of the resource planning application programme ESAP and creating a new expense share group 8. As it is seen, in the case that a new user of the resource planning application programme ESAP is already a registered user of the financial transaction application programme FTAP, the new user starts the resource planning application programme ESAP which is thereby displayed on the screen 2 of the mobile computing device 1 of said user. A welcome page is displayed. The user may now choose the option of logging in by means of the financial transaction application programme FTAP. In the case of the mobile computing device 1 being for instance a smart phone, this may be done by pressing an appropriate icon on the screen 2 of the mobile computing device. Consequently, the resource planning application programme ESAP calls the financial transaction application programme FTAP, whereby the screen 2 of said mobile compu- ting device 1 switches 1 1 from displaying the resource planning application programme ESAP to displaying the financial transaction application programme FTAP. The new
user of the resource planning application programme ESAP then logs in with the financial transaction application programme FTAP using an existing FTAP user profile. Subsequently, the financial transaction application programme FTAP calls the resource planning application programme ESAP, whereby the screen 2 of said mobile computing device 1 switches 12 from displaying the financial transaction application programme FTAP to displaying the resource planning application programme ESAP. The user accepts terms and conditions. The user is requested to give the resource planning application programme ESAP access to mobile computing device information and data, such as contact list, camera, photos and location. Thereby, said new user is registered as a user of the resource planning application programme ESAP by transferring identification details of said new user from the second user database 7 to the first user database 5. Preferably, the first server 4 communicates directly with the second server 6 in order to transfer identification details of said new user from the second user database 7 to the first user database 5. Now, an overview 14 of expense share groups is displayed on the screen 2 of the mobile computing device 1 as illustrated to the left in Fig. 3. In Fig. 2, this is denoted "Display group overview".
As it is furthermore seen in Fig. 2, in the case that a new user of the resource planning application programme ESAP is also not a registered user of the financial transaction application programme FTAP, the new user starts the resource planning application programme ESAP which is thereby displayed on the screen 2 of the mobile computing device 1 of said new user. A welcome screen is displayed. The user may now choose the option of registering as a user of the resource planning application programme ESAP by entering identification details of said new user into the resource planning application programme ("Create new ESAP user profile"). In the case of the mobile computing device 1 being for instance a smart phone, this option may be chosen by pressing an appropriate icon on the welcome page on the screen 2 of the mobile computing device. A user verification is then performed, for example by sending a verification code as a text message (SMS) to the mobile computing device 1. The user accepts terms and conditions. The user is requested to give the resource planning application programme ESAP access to mobile computing device information and data, such as contact list, camera, photos and location. Identification details of said new user are transferred from the resource planning application programme ESAP to the first user database 5 and said new user is now a registered user of the resource planning application programme ESAP. Now, like explained above, the overview 14 of expense share groups is displayed on the screen 2 of the mobile computing device 1 as illustrated to the left in Fig. 3.
As it is furthermore seen in Fig. 2, said new user which is now a registered user of the resource planning application programme ESAP may now create a new expense share group 8 ("Create new group"). This may be done by pressing a new expense share group icon 40 as illustrated to the left in Fig. 3. In order to invite users to the new expense share group 8 ("Send invitations to users"), a list of contacts taken from the users contact list is displayed on the screen 2. Contacts may be checked and will then be invited to the new expense share group. Furthermore, an input field lets the user search for contacts or input a phone number. The input is active and the keyboard may be shown by default. The procedure of choosing contacts is not illustrated in the figures.
As a next step, the resource planning application programme ESAP communicates over the network 3 with the first server 4 which consults the first user database 5 in order to determine, whether the invited users are already registered users of the resource plan- ning application programme ESAP ("Have the invited users already a user profile?"). If an invited user is not already a registered user of the resource planning application programme ESAP, an invitation is sent to said user, preferably as a text message (SMS). The new user may then create a user profile and become a registered user of the resource planning application programme ESAP in the same way as already explained above with reference to the upper part of Fig. 2.
Subsequently, the invited users accept the invitation to participate in the new expense share group 8 and an expense share group thread 18 as illustrated to the left of Fig. 4 is generated ("Generate group thread").
Fig. 3 illustrates the overview 14 of expense share groups and how a user of the resource planning application programme ESAP may receive various notifications 15, 16, 20. Specifically, when the overview 14 of expense share groups is displayed on the screen 2 of the mobile computing device 1 of a user which has been invited by another user to participate in said expense share group 8, said expense share group 8 to which said user has been invited is provided with a notification 15 highlighting the pending invitation until said invitation has been accepted by said user. The invitation may be accepted by
pressing an appropriate icon which may the notification 15 itself. Thereby, the user enters the expense share group 8 and the expense share group thread 18 as illustrated to the left of Fig. 4 is displayed. In general, in the display of said overview 14 of expense share groups, an expense share group 8 in which a group member has initiated settlement of expenses is provided with a notification 16 highlighting the pending settlement until said expenses have been settled. Said notification 16 highlighting the pending settlement may be provided with a counter indicating time left until settlement has to be finalised.
In general, in the display of said overview 14 of expense share groups, an expense share group 8 in which settlement of expenses has been finalised is provided with a notification 17 highlighting that expenses have been settled. Fig. 4 illustrates how an expense share group thread 18 is displayed on the screen 2 of the mobile computing device 1 of a member of said expense share group 8. The expense share group thread 18 includes a listing of expenses 9 that have been set up by members of said expense share group 8. Furthermore, the expense share group thread 18 may include messages 19 and/or photos 41 added by members of said expense share group 8. An expenses 9 that a user is not part of may visually appear faded down to indicate that the user does not have to worry about this expense. The resource planning application programme ESAP may communicate messages to the user in the form of a bot 34 (a virtual robot) in different situations and function as an alternative to errors, alerts etc.
As further illustrated in Fig. 4, in an embodiment, a number of items such as expenses 9, text messages, voice messages or photos which are added to said expense share group thread 18 by members of said expense share group 8 within a certain time period from each other, such as for instance 1 , 2, 10, 30 or even more minutes, are listed in said expense share group thread 18 visually grouped together relative to other items of said expense share group thread, such as by being positioned relatively closer to each other or by being positioned in a common frame or icon. Said number of items listed in said expense share group thread 18 and visually grouped together may include only items added by the same member of said expense share group, and said number of items may preferably be provided with one single time stamp. Thereby, several items,
such as short messages, following each other may be seen as one message and thereby provide a better overview in the expense share group thread 18.
As further illustrated in Fig. 4, in an embodiment, in the display of said listing of items of said expense share group thread 18, an item which has been displayed on the respective mobile computing devices 1 of each of the members of said expense share group
8 is provided with a notification 20 highlighting that each of the members has seen the item. This lets the user know which is the last input every member of the group has seen. In an embodiment, the notification 20 is only shown on the latest input seen by all.
As further illustrated in Fig. 4, said expense share group thread 18 includes a header 21 , the header preferably including information such as the title of the group 8, the total amount of all shared expenses or the amount the member of said expense share group has to pay, in the case that the expenses 9 have already been settled, or may expect to pay based on the expenses already set up, in the case that the expenses have not already been settled.
As further illustrated in Fig. 4, an expense details overview 22 may be displayed on the screen 2 of the mobile computing device 1 of a member of said expense share group 8. Said expense details overview 22 may include at least an indication 23 of an amount due and an indication 24 of the member of said expense share group 8 to which said amount is due, and said expense details overview preferably also includes a title of said expense. Preferably, said expense details overview 22 includes an indication 25 of specific members of said expense share group 8 among which said expense should be shared.
As further illustrated in Fig. 4, a split expense overview 26 may be displayed on the screen 2 of the mobile computing device 1 of a member of said expense share group 8. Said split expense overview 26 includes an indication of specific members 25 of said expense share group together with respective fields 27 indicating the share of said expense 9 that the respective specific members have to pay. The share of said expense
9 indicated in the respective fields 27 may be amended by said member of said expense share group. Preferably, initially, by default, the respective fields 27 may each display an equal share of said expense 9 and the user may then amend one or more fields 27 in the case that not all users have to pay an equal amount in relation to the expense.
The split expense overview 26 may conveniently for the user be provided with a calculator 33, as illustrated. Thereby, any calculation necessary for entering the respective shares in the fields 27 may easily be performed. Fig. 5 illustrates an expense share group details overview 42 together with examples of different expense share group detail views 43, 44, 45. The expense share group details overview 42 may be provided with a header indicating title, description and group photo. The expense share group details overview 42 may furthermore be provided with key figures such as total amount of expenses, how much the user has paid, the amount the user has to pay or can expect to be paid. Icons or tabs may lead the user to a summary 43 of users expenses, a list 44 of all expenses or a collection 45 of photos 41. The user may also leave the group from the expense share group details overview 42. Furthermore, the user may initiate the settle up process from the expense share group details overview 42.
Fig. 6 illustrates part of the expense share group settle up procedure. To the left in the figure, a settle up summary 10 of the respective due amounts to be paid or received by the respective expense share group members is illustrated. The users figures of the actual user are highlighted so they stand out. A share functionality that lets the user share an overview of shared expenses via e-mail, text message (SMS) or as a link may be provided. If a user in the group has not accepted the invitation to participate in the group, the user will be listed as inactive so it is clear that the user has not taken part in the sharing of expenses. In the middle of Fig. 6, a confirmation modal 31 as explained in further detail below is illustrated. To the right of Fig. 6, an example of inactive user prompt 30 as also explained in further detail below is illustrated.
Fig. 7 illustrates profile settings for a user of the resource planning application programme ESAP. To the left in the figure, a profile for FTAP users is illustrated. The user profile information is retrieved from the financial transaction application programme FTAP or from the second server 6. On the profile page this dynamic may be explained and it may also explained that if a user wants to update the information, the user must go to the financial transaction application programme FTAP and can do that by clicking an icon on the page (in the case of for instance in iPhone, this initiates a standard iOS app switch). In the middle of Fig. 7, a profile for NON FTAP users is illustrated. NON FTAP users may update all their information here. When updating the
phone number, a new verification may be sent by text message to verify the new phone number. To the right of Fig. 7, an example of a verification code input interface is illustrated. Fig. 8 illustrates an embodiment of the method according to the invention of an expense share group settle up initiation procedure. It is seen that in the case that a user which is not a user of the financial transaction application programme FTAP initiates the settle up procedure, the resource planning application programme ESAP of that user provides a settle up summary 13 indicating for each expense share group member a number of due amounts to be paid to or received from respective other expense share group members. Subsequently, a settled expense group thread 29 is displayed on the screen 2. Furthermore it is seen that in the case that a user which is also a user of the financial transaction application programme FTAP initiates the settle up procedure, the resource planning application programme ESAP of that user provides the settle up summary 10 of the respective due amounts to be paid or received by the respective expense share group members. Subsequently, the user may be presented with the inactive user prompt 30 mentioned above. This happens if another user in the expense share group has not yet accepted the invitation to participate in the group. The resource planning application programme ESAP therefore prompts the user for whether the user wants to proceed with the settle up process, or the user wants to remove that other user from the group before settling up. Subsequently, the user is presented with the confirmation modal 31 as mentioned above which explains and sets the scene for the settle up process. This may include communication of an expiration period before a settle up process is cancelled. Subsequently, if the user does not owe money, a settled expense group thread 29 may subsequently be displayed on the screen 2 when the expense has been settled. On the other hand, if the user does owe money, according to the illustrated embodiment, the resource planning application programme ESAP calls the financial transaction application programme FTAP, and said financial transaction application programme communicates over the network 3 with the second server 6 which performs at least one financial transaction between said user and at least one other registered user of the financial transaction application programme FTAP. Subsequently, the financial transaction application programme FTAP calls the resource planning application programme ESAP, and the settled expense group thread 29 is displayed on the screen 2. Alternatively, as discussed above, the resource planning application programme ESAP may communicate with the second server 6, possibly via the first server 4, whereby the second server 6 performs said at least one financial transaction. Before the financial
transaction is performed, the user may be prompted on the respective mobile computing device by a respective direct message, such as a push message, from the second server, and user accepts the transaction before it is performed. The acceptance may be performed by means of the resource planning application programme. In fact, the direct message may even be received by said user without running the resource planning application programme ESAP.
Fig. 9 illustrates an embodiment of the method according to the invention of an expense share group settle up receiving procedure. Like explained above for Fig. 8, it is seen that in the case that a user which is not a user of the financial transaction application programme FTAP initiates the settle up procedure, the resource planning application programme ESAP of that user provides a settle up summary 13 indicating for each expense share group member a number of due amounts to be paid to or received from respective other expense share group members. Subsequently, the user is asked to agree to the settle up summary 13. Subsequently, a settled expense group thread 29 is displayed on the screen 2. Furthermore it is seen that in the case that a user which is also a user of the financial transaction application programme FTAP is a receiver of the settle up procedure, the resource planning application programme ESAP of that user provides the settle up summary 10 of the respective due amounts to be paid or received by the respective expense share group members. Subsequently, according to the illustrated embodiment, the resource planning application programme ESAP calls the financial transaction application programme FTAP, and said financial transaction application programme communicates over the network 3 with the second server 6 which performs at least one financial transaction between said user and at least one other registered user of the financial transaction application programme FTAP. Subsequently, the financial transaction application programme FTAP calls the resource planning application programme ESAP, and the settled expense group thread 29 is displayed on the screen 2. Alternatively, as discussed above, the resource planning application programme ESAP may communicate with the second server 6, possibly via the first server 4, whereby the second server 6 performs said at least one financial transaction. Before the financial transaction is performed, the user may be prompted on the respective mobile computing device by a respective direct message, such as a push message, from the second server, and user accepts the transaction before it is performed. The acceptance may be performed by means of the resource planning application programme. In fact, the direct message may even be received by said user without running the resource planning application programme ESAP.
List of reference numbers
ESAP resource planning application programme
FTAP financial transaction application programme
1 mobile computing device
2 screen
3 network
4 first server
5 first user database
6 second server
7 second user database
8 expense share group
9 expense
10 settle up summary
1 1 switch from displaying ESAP to displaying FTAP
12 switch from displaying FTAP to displaying ESAP
13 settle up summary for non FTAP user
14 overview of expense share groups
15 notification highlighting pending invitation
16 notification highlighting pending settlement
17 notification highlighting expenses have been settled
18 expense share group thread
19 message
20 notification highlighting that each of members has seen item 21 header
22 expense details overview
23 indication of an amount due
24 indication member to which amount is due
25 indication of specific members of said expense share group 26 split expense overview
27 field indicating share of expense to pay
28 system for carrying out method of settling plurality of expenses
29 settled expense group thread
30 inactive user prompt
31 confirmation modal
32 profile settings
33 calculator
34 bot
35 avatar
36 keyboard
37 profile settings for FTAP users
38 profile settings for non FTAP users
39 verification code input
40 new expense share group icon
41 photo
42 expense share group details overview
Claims
1. A method of providing a financial transaction between a first financial account of a first user, and a second financial account of a second user,
said method comprising the steps of
providing a first mobile computing device, and a second mobile computing device, each of said first mobile computing device, and said second mobile computing device comprising a resource planning application programme and a financial transaction application programme,
said resource planning programme having a first security protocol for securing access to said resource planning programme, and said financial transaction programme having a second security protocol for securing access to said financial transaction programme, said first security protocol having a lower degree of security than said second security protocol, said method further comprising the steps of
providing a first server for maintaining a first user database of registered users of said resource planning application programme,
providing a second server for maintaining a second user database of registered users of said financial transaction application programme, said second server being regulated by a financial regulatory authority, said resource planning application programme communicating over a network with said first server for providing a substantially real-time text transmission between said first mobile computing device, and said second mobile computing device for determining an amount of money to be transferred between said first financial account and said second financial account in said financial transaction, said resource planning application programme having a control element for initiating said financial transaction of said amount of money, whereby upon user interaction with said control element said resource planning application programme calls said financial transaction application programme, and provides said amount of money as a string to said financial transaction application programme,
said financial transaction application programme communicating over said network with said second server, and said amount of money is transferred between said first account and said second account.
2. A method according to claim 1 , said second server transfers said amount of money between said first account and said second account.
3. A method according to any one of the preceding claims, said financial transaction application programme prompts a first user authentication in response to said resource planning application programme calling said financial transaction application programme.
4. A method according to any one of the preceding claims, said first user database comprises first user identification data including a user telephone number.
5. A method according to claim 4, said first user identification data excluding a national identification number.
6. A method according to any one of the preceding claims, said second user database comprising second user identification data including an authentication string.
7. A method according to claim 6, said second user identification data including a national identification number.
8. A method according to claims 4 and 6, said second user identification data including said user telephone number.
9. A method according to any one of the preceding claims, said first security protocol comprising prompting a second user authentication upon a first access to said resource planning application programme, and whereby a subsequent access to said resource planning application programme being open.
10. A method according to claim 9, said second user authentication consisting of said authentication string.
1 1. A method according to claim 10, said first security protocol comprising calling said financial transaction application programme for verifying said authentication string.
12. A method according to claims 4 and 6, said first user identification data being a subset of said second user identification data.
13. A method according to claims 4 and 6, said first user identification data being provided to said first server from said second server via said network.
14. A method according to any one of the preceding claims, said second security protocol comprising a multi factor authentication.
15. A method according to any one of the preceding claims, said resource planning application programme communicating with said first server with a first security level.
16. A method according to claim 15, said financial transaction application programme communicating with said second server with a second security level, said first security level being lower than said second security level.
17. A method according to any one of the preceding claims, said first server having a first encryption level.
18. A method according to any one of the preceding claims, said first server being unencrypted.
19. A method according to claim 17, said second server having a second encryption level, said first encryption level being lower than said second encryption level.
20. A method according to any one of the preceding claims, said resource planning application programme communicating with said first server at a first speed.
21. A method according to claim 20, said financial transaction application programme communicating with said second server at a second speed, said first speed being higher than said second speed.
22. A method according to claims, said resource planning application programme comprising a deadline for user interaction with said control element before said resource planning application programme deleting said amount of money having been determined by said resource planning application programme.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| IBPCT/IB2016/053496 | 2016-06-14 | ||
| IB2016053496 | 2016-06-14 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2017216672A1 true WO2017216672A1 (en) | 2017-12-21 |
Family
ID=56137477
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/IB2017/053285 WO2017216672A1 (en) | 2016-06-14 | 2017-06-02 | Method of providing a financial transaction |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2017216672A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112101919A (en) * | 2020-09-16 | 2020-12-18 | 财付通支付科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070244811A1 (en) * | 2006-03-30 | 2007-10-18 | Obopay Inc. | Mobile Client Application for Mobile Payments |
| US20090327128A1 (en) | 2000-08-08 | 2009-12-31 | Ebay Inc. | System and method for managing allocation of funds between a plurality of entities |
| US20140108235A1 (en) | 2012-10-16 | 2014-04-17 | American Express Travel Related Services Company, Inc. | Systems and Methods for Payment Settlement |
| US20150142661A1 (en) * | 2013-11-20 | 2015-05-21 | Capital One Financial Corporation | Shared expense management |
-
2017
- 2017-06-02 WO PCT/IB2017/053285 patent/WO2017216672A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090327128A1 (en) | 2000-08-08 | 2009-12-31 | Ebay Inc. | System and method for managing allocation of funds between a plurality of entities |
| US20070244811A1 (en) * | 2006-03-30 | 2007-10-18 | Obopay Inc. | Mobile Client Application for Mobile Payments |
| US20140108235A1 (en) | 2012-10-16 | 2014-04-17 | American Express Travel Related Services Company, Inc. | Systems and Methods for Payment Settlement |
| US20150142661A1 (en) * | 2013-11-20 | 2015-05-21 | Capital One Financial Corporation | Shared expense management |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112101919A (en) * | 2020-09-16 | 2020-12-18 | 财付通支付科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN112101919B (en) * | 2020-09-16 | 2024-04-12 | 财付通支付科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10970692B2 (en) | Method, system and server system of payment based on a conversation group | |
| US11869005B2 (en) | System and method linking to accounts using credential-less authentication | |
| US20220038451A1 (en) | Utilizing Federated User Identifiers to Enable Secure Information Sharing | |
| US20160247156A1 (en) | Secure transaction processing through wearable device | |
| US20140279489A1 (en) | Systems and methods for providing alternative logins for mobile banking | |
| US20150046327A1 (en) | Server-based payment system | |
| CN107735999A (en) | The certification for passing through multiple approach based on functions of the equipments and user's request | |
| CN107341402A (en) | A kind of program excutive method and device | |
| KR101879353B1 (en) | Mediation Service System and Method using Virtual Money | |
| US20150339638A1 (en) | System and method for providing social cash | |
| US10922667B2 (en) | Transaction interactions between node groups | |
| CN110276184A (en) | A kind of cloud computing resources authorization method and device | |
| WO2017216672A1 (en) | Method of providing a financial transaction | |
| KR102140453B1 (en) | Meeting management method and meeting management system using the method | |
| WO2019025868A1 (en) | System and method for providing secured services | |
| US11314850B2 (en) | Preventing unauthorized access to secure information systems using advanced biometric authentication techniques | |
| US20140006271A1 (en) | Cross-network electronic payment processing system and method | |
| US11227266B2 (en) | Digital holding account | |
| CN113963495A (en) | Withdrawal method and apparatus | |
| KR101354887B1 (en) | The system which supports a authentication process of a user who using a non-facing service | |
| CN116703395B (en) | Digital RMB payment method, device, equipment, system and medium | |
| US20240015158A1 (en) | Systems and methods for granting account access to a guest contact | |
| CA3061124A1 (en) | Communications and analysis system | |
| US10404691B2 (en) | Preventing unauthorized access to secured information systems using authentication tokens | |
| KR101803900B1 (en) | Apparatus, Server and Method for Providing Financial Service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17729556 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 17729556 Country of ref document: EP Kind code of ref document: A1 |