JP2005173827A - Settlement server, settlement management system and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a settlement server and the like capable of performing settlement properly. <P>SOLUTION: A balance management DB 403 stores balance information of respective electronic moneys. A settlement control part 402 generates deposit information including a deposit amount to store it in a deposit management DB 404 for depositing a payment amount (a participation fee and the like) of the electronic money generated in a game server 11 before determination of a balance. The settlement control part 402 offsets a refund amount (prize money and the like) generated in the game server 11 before determination of the balance against the deposit amount in the deposit information. In determination of the balance, the settlement control part 402 updates the balance information of the balance management DB 403 on the basis of the deposit information stored in the deposit management DB 404. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a settlement server, a settlement management system, a settlement management method, and a program.

In recent years, network games (online games) using a game server or the like on the Internet have become widespread. Sales sites that sell digital contents such as music and video on the Internet are also widely known.
A user operates a game device, a personal computer, or the like to access these game servers or sales sites, play a network game, or download digital content. At this time, for example, prepaid electronic money is used as a settlement means.

  This electronic money is purchased (charged) by a user for a predetermined amount in advance, and used (consumed) in the same way as money for settlement on the Internet. Further, when the balance of electronic money decreases due to use, the balance can be increased by additional purchase (recharge) by the user.

In conventional network games, fees (participation fees, etc.) are simply deducted from electronic money, regardless of whether the game is won or lost. For this reason, even if the game was won, preferential treatment was not obtained, and there were many users who felt unsatisfactory in achievement.
In some cases, a company or the like that operates a network game may make a plan to provide prizes (such as book tickets) or prize money to game winners. In this case, it is necessary for the company side to send a prize to the registered address of the winner (user) or transfer the prize money to the designated account, which is not only complicated, but also causes additional expenses. As a result, companies tend to be reluctant to make such plans.

  Therefore, a settlement method for paying back the prize amount and the prize amount to the winner's electronic money is being tried as satisfying both the user side and the company side.

However, there are concerns that various problems may occur when such a payment method is actually performed.
For example, at the time of settlement, in addition to the withdrawal (withdrawal) process of electronic money, a new deposit (refund) process occurs, and the number of processes increases accordingly.
Further, in the case of introducing a service for cashing (cashing) electronic money, conventionally, there is no problem in cashing the remaining electronic money without increasing the balance. On the other hand, if the balance of prizes or prize money occurs and the balance of electronic money has increased from the time of purchase or additional purchase, the user can gain profits by cashing as if gambling. Will end up.
Furthermore, even if the prize is refunded, if the electronic money is used in a name other than the intended use, the meaning provided as the prize is lost.

  Therefore, it has been required to establish a settlement method that satisfies both the user side and the company side while solving these problems.

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a settlement server, a settlement management system, a settlement management method, and a program capable of performing appropriate settlement.

  The settlement server according to the first aspect of the present invention includes a balance information storage unit, a deposit information storage unit, a deposit information update unit, and a settlement unit, and is configured as follows.

  First, the balance information storage unit stores, for example, balance information for managing a balance that can be paid for electronic money. The deposit information storage unit stores deposit information for managing a payment amount generated until the balance is confirmed as a deposit amount.

  The deposit information update unit offsets the refund amount generated until the balance is settled with the deposit amount of the deposit information. For example, when the deposit amount and the refund amount (refund amount) are the same amount, the deposit information update unit deletes the deposit information from the deposit information storage unit. Then, the settlement unit updates the balance of the balance information based on the deposit information after offset when determining the balance.

  In this way, since the refund amount is offset with the deposit amount, it is possible to omit the settlement, and to appropriately reduce the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement.

  The settlement server may further include a balance management unit that manages a balance until a balance is determined as an amount obtained by subtracting a deposit amount of the deposit information from a balance of the balance information. In this case, since the balance management unit manages the balance in consideration of the deposit amount and the like, it is possible to prevent the occurrence of payment that causes a shortage of balance during settlement.

  A settlement server according to a second aspect of the present invention includes a balance information storage unit, a deposit information storage unit, a bond information storage unit, a settlement amount calculation unit, and a settlement unit, and is configured as follows.

  First, the balance information storage unit stores, for example, balance information for managing a balance that can be paid for electronic money. The deposit information storage unit stores deposit information for managing a payment amount generated until the balance is confirmed as a deposit amount. The claim information storage unit stores claim information for managing a refund amount generated until the balance is determined as a claim amount.

  The settlement amount calculation unit calculates the combined settlement amount by offsetting the deposit amount of the deposit information and the claim amount of the bond information when determining the balance. Then, the settlement unit updates the balance of the balance information based on the calculated settlement amount.

  In this way, it is possible to offset and collect the deposit amount and the amount of receivable generated until the balance is determined, and the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement can be appropriately reduced.

  The settlement server may further include a balance management unit that manages a balance until a balance is determined as an amount obtained by adding the amount of the credit to the balance of the balance information and further subtracting the deposit amount of the deposit information. . In this case, since the balance management unit manages the balance in consideration of the deposit amount and the amount of receivables, it is possible to prevent the occurrence of payment that causes a shortage of balance during settlement.

The balance information storage unit stores balance information including a specific use balance that can be paid for a specific use,
The deposit information storage unit stores deposit information including a deposit amount for a specific use,
The claim information storage unit stores claim information including a claim amount for a specific use,
The settlement amount calculation unit calculates a settlement amount for a specific use by offsetting a deposit amount for the specific use and a claim amount for the specific use,
The payment unit may update the specific use balance based on the calculated payment amount for the specific use. In this case, the amount specified as the specific application can be used appropriately.

  A payment management system according to a third aspect of the present invention is a payment management system including a game server that is communicably connected to a plurality of terminals, and a payment server that is communicably connected to the game server. The configuration is as follows.

The game server includes a game control unit and a processing request unit.
First, the game control unit controls a game played with each connected terminal. The processing request unit requests the payment server to process at least the payment collected at the start of the game and the refund paid at the end of the game.

On the other hand, the settlement server includes a balance information storage unit, a deposit information storage unit, a deposit information update unit, and a settlement unit.
First, the balance information storage unit stores, for example, balance information for managing a balance that can be paid for electronic money. The deposit information storage unit stores deposit information for managing, as a deposit amount, a payment generated at the game server until the balance is confirmed. Further, the deposit information update unit offsets the refund generated in the game server until the balance is confirmed with the deposit amount of the deposit information. For example, when the deposit amount and the refund amount (refund amount) are the same amount, the deposit information update unit deletes the deposit information from the deposit information storage unit. Then, the settlement unit updates the balance of the balance information based on the deposit information after offset when determining the balance.

  In this way, since the refund amount is offset with the deposit amount, it is possible to omit the amount of settlement, and the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement can be appropriately reduced.

  A payment management system according to a fourth aspect of the present invention is a payment management system including a game server that is communicably connected to a plurality of terminals, and a payment server that is communicably connected to the game server. The configuration is as follows.

The game server includes a game control unit and a processing request unit.
First, the game control unit controls a game played with each connected terminal. The processing request unit requests the payment server to process at least the payment collected at the start of the game and the refund paid at the end of the game.

On the other hand, the settlement server includes a balance information storage unit, a deposit information storage unit, a bond information storage unit, a settlement amount calculation unit, and a settlement unit.
First, the balance information storage unit stores, for example, balance information for managing a balance that can be paid for electronic money. The deposit information storage unit stores deposit information for managing, as a deposit amount, a payment generated in the game server until a balance is determined. The receivable information storage unit stores receivable information for managing the amount of reimbursement generated at the game server until the balance is determined as the amount of receivable. In addition, the settlement amount calculation unit calculates the combined settlement amount by offsetting the deposit amount of the deposit information and the claim amount of the claim information when determining the balance. Then, the settlement unit updates the balance of the balance information based on the calculated settlement amount.

  In this way, it is possible to offset and collect the deposit amount and the amount of receivable generated until the balance is determined, and the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement can be appropriately reduced.

  The settlement management method according to the fifth aspect of the present invention uses a balance information storage unit that stores balance information for managing balances that can be paid, and a deposit information storage unit that stores deposit information for managing deposit amounts. A settlement management method, which includes a deposit information storage step, a deposit information update step, and a settlement step, and is configured as follows.

  First, in the deposit information storage step, deposit information with the deposit amount generated until the balance is confirmed is stored in the deposit information storage unit. In the deposit information update step, the refund generated until the balance is settled is offset with the deposit amount of the deposit information. For example, when the deposit amount and the refund amount (refund amount) are the same amount, the deposit information update step deletes the deposit information from the deposit information storage unit. And a settlement step updates the balance of the said balance information based on the said deposit information after offset when finalizing a balance.

  In this way, since the refund amount is offset with the deposit amount, it is possible to omit the settlement, and to appropriately reduce the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement.

  A payment management method according to a sixth aspect of the present invention includes a balance information storage unit that stores balance information for managing balances that can be paid, a deposit information storage unit that stores deposit information for managing deposit amounts, A payment management method using a bond information storage unit for storing bond information for managing an amount, comprising a deposit information storage step, a bond information storage step, a payment amount calculation step, and a payment step, and is configured as follows To do.

  First, in the deposit information storage step, deposit information with the deposit amount generated until the balance is confirmed is stored in the deposit information storage unit. In the claim information storage step, the claim information storage unit stores the claim information in which the amount of the refund generated until the balance is determined is set as the amount of the claim. In the settlement amount calculation step, when the balance is determined, the deposit amount of the deposit information and the claim amount of the claim information are offset to calculate a combined settlement amount. In the settlement step, the balance of the balance information is updated based on the calculated settlement amount.

  In this way, it is possible to offset and collect the deposit amount and the amount of receivable generated until the balance is determined, and the number of deposit / withdrawal processing (payment / withdrawal processing) at the time of settlement can be appropriately reduced.

  A program according to a seventh aspect of the present invention is configured to cause a computer (including an electronic device) to function as the above settlement server.

  This program can be recorded on a computer-readable information recording medium such as a compact disk, flexible disk, hard disk, magneto-optical disk, digital video disk, magnetic tape, and semiconductor memory.

  The above program can be distributed and sold via a computer communication network independently of the computer on which the program is executed. The information recording medium can be distributed and sold independently of the computer.

  According to the present invention, appropriate settlement can be performed.

  Embodiments of the present invention will be described below. In the following, for ease of understanding, an embodiment in which the present invention is applied to a game device will be described. However, the present invention can be similarly applied to information processing devices such as various computers, PDAs, and mobile phones. it can. That is, the embodiment described below is for explanation, and does not limit the scope of the present invention. Therefore, those skilled in the art can employ embodiments in which each or all of these elements are replaced with equivalent ones, and these embodiments are also included in the scope of the present invention.

(Embodiment 1)
FIG. 1 is a schematic diagram showing an example of a schematic configuration of the settlement management system according to the first embodiment of the present invention. Hereinafter, a description will be given with reference to FIG.

  As an example, the payment management system 10 is a system that manages payments in a network game, and a game server 11 that controls execution of a game and the like is arranged on the Internet 14. The game server 11 is connected to a settlement server 12 that manages the balance of electronic money. The plurality of terminals 13 in the payment management system 10 are connected to the game server 11 via the Internet 14 so as to be communicable. Note that communication between the terminals 13 can also be performed by a so-called peer-to-peer communication technique. In order to facilitate understanding, a game device that can be connected to the Internet as the terminal 13 will be described below as an example.

  FIG. 2 is a schematic diagram showing a schematic configuration of a game device that functions as the terminal 13 of the present embodiment. Hereinafter, a description will be given with reference to FIG.

  The game apparatus 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, an interface 104, a controller 105, an external memory 106, and a DVD (Digital Versatile Disk). ) -ROM drive 107, image processing unit 108, audio processing unit 109, and NIC (Network Interface Card) 110.

  Note that a DVD-ROM storing a game program and data is loaded into the DVD-ROM drive 107 and the game apparatus 100 is turned on to execute the program, thereby realizing the terminal of the present embodiment. The

  The CPU 101 controls the overall operation of the game apparatus 100 and is connected to each component to exchange control signals and data.

  The ROM 102 records an IPL (Initial Program Loader) that is executed immediately after the power is turned on, and when this is executed, the program recorded on the DVD-ROM is read out to the RAM 103 and execution by the CPU 101 is started. The The ROM 102 stores an operating system program and various data necessary for operation control of the entire game apparatus 100.

  The RAM 103 is for temporarily storing data and programs, and holds programs and data read from the DVD-ROM and other data necessary for game progress and chat communication.

  The controller 105 connected via the interface 104 receives an operation input performed when the user executes the game. For example, the controller 105 accepts input of a character string (message) or the like according to the operation input.

  The external memory 106 detachably connected via the interface 104 stores data indicating the progress of the game, chat communication log (record) data, and the like in a rewritable manner. The user can record these data in the external memory 106 as appropriate by inputting an instruction via the controller 105.

  A DVD-ROM mounted on the DVD-ROM drive 107 stores a program for realizing the game and image data and sound data associated with the game. Under the control of the CPU 101, the DVD-ROM drive 107 performs a reading process on the DVD-ROM loaded therein, reads out necessary programs and data, and these are temporarily stored in the RAM 103 or the like.

  The image processing unit 108 processes the data read from the DVD-ROM by the CPU 101 or an image arithmetic processor (not shown) included in the image processing unit 108, and then processes the processed data on a frame memory ( (Not shown). The image information recorded in the frame memory is converted into a video signal at a predetermined synchronization timing and output to a monitor (not shown) connected to the image processing unit 108. Thereby, various image displays are possible.

The image calculation processor can execute a two-dimensional image overlay calculation, a transmission calculation such as α blending, and various saturation calculations at high speed.
In addition, the polygon information arranged in the virtual three-dimensional space and added with various texture information is rendered by the Z buffer method, and a rendering image obtained by overlooking the polygon arranged in the virtual three-dimensional space from a predetermined viewpoint position is obtained. High speed execution of the obtained operation is also possible.

  Further, the CPU 101 and the image arithmetic processor operate in a coordinated manner, so that a character string can be drawn as a two-dimensional image in a frame memory or drawn on the surface of each polygon according to font information that defines the character shape. is there. The font information is recorded in the ROM 102, but it is also possible to use dedicated font information recorded in the DVD-ROM.

  The audio processing unit 109 converts audio data read from the DVD-ROM into an analog audio signal, and outputs the analog audio signal from a speaker (not shown) connected thereto. Further, under the control of the CPU 101, sound effects and music data to be generated during the progress of the game are generated, and sound corresponding to this is output from the speaker.

  The NIC 110 is for connecting the game apparatus 100 to a computer communication network (not shown) such as the Internet, and conforms to the 10BASE-T / 100BASE-T standard used when configuring a LAN (Local Area Network). Therefore, analog modems for connecting to the Internet using telephone lines, ISDN (Integrated Services Digital Network) modems, ADSL (Asymmetric Digital Subscriber Line) modems, cables for connecting to the Internet using cable television lines A modem or the like, and an interface (not shown) that mediates between them and the CPU 101 are configured.

In addition, the game apparatus 100 uses a large-capacity external storage device such as a hard disk so that the ROM 102, the RAM 103, the external memory 106, the DVD-ROM attached to the DVD-ROM drive 107, and the like function. It may be configured.
Further, it is possible to adopt a form in which a keyboard for accepting a character string editing input from a user, a mouse for accepting various position designations and selection inputs, and the like are connected.

  Further, instead of the game apparatus 100 of the present embodiment, a general computer (a general-purpose personal computer or the like) can be used. For example, a general computer, like the game apparatus 100, includes a CPU, RAM, ROM, DVD-ROM drive, and NIC, and an image processing unit that has simpler functions than the game apparatus 100. In addition to having a hard disk as an external storage device, a flexible disk, a magneto-optical disk, a magnetic tape, and the like can be used. In addition, a keyboard, a mouse or the like is used as an input device instead of a controller.

  In consideration of the fact that network games often use not only game machines but also general computers, unless otherwise noted, the terminal will be described with reference to the game apparatus 100 shown in FIG. These can be appropriately replaced with general computer elements as necessary, and these embodiments are also included in the scope of the present invention.

  The game server 11 and the settlement server 12 are realized on a general computer, but a predetermined game device 100 in the group of game devices 100 may be used as the game server 11 and the settlement server 12. Is possible. The game apparatus 100 and a general computer are not greatly different in configuration and function. That is, the game server 11 and the settlement server 12 of the present invention can be realized by the game device 100. Therefore, in the following description, a general computer and the game apparatus 100 are handled in the same way.

(Game server configuration and operation)
FIG. 3 is a schematic diagram illustrating an example of a schematic configuration of the game server 11 according to the present embodiment. FIG. 4 is a flowchart showing a flow of game control processing executed by the game server 11. Hereinafter, description will be given with reference to these drawings.
As an example, a case will be described in which the game server 11 controls a battle game performed between a plurality of users (a plurality of terminals 13). When the user plays the battle game, a predetermined amount of participation fee is required, and the participation fee is refunded to the winner of the game.

  As shown in FIG. 3, the game server 11 includes an authentication unit 201, a user information storage unit 202, a game control unit 203, a game information storage unit 204, and a charge management unit 205.

The authentication unit 201 receives login information sent from the terminal 13 before authenticating the user, and authenticates the user using information stored in the user information storage unit 202.
For example, when receiving the login information including the user ID and the password, the authentication unit 201 compares the user information stored in the user information storage unit 202 and can authenticate the user only when they match.

The user information storage unit 202 stores user information related to each user in advance.
For example, the user information storage unit 202 stores user information including a user ID for identifying a user, a password, a handle name, and a money ID for identifying electronic money used by the user.

The game control unit 203 exchanges predetermined information with the user (terminal 13) authenticated by the authentication unit 201.
For example, the game control unit 203 receives instruction information sent from each terminal 13 of the user (player) who plays the game, and controls the battle game according to the received instruction information. Then, information indicating the control result (game progress status, etc.) is sequentially transmitted to each terminal 13.

The game information storage unit 204 stores information on each player, network information of the terminal 13 of each player, and the like.
For example, the game information storage unit 204 stores the user ID and handle name of each player, and stores the IP address and MAC address of each terminal 13. In addition to this, the game information storage unit 204 also stores various information necessary for controlling the battle game.

  The charge management unit 205 requests the payment server 12 to deposit the participation fee of the player. Further, when the game is over, the payment server 12 is requested to refund the participation fee to the winning player (cancellation of deposit). Then, the settlement server 12 is requested to execute the settlement process.

  The game server 11 having such a configuration executes a game control process shown in FIG. 4 in response to a request from the terminal 13 operated by the user. Hereinafter, this game control process will be described.

First, the authentication unit 201 stands by until login information that can be sent from the terminal 13 is received before user authentication (step S301; No).
For example, the authentication unit 201 is accessed from the terminal 13 operated by a user who intends to play a competitive game, and waits until login information including a user ID and a password is transmitted from the terminal 13.

When receiving the login information (step S301; Yes), the authentication unit 201 authenticates the user using the user information stored in the user information storage unit 202 (step S302).
When the user is authenticated, the authentication unit 201 notifies the game control unit 203 of the network information (IP address, MAC address, etc.) of the user's terminal 13 and communicates between the game control unit 203 and the terminal 13. to approve. Further, the money ID registered in the user information storage unit 202 is specified as electronic money used by the user.
If the user is not authenticated due to an illegal password or the like, the authentication unit 201 transmits a message indicating that authentication cannot be performed to the terminal 13 and waits for reception of login information again.

After the user is authenticated, the game control unit 203 acquires balance information from the settlement server 12 via the charge management unit 205 (step S303).
For example, the billing management unit 205 transmits balance reference request information including a money ID to the settlement server 12 and requests a return of balance information of electronic money. In response to this, the settlement server 12 reads target balance information from a balance management DB 403 described later, and returns it to the charge management unit 205. When the balance management unit 205 receives the balance information, the billing management unit 205 supplies the balance control unit 205 to the game control unit 203.

  The game control unit 203 determines whether or not the balance of electronic money is sufficient based on the balance information (step S304). That is, it is determined whether or not the current balance of the balance information is equal to or greater than the participation fee.

  If the game control unit 203 determines that the balance of the electronic money is not sufficient (step S304; No), the process returns to the above-described step S301 without allowing the user to participate in the game.

On the other hand, when it is determined that the balance of the electronic money is sufficient (step S304; Yes), the game control unit 203 registers the player and controls the charging management unit 205 to deposit the participation fee (step S305). ).
For example, the billing management unit 205 generates deposit request information including a game number, money ID, date and time of occurrence, and deposit amount (participation fee), and transmits the deposit request information to the settlement server 12. In response to this, the settlement server 12 stores the deposit information in the deposit management DB 404 described later.
At the time of player registration, the game information storage unit 204 stores a user ID, a handle name, an IP address of the terminal 13, and the like.

The game control unit 203 determines whether or not the battle game can be started (step S306).
For example, the game control unit 203 determines that the battle game can be started when the required number of players are registered and the communication state of each player with the terminal 13 is good.
When determining that the game cannot be started (step S306; No), the game control unit 203 returns the process to step S301, and repeatedly executes the processes of steps S301 to S306 described above.

On the other hand, when it is determined that the game can be started (step S306; Yes), the game control unit 203 starts the battle game and controls the battle game according to the instruction information sent from the terminal 13 of each player ( Step 307).
At this time, the game control unit 203 transmits information indicating the progress of the battle game being controlled to the terminal 13 of each player.

The game control unit 203 determines whether or not the battle game has ended (step S308).
For example, it is determined whether or not a winning or losing decision has been made based on the rules of the competitive game.
If it is determined that the game has not ended (step S308; No), the game control unit 203 continues to control the battle game in step S307.

On the other hand, when it is determined that the game has ended (step S308; Yes), the game control unit 203 requests settlement by canceling the deposit of the winner via the charge management unit 205 (step S309).
For example, the charge management unit 205 generates cancellation request information including a game number and a winner's money ID, and transmits the cancellation request information to the settlement server 12. In response to this, the settlement server 12 deletes the target deposit information from the deposit management DB 404 described later.
Subsequently, the charge management unit 205 generates payment request information including the game number and transmits it to the payment server 12. In response to this, the settlement server 12 updates the balance management DB 403 (to be described later) using the target deposit information stored in the deposit management DB 404 (to be described later).

By such a game control process, the game server 11 temporarily deposits the participation fee until the game is finished, and after the game is finished and the participation fee is refunded (cancellation of the deposit), the settlement is made. Request.
For this reason, it is possible to eliminate the settlement of the offset amount (winner's participation fee) and appropriately reduce the number of deposit / withdrawal processing (payment / withdrawal processing) in the settlement server 12.

(Configuration and operation of payment server)
FIG. 5 is a schematic diagram illustrating an example of a schematic configuration of the settlement server 12 according to the present embodiment. FIG. 6 is a schematic diagram showing an example of balance information stored in the balance management DB (database) 403 of the settlement server 12. FIG. 7 is a schematic diagram showing an example of deposit information stored in the deposit management DB 404 of the settlement server 12.
FIG. 8 is a flowchart showing the flow of the payment management process executed by the payment server 12. Hereinafter, description will be given with reference to these drawings.

  As shown in FIG. 5, the payment server 12 includes a request receiving unit 401, a payment control unit 402, a balance management DB 403, a deposit management DB 404, and a balance information transmission unit 405.

  The request receiving unit 401 receives various request information sent from the game server 11. For example, the request reception unit 401 includes balance reference request information for requesting reference to the balance of electronic money, deposit request information for requesting deposit such as a participation fee, cancel information for requesting cancellation of deposit, and a settlement request for requesting settlement. Accept information etc. Then, the received request information is supplied to the settlement control unit 402.

The settlement control unit 402 executes predetermined processing in response to the request information supplied from the game server 11 via the request receiving unit 401.
For example, when the balance reference is requested, the settlement control unit 402 reads the balance information of the target electronic money from the balance management DB 403 and transmits it to the game server 11 via the balance information transmission unit 405.
Further, when deposit is requested, deposit information is added to the deposit management DB 404 and stored. When the deposit cancellation is requested, the target deposit information is deleted from the deposit management DB 404.
Furthermore, when payment is requested, based on the deposit information stored in the deposit management DB 404, the balance information of the target electronic money in the balance management DB 403 is updated.

The balance management DB 403 stores balance information for managing the balance of each electronic money, for example, as shown in FIG.
This balance information includes a money ID for identifying the electronic money, a current balance indicating the current balance of the electronic money, a balance at the time of purchase that defines an upper limit for cashing (cashing), and the like.

As shown in FIG. 7, the deposit management DB 404 stores deposit information for managing deposit contents, for example.
This deposit information includes a unique game number assigned for each game, a money ID for identifying electronic money, a deposit occurrence date and time, a deposit amount (participation fee, etc.), and the like.

  Returning to FIG. 5, the balance information transmission unit 405 transmits the balance information to the game server 11 when the balance reference is requested and the target balance information is read from the balance management DB 403 by the settlement control unit 402. .

  The settlement server 12 having such a configuration stores the balance at the time of purchase in the balance management DB 403 so that when the current balance of electronic money is cashed (cashed), the amount higher than the balance at the time of purchase cannot be cashed. , Preventing gambling-like benefits for the user. After cashing, the purchase balance is deducted accordingly. In addition, when an additional purchase is made, the purchase balance increases accordingly.

  Further, the settlement server 12 sequentially executes the settlement management process shown in FIG. 8 in response to the request information sent from the game server 11 that executes the above-described game control process. Hereinafter, the settlement management process will be described.

  First, the request reception unit 401 receives request information sent from the game server 11 (step S501). The request reception unit 401 supplies the received request information to the settlement control unit 402.

The settlement control unit 402 determines whether or not the request information is balance reference request information for requesting reference of the balance (step 502).
If the settlement control unit 402 determines that it is balance reference request information (step S502; Yes), it acquires target balance information from the balance management DB 403 (step S503).
For example, the settlement control unit 402 searches the balance management DB 403 using the money ID included in the balance reference request information as a key, and reads the balance information of the target electronic money.
When the payment control unit 402 acquires the balance information, the payment control unit 402 transmits the acquired balance information to the game server 11 via the balance information transmission unit 405 (step 504).

On the other hand, when it is determined that the information is not balance reference request information (step S502; No), the settlement control unit 402 determines whether the information is deposit request information for requesting deposit (step S505).
If the settlement control unit 402 determines that it is deposit request information (step S505; Yes), it adds the deposit information to the deposit management DB 404 and stores it (step S506).
For example, the settlement control unit 402 generates deposit information including a game number, a money ID, an occurrence date and a deposit amount based on the deposit request information, and stores the deposit information in the deposit management DB 404 as shown in FIG.

On the other hand, when it is determined that the information is not deposit request information (step S505; No), the settlement control unit 402 determines whether the request is cancel request information for requesting cancel of deposit (step S507).
If the settlement control unit 402 determines that the request is cancellation request information (step S507; Yes), it deletes the target deposit information from the deposit management DB 404 (step S508).
For example, the settlement control unit 402 searches the deposit management DB 404 as shown in FIG. 7 using the game number and money ID included in the cancellation request information as keys, and sets the target deposit information (winner deposit information). delete.

On the other hand, when it is determined that the information is not cancellation request information (step S507; No), the payment control unit 402 determines whether the information is payment request information for requesting payment (step S509).
If the payment control unit 402 determines that the payment request information is payment request information (step S509; Yes), it acquires the target deposit information from the deposit management DB 404 (step S510).
For example, the settlement control unit 402 searches the deposit management DB 404 as shown in FIG. 7 using the game number included in the settlement request information as a key, and reads out all the deposit information as targets.

The settlement control unit 402 updates the balance information in the balance management DB 403 according to each read deposit information (step S511).
For example, the deposit control unit 402 reads target balance information from the balance management DB 403 as shown in FIG. 6 using the money ID of the deposit information as a key. Then, the current balance (balance information) is updated by subtracting the deposit amount (participation fee) of the deposit information from the current balance of the read balance information.

  If it is determined in step S509 that the information is not settlement request information (step S509; No), the settlement control unit 402 ends the settlement management process without performing any processing because it is not assumed request information.

With such a payment management process, the payment server 12 manages the participation fee requested from the game server 11 as deposit information in the deposit management DB 404. Then, after the game is finished on the game server 11 and the participation fee is refunded to the winner (deposit information is deleted), the remaining deposit information is used to make a settlement.
For this reason, it is possible to eliminate the settlement of the offset amount (payment / withdrawal for the winner's participation fee), and appropriately reduce the number of deposit / withdrawal processing (payment / withdrawal processing) in the settlement server 12.

(Embodiment 2)
In the first embodiment described above, a case has been described in which the participation fee is paid back to the game winner as it is (cancellation of deposit information), but a predetermined amount of prize money may be paid back to the game winner. In the first embodiment, payment is made at the same time as one game is finished. However, payment may be made collectively when a predetermined number of games are finished.
Hereinafter, a settlement management system according to the second embodiment of the present invention will be described.

(Game server operation)
In the present embodiment, the game server 11 has the same configuration as shown in FIG. Nevertheless, unlike FIG. 4, the game server 11 executes the game control process shown in FIG. In the game control process of FIG. 9, the user authentication portion is omitted, but it is assumed that user authentication is performed in the same manner as in FIG. Hereinafter, the game control process of FIG. 9 will be described.

First, the game control unit 203 waits until receiving participation information sent from the terminal 13 of the user participating in the game (step S601; No).
When the game control unit 203 receives the participation information (step S601; Yes), the game control unit 203 requests the settlement server 12 to return the balance information (balance information considering the deposit information and the like) via the billing management unit 205 (step S602). . That is, the balance reference request information including the money ID is transmitted to the settlement server 12.

  In response to this, the settlement server 12 searches the deposit management DB 404 and the bond management DB 701 (to be described later) for the target deposit information and bond information (information such as prize money to be paid back), and calculates the correct current balance at the present time. Then, the balance information including the calculated current balance is transmitted to the charge management unit 205.

  The game control unit 203 determines whether or not the balance of electronic money is sufficient based on the balance information (step S603). If the game control unit 203 determines that the balance of electronic money is not sufficient (step S603; No), the game control unit 203 returns the process to step S601 described above without allowing the user to participate in the game.

  On the other hand, when it is determined that the balance of the electronic money is sufficient (step S603; Yes), the game control unit 203 registers the player and requests the payment server 12 to deposit the participation fee (step S604). In response to this, the settlement server 12 adds deposit information to the deposit management DB 404 and stores it.

  The game control unit 203 determines whether or not the battle game can be started (step 605). If the game control unit 203 determines that the game cannot be started (step S605; No), the process returns to step S601, and the above-described steps S601 to S605 are repeatedly executed.

  On the other hand, when it is determined that the game can be started (step S605; Yes), the game control unit 203 starts the battle game and controls the battle game according to the instruction information sent from the terminal 13 of each player ( Step 606).

  The game control unit 203 determines whether or not the battle game has ended (step S607). If the game control unit 203 determines that the game has not ended (step S607; No), the game control unit 203 continues to control the game in step S606.

On the other hand, when it is determined that the game is over (step S607; Yes), the game control unit 203 requests the payment server 12 to pay out the prize money (step S608).
For example, the charge management unit 205 generates credit request information including a game number, a money ID, an occurrence date and a credit amount (award amount), and transmits it to the settlement server 12. In response to this, the settlement server 12 adds and stores bond information in a bond management DB 701 described later.

The game control unit 203 determines whether or not a predetermined number of games have been completed (step S609).
If the game control unit 203 determines that the predetermined number of games have not ended (step S609; No), the process returns to step S601, and the above-described steps S601 to S609 are repeatedly executed.

On the other hand, when it is determined that a predetermined number of games have been completed (step S609; Yes), the game control unit 203 requests the payment server 12 to make a payment (step S610).
For example, the billing management unit 205 generates payment request information including a series of game numbers (a predetermined number of game numbers) and transmits the payment request information to the payment server 12. In response to this, the settlement server 12 updates the balance management DB 403 using the target deposit information and bond information stored in the deposit management DB 404 and the bond management DB 701.

  By such a game control process, the game server 11 causes the settlement server 12 to manage the participation fee as deposit information, and also manages the winnings to be paid back as bond information. Then, when the predetermined number of games are completed, the settlement server 12 is requested to perform settlement using these deposit information and bond information.

(Configuration and operation of payment server)
FIG. 10 is a schematic diagram illustrating an example of a schematic configuration of the settlement server 12 according to the present embodiment. That is, in this embodiment, the settlement server 12 further includes a bond management DB 701 in addition to the configuration shown in FIG. FIG. 11 is a schematic diagram showing an example of bond information stored in the bond management DB 701.
FIG. 12 is a flowchart showing the flow of the payment management process executed by the payment server 12. Hereinafter, description will be given with reference to these drawings.

  As shown in FIG. 10, the settlement server 12 further includes a claim management DB 701 in addition to the request reception unit 401 to the balance information transmission unit 405.

As shown in FIG. 11, the claim management DB 701 stores, for example, claim information for managing the contents of the claim.
This bond information includes a unique game number assigned to each game, a money ID for identifying electronic money, a date and time when a bond is generated, a generated bond amount, and the like.

  The settlement server 12 having such a configuration sequentially executes the settlement management process shown in FIG. 12 in response to the request information sent from the game server 11 that executes the game control process of FIG. 9 described above. Hereinafter, the settlement management process shown in FIG. 12 will be described.

  First, the request reception unit 401 receives request information sent from the game server 11 (step S801). Note that the request reception unit 401 also receives refund request information for requesting a refund of prize money.

The settlement control unit 402 determines whether the request information is balance reference request information (step 802).
If the settlement control unit 402 determines that it is balance reference request information (step S802; Yes), it acquires target balance information from the balance management DB 403 (step S803).

Subsequently, the settlement control unit 402 searches for deposit information from the deposit management DB 404 (step S804).
For example, the settlement control unit 402 searches the deposit management DB 404 using the money ID included in the balance reference request information as a key, and reads the retrieved deposit information. In addition, when a plurality of deposit information is searched, each deposit information is read.

Further, the settlement control unit 402 searches for bond information from the bond management DB 701 (step S805).
For example, the settlement control unit 402 similarly searches the claim management DB 701 using the money ID as a key, and reads the found claim information. In addition, when a plurality of bond information is searched, each bond information is read out.

  The settlement control unit 402 corrects the balance information (current balance) based on the read deposit information and bond information, and transmits the corrected balance information to the game server 11 via the balance information transmission unit 405 (step 806). ). If no deposit information or bond information is searched, the balance information (current balance) is transmitted to the game server 11 without being corrected.

If it is determined in step S802 that the request is not balance reference request information (step S802; No), the settlement control unit 402 determines whether the request information is deposit request information (step S807).
If the settlement control unit 402 determines that it is deposit request information (step S807; Yes), it adds the deposit information to the deposit management DB 404 and stores it (step S808).

On the other hand, when it is determined that the information is not deposit request information (step S807; No), the settlement control unit 402 determines whether the request is refund request information for requesting a payout of a prize (step S809).
If the settlement control unit 402 determines that it is refund request information (step S809; Yes), it adds and stores bond information in the bond management DB 701 (step S810).
For example, the settlement control unit 402 generates bond information including a game number, a money ID, an occurrence date and a bond amount according to the refund request information, and stores the bond information in the bond management DB 701 as shown in FIG.

On the other hand, when it is determined that the request information is not refund request information (step S809; No), the settlement control unit 402 determines whether the request information is settlement request information (step S811).
If the settlement control unit 402 determines that it is settlement request information (step S811; Yes), it acquires a plurality of deposit information from the deposit management DB 404 (step S812).
For example, the settlement control unit 402 searches the deposit management DB 404 using a series of game numbers included in the settlement request information as a key, and reads out all the deposit information as targets.

Subsequently, the settlement control unit 402 acquires a plurality of pieces of bond information from the bond management DB 701 (step S813).
For example, the settlement control unit 402 similarly searches the credit management DB 701 using a series of game numbers as keys, and reads all target credit information.

  The settlement control unit 402 matches and cancels the deposit information (deposit amount) and the claim information (deposit amount) that have the same money ID, and generates each settlement information (step S814). That is, the deposit amount and the claim amount are totaled for each money ID, and the settlement amount of each electronic money is calculated by subtracting the tabulated deposit amount from the tabulated claim amount. In this case, when the payment amount is negative, the payment information is withdrawn. Conversely, when the payment amount is positive, the payment is payment information. If the payment amount is exactly zero, payment information need not be generated.

  And the payment control part 402 updates the balance information of balance management DB403 based on each produced | generated payment information (step S815). That is, the current balance of each corresponding balance information is updated.

  If it is determined in step S811 that the request is not settlement request information (step S811; No), the settlement control unit 402 ends the settlement management process without performing any processing because it is not assumed request information.

With such a payment management process, the payment server 12 manages the participation fee as deposit information in the deposit management DB 404 and manages the payout money to be paid back as bond information in the bond management DB 701. Then, after a predetermined number of games are completed on the game server 11, the deposit information and the bond information are matched and offset, and the combined settlement is performed.
For this reason, the payment amount can be combined into one for each electronic money, and the number of deposit / withdrawal processing (payment / withdrawal processing) in the settlement server 12 can be appropriately reduced.

(Other embodiments)
In the second embodiment described above, the case where the payment server 12 is requested to make a payment every time a predetermined number of games are completed on the game server 11 has been described. However, the payment server 12 manages the payment deadline by itself. Alternatively, the payment may be made at the timing when the deadline has passed.
For example, the settlement server 12 may collectively settle each electronic money using deposit information and bond information generated during the month at the end of the month.
Hereinafter, the settlement operation of the settlement server according to another embodiment of the present invention will be described.

(Payment operation of payment server)
In the present embodiment, the settlement server 12 has the same configuration as that shown in FIG. Nevertheless, the settlement server 12 executes a collective settlement process as shown in FIG. 13 at the end of the month. Hereinafter, the collective settlement process will be described.

First, the settlement control unit 402 acquires one piece of balance information from the balance management DB 403 in a predetermined order (step S901).
The settlement control unit 402 searches for deposit information from the deposit management DB 404 using the money ID included in the acquired balance information as a key (step S902).

The settlement control unit 402 determines whether the deposit information has been searched (step S903). If the settlement control unit 402 determines that no deposit information has been searched (step S904; No), the settlement control unit 402 sets the total deposit amount to zero (step S904).
On the other hand, when it is determined that the deposit information has been searched (step S903; Yes), the settlement control unit 402 counts the deposit amount from each searched deposit information (step S905).

  Similarly, the settlement control unit 402 searches for the claim information from the claim management DB 701 using the money ID as a key (step S906). The settlement control unit 402 determines whether the bond information has been searched (step S907).

If the settlement control unit 402 determines that no claim information has been retrieved (step S907; No), the settlement control unit 402 sets the total amount of claims to be zero (step S908).
On the other hand, when it is determined that the claim information has been searched (step S907; Yes), the settlement control unit 402 adds up the amount of claims from each searched claim information (step S909).

The settlement control unit 402 calculates the settlement amount and updates the balance information (step S910).
Specifically, the settlement control unit 402 subtracts the deposit amount from the total amount of receivables, and calculates a settlement amount in which the settlement amounts during the month are collected together.
If the settlement amount is negative, the payment settlement information is used. Conversely, if the settlement amount is positive, the payment settlement information is used.
Then, the payment management unit 402 updates the balance information (current balance) in the balance management DB 403 based on the calculated payment amount. If the settlement amount is zero, it is not necessary to perform settlement.

The settlement management unit 402 determines whether or not all settlements have been completed (step S911). If the payment management unit 402 determines that all payments have not been completed (step S911; No), the process returns to step S901, and the above-described steps S901 to S911 are repeatedly executed.
On the other hand, when it is determined that all payments have been completed (step S911; Yes), the payment management unit 402 ends the collective payment process.

  By such a collective payment process, the payment server 12 matches and cancels the participation fee and the prize money generated during the month, and collects the payment amount in units of electronic money. Since the settlement is performed based on the settlement amount summarized in this way, the number of processing of the deposit / withdrawal process (payment / withdrawal process) can be appropriately reduced.

In the above embodiment, the case where the prize is paid back to the winner of the game has been described. However, instead of the prize, the amount of the prize (amount limited to a specific use) is refunded, It is also applicable as appropriate when a limited amount is deposited (used).
In this case, the balance information managed by the balance management DB 403 separately includes a balance limited in usage (for example, usage A balance, usage B balance, etc.) as shown in FIG. .
In addition, the deposit information managed by the deposit management DB 404 includes a deposit amount for limited use (for example, use A and use B) separately as shown in FIG. In addition, the receivable information managed by the receivable management DB 701 separately includes a receivable amount (for example, use A or use B) whose use is limited, as shown in FIG.

  Then, when executing the above-described settlement management process (at the time of settlement) in FIG. 12 and the above-described collective settlement process in FIG. 13, the settlement server 12 performs a settlement by matching these limited applications. For example, the deposit amount for use A of the deposit information and the amount of claim for use A of the claim information are matched and offset, and the settlement amount in which usage A is collected is calculated. Similarly, the deposit amount for usage B and the amount of claim for usage B are matched and offset, and the settlement amount in which usage B is collected is calculated. Then, the balance whose usage of the balance information is limited is updated. In addition, when the balance for which the usage is limited is insufficient, the balance is replenished from the current balance for which the usage is not limited.

  As described above, according to the present invention, appropriate settlement can be performed.

It is a mimetic diagram showing the outline composition of the settlement management system of this embodiment. It is a schematic diagram which shows an example of schematic structure of a game device. It is a schematic diagram which shows an example of schematic structure of the game server which concerns on 1st Embodiment. It is a flowchart which shows the flow of the game control process performed with the said game server. It is a schematic diagram which shows an example of schematic structure of the payment server which concerns on 1st Embodiment. It is a schematic diagram which shows an example of the balance information memorize | stored in the balance management DB of the said payment server. It is a schematic diagram which shows an example of the deposit information memorize | stored in the deposit management DB of the said payment server. It is a flowchart which shows the flow of the payment management process performed with the said payment server. It is a flowchart which shows the flow of the game control process performed with the game server which concerns on 2nd Embodiment. It is a schematic diagram which shows an example of schematic structure of the payment server which concerns on 2nd Embodiment. It is a schematic diagram which shows an example of the claim information memorize | stored in the claim management DB of the said payment server. It is a flowchart which shows the flow of the payment management process performed with the said payment server. It is a flowchart which shows the flow of the collective payment process performed with the said payment server. It is a schematic diagram which shows an example of the information memorize | stored in DB of the payment server which concerns on other embodiment, Comprising: (a) is balance information memorize | stored in balance management DB, (b) is in deposit management DB. The deposit information is stored, and (c) is the bond information stored in the bond management DB.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Payment management system 11 Game server 12 Payment server 13 Terminal 14 Internet 100 Game device 101 CPU
102 ROM
103 RAM
104 Interface 105 Controller 106 External Memory 107 DVD-ROM Drive 108 Image Processing Unit 109 Audio Processing Unit 110 NIC
DESCRIPTION OF SYMBOLS 201 Authentication part 202 User information storage part 203 Game control part 204 Game information storage part 205 Charge management part 401 Request reception part 402 Payment control part 403 Balance management DB
404 Deposit Management DB
405 Balance information transmission unit 701 Claim management DB

Claims (11)

A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing payments made until the balance is confirmed as deposit amounts;
A deposit information update unit that offsets the refund amount that has occurred until the balance is confirmed, and the deposit amount of the deposit information;
A settlement unit that updates the balance of the balance information based on the deposit information after offset when determining the balance;
A payment server characterized by that. The payment server according to claim 1,
A balance management unit for managing the balance until the balance is confirmed as an amount obtained by subtracting the deposit amount of the deposit information from the balance of the balance information;
It is characterized by that. A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing payments made until the balance is confirmed as deposit amounts;
A receivable information storage unit for storing receivable information for managing the amount of reimbursement generated until the balance is confirmed as a receivable amount;
A settlement amount calculation unit for calculating the total settlement amount by offsetting the deposit amount of the deposit information and the claim amount of the claim information when determining the balance;
A payment unit that updates the balance of the balance information based on the calculated payment amount;
A payment server characterized by that. The payment server according to claim 3,
A balance management unit for managing the balance until the balance is confirmed as an amount obtained by adding the amount of the claim to the balance of the balance information and further subtracting the deposit amount of the deposit information;
It is characterized by that. The payment server according to claim 3,
The balance information storage unit stores balance information including a specific use balance that can be paid for a specific use,
The deposit information storage unit stores deposit information including a deposit amount for a specific use,
The claim information storage unit stores claim information including a claim amount for a specific use,
The settlement amount calculation unit calculates a settlement amount for a specific use by offsetting a deposit amount for the specific use and a claim amount for the specific use,
The settlement unit updates the specific use balance based on the calculated specific use settlement amount.
It is characterized by that. A payment management system comprising: a game server communicatively connected to a plurality of terminals; and a payment server communicatively connected to the game server,
The game server
A game control unit that controls a game performed between each connected terminal;
A processing request unit for requesting the payment server to process at least a payment collected at the start of the game and a refund paid at the end of the game;
The payment server
A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing a payment amount generated in the game server as a deposit amount until a balance is determined;
A deposit information update unit that offsets the refund generated in the game server until the balance is confirmed, and the deposit amount of the deposit information;
A settlement unit that updates the balance of the balance information based on the deposit information after offset when determining the balance;
It is characterized by that. A payment management system comprising: a game server communicatively connected to a plurality of terminals; and a payment server communicatively connected to the game server,
The game server
A game control unit that controls a game performed between each connected terminal;
A processing request unit for requesting the payment server to process at least a payment collected at the start of the game and a refund paid at the end of the game;
The payment server
A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing a payment amount generated in the game server as a deposit amount until a balance is determined;
A receivable information storage unit for storing receivable information for managing a refund amount generated in the game server as a receivable amount until a balance is determined;
A settlement amount calculation unit for calculating the total settlement amount by offsetting the deposit amount of the deposit information and the claim amount of the claim information when determining the balance;
A payment unit that updates the balance of the balance information based on the calculated payment amount;
It is characterized by that. A settlement management method using a balance information storage unit and a deposit information storage unit, wherein the balance information storage unit stores balance information for managing a balance that can be paid, and the deposit information storage unit manages a deposit amount Memorize deposit information
A deposit information storage step for storing deposit information in the deposit information storage unit with the deposit amount generated until the balance is confirmed;
A deposit information update step for offsetting the refund generated until the balance is settled with the deposit amount of the deposit information;
A settlement step of updating the balance of the balance information based on the deposit information after offset when determining the balance;
A method characterized by that. A settlement management method using a balance information storage unit, a deposit information storage unit, and a bond information storage unit, wherein the balance information storage unit stores balance information for managing a balance that can be paid, and a deposit information storage unit Stores deposit information for managing the deposit amount, and the claim information storage unit stores the claim information for managing the deposit amount,
A deposit information storage step for storing deposit information in the deposit information storage unit with the deposit amount generated until the balance is confirmed;
A receivable information storage step of storing receivable information in a receivable information storage unit with a receivable amount generated until the balance is confirmed;
A settlement amount calculating step for offsetting the deposit amount of the deposit information and the claim amount of the claim information when calculating the balance, and calculating a settlement amount;
A payment step of updating the balance of the balance information based on the calculated payment amount;
A method characterized by that. Computer
A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing the amount of payment that has occurred until the balance is confirmed as a deposit amount;
A deposit information update unit that offsets the refund amount that has occurred until the balance is confirmed, with the deposit amount of the deposit information,
A settlement unit that updates the balance of the balance information based on the deposit information after offsetting when determining the balance;
A program characterized by functioning as Computer
A balance information storage unit for storing balance information for managing balances that can be paid;
A deposit information storage unit for storing deposit information for managing the amount of payment that has occurred until the balance is confirmed as a deposit amount;
Receivable information storage unit for storing receivable information for managing the amount of reimbursement generated until the balance is confirmed as receivable amount,
A settlement amount calculation unit for calculating the total settlement amount by offsetting the deposit amount of the deposit information and the claim amount of the claim information when determining the balance;
A payment unit that updates the balance of the balance information based on the calculated payment amount;
A program characterized by functioning as

Images