JP7412971B2 - Terminal device, payment program, payment account registration processing method, and distribution server - Google Patents

Description

The present disclosure relates to a terminal device, a payment program, a payment account registration processing method, and an allocation server.

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, the payment can be completed 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 users. 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. For example, if Bank A and Bank B are different payment service providers, when a user registers a payment account, Bank A's payment app will display Bank B as a candidate bank that can be registered. Not done.

According to one aspect of the present disclosure, the purpose of the present disclosure is to provide a terminal device that enables users to register their own accounts for multiple groups of banks that provide similar payment services without being aware of their differences; The purpose of the present invention is to provide a computer program, a payment account registration processing method, and a distribution server.

According to one aspect of the present disclosure, a payment program that enables use of a first payment service provided by a first bank group and a second payment service provided by a second bank group is stored. and a processor that executes a payment program, and when executed by the processor, the payment program accepts a first operation for starting registration of a bank account to be used for payment; from a distribution server that distributes payment processing between a first server device that executes processing related to direct debits for banks in a bank group and a second server device that manages payment related processing in a second bank group; , obtain a bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group, and perform a process of displaying the bank list on the execution screen of the payment program in response to the first operation. A terminal device is provided for executing the instructions.

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

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. It is a flow diagram for explaining the flow of payment processing executed by the payment management server according to the present embodiment. It is a flow diagram for explaining the flow of registration processing performed by the distribution server according to the present embodiment. FIG. 2 is a first flow diagram for explaining the flow of registration processing executed by the terminal according to the present embodiment. FIG. 7 is a second flow diagram for explaining the flow of registration processing performed by the terminal according to the present embodiment. FIG. 2 is a schematic diagram for explaining a GUI provided by a payment application of a terminal during registration processing 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. Further, the affiliated store terminal 11 includes a list display means 116 , a registration request means 117 , an imaging means 118 , and a position information acquisition means 119 .

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, the receipt display means 115, the list display means 116, the registration request means 117, the imaging means 118, and the position information acquisition means 119 are mainly performed by the processor 5a described above. This can be realized by

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.

When registering a member store, the list display means 116 requests the allocation server 20 for a list of banks that can be used for payment (hereinafter referred to as bank list), and displays the bank list obtained from the allocation server 20 on the screen. . When the bank used by the member store is selected from the bank list, the registration request means 117 displays an input form for inputting information to be registered such as account information of the member store and management information of the member store. Further, the registration requesting means 117 acquires the terminal ID of the affiliated store terminal 11 and transmits a registration request including the terminal ID and the information input in the input form to the distribution server 20. Further, upon receiving a report of registration completion from the distribution server 20, the registration requesting means 117 displays a message to the effect that the registration has been completed on the screen.

When registering an affiliated store, the imaging means 118 activates the camera function of the affiliated store terminal 11 in response to a specific operation so that it can take an image of a cash card or passbook. When a member store takes an image of a cash card or passbook, the imaging means 118 analyzes the imaged data and reads the bank code, store number, account number, and account holder's name. The imaging means 118 then provides the registration requesting means 117 with account information including at least part of the read information. In this case, the registration requesting means 117 assists in inputting the member store by entering the account information received from the imaging means 118 in the entry field of the input form in advance.

The location information acquisition means 119 acquires the current location of the member store terminal 11 using functions such as GPS. Further, the location information acquisition means 119 may store history data indicating the movement history of the member store terminal 11 in the storage means 111. Additionally, the location information acquisition means 119 acquires information on locations where bank-related facilities (hereinafter referred to as bank-related facilities) that can be included in the bank list are located, collates the acquired location information with historical data, and Bank-related facilities visited by the store may also be identified. Bank-related facilities include bank stores and ATMs (Automated Teller Machines).

The location information acquisition unit 119 provides the list display unit 116 with information indicating the current location of the member store terminal 11, information on bank-related facilities visited by the member store (hereinafter referred to as facility information), and the like.

After receiving the current location, the list display means 116 identifies banks around the current location, and displays the identified banks at the top when displaying the bank list. For example, the list display means 116 may rearrange and display the banks in the bank list in order of proximity to the current location. Furthermore, the list display means 116 may adjust the order of the banks so that, among the banks located in a predetermined area based on the current position, the main bank of the area is placed at the top. Furthermore, the list display means 116 may receive the facility information from the position information acquisition means 119 and adjust the order of the facilities in descending order of the number of times they have stopped by, or in descending order of the timing of their stops closest to the present.

The number of banks that can provide payment services via the distribution server 20 is enormous. Therefore, when a bank list containing all available banks is displayed, merchants are required to scroll the display area multiple times or refine their search to find the desired bank. . However, by applying the above method to control the order of the bank list, banks that are likely to be registered by the merchant will be displayed at the top of the bank list, making it easy for the merchant to select the desired bank. This will allow you to proceed with the registration process smoothly.

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. Further, the user terminal 12 includes a list display means 126 , a registration request means 127 , an imaging means 128 , and a position information acquisition means 129 .

The function of the storage means 121 can be realized by the above-mentioned memory 5b. The functions of the code reading means 122, bank selection means 123, payment request means 124, receipt display means 125, list display means 126, registration request means 127, imaging means 128, and location information acquisition means 129 are mainly performed by the processor 5a described above. This can be realized by

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 means 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.

When registering a user, the list display means 126 requests the distribution server 20 for a list of banks that can be used for payment (bank list), and displays the bank list obtained from the distribution server 20 on the screen. When the user selects a bank to use from the bank list, the registration requesting means 127 displays an input form for inputting information to be registered such as the user's account information and user management information. Further, the registration requesting means 127 acquires the terminal ID of the user terminal 12 and transmits a registration request including the terminal ID and the information input in the input form to the distribution server 20. Further, upon receiving a report of registration completion from the distribution server 20, the registration requesting means 127 displays a message to the effect that the registration has been completed on the screen.

When registering a user, the imaging means 128 activates the camera function of the user terminal 12 in response to a specific operation so that it can take an image of a cash card or passbook. When the user takes an image of a cash card or passbook, the imaging means 128 analyzes the imaged data and reads the bank code, store number, account number, and account holder's name. The imaging means 128 then provides the registration requesting means 127 with account information including at least part of the read information. In this case, the registration requesting means 127 assists the user in inputting the account information received from the imaging means 128 by filling in the entry field of the input form in advance.

The location information acquisition means 129 acquires the current location of the user terminal 12 using functions such as GPS. Further, the position information acquisition means 129 may accumulate history data indicating the movement history of the user terminal 12 in the storage means 121. Furthermore, the location information acquisition unit 129 acquires information on locations where bank-related facilities (hereinafter referred to as bank-related facilities) that can be included in the bank list are located, collates the acquired location information with historical data, and may identify the bank-related facilities visited by the person. Bank-related facilities include bank stores and ATMs.

The location information acquisition unit 129 provides the list display unit 126 with information indicating the current location of the user terminal 12, information on bank-related facilities visited by the user (facility information), and the like.

Upon receiving the current location, the list display means 126 identifies banks around the current location, and displays the identified banks at the top when displaying the bank list. For example, the list display means 126 may rearrange and display the banks in the bank list in order of proximity to the current location. Furthermore, the list display means 126 may adjust the order of the banks so that, among the banks located within a predetermined area based on the current position, the main bank of the area is placed at the top. Furthermore, the list display means 126 may receive the facility information from the position information acquisition means 129 and adjust the arrangement order in descending order of the number of visits, or in descending order of the timing of the visits closest to the present.

The number of banks that can provide payment services via the distribution server 20 is enormous. Therefore, when a bank list including all available banks is displayed, the user is required to scroll the display area many times or perform a narrowed search in order to find the desired bank. However, by applying the above method to control the order of the bank list, banks that the user is likely to register will be displayed at the top of the bank list, making it easier for the user to find the bank they want. This allows the registration process to proceed smoothly.

(Payment flow)
Here, with reference to FIG. 4, the flow of payment using the member store terminal and user terminal according to this embodiment will be explained. 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 means 201, a terminal authentication means 202, a code issuance means 203, a request distribution means 204, a receipt issuance means 205, a member store registration means 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 transmits a list of registrable banks (bank list) to the member store terminal 11 in response to a request from the member store terminal 11. In the example of FIG. 1, the accounts of X1 Bank, X2 Bank, Y1 Bank, and Y2 Bank can be used for payment via the distribution server 20, so these banks are included in the bank list.

Note that when current location information and facility information can be obtained from the member store terminal 11, the member store registration means 206 sorts the bank list based on the current location information and facility information, and The list may be provided to the member store terminal 11. The method of sorting may be the same as the method of sorting by the list display means 116 of the member store terminal 11, for example.

Further, the member store registration means 206 receives a registration request including the member store's account information, the terminal ID of the terminal used by the member store for payment, and the like. Further, the member store registration means 206 transfers the registration request to the server (X1 bank payment management server 31, X2 bank payment management server 32, or debit payment server 60) corresponding to the bank selected by the member store. Further, the affiliated store registration means 206 obtains the affiliated store ID on the bank side from the transfer destination of the registration request. 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. When the registration is completed, the member store registration means 206 sends a notification of completion of the registration process to the member store terminal 11.

The user registration means 207 executes processing for registering users who use the payment service. For example, the user registration means 207 transmits a list of registrable banks (bank list) to the user terminal 12 in response to a request from the user terminal 12. Note that when current location information and facility information can be obtained from the user terminal 12, the user registration means 207 sorts the bank list based on the current location information and facility information, and updates the bank list after sorting. It may also be provided to the user terminal 12. The method of sorting may be the same as the method of sorting by the list display means 126 of the user terminal 12, for example.

Further, 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 transfers the registration request to the server (X1 bank payment management server 31, X2 bank payment management server 32, or debit payment server 60) corresponding to the bank selected by the user. Further, the user registration means 207 obtains the bank-side user ID from the transfer destination of the registration request. 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. When the registration is completed, the user registration means 207 sends a notification of completion of the registration process to the user terminal 12.

(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, a distribution request unit 313, an affiliated store registration unit 314, and a user registration unit 315. 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, the distribution means 402, the affiliated store registration means 314, and the user registration means 315 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 gateway 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 means 401 completes the provisional payment, 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.

When the member store registration means 314 receives a registration request from the distribution server 20, it queries the bank system 51 for the account information in the registration request, and if the member store's account can be confirmed, it issues a member store ID and registers the member store along with the account information. Register in the store DB 311a. If the registration request includes distribution date information, the member store registration means 314 registers the distribution date information in the member store DB 311a. On the other hand, if the registration request does not include distribution date information, member store registration means 314 requests distribution date information from member store terminal 11 via distribution server 20. When registration is completed, member store registration means 314 notifies distribution server 20 of completion of registration.

When the user registration means 315 receives a registration request from the distribution server 20, it queries the bank system 51 for the account information in the registration request, and if the user's account can be confirmed, it issues a user ID and registers it together with the account information in the user DB 311b. do. When registration is completed, user registration means 315 notifies distribution server 20 of completion of registration.

[2. Process flow]
Next, the flow of payment processing and registration processing according to this embodiment will be explained.

(Flow of payment processing)
First, 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.

(Flow of registration process)
The flow of the registration process executed by the distribution server according to this embodiment will be described with reference to FIG. 14. FIG. 14 is a flow diagram for explaining the flow of registration processing executed by the distribution server according to this embodiment. Note that since the registration process for users and member stores is substantially the same, in the explanations of FIGS. The explanation will proceed by referring to them as "terminals" without distinguishing between them.

(S301) When the payment application is started on the terminal and the screen transitions to a registration screen for registering a registrant, the distribution server 20 sends a list of banks (bank list) that can be used for payment with the payment service to the terminal. Send. When the terminal receives the bank list, the payment application screen transitions to a bank list display screen.

(S302) The distribution server 20 determines whether a bank has been selected from the bank list within a predetermined time (for example, within 3 minutes). If the registrant selects a bank within the predetermined time and the terminal notifies the selected bank, the process advances to S303. On the other hand, if the registrant does not select a bank within the predetermined time and the selected bank is not notified even after the predetermined time has elapsed, the bank list is hidden and the process proceeds to S310.

(S303) The distribution server 20 refers to the registrant DB (affiliated store DB 201a, user DB 201b) and determines whether the selected bank account has already been registered as a payment account. If there is already a registered account with the selected bank, a record exists in the registrant DB that associates the registrant's terminal ID with the selected bank. In this case, the process advances to S304. On the other hand, if there is no registered account at the selected bank, the process advances to S305.

(S304) The distribution server 20 determines whether the selected bank is a bank that allows registration of multiple accounts (hereinafter referred to as a specific bank) as a payment account. If the selected bank is a specific bank, the process advances to S305. On the other hand, if the selected bank is not a specific bank, the process advances to S310. Note that if the selected bank is not a specific bank, the distribution server 20 may delete or freeze (invalidate) the record in the registrant DB corresponding to the selected bank.

(S305) The allocation server 20 causes the terminal to display the terms and conditions common to all banks that provide payment services via the allocation server 20. When the registrant confirms and agrees to the displayed terms and conditions, the distribution server 20 controls the payment application on the terminal to transition to an input screen for registrant information and account information. For example, an input form is displayed on the screen of a payment app.

(S306) When the registrant completes the input of registrant information and account information by the registrant and receives a registration request including the registrant information and account information from the terminal, the distribution server 20 sends the server corresponding to the selected bank (X1 bank The registration request is transferred to the payment management server 31, the X2 bank payment management server 32, and the debit payment server 60). When the registrant's account is confirmed at the transfer destination of the registration request, the registrant's account information is registered and a bank-side ID (bank-side member store ID, bank-side user ID) is issued.

(S307) The distribution server 20 determines whether the bank ID could be obtained from the transfer destination of the registration request. If the bank ID can be obtained, the process advances to S308. On the other hand, if the bank ID cannot be obtained, the process advances to S310.

(S308, S309) The distribution server 20 issues a terminal-side ID (terminal-side member store ID, terminal-side user ID), and links it with the bank-side ID to the registrant along with the terminal ID and registrant information. Store in DB. Then, the distribution server 20 sends a notification to the registrant's terminal that the registration has been completed. When the process of S309 is completed, the series of processes shown in FIG. 14 ends.

(S310) The distribution server 20 sends a notification to the registrant's terminal that the registration has failed. When the process of S310 is completed, the series of processes shown in FIG. 14 ends.

As mentioned above, according to the process flow of FIG. 14, not only when the bank ID cannot be obtained (Case #3: S307), but also when the bank is not selected within a predetermined time (Case #1: (see S302), the selected bank already has a registered account and the selected bank is not a specific bank (case #2: see S303, S304), the process reaches S310. The condition of case #1 improves security by making the display of the bank list one-time. The conditions for case #2 are to prevent the expansion of unauthorized use and increase security by making it a rule to register one account per bank, with the exception of specific banks. Such a processing flow can contribute to improving security.

Next, the flow of the registration process executed by the terminal according to this embodiment will be described with reference to FIGS. 15 and 16. FIG. 15 is a first flow diagram for explaining the flow of registration processing performed by the terminal according to the present embodiment. FIG. 16 is a second flow diagram for explaining the flow of the registration process executed by the terminal according to the present embodiment.

(S321) When the registrant starts the payment application on the terminal and performs an operation to transition the display screen of the payment application to the registration screen, the payment application acquires the bank list from the distribution server 20.

(S322) The payment application acquires the location information of the terminal and identifies banks around the current location. At this time, the payment application may identify nearby banks using map information acquired via the network NW, or may identify nearby banks using map information stored in the terminal in advance. You can.

(S323) The payment application checks whether any other payment application is installed on the terminal. If other payment apps are installed on the device, the payment app identifies banks associated with the other payment apps. For example, if the other payment application is a payment application program of X1 Bank, the payment application specifies X1 Bank as a bank related to the other payment application. Furthermore, if the other payment application is a payment application program that can register multiple banks, the payment application identifies the multiple banks as banks related to the other payment application.

(S324) If there is historical data indicating the movement history of the terminal, the payment application detects the bank-related facilities where the registrant stopped by by comparing the movement history of the terminal with the locations of bank-related facilities, and detects the bank-related facilities where the registrant stopped by. The history of visited bank-related facilities is saved on the terminal as a visit history. If there is a history of visits, the payment app identifies the bank that corresponds to the bank-related facility that the registrant visited.

(S325) The payment application inquires about the number of registrations for each bank in the allocation server 20, and acquires information on the number of registrations from the allocation server 20.

(S326) The payment application controls the order of the bank list so that the banks specified in the processes of S322 to S324 are placed at the top. Further, the payment application displays the remaining banks in descending order of the number of registrations below the bank specified in the processing of S322 to S324.

Note that if a bank is specified in multiple processes among S322 to S324, the order of banks may be determined according to a preset priority. For example, if the priority is set in the order of S322, S323, and S324, the payment application displays the banks specified in the process of S322 or less at the top, and the banks specified in the process of S323 below that. The banks having the specified number or less are displayed, and the banks having the predetermined number or less specified in the process of S324 are displayed further below. At this time, the payment app prevents the same bank from being displayed twice. The predetermined number can be set to any number greater than or equal to one.

As a modification, the payment application may arrange the set of banks identified in the processing of S322 to S324 in order of the number of registrations, and then arrange the remaining banks in order of the number of registrations below that. Further, the payment application may identify the bank only by the process selected by the registrant from S322 to S324. Further, the payment application may omit the processing of S322 to S324 and sort all the banks in descending order of the number of registrations. Note that the order of the processing in S322 to S325 may be changed.

(S327) The payment application displays an advertisement for a bank where an account can be opened from the terminal when a predetermined period of time (for example, 1 minute) has elapsed after the bank list was scrolled to the bottom. The banks displayed in the advertisement are those included in the bank list. This advertisement display facilitates the procedure for opening an account on the spot when the registrant cannot find a bank corresponding to his/her account in the bank list.

(S328) The payment application determines whether a bank is selected from the bank list within a predetermined time (for example, 3 minutes). Note that this determination may be performed on the distribution server 20 side via a payment application. If a bank is selected within the predetermined time, the process advances to S329. On the other hand, if no bank is selected within the predetermined time, the bank list is hidden and the process proceeds to S335.

(S329) The payment application notifies the allocation server 20 of the selected bank. Upon receiving the notification of the selected bank, the allocation server 20 determines whether there is a registered account of the selected bank, and if there is a registered account, it is determined whether the selected bank allows multiple account registration. Then, if there is no registered account at the selected bank, or if the selected bank allows multiple account registration, the payment application is notified that the selected bank can be registered.

(S330) The payment application determines whether account registration at the selected bank is possible based on the notification from the distribution server 20. If account registration at the selected bank is possible, the process advances to S331. On the other hand, if account registration at the selected bank is not possible, the process advances to S335.

(S331) The payment application displays the terms and conditions common to all banks that provide payment services via the distribution server 20. If the registrant confirms and agrees to the terms and conditions, the payment application displays an input form for entering registrant information and account information, and accepts the registrant's input of information.

(S332) The payment application transmits a registration request including the information input by the registrant to the distribution server 20. In response to this registration request, a registration process is executed on the distribution server 20 side, and when the registration process is completed, a notification to the effect that the registration has been completed is sent to the payment application.

(S333) The payment application determines whether a registration completion notification has been received from the distribution server 20. If a registration completion notification is received, the process advances to S334. On the other hand, if a notification that registration has failed is received, the process advances to S335.

(S334) The payment application displays a registration completion message on the screen. Thereafter, the registrant will be able to use the payment app to use the payment service using the registered account. When the process of S334 is completed, the series of processes shown in FIGS. 15 and 16 ends. Note that, after displaying the registration completion message, when transitioning to a predetermined screen (for example, the top page) of the payment application, the payment application may display an advertisement of the selected bank. Further, the payment application may be configured to allow payment to be made using a payment application program provided by the selected bank.

(S335) The payment application displays a registration failure message on the screen. When the process of S335 is completed, the series of processes shown in FIGS. 15 and 16 ends. Note that if registration fails due to multiple account registration, the payment application may display a message recommending the use of a specific bank that allows multiple account registration.

(GUI of registration screen)
With reference to FIG. 17, a GUI (Graphical User Interface) provided by the payment application of the terminal during the registration process according to this embodiment will be described. FIG. 17 is a schematic diagram for explaining the GUI provided by the payment application of the terminal during the registration process according to the present embodiment. Note that the payment application 121c will be explained here as an example. The user terminal 12 illustrated in FIG. 17 includes a display 12a and a camera 12b.

FIG. 17 schematically shows registration screens R1, R2, and R3. A bank list is displayed on the registration screen R1. The bank list includes button objects Bt1, Bt2, Bt3, and Bt4 for selecting bank X1, bank X2, bank Y1, and bank Y2, respectively. For example, to select Bank X1, the user only has to touch button object Bt1. When any one of the button objects Bt1, Bt2, Bt3, and Bt4 is touched, information on the selected bank is transmitted to the distribution server 20.

If account registration at the selected bank is possible, a registration screen R2 is displayed on the display 12a. The registration screen R2 displays a terms and conditions display area Ct1 for displaying the terms and conditions, a button object Bt5 for indicating the intention to agree to the terms and conditions, and a button object Bt6 for returning to the registration screen R1. In the terms and conditions display area Ct1, terms and conditions common to all banks in the bank list are displayed. When the button object Bt5 is touched, the display screen of the display 12a changes to the registration screen R3. When the button object Bt6 is touched, the display screen of the display 12a changes to the registration screen R1.

An account information input form Ac1 for inputting account information is displayed on the registration screen R3. The account information input form Ac1 is provided with an input field for account type, an input field for store number, an input field for account number, and an input field for account holder. The input fields for the account type and store number may include an input assistance mechanism such as displaying a list of options.

Further, on the registration screen R3, a button object Bt7 for activating a function that assists input of account information by capturing an image of a cash card or passbook is displayed. When the button object Bt7 is touched, the camera function of the user terminal 12 (imaging function by the camera 12b) is activated, and the display screen of the display 12a changes to an imaging screen. When the user takes an image of the cash card or passbook with the camera 12b, the display screen of the display 12a changes to a registration screen R3. At this time, the payment application 121c analyzes the imaging data, obtains at least part of the account type, store number, account number, and account holder, and displays the obtained information in an editable state in the input field. . This reduces the burden of inputting account information.

When information is entered in each input field and the button object Bt8 is touched, the payment application 121c displays an input form for entering user information other than account information, and displays a message prompting the user to input user information. indicate. When the input of user information is completed, the payment application 121c transmits a registration request to the distribution server 20. When the registration is completed, the payment application 121c displays a registration completion message on the display 12a. Note that the registration screen schematically shown in FIG. 17 is an example, and can be modified as appropriate depending on the implementation mode.

[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. 18, a payment flow using a member store terminal and a user terminal according to a modified example of this embodiment will be described. FIG. 18 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.

(S401) 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.

(S402) 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.).

(S403) 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.

(S404) 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.

(S405) 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.

(S406, S407) 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 S406 and S407 are completed, the series of processes shown in FIG. 18 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 12a Display 12b Camera 20 Distribution server 31 X1 bank payment management server 32 X2 bank payment management server 40 Transfer gateway server 51 X1 bank system 52 X2 bank system 53 Y1 bank system 54 Y2 bank system 60 Debit payment Servers 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 116, 126 List display means 117 , 127 Registration requesting means 118, 128 Imaging means 119, 129 Location information acquisition means 122 Code reading means 123 Bank selection means 124 Payment requesting means 125 Receipt displaying 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 314 Member store registration means 315 User registration means 401 Temporary payment means 402 Distribution means Ac1 Account information input form Bt1, Bt2, Bt3, Bt4, Bt5, Bt6, Bt7, Bt8 Button object Ct1 Terms and conditions display Area R1, R2, R3 Registration screen SVG1 1st service group SVG2 2nd service group NW Network

Claims (15)

a memory storing a payment program that enables the use of a first payment service provided by a first bank group and a second payment service provided by a second bank group, and the payment program; and a processor that runs the
When executed by the processor, the payment program:
Accept the first operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. A bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group is obtained from the distribution server, and in response to the first operation, an execution screen of the payment program is obtained. display said bank list in
accepting a third operation of selecting a bank from the bank list;
Inquiring of the distribution server whether the bank account selected by the third operation is already registered as a bank account to be used for the payment, and if the selected bank account is not registered; and a terminal device that executes a process for registering the account as a bank account to be used for the payment . The payment program is
After displaying the bank list, when a first predetermined time period has elapsed without a second operation for selecting a bank to be used for payment, hiding the bank list;
The terminal device according to claim 1. a memory storing a payment program that enables use of a first payment service provided by a first bank group and a second payment service provided by a second bank group; and the payment program and a processor that runs the
When executed by the processor, the payment program:
Accept the first operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. A bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group is obtained from the distribution server, and in response to the first operation, an execution screen of the payment program is obtained. display said bank list in
accepting a third operation of selecting a bank from the bank list;
The bank selected by the third operation is notified to the distribution server, and the selected bank is either a licensed bank that allows registration of multiple accounts or an unauthorized bank that does not allow registration of multiple accounts. receive a notification regarding the determination result;
When the selected bank is the unauthorized bank, the distribution server is inquired as to whether or not the selected bank account has already been registered as a bank account to be used for the payment; If a bank account is not registered, execute the process to register the bank account as the bank account to be used for the payment.
A terminal device that executes processing . The payment program is
After displaying the bank list, when a first predetermined time period has elapsed without a second operation for selecting a bank to be used for payment, hiding the bank list;
The terminal device according to claim 3. The terminal device further includes a sensor unit that acquires the current position of the terminal device,
When displaying the bank list, the payment program displays banks around the current location at the top.
The terminal device according to any one of claims 1 to 4. The payment program detects a bank application program installed on the terminal device, and when displaying the bank list, displays banks corresponding to the bank application program at the top.
The terminal device according to any one of claims 1 to 4. The terminal device further includes a sensor unit that acquires the current location of the terminal device,
The payment program is
The movement route of the terminal device obtained using the sensor unit is compared with the location of the bank or bank-related facility, and the comparison result is analyzed to determine the location of the bank or bank-related facility where the user of the terminal device stopped by. identifying a bank corresponding to a location and displaying the identified bank at the top when displaying the bank list;
The terminal device according to any one of claims 1 to 4. If a separate program for payment that enables the use of the first payment service and the second payment service is stored in the memory, the payment program, when displaying the bank list, Display banks registered at the top,
The terminal device according to any one of claims 1 to 4. The payment program is
For banks registered by a user who uses a program similar to the payment program, information regarding the number of registrations of each bank or the list of banks sorted in descending order of the number of registrations is obtained from the distribution server;
When displaying the bank list, the banks with a larger number of registrations are displayed higher up;
The terminal device according to any one of claims 1 to 4. The terminal device further includes an imaging unit,
The payment program is
A process of acquiring an image of a cash card or passbook captured using the imaging unit, and registering a bank account to be used for the payment using bank and account information read from the acquired image. execute,
The terminal device according to claim 1. The payment program is
When the bank list is scrolled to the bottom and a second predetermined time period has elapsed, an advertisement for a bank where an account can be opened is displayed on the execution screen of the payment program via the connection network of the terminal device.
The terminal device according to any one of claims 1 to 10. A payment program that enables use of a first payment service provided by a first bank group and a second payment service provided by a second bank group, the program comprising:
Accept the operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. Obtaining a bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group from the distribution server, and executing the payment program in response to the start operation. display the bank list on the screen;
accept an operation to select a bank from the bank list;
Inquire of the distribution server whether or not the bank account selected by the selection operation is already registered as a bank account to be used for the payment, and if the selected bank account is not registered, , a payment program that causes a computer to execute a process for registering the account as a bank account to be used for the payment. A payment program that enables use of a first payment service provided by a first bank group and a second payment service provided by a second bank group,
Accept the operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. Obtaining a bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group from the distribution server, and executing the payment program in response to the start operation. display the said bank list on the screen;
accept an operation to select a bank from the bank list;
Notify the distribution server of the bank selected by the selection operation, and determine whether the selected bank is a licensed bank that allows registration of multiple accounts or a non-licensed bank that does not allow registration of multiple accounts. receive a notification regarding the determination result from the distribution server,
When the selected bank is the unauthorized bank, the distribution server is inquired as to whether or not the selected bank account has already been registered as a bank account to be used for the payment; If a bank account is not registered, execute the process to register the bank account as the bank account to be used for the payment.
A payment program that causes a computer to perform processing. A computer that executes a payment program that enables the use of a first payment service provided by a first bank group and a second payment service provided by a second bank group,
Accept the first operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. A bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group is obtained from the distribution server, and in response to the first operation, an execution screen of the payment program is obtained. display said bank list in
accept an operation to select a bank from the bank list;
Inquire of the distribution server whether or not the bank account selected by the selection operation is already registered as a bank account to be used for the payment, and if the selected bank account is not registered, , a method for registering a payment account, which executes a process for registering the account as a bank account to be used for the payment. A computer that executes a payment program that enables the use of a first payment service provided by a first bank group and a second payment service provided by a second bank group,
Accept the first operation to start registering the bank account used for payment,
Distributing payment processing between a first server device that executes processing related to direct debits for banks in the first bank group and a second server device that manages payment related processing in the second bank group. A bank list indicating each bank belonging to the first bank group and each bank belonging to the second bank group is obtained from the distribution server, and in response to the first operation, an execution screen of the payment program is obtained. display the said bank list in
accept an operation to select a bank from the bank list;
Notify the distribution server of the bank selected by the selection operation, and determine whether the selected bank is a licensed bank that allows registration of multiple accounts or a non-licensed bank that does not allow registration of multiple accounts. receive a notification regarding the determination result from the distribution server,
When the selected bank is the unauthorized bank, the distribution server is inquired as to whether or not the selected bank account has already been registered as a bank account to be used for the payment; If a bank account is not registered, execute the process to register the bank account as the bank account to be used for the payment.
A payment account registration processing method that executes the process.

Images