JP7322129B2 - Service management system, transaction server and service management method - Google Patents

Description

The present disclosure relates to a service management system, transaction server and service management method for displaying transaction information.

Today, various services are provided via the Internet. A portal site system is being studied to enable a list of such various services to be grasped (see, for example, Patent Document 1). In the technique described in this document, a portal site system connects servers of a plurality of vendors and client terminals of users via a network. Then, guide users to the applications, contents, and services provided by each vendor.

Also, a technique for electronically transferring money between users by presenting an optically readable information code using a settlement application stored in a user terminal is being studied (see Patent Document 2, for example). The technology described in this document uses a server that associates and stores account identification information and balance information. Then, the first user terminal uses the information related to the account identification information of the remittance source user, the remittance amount information, and the remittance destination account read from the medium of the remittee user using the imaging device of the first user terminal. Send a remittance order containing identification information to the server. Upon receiving the remittance command, the server performs electronic remittance by storing account identification information of the remittance source user and balance information linked to the account identification information of the remittee based on the remittance amount.

WO2014/196032 JP 2019-125287 A

By using the portal service, various services can be used from one entrance. However, there are various transaction scenes, and even when using a settlement service (transaction service), there are cases where the portal service is used and there are cases where it is not used. Since the portal service and the payment service are independent services, the portal service may not be able to grasp the usage status of the payment service.

A service management system for solving the above problems includes a portal server connected via a portal application of a user terminal and a transaction server connected via a transaction application. Then, the transaction server acquires a transaction instruction from the transaction application selected by the portal application of the user terminal, performs transaction processing according to the transaction instruction, and transmits transaction identification information about the transaction instruction to the portal application. It is provided to the portal server of the application, and the portal server records the transaction identification information obtained from the transaction server. Then, when a transaction history inquiry request is obtained from the portal application, the transaction history related to the transaction identification information is obtained from the transaction server and output by the portal application.

According to the present disclosure, transaction information can be displayed efficiently.

1 is an explanatory diagram of a service management system according to an embodiment; FIG. 3 is an explanatory diagram of the hardware configuration of the embodiment; FIG. 1 is an explanatory diagram of an information storage unit according to an embodiment, in which (a) is a payment user information storage unit, (b) is a member store information storage unit, (c) is a transaction information storage unit, and (d) is a portal user information storage unit. It is an explanatory view of a part. It is an explanatory view of the processing procedure of the embodiment. It is an explanatory view of the processing procedure of the embodiment. It is an explanatory view of the processing procedure of other embodiments.

Embodiments embodying a service management system, a transaction server, and a service management method will be described below with reference to FIGS. 1 to 5. FIG. In this embodiment, it is assumed that transactions are made through a portal site.

As shown in FIG. 1, this embodiment uses a user terminal 10, a settlement server 20, a portal server 30, etc., which are connected via a network.
(Hardware configuration)
The hardware configuration of the information processing device H10 that constitutes the user terminal 10, the settlement server 20, and the portal server 30 will be described with reference to FIG. The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage unit H14, and a processor H15. Note that this hardware configuration is an example, and can be realized by other hardware.

The communication device H11 is an interface that establishes a communication path with another device and executes data transmission/reception, such as a network interface or a wireless interface.

The input device H12 is a device that receives input from a user or the like, such as a mouse or a keyboard. The display device H13 is a display or the like that displays various information. A touch panel display or the like functions as an input device H12 and a display device H13.

The storage unit H14 is a storage device that stores data and various programs for executing various functions of the user terminal 10, the settlement server 20, and the portal server 30. FIG. Examples of the storage unit H14 include ROM, RAM, hard disk, and the like.

The processor H15 controls each process in the user terminal 10, the settlement server 20, and the portal server 30 using programs and data stored in the storage unit H14. Examples of the processor H15 include, for example, a CPU and an MPU. This processor H15 expands programs stored in ROM or the like into RAM and executes various processes for each process.

Processor H15 is not limited to performing software processing for all the processing that it itself executes. For example, the processor H15 may include a dedicated hardware circuit (for example, an application specific integrated circuit: ASIC) that performs hardware processing for at least part of the processing performed by the processor H15. That is, the processor H15 can be configured as follows.

(1) one or more processors that operate according to a computer program (software); (2) one or more dedicated hardware circuits that perform at least some of the various types of processing; or (3) a combination thereof. circuit containing
A processor includes a CPU and memory, such as RAM and ROM, which 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.

(System configuration)
Next, functions of the user terminal 10, the settlement server 20, and the portal server 30 will be described with reference to FIG.

The user terminal 10 is a computer terminal (for example, mobile terminal) used by a user. This user terminal 10 includes an application execution unit 11 and executes an application stored in a storage unit. In this embodiment, the portal application 111 and the payment application 112 are executed.

The portal application 111 is an application program that provides a user interface at the entrance of various services (portal services) in the user terminal 10 . In this embodiment, payment service is included in various services provided by the portal service.

The payment application 112 is an application program that functions as a transaction application and manages user accounts. In this embodiment, the user can perform remittance and settlement by using the account balance.
The portal application 111 and the payment application 112 each hold information (portal user ID, payment user ID) for specifying the user of the user terminal 10 .

The payment server 20 is a computer system of a service provider that functions as a transaction server and provides payment services via the payment application 112 . The payment server 20 manages the account balance held by the user of the payment application 112 . The users include member stores that provide products and services through payment using payment services. The payment server 20 includes a control unit 21 , a payment user information storage unit 22 , a member store information storage unit 23 and a transaction information storage unit 24 .

The control unit 21 functions as an access management unit 211 and a transaction management unit 212 by executing an account management program.
The access management unit 211 executes processing for authenticating an access source. Furthermore, the access management unit 211 has an API (application programming interface) for providing various information to the user. This access management unit 211 holds a server ID and authentication information for authenticating the portal server 30 .
The transaction management unit 212 executes processing for managing transactions (for example, settlement) using the user's account.

As shown in FIG. 3( a ), the settlement user information storage unit 22 records a settlement user management record 220 . This settlement user management record 220 is recorded when a user opens an account, and is updated when settlement, remittance, or charging is performed using the account. Settlement user management records 220 record data relating to settlement user IDs, user information, authentication information, user accounts, and balances.

In the payment user ID data area, data relating to an identifier for specifying the account of the user of the payment application 112 is recorded.
In the user information data area, data (name, address, contact information, etc.) relating to users who have accounts are recorded.

Data for authenticating the user is recorded in the authentication information data area.
In the user account data area, data relating to identifiers (financial institution code, head/branch code, account type, account number, etc.) for specifying the financial institution account held by the user are recorded. This user account is used, for example, to charge the balance.

Data relating to the balance of this account is recorded in the balance data area.
Furthermore, in the payment user information storage unit 22, a transaction history record 221 is recorded in association with the payment user management record 220. FIG.

The transaction history record 221 is recorded when a transaction is made using the user's account. The transaction history record 221 records data relating to transaction ID, transaction date and time, transaction content, and amount.

Data relating to an identifier (transaction identification information) for specifying each transaction is recorded in the transaction ID data area.
Data relating to the date and time of the transaction is recorded in the transaction date and time data area.

In the transaction content data area, data regarding the type of transaction (settlement, remittance, etc.) and the remittance destination are recorded.
In the amount data area, data relating to the amount of transaction is recorded.

As shown in FIG. 3B, the member store management record 230 is recorded in the member store information storage unit 23 . This member store management record 230 is recorded when an account is opened by a member store and updated when payment is made. The member store management record 230 records member store IDs, member store information, authentication information, member store accounts, and data on sales.

In the member store ID data area, data relating to an identifier for specifying the account of the member store is recorded.
In the member store information data area, data (name, address, contact information, etc.) relating to the member store that owns the account is recorded.

Data for authenticating the member store is recorded in the authentication information data area.
In the member store account data area, data relating to identifiers (financial institution code, head/branch code, account type, account number, etc.) for specifying the financial institution account held by this member store are recorded. This merchant account is used, for example, to conduct remittance of sales.
In the sales data area, data relating to the sales amount of this member store is recorded.

Furthermore, the member store information storage unit 23 records a transaction history record 231 in association with the member store management record 230 .

The transaction history record 231 is recorded when a transaction is made using the member store's account. The transaction history record 231 records data relating to transaction ID, transaction date and time, transaction content, and amount.

Data relating to an identifier (transaction identification information) for specifying each transaction is recorded in the transaction ID data area.
Data relating to the date and time of the transaction is recorded in the transaction date and time data area.

In the transaction details data area, data relating to the type of transaction (settlement, etc.) and the source of remittance are recorded.
In the amount data area, data relating to the amount of transaction is recorded.

As shown in FIG. 3(c), the transaction information storage unit 24 stores a transaction management record 240 relating to the user's transaction. A transaction management record 240 is recorded when a transaction is made. The transaction management record 240 includes transaction ID, transaction date and time, remittance source ID, remittance destination ID, and data related to the amount.

In the transaction ID data area, data regarding an identifier for specifying each transaction is recorded.
In the transaction date and time data area, data relating to the date and time of acceptance of this transaction are recorded.

In the remittance source ID data area, data relating to an identifier for specifying the remittance source account in this transaction is recorded.
In the remittee ID data area, data relating to an identifier for specifying the remittee's account in this transaction is recorded.
Data relating to the transaction amount is recorded in the amount data area.

The portal server 30 shown in FIG. 1 is a computer system of a service provider that provides portal services that provide various services to users via the portal application 111 . The portal server 30 manages user information using the portal application 111 . This portal server 30 includes a control unit 31 and a portal user information storage unit 32 .
The control unit 31 functions as a user management unit by executing a user management program.

As shown in FIG. 3D, a portal user management record 320 is recorded in the portal user information storage unit 32. FIG. This portal user management record 320 is recorded when user information is registered. The portal user management record 320 records data relating to the portal user ID, personal information, services used, and transaction history.

In the portal user ID data area, data relating to an identifier (user identification information) for identifying each user of the portal application 111 is recorded.
In the personal information data area, data relating to personal information such as the user's name, address and attributes are recorded.

In the used service data area, data relating to an identifier for identifying the service used by the user is recorded. The service to be used includes a payment service provided by the payment server 20. FIG. By using this used service identifier, it is possible to specify the access destination (settlement server 20) of the server that provides each service.
In the transaction history data area, data relating to an identifier (transaction ID) for specifying a transaction performed by the user is recorded in association with the date and time of acquisition.

(Service management method)
Next, the service management method will be described with reference to FIGS. 4 and 5. FIG. Here, processing at settlement (FIG. 4) and processing at inquiry (FIG. 5) will be described. The settlement process is executed when a transaction (for example, settlement) is performed using the settlement application 112 designated by the portal application 111 . Inquiry processing is executed when a transaction history is acquired using the portal application 111 .

(Processing at the time of payment)
First, with reference to FIG. 4, the settlement processing will be described.
Here, it is assumed that the user uses the user terminal 10 and makes a transaction using the account balance of the settlement means.

The application executing unit 11 of the user terminal 10 executes portal application activation processing (step S101). Specifically, the user instructs the activation of the portal application 111 . In this case, application execution unit 11 activates portal application 111 . The portal application 111 then outputs the portal screen to the display device H13.

Next, the application executing unit 11 of the user terminal 10 executes a payment means selection process (step S102). Specifically, the portal application 111 outputs a payment method selection screen to the display device H13 in accordance with the user's instruction on the portal screen. Then, the user selects a desired payment method using the payment method selection screen. In this case, the portal application 111 instructs activation of the payment application 112 of the selected payment means. This activation instruction includes portal identification information and information on the portal user ID. The portal service used by the user can be identified by this portal identification information.

Next, the application executing unit 11 of the user terminal 10 executes settlement application activation processing (step S103). Specifically, the application execution unit 11 activates the payment application 112 by deep linking (application link function).

Next, the application execution unit 11 of the user terminal 10 executes payment input processing (step S104). Specifically, the payment application 112 outputs a payment setting screen to the display device H13. Then, on the payment setting screen, the camera of the user terminal 10 is activated to read the two-dimensional code image placed at the store. This two-dimensional code image contains information about the member store's member store ID. Then, the user inputs the payment amount (transaction amount) on this settlement setting screen.

Next, the application execution unit 11 of the user terminal 10 executes payment instruction processing (step S105). Specifically, when a payment instruction is input, the payment application 112 transmits a payment request (transaction instruction) to the payment server 20 . This payment request includes portal identification information, portal user ID, payment user ID of the remittance source, member store ID of the member store, and information on the amount. Note that the payment user ID of the remittance source is the payment user ID held by the payment application 112 .

Next, the control unit 21 of the payment server 20 executes payment processing (step S106). Specifically, the transaction management unit 212 of the control unit 21 assigns a transaction ID to the acquired settlement request. Then, the transaction management unit 212 creates a transaction management record 240 that records the transaction ID, transaction date and time (current date and time), remittance source ID (settlement user ID of the user), remittance destination ID (member store ID of the member store), and the amount. It is generated and recorded in the transaction information storage unit 24 .

Then, the transaction management unit 212 subtracts the transaction amount from the balance of the remittance source account and adds the transaction amount to the balance of the remittance destination account. Next, the transaction management unit 212 generates a transaction history record 221 that records the transaction ID, transaction date and time (current date and time), transaction content (member store ID of the member store), and amount, and records it in the settlement user information storage unit 22 . do.

Next, the control unit 21 of the settlement server 20 executes transaction ID provision processing (step S107). Specifically, the transaction management unit 212 of the control unit 21 transmits the transaction information to the portal server 30 specified by the portal identification information. This transaction information includes information on the portal user ID and transaction ID.

Next, the control unit 31 of the portal server 30 executes transaction ID recording processing (step S108). Specifically, the control unit 31 records the transaction ID in association with the acquisition date and time (current date and time) in the transaction history data area of the portal user management record 320 containing the acquired portal user ID.

(Inquiry processing)
Next, referring to FIG. 5, the inquiry process will be described.
Here, the application execution unit 11 of the user terminal 10 executes portal application activation processing (step S201). Specifically, when the user checks the transaction history, the portal application 111 is activated. In this case, the portal application 111 outputs the portal screen to the display device H13.

Next, the application execution unit 11 of the user terminal 10 executes a payment history inquiry process (step S202). Specifically, according to the user's instruction, the portal screen instructs the display of the settlement history. In this case, the portal application 111 transmits a transaction history inquiry request to the portal server 30 . This query request includes information about the portal user ID.

Next, the control unit 31 of the portal server 30 executes transaction ID identification processing (step S203). Specifically, the control unit 31 acquires the portal user management record 320 in which the acquired portal user ID is recorded from the portal user information storage unit 32 . Then, among the transaction IDs recorded in the portal user management record 320, the transaction ID whose acquisition date and time is the most recent predetermined period is acquired.

Next, the control unit 31 of the portal server 30 executes API cooperation processing (step S204). Specifically, the control unit 31 uses the API of the payment server 20 . Therefore, the control unit 31 transmits an authentication request including the server ID of the portal server 30 and authentication information to the API of the settlement server 20 . In this case, the access management section 211 of the control section 21 of the settlement server 20 authenticates the server ID. If the server ID can be authenticated, the control unit 21 issues an access token to the portal server 30 . Next, the control section 31 transmits a transaction information request. This transaction information request includes the transaction ID and access token specified in the portal user management record 320 .

Next, the control unit 21 of the settlement server 20 executes processing for providing the settlement history of the transaction ID (step S205). Specifically, the access management unit 211 of the control unit 21 uses the access token to authenticate the portal server 30 of the API cooperation source. When the authentication is completed, the access management section 211 acquires the transaction management record 240 in which the transaction ID is recorded from the transaction information storage section 24 . The access management unit 211 then provides the transaction history to the portal server 30 .

Next, the control unit 31 of the portal server 30 executes processing for transmitting the settlement history of the transaction ID (step S206). Specifically, the control unit 31 provides the acquired transaction history to the user terminal 10 .

Next, the application executing unit 11 of the user terminal 10 executes display processing (step S207). Specifically, the portal application 111 displays the acquired transaction history on the portal screen output to the display device H13.

As described above, according to the present embodiment, the following effects can be obtained.
(1) In the present embodiment, the application execution unit 11 of the user terminal 10 executes payment instruction processing (step S105). Specifically, the payment application 112 transmits a payment request to the payment server 20 when a payment instruction is input. This payment request includes portal identification information, portal user ID, payment user ID of the remittance source, member store ID of the member store, and information on the amount. Thereby, the settlement server 20 can grasp the portal server 30 used.

(2) In the present embodiment, the control unit 21 of the settlement server 20 executes transaction ID provision processing (step S107). As a result, the portal server 30 can grasp the transaction ID of the transaction made by the user.

(3) In the present embodiment, the control unit 31 of the portal server 30 executes transaction ID identification processing (step S203) and API cooperation processing (step S204). The control unit 21 of the settlement server 20 executes processing for providing the settlement history of the transaction ID (step S205). As a result, the transaction information of the payment application 112 can be output within the portal application 111 .

This embodiment can be implemented with the following modifications. This embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
- In the above-described embodiment, the control unit 21 of the settlement server 20 executes the process of providing the transaction ID (step S107). Specifically, the transaction management unit 212 of the control unit 21 transmits the transaction information to the portal server 30 specified by the portal identification information. As long as the portal server 30 can hold a transaction ID for each user, the method of providing the transaction ID is not limited.

Another settlement process will be described with reference to FIG.
The application execution unit 11 of the user terminal 10 executes the portal application activation process (step S301) and the payment method selection process (step S302) in the same manner as in steps S101 and S102.

Next, the application execution unit 11 of the user terminal 10 executes payment application activation processing (step S303), payment input processing (step S304), and payment instruction processing (step S305), as in steps S103 to S105.

Next, the control unit 21 of the payment server 20 executes payment processing (step S306), as in step S106.
Next, the control unit 21 of the settlement server 20 executes transaction ID provision processing (step S307). Specifically, the transaction management unit 212 of the control unit 21 transmits transaction information to the user terminal 10 . This transaction information includes portal identification information and transaction ID information.

Next, the application executing unit 11 of the user terminal 10 executes a process of providing the transaction ID to the portal application (step S308). Specifically, the payment application 112 provides the transaction ID to the portal application 111 corresponding to the portal identification information by deep linking.

Next, the application executing unit 11 of the user terminal 10 executes transaction ID upload processing (step S309). Specifically, portal application 111 transmits transaction information to portal server 30 . This transaction information includes the portal user ID held by the portal application 111 and the transaction ID obtained from the settlement application 112 .

Next, the control unit 31 of the portal server 30 executes transaction ID recording processing (step S310), as in step S108.
Thereby, the settlement server 20 can provide the transaction ID to the portal server 30 via the user terminal 10 .

- In the above embodiment, the application execution unit 11 of the user terminal 10 executes the payment input process (step S104). Here, a two-dimensional code image placed in the store is read. The settlement method is not limited to reading the two-dimensional code image placed in the store. For example, at the time of transaction, the store terminal may access the payment server 20 and acquire a two-dimensional code image including the transaction ID issued by the payment server 20 . Also, at the time of transaction, the two-dimensional code image displayed on the display device H13 of the user terminal 10 may be read by the shop terminal. Also in this case, the user terminal 10 may access the payment server 20 and obtain a two-dimensional code image including the transaction ID issued by the payment server 20 at the time of transaction.

- In the above-described embodiment, in the settlement process, the control unit 21 of the settlement server 20 executes the settlement process (step S106). Then, the control unit 31 of the portal server 30 executes transaction ID recording processing (step S108). As long as the transaction ID can be recorded, it can be applied to transaction processing using the settlement server 20 via the portal server 30, without being limited to the time of settlement. For example, the issued transaction ID is recorded in transactions such as remittance, deposit/withdrawal, charge, point award, cooperation with other services in the portal server 30, etc. using the settlement server 20 via the portal server 30. .

In addition, when the portal application 111 is installed in the recipient's user terminal 10 at the time of remittance, the transaction ID may be recorded in the recipient's portal user management record 320 in the portal user information storage unit 32 as well. good. In this case, the portal user ID of the remitter and the portal user ID of the recipient are included in the activation instruction for the payment method selection process (step S102).

10 User terminal 11 Application execution unit 111 Portal application 112 Settlement application 20 Settlement server 21 Control unit 211 Access management unit 212 Transaction management unit 22 Settlement user information storage unit , 24... transaction history storage unit, 30... portal server, 31... control unit, 32... portal user information storage unit.

Claims (5)

A service management system comprising a portal server connected via a portal application of a user terminal and a transaction server connected via a transaction application,
the transaction server
The portal application of the user terminal acquires a transaction instruction from a transaction application selected from among the transaction applications stored in the user terminal , and according to the transaction instruction , creates an account of the settlement user ID of the transaction application. to process transactions using
transmitting transaction identification information for the transaction instruction to the portal server together with a portal user ID associated with the settlement user ID ;
the portal server,
record the transaction identification information acquired from the transaction server in association with the portal user ID ;
when obtaining a transaction history inquiry request for the portal user ID from the portal application, obtaining a transaction history for the transaction identification information from the transaction server;
A service management system, wherein the transaction history is output in the portal application. A service management system comprising a portal server connected via a portal application of a user terminal and a transaction server connected via a transaction application,
the transaction server
The portal application of the user terminal acquires a transaction instruction from a transaction application selected from among the transaction applications stored in the user terminal, and according to the transaction instruction, creates an account of the settlement user ID of the transaction application. to process transactions using
transmitting transaction identification information about the transaction instruction to the portal server together with a portal user ID of the portal application via the transaction application and the portal application stored in the user terminal;
the portal server,
record the transaction identification information acquired from the transaction server in association with the portal user ID;
when obtaining a transaction history inquiry request for the portal user ID from the portal application, obtaining a transaction history for the transaction identification information from the transaction server;
A service management system, wherein the transaction history is output in the portal application. 3. The transaction server according to claim 1, wherein said transaction server acquires said transaction instruction including portal identification information from a transaction application activated by an application link function in said portal application in said user terminal. service management system. A method of managing a service using a service management system comprising a portal server connected via a portal application of a user terminal and a transaction server connected via a transaction application, comprising:
the transaction server
The portal application of the user terminal acquires a transaction instruction from a transaction application selected from among the transaction applications stored in the user terminal , and according to the transaction instruction , creates an account of the settlement user ID of the transaction application. to process transactions using
transmitting transaction identification information for the transaction instruction to the portal server together with a portal user ID associated with the settlement user ID ;
the portal server,
record the transaction identification information obtained from the transaction server in association with the portal user ID ;
when obtaining a transaction history inquiry request for the portal user ID from the portal application, obtaining a transaction history for the transaction identification information from the transaction server;
A service management method, wherein the transaction history is output in the portal application. A method of managing a service using a service management system comprising a portal server connected via a portal application of a user terminal and a transaction server connected via a transaction application, comprising:
the transaction server
The portal application of the user terminal acquires a transaction instruction from a transaction application selected from among the transaction applications stored in the user terminal, and according to the transaction instruction, creates an account of the settlement user ID of the transaction application. to process transactions using
transmitting transaction identification information about the transaction instruction to the portal server together with a portal user ID of the portal application via the transaction application and the portal application stored in the user terminal;
the portal server,
record the transaction identification information acquired from the transaction server in association with the portal user ID;
when obtaining a transaction history inquiry request for the portal user ID from the portal application, obtaining a transaction history for the transaction identification information from the transaction server;
A service management method, wherein the transaction history is output in the portal application.

Images