TWI854048B - Computer program product, method, and computer apparatus for prior authorization of transction in shared account - Google Patents

Abstract

The present invention discloses a computer program product, method and computer device for pre-approving transactions of shared accounts. The shared account transaction method of one embodiment may include: a generating step, based on a request from a user of the computer device, generating a shared account that allows the user to share usage details with at least one member selected from a friend list of an instant messaging software installed in the computer device; a transmitting step, when a transaction request of the shared account occurs, transmitting a pre-approval message for the transaction request to the computer device of the member through the instant messaging software; and an executing step, based on a response of the member to the pre-approval message, executing the pre-approved transaction of the shared account.

Description

Computer program product, method and computer device for pre-approving transactions of shared accounts

The following description relates to techniques for processing transaction approvals for shared accounts.

Online banking is a service that uses the Internet to process various financial transactions such as deposits and withdrawals provided by banks and utilizes various financial information and functions. To this end, users can open an account provided by a bank and use online printing by corresponding accounts.

In order to use online banking, users set up an application-like proxy on the user terminal and handle banking transactions by connecting to the server that manages banking transactions through the corresponding proxy.

As a result, users can use agents to handle various banking transactions without having to visit the bank directly.

For example, Patent No. 10-2015861 granted in Korea (grant date August 23, 2019) discloses a technology for opening a bank account to handle banking transactions without face-to-face communication.

Invent the problem you want to solve

Transactions on shared accounts can be processed with pre-approval from members using instant messaging software.

Improper use by members who have transaction permissions on the shared account can be prevented in advance.

Technical means to solve the problem

The present invention provides a shared account transaction method, which is executed in a computer device, wherein the computer device includes at least one processor that executes a plurality of computer-readable instructions contained in a memory. The shared account transaction method includes: a generation step, wherein the at least one processor generates, based on a request from a user of the computer device, a shared account transaction for the user to share with at least one member selected from a friend list of an instant messaging software installed in the computer device. A shared account with usage details; a sending step, by the at least one processor, in the event of a transaction request of the shared account, sending a pre-approval message for the transaction request to the computer device of the member through the instant messaging software; and an execution step, by the at least one processor, executing the pre-approved transaction of the shared account based on the response of the member to the pre-approval message.

According to one embodiment, in the transmitting step, the pre-approval message including at least one of the transaction amount and the transaction purpose selected or input for the transaction of the shared account may be transmitted.

According to another implementation, in the above-mentioned transmission step, when a settlement request is made using the above-mentioned shared account, the above-mentioned pre-approval message including the settlement request information of the franchise store can be transmitted.

According to another embodiment, the pre-approval message may be constituted by an action message including a user interface (UI) for inputting permission or rejection of the transaction request.

According to another embodiment, in the sending step, if the transaction request meets the transaction conditions set in the shared account, the pre-approval message may be sent.

According to another implementation, as a pre-determined rule for transactions requiring prior approval, the transaction conditions may include at least one of an industry category, amount or time related to the transaction.

According to another implementation, in the above-mentioned execution step, the pre-approved transaction of the above-mentioned shared account may be allowed if the response to the above-mentioned pre-approval message meets the valid approval processing conditions set in the above-mentioned shared account.

According to another embodiment, as a pre-determined rule for the transaction, the above-mentioned valid approval processing conditions may include at least one of the number of persons or the proportion of persons certified as valid approvals and the response time.

According to another embodiment, the above-mentioned effective approval processing conditions can be set differently according to the above-mentioned transaction conditions.

According to another implementation, in the above-mentioned execution step, the transaction of the above-mentioned shared account may be allowed if the actual transaction content of the above-mentioned shared account corresponds to the transaction content pre-approved by the above-mentioned members.

According to another embodiment, the shared account transaction method may further include the step of monitoring the shared account transactions by the at least one processor to provide reminders to the members' computer devices of transactions corresponding to predetermined improper use conditions.

According to another embodiment, in the providing step, uncompleted pre-approved transactions can be monitored in the transactions of the shared account, and whether the shared account is improperly used can be determined based on at least one of the transaction time and the transaction location.

According to another embodiment, the shared account transaction method may further include the step of sending a pre-approval message for the setting change to the computer device of the member by the at least one processor when the user changes the setting related to the shared account.

According to another embodiment, the shared account transaction method may further include the following step, namely, by means of the at least one processor, in the event that there is a request from the user to delete or add a member of the shared account, a pre-approval message regarding the deletion or addition of a member is transmitted to the computer device of the member.

According to another embodiment, the shared account transaction method may further include the following step, namely, by means of the at least one processor, setting the member selected by the user among the members of the shared account as a temporary master agent having transaction permission for the shared account.

According to another embodiment, in the above setting step, at least one of the transaction type, industry category, time and amount for which the above master agent's permission is valid can be set.

According to another embodiment, the shared account transaction method may further include the step of transmitting, by the at least one processor, a pre-approval message related to the setting of the master agent to the computer device of the member.

According to another embodiment, the shared account transaction method may further include the following steps, namely, by means of the at least one processor, based on the user sending a deposit request to the shared account, after the member completes the deposit, when a transaction request of the shared account for a transaction related to the deposit request occurs, the transaction related to the deposit request is executed without prior approval.

The present invention provides a computer program product, which is stored in a computer-readable recording medium in order to execute the shared account transaction method on a computer.

The present invention provides a server, which includes at least one processor for executing computer-readable instructions contained in a memory. The at least one processor generates a shared account based on a request from the electronic device user of the electronic device, which allows the user to share usage details with at least one member selected from a friend list of an instant messaging software installed in the electronic device. When a transaction request from the shared account occurs, a pre-approval message for the transaction request is sent to the electronic device of the member through the instant messaging software installed in the electronic device of the member, and the pre-approved transaction of the shared account is executed based on the member's response to the pre-approval message.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Embodiments of the present invention relate to techniques for processing transaction approvals for shared accounts.

Multiple embodiments including the content specifically disclosed in this specification can use instant messaging software to process transactions of shared accounts through pre-approval of multiple members, thereby managing shared accounts based on the participation of multiple members and preventing improper use of shared accounts.

Fig. 1 is a diagram showing an example of a network environment of an embodiment of the present invention. The network environment of Fig. 1 includes a plurality of electronic devices 110, 120, 130, 140, a plurality of servers 150, 160 and a network 170. Fig. 1 is an example for illustrating the present invention, and the number of electronic devices and the number of servers are not limited to Fig. 1.

The plurality of electronic devices 110, 120, 130, 140 may be fixed terminals or mobile terminals implemented by a computer system. For example, the plurality of electronic devices 110, 120, 130, 140 may be smart phones, mobile phones, navigators, computers, laptops, digital broadcast terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), tablet computers, game consoles, wearable devices, Internet of Things (IoT) devices, virtual reality (VR) devices, and augmented reality (AR) devices. As an example, in FIG. 1 , a smartphone is shown as an example of the electronic device 110. In an embodiment of the present invention, the electronic device 110 may actually be one of a variety of physical computer systems that communicate with other electronic devices 120, 130, 140 and/or back-end servers 150, 160 via a network 170 using wireless or wired communication methods.

The communication method is not limited thereto, and may include communication methods using a communication network (e.g., a mobile communication network, a wired network, a wireless network, a broadcast network, a satellite network, etc.) that may be included in the network 170 and short-range wireless communication between multiple devices. For example, the network 170 may include any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like. Furthermore, the network 170 may include one or more network topologies including a bus network, a star network, a ring network, a mesh network, a mesh network, a star bus network, a tree hierarchical network, etc., but is not limited thereto.

The servers 150 and 160 may be implemented as a computer device or multiple computer devices that communicate with multiple electronic devices 110, 120, 130, and 140 via a network 170 to provide instructions, codes, files, content, services, etc. For example, the server 150 may be a system that provides a first service to multiple electronic devices 110, 120, 130, and 140 connected via the network 170, and the server 160 may also be a system that provides a second service to multiple electronic devices 110, 120, 130, and 140 connected via the network 170. As a more specific example, the server 150 can provide the services required by the corresponding applications (for example, online banking services, etc.) as the first service to the multiple electronic devices 110, 120, 130, 140 through the application of the computer program installed in the multiple electronic devices 110, 120, 130, 140 and driven. As another example, the server 160 can provide the service of distributing the files used to install and drive the above-mentioned application to the multiple electronic devices 110, 120, 130, 140 as the second service.

FIG2 is a block diagram for explaining the internal structure of an electronic device and a server according to an embodiment of the present invention. FIG2 illustrates the internal structure of an electronic device 110 and a server 150 as an example of an electronic device. In addition, other electronic devices 120, 130, 140 or a server 160 may also have the same or similar internal structure as the electronic device 110 or the server 150.

The electronic device 110 and the server 150 may include memories 211, 221, processors 212, 222, communication modules 213, 223, and input/output interfaces 214, 224. The memories 211, 221 are computer-readable recording media (e.g., non-transitory computer-readable recording media) and may include permanent mass storage devices such as random access memory (RAM), read only memory (ROM), disk drives, solid state drives (SSD), and flash memory. Among them, a permanent large-capacity storage device such as a read-only memory, a solid-state hard disk, a cache memory, a disk drive, etc. is an additional permanent storage device distinguished from the memory 211, 221, and can be included in the electronic device 110 or the server 150. In addition, the memory 211, 221 can store an operating system and at least one program code (as an example, a browser installed in the electronic device 110 and driven or an application installed in the electronic device 110 to provide a specific service). Such a software structural element can be loaded from a computer-readable recording medium separate from the memory 211, 221. Such additional computer-readable recording media may include computer-readable recording media such as floppy disks, disks, tapes, DVD/CD-ROM optical disks, memory cards, etc. In another embodiment, the software structural element may be loaded into the memory 211, 221 via the communication module 213, 223, rather than being loaded via the software structural element. For example, at least one program may be loaded into the memory 211, 221 based on a computer program (e.g., the above-mentioned application), and the above-mentioned computer program is set by a file, and the above-mentioned file is provided by the developer or the file distribution system (as an example, the above-mentioned server 160) that distributes the setting file of the application via the network 170.

The processor 212, 222 can perform basic arithmetic, logic and input/output calculations to process instructions of a computer program. Instructions can be provided to the processor 212, 222 via the memory 211, 221 or the communication module 213, 223. For example, the processor 212, 222 can execute instructions received according to program codes stored in a recording device such as the memory 211, 221.

The communication modules 213 and 223 can provide the function of mutual communication between the electronic device 110 and the server 150 through the network 170, and can provide the function of communication between the electronic device 110 and/or the server 150 and other electronic devices (for example, the electronic device 120) or other servers (for example, the server 160). For example, the processor 212 of the electronic device 110 can transmit the request generated by the program code stored in the storage medium such as the memory 211 to the server 150 through the network 170 under the control of the communication module 213. On the contrary, the control signal or instruction, content, file, etc. provided by the processor 222 of the server 150 is transmitted to the electronic device 110 through the communication module 213 of the electronic device 110 via the communication module 223 and the network 170. For example, the control signal or instruction, content, file, etc. of the server 150 received by the communication module 213 can be transmitted to the processor 212 or the memory 211, and the content or file, etc. can be stored in the storage medium (the above-mentioned permanent storage device) that the electronic device 110 can also include.

The input-output interface 214 may be an interface of an input-output device 215. For example, the input device may include a keyboard, a mouse, a microphone, a camera, etc., and the output device may include a display, a speaker, a haptic feedback device, etc. As another example, such as a touch screen, the input-output interface 214 may be an interface of a device that combines the functions of input and output into one. The input-output device 215 may also constitute a device with the electronic device 110. Furthermore, the input-output interface 224 of the server 150 may be an interface of a device (not shown) for input or output that is connected to the server 150 or that the server 150 may include. As a more specific example, when the processor 212 of the electronic device 110 processes the instructions of the computer program loaded in the memory 211, the service screen or content constructed using the data provided by the server 150 or the electronic device 120 can be displayed on the display through the input and output interface 214.

Moreover, in another embodiment, the electronic device 110 and the server 150 may include more structural elements than the structural elements of FIG. 2 . However, it is not necessary to explicitly show the structural elements of most of the prior art. For example, the electronic device 110 includes at least a portion of the above-mentioned input-output device 215, or may also include other structural elements such as a transceiver, a global positioning system (GPS) module, a camera, various sensors, a database, etc. As a more specific example, in the case where the electronic device 110 is a smart phone, usually, a variety of structural elements including an accelerometer or a gyroscope sensor of the smart phone, a camera module, various physical buttons, buttons using a touch panel, input-output ports, a vibrator for vibration, etc. are also included in the electronic device 110.

The following describes a specific embodiment of a method and system for pre-approving transactions between shared accounts.

In this manual, a shared account is a bank deposit account that allows deposits and withdrawals. It is an account in which multiple users can deposit an amount in one account and share the usage details (deposit and withdrawal details) of the corresponding account. Members who can participate in a shared account include members corresponding to the depositor who opened the account (hereinafter referred to as "primary members") and members registered by the primary member as account sharing objects (hereinafter referred to as "members"). In this case, the primary member has transaction permission to use the deposit amount of the shared account for settlement, withdrawal, remittance, etc., and the member can have participation permission to share the usage details related to the deposit amount of the shared account. In particular, in an embodiment of the present invention, members can have approval authority for transactions in a shared account in order to prevent the main member from improperly using the shared account. According to the embodiment, through the settings of the main member, at least some members can have temporary transaction permissions instead of the main member.

FIG. 3 is a diagram showing an example of structural elements that may be included in a processor of an electronic device according to an embodiment of the present invention, and FIG. 4 is a flow chart showing an example of a method that may be performed by an electronic device according to an embodiment of the present invention.

The electronic device 110 of this embodiment may include a shared account transaction system implemented by a computer. For example, the shared account transaction system is implemented as an independent program or in an application form of a specific application, so that when the specific application can be operated, it provides online banking services by linking with the server 150.

Based on the instructions provided by the application installed in the electronic device 110, the shared account transaction system implemented in the electronic device 110 can execute the shared account transaction method shown in FIG. 4 .

In order to execute the shared account transaction method of FIG. 4 , as shown in FIG. 3 , as structural elements, the processor 212 of the electronic device 110 may include an account generation unit 310, an approval processing unit 320, and a transaction processing unit 330. According to an embodiment, the structural elements of the processor 212 may be selectively included in or excluded from the processor 212. Furthermore, according to an embodiment, the structural elements of the processor 212 may be separated or combined in order to present the functions of the processor 212.

The electronic device 110 may be controlled to cause the processor 212 and the structural elements of the processor 212 to execute the multiple steps (steps S410 to S440) included in the shared account transaction method of FIG4. For example, the processor 212 and the structural elements of the processor 212 may execute the operating system code included in the memory 211 and instructions based on at least one program code.

The structural elements of the processor 212 may be surfaces of different functions of the processor 212 executed by the processor 212 according to instructions provided by program code stored in the electronic device 110 (e.g., instructions provided by an application driven in the electronic device 110). For example, the electronic device 110 may utilize the account generation unit 310 as a functional expression of the processor 212 of the electronic device 110 in accordance with the instructions in order to generate a shared account.

In step S410, the processor 212 may read necessary instructions from the memory 211 that loads instructions related to the control of the electronic device 110. In this case, the read instructions may include instructions for controlling in such a manner that the processor 212 executes the steps (steps S420 to S440) described later.

In step S420, the account generation unit 310 can be linked with the server 150 to generate a shared account based on the account opening request of the user of the electronic device 110, so that the user of the electronic device 110 and at least one friend selected from the friend list of the instant messaging software set in the electronic device 110 (that is, the instant messaging software that can be linked to the shared account transaction system implemented in the electronic device 110) can share deposit and withdrawal details. In other words, the account generation unit 310 may generate a shared account by using the user of the electronic device 110 as a main member with transaction permission, and using the instant messaging software friend selected by the user of the electronic device 110 as a member with participation permission and approval authority as an account related to the user of the electronic device 110 (e.g., a deposit account of a depositor). In the process of generating the shared account, the account related to the user of the existing electronic device 110 (e.g., a deposit account of a depositor) is converted into a shared account to generate a new shared account. The account generation unit 310 may send a message to the friends selected by the user of the electronic device 110 to participate in the shared account through the instant messaging software, and then register the friends who received the account participation as members of the shared account in response to the invitation message and manage them.

In the process of generating a shared account, the account generating unit 310 may set pre-approval rules related to the shared account through the user of the electronic device 110. The pre-approval rules may include transaction conditions that require pre-approval and valid approval processing conditions. In this case, the transaction conditions may include the transaction industry category, transaction amount, transaction time, etc. that require pre-approval, and the valid approval processing conditions may include the number of personnel, personnel ratio, response time, etc. that are certified as valid approvals for pre-approval, and the valid approval processing conditions may be determined according to the transaction conditions. For example, in relation to transaction conditions, pre-approval may be omitted for settlements in the food or catering industry, and a rule for receiving pre-approval may be set for settlements in the surplus industry, pre-approval may be omitted for settlements below a specified amount, and a rule for receiving pre-approval may be set for settlements exceeding a specified amount, pre-approval may be omitted for settlements during daytime hours (e.g., 08:00-18:59), and a rule for receiving pre-approval may be set for settlements during nighttime hours (e.g., 19:00-07:59), etc. As a condition for effective approval processing, for example, if a specified number of persons (e.g., 1 person) or a specified proportion of persons (e.g., 10%) or more accepts approval within a specified time (1 hour), it may be processed as effective approval. In this case, if there is no member who refuses (deny) within the specified time, it can be processed as a member who has the intention to approve. As another example, in the settlement process below the specified amount, if a part of the members, such as a specified number of people (for example, 1) or a specified proportion of people (for example, 10%), accepts approval, it will be processed as valid approval. In the settlement process exceeding the specified amount, it is necessary for all members to approve it before it can be processed as valid approval. Pre-approval rules can be set for each transaction type (settlement, remittance, withdrawal, etc.) by distinguishing the transaction type.

In addition to the above examples, pre-approval rules related to shared accounts can be set by combining multiple conditions.

In step S430, when a transaction request including at least one of a transaction amount and a transaction purpose for a transaction for a shared account occurs, the approval processing unit 320 cooperates with the instant messaging software installed in the electronic device 110 to transmit a pre-approval message related to the transaction request to the members of the shared account through the corresponding instant messaging software. The pre-approval message is a message for the purpose of confirmation for receiving pre-approval from a plurality of members before the main member uses the deposit amount of the shared account by settlement, withdrawal, remittance, etc., and may be composed of an action message of a user interface for selectively inputting one of an approval intention and a rejection intention for using the deposit amount of the shared account.

As an example, the transaction amount and the transaction purpose may be directly selected or inputted by the user of the electronic device 110 for the transaction using the shared account, in which case the approval processing unit 320 may transmit a pre-approval message to the transaction request including at least one of the transaction amount and the transaction purpose selected or inputted by the user of the electronic device 110. As another example, in a shopping platform that can be linked with the shared account transaction system implemented in the electronic device 110, in the case of a transaction request using the shared account as a settlement unit, the approval processing unit 320 may obtain the shopping information (e.g., the settlement amount, industry, or commodity category, etc.) of the user of the electronic device 110 from the corresponding platform, and may transmit a pre-approval message including the obtained shopping information to the members of the shared account. In this case, the settlement amount included in the shopping information may correspond to the transaction amount, and the industry or product category included in the shopping information may correspond to the transaction purpose. When a settlement request using a shared account is made in an online or offline franchise store, if the franchise store's settlement request information (e.g., settlement amount, industry, or product category, etc.) is available, a pre-approval message containing the corresponding settlement request information may be sent to members of the shared account.

The approval processing unit 320 can transmit a pre-approval message to a member of the shared account based on the pre-approval rule related to the shared account, when a transaction request based on the user of the electronic device 110 corresponds to a transaction condition requiring pre-approval. Furthermore, the approval processing unit 320 can receive a response message (approval, rejection intention) related to the pre-approval message from the member of the shared account and transmit it to the user of the electronic device 110 via the instant messaging software.

In step S440, the transaction processing unit 330 can execute the transaction of the shared account corresponding to the transaction request based on the response related to the pre-approval message. In this case, the transaction processing unit 330 can access the pre-approval rule related to the shared account, and when the responses (approval, rejection intention) received from multiple members to the pre-approval meet the valid approval processing conditions, the transaction processing unit 330 can approve the transaction of the shared account. Even if multiple responses (approval, rejection intention) to the pre-approval meet the valid approval processing conditions, when at least one or more members transmit a rejection intention for the pre-approval, the transaction processing unit 330 does not execute the transaction of the shared account corresponding to the transaction request, but can hold it.

When the actual transaction of the shared account corresponds to the transaction content received in advance from multiple members, the transaction processing unit 330 can execute the transaction of the shared account. As an example, when the actual transaction amount is the same as or within the transaction amount included in the security request, that is, the pre-approved amount, the transaction processing unit 330 can execute the transaction of the shared account. As an example, for the transaction purpose included in the transaction request, that is, the franchise store of the industry category corresponding to the pre-approved purpose, the transaction processing unit 330 can execute the transaction of the shared account. Therefore, even if the user of the electronic device 110 is a main member with transaction permission for the shared account, the transaction of the shared account is performed after receiving the pre-approval of multiple members for the amount or purpose to be used to certify.

5 to 6 show examples of screens of a user interface for explaining a process of generating a shared account.

FIG. 5 shows an account creation screen 500 displayed on the screen of the electronic device 110 .

5 , the processor 212 may provide an account generation screen 500 including an account type catalog 510 that can be generated based on a request from a user of the electronic device 110. In this case, the account type catalog 510 is a bank deposit account provided by an online banking service, for example, and may include a deposit and withdrawal account, a shared account, a time deposit account, a free deposit account, etc.

When the user selects the "shared account" menu 501 in the account category list 510, the processor 212 may provide a shared account generation screen 600 for generating a shared account, as shown in FIG. 6 .

The shared account generation screen 600 is an interface screen for receiving information required to generate a shared account, and may include a "password setting" menu 601 for setting a password for the shared account, a "shared account name" menu 602 for setting a name of the shared account (for example, an alias related to the purpose), a "shared members" menu 603 for setting members of the shared account, and a "pre-approval rules" menu 604 for setting pre-approval rules for the shared account, etc.

The members of the shared account can be set by using the friend list on the instant messaging software in conjunction with the instant messaging software installed in the electronic device 110. When the user selects the "shared members" menu 603, the processor 212 can provide the following interface, that is, by linking with the instant messaging software, the friend list added in the instant messaging software is called, and at least one friend selected by the user is added in the friend list as a member participating in the shared account. The "pre-approval rules" menu 604 can support movement to an interface screen for setting pre-approval rules for the shared account. Pre-approval rules may include transaction conditions that require pre-approval (e.g., industry category, transaction amount, transaction time, etc.) and valid approval processing conditions (e.g., the number of persons certified as validly approved, the proportion of persons, and time, etc.). In this case, the valid approval processing conditions may be set differently according to the transaction conditions.

7 to 10 show illustrations of screens of a user interface for illustrating a process of handling pre-approval of transactions for a shared account.

Fig. 7 shows an owned account screen 700 displayed on the screen of the electronic device 110. Referring to Fig. 7, the owned account screen 700 may include an owned account directory 710 of the user of the electronic device 110 being a depositor, and the owned account directory 710 may include a shared account 701 sharing usage details with the user's instant messaging software friends.

As shown in FIG8 , when the user selects the shared account 701 from the account list 710, the processor 212 may provide a transaction type list 820. The transaction type list 820 is a transaction that can be performed using the shared account, for example, it may include settlement, remittance, withdrawal, deposit request, etc.

As shown in FIG. 9 , when the user selects a transaction type in the transaction type catalog 820, the processor 212 may provide a transaction content input screen 930 for inputting at least one transaction content of the transaction amount and the transaction purpose.

The transaction content input screen 930 may include an interface where the user can directly select or input the transaction amount and transaction catalog. As another example, in online and offline franchise stores, when a settlement request is made using a shared account, the transaction amount and transaction purpose can be extracted from the franchise store's settlement request information (e.g., settlement amount, industry or product category, etc.) and automatically input.

The transaction content input screen 930 may include a “pre-approval” menu 931 for requesting pre-approval from members of a shared account for transaction content including at least one of a transaction amount and a transaction purpose.

When at least one of the transaction amount and the transaction purpose is input into the transaction content input screen 930 and the user selects the "pre-approval" menu 931, the processor 212 may send a pre-approval message containing the corresponding transaction content to the members of the shared account via the instant messaging software installed in the electronic device 110.

FIG. 10 illustrates an example of an instant messaging software screen 1000 of a receiving device (eg, electronic device 120) of a member displaying a pre-approved message.

10 , the members of the shared account can confirm the pre-approval message 1010 received from the main member (user of the electronic device 110) through the instant messaging software screen 1000. The pre-approval message 1010 may include the transaction content (at least one of the transaction amount and the transaction purpose) of the shared account used by the main member, and may include an "Approve" menu 1011 for inputting the intention to approve the transaction content, and a "Reject" menu 1012 for inputting the intention to reject. The member who receives the pre-approval message 1010 can input a response to the pre-approval message using the "Approve" menu 1011 and the "Reject" menu 1012 on the instant messaging software screen 1000. In this case, the processor 212 receives a response (approval, rejection intention) to the pre-approval message received from the member of the shared account through the instant messaging software, and can generate a response message based on the received response in a manner that the corresponding response can be transmitted to the user of the electronic device 110 through the instant messaging software. According to another embodiment, the processor 212 receives a response (approval, rejection intention) to the pre-approval message received from the member of the shared account through the instant messaging software, and can transmit the received response to the server 150. According to another embodiment, the processor 212 may receive a response (approval, rejection intention) to a pre-approval message received from a member of the shared account through the instant messaging software, and based on the received response, transmit the received response to the generation server 160 in a manner that can transmit a corresponding response to the user of the electronic device 110. For example, if the processor 212 approves a predetermined number of members (e.g., 1) or a predetermined proportion of members (e.g., 10%) for the transaction content of the shared account used by the main member, the transaction of the shared account may be approved. According to one embodiment, the processor 212 determines whether a predetermined number of members (e.g., 1) or a predetermined ratio (e.g., 10%) of members approve the transaction content of the shared account used by the main member based on the response information generated based on the response from the members of the shared account, and can approve the transaction of the shared account according to the determination result. In this case, if at least one of the members transmits a rejection intention, the transaction of the shared account can be approved even if the predetermined number of members (e.g., 1) or a predetermined ratio (e.g., 10%) of members approve it. Furthermore, if there is no member among the members who responds (approves, rejects) for a predetermined time (1 hour) or more, the member can be regarded as a member who responds to the rejection intention. According to another embodiment, the processor 212 receives information from the server 150 or the server 160 regarding whether a specified number (e.g., 1) or a specified proportion (e.g., 10%) of members are approved for transaction contents of a shared account used by a master member, and may approve transactions of the shared account based on the received information.

When the processor 212 receives pre-approval from multiple members for the transaction content of the shared account, the transaction of the shared account can be executed for the transaction content for which the pre-approval is received. For example, as shown in FIG9 , for the main member to use 320,000 Korean won by purchasing food, when the pre-approval is received from multiple members, the transaction of the shared account can be executed when the actual transaction of the shared account corresponds to the pre-approval purpose "purchase of food" and the pre-approval amount "320,000 Korean won" or the pre-approval amount is less than "320,000 Korean won".

The master member selects the "Deposit Request" menu for requesting multiple members to deposit money into a common account from the transaction type list 820 shown in FIG8 , and after inputting at least one of the deposit amount and the deposit purpose, the deposit request of the corresponding content can be transmitted to the multiple members. In this case, based on at least one of the deposit amount and the deposit purpose input by the master member, the processor 212 generates a deposit request message on the instant messaging software, so that the deposit request message can be transmitted to the multiple members through the instant messaging software. As another example, at least one of the deposit amount and the deposit purpose input by the master member is transmitted to the server 150 or the server, and a deposit request message generated based on at least one of the deposit amount and the deposit purpose input by the server 150 or the server 160 can be transmitted to multiple members through the instant messaging software. In the case where multiple members make deposits to the shared account in response to the master member's deposit request, the processor 212 can regard it as pre-approval. Thus, for transactions with the same content (deposit amount and deposit purpose) as the deposit request made after the master member's deposit request and the deposits made by multiple members, transactions in the shared account can be performed without pre-approval from multiple members. In other words, for a shared account, the processor 212 may omit the pre-approval step in the case of a transaction associated with a deposit request.

Furthermore, the processor 212 can provide reminders to multiple members of the shared account for transactions corresponding to the improper use conditions by monitoring the transactions of the shared account. As an example, in the transaction process of the shared account, transactions that have not been pre-approved can be monitored. For example, when the time interval between transactions such as settlement, remittance, withdrawal, etc. using the shared account is within a specified time (e.g., 10 minutes), when the distance between the locations where the transactions occurred exceeds a specified radius (e.g., 100 km), it is determined to be improper use, and reminders of improper use can be provided to the members of the shared account.

Basically, the pre-approval step can be performed on transaction requests such as settlement, remittance, withdrawal, etc. using a shared account. According to an embodiment, in the event that the main member changes the settings related to the shared account, pre-approval from multiple members can be required.

As an example, when the processor 212 deletes or adds a member of a shared account, a pre-approval message related to member deletion or addition may be sent to other members. Referring to FIG. 11 , the processor 212 may provide a shared member screen 1100 for managing members of a shared account according to a request from a user of the electronic device 110 .

The shared member screen 1100 may include a member directory 1110 of the shared account logged in by the user (primary member) of the electronic device 110, and may include an "Add Friend" menu 1101 for adding members of the shared account, a "Delete Friend" menu 1102 for deleting members of the shared account, and a "Primary Agent" menu 1103 for granting primary member permission to members of the shared account.

For example, when the user selects the "Friend Delete" menu 1102, as shown in FIG. 12, the processor 212 may provide a shared member deletion screen 1200. In this case, after the user selects the member to be deleted from the members of the shared account through the selection box 1201, if the "Delete" menu 1202 is selected, a pre-approval message containing information related to the selected member (e.g., member name, etc.) may be sent to the members of the shared account as a step of pre-approving the member deletion. For example, when deleting members exceeding a preset number or ratio at the same time or successively, or when the member deletion interval is within a preset time, a pre-approval step may be performed on the deletion request corresponding to a part of the conditions. The pre-approval message may be sent to the remaining members except the member to be deleted. For member deletion, if the members exceeding a preset number (e.g., 1 person) or a preset ratio (e.g., 10%) approve it, the processor 212 may delete the member from the shared account. In this case, the processor 212 may determine, based on information transmitted from the server 150 or the server 160, whether to delete a specified number (e.g., 1 person) or a specified proportion (e.g., 10%) of the approved members.

The process of adding members to a shared account may also include a step of pre-approving member additions as appropriate.

In this embodiment, the main member adds or deletes members of the shared account, but is not limited to this. Members can add or delete members of the shared account with the prior approval of other members including the main member.

As another example, the processor 212 may temporarily allow one of the members of the shared account to have the master member permission according to the request of the user (not shown) of the electronic device 110, in which case a pre-approval message related to the master agent setting may be sent to other members. In the process of the processor 212 setting the master agent, at least one of the transaction type, industry category, time and amount for which the master member permission is valid may be set by the user setting, thereby limiting the transaction permission of the shared account. In addition, the processor 212 may set the master agent by transaction industry category, transaction amount or transaction time by the user setting.

For example, when the user selects the "primary agent" menu 1103 in the shared member screen 1100 of FIG. 11 , as shown in FIG. 13 , the processor 212 may provide a primary agent setting screen 1300, in which the user selects a member axis to be granted primary member permission from among the members of the shared account through a check box 1301, and if the "login" menu 1302 is selected, a pre-approval step for setting the primary agent is performed, and a pre-approval message containing information related to the selected member (e.g., member name, etc.) may be sent to the members of the shared account through the instant messaging software. The pre-approval message may be sent to the remaining members other than the selected member. If the processor 212 is set to approve a specified number of members (e.g., 1) or a specified ratio of members (e.g., 10%), the processor 212 may grant the corresponding member a master member permission, that is, a transaction permission. In this case, the processor 212 may determine whether to approve a specified number of members (e.g., 1) or a specified ratio of members (e.g., 10%) or more among the members for the master agent setting, based on information transmitted from the server 150 or the server 160.

Therefore, in this embodiment, transactions such as settlement, remittance, withdrawal, etc. of a shared account can be performed, and when deleting or adding members of a shared account or changing at least part of the settings related to the shared account, such as granting transaction permissions to members of the shared account, pre-approval of multiple members can be required.

The multiple screens of the interfaces of FIG. 5 to FIG. 13 are merely examples, and the present invention is not limited thereto. The screen composition or access path, screen movement order, etc. related to the shared account may be changed at will.

According to the embodiment of the present invention, for transactions of shared accounts, corresponding transactions can be executed by using instant messaging software after pre-approval of multiple members. Therefore, the permission of the main member of the shared account can be effectively restricted to prevent improper use of the shared account in advance.

The devices described above may be implemented by hardware structural elements, software structural elements and/or a combination of hardware structural elements and software structural elements. For example, the devices and structural elements described in the embodiments may be implemented using one or more conventional computers or special purpose computers such as processors, controllers, arithmetic logic units (ALUs), digital signal processors (DSPs), microcomputers, field programmable gate arrays (FPGAs), programmable logic units (PLUs), microprocessors, or any type of device that can execute and respond to instructions. The processing device may execute an operating system and one or more software applications executed on the operating system. Furthermore, the processing device may access, store, operate, process and generate data in response to the execution of the software. For ease of understanding, there is a situation where a processing device is used, and a person of ordinary skill in the art to which the present invention belongs may know that the processing device may include multiple processing elements and/or multiple types of processing elements. For example, the processing device may include multiple processors or a processor and a controller. Alternatively, it may be other processing configurations such as parallel processors.

Software may include a computer program, code, instructions, or a combination of more than one of these. A processing device may perform the required work, or instructions may be issued to the processing device independently or collectively. Software and/or data may be embodied in any type of machine, component, physical device, computer storage medium or device for interpretation by a processing device or for providing instructions or data to a processing device. Software may be distributed across computer systems connected via a network, or stored or executed by a distributed method. Software and data may be stored on one or more computer-readable recording media.

The method of the embodiment is implemented as a program instruction form that can be executed by a variety of computer units and recorded on a computer-readable medium. In this case, the medium can continue to store the program that can be executed by the computer, or temporarily store it for execution or downloading. In addition, the medium can be a single or multiple hardware combined forms of multiple recording units or storage units, and is not limited to a medium directly connected to a computer system, and can also be dispersed on the network. Examples of media include magnetic media such as hard disks, floppy disks, and disks, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and structures storing program instructions such as ROMs, RAMs, and cache memories. Examples of other media include application stores that distribute applications, web pages that distribute other types of software, and recording media or storage media managed in servers.

As described above, the embodiments are described by the limited embodiments and the accompanying drawings, and a person skilled in the art of the present invention may make various modifications and variations from the above description. For example, the described technology may be performed in a different order than the described method, and/or the structural elements of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the described method, or may be replaced or substituted by other structural elements or equivalent technical solutions to achieve appropriate results.

Therefore, other examples, other embodiments and contents equivalent to the scope of protection of the invention claims also fall within the scope of protection of the invention claims described later.

110,120,130,140: Electronic equipment 150,160: Server 170: Network 211,221: Memory 212,222: Processor 213,223: Communication module 214,224: Input/output interface 215: Input/output device 310: Account generation unit 320: Annotation processing unit 330: Transaction processing unit S410~S440: Steps 500: Account generation screen 501: Menu 510: Account type directory 600: Shared account generation screen 601~604: Select 700: Account ownership screen 701: Shared accounts 710: Account ownership directory 820: Transaction type directory 930: Transaction content input screen 931: Menu 1000: Instant messaging software screen 1010: Pre-approved messages 1011~1012: Menu 1100: Shared member screen 1101~1103: Menu 1110: Member directory 1200: Shared member deletion screen 1201: Selection box 1202: Menu 1300: Master agent settings screen 1301: Selection box 1302: Menu

FIG. 1 is a diagram showing an example of a network environment according to an embodiment of the present invention.

FIG. 2 is a block diagram for illustrating the internal structure of an electronic device and a server according to an embodiment of the present invention.

FIG. 3 is a diagram showing an example of structural elements that may be included in a processor of an electronic device according to an embodiment of the present invention.

FIG. 4 is a flow chart showing an example of a method that can be performed by an electronic device according to an embodiment of the present invention.

5 to 6 show examples of screens of a user interface for explaining a process of generating a shared account according to an embodiment of the present invention.

7 to 10 show examples of screens of a user interface for explaining a process of handling pre-approval of transactions for a shared account according to an embodiment of the present invention.

11 to 13 show examples of screens of a user interface for explaining a process of managing members of a shared account according to an embodiment of the present invention.

S410~S440: Steps

Claims (20)

A shared account transaction method is performed in a computer device, wherein the computer device includes at least one processor that executes a plurality of computer-readable instructions contained in a memory, and the shared account transaction method includes: providing a first user interface by the at least one processor according to a request from a user of the computer device, wherein the first user interface displays an account category directory including shared accounts; providing a second user interface by the at least one processor according to a selection of the shared account in the account category directory, wherein the second user interface is used to set a generated account for the user to use; The computer device includes a computer device that is configured to transmit information required for a user to share usage details of the shared account with at least one member, wherein the information includes the at least one member selected from a friend list of an instant messaging software set in the computer device; a transmission step, in which the at least one processor transmits a pre-approved message for the transaction request to the computer device of the member through the instant messaging software when a transaction request of the shared account occurs; and an execution step, in which the at least one processor executes the pre-approved transaction of the shared account based on the member's response to the pre-approved message. A shared account transaction method as claimed in claim 1, wherein, in the transmitting step, the pre-approval message including at least one of the transaction amount and transaction purpose selected or input for the shared account transaction is transmitted. As in the shared account transaction method of claim 1, in the transmission step, when a settlement request is made using the shared account, the pre-approval message containing the settlement request information of the franchise store is transmitted. A shared account transaction method as in claim 1, wherein the pre-approval message is composed of the following action message, i.e., a user interface for inputting permission or rejection of the transaction request. As in the shared account transaction method of claim 1, wherein, in the sending step, if the transaction request meets the transaction conditions set in the shared account, the pre-approval message is sent. A shared account transaction method as claimed in claim 5, wherein, as a pre-determined rule for transactions requiring pre-approval, the transaction condition includes at least one of an industry category, amount or time related to the transaction. As in claim 5, the shared account transaction method, wherein, in the execution step, if the response to the pre-approval message meets the valid approval processing conditions set in the shared account, the pre-approved transaction of the shared account is allowed. A shared account transaction method as claimed in claim 7, wherein, as a pre-determined rule for the transaction, the valid approval processing condition includes at least one of the number of persons or the proportion of persons certified as valid approvals and the response time. A shared account transaction method as in claim 7, wherein the valid approval processing condition is set differently according to the transaction condition. As in claim 1, the shared account transaction method, wherein, in the execution step, the shared account transaction is allowed if the actual transaction content of the shared account corresponds to the transaction content pre-approved by the member. As in claim 1, the shared account transaction method further comprises the following step, namely, monitoring the transactions of the shared account by the at least one processor to provide the member's computer device with a reminder of the transaction corresponding to the predetermined improper use conditions. As in claim 11, the shared account transaction method, wherein in the providing step, in the shared account transaction, uncompleted pre-approved transactions are monitored, and whether the shared account is improperly used is determined based on at least one of the transaction time and the transaction location. As in claim 1, the shared account transaction method further comprises the following step, namely, when the user changes the settings related to the shared account, the at least one processor sends a pre-approval message for the setting change to the member's computer device. As in claim 1, the shared account transaction method further comprises the following step, namely, when there is a request from the user to delete or add a member of the shared account, the at least one processor transmits a pre-approval message related to member deletion or addition to the member's computer device. As in claim 1, the shared account transaction method further includes the following step, namely, by means of the at least one processor, among the members of the shared account, setting the member selected by the user as a temporary master agent with transaction permission for the shared account. A shared account trading method as claimed in claim 15, wherein, in the setting step, at least one of the transaction type, industry category, time and amount for which the master agent's permission is valid is set. As claimed in claim 15, the shared account transaction method further comprises the step of transmitting a pre-approval message related to the setting of the master agent to the member's computer device by the at least one processor. As in claim 1, the shared account transaction method further comprises the following steps, namely, by the at least one processor, based on the user sending a deposit request to the shared account, after the member completes the deposit, when a transaction request of the shared account occurs for a transaction related to the deposit request, the transaction related to the deposit request is executed without prior approval. A computer program product, wherein the program is stored in a computer-readable recording medium for executing the shared account transaction method of any one of claims 1 to 18 on a computer. A computer device, comprising at least one processor for executing computer-readable instructions contained in a memory, wherein the at least one processor provides a first user interface based on a request from a user of an electronic device, wherein the first user interface displays an account category directory including a shared account; and the at least one processor provides a second user interface based on a selection of the shared account in the account category directory, wherein the second user interface is used to set and generate a user interface for the user to communicate with at least one shared account. The information required for the shared account to be shared by at least one member of the computer device, wherein the information includes the at least one member selected from the friend list of the instant messaging software installed in the computer device. When a transaction request of the shared account occurs, the instant messaging software installed in the electronic device of the member sends a pre-approval message for the transaction request to the electronic device of the member, and the pre-approved transaction of the shared account is executed based on the response of the member to the pre-approval message.