JP7412970B2 - Payment processing allocation method, information processing device, and program - Google Patents

Description

The present disclosure relates to a method for allocating payment processing, an information processing device, and a program.

Recently, non-cash payments, in which payments are made using payment means other than cash, have become widely used. There are various methods of non-cash payment, such as a method using a credit card, a method using a debit card, and a method using an IC (Integrated Circuit) card charged with electronic money. Additionally, methods of making non-cash payments using payment application programs (hereinafter referred to as payment apps) installed on terminal devices such as smartphones are also becoming popular. In a method using a payment app, when a user makes a payment using a payment app, the amount used is debited from the user's pre-registered bank account.

Regarding the method of using a payment app, Patent Document 1 below discloses that when a transaction is made using a payment app, the amount is immediately withdrawn from a designated account through an account transfer system that performs payments between a bank account and a coordinating bank account in real time. A mechanism has been proposed to make it possible to remove it. Further, Patent Document 1 listed below proposes a mechanism for providing store information to a terminal device using a two-dimensional code of a product. Note that Patent Document 2 below describes a bank selection screen that is displayed on a terminal device when registering a bank account.

Japanese Patent Application Publication No. 2018-055669 Japanese Patent Application Publication No. 2019-106095

In the case of using the above-mentioned payment app, payments can be made using only the terminal device that is often carried around at all times. Therefore, there is no need to separately carry cards such as credit cards, which is highly convenient for the user. However, there are issues that need to be improved to improve convenience, such as the existence of multiple similar payment services and the need to use different payment apps depending on the payment service and bank used for payment.

According to one aspect of the present disclosure, the purpose of the present disclosure is to process a payment process that allows users to use their own accounts for payments without being aware of the differences between multiple groups of banks that each provide similar payment services. The purpose of the present invention is to provide a method for allocating information, an information processing device, and a program.

According to one aspect of the present disclosure, a first server device executes processing related to direct debit for a bank of a first bank group that provides a first payment service, and a second server device that provides a second payment service. A computer connected to a second server device that manages payment-related processing in a bank group receives a first request including amount information from a recipient's terminal, and in response to the first request. , sending code information including payment identification information and amount for identifying each payment to the payee's terminal, and transmitting information about the bank specified by the payer and payment identification information from the payer's terminal. a first server device corresponding to the specified bank; and, if the designated bank belongs to the second bank group, requesting the second server device to perform processing related to the withdrawal of the amount from the payer's account. A method for allocating processing is provided.

According to the present disclosure, it becomes possible to use one's own account for payment without being aware of the differences among a plurality of bank groups that each provide similar payment services.

FIG. 1 is a block diagram for explaining a system according to the present embodiment. FIG. 2 is a block diagram illustrating computer hardware capable of realizing the functions of a terminal and a server included in the system according to the present embodiment. FIG. 2 is a block diagram for explaining functions of a member store terminal and a user terminal according to the present embodiment. It is a sequence diagram for explaining the flow of payment using the member store terminal and user terminal according to the present embodiment. It is a block diagram for explaining the function of the distribution server concerning this embodiment. It is a chart for explaining the contents of member store DB managed by the distribution server according to the present embodiment. It is a chart for explaining the contents of a user DB managed by the distribution server according to the present embodiment. FIG. 2 is a block diagram for explaining the functions of a payment management server and a transfer gateway server according to the present embodiment. It is a chart for explaining the contents of a member store DB managed by the payment management server according to the present embodiment. It is a chart for explaining the contents of a user DB managed by the payment management server according to the present embodiment. It is a chart for explaining the contents of the payment management DB managed by the payment management server according to the present embodiment. It is a flow diagram for explaining the flow of payment processing executed by the distribution server according to the present embodiment. FIG. 2 is a flowchart for explaining the flow of processing related to provisional payment among the processing executed by the payment management server according to the present embodiment. FIG. 2 is a flowchart for explaining the flow of processing related to distribution among the processing executed by the payment management server according to the present embodiment. It is a sequence diagram for explaining the flow of payment using a member store terminal and a user terminal according to a modified example of the present embodiment.

Embodiments of the present disclosure will be described below with reference to the accompanying drawings. Note that in this specification and the drawings, elements having substantially the same functions may be designated by the same reference numerals, thereby omitting repeated explanation.

[1. system]
A system according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram for explaining a system according to this embodiment.

As shown in FIG. 1, the system according to the present embodiment includes a member store terminal 11, a user terminal 12, an allocation server 20, an X1 bank payment management server 31, an X2 bank payment management server 32, and a transfer gateway. (Gateway) server 40. Further, the system according to the present embodiment includes an X1 bank system 51, an X2 bank system 52, a Y1 bank system 53, a Y2 bank system 54, and a debit payment server 60.

In the example of FIG. 1, to simplify the explanation, the number of member store terminals is 1, the number of user terminals is 1, and the number of bank systems is 4. The number and number of banking systems are not limited to this. Furthermore, in the following description, the member store terminal 11 and the user terminal 12 may be simply referred to as a terminal. Further, the X1 bank payment management server 31 and the X2 bank payment management server 32 may be referred to as payment management servers.

In the following, for convenience of explanation, the payment service provided via the X1 bank payment management server 31, the X2 bank payment management server 32, and the transfer gateway server 40 will be referred to as the "first payment service", and the debit payment server 60 The payment service provided through the ``second payment service'' may be referred to as the ``second payment service''. In addition, when the element group for providing the first payment service is referred to as the first service group (SVG1), and the element group for providing the second payment service is referred to as the second service group (SVG2). There is.

In the example of FIG. 1, the X2 bank system 52 belongs to the first service group SVG1, and the Y1 bank system 53 and the Y2 bank system 54 belong to the second service group SVG2. Furthermore, the X1 bank system 51 belongs to both the first service group SVG1 and the second service group SVG2. In this example, X1 bank provides both the first payment service and the second payment service, X2 bank provides the first payment service, and Y1 bank and Y2 bank provide the second payment service. do.

The member store terminal 11 is a terminal used by a member store that receives payment for transactions conducted with users (hereinafter referred to as payment amount). The member store terminal 11 may be, for example, a computer such as a tablet terminal, a POS (Point Of Sale) system, a PC (Personal Computer), or a smartphone.

The user terminal 12 is a terminal used by a user who pays the payment amount. The user terminal 12 may be, for example, a computer such as a smartphone, a tablet terminal, a PC, a portable game machine, and a portable music player. The member store terminal 11 and the user terminal 12 access the distribution server 20 via the network NW when using the payment service. The network NW may be a wired and/or wireless network configured with a LAN (Local Area Network) and/or a WAN (Wide Area Network).

The distribution server 20 distributes payment requests from the user terminals 12 to any of the X1 bank payment management server 31, the X2 bank payment management server 32, and the debit payment server 60. The distribution server 20 may be, for example, a computer such as a PC, a workstation, or a server device. The distribution server 20, the X1 bank payment management server 31, the X2 bank payment management server 32, and the debit payment server 60 are each connected to a secure network such as a dedicated line network or an encrypted communication network where access from outside is restricted. can be connected via.

The X1 bank payment management server 31 provides a first payment service to users who have an X1 bank account managed by the X1 bank system 51. The X2 bank payment management server 32 provides a first payment service to users who have an X2 bank account managed by the X2 bank system 52. The X1 bank payment management server 31 and the X2 bank payment management server 32 may be computers such as PCs, workstations, and server devices, for example. Each of the X1 bank payment management server 31 and the X2 bank payment management server 32 and the transfer gateway server 40 can be connected via a secure network such as a dedicated line network or an encrypted communication network that restricts access from the outside. .

Each of the X1 bank payment management server 31 and the X2 bank payment management server 32 executes a debit process for withdrawing the payment amount from the user's account via the transfer gateway server 40 and a deposit process for depositing the payment amount into the member store's account. . The transfer GW server 40 manages the collection accounts opened in advance at each of the X1 bank and the X2 bank, and can realize real-time payment in the first payment service using the collection accounts. Examples of real-time payment methods using a consolidated account include the method described in Japanese Patent Application Laid-Open No. 2018-055669. The transfer gateway server 40 and each of the X1 bank system 51 and the X2 bank system 52 may be connected via a secure network such as a dedicated line network or an encrypted communication network to which access from the outside is restricted.

The debit payment server 60 provides a second payment service that enables payment using a payment application using a debit card payment mechanism. Debit payment server 60 may be, for example, a computer such as a PC, a workstation, or a server device. In order to utilize the debit card payment mechanism, some banks that provide the first payment service can also provide the second payment service. In the example of FIG. 1, X1 Bank provides both the first payment service and the second payment service. In this case, the debit payment server 60 is connected to the X1 bank system 51 as well as the Y1 bank system 53 and the Y2 bank system 54 . The debit payment server 60 and each of the X1 bank system 51, Y1 bank system 53, and Y2 bank system 54 are connected via a secure network such as a dedicated line network or an encrypted communication network that restricts access from the outside. It can be done.

(hardware)
Here, with reference to the example of the computer 5 shown in FIG. 2, computer hardware that can realize the functions of the terminal and server included in the system according to this embodiment will be described. FIG. 2 is a block diagram for explaining computer hardware that can realize the functions of the terminal and server included in the system according to the present embodiment.

The functions of the member store terminal 11, user terminal 12, distribution server 20, X1 bank payment management server 31, X2 bank payment management server 32, transfer gateway server 40, and debit payment server 60 are performed by the computer shown in FIG. 5 or a computer system including a plurality of computers substantially the same as computer 5. Note that the same applies to each bank system illustrated in FIG.

As shown in FIG. 2, the computer 5 includes a processor 5a, a memory 5b, a display IF (Interface) 5c, a communication IF 5d, and a connection IF 5e.

The processor 5a is a processing circuit such as a CPU (Central Processing Unit), a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a GPU (Graphic Processing Unit). It's fine. The memory 5b may be a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory.

The display IF 5c is an interface for connecting a display device such as an LCD (Liquid Crystal Display) or an ELD (Electro-Luminescence Display). Display control of the display device may be performed by the processor 5a connected to the display IF 5c and/or the GPU installed in the display IF 5c.

The communication IF 5d is an interface for connecting to a wired and/or wireless network. The communication IF 5d can be connected to a communication network including a wired LAN, wireless LAN, optical communication network, mobile phone network, etc., the above-mentioned secure network, or a dedicated line that directly connects devices.

The connection IF 5e is an interface for connecting various devices. The connection IF 5e is a USB (Universal Serial Bus) port, an IEEE1394 port, a SCSI (Small Computer System Interface), or the like. An input interface such as a keyboard, a mouse, a touch panel, a touch pad, a GPS (Global Positioning System), a motion sensor, a camera, etc. can be connected to the connection IF 5e.

Furthermore, a portable recording medium 5f can be connected to the connection IF 5e. The recording medium 5f is a non-transitory computer readable storage medium such as a magnetic recording medium, an optical disk, a magneto-optical disk, or a semiconductor memory. The above-mentioned processor 5a can read the program stored in the recording medium 5f, store it in the memory 5b, and control the operation of the computer 5 according to the program read out from the memory 5b. The program that controls the operation of the computer 5 may be stored in advance in the memory 5b, or may be downloaded from an external server or system via the communication IF 5d.

(terminal function)
Next, the functions of the member store terminal and user terminal according to this embodiment will be explained with reference to FIG. FIG. 3 is a block diagram for explaining the functions of the member store terminal and user terminal according to this embodiment.

First, the functions of the member store terminal 11 will be explained.
As shown in FIG. 3, the affiliated store terminal 11 includes a storage means 111, an amount input means 112, a payment request means 113, a code display means 114, and a receipt display means 115. The function of the storage means 111 can be realized by the memory 5b mentioned above. The functions of the amount input means 112, the payment request means 113, the code display means 114, and the receipt display means 115 can be mainly realized by the processor 5a described above.

The storage means 111 stores member store information 111a, device information 111b, and payment application 111c.

The member store information 111a may include a member store ID (Identifier) for identifying the member store, and management information such as the name, location, and telephone number of the member store. For example, the member store ID may be provided by the distribution server 20 after registering to use the payment service. The management information may include information on a bank account used for payment and information on a password used by the distribution server 20 to authenticate the member store. The device information 111b includes a terminal ID for identifying the member store terminal 11. The terminal ID may be, for example, an identifier assigned in advance to the payment application 111c, a MAC (Media Access Control) address of the member store terminal 11, or the like. Note that bank account information and password information may not be included in the member store information 111a, but may be stored on the bank's servers (X1 bank payment management server 31, X2 bank payment management server 32, debit payment server 60, etc.). good. Furthermore, the contents exemplified here do not prevent this information from being held in other servers or systems.

The payment application 111c provides the functions of an amount input means 112, a payment request means 113, a code display means 114, and a receipt display means 115 when executed by the processor 5a. The payment application 111c may be provided from the distribution server 20 via the network NW, may be provided from an external system (for example, an app store), or may be installed in the member store terminal 11 in advance. As a modification, functions equivalent to the payment application 111c may be provided to the member store by accessing the distribution server 20 using a web browser or the like, without using the payment application 111c.

The amount input means 112 displays an input form for inputting the payment amount and prompts the member store to input the payment amount. The payment requesting means 113 transmits a code issuance request including the member store ID, terminal ID, and payment amount to the distribution server 20 to request the issuance of code information. The code display means 114 receives code information including a payment ID for identifying each payment from the distribution server 20, and displays the code information on the screen. The code information is a one-dimensional or two-dimensional barcode (for example, a QR code (registered trademark)).

The code display means 114 may display a message on the screen prompting the user terminal 12 to read the code information. When the code information is read by the user terminal 12, information used for payment processing is transmitted from the user terminal 12 to the distribution server 20. When the payment amount is debited from the user's account (when the provisional payment described below is completed), receipt information is transmitted from the distribution server 20 to the member store terminal 11 and the user terminal 12. The receipt display unit 115 receives receipt information from the distribution server 20 and displays the receipt on the screen. Here, we have illustrated a mechanism in which the member store terminal 11 receives receipt information from the distribution server 20 in response to the completion of provisional payment, but the member store terminal 11 receives receipt information from the target bank's server (X1 Bank A mechanism may also be adopted in which the provisional payment completion notification is directly received from the payment management server 31, the X2 bank payment management server 32, the debit payment server 60, etc.). Note that the contents illustrated here do not limit the notification method of payment completion.

Next, the functions of the user terminal 12 will be explained.
As shown in FIG. 3, the user terminal 12 includes a storage means 121, a code reading means 122, a bank selection means 123, a payment requesting means 124, and a receipt displaying means 125. The function of the storage means 121 can be realized by the above-mentioned memory 5b. The functions of the code reading means 122, the bank selection means 123, the payment requesting means 124, and the receipt displaying means 125 can be mainly realized by the processor 5a described above.

The storage means 121 stores user information 121a, device information 121b, and payment application 121c.

The user information 121a includes a user ID for identifying the user, and management information such as the user's name, address, and telephone number. The user ID may be provided by the distribution server 20, for example, after registration to use the payment service. The management information may include information on a bank account used for payment and information on a password used by the distribution server 20 for user authentication. Device information 121b includes a terminal ID for identifying user terminal 12. The terminal ID may be, for example, an identifier assigned in advance to the payment application 121c, a MAC address of the user terminal 12, or the like.

The payment application 121c provides the functions of a code reading means 122, a bank selection means 123, a payment requesting means 124, and a receipt displaying means 125 when executed by the processor 5a. The payment application 121c may be provided from the distribution server 20 via the network NW, may be provided from an external system (for example, an app store), or may be installed in the user terminal 12 in advance. As a modification, functions equivalent to the payment application 121c may be provided to the user by accessing the distribution server 20 using a web browser or the like, without using the payment application 121c.

The code reading means 122 reads code information displayed on the screen of the member store terminal 11. For example, the code reading unit 122 activates the camera function of the user terminal 12, captures an image of the screen of the member store terminal 11 on which code information is displayed, and analyzes the captured data of the code information to obtain the contents of the code information. . The contents of the code information include, for example, a payment ID for uniquely identifying a payment, a payment amount, and the like.

When the user has registered a plurality of accounts for payment, the bank selection means 123 displays a list of banks corresponding to the plurality of accounts and allows the user to select the bank to be used for payment. The payment requesting means 124 sends a payment request including the selected bank, user ID, terminal ID, and code information to the distribution server 20 to request payment. When the distribution server 20 requests password authentication, the payment request means 124 requests the user to input the password, includes the input password in the payment request, and transmits the payment request to the distribution server 20. The receipt display means 125 receives receipt information from the distribution server 20 and displays the receipt on the screen.

(Payment flow)
Next, with reference to FIG. 4, the flow of payment using the member store terminal and user terminal according to this embodiment will be described. FIG. 4 is a sequence diagram for explaining the flow of payment using the member store terminal and user terminal according to this embodiment.

(S101) The user starts the payment application 121c and selects the bank to be used for payment. The user also operates the payment application 121c to display a code reading screen. Note that the bank selection operation may be performed after the code reading screen display operation.

(S102) The member store starts the payment application 111c and inputs the payment amount. When the payment amount is input, the payment application 111c transmits a code issuance request including the member store ID, terminal ID, and payment amount to the distribution server 20, and requests issuance of code information. When the distribution server 20 requests password authentication, the payment application 111c includes the member store's password in a code issuance request and transmits it to the distribution server 20.

(S103) The payment application 111c receives the code information from the distribution server 20 and displays the code information on the screen of the member store terminal 11. The payment application 111c may display a message prompting the affiliated store to present the code information to the user, or may display a message prompting the user to read the code information with the user terminal 12.

(S104) When the user terminal 12 is held over the screen of the member store terminal 11 on which the code information is displayed, the payment application 121c captures an image of the screen of the member store terminal 11 on which the code information is displayed, and analyzes the captured data. to read the contents of the code information. For example, if the code information includes a payment ID and payment amount for uniquely identifying the payment, the payment application 121c reads the payment ID and the payment amount, displays the payment amount on the screen of the user terminal 12, and confirms the payment. A message is displayed on the screen asking you to decide whether to approve the content.

(S105) When the user performs an operation to approve the payment details, the payment application 121c sends a payment request including the code information, selected bank, user ID, and terminal ID to the distribution server 20 to complete the payment. request. When the distribution server 20 requests password authentication, the payment application 121c requests the user to input a password, includes the input password in the payment request, and transmits the payment request to the distribution server 20.

(S106, S107) When the withdrawal process for withdrawing the payment amount from the user's account is completed (when the provisional payment described below is completed), the distribution server 20 sends a completion notification and receipt information to the member store terminal 11 and the user terminal 12. be done. The member store terminal 11 and the user terminal 12 receive the completion notification and receipt information and display the receipt on the screen. When the processes of S106 and S107 are completed, the series of processes shown in FIG. 4 ends.

(Function of distribution server)
Next, the functions of the distribution server according to this embodiment will be explained with reference to FIG. 5. FIG. 5 is a block diagram for explaining the functions of the distribution server according to this embodiment.

As shown in FIG. 5, the distribution server 20 includes a storage unit 201, a terminal authentication unit 202, a code issuing unit 203, a request distribution unit 204, a receipt issuing unit 205, a member store registration unit 206, and a user registration means 207. Note that among the terminal authentication means 202, code issuing means 203, request distributing means 204, receipt issuing means 205, and member store registration means 206, functions other than the function of specifying the target server and distributing the processing are Instead of being installed in the server 20, it may be installed in a bank server (X1 bank payment management server 31, X2 bank payment management server 32, debit payment server 60, etc.). Moreover, the contents illustrated here do not prevent these functions from being installed in other servers or systems.

The function of the storage means 201 can be realized by the above-mentioned memory 5b. The functions of the terminal authentication means 202, the code issuing means 203, the request allocating means 204, the receipt issuing means 205, the affiliated store registration means 206, and the user registration means 207 can be realized mainly by the processor 5a described above.

The storage means 201 stores a member store DB 201a, a user DB 201b, bank attribute information 201c, and registered business information 201d. Note that the member store DB 201a and the user DB 201b are held by each server on the bank side (X1 bank payment management server 31, X2 bank payment management server 32, debit payment server 60, etc.) instead of being held by the distribution server 20. It's okay. Further, the contents exemplified here do not prevent these DBs from being held in other servers or systems.

The member store DB 201a stores information for identifying member stores and member store terminals 11 in the allocation server 20, and information for identifying member stores and member store terminals 11 on the bank side (payment management server, bank system, transfer gateway server 40, and debit payment server 60). and information for identifying the member store terminal 11. Then, the affiliated store DB 201a associates these two types of information. The user DB 201b includes information for identifying users and user terminals 12 on the distribution server 20 and information for identifying users and user terminals 11 on the bank side. Then, the user DB 201b associates these two types of information.

Bank attribute information 201c includes information for specifying the service group to which X1 Bank, X2 Bank, Y1 Bank, and Y2 Bank belong. In the example of FIG. 1, the bank attribute information 201c includes information indicating that Bank X1 and Bank X2 belong to the first service group SVG1, and Bank X1, Bank Y1, and Bank Y2 belong to the second service group SVG2. It will be done.

The registered business information 201d includes information for managing businesses that provide the payment applications 111c and 121c. For example, information about a business that has concluded a payment service provision contract with at least one bank is registered in the registered business information 201d, and a payment application of the business registered in the registered business information 201d is used by the distribution server 20. All payment services provided through the service will be available. Information on businesses that have an account with at least one bank may be registered in the registered business information 201d, and payment services provided by any bank may be made available to the payment application of that business.

Here, the contents of the member store DB managed by the distribution server according to this embodiment will be explained with reference to the example of FIG. 6. FIG. 6 is a chart for explaining the contents of the member store DB managed by the distribution server according to the present embodiment.

As shown in FIG. 6, the member store DB 201a includes member store IDs, terminal IDs, and member store information.

In the affiliated store ID column, the affiliated store ID on the terminal side and the affiliated store ID on the bank side are written in association with each other. The member store ID on the terminal side is identification information used by the distribution server 20 to identify the member store. The member store ID on the bank side is identification information used by the bank side including the X1 bank payment management server 31, the X2 bank payment management server 32, and the debit payment server 60 to identify the member store. The terminal ID of the member store terminal 11 is written in the terminal ID column.

In the affiliated store information column, registered bank information and affiliated store management information are written. The registered bank information is bank information (eg, bank name, bank code, etc.) corresponding to the member store's payment account. The management information includes information such as the member store's name, location, and password. Note that the contents of the management information can be modified as appropriate depending on the implementation mode.

Next, the contents of the user DB managed by the distribution server according to this embodiment will be explained with reference to the example of FIG. 7. FIG. 7 is a chart for explaining the contents of the user DB managed by the distribution server according to the present embodiment.

As shown in FIG. 7, the user DB 201b may include a user ID, a terminal ID, and user information. Note that the user information may be managed by the bank-side servers (X1 bank payment management server 31, X2 bank payment management server 32, debit payment server 60) and not retained by the distribution server 20. Further, the contents illustrated here do not prevent user information from being held in another server or system.

In the user ID column, the user ID on the terminal side and the user ID on the bank side are written in association with each other. The user ID on the terminal side is identification information used by the distribution server 20 to identify the user. The bank side user ID is identification information used to identify the user on the bank side including the X1 bank payment management server 31, the X2 bank payment management server 32, and the debit payment server 60. The terminal ID of the user terminal 11 is written in the terminal ID column.

In the user information column, registered bank information and user management information are written. The registered bank information is bank information (eg, bank name, bank code, etc.) corresponding to the user's payment account. The management information includes information such as the user's name, password, and contact information. Note that the contents of the management information can be modified as appropriate depending on the implementation mode.

Referring again to FIG. The terminal authentication means 202 uses a set of the password, the terminal-side member store ID, and the terminal ID transmitted from the member store terminal 11, the password, the terminal-side member store ID, and the terminal ID registered in the member store DB 201a. Authentication is performed by comparing with the set of . In addition, the terminal authentication means 202 includes a password, a terminal-side user ID, and a set of terminal ID transmitted from the user terminal 12, and a set of the password, terminal-side user ID, and terminal ID registered in the user DB 201b. Authentication is performed by comparing the

Code issuing means 203 issues a payment ID in response to a code issuance request from member store terminal 11 , generates code information including the payment ID, and transmits it to member store terminal 11 . The code information may include, for example, the payment amount obtained from the code issuance request in addition to the payment ID.

The request distribution means 204 receives the payment request from the user terminal 12, refers to the member store DB 201a, replaces the member store ID on the terminal side with the member store ID on the bank side, and refers to the user DB 201b to replace the member store ID on the terminal side. Replace the user ID with the bank user ID. The request allocating means 204 also refers to the user DB 201b to identify the registered bank of the user, and uses a server (X1 bank payment management server 31, X2 bank payment management server 32, or debit payment server) corresponding to the specified registered bank. 60) for payment processing.

In the example of FIG. 7, when the user ID on the terminal side is FS101, the registered bank is identified as X2 Bank. In this case, the request allocating means 204 requests the X2 bank payment management server 32 to process the payment. As another example, if the registered bank is Y1 bank included in the second service group SVG2, the request allocating means 204 requests the debit payment server 60 to perform payment processing.

If the registered bank is the X1 bank that belongs to both the first service group SVG1 and the second service group SVG2, the request allocating means 204 requests the X1 bank payment management server 31 to perform payment processing. If the registered bank is X1 Bank and the use of the second payment service is set in advance, the request allocating means 204 requests the debit payment server 60 to perform payment processing.

Receipt issuing means 205 issues a receipt upon completion of the payment processing requested to X1 bank payment management server 31, 11 and the user terminal 12. The receipt includes, for example, a payment ID, a payment amount, member store (recipient) information, user (payer) information, payment date, and the like.

Member store registration means 206 executes processing for registering member stores that use the payment service. For example, the member store registration means 206 receives a registration request including the member store's account information and the terminal ID of the terminal used by the member store for payment. Further, the affiliated store registration means 206 confirms the existence of the specified account and obtains the affiliated store ID on the bank side. Further, the member store registration means 206 issues the member store ID on the terminal side, and stores the member store ID on the bank side, the terminal ID, the registered bank, and management information in the member store DB 201a in a form that is associated with the member store ID on the terminal side. Register.

The user registration means 207 executes processing for registering users who use the payment service. For example, the user registration means 207 receives a registration request including the user's account information and the terminal ID of the terminal used by the user for payment. Further, the user registration means 207 confirms the existence of the specified account and obtains the bank's user ID. Further, the user registration means 207 issues a terminal-side user ID, and registers the bank-side user ID, terminal ID, registered bank, and management information in the user DB 201b in a form that is associated with the terminal-side user ID.

(Functions of payment management server and transfer gateway server)
Next, the functions of the payment management server and transfer gateway server according to this embodiment will be explained with reference to FIG. 8. FIG. 8 is a block diagram for explaining the functions of the payment management server and transfer gateway server according to this embodiment. In order to simplify the explanation, the functions of the X1 bank payment management server 31 will be described assuming that the X1 bank payment management server 31 and the X2 bank payment management server 32 have substantially the same functions, and the X2 bank payment management server The description of the function of No. 32 will be omitted.

As shown in FIG. 8, the X1 bank payment management server 31 includes a storage unit 311, a provisional payment request unit 312, and a distribution request unit 313. The transfer gateway server 40 includes a provisional payment means 401 and a distribution means 402. The function of the storage means 311 can be realized by the memory 5b described above. The functions of the temporary payment requesting means 312, the distribution requesting means 313, the temporary payment means 401, and the distribution means 402 can be mainly realized by the processor 5a described above.

The storage means 311 stores a member store DB 311a, a user DB 311b, and a payment management DB 311c. The member store DB 311a contains information for identifying member stores on the X1 Bank side (X1 Bank payment management server 31, transfer gateway server 40, X1 Bank system 51) and information on payment accounts held by member stores at X1 Bank. Correlate with. The user DB 311b associates information for identifying the user on the X1 Bank side with information on the payment account held by the user at the X1 Bank. The payment management DB 311c is a database for managing the details of payments made via the X1 bank payment management server 31.

Here, the contents of the member store DB managed by the payment management server according to this embodiment will be explained with reference to the example of FIG. 9. FIG. 9 is a chart for explaining the contents of the member store DB managed by the payment management server according to the present embodiment.

As shown in FIG. 9, the member store DB 311a contains the member store ID managed by the X1 Bank (the bank's member store ID), the account information of the account opened by the member store at the X1 Bank, and the distribution date. Member store information is stored. The account information includes the account type, store number, and account number. The member store information includes information such as the member store's name, location, and contact information. Note that the contents of the affiliated store information can be modified as appropriate depending on the mode of implementation.

The distribution date is information indicating the timing at which money is deposited from the collection account managed by the transfer gateway server 40 to the member store account. In the case of real-time payments using the transfer gateway server 40, the timing at which funds are deposited from the user's payment account to the collection account is not synchronized with the timing at which funds are deposited from the collection account to the member store account. When the distribution date set by the store arrives, funds will be deposited from the collection account to the member store account. Therefore, the member store DB 311a includes information regarding the distribution date. In this specification, the process related to depositing money into the collective account is referred to as "provisional payment", and the process related to depositing money from the collective account to the member store account is referred to as "distribution".

Next, the contents of the user DB managed by the payment management server according to this embodiment will be described with reference to the example of FIG. 10. FIG. 10 is a chart for explaining the contents of the user DB managed by the payment management server according to this embodiment.

As shown in FIG. 10, the user DB 311b stores a user ID managed by the X1 bank (bank user ID), account information of an account opened by the user at the X1 bank, and user information. The account information includes the account type, store number, and account number. The user information includes information such as the user's name, address, and contact information. Note that the contents of the user information can be modified as appropriate depending on the implementation mode.

Next, the contents of the payment management DB managed by the payment management server according to this embodiment will be described with reference to the example of FIG. 11. FIG. 11 is a chart for explaining the contents of the payment management DB managed by the payment management server according to this embodiment.

As shown in FIG. 11, the payment management DB 311c includes a payment ID for identifying each payment, a member store ID and user ID corresponding to the member store and user involved in the payment, and a provisional payment execution date. The payment amount and information regarding the distribution status are stored. The provisional payment execution date column describes the date on which the provisional payment was performed. Note that the provisional payment execution completion time may be written in the provisional payment execution date column. In the distribution column, information indicating whether the distribution has been completed (completed) or incomplete (unfinished) and, if the distribution has been completed, the execution date of the distribution is written.

Referring again to FIG. In response to a payment request from the distribution server 20, the provisional payment requesting means 312 creates a record including a payment ID, member store ID, user ID, and payment amount in the payment management DB 311c. Further, the provisional payment requesting means 312 requests the transfer GW server 40 to perform a provisional payment process in which the payment amount is debited from the user's payment account and deposited into the collection account of the X1 bank. Upon receiving the request from the provisional payment requesting means 312, the provisional payment means 401 accesses the X1 bank system 51 and executes provisional payment. When the provisional payment by the provisional payment means 401 is completed, the provisional payment requesting means 312 records the provisional payment execution date in the payment management DB 311c and notifies the distribution server 20 of the completion of the provisional payment.

The distribution requesting means 313 refers to the distribution date column of the member store DB 311a and specifies the member store ID corresponding to the member store to which distribution is to be made. Then, the distribution requesting means 313 calculates the total amount of settlement amount to be paid to the member store to be distributed, collects the calculated total amount, and transfers the distribution process to transfer the amount from the account to the member store account. request. Upon receiving the request from the distribution requesting means 313, the distribution means 402 accesses the X1 bank system 51 and executes the distribution. When the distribution by the distribution means 402 is completed, the distribution request means 313 updates the distribution column of the payment management DB 311c and notifies the distribution server 20 of the completion of distribution. A notification of completion of distribution is sent to the member store to which distribution is to be made via the distribution server 20.

[2. Process flow]
Next, with reference to FIG. 12, the flow of payment processing executed by the distribution server according to this embodiment will be described. FIG. 12 is a flow diagram for explaining the flow of payment processing executed by the distribution server according to the present embodiment.

(S201) The distribution server 20 receives a code issuance request including the member store ID, terminal ID, password, and payment amount from the member store terminal 11.

(S202) The distribution server 20 sets a set of the password, member store ID, and terminal ID included in the code issuance request, and a set of the password, member store ID of the terminal side, and terminal ID stored in the member store DB 201a. Authentication is performed by comparing the If the authentication is successful, the distribution server 20 issues a payment ID and generates code information including the payment ID and the payment amount. Then, the distribution server 20 transmits the generated code information to the member store terminal 11.

The member store terminal 11 that has received the code information displays the code information on the screen of the payment application 111c. The affiliated store presents the code information displayed on the screen to the user and prompts the user to read the code information using the user terminal 12. When the code information is read by the user terminal 12, information such as the payment amount is displayed on the payment application 121c. The user who approves the payment enters a password, selects the bank to be used, and performs operations to proceed with the payment. In response to this operation, a payment request is transmitted from the user terminal 12 to the distribution server 20. The payment request includes the password, selected bank information, user ID, terminal ID, and code information.

(S203) The distribution server 20 receives a payment request from the user terminal 12.

(S204) The distribution server 20 compares the set of password, user ID, and terminal ID included in the payment request with the set of password, terminal user ID, and terminal ID stored in the user DB 201b. Perform authentication. If the authentication is successful, the distribution server 20 refers to the bank attribute information 201c to identify the service group to which the bank specified in the payment request (selected bank) belongs.

(S205) The distribution server 20 determines whether the selected bank belongs to both the first service group SVG1 and the second service group SVG2. If the selected bank belongs to both service groups, the process advances to S206. If the selected bank belongs to only one service group, the process advances to S207. For example, if the selected bank is X1 bank, the process proceeds to S206, and if the selected bank is any other bank, the process proceeds to S207.

(S206) The distribution server 20 preferentially selects the payment management server managed by the selected bank instead of the debit payment server 60. However, if the user has set in advance to preferentially use the second payment service, the debit payment server 60 is selected. When the process of S206 is completed, the process advances to S208.

(S207) The distribution server 20 selects a server corresponding to the selected bank. For example, when the selected bank is X2 Bank, the X2 bank payment management server 32 corresponding to X2 Bank is selected, and when the selected bank is Y1 Bank or Y2 Bank, the debit payment server 60 is selected.

(S208) The distribution server 20 refers to the member store DB 201a and the user DB 201b and replaces the terminal-side member store ID and the terminal-side user ID with the bank-side member store ID and the bank-side user ID. In addition, the distribution server 20 sends the payment request including the payment ID, payment amount, bank-side member store ID, and bank-side user ID to the servers selected in S206 or S207 (X1 bank payment management server 31, the bank payment management server 32 or the debit payment server 60).

(S209) When the distribution server 20 receives the provisional payment completion notification from the server selected in S206 or S207, it issues a receipt and transmits the receipt information to the member store terminal 11 and the user terminal 12. Note that if the provisional payment fails, the distribution server 20 notifies the member store terminal 11 and the user terminal 12 of the failure (incomplete) of the payment process. When the process of S209 is completed, the series of processes shown in FIG. 12 ends.

Note that the above-mentioned processes of S201 and S202 are carried out through communication between the member store terminal 11 and the bank-side servers (X1 bank payment management server 31, X2 bank payment management server 32, debit payment server 60, etc.). May be executed. In addition, some or all of the processing from S203 onwards, excluding the part where the target server is selected and the processing is distributed, is performed by a bank server (X1 bank payment management server) instead of the distribution server 20. 31, X2 bank payment management server 32, debit payment server 60, etc.). Furthermore, the contents exemplified here do not preclude executing some or all of these processes on other servers or systems.

Next, with reference to FIG. 13, a flow of processing related to provisional payment among the processes executed by the payment management server according to this embodiment will be described. FIG. 13 is a flow diagram for explaining the flow of processing related to provisional payment among the processing executed by the payment management server according to the present embodiment. Note that the process shown in FIG. 13 is mainly executed by the provisional payment requesting means 312 of the X1 bank payment management server 31 and the provisional payment means 401 of the transfer gateway server 40.

(S211) The X1 bank payment management server 31 receives the payment request from the distribution server 20, and acquires the user ID from the payment request. Furthermore, the X1 bank payment management server 31 extracts account information corresponding to the acquired user ID from the user DB 311b. Further, the X1 bank payment management server 31 provides the extracted account information to the transfer gateway server 40 and inquires of the bank system 51 via the transfer gateway server 40 about the account balance. Then, the X1 bank payment management server 31 checks the account balance of the user corresponding to the acquired user ID.

(S212) The X1 bank payment management server 31 compares the account balance confirmed in S211 with the payment amount included in the payment request, and determines whether the account balance is greater than the payment amount. If the account balance is greater than the payment amount, the process advances to S213. On the other hand, if the account balance is not greater than the payment amount, the process advances to S217.

(S213) The X1 bank payment management server 31 adds a record including the payment ID, member store ID, user ID, and payment amount to the payment management DB 311c. Further, the X1 bank payment management server 31 generates transfer data including the payment amount and account information.

(S214) The X1 bank payment management server 31 transmits the transfer data generated in S213 to the transfer GW server 40, and requests a transfer from the user's account to the consolidated account. In response to this request, the transfer gateway server 40 executes a withdrawal process from the user account and a deposit process to the collection account based on the transfer data, and reports the completion of the provisional payment to the X1 bank payment management server 31.

(S215, S216) When the X1 bank payment management server 31 receives the provisional payment completion report from the transfer gateway server 40, it registers the provisional payment execution date in the payment management DB 311c. Furthermore, the X1 bank payment management server 31 notifies the distribution server 20 of the completion of the payment. When the process of S216 is completed, the series of processes shown in FIG. 13 ends.

(S217) The X1 bank payment management server 31 notifies the distribution server 20 of the insufficient balance. When the process of S217 is completed, the series of processes shown in FIG. 13 ends.

Note that the processes of S211, S212, and S217 described above may be omitted. For example, the determination in S212 may be performed by a banking system, and the system may return the determination result (successful payment transaction or insufficient balance) at the time of a payment transaction. In this case, the determination in S212 may be performed between the processing in S214 and the processing in S215. The contents illustrated here do not prevent these processes from being executed by other servers or systems, nor do they limit the timing of the processes to the above example.

Next, with reference to FIG. 14, the flow of processing related to distribution among the processing executed by the payment management server according to this embodiment will be described. FIG. 14 is a flow diagram for explaining the flow of processing related to distribution among the processing executed by the payment management server according to the present embodiment. The processing shown in FIG. 14 is mainly executed by the distribution requesting means 313 of the X1 bank payment management server 31 and the distribution means 402 of the transfer gateway server 40.

(S221) The X1 bank payment management server 31 refers to the member store DB 201a and extracts the member store ID of the member store to which distribution is to be made.

(S222) The X1 bank payment management server 31 refers to the payment management DB 311c and extracts the outstanding payment ID corresponding to the member store ID extracted in S221.

(S223) The X1 bank payment management server 31 obtains the payment amount corresponding to the extracted payment ID, and calculates the total amount of the payment amount corresponding to each member store. Then, the X1 bank payment management server 31 refers to the member store DB 311a and creates transfer data including the member store ID of the target member store, the account information corresponding to the member store ID, and the total amount.

(S224) The X1 bank payment management server 31 transmits the transfer data for each member store created in S223 to the transfer gateway server 40. Upon receiving this transfer data, the transfer gateway server 40 executes a process of withdrawing the total amount corresponding to each member store from the consolidated account, and executes a process of depositing an amount corresponding to the total amount into the account of each member store. When the payment processing for the member store to which the distribution is to be made is completed, a distribution completion report is transmitted from the transfer GW server 40 to the X1 bank payment management server 31.

(S225) When the X1 bank payment management server 31 receives the distribution completion report from the transfer GW server 40, it updates the contents of the distribution column for the corresponding record in the payment management DB 311c. Furthermore, the X1 bank payment management server 31 notifies the member stores targeted for distribution of the completion of distribution. Note that the completion of distribution may be notified via the payment application 111c of the member store terminal 11, or may be notified using other communication means such as e-mail. When the process of S225 is completed, the series of processes shown in FIG. 14 ends.

[3. Modified example]
Although the above description assumes payment using the so-called MPM (Merchant Presented Mode) method, the technology according to the present embodiment is also applicable to payment using the so-called CPM (Consumer Presented Mode) method. In addition, in the above explanation, a dynamic MPM method (for example, a method using a dynamic QR code) in which the member store terminal acquires code information from the distribution server was exemplified, but the fixed code provided by the member store is The technology according to this embodiment can also be applied to a static MPM method (for example, a method using a static QR code) in which information is read by a user terminal.

Application to the CPM method will be described below as a modified example of this embodiment.

With reference to FIG. 15, a payment flow using a member store terminal and a user terminal according to a modified example of this embodiment will be described. FIG. 15 is a sequence diagram for explaining the flow of payment using the member store terminal and user terminal according to a modified example of the present embodiment.

(S301) The user starts the payment application 121c and selects the bank to be used for payment. When a bank is selected, the payment application 121c transmits a code issuance request including the user ID and terminal ID to the distribution server 20 to request the issuance of code information. When the distribution server 20 authenticates the user's password, the payment application 121c prompts the user to input the password, includes the password input by the user in a code issuance request, and sends the code to the distribution server 20.

(S302) The payment application 121c receives code information from the distribution server 20 and displays the code information on the screen of the user terminal 12. The user presents the code information displayed on the screen to the member store and urges the member store terminal 11 to read the code information. The code information is a one-dimensional or two-dimensional barcode (eg, QR code, etc.).

(S303) The member store starts the payment application 111c and inputs the payment amount. When the payment amount is input, the payment application 111c displays a code reading screen.

(S304) The member store uses the member store terminal 11 to image the code information displayed on the screen of the user terminal 12. Note that if a device for reading the code information is connected to the member store terminal 11, the member store uses the device to read the code information. The payment application 111c analyzes the read code information data and acquires the contents of the code information.

(S305) The payment application 111c sends a payment request including the contents of the code information (payment ID, etc.), member store ID, and terminal ID to the distribution server 20 to request payment. When the distribution server 20 performs password authentication for the member store, the payment application 111c includes the password input by the member store in the payment request and transmits it to the distribution server 20.

(S306, S307) When the payment process is completed, the distribution server 20 sends a completion notification and receipt information to the member store terminal 11 and the user terminal 12. The member store terminal 11 and the user terminal 12 each receive the completion notification and receipt information and display the receipt. When the processes of S306 and S307 are completed, the series of processes shown in FIG. 15 ends.

Although preferred embodiments of the present disclosure have been described above with reference to the accompanying drawings, the present disclosure is not limited to such examples. It is obvious that those skilled in the art can come up with various changes or modifications within the scope of the claims, and these naturally fall within the technical scope of the present disclosure.

For example, in the above explanation, the payment example is explained in which the payee is a member store and the payer is a user, but the payer may be a store and the payee may be an individual, or the payer and payee may be Both parties may be individuals, or both the payer and payee may be stores. Further, in the above description, an example is shown in which an ID is used as information for identifying a user of a payment service, but this can be modified to a mechanism for identifying a user using an access token. In this case, the distribution server 20 has a function of holding information linking the access token on the bank side and the access token on the terminal side, and replacing the two. Naturally, such modifications also fall within the technical scope of this embodiment.

11 Member store terminal 12 User terminal 20 Distribution server 31 X1 bank payment management server 32 X2 bank payment management server 40 Transfer GW server 51 X1 bank system 52 X2 bank system 53 Y1 bank system 54 Y2 bank system 60 Debit payment server 111, 121 , 201, 311 Storage means 111a Member store information 111b, 121b Device information 111c, 121c Payment application 121a User information 112 Amount input means 113 Payment request means 114 Code display means 115 Receipt display means 122 Code reading means 123 Bank selection means 124 Payment request Means 125 Receipt display means 201a, 311a Member store DB
201b, 311b User DB
201c Bank attribute information 201d Registered business information 202 Terminal authentication means 203 Code issuing means 204 Request distribution means 205 Receipt issuing means 206 Member store registration means 207 User registration means 311c Settlement management DB
312 Temporary payment requesting means 313 Distribution requesting means 401 Temporary payment means 402 Distribution means SVG1 First service group SVG2 Second service group NW network

Claims (6)

A first server device that executes processing related to direct debit for a bank in a first group of banks that provides a first payment service, and manages payment-related processing in a second group of banks that provides a second payment service. A computer connected to a second server device that
receiving a first request including amount information from a recipient's terminal;
In response to the first request, transmitting code information including payment identification information for identifying each payment and the amount to the recipient's terminal;
receiving from a payer's terminal a second request including information regarding a bank specified by the payer and the payment identification information;
If the specified bank belongs to the first bank group, requesting the first server device corresponding to the specified bank to perform processing related to the withdrawal of the amount from the payer's account; If the specified bank belongs to the second bank group, requesting the second server device to perform a process related to debiting the amount from the payer's account;
Payment processing distribution method that performs processing including. The first request further includes a first payee identification information, the second request further includes a first payer identification information, and
identifying the payee using the first payee identification information when receiving the first request; and identifying the payee using the first payee identification information when receiving the second request; identifying the payer using identifying information;
When requesting processing related to the above-mentioned withdrawal,
a recipient database that associates second recipient identification information used by the first server device or the second server device to identify the recipient with the first recipient identification information; , a payer database that associates second payer identification information used by the first server device or the second server device to identify the payer and the first payer identification information; referencing, replacing the first payee identification information with the second payee identification information, and replacing the first payer identification information with the second payer identification information;
further including,
The method for allocating payment processing according to claim 1. If the specified bank is a bank that belongs to both the first bank group and the second bank group, the computer transfers the processing related to the withdrawal to the first server corresponding to the specified bank. The payment processing distribution method according to claim 1 or 2, wherein the payment processing is requested to a device. If the designated bank is a bank that belongs to both the first bank group and the second bank group, the computer:
When the first payment service is given a higher priority than the second payment service, the first server device corresponding to the specified bank is requested to perform the processing related to the withdrawal, and 3. The payment processing distribution method according to claim 1, wherein when a higher priority is set for a payment service than the first payment service, the second server device is requested to perform processing related to the withdrawal. A first server device that executes processing related to direct debit for a bank in a first group of banks that provides a first payment service, and manages payment-related processing in a second group of banks that provides a second payment service. An information processing device connected to a second server device,
comprising a processor and a memory, the memory stores information on banks belonging to the first bank group and information on banks belonging to the second bank group, and the processor:
A first request including amount information is received from a recipient's terminal, and in response to the first request, code information including payment identification information for identifying an individual payment and the amount is sent to the recipient. Send it to the terminal of
A second request including information regarding the bank designated by the payer and the payment identification information is received from the payer's terminal, and if the designated bank belongs to the first bank group, the payment The first server device corresponding to the designated bank is requested to perform processing related to the withdrawal of the amount from the person's account, and if the designated bank belongs to the second bank group, the payer An information processing device that executes a process of requesting the second server device to perform a process related to the withdrawal of the amount from an account. A first server device that executes processing related to direct debit for a bank in a first group of banks that provides a first payment service, and manages payment-related processing in a second group of banks that provides a second payment service. a computer connected to a second server device,
receiving a first request including amount information from a recipient's terminal;
In response to the first request, transmitting code information including payment identification information for identifying each payment and the amount to the recipient's terminal;
receiving from a payer's terminal a second request including information regarding a bank specified by the payer and the payment identification information;
If the specified bank belongs to the first bank group, requesting the first server device corresponding to the specified bank to perform processing related to the withdrawal of the amount from the payer's account; If the specified bank belongs to the second bank group, requesting the second server device to perform a process related to debiting the amount from the payer's account;
A program that executes processing including.

Images