Service cooperation system and service cooperation method

Abstract

To provide a service cooperation system and a service cooperation method for efficiently performing transactions.SOLUTION: A service cooperation system A1 includes a second server 30 which is connected to a first server 20 providing a first settlement service and provides a second settlement service, and user terminals 10 using the first settlement service. Then, a second server 30 executes image generation processing for generating an image identifier to be included in a code image to be used for settlement, and association processing for associating and storing the anonymous identifier generated by the first server 20 and the image identifier. Further, when acquiring the image identifier of the code image read by the reading terminal, the second server 30 executes settlement stage processing for making the first server 20 execute the settlement of the transaction of the anonymous identifier associated with the image identifier.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a service collaboration system and a service collaboration method for performing payments. [Background technology]

[0002] Payments may be made at member stores of various payment services (see, for example, Patent Document 1). In the technology described in this document, a payment server acquires a transaction instruction from a payment application selected by a portal application on a user terminal. Then, after processing the transaction in accordance with the transaction instruction using a code image, the payment server provides transaction identification information for the transaction instruction to the portal server of the portal application. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-96292 Summary of the Invention [Problem to be solved by the invention]

[0004] However, a merchant who wishes to use a code image for a transaction may not necessarily be a member of the payment service the user uses. In this case, the user cannot make a payment using the payment service they desire. If a new membership registration is required, the process becomes complicated. [Means for solving the problem]

[0005] A service collaboration system that solves the above problem includes a first server that provides a first payment service, a second server that is connected to the first server that provides a second payment service, and a user terminal that uses the first payment service. The second server executes an image generation process in which the second server generates an image identifier to be included in a code image used for payment, an association process in which the first server associates and stores the anonymous identifier generated by the first server with the image identifier, and a payment stage process in which, when the second server acquires the image identifier of the code image read by a reading terminal, the first server executes payment for the transaction of the anonymous identifier associated with the image identifier. [Effects of the Invention]

[0006] According to the present invention, transactions can be carried out efficiently. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is an explanatory diagram of a service collaboration system according to an embodiment. [Figure 2] FIG. 2 is an explanatory diagram of a hardware configuration of the embodiment. [Figure 3] FIG. 10 is an explanatory diagram of a settlement processing procedure according to the CPM method of the embodiment. [Figure 4] FIG. 10 is an explanatory diagram of a payment processing procedure using the dynamic MPM method according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of a service collaboration system and a service collaboration method will be described with reference to Figures 1 to 4. In this embodiment, it is assumed that a transaction (payment) is carried out using a collaboration service that collaborates multiple services, such as a first payment service and a second payment service.

[0009] As shown in FIG. 1, in this embodiment, a service collaboration system A1 uses a user terminal 10, a store terminal 15, a first server 20, a second server 30, and the like, which are connected via a network.

[0010] (Hardware configuration) 2, the hardware configuration of the information processing device H10 that constitutes the user terminal 10, the store terminal 15, the first server 20, and the second server 30 will be described. The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is an example, and it can also be realized by other hardware.

[0011] The communication device H11 is an interface that establishes a communication path with another device and executes data transmission and reception, and is, for example, a network interface or a wireless interface.

[0012] The input device H12 is a device that accepts input from a user, etc., and is, for example, a mouse, a keyboard, etc. The display device H13 is a display, etc. that displays various information. A touch panel display, etc., functions as the input device H12 and the display device H13.

[0013] The storage device H14 is a storage device that stores data and various programs for executing various functions of the user terminal 10, the store terminal 15, the first server 20, and the second server 30. Examples of the storage device H14 include a ROM, a RAM, a hard disk, etc.

[0014] The processor H15 uses programs and data stored in the storage device H14 to control each process in the user terminal 10, the store terminal 15, the first server 20, and the second server 30. Examples of the processor H15 include a CPU and an MPU. The processor H15 loads programs stored in a ROM or the like into a RAM and executes various processes for each process.

[0015] The processor H15 is not limited to a processor that performs all of its processing using software. For example, the processor H15 may include a dedicated hardware circuit (e.g., an application-specific integrated circuit (ASIC)) that performs hardware processing for at least part of the processing it performs. That is, the processor H15 may be configured with the following:

[0016] (1) One or more processors operating according to a computer program (software) (2) One or more dedicated hardware circuits that perform at least some of the processes; or (3) Circuits, including combinations thereof The processor includes a CPU and memory, such as RAM and ROM, that stores program code or instructions configured to cause the CPU to perform processes. Memory, or computer-readable media, includes any available media that can be accessed by a general-purpose or special-purpose computer.

[0017] (System Configuration) Next, the functions of the user terminal 10, the store terminal 15, the first server 20, and the second server 30 will be described with reference to FIG.

[0018] The user terminal 10 is a computer terminal (for example, a mobile terminal) used by a user. The user terminal 10 includes an application execution unit 11, and executes an application stored in a storage unit. In this embodiment, the user terminal 10 executes a payment application 11a.

[0019] The payment application 11a is an application program that functions as a transaction application for using the first payment service provided by the first server 20 and manages user accounts. In this embodiment, the first server 20 manages the balance of the account held by the user of the payment application 11a, and the user can make payments by using the balance of this account. The payment method is not limited to using the balance, and any payment method is acceptable. For example, credit settlement using a credit card or debit settlement by debiting from an account may be used.

[0020] Payment application 11a is a platform application that provides an execution environment for mini application 11b to operate. Mini application 11b uses web technology (WebView) to use the second payment service provided by second server 30. For this purpose, mini application 11b stores information about the access destination of second server 30.

[0021] The store terminal 15 is a computer terminal (e.g., a mobile terminal) used by a business partner store. The store terminal 15 is used to use the second payment service. For this purpose, the store terminal 15 stores information related to the affiliated store ID and communicates with the second server 30.

[0022] First server 20 functions as a payment server and is a computer system of a service provider that provides payment services via payment application 11a. First server 20 manages the balances of accounts held by users of payment application 11a. First server 20 includes control unit 21 and user information storage unit 22.

[0023] The control unit 21 functions as an authentication unit 211 and a management unit 212 by executing an account management program. The authentication unit 211 executes a process for authenticating a user. The management unit 212 executes a process for managing transactions (for example, payments) using a user's account.

[0024] User management data is recorded in the user information storage unit 22. This user management data is recorded when a user opens an account, and is updated when a payment or the like is made using the account. The user management data records data related to the user ID, user information, authentication information, and balance.

[0025] The user ID is an identifier for identifying the user's account of the payment application 11a. User information is data about the user who holds the account (such as name, address, contact information, etc.). The authentication information is data for authenticating a user. The balance is the remaining balance in this account.

[0026] Furthermore, the user information storage unit 22 stores transaction history records in association with the user management data. The transaction history record is recorded when a transaction is made using a user's account. The transaction history record includes information such as the transaction number, transaction date and time, transaction content, and amount.

[0027] The transaction number is an identifier (anonymous identifier) ​​for identifying each transaction. This transaction number can identify the use of the first payment service. This transaction number is an identifier that is not related to credit card numbers or other card member data, and is issued as a unique number for each transaction.

[0028] The transaction date and time is the date and time when the transaction was made. The transaction details include the type of transaction (payment, deposit, etc.) and the trading partner. The amount is the amount of the transaction (payment amount, deposit amount, etc.).

[0029] Second server 30 is a computer system of a service provider that provides a second payment service via a payment app different from payment app 11a. This second server 30 manages the balances of accounts held by users who use the second payment service. This second server 30 includes a control unit 31, an affiliated store information storage unit 32, and a transaction information storage unit 33. The control unit 31 functions as a generation unit 311 and a transaction unit 312 by executing the service cooperation program. The generation unit 311 executes a process of generating a code character string to be included in a code image used in the second payment service. The transaction unit 312 executes a process to support payments using the first payment service at member stores of the second payment service.

[0030] Member store management data is recorded in the member store information storage unit 32. This member store management data is recorded when an account is opened by a member store and is updated when a payment is made. The member store management data includes data related to the member store ID, member store information, authentication information, member store account, and sales.

[0031] The affiliated store ID is an identifier for identifying the affiliated store's account. Merchant information is data (such as name, address, and contact information) about merchants who hold accounts.

[0032] The authentication information is data for authenticating the affiliated store. The merchant account is an identifier (financial institution code, head office / branch code, account type, account number, etc.) that identifies the financial institution account held by this merchant. This merchant account is used, for example, to transfer sales proceeds. Sales are the sales amount of this franchise store.

[0033] Furthermore, the affiliated store information storage unit 32 stores transaction history records in association with the affiliated store management data. Transaction history records are recorded when a transaction is made using a merchant's account. Transaction history records include transaction ID, transaction date and time, transaction details, and sales data.

[0034] The transaction ID is an identifier (image identifier) ​​for identifying each transaction. The transaction date and time is the date and time when the transaction was made. The transaction details include the type of transaction (payment, etc.) and information about the sender. Sales are the sales amount of the affiliated store from this transaction.

[0035] The transaction information storage unit 33 stores transaction management records related to user transactions. Transaction management records are recorded when a transaction is made. The transaction management record includes data related to the transaction ID, acceptance date and time, remittance source ID, remittance destination ID, status, and transaction amount.

[0036] The transaction ID is an identifier for identifying each transaction. The acceptance date and time is the date and time when the code string was generated upon acceptance of this transaction. The validity period of the code image is calculated based on the acceptance date and time. The remitter ID is an identifier for identifying the remitter (customer) in this transaction.

[0037] The remittance destination ID is an identifier for identifying the remittance destination (affiliated store) in this transaction. The status is a flag that identifies the status of this transaction. If the payment is completed, a used flag (used information) is recorded, and if the sales amount is deposited into the affiliated store's account, a settlement flag is recorded. The transaction amount is the amount settled for the transaction.

[0038] (Service integration processing) Next, the service cooperation process will be described with reference to Figures 3 and 4. The service cooperation process is executed when a payment is made at a store using payment application 11a. When making a payment, there are two methods: CPM and MPM.

[0039] In the CPM method, a user (customer) uses a user terminal 10 to present a code image such as a QR code (registered trademark), which is then read by a store terminal 15 on the store side. On the other hand, in the MPM method, a user (customer) uses a user terminal 10 to read a code image presented by the store side. Note that the MPM method in this embodiment uses a dynamic MPM method in which the store side uses the store terminal 15 to use a dynamically generated code image.

[0040] (CPM method) First, a case where settlement is performed using the CPM method will be described with reference to FIG. Here, the application execution unit 11 of the user terminal 10 executes a first code request process (step S11). Specifically, the user launches the payment application 11a. In this case, the application execution unit displays a payment screen on the display device H13. Furthermore, the user selects a code request button included in this payment screen. In this case, the application execution unit 11 sends a first code request to the first server 20 using the mini application 11b. This first code request includes the user ID and authentication information.

[0041] Next, the control unit 21 of the first server 20 executes member authentication processing (step S12). Specifically, the authentication unit 211 of the control unit 21 performs member authentication using the user information storage unit 22 based on the user ID and authentication information included in the first code request. When member authentication is complete, the management unit 212 generates a transaction history record to which a transaction number (one-time code) is assigned in response to the first code request acquired from the user terminal 10, and records the record in the user information storage unit 22 in association with the user ID.

[0042] The control unit 21 of the first server 20 executes a second code request process (step S13). Specifically, the management unit 212 of the control unit 21 sends a second code request to the second server 30. The second code request includes the transaction number.

[0043] Next, the control unit 31 of the second server 30 executes a transaction ID issuing process (step S14). Specifically, the generation unit 311 of the control unit 31 generates transaction management data with the transaction ID assigned in response to the second code request, and records the data in the transaction information storage unit 33 (image generation process). This transaction management data records the current date and time as the acceptance date and time, and the transaction number as the remitter ID (association process).

[0044] Next, the control unit 31 of the second server 30 executes a code string transmission process (step S15). Specifically, the generation unit 311 of the control unit 31 generates a code string including the transaction ID and transmits it to the first server 20.

[0045] Next, the control unit 21 of the first server 20 executes a code string transfer process (step S16). Specifically, the management unit 212 of the control unit 21 transmits the code string acquired from the second server 30 to the user terminal 10 that made the first code request.

[0046] Next, application execution unit 11 of user terminal 10 executes a code string acquisition process (step S17). Specifically, application execution unit 11 acquires a code string from first server 20 by mini application 11b of payment application 11a.

[0047] Next, the application execution unit 11 of the user terminal 10 executes a code display process (step S18). Specifically, the application execution unit 11 generates a code image by encoding the code string using the mini application 11b of the payment application 11a, and outputs the code image to the display device H13.

[0048] Next, the store terminal 15 (reading terminal) executes a code reading process (step S19). Specifically, the user presents the user terminal 10 on which the code image is output to the store. Then, using the store terminal 15, the code image output on the display device H13 of the user terminal 10 is read and the code character string is decoded. Furthermore, the payment amount is input into the store terminal 15. Then, the store terminal 15 transmits the affiliated store ID, the code character string, and the payment amount to the second server 30.

[0049] Next, the control unit 31 of the second server 30 executes a code character string check process (step S20). Specifically, the transaction unit 312 of the control unit 31 determines whether the code character string acquired from the first server 20 satisfies the usage conditions (validity). Here, the following are used as the usage conditions:

[0050] The transaction ID of the code string is recorded in the transaction information storage unit 33. The time elapsed since the date and time of receipt of the transaction ID in the code string is within the validity period. The transaction ID of the code string is unused and the used flag is not recorded. If the transaction ID of the code string does not satisfy any of the usage conditions, the transaction unit 312 returns transaction disapproval information to the store terminal 15. On the other hand, if the transaction ID of the code string satisfies all of the usage conditions, the transaction unit 312 records the remittance destination ID (affiliated store ID) and transaction amount (payment amount) in the transaction management data for the transaction ID corresponding to the code string.

[0051] Next, the control unit 31 of the second server 30 executes a payment request process (payment stage process) (step S21). Specifically, the transaction unit 312 of the control unit 31 identifies the transaction number associated with the transaction ID corresponding to the code string in the transaction information storage unit 33. Then, the transaction unit 312 sends a payment request to the first server 20. This payment request includes the transaction number, payment amount, and affiliated store ID.

[0052] Next, the control unit 21 of the first server 20 executes the payment process (step S22). Specifically, the management unit 212 of the control unit 21 identifies the user ID using the transaction number in the user information storage unit 22. The management unit 212 then performs the payment by debiting the payment amount from the balance of the user's account. The transaction history record records the transaction date and time (current date and time), transaction details (payment), business partner (affiliated store ID), and amount (payment amount). The management unit 212 then outputs the payment result to the user terminal 10.

[0053] In this case, the application execution unit 11 of the user terminal 10 executes a payment result display process (step S23). Specifically, the application execution unit 11 outputs the payment result to the display device H13 using the payment application 11a. Furthermore, the control unit 21 of the first server 20 executes a payment result return process (step S24). Specifically, the management unit 212 of the control unit 21 returns the payment result to the second server 30.

[0054] Next, the control unit 31 of the second server 30 executes a payment result registration process (step S25). Specifically, the transaction unit 312 of the control unit 31 obtains the payment result from the first server 20. The transaction unit 312 then records the status (used flag) of the transaction management data in the transaction information storage unit 33. The transaction unit 312 then records the transaction ID, transaction date and time, transaction details, and amount in the transaction history record in the affiliated store information storage unit 32. The transaction unit 312 then transmits payment completion information to the store terminal 15. Next, the store terminal 15 executes a payment result display process (step S26). Specifically, the store terminal 15 outputs payment completion information to the display device H13.

[0055] (Dynamic MPM method) Next, a case where payment is made using the dynamic MPM method will be described with reference to FIG.

[0056] First, the store terminal 15 executes a code request process (step S31). Specifically, when conducting a transaction with a user (customer), the store clerk inputs the payment amount into the store terminal 15 and transmits a code request to the second server 30. This code request includes information about the affiliated store ID and the payment amount.

[0057] Next, the control unit 31 of the second server 30 executes a transaction ID issuance process (image generation process) (step S32). Specifically, the generation unit 311 of the control unit 31 generates transaction management data with the transaction ID used to generate the code image, and records it in the transaction information storage unit 33. This transaction management data records the acceptance date and time (current date and time), remittance destination ID (affiliated store ID), and transaction amount (payment amount).

[0058] Next, the control unit 31 of the second server 30 executes a code character string transmission process (step S33). Specifically, the generation unit 311 of the control unit 31 generates a code character string including the transaction ID and transmits it to the shop terminal 15.

[0059] Next, the store terminal 15 executes a code display process (step S34). Specifically, the store terminal 15 generates a code image by encoding the code character string acquired from the second server 30, and outputs the code image to the display device H13.

[0060] Next, the application execution unit 11 of the user terminal 10 (reading terminal) executes a code acquisition process (step S35). Specifically, the user launches the payment application 11a. In this case, the application execution unit 11 displays a payment screen on the display device H13. Furthermore, the user selects the code reading button included in this payment screen. In this case, the application execution unit 11 reads the code image output to the display device H13 of the store terminal 15 by the mini application 11b of the payment application 11a, and decodes the code character string.

[0061] Next, the application execution unit 11 of the user terminal 10 executes a code string transmission process (step S36). Specifically, the application execution unit 11 transmits a code verification request to the first server 20. This code verification request includes the user ID, authentication information, and the decoded code string.

[0062] Next, control unit 21 of first server 20 executes member authentication processing (step S37). Specifically, authentication unit 211 of control unit 21 performs member authentication using the user ID and authentication information included in the code verification request.

[0063] Next, the control unit 21 of the first server 20 executes a transaction number assignment process (step S38). Specifically, the management unit 212 of the control unit 21 assigns a transaction number (one-time code) to the code verification request acquired from the user terminal 10, associates it with the user ID, and records it in the user information storage unit 22. The management unit 212 then transmits a code request including the transaction number to the second server 30.

[0064] Next, the control unit 31 of the second server 30 executes a code string check process (step S39), similar to step S20. In this case, the transaction unit 312 also checks whether the code string obtained from the first server 20 satisfies the usage conditions. If the transaction ID of the code string satisfies all the usage conditions, the transaction unit 312 records the transaction number as the remitter ID in the transaction management data of the transaction ID corresponding to the code string (association process).

[0065] Next, the control unit 31 of the second server 30 executes a confirmation result return process (step S40). Specifically, the transaction unit 312 of the control unit 31 transmits the confirmation result to the first server 20. This confirmation result includes data related to the transaction number and the settlement amount.

[0066] Next, the control unit 21 of the first server 20 executes a confirmation screen display process (step S41). Specifically, the management unit 212 of the control unit 21 outputs a confirmation screen to the user terminal 10. This confirmation screen includes information related to the payment amount.

[0067] Next, the application execution unit 11 of the user terminal 10 executes a payment confirmation process (step S42). Specifically, the application execution unit 11 outputs the payment result to the display device H13 using the mini application 11b of the payment application 11a. After confirming the payment amount, the user confirms the payment by entering a confirmation.

[0068] Next, application execution unit 11 of user terminal 10 executes a payment request process (step S43). Specifically, application execution unit 11 sends a payment request to first server 20 by mini application 11b of payment application 11a. This payment request includes a transaction number.

[0069] Next, the control unit 21 of the first server 20 executes the payment process in the same manner as in step S22 (step S44). Next, the application execution unit 11 of the user terminal 10 executes the payment result display process in the same manner as in step S23 (step S45).

[0070] Next, the control unit 21 of the first server 20 executes a payment request process (step S46). Specifically, the management unit 212 of the control unit 21 transmits a payment request to the second server 30. This payment request includes information related to the transaction number.

[0071] Next, the control unit 31 of the second server 30 executes the payment result registration process in the same manner as in step S25 (step S47). Next, the store terminal 15 executes the payment result display process in the same manner as in step S26 (step S48).

[0072] (Clearance process) Next, the settlement process for sales at affiliated stores of the second payment service will be described. The second server 30 performs a settlement process for sales from the linked service at a predetermined timing. In this case, the second server 30 extracts, from the transaction information storage unit 33, transaction management data in which a transaction number is recorded from among the transaction management data in which a settlement flag is not recorded. The second server 30 then collects the transaction amount from the provider of the first payment service. Furthermore, the second server 30 uses the affiliated store information storage unit 32 to identify the affiliated store account of the affiliated store corresponding to the remittance destination ID in the transaction management data, and settles the transaction by depositing the collected amount into this affiliated store account.

[0073] (Action of this embodiment) Since the second server 30 provides the first payment service to the user terminal 10 via the first server 20, there is no need to know the member information of the first payment service.

[0074] (Effects of this embodiment) (1) In this embodiment, the application execution unit 11 of the user terminal 10 executes a first code request process (step S11). The control unit 21 of the first server 20 executes a member authentication process (step S12) and a second code request process (step S13). In this case, the first server 20 uses the transaction number, so the second code request can be made without providing user information to the second server 30. (2) In this embodiment, the control unit 31 of the second server 30 executes a transaction ID issuing process (step S14) and a code string sending process (step S15). The control unit 21 of the first server 20 executes a code string transferring process (step S16). This allows the code string to be provided to the user terminal 10 via the first server 20 without directly communicating with the user terminal 10.

[0075] (3) In this embodiment, the application execution unit 11 of the user terminal 10 executes a code display process (step S18). Next, the store terminal 15 executes a code reading process (step S19). This allows a transaction to be performed using a code image, similar to the second payment service.

[0076] (4) In this embodiment, the control unit 31 of the second server 30 executes a code character string check process (step S20). This makes it possible to prevent fraudulent transactions, similar to the second payment service.

[0077] (5) In this embodiment, the control unit 31 of the second server 30 executes a payment request process (step S21). The control unit 21 of the first server 20 executes a payment process (step S22). This makes it possible to provide a payment service to users who do not have an account with the second server 30. The member stores of the first payment service and the second payment service may be different. Even in this case, users of the first payment service can conduct transactions using the member stores of the second payment service, thereby increasing the flexibility of payment. (6) In this embodiment, the store terminal 15 executes a payment result display process (step S26), which allows the store to know that the payment has been completed.

[0078] (7) In this embodiment, the store terminal 15 executes a code request process (step S31) and a code display process (step S34). As a result, a code image used in the dynamic MPM method can be displayed, similar to the second payment service.

[0079] (8) In this embodiment, the application execution unit 11 of the user terminal 10 executes a code acquisition process (step S35) and a code character string transmission process (step S36). This allows a user of the first payment service to use the code image used in the second payment service.

[0080] (9) In this embodiment, the control unit 21 of the first server 20 executes a member authentication process (step S37) and a transaction number assignment process (step S38). This allows a transaction number to be assigned to a user of the first payment service instead of user information.

[0081] (10) In this embodiment, the control unit 31 of the second server 30 executes a code character string check process (step S39). This makes it possible to prevent fraudulent transactions, similar to the second payment service.

[0082] (11) In this embodiment, the control unit 21 of the first server 20 executes a confirmation screen display process (step S41). The application execution unit 11 of the user terminal 10 executes a payment confirmation process (step S42) and a payment request process (step S43). The control unit 21 of the first server 20 executes a payment process (step S44). This allows the user to confirm the payment details using the code image used in the second payment service and make the payment. Since the member stores of the first payment service and the second payment service may be different, the user of the first payment service can conduct transactions using the member stores of the second payment service, thereby increasing the flexibility of payment. (12) In this embodiment, the store terminal 15 executes a payment result display process (step S48), which allows the store to know that the payment has been completed.

[0083] This embodiment can be modified as follows: This embodiment and the following modifications can be combined and implemented within the scope of technical compatibility. In the above embodiment, the CPM method and the MPM method are used, but the linked service may be provided by using either one of them.

[0084] In the above embodiment, payment application 11a and mini application 11b are used, but the present invention is not limited to using mini application 11b as long as connection to second server 30 can be established via first server 20. Payment application 11a may also be customized and used.

[0085] In the above embodiment, a dynamic MPM method is used. Alternatively, a static MPM method may be used. In this case, a code image is generated by encoding the code character string obtained from the second server 30 and is displayed in advance at the store. Then, the price is set on the user terminal 10.

[0086] In the above embodiment, the store terminal 15 (reading terminal) executes the code reading process (step S19). Here, the payment amount is input into the store terminal 15. The payment amount may be obtained from the user terminal 10. In the above embodiment, it is assumed that the second server 30 manages the balance of the account held by the user who uses the second payment service. If the second payment service provides a service different from the first payment service, it is not necessary to manage the balance. In the above embodiment, the settlement process involves settling the sales of the affiliated store of the second payment service, but the settlement method is not limited to this method.

[0087] In the above embodiment, member authentication processing (steps S12, S37) is performed, but the timing of member authentication is not limited as long as it is performed before a transaction number is assigned. [Explanation of symbols]

[0088] A1...service collaboration system, 10...user terminal, 11...app execution unit, 11a...payment app, 11b...mini app, 15...store terminal, 20...first server, 21...control unit, 211...authentication unit, 212...management unit, 22...user information storage unit, 30...second server, 31...control unit, 311...generation unit, 312...transaction unit, 32...affiliated store information storage unit, 33...transaction information storage unit.

Claims

1. a second server connected to the first server providing the first payment service and providing a second payment service; A service collaboration system including: a user terminal that uses the first payment service; The second server, an image generation process for generating an image identifier to be included in a code image used for payment; an association process for associating and storing the anonymous identifier generated by the first server with the image identifier; a settlement stage process for causing the first server to execute settlement of the transaction of the anonymous identifier associated with the image identifier when the image identifier of the code image read by the reading terminal is acquired; A service collaboration system that executes the above.

2. the reading terminal is a store terminal of the second payment service, The second server, In the image generation process, receiving a code request including the anonymous identifier assigned by the first server; In response to the code request, generate the image identifier associated with the anonymous identifier and transmit the image identifier to the first server; 2. The service collaboration system according to claim 1, wherein the image identifier is acquired from the store terminal that reads the code image displayed on the user terminal in the payment stage processing.

3. the reading terminal is a user terminal of the first payment service, The second server, In the image generation process, generating the image identifier to be included in the code image used for payment, and displaying the image identifier on the store terminal of the second payment service; The service collaboration system described in claim 1, characterized in that, in the payment stage processing, the image identifier and the anonymous identifier assigned by the first server are obtained from the first server that obtained the image identifier of the code image read by the user terminal.

4. A service collaboration system as described in any one of claims 1 to 3, characterized in that when the second server obtains the image identifier of the code image read by the reading terminal, it determines validity based on the elapsed time since the image identifier was generated.

5. The second server, Recording used information for the image identifier that has completed the payment stage process; A service collaboration system described in any one of claims 1 to 3, characterized in that when the image identifier of the code image read by the reading terminal is obtained, validity is determined based on the record of the used information of the image identifier.

6. a second server connected to the first server providing the first payment service and providing a second payment service; a user terminal that uses the first payment service, and a service collaboration system including the user terminal, The second server, an image generation process for generating an image identifier to be included in a code image used for payment; an association process for associating and storing the anonymous identifier generated by the first server with the image identifier; a settlement stage process for causing the first server to execute settlement of the transaction of the anonymous identifier associated with the image identifier when the image identifier of the code image read by the reading terminal is acquired; A service collaboration method characterized by executing the above.

Images