JP6823676B2 - Information processing methods, information processing devices, and computer programs - Google Patents

Description

The present invention relates to an information processing method, an information processing device, and a computer program relating to the settlement of charges for services or goods.

Electronic money using a non-contact IC chip that communicates identification information by short-range wireless communication and enables payment of service or product charges has become widespread. In addition, a payment service that completes payment with a user's bank account or credit card by simply taking a picture of a two-dimensional barcode with a camera is also widespread (Patent Document 1 and the like). Cashless society is progressing due to such electronic money and payment services.

Services or products are not only used in the personal activities of the user, but may also be used in the business activities of the organization to which the user belongs. In the latter case, the service or product is used by the organization or business partner as a necessary expense. Payment is settled. In the settlement of expenses, it is necessary to record items and amounts, but the information registration process is very complicated. An accounting system has been proposed that automatically classifies and registers expense items based on payment records in credit cards or bank accounts. (Patent Document 2)

JP-A-2007-328549 JP-A-2018-116566

As mentioned above, cashless payment still presupposes that the payer of the cost is the individual user who enjoys the service or product. Even in view of various accounting systems such as Patent Document 2, it is normal for the user to pay the fee once and then settle the fee based on the user's application by the company to which the user belongs or the business partner company. It is not easy to reduce the complexity of the settlement process.

It is expected that the advance payment of users will be reduced as much as possible and the complexity of the settlement process will be reduced. Convenience is improved by enabling cashless payment that distinguishes between the use of the user's personal activities and the use of the user's business activities in the same system.

An object of the present invention is to provide an information processing method, an information processing device, and a computer program that improve the convenience of both a user who directly enjoys a service or a product and a payer of a fee.

The information processing method of the embodiment of the present disclosure includes user identification information that identifies a user who uses a service or a product, and provider identification information that identifies a provider who provides the service or product. When the amount of the service or product is determined by acquiring the provider information, the confirmation from the user is accepted for the amount, and after the confirmation is received, the above is associated with the user provider information. The expense registration process of the amount of the service or product to the payer of the fee related to the service or product, and the settlement process to the provider of the service or product are executed.

The information processing device of the embodiment of the present disclosure is provided by a user including user identification information for identifying a user who uses a service or a product and provider identification information for identifying a provider who provides the service or a product. An acquisition unit for acquiring personal information, a confirmation unit for receiving confirmation from the user when the amount of the service or product is determined, and the user after the confirmation is received by the confirmation unit. It includes a processing unit that executes expense registration processing of the amount of the service or product for the payer of the fee related to the service or product in association with the provider information, and payment processing for the provider of the service or product.

The computer program of one embodiment of the present disclosure includes a user identification information that identifies a user who uses a service or a product, and a provider identification information that identifies a provider who provides the service or the product. When the information is acquired and the amount of the service or product is determined, the confirmation from the user is accepted for the amount, and after the confirmation is received, the service or product is associated with the user provider information. The computer is made to execute the process of registering the cost of the amount of the service or the product for the payer of the fee and the process of displaying the information regarding the payment process for the provider of the service or the product on the display unit.

The computer program of one embodiment of the present disclosure includes a user identification information that identifies a user who uses a service or a product, and a provider identification information that identifies a provider who provides the service or the product. When the information is acquired and the amount of the service or product is decided, the confirmation from the user is accepted about the amount, and the payment of the fee related to the service or product is treated as an expense, or the user's personal burden is paid. Let the computer execute the process of accepting the selection of.

According to the present disclosure, it is possible to improve the convenience of both the user and the payer of the service or product.

It is a figure which shows the outline of the payment method using an information information system. It is a block diagram which shows the structure of the user terminal apparatus included in an information processing system. It is a block diagram which shows the structure of the information processing apparatus included in an information processing system. It is a figure which shows the content example of the information stored in a user DB. It is a figure which shows the content example of the information stored in the provider DB. It is a figure which shows the content example of the information stored in the payer DB. It is a figure which shows the content example of the information stored in the condition DB. It is a figure which shows the content example of the information stored in the form DB. It is a figure which shows the content example of the information stored in the usage record DB. It is a figure which shows the content example of the information stored in a ticket DB. It is a block diagram which shows the structure of the provider terminal apparatus included in an information processing system. It is a block diagram which shows the structure of the payer terminal apparatus included in the information processing system. It is a sequence diagram which shows an example of the use sequence. It is a sequence diagram which shows an example of the use sequence. It is a figure which shows the screen example which is displayed on the display part of a user terminal apparatus. It is a figure which shows the screen example which is displayed on the display part of a user terminal apparatus. It is a figure which shows the screen example which is displayed on the display part of a user terminal apparatus. It is a figure which shows the screen example which is displayed on the display part of a user terminal apparatus. It is a flowchart which shows an example of the processing procedure based on the usage record DB. It is a sequence diagram which shows an example of the processing procedure of ticket issuance based on a usage record DB. It is a figure which shows the example of the ticket list screen. It is a sequence diagram which shows an example of the utilization sequence in Embodiment 2. It is a sequence diagram which shows an example of the utilization sequence in Embodiment 2. It is a figure which shows the screen example which is displayed on the display part of the user terminal apparatus in Embodiment 2. FIG. It is a figure which shows the screen example which is displayed on the display part of the user terminal apparatus in Embodiment 2. FIG. It is a figure which shows the screen example which is displayed on the display part of the user terminal apparatus in Embodiment 2. FIG. It is a sequence diagram which shows an example of the utilization sequence in Embodiment 3. It is a sequence diagram which shows an example of the utilization sequence in Embodiment 3. It is a sequence diagram which shows an example of the utilization sequence in Embodiment 3. It is a figure which shows the example of the ticket list screen in Embodiment 3. FIG.

The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof. In the following embodiment, an information processing system that realizes payment by applying the information processing method of the present disclosure will be described.

(Embodiment 1)
FIG. 1 is a diagram showing an outline of a payment method using the information processing system 100. The information processing system 100 of the first embodiment includes a user terminal device 1 of a user, an information processing device 2, a provider terminal device 3 used by a service or product provider, and a payer terminal device 4 used by a payer. And include. The user terminal device 1, the provider terminal device 3, and the payer terminal device 4 can each communicate with the information processing device 2 via the network N to transmit and receive information.

The user terminal device 1 is a user's smartphone, the provider terminal device 3 is a tablet terminal owned by a service provider, and the payer terminal device 4 is a personal computer or server computer managed by a business operator who is a payer. It is a general-purpose computer. The provider terminal device 3 may be in the form of a general-purpose computer as well as a tablet terminal, or may include a general-purpose computer capable of communicating with each of the tablet terminal groups if the provider is organized. The information processing device 2 is a server computer that executes processing related to the payment service.

The information processing device 2 is a server computer that transmits / receives information by communicating with at least one of a user terminal device 1, a provider terminal device 3, and a payer terminal device 4. The information processing device 2 functions as a payment platform that issues a digital form DF related to services or products enjoyed by the user, adds various information to the digital form DF, and realizes a payment service or expense registration service based on the digital form DF. To do. With the payment platform, it is possible to realize not only a payment service based on the digital form DF but also a ticket distribution service. The information processing device 2 is communicated and connected to a payment system 200 that executes deposits and withdrawals between bank accounts corresponding to service or product providers, payers, and users via a dedicated line NN.

The network N includes a public communication network N1 which is a so-called Internet, a carrier network N2 which realizes wireless communication according to a predetermined mobile communication standard, and a dedicated line N3. The public communication network N1 includes an access point AP. The carrier network N2 includes a base station BS. Communication connection is possible between the user terminal device 1 and the information processing device 2, and between the provider terminal device 3 and the information processing device 2 via the public communication network N1 or the carrier network N2. The payer terminal device 4 can be connected to the information processing device 2 via a dedicated line N3 or a public communication network N1.

In the first embodiment, the service provider is a taxi operator. The user uses a taxi for a business trip, that is, for the business activity of the company to which the user belongs. The payer is the accounting department of the company to which the user belongs. In the first embodiment, the user terminal device 1 is a smartphone personally owned by the user. The provider terminal device 3 is a tablet terminal possessed by a taxi driver. The provider terminal device 3 may be a dedicated device linked to the taximeter.

The user who possesses the user terminal device 1 acquires a provider ID (identification information) that identifies the service provider when boarding a taxi or at the time of payment, and transmits it to the information processing device 2 in association with the user ID. .. The user ID or provider ID corresponds to the code related to the service. The provider ID is included in the two-dimensional barcode presented inside the taxi. It is preferable that the two-dimensional barcode includes a provider ID for identifying the taxi operator, a vehicle ID, and a driver ID so that the use of the taxi can be identified once. The two-dimensional barcode may be printed out on a paper medium, sticker paper, or the like, or may be output on the display unit of the provider terminal device 3.

The information processing device 2 issues a digital form DF for the user identified by the transmitted user ID to pay the cost related to the taxi transportation provided by the provider identified by the provider ID. When the taxi fare is fixed, the information processing device 2 acquires the amount from the user terminal device 1 or the provider terminal device 3. The user terminal device 1 may read the amount output on the receipt printed out from the taximeter and send it to the information processing device 2, or the provider terminal device 3 may send the amount to the information processing device 2. Good.

The information processing device 2 adds the acquired amount to the issued digital form DF, notifies the user terminal device 1, and accepts confirmation of the amount by the user. When the user confirms the amount notified to the user terminal device 1, the information processing device 2 accepts the confirmation and executes the payment by the payment method agreed between the service provider and the payer. The information processing device 2 can transmit payment information to the payment system 200 and execute payment. The information processing device 2 allocates an account item (for example, "transportation cost") based on a pre-registered expense processing rule, and transmits it to the payer terminal device 4.

As a result, the user can take a taxi for a business trip without using cash or a credit card owned by the user. The company to which the user belongs also does not need to settle the travel expenses in advance, and the expenses are automatically registered, so there is no need to settle the expenses by applying from the user. The taxi company that is the service provider can also collect the fee from the payer.

It is also possible to link the payment platform with the user's personal payment method. The information processing device 2 can select whether to use a personal payment method or to record it as an expense by the company to which it belongs. After the fact, the information processing device 2 can allocate the payment or the like once recorded as an expense to a personal payment method as if it was a personal use. On the contrary, the information processing device 2 can transfer the cost equivalent to the expense processing from the payer's account to the user's individual account after the approval for the expense once paid by the personal payment method.

The information processing system 100 for realizing the payment service and the expense registration service will be described in detail. FIG. 2 is a block diagram showing a configuration of a user terminal device 1 included in the information processing system 100. As described above, the user terminal device 1 uses a computer having a communication function such as a smartphone. The user terminal device 1 includes a control unit 10, a storage unit 11, a communication unit 12, a display unit 13, an operation unit 14, and a reading unit 15.

The control unit 10 is a processor using a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), and uses a built-in memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory) to control each component unit. Control and execute processing. The control unit 10 may be configured as one piece of hardware (SoC: System On a Chip) in which a processor, a memory, a storage unit 11, and a communication unit 12 are integrated. The control unit 10 communicates with the information processing device 2 based on the wallet application program (hereinafter referred to as a wallet application) 1P stored in the storage unit 11 to realize the use of the payment service.

The storage unit 11 uses a flash memory to store programs and data referred to by the control unit 10 including the wallet application 1P. A user ID that identifies a user of the payment service is stored in the storage unit 11. The control unit 10 causes the display unit 13 to display an operation screen based on the information transmitted from the information processing device 2 based on the wallet application 1P.

The communication unit 12 is a wireless communication module that realizes wireless communication with the information processing device 2 via the public communication network N1 or the carrier network N2. The communication unit 12 uses, for example, a wireless communication device compatible with Wi-Fi or a carrier communication module.

The display unit 13 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 14 is an interface that accepts user operations, and uses physical buttons, a touch panel device with a built-in display, a speaker, a microphone, and the like. The operation unit 14 may accept an operation on the screen displayed on the display unit 13 by a physical button or a touch panel, recognizes the operation content from the input voice by the microphone, and interacts with the voice output by the speaker. The operation may be accepted in the form.

The reading unit 15 is a reader that reads a code such as a provider ID. The reading unit 15 is at least one of a barcode reader, a camera, and a wireless tag reader. The reading unit 15 may include any of them and selectively use any of them depending on the mode of presenting the code to read the code. The reading unit 15 notifies the control unit 10 of the read code.

FIG. 3 is a block diagram showing a configuration of an information processing device 2 included in the information processing system 100. As described above, the information processing apparatus 2 uses a server computer. In the first embodiment, the information processing device 2 will be described as one server computer, but the functions or processes may be distributed among a plurality of server computers, or the information processing device 2 may be virtually generated by one large computer. It may be one of a plurality of server computers (instances).

The information processing device 2 includes a control unit 20, a storage unit 21, a first communication unit 22, a second communication unit 23, and an input / output unit 24.

The control unit 20 is a processor using a CPU or GPU, and controls each component unit using a built-in memory to execute processing. The control unit 20 executes information processing based on the information processing program 2P stored in the storage unit 21.

The storage unit 21 uses a hard disk or an SSD (Solid State Drive). The storage unit 21 stores the information processing program 2P, and also stores other programs and data referred to by the control unit 20.

The first communication unit 22 realizes communication in the public communication network N1 or the carrier network N2. The control unit 20 can transmit and receive information between the user terminal device 1 and the provider terminal device 3 via the public communication network N1 or the carrier network N2 by the first communication unit 22.

The second communication unit 23 realizes communication on the dedicated line N3. The control unit 20 can send and receive information to and from the payer terminal device 4 via the dedicated line N3 by the second communication unit 23.

The input / output unit 24 is a connection interface with a service DB (Data Base: database) 201 that stores various information related to the payment platform. The service DB 201 may be built in the storage unit 21.

The service DB 201 includes a user DB 202, a provider DB 203, a payer DB 204, a condition DB 205, a form DB 206, a usage record DB 208, and a ticket DB 209.

FIG. 4 is a diagram showing an example of the content of the information stored in the user DB 202. The user DB 202 stores attributes such as a user's name in association with the user's user ID. It is preferable that the attributes include contact information such as a user's telephone number and e-mail address, a company name to which the user belongs, an employee ID, and the like. The user DB 202 stores a payer ID that identifies a default payer when the expense is recorded by the company to which the user belongs in association with the user ID. The user DB 202 stores information that identifies a bank account in the user's payment system 200, or payment information that is information on the user's personal credit card. The user DB 202 stores rank information based on the frequency of use of the user's service or the set importance in association with the user ID. The rank information can be set by the information processing device 2.

FIG. 5 is a diagram showing an example of the content of the information stored in the provider DB 203. The provider DB 203 stores attributes such as the name of the provider, the type of the provider, and the like in association with the provider ID of the provider of the service or product. The provider ID may be identified by a direct service provider, for example, a taxi driver, a restaurant store, a restaurant staff ID, etc. when the provider is organized, or for each business operator. It may be identified. The provider DB 203 stores information that identifies a bank account in the provider's payment system 200.

FIG. 6 is a diagram showing an example of the contents of the information stored in the payer DB 204. The payer DB 204 stores attributes such as the name of the company that is the payer in association with the payer ID of the payer. The payer DB 204 stores information that identifies a bank account in the payer's payment system 200.

FIG. 7 is a diagram showing an example of the content of the information stored in the condition DB 205. The condition DB 205 stores the charge upper limit, the number of times upper limit, the due date, the place, or the discount rate in association with the rank information. The condition DB 205 may store usage conditions including a charge upper limit, a number of times upper limit, a due date, a place, or a discount rate set for each user in association with the user ID. The condition DB 205 may store usage conditions such as a charge upper limit, a number of times upper limit, a description, or a discount rate unique to the combination based on an agreement between the payer and the provider. Each of these usage conditions may be stored with a condition ID.

The payer ID is issued with the authority of the administrator of the payment platform in response to the application from the payer company. User IDs are issued for the number of users included in the application. The information stored in the user DB 202, the payer DB 204, and the condition DB 205 is registered by the payer in association with the issued payer ID or user ID. It may be registered remotely from the payer terminal device 4. The information stored in the provider DB 203 is also associated with the provider ID issued by the administrator in response to the membership application from the service or product provider, and the attributes, vehicle ID, driver ID, etc. are determined by the provider. May be registered. The condition DB 205 may be registered at the time of application and rewritten after the fact, or may be rewritten remotely from the payer terminal device 4.

FIG. 8 is a diagram showing an example of the contents of the information stored in the form DB 206. The form DB 206 stores the digital form DF. Digital form DF is a form ID, issuance date and time, use start date and time, use end date and time, purpose of use, name of service or product used, detailed content, amount of money, user ID of user, provider who provides service or product. Includes provider ID, payer's payer ID, and terms of use. The digital form DF includes the type of personal burden or expense processing. When the cost is shared between the payer and the user himself / herself for one use, the user ID or the payer ID of another payer is included as the second payer. Is the digital form DF a one-time type issued by specifying the provider ID when using the service, or a wallet type issued by specifying the user ID and amount first and applying? May include the type of.

FIG. 9 is a diagram showing an example of the contents of the information stored in the usage record DB 208. The usage record DB 208 stores the usage record of the digital form DF that has been settled in association with the user ID. The payment ID numbered by the payment system 200 may be associated and stored. The usage record DB 208 may store a part or all of the contents of the digital form DF in association with the user ID and the form ID.

FIG. 10 is a diagram showing an example of the contents of the information stored in the ticket DB 209. The ticket DB 209 stores a digital ticket issued to the user by an application from the provider based on the usage record stored in the usage record DB 208. The digital ticket is a digital form DF in which only the user ID, the provider ID, and the usage conditions are specified, and the form ID is numbered. The ticket DB 209 stores not only the tickets before use but also the used tickets. The digital ticket may be stored in the form DB 206 when the use is started.

FIG. 11 is a block diagram showing a configuration of a provider terminal device 3 included in the information processing system 100. As described above, the provider terminal device 3 uses a computer having a communication function such as a tablet terminal. The provider terminal device 3 includes a control unit 30, a storage unit 31, a communication unit 32, a display unit 33, an operation unit 34, and a reading unit 35.

The control unit 30 is a processor that uses a CPU or GPU, and uses a built-in memory such as a ROM or RAM to control each component and execute processing. The control unit 30 transmits information on charges related to the service provided to the information processing device 2 based on the provider application program 3P stored in the storage unit 31.

The storage unit 31 uses a flash memory to store programs and data referenced by the control unit 30 including the provider application program 3P. The provider ID is stored in the storage unit 31. The storage unit 31 may store the vehicle number for identifying the vehicle and the driver ID for identifying the driver. The application program 3P for the provider may realize a function of supporting the transportation record of the passenger for each driver belonging to the taxi operator in the first embodiment.

The communication unit 32 is a wireless communication module that realizes wireless communication with the information processing device 2 via the public communication network N1 or the carrier network N2. The communication unit 32 uses, for example, a wireless communication device compatible with Wi-Fi or a carrier communication module.

The display unit 33 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 34 is an interface that receives the operation of the service provider and the taxi driver in the first embodiment, and uses physical buttons, a touch panel device with a built-in display, a speaker, a microphone, and the like. The operation unit 34 may accept an operation on the screen displayed on the display unit 33 by a physical button or a touch panel, recognizes the operation content from the input voice by the microphone, and interacts with the voice output by the speaker. The operation may be accepted in the form.

The reading unit 35 is a reader that reads information from other devices. The reading unit 35 may be an interface connected to the taximeter. The reading unit 35 may be a barcode reader or a camera. The reading unit 35 reads the taxi driving record (date and time, boarding place, latter place) and the amount of money directly from the taximeter. The reading unit 35 may read the operation record and the amount of money from the paper discharged from the output device that prints and outputs a two-dimensional bar code indicating a predetermined amount of money in conjunction with the taximeter. The charge may be input using the operation unit 34.

Further, the reading unit 35 may function as a reader for reading the user ID presented from the user terminal device 1 as described later. In this case, the reading unit 35 is a barcode reader, a camera, or a short-range wireless communication module, and acquires information including a user ID of a user who is a customer of a service or a product. The reading unit 35 notifies the control unit 30 of the read information.

The provider terminal device 3 is provided to a general-purpose tablet terminal if the service can be obtained from a taximeter if the service is a taxi business, a cash register terminal if the service is a restaurant, or a check-in check-out system if the service is an accommodation business. It is realized by installing the application program 3P for users.

FIG. 12 is a block diagram showing a configuration of a payer terminal device 4 included in the information processing system 100. As described above, the payer terminal device 4 is a personal computer or a server computer managed by the accounting department of the company that is the payer. The payer terminal device 4 includes a control unit 40, a storage unit 41, a communication unit 42, a display unit 43, and an operation unit 44.

The control unit 40 is a processor that uses a CPU or GPU, and uses a built-in memory such as a ROM or RAM to control each component and execute processing. The control unit 40 can communicate with the information processing device 2 and transmit / receive information to / from the information processing device 2 based on the payer application program 4P stored in the storage unit 41.

The storage unit 41 uses a hard disk or SSD. The storage unit 41 stores programs and data referred to by the control unit 40 including the payer application program 4P. The payer ID is stored in the storage unit 41. The storage unit 41 stores the payer DB 401 including the user information including the user ID and attributes of the user belonging to the payer's company. The payer DB 401 includes identification information of wallet information based on the digital form DF for the user to which the payer has applied for issuance. The payer DB 401 includes expense information for which payment has been completed.

The communication unit 42 is a network card that realizes a communication connection with the information processing device 2 via the dedicated line N3.

The display unit 43 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 44 is an interface that receives an operation of an operator in the accounting department of a company, and uses a keyboard and a pointing device. The operation unit 44 may use a speaker, a microphone, or the like to recognize the operation content from the input voice by the microphone and accept the operation in an interactive manner with the voice output by the speaker.

The specific processing contents in the information processing system 100 configured in this way will be described for each scene.

[Preparation for using payment platform]
As a usage preparation scene, the procedure for starting the use of the payment platform by each user, payer, and provider will be described. In the first usage preparation scene, the accounting department of the company installs the payer application program 4P distributed from the information processing device 2 or the distribution server (not shown) on the personal computer. By installing the payer application program 4P, the personal computer, which is a general-purpose computer, functions as the payer terminal device 4 of the information processing system 100. Based on the payer application program 4P, the payer terminal device 4 receives registration of attributes such as a payer ID and a name from an operator in the accounting department, and transmits the received payer ID and attribute information to the information processing device 2. To do. The payer ID may be issued by the administrator of the payment platform that manages the information processing device 2 by prior application. The payer terminal device 4 receives the information of the settlement bank account used for payment of the fee to the provider of the service or the product, and transmits the information to the information processing device 2. As a result, as shown in FIG. 6, the payer information is stored in the payer DB 204 in association with the payer ID. When the payer terminal device 4 requests the information processing device 2 to issue user IDs for the number of users belonging to the company that is the payer based on the operation of the operator, and receives the issued user IDs. Good.

In the information processing system 100 of the first embodiment, the user installs the wallet application 1P distributed from the information processing device 2 or a distribution server (not shown) on the smartphone. By installing the wallet application 1P, the smartphone, which is a general-purpose computer, functions as the user terminal device 1 of the information processing system 100. Based on the wallet application 1P, the user terminal device 1 accepts registration of attributes including contact information such as a user ID and a name and an e-mail address from the user, and processes the received user ID and attribute information in the information processing device 2 Send to. The user ID is preferably issued in advance by the information processing apparatus 2 in response to an application from the company to which the payer belongs, as described above, in order to accurately associate the relationship with the default payer. The user terminal device 1 accepts registration of payment information for personal use of the wallet application 1P and transmits it to the information processing device 2. The payment information is the user's personal bank account or credit card information. As a result, as shown in FIG. 4, the user information is stored in the user DB 202 in association with the user ID.

With the user ID registered, the payer terminal device 4 may accept registration of rank information for the user ID and registration of usage conditions based on the operation of the operator of the accounting department.

In the usage preparation scene, the provider of the service or product installs the provider application program 3P distributed from the information processing device 2 or the distribution server (not shown) on the tablet terminal. By installing the provider application program 3P, the tablet terminal, which is a general-purpose computer, functions as the provider terminal device 3 of the information processing system 100. Based on the provider application program 3P, the provider terminal device 3 accepts the registration of attributes such as the provider ID and the name from the operator of the taxi operator, and transmits the received provider ID and attribute information to the information processing device 2. Send. Since the same taxi operator uses a plurality of provider terminal devices 3, registration may be accepted by a specific provider terminal device 3, such as a general-purpose computer used by an operator in the accounting department. The specific provider terminal device 3 receives the information of the bank account for deposit used for depositing the fee related to the service or the product, and transmits it to the information processing device 2. As a result, as shown in FIG. 5, the provider information is stored in the provider DB 203 in association with the provider ID. As part of the preparation for use, the provider terminal device 3 requests the information processing device 2 to issue a service code that identifies the service. The service code is, for example, an ID that identifies the provider for each event unit and may be the same as the provider ID, or is an ID that individually identifies the staff when the provider is composed of a plurality of staff. It may be present, or it may be an ID that identifies the location of staff. For example, in the case of a taxi, the location may be a vehicle number, and in the case of a restaurant, a store ID that identifies the store may be used. In this case, the specific provider terminal device 3 associates the number of taxi drivers to which the taxi driver belongs or the issuance of service codes for the number of taxis with the information for identifying each (driver ID or vehicle number). You may request the processing device 2. The provider terminal device 3 other than the specific provider terminal device 3 receives and uses the service code including at least the provider ID issued to the provider. When the service code is attached so as to identify the staff or the location, etc., instead of each provider, the provider terminal device 3 is issued for each driver ID or vehicle number in addition to the provider ID. Is received and used. Providers should present a two-dimensional bar-coded service code inside each taxi. The presentation method may be a method of printing and sticking on a sticker medium, or a method of being displayed on the display unit 33 of the provider terminal device 3.

[Payment service usage stage]
The actual usage sequence based on the above-mentioned usage preparation will be described with reference to the flowchart. 13 and 14 are sequence diagrams showing an example of the utilization sequence. When a user who intends to take a taxi activates the wallet application 1P on the user terminal device 1, the following processing is executed between the user terminal device 1, the information processing device 2, and the provider terminal device 3. ..

The control unit 10 of the user terminal device 1 outputs a screen prompting the user to read the service code to the display unit 13 (step S101), and acquires the service code (step S102).

When the service code is presented in the vehicle as a two-dimensional bar code, in step S102, the control unit 10 uses the reading unit 15 which is a camera to acquire the service code included in the two-dimensional bar code.

The screen displayed in step S101 may include a selection screen including a list of services to be used. In this case, the list is created by the information processing device 2 based on the information stored in the provider DB 203 of the service DB 201 by the information processing device 2. In step S102, for example, when the name of the taxi operator of the taxi to be used is selected from the list, the control unit 10 acquires a service code including the provider ID associated with the selected name.

The screen displayed in step S101 may include a two-dimensional barcode including a user ID, a one-dimensional barcode, or character information. In this case, the reading unit 35 of the provider terminal device 3 reads this, the provider ID and the user ID are transmitted from the provider terminal device 3 to the information processing device 2, and the corresponding service code is the user terminal device 1. Is transmitted to, and the control unit 10 of the user terminal device 1 receives and acquires this (S102).

The control unit 10 specifies the acquired service code and transmits an application for issuing a taxi digital ticket to the information processing device 2 (step S103). The issuance application includes a provider ID included in the service code, a vehicle number or a driver ID, and a user ID stored in the storage unit 11 of the user terminal device 1.

In the information processing apparatus 2, the first communication unit 22 receives the issuance application (step S201), and the control unit 20 refers to the corresponding usage conditions from the condition DB 205 (step S202) based on the received issuance application. A digital form DF is issued based on the issuance application and usage conditions (step S203). The control unit 20 notifies the payer terminal device 4 of the default payer of the user ID together with the form ID numbered to the issued digital form DF from the second communication unit 23 (step). S204). The control unit 20 transmits information on a digital ticket that allows a taxi to be used based on the digital form DF from the first communication unit 22 to the user terminal device 1 (step S205).

The digital ticket information transmitted in step S205 includes a form ID, a user ID, a provider ID, and a default payer ID included in the digital form DF. The digital ticket information may include the name of the company corresponding to the payer ID and the terms of use corresponding to the user ID.

When the control unit 10 of the user terminal device 1 receives the digital ticket information (step S104), the control unit 10 causes the display unit 13 to output the contents of the digital ticket (see FIG. 16) (step S105).

The control unit 10 presents the digital ticket information, particularly the form ID, to the provider terminal device 3 (step S106). In step S106, the presentation method may be a method in which the control unit 10 displays the user ID and the form ID as a two-dimensional barcode on the display unit 13. In this case, the user holds the display unit 13 over the reading unit 35, which is the camera of the provider terminal device 3 installed in the vehicle, and causes the user to read from the provider terminal device 3. The control unit 10 may transmit the user ID and the form ID to the provider terminal device 3 by using the reading unit 15 which is a short-range wireless communication module. The control unit 10 may transmit the user ID and the form ID to the provider terminal device 3 via the information processing device 2 by the communication unit 12. Note that step S106 is not essential, and the information on the form ID of the digital ticket may be transmitted from the information processing device 2 as long as the provider terminal device 3 brought into the taxi on which the user is riding can be identified.

The provider terminal device 3 acquires the digital ticket information (step S301). In step S301, the control unit 30 of the provider terminal device 3 may read and acquire the two-dimensional bar code displayed on the display unit 13 of the user terminal device 1 by the reading unit 35 as described above. It may be acquired by short-range wireless communication. The control unit 30 may receive the digital ticket information from the information processing device 2.

At the time of step S101, the taxi may already carry the user and start traveling while operating the taximeter. If it is necessary for the provider terminal device 3 in step S106 and step S301 to acquire the digital ticket information before the start of traveling, the taxi starts traveling after acquiring the information in step S301.

The control unit 30 of the provider terminal device 3 determines whether or not the user is in a state of getting off and paying (step S302). When it is determined in step S302 that the vehicle is not in the state of getting off / paying (S302: NO), the control unit 30 acquires the traveling state and transmits it to the information processing device 2 (step S303), and processes the process. Is returned to step S302. The traveling state includes the mileage that can be obtained from the taximeter, the fare based on the mileage, the traveling position, and the like. This makes it possible to monitor the running status of the taxi via the information processing device 2, for example, the provider terminal device 3 used by the operator.

When it is determined in step S302 that the vehicle is in a state of getting off / paying (S302: YES), the control unit 30 transmits the determined charge information to the information processing device 2 in association with the form ID (step). S304). The determined fee may be obtained from the taximeter or may be entered by the driver's operation.

In the information processing apparatus 2, the first communication unit 22 receives the information on the charge corresponding to the form ID (step S206), and the control unit 20 adds the charge to the corresponding digital form DF (step S207). The control unit 20 transmits the charge information to the user terminal device 1 in association with the form ID (step S208), and proceeds to the process in step S209.

The user terminal device 1 receives charge information in association with the form ID for the digital ticket being used by the communication unit 12 (step S107). The control unit 10 displays a confirmation acceptance screen for accepting confirmation of charges based on the received information on the display unit 13 (step S108), accepts confirmation on the confirmation acceptance screen (step S109), and sends the confirmation to the information processing device 2. Notify (step S110).

In the information processing device 2, the control unit 20 determines whether or not the confirmation of the charge has been accepted (step S209). If it is determined that the charge confirmation cannot be accepted (S209: NO), the control unit 20 returns the process to step S209 and waits until the charge confirmation is accepted. When the confirmation is received by the user terminal device 1 and notified, the control unit 20 determines that the confirmation of the charge has been accepted (S209: YES), and notifies the payer terminal device 4 of the approval request (step). S210). The control unit 20 receives the approval for the notified payment approval request (step S211), and includes an item corresponding to taxi use, for example, an item called "transportation expense", an amount, a date and time of use, a user ID, and a form ID that is the basis. Expense information including the above is created (step S212) and transmitted to the payer terminal device 4 (step S213). The approval process of steps S210 and S211 may be automatically performed by transmitting and receiving information to and from the payer terminal device 4, or may be automatically executed based on the usage conditions stored in the condition DB 205.

The control unit 20 executes a payment process for transmitting payment information including payment bank account information corresponding to the payer ID, payment bank account information corresponding to the provider ID, and amount to the payment system 200 (step). S214).

The processing of steps S212-S213 and S214 may be executed ex post facto based on the digital form DF based on the expense processing rule registered in advance in the condition DB 205.

The control unit 20 notifies the user terminal device 1 and the provider terminal device 3 of the completion of payment (step S215), stores the digital form DF as a usage record for which payment has been completed in the usage record DB 208 (step S216), and stores the digital form DF in the usage record DB 208. End the process.

The user terminal device 1 receives a payment completion notification from the communication unit 12 (step S111), and the control unit 10 displays a screen on the display unit 13 indicating that one use of the payment service has been completed in response to the notification. It is displayed (step S112), and one process is completed.

Also in the provider terminal device 3, the communication unit 32 receives the payment completion notification (step S305), and the control unit 30 displays a screen on the display unit 33 indicating that one payment of the payment service has been completed in response to the notification. It is displayed (step S306), and one process is completed.

15 to 18 are views showing an example of a screen displayed on the display unit 13 of the user terminal device 1. FIG. 15 shows an example of the service code reading screen 130. The reading screen 130 includes a service selection screen 131 that includes a list of services. The service selection screen 131 includes a list of businesses narrowed down as businesses that can be used based on the usage conditions of the user by the processing of the information processing device 2, and a list of names of taxi businesses in the first embodiment. The names of taxi operators included in the list can be selected respectively, and if any of them is selected, the provider ID corresponding to the name is acquired as a service code (S102). If the GPS function provided in the user terminal device 1 can identify the taxi to be taken by the position information, the taxi vehicle number may be included in the list.

As shown in FIG. 15, the reading screen 130 includes a reading button 132 for reading a two-dimensional barcode including a service code presented in a taxi. When the reading button 132 is selected, the control unit 10 activates the reading unit 15 which is a camera to acquire the service code including the provider ID from the two-dimensional barcode (S102).

As shown in FIG. 15, the reading screen 130 includes a display button 133 for displaying a two-dimensional barcode including a user ID to be read by the reading unit 35 of the provider terminal device 3 on the display unit 13. When the display button 133 is selected, the user holds the display unit 13 on which the two-dimensional barcode is displayed over the reading unit 35. As a result, the information including the user ID and the provider ID is transmitted from the provider terminal device 3 to the information processing device 2, and the corresponding service code is transmitted from the information processing device 2 to the user terminal device 1 and acquired. (S102). The transmission of the information including the user ID and the provider ID from the provider terminal device 3 to the information processing device 2 is the transmission of the ticket issuance application including the user ID and the provider ID to the information processing device 2 (S201). May be merged with.

FIG. 16 is a diagram showing an example of the contents of the digital ticket display screen 134. As shown in FIG. 16, the display screen 134 shows the service content specified based on the form ID, the issue date, the purpose of use, and the provider ID of the digital form DF that is the basis of the ticket. The digital ticket display screen 134 includes a button 135 for displaying a two-dimensional barcode for displaying the digital ticket information including the form ID in step S106 on the display unit 13.

FIG. 17 is a diagram showing an example of the contents of the digital ticket display screen 134 after the charge is determined. In the display screen 134 shown in FIG. 17, the charge is displayed in the charge column as compared with the display screen 134 shown in FIG. The display screen 134 after the charge is determined includes a confirmation button 136 for the control unit 10 to receive confirmation of the charge. When the confirmation button 136 is selected, the control unit 10 accepts the confirmation (S109) and notifies the information processing apparatus 2 that the confirmation has been accepted (S110).

FIG. 18 is a diagram showing a content example of the usage completion display screen 137. The display screen 137 is a screen displayed in step S112 when the use is completed. On the display screen 137 shown in FIG. 18, detailed information on who the payer is and how much amount is recorded as an expense is displayed. The usage completion display screen 137 includes a button 138 for returning to the main screen.

As a result, the user can take a taxi used for business purposes such as business trips without using cash or a credit card owned by the user. The company to which the user belongs can also eliminate the need for reimbursement of expenses and can dramatically reduce the burden of expense processing operations. The taxi company, which is the service provider, can also collect the fee from the payer by distributing the tablet terminal on which the payer application program 4P is installed to the driver.

[Utilization of usage record]
By using the payment service, the digital form DF for which payment has been completed is accumulated in the usage record DB 208. As shown in FIG. 9, since the usage history is stored in association with the user ID, it is possible to extract the usage record by provider ID. Therefore, as a provider, the payment platform can be used to carry out sales promotion activities.

FIG. 19 is a flowchart showing an example of a processing procedure based on the usage record DB 208. The information processing device 2 regularly, for example, every month, distributes the usage record for each provider ID or each payer ID.

The control unit 20 of the information processing device 2 reads the usage record DB 208 (step S401), and has completed the payment for a predetermined period in which the payer ID of the payer who wishes to distribute the usage record is associated as the payer. A certain digital form DF is extracted (step S402). The predetermined period is the period from the previous distribution to the current distribution, which is regularly carried out.

The control unit 20 sorts the extracted digital form DF by the user ID and the provider ID (step S403), and creates a usage record report summarizing the services or products used for each user, the date and time of use, and the amount of money. (Step S404). The control unit 20 transmits the created usage record report to the payer terminal device 4 corresponding to the payer ID (step S405), and ends the distribution of one usage record.

The control unit 20 executes the processing procedure shown in the flowchart of FIG. 19 for the provider, and transmits a usage record report based on the payment completed digital form DF extracted by the provider ID to the provider terminal device 3. You may.

The information processing device 2 receives an inquiry from the provider regarding the usage record stored in the usage record DB 208, presents the search result of the usage record, and requests the issuance of a ticket for sales promotion activities based on the search result. Accept.

FIG. 20 is a sequence diagram showing an example of a ticket issuance processing procedure based on the usage record DB 208.

The control unit 30 of the provider terminal device 3 processes the search request of the usage record for which the provider ID and the search conditions are specified, based on the operation of the operator, that is, the operation unit 34 of the operator of the management department of the taxi operator. It is transmitted to the device 2 (step S501). The search request can be accepted only by the provider terminal device 3 having the administrator authority even if the same provider ID is set by setting for the provider application program 3P. The search condition includes, for example, the period of use, the amount of money used, or the number of times of use.

In the information processing apparatus 2, the search request is received by the first communication unit 22 (step S411), the control unit 20 reads the usage record DB 208 (step S412), and the provider ID associated with the search request in the usage record. Extracts the digital form DF for which payment has been completed with the provider (step S413). The control unit 20 narrows down the digital form DF extracted in step S413 according to the search condition (step S414), sorts it by user ID or payer ID (step S415), and sorts each user and each payer. A search result including a list of one-time usage contents is transmitted to the provider terminal device 3 (step S416).

The provider terminal device 3 receives the search result (step S502), and the control unit 30 displays the search result on the display unit 33 (step S503). The control unit 30 accepts the ticket issuance condition (step S504), transmits the issuance application specifying the accepted ticket issuance condition to the information processing apparatus 2 (step S505), and ends the process. Ticket issuance conditions include a payer ID, a user ID, a total usage amount for a predetermined period, or the number of usages. The ticket issuance application includes the ticket contents for which the number of times, the discount amount, the discount rate, etc. are specified.

In the information processing apparatus 2, the issuance application is received by the first communication unit 22 (step S417), the payer ID or user ID specified in the issuance application is specified, and a new form ID with the provider ID specified. Is numbered and a digital form DF is issued (step S418). The digital form DF issued in step S418 includes the ticket contents included in the issuance application as usage conditions. In step S418, the control unit 20 may issue a plurality of digital form DFs based on the number of times included in the ticket contents.

As the digital form DF issued in step S418, only the form ID, the issue date and time, the provider ID (service content), and the user ID are specified as shown in the content example of the ticket DB 209 of FIG. The user ID of the digital form DF issued as a ticket for the payer may be empty. In this way, it is possible to issue a digital form DF in which it is undecided who will use it and who will pay it. For expenses that are recorded as entertainment expenses, the payer ID and the user ID may be specified and the provider ID may be empty. The ticket may be a ticket in which only the date and time of use is not specified, the user ID and the provider ID are specified, the charge is zero, or the provider ID is specified as the payer ID.

Based on the issued digital form DF, the control unit 20 sends a ticket to the user terminal device 1 corresponding to the designated user ID or to the payer terminal device 4 corresponding to the designated payer ID. Notify the issuance (step S419). The control unit 20 stores the issued digital ticket in the ticket DB 209 (step S420), transmits an issuance completion notification including a list of issued digital tickets to the provider terminal device 3 (step S421), and ends the process.

The provider terminal device 3 receives the issuance completion notification (step S506), the control unit 30 displays the issuance completion on the display unit 33 (step S507), and ends the process.

The digital ticket issued to the payer terminal device 4 may be sent to the user terminal device 1 via the information processing device 2 after the user ID is designated by the accounting department of the company that is the payer. ..

The ticket issuance notification of the digital ticket based on the digital form DF issued by designating the user ID is displayed on the display unit 13 when the wallet application 1P is started on the user terminal device 1. FIG. 21 is a diagram showing an example of a ticket list screen. FIG. 21A shows the main screen 139. The main screen 139 includes a notification field 140. In the notification column 140, a message that a digital ticket related to taxi use has arrived from the taxi operator to the user and a display button 141 for displaying the ticket list screen are displayed. The main screen 139 also includes a ticket application button 142. When the ticket application button 142 is selected, the control unit 10 displays the reading screen 130 shown in FIG. FIG. 21B shows the ticket list screen 143. As shown in FIG. 21B, the ticket list screen 143 includes a list of digital tickets sent to the user.

As described above, in the payment platform of the present disclosure, the usage record can be accumulated in the usage record DB 208 and the usage record report can be transmitted to the provider or the payer. In addition, by issuing a digital form DF for which the user ID or payer ID has not been determined, it is very easy to develop into the sales promotion business and manage it, and the complicated work of the user and the payer is reduced. Not only will it be provided as a highly convenient platform for providers.

(Embodiment 2)
In the information processing system 100 of the second embodiment, the payment service can be used personally. The configuration of the information processing system 100 in the second embodiment is the same as that in the first embodiment except that the processing procedure between the devices in the utilization sequence is partially different. Of the configurations of the information processing system 100 according to the second embodiment, the common configurations are designated by the same reference numerals, and detailed description thereof will be omitted.

22 and 23 are sequence diagrams showing an example of the utilization sequence according to the second embodiment. Among the processing procedures shown in the sequence diagrams of FIGS. 22 and 23, the procedures common to the processing procedures shown in the sequence diagrams of FIGS. 13 and 14 showing the utilization sequence in the first embodiment are assigned the same step numbers. The detailed description will be omitted.

In the second embodiment, the control unit 10 of the user terminal device 1 specifies the taxi service code and before transmitting the taxi digital ticket issuance application to the information processing device 2, either expense processing or personal expense. Accepts the selection (step S121). When transmitting the issuance application in step S103, the control unit 10 also transmits information indicating whether expense processing or personal burden is selected.

When the information processing apparatus 2 receives the issuance application by the first communication unit 22 (S201), the information processing apparatus 2 refers to the corresponding usage conditions from the condition DB 205 based on the received issuance application (S202), and pays the fee related to the issuance application. Is specified as an expense processing or an individual burden of the user (step S221). In step S202, the control unit 20 refers to both the usage conditions in the case of expense processing and the usage conditions in the case of personal burden, and in step S221, for example, when the number of issuance applications is expense processing. If it exceeds the upper limit of, it may be specified as an individual expense.

Subsequently, the control unit 20 issues the digital form DF based on the result specified in step S221, the issuance application, and the usage conditions (S203). In step S203, the control unit 20 issues a digital form DF by designating the payer ID of the default payer of the user ID when it is specified to be expense processing.

Subsequently, the control unit 20 determines whether or not it has been specified as expense processing (step S222). When it is determined in step S222 that the expense processing is specified (S222: YES), the control unit 20 notifies the payer terminal device 4 of the default payer of the user ID from the second communication unit 23 (step). S204).

If it is determined that the expense processing is not specified (S222: NO), the control unit 20 skips the notification processing to the payer terminal device 4 of S204 and next because it is specified that the payment is to be borne by the individual. The process proceeds to step S205 of.

In the second embodiment, after receiving the charge information in step S206 and adding the charge in step S207, the control unit 20 determines whether or not it is specified as expense processing (step S223). When it is determined in step S223 that the expense processing is specified (S223: YES), it is determined whether or not the charge received in step S206 exceeds the upper limit included in the usage conditions in the case of expense processing (step S224). ).

If it is determined that the amount has been exceeded (S224: YES), the control unit 20 determines the amount to be paid by the payer (step S225), and determines the excess amount as the amount to be paid by the user personally (step S226). Information on each determined charge is transmitted to the user terminal device 1 (S208). The amount of the charge determined in steps S225 and S226 is added to the digital form DF.

If it is determined in step S223 that the expense processing is not specified (S223: NO), the control unit 20 advances the processing to step S208. In this case, since it is specified as an individual burden, it is processed so that the fee is paid to the provider from the user's bank account or credit card.

If it is determined in step S224 that the amount is not exceeded (S224: NO), the control unit 20 advances the process to step S208. In this case, the fee is processed to be paid by the payer.

In the sequence diagrams of FIGS. 22 and 23, it was determined whether or not the usage fee exceeded the upper limit included in the usage conditions. However, the determination of the information processing device 2 is not limited to this, and as described above, when the ticket issuance application is received, it is determined whether or not the upper limit of the number of times of expense processing included in the usage conditions has been exceeded, and the upper limit of the number of times has been exceeded. If so, specify it as an individual expense. The terms of use may be other restrictions such as due date or place.

The procedure shown in the sequence diagram of FIGS. 22 and 23 will be described with reference to a screen example of the user terminal device 1. 24 to 26 are views showing an example of a screen displayed on the display unit 13 of the user terminal device 1 according to the second embodiment.

FIG. 24 is a diagram showing an example of a selection screen 144 for either expense processing or personal burden. The selection screen 144 is displayed on the display unit 13 after the service code is acquired by the reading screen 130 of FIG. The selection screen 144 includes a button 145 for selecting expense processing, a button 146 for selecting personal expense, and further includes a ticket issuance application button 147 based on any selection. In the screen example of FIG. 24, when the expense processing is selected and the issuance application button 147 is selected, the control unit 10 transmits the issuance application of the digital ticket for which the expense processing is specified to the information processing device 2.

FIG. 25 is a diagram showing an example of the contents of the digital ticket display screen 134 according to the second embodiment. In the second embodiment, the usage conditions for the user in the example shown in FIG. 25 include a condition that the taxi fare exceeding 1000 yen is borne by the individual even in the case of expense processing. In the content example of FIG. 25, the usage conditions are specified.

FIG. 26 is a diagram showing an example of the contents of the digital ticket display screen 134 after the charge is determined. As shown in FIG. 26, the display screen 134 includes a determined charge and an excess charge personally borne. When the confirmation button 136 included in the display screen 134 is selected, the control unit 10 accepts the confirmation (S109) and notifies the information processing apparatus 2 that the confirmation has been accepted (S110). In this case, the excess amount of 280 yen with respect to the usage condition of 1000 yen is settled by the user's personal bank account or credit card.

As described above, in the second embodiment, the personal burden and the expense processing can be separately processed based on one digital form DF. Therefore, the user may use the same wallet application 1P for personal use of the service and for expense processing, which is highly convenient for the user. For the payer, only the payment of the fee borne by the payer is executed from the settlement bank account, and the expense information in which the fee is associated with the item for the paid fee can be automatically acquired. There is no need for reimbursement, and the burden of payment work is dramatically reduced. The provider, of course, can be sure to pay for the services and products provided without compromising convenience.

(Embodiment 3)
In the information processing system 100 of the third embodiment, the payer can apply for the issuance of a digital ticket (wallet). A wallet is a bunch of digital tickets. The configuration of the information processing system 100 in the third embodiment is the same as that of the first or second embodiment except that the processing procedure between the devices in the utilization sequence is partially different. Among the configurations of the information processing system 100 according to the third embodiment, the common configurations are designated by the same reference numerals, and detailed description thereof will be omitted.

27 to 29 are sequence diagrams showing an example of the utilization sequence according to the third embodiment. FIG. 27 shows the process until the wallet is transmitted to the user terminal device 1, and FIGS. 28 and 29 show the process until the user uses the wallet on the user terminal device 1 and the payment is completed. Shown. Of the processing procedures shown in the sequence diagrams of FIGS. 27 to 29, the procedures common to the processing procedures shown in the sequence diagrams of FIGS. 13 and 14 of the first embodiment will be described with the same step numbers. To simplify.

In the third embodiment, the payer terminal device 4 accepts an application for a digital wallet, which is a bundle of digital tickets used for transportation expenses, accommodation expenses, food and drink services or products related to business trips (step S601). The application in step S601 may be performed on the system in the company to which the user belongs. The procedure for business trip application may be realized by the wallet application 1P.

Based on the application, the control unit 40 specifies a user ID and usage conditions to be used, and transmits an application for issuing a digital wallet, which is a bundle of digital tickets, to the information processing device 2 (step S602). The issuance application includes an application for issuance of each digital ticket related to transportation expenses, accommodation expenses, and food and drink.

The information processing apparatus 2 receives the issuance application by the second communication unit 23 (S201), and issues the digital form DF based on the usage conditions referred to in step S202 based on the received issuance application (S203). The issued digital form DF will be required for transportation expenses by different service providers such as railroads, airplanes, taxis, buses, etc., and will be paid by service providers that are different from accommodation expenses and food and drink expenses. Therefore, it may be decided to issue a plurality of applications based on the acceptance of the application in step S601. In this case, in step S203, the control unit 20 may associate a plurality of digital form DFs related to the same business trip with each other. For example, the information for identifying a business trip (business trip ID, business trip person and purpose) may be the same.

In the digital form DF issued in step S203, the user ID and the payer ID are specified, but the provider ID is not specified. The provider can select either after the user receives the digital ticket. In this respect, the issuance and processing of the digital form DF based on the service code of the first embodiment is different.

In step S203, by configuring the configuration so that a plurality of service providers can be specified, one digital form DF including expenses of different items is issued, and even if a plurality of digital tickets are issued based on one digital form DF. Good.

The control unit 20 notifies the payer terminal device 4, which is the sender of the issuance application, of the content of the issuance application together with the numbered form ID to the issued digital form DF from the second communication unit 23 (S204). .. Based on the issued digital form DF, the control unit 20 uses the user ID designated by the first communication unit 22 for the information of the digital ticket divided into transportation expenses (plural), accommodation expenses, food and drink expenses, etc. It is transmitted to the person terminal device 1 (S205).

In the payer terminal device 4, the control unit 40 receives the content of the issuance application notified from the information processing device 2 (step S603).

When the control unit 10 of the user terminal device 1 receives the digital ticket information (S104), the control unit 10 outputs a digital ticket notification (see FIG. 30) to the display unit 13 (S105).

Next, the processing when the digital ticket is used will be described with reference to the sequence diagrams of FIGS. 28 and 29. At the time of use, the user uses the user terminal device 1 and presents digital ticket information suitable for the purpose of use, particularly a form ID, to the provider terminal device 3 (S106). If it is a transportation expense, it is presented to the cashier terminal and the provider terminal device 3 which is a check-in terminal at the time of purchasing a ticket or passport, checking in, or boarding a taxi. It may be presented to the provider terminal device 3 which is a cash register terminal at the time of check-in for accommodation and at the time of entry for restaurants. It should be noted that the digital ticket may be presented by short-range radio in cooperation with the transportation IC card.

The provider terminal device 3 acquires the digital ticket information (S301). In step S301, the control unit 30 of the provider terminal device 3 may read and acquire the two-dimensional bar code displayed on the display unit 13 of the user terminal device 1 by the reading unit 35, or short-range wireless communication. May be obtained by.

The control unit 30 of the provider terminal device 3 determines whether or not the user is in a state of making a payment (payment) (step S312). When it is determined in step S312 that the payment (payment) is not performed (S312: NO), the control unit 30 acquires the usage status and transmits it to the information processing device 2 (step S313) for processing. Is returned to step S312.

When it is determined in step S312 that the settlement (payment) is to be performed (S312: YES), the control unit 30 corresponds the determined charge information with the provider ID and the form ID acquired in step S301. It is attached and transmitted to the information processing apparatus 2 (step S314). If the provider terminal device 3 is a cash register terminal, the control unit 30 transmits information indicating the calculated amount of money to the information processing device 2.

The information processing device 2 receives the information of the provider ID and the charge corresponding to the form ID from the provider terminal device 3 by the first communication unit 22 (step S236). The control unit 20 adds the received provider ID and charge to the corresponding digital form DF (step S237). The control unit 20 transmits the charge information to the user terminal device 1 in association with the form ID (S208), and proceeds to the process in step S209.

The user terminal device 1 receives charge information regarding the digital ticket in use (S107). The control unit 10 displays a confirmation reception screen for accepting confirmation of charges on the display unit 13 (S108), accepts confirmation (S109), and notifies confirmation (S110).

When the information processing apparatus 2 determines that the confirmation of the charge has been accepted in step S209 (S209: YES), the information processing apparatus 2 notifies the payer terminal apparatus 4 of the approval request (S210).

The control unit 40 of the payer terminal device 4 receives the approval request (step S604) and approves it based on the amount and usage conditions (step S605). The approval process in step S605 is preferably performed automatically because an immediate response is required, but it may be performed after the fact, so that the approval operation may be performed by the operator of the accounting department. As a result of step S605, the approval is notified to the information processing apparatus 2 (step S606).

The control unit 20 receives the approval for the notified payment approval request (S211), and includes items corresponding to the contents of the digital ticket, such as "transportation expenses" and "accommodation expenses", as well as the amount, date and time of use, and user ID. , And the expense information including the original form ID (S212), and transmit it to the payer terminal device 4 (S213).

When calculating the expense information, the control unit 20 compares the daily allowance specified by each company with the food and drink expenses actually incurred, and determines the amount of the allowance to be deposited in the bank account for the user's personal payment. You may.

The control unit 20 executes a payment process of transmitting the payment information including the payment bank account information corresponding to the payer ID, the deposit bank account information corresponding to the provider ID, and the amount of money to the payment system 200 (S214). ). The control unit 20 notifies the user terminal device 1 and the provider terminal device 3 of the completion of payment (S215), stores the digital form DF as a usage record for which payment has been completed in the usage record DB 208 (S216), and performs processing. finish.

The user terminal device 1 receives a payment completion notification from the communication unit 12 (S111), and the control unit 10 displays a screen indicating that the use using the digital ticket included in the wallet is completed in response to the notification. It is displayed on 13 (S112), and one process is completed.

The provider terminal device 3 also receives a payment completion notification from the communication unit 32 (S305), and the control unit 30 displays a screen on the display unit 33 indicating that one payment of the payment service has been completed in response to the notification. (S306), one process is completed.

In the usage sequence, the processing of FIGS. 28 and 29 is performed each time the service or product is used. There may be digital tickets that are issued in large numbers in advance but are not used. In this case, the corresponding digital form DF may be stored in the usage record DB 208 as unused.

FIG. 30 is a diagram showing an example of the ticket list screen according to the third embodiment. FIG. 30A shows the main screen 139. The main screen 139 includes a notification field 140. In the notification column 140, a message that a digital wallet related to the expenses required for a business trip has arrived from the accounting department of the company to which the user of the user terminal device 1 belongs to the user, and a list of digital tickets included in the wallet. A display button 148 for displaying the screen is displayed. The main screen 139 also includes a ticket application button 142. FIG. 30B shows the ticket list screen 149. As shown in FIG. 30B, the ticket list screen 149 includes a list of digital tickets associated with each other as a digital wallet. The digital ticket is used in the processing procedure as shown in the sequence diagrams of FIGS. 28 and 29, respectively.

In this way, the user can move, stay, and eat and drink on a business trip without using cash or a credit card owned by the user. The company to which the user belongs can also eliminate the need for reimbursement of expenses and can dramatically reduce the burden of expense processing operations. If each business operator that is a service provider can also install a tablet terminal on which the provider application program 3P is installed at the checkout location or have the cashier terminal execute processing based on the provider application program 3P, the payer Fees can be collected from.

Also in the third embodiment, it is possible to process the payment by the individual and the expense processing of the company shown in the second embodiment based on one digital form DF.

In the first to third embodiments, the payer of the fee when the user uses the service or the product is initially designated as the accounting department of the company to which the user belongs. However, the payer can also have the payer issue a digital ticket as shown in Utilization of the usage record of the first embodiment. Therefore, the corporation of the user's business partner or a natural person can be the payer.

The embodiments disclosed as described above are exemplary in all respects and are not restrictive. The scope of the present invention is indicated by the scope of claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

1 User terminal device 10 Control unit 11 Storage unit 13 Display unit 131 Service selection screen 1P wallet application program 2 Information processing device 20 Control unit 2P information processing program 3 Provider terminal device 30 Control unit 3P Provider application program 4 Payer Terminal device 40 Control unit 4P Application program for payer

Claims (12)

Acquire user provider information including user identification information that identifies a user who uses a service or product and provider identification information that identifies a provider who provides the service or product.
When the amount of the service or product that is undecided until the service or product is provided is determined at the time of providing the service or product, the user regarding the amount received from the provider terminal device of the provider. Accepting confirmation from,
After the confirmation is accepted, the expense registration process of the amount of the service or product to the payer of the fee related to the service or product in association with the user provider information, and the provider of the service or product An information processing method that executes payment processing. The provider terminal device of the provider acquires the user identification information and acquires the user provider information from the provider terminal device, or the user terminal device of the user acquires the provider identification information. The information processing method according to claim 1, wherein the user provider information is acquired from the user terminal device. Ticket information for using the service or product including the user provider information is transmitted to the user terminal device of the user, and the ticket information is transmitted.
The information processing method according to claim 1 or 2, wherein the user terminal device receives the ticket information and outputs the ticket information to the display unit. Based on the rank information stored in association with the user identification information of the user or the rank information stored in association with the user provider information, the amount of the charge related to the service or product The amount that the payer can pay is determined.
The information processing method according to any one of claims 1 to 3, wherein the expense registration process is executed for the determined amount. If the amount exceeds the determined amount, the excess charge is processed by the payment method associated with the user identification information of the user to the provider. The information processing method according to 4. The usage record for which payment processing has been executed is stored in association with the user identification information or the provider identification information.
Output the usage record extracted from the user identification information or the provider identification information,
To use the service or product to the user identified by the user identification information based on the frequency of use or the number of times of use of the same service or product included in the usage record extracted by the user identification information. The information processing method according to claim 1, wherein the ticket information of the above is transmitted. The information processing method according to any one of claims 1 to 6, wherein the payer is determined based on the setting information of the organization to which the user belongs. Acquire user provider information including user identification information that identifies a user who uses a service or product, and provider identification information that identifies a provider who provides the service or product.
When the amount of the service or product , which is undecided until the service or product is provided, is determined at the time of providing the service or product, the use of the amount received from the provider terminal device of the provider. Accepting confirmation from the person,
An information processing method that specifies whether payment of a fee related to the service or product shall be expensed or paid by the user before the service or product is provided or at the time of receiving confirmation . When it is specified as expense processing, the expense registration process of the amount of the service or product to the payer of the fee related to the service or product in association with the user provider information, and the service or the service from the payer The information processing method according to claim 8, which executes a payment process for a product provider. An acquisition unit that acquires user identification information that identifies a user who uses a service or product, and user provider information that includes provider identification information that identifies a provider who provides the service or product.
When the amount of the service or product , which is undecided until the service or product is provided, is determined at the time of providing the service or product, the amount received from the provider terminal device of the provider is received from the user. Confirmation unit that accepts confirmation of
After the confirmation is received by the confirmation unit, the expense registration process of the amount of the service or product to the payer of the fee related to the service or product in association with the user provider information, and the service or product An information processing device that includes a processing unit that executes payment processing for the provider of. Acquire user provider information including user identification information that identifies a user who uses a service or product, and provider identification information that identifies a provider who provides the service or product.
If the service or product is the amount of the service or product is not determined until it is provided, has been determined at the time of the provision of the service or product, you accept the confirmation from the user for the amount of money,
After the confirmation is accepted, the expense registration process of the amount of the service or product to the payer of the fee related to the service or product in association with the user provider information, and the provider of the service or product A computer program that causes a computer to execute processing that displays information about payment processing on the display. Acquire user provider information including user identification information that identifies a user who uses a service or product, and provider identification information that identifies a provider who provides the service or product.
When the amount of the service or product , which is undecided until the service or product is provided, is determined at the time of providing the service or product, the user regarding the amount received from the provider terminal device of the provider. Accepting confirmation from,
Before the service or product is provided, or when the confirmation is accepted , the computer is made to execute a process of accepting the selection of whether to pay the fee related to the service or product as an expense process or to pay the user's personal expense. Computer program.

Images