Information processing device, program, and information processing method
Patent Information
- Application Number
- JP2023099467
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-06-16
- Publication Date
- 2025-03-06
- Estimated Expiration
- 2043-06-16
AI Technical Summary
【0027】 本発明によれば、ユーザの決済における利便性を保ちつつ、決済結果の容易な把握を可能とするプログラム、方法、及び情報処理装置を提供することができる。
Smart Images

Figure 0007641080000001 
Figure 0007641080000002 
Figure 0007641080000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device, a program, and an information processing method. [Background technology]
[0002] Currently, many payment service providers are offering payment services that use 2D codes. When making a payment at a store, users can operate their smartphone to launch the application for the payment service they want to use and perform the required operations to make the payment.
[0003] In a payment service using a two-dimensional code, a two-dimensional code installed in a store or the like is read by a user's smartphone. There is also a system in which a store or the like that has contracts with multiple payment service providers allows a user to read a certain two-dimensional code that can be read by each application provided by each payment service provider, enabling payment by each payment service provider. Patent Document 1 discloses a payment service using a two-dimensional code. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Special Publication No. 2016-522938 Summary of the Invention [Problem to be solved by the invention]
[0005] When a payment is made through a service provided by a payment service provider selected by a user using an application for each payment service provider, the payment information is recorded for each payment service provider. For example, if a seller wants to centrally manage information identifying a payment and the payment result, the seller needs to obtain information separately from each payment service provider.
[0006] Therefore, an object of the present invention is to provide an information processing device, a program, and an information processing method that enable a user to easily grasp the result of a payment while maintaining convenience in the payment process. [Means for solving the problem]
[0007] An information processing device according to one embodiment of the present invention is an information processing device in a system in which payment is made by reading a specified code with an application installed on a user terminal used by a user making a payment, and comprises a payment information acquisition unit that acquires payment identification information that identifies the payment and payment amount information indicating the amount of the payment from the user terminal in response to the user terminal reading the specified code, a reception unit that accepts a payment request from the user terminal specifying one of a plurality of payment providers to execute the payment processing, a request unit that sends a request for payment processing to a payment execution device corresponding to the payment provider when the reception unit accepts the payment request, a payment result acquisition unit that acquires the processing result of the payment processing from the payment execution device corresponding to the payment provider, and a payment result memory unit that stores payment result information in which the processing result is associated with the payment identification information and the payment amount information.
[0008] According to this aspect, the information processing device can accept, from a user terminal, the designation of one of the multiple payment providers to execute the payment process. The information processing device acquires the processing result of the payment process from a payment execution device corresponding to the payment provider. The information processing device stores the payment identification information for identifying the payment and the payment amount information acquired in response to reading a predetermined code in association with the processing result. This makes it possible for the information processing device to store the payment identification information for identifying the payment and the payment amount information in association with the processing result, even when a user makes a payment using one payment provider selected from the multiple payment providers. This makes it possible for the user to easily grasp the payment result while maintaining the convenience of payment.
[0009] In the above aspect, the payment information acquisition unit may acquire the payment identification information and the payment amount information in response to reading a predetermined code generated based on the payment identification information and the payment amount information.
[0010] This allows the payment identification information and payment amount information to be included in advance in the specific code. For example, by dynamically generating the specific code, the payment identification information and payment amount information can be updated as appropriate, while maintaining the convenience of the user's payment and allowing the user to easily understand the payment result.
[0011] In the above aspect, the payment information acquisition unit may generate input screen information for displaying an input screen on a user terminal that accepts input of payment identification information and payment amount information, and acquire the payment identification information and payment amount information from the user terminal via the input screen.
[0012] As a result, for example, payment identification information and payment amount information are communicated to the user at the time of payment, and the payment is executed and the result is stored based on the payment identification information and payment amount information entered using the user terminal. Therefore, for example, even if it is necessary to record a code on a specified medium and make a payment while changing the payment identification information and payment amount information, the convenience of the user in payment is maintained and the payment result can be easily understood.
[0013] In the above aspect, the reception unit may receive a request to refer to payment result information from a seller terminal in a payment, and notify the seller terminal of the payment result information related to the seller.
[0014] This makes it easier for the seller to understand the settlement result.
[0015] In the above aspect, the predetermined code may be a code including business information that identifies the business of the seller in the payment.
[0016] This eliminates the need to separately input information for identifying the business operator, improving convenience for users in making payments.
[0017] In the above aspect, the predetermined code may be a code including provider information for identifying a provider of a service when the subject of the payment is the provision of a service.
[0018] This eliminates the need to separately input information identifying the provider, improving convenience for users in making payments.
[0019] In the above aspect, the information processing device may further include a notification unit that notifies the user terminal of a processing result of the payment processing.
[0020] This allows the user to quickly know when the payment has been completed, improving convenience for the user when making payments.
[0021] In the above aspect, the payment result acquisition unit may acquire a processing result including information about the payment service provider that executed the payment processing.
[0022] This enables, for example, a seller to grasp the trends of the payment service provider designated by the user, improving convenience in grasping payment results.
[0023] In the above aspect, the payment information acquisition unit acquires from the user terminal additional amount information indicating the payment amount of an additional payment that occurred after the payment and associated with payment identification information, the reception unit accepts from the user terminal a payment request specifying one of multiple payment providers to execute the additional payment processing, which is payment processing for the additional payment, the request unit transmits a request for the additional payment processing to the payment execution device corresponding to the payment provider, the payment result acquisition unit acquires the processing result of the additional payment processing from the payment execution device corresponding to the payment provider, and the payment result memory unit stores payment result information in which the processing result of the additional payment processing is associated with the payment identification information and the additional amount information.
[0024] This allows additional payments to be made, improving payment convenience for users.
[0025] Another aspect of the present invention is a program in a system in which payment is made by reading a specified code with an application installed on a user terminal used by a user making a payment, which causes a computer to obtain, in response to reading the specified code by the user terminal, payment identification information that identifies the payment and payment amount information that indicates the amount of the payment from the user terminal, accept a payment request from the user terminal that specifies one of a plurality of payment providers to execute the payment processing, and, upon accepting the payment request, send a request for payment processing to a payment execution device corresponding to the payment provider, obtain a processing result of the payment processing from the payment execution device corresponding to the payment provider, and store payment result information in which the processing result is associated with the payment identification information and the payment amount information.
[0026] A program according to another aspect of the present invention is an information processing method in which a payment is made by reading a specific code with an application installed on a user terminal used by a user making a payment, the program comprising the steps of: acquiring, from the user terminal in response to reading the specific code by the user terminal, payment identification information that identifies the payment and payment amount information that indicates the amount of the payment; accepting, from the user terminal, a payment request that specifies one of a plurality of payment providers to execute the payment process; When a payment request is accepted, the method includes sending a request for payment processing to a payment execution device corresponding to the payment service provider, obtaining a processing result of the payment processing from the payment execution device corresponding to the payment service provider, and storing payment result information in which the processing result is associated with payment identification information and payment amount information. Effect of the Invention
[0027] According to the present invention, it is possible to provide a program, a method, and an information processing device that enable a user to easily grasp the result of a payment while maintaining convenience in the payment process. [Brief description of the drawings]
[0028] [Figure 1] FIG. 1 is a schematic diagram of a payment management system. [Diagram 2] FIG. 2 is a diagram illustrating an outline of processing in a payment management system. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of the payment management device. [Figure 4] FIG. 2 is a block diagram of each device or terminal in the payment management system. [Diagram 5] 11 is a diagram illustrating information stored in the payment management device. FIG. [Figure 6] FIG. 2 is a diagram illustrating a process flow in the payment management system. [Figure 7] FIG. 13 is a diagram showing an example of a payment confirmation screen in the payment management system. [Figure 8] FIG. 13 is a diagram showing an example of a payment service provider selection screen in the payment management system. [Figure 9] FIG. 13 is a diagram showing an example of a payment result screen in the payment management system. [Figure 10] FIG. 11 is a diagram illustrating another flow of processing in the payment management system. [Figure 11] FIG. 13 is a diagram showing another example of a payment confirmation screen in the payment management system. [Figure 12] 11 is a diagram illustrating a process for viewing payment result information in the payment management system. FIG. [Figure 13] FIG. 11 is a diagram showing an example of payment result information in the payment management system. [Figure 14] FIG. 11 is a diagram illustrating another flow of processing in the payment management system. [Figure 15] FIG. 13 is a diagram showing another example of a payment confirmation screen in the payment management system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will now be described with reference to the accompanying drawings, in which like reference numerals denote like or similar structures.
[0030] Fig. 1 shows a block diagram illustrating an outline of a payment management system 10 according to this embodiment. The payment management system 10 includes a payment management device 101, user terminals 201a, 201b, 201c, payment execution devices 301a, 301b, 301c, and a business operator terminal 401. Although there are a plurality of user terminals and payment execution devices, such as user terminals 201a, 201b, 201c and payment execution devices 301a, 301b, 301c, they will be simply referred to as user terminal 201 and payment execution device 301 when there is no need to distinguish between them.
[0031] In the payment management system 10, the user terminal 201, the payment management device 101, and the business terminal 401 are communicatively connected via a network N1. Also, in the payment management system 10, the payment management device 101 and the payment execution device 301 are communicatively connected via a network N2.
[0032] In the payment management system 10, a user making a payment reads a predetermined code (e.g., a two-dimensional code) using the user terminal 201 to access the payment management device 101. The payment management device 101 accepts the designation of a payment business operator designated by the user from the user terminal 201, and accesses the payment execution device 301 of the designated payment business operator. The user terminal 201 transmits information necessary for payment to the payment execution device 301. The payment is executed by the payment execution device 301, and the payment result is transmitted to the payment management device 101. The payment management device 101 notifies the user terminal 201 that the payment has been completed, and completes the payment.
[0033] Here, transactions that are the subject of settlement include, but are not limited to, various transactions such as the provision of services such as cleaning, the use of amusement facilities, and the purchase of goods.
[0034] The payment management device 101 is a server device having a computer that performs predetermined processes by executing predetermined programs stored in a storage unit of the payment management device 101 .
[0035] The user terminal 201 is, for example, an information processing device used by a user, such as a smartphone, a tablet terminal, a personal computer, etc. The user terminal 201 has an imaging means such as a camera, and can acquire information from a two-dimensional code.
[0036] The payment execution device 301 is a server device having a computer that performs predetermined processing by executing a predetermined program stored in the memory unit of the payment execution device 301. The payment execution device 301 performs payment by communicating with the user terminal 201. The user terminal 201 may access the payment execution device 301 through the payment management device 101, or may access the payment execution device 301 by directly communicating with the payment execution device 301.
[0037] The business operator terminal 401 is an information processing device used by a business user, and is a smartphone, a tablet terminal, a personal computer, etc. The business operator can access the payment management device 101 from the business operator terminal 401 and grasp the status of the payment.
[0038] An overview of information processing by the payment management system 10 will be described with reference to Fig. 2. In the example of Fig. 2, a case will be described in which a user U makes a payment for a service or product provided by a certain business operator or provider.
[0039] In step (A), the user terminal 201 reads a predetermined code CD1, CD2, or CD3. Here, the code CD1 is printed, for example, on a card C1 indicating the affiliation of the donor, and the codes CD2 and CD3 are displayed, for example, on the screens of the terminals D1 and D2 held by the donor.
[0040] In step (B), the user terminal 201 of the user U acquires payment identification information and payment amount information. Here, the payment identification information is information for identifying each case, for example, when a service is provided to the user U. Alternatively, the payment identification information may be a product code or the like for identifying a product. The payment amount information is information indicating the amount to be paid by the user U.
[0041] The payment identification information and the payment amount information may be recorded in advance as information in the code CD1, CD2, or CD3, or may be input via the screen of the user terminal 201. When the payment identification information and the payment amount information are input via the screen of the user terminal 201, the input may be performed by the user U or by the provider.
[0042] Moreover, the code CD1, CD2, or CD3 may include business entity information for identifying a business entity, or may include provider information for identifying a provider.
[0043] In step (C), the user terminal 201 accesses the payment management device 101 based on the information contained in the code CD1, CD2, or CD3, and transmits payment identification information and payment amount information to the payment management device 101. Access from the user terminal 201 to the payment management device 101 is performed, for example, by accessing the URL embedded in the code CD1, CD2, or CD3 using browsing software (application) installed in the user terminal 201.
[0044] In step (D), the payment management device 101 presents to the user U via the user terminal 201 payment service providers that the user U can use.
[0045] In step (E), the user U operates the user terminal 201 to specify a payment service provider.
[0046] In step (F), the user terminal 201 makes a payment processing request including information about the specified payment business operator to the payment management device 101.
[0047] In step (G), the payment management device 101 transmits a request for payment processing to the payment execution device 301 of the specified payment business operator.
[0048] In step (H), the payment management device 101 acquires the result of the payment process from the payment execution device 301 of the specified payment business operator.
[0049] In step (I), the payment management device 101 notifies the user terminal 201 of the result of the payment process.
[0050] In the payment management system 10, the payment identification information and the payment amount information are associated with the processing result and stored in the payment management device 101. The business operator can grasp the stored information by accessing the payment management device 101 through the business operator terminal 401. This allows the business operator to grasp the status of the payment only by accessing the payment management device 101, without accessing the payment execution device 301 or system of each payment business operator (payment business operator A, payment business operator B, payment business operator C).
[0051] In the payment management system 10, the payment process is completed by communication between the user terminal 201 and the payment management device 101, and the business terminal 401 does not need to execute the payment process itself. For example, when the payment process is executed by a cashless payment terminal such as a POS terminal or a credit card payment terminal managed by the business, it is considered that the payment process cannot be executed when the network to which the terminal is connected is interrupted or the power supply to the terminal is stopped due to a power outage. For example, such a situation may occur when a disaster occurs. On the other hand, in the payment management system 10, the payment is completed by communication between the user terminal 201 and the payment management device 101, so that the payment process can be completed as long as the network between the user terminal 201 and the payment management device 101 is available and power is supplied to each of the user terminal 201 and the payment management device 101. Therefore, the payment management system 10 can complete the cashless payment even when a disaster occurs, for example.
[0052] An example of a hardware configuration of the payment management device 101 will be described with reference to Fig. 3. The payment management device 101 has a processor 501 such as a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit), a storage device 502 such as a memory, an HDD (Hard Disk Drive) and / or an SSD (Solid State Drive), a communication IF (Interface) 503 for wired or wireless communication, an input device 504 for accepting input operations, and an output device 505 for outputting information. The input device 504 is, for example, a keyboard, a touch panel, or a mouse. The output device 505 is, for example, a display or a touch panel.
[0053] 4, the following describes each of the payment management device 101, the user terminal 201, the payment execution device 301, and the business operator terminal 401. Each of the units of the payment management device 101, the user terminal 201, the payment execution device 301, and the business operator terminal 401 can be realized by a processor executing a program stored in a storage device in an information processing device having the above-mentioned hardware configuration.
[0054] The payment management device 101 has a communication unit 1011 , a memory unit 1012 , a payment information acquisition unit 1013 , a reception unit 1014 , a request unit 1015 , a payment result acquisition unit 1016 , a payment result memory unit 1017 , and a notification unit 1018 .
[0055] The communication unit 1011 can be realized by using the communication IF 503 included in the payment management device 101. The storage unit 1012 can be realized by using the storage device 502 included in the payment management device 101. The payment information acquisition unit 1013, the reception unit 1014, the request unit 1015, the payment result acquisition unit 1016, the payment result storage unit 1017, and the notification unit 1018 can be realized by the processor 501 of the payment management device 101 executing a program stored in the storage device 502. The program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer readable storage medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a USB memory or a CD-ROM.
[0056] The communication unit 1011 controls communication between the payment management device 101 and devices external to the payment management device 101 , including the user terminal 201 , the payment execution device 301 , and the business operator terminal 401 .
[0057] The storage unit 1012 stores various information used in the processing in the payment management device 101. The storage unit 1012 includes a payment result DB10121.
[0058] Referring to Figure 5, the payment result information stored in payment result DB10121 will be described. The payment result information has the following fields: "payment identification information", "payment amount", "payment provider", and "payment result". The "payment identification information" field stores payment identification information. The "payment amount" field stores the payment amount. The "payment provider" field stores information indicating the payment method. The "payment result" field stores information indicating the result of payment by the payment execution device 301.
[0059] In the example of FIG. 5, for a payment with payment identification information "123456", the payment amount is "5,000 yen", the payment company is "credit card", and the payment result is "payment successful". For a payment with payment identification information "987654", the payment amount is "10,000 yen", the payment company is "A Pay", and the payment result is "payment successful". Information stored in the payment company field is, for example, a name such as "credit card" or "A Pay", which is a payment service that enables electronic payment, depending on the payment method as described above. In addition, for "credit card", information indicating a payment brand or the like and information indicating the acquirer or issuer of the card may be further stored.
[0060] The payment information acquisition unit 1013 acquires payment identification information for identifying a payment and payment amount information indicating the amount of the payment from the user terminal 201 in response to reading the code by the user terminal 201. The payment information acquisition unit 1013 also acquires the payment identification information and the payment amount information in response to reading a predetermined code generated based on the payment identification information and the payment amount information. Alternatively, the payment information acquisition unit 1013 generates input screen information for displaying an input screen on the user terminal 201 that accepts input of the payment identification information and the payment amount information, and acquires the payment identification information and the payment amount information from the user terminal 201 via the input screen.
[0061] The reception unit 1014 receives a payment request specifying one of a plurality of payment providers to execute the payment process from the user terminal 201. For example, the reception unit 1014 displays a payment provider selection screen described below on the user terminal 201, and receives a payment request specifying a payment provider through the payment provider selection screen. The reception unit 1014 also receives a request to refer to payment result information from the provider terminal 401.
[0062] When the reception unit 1014 receives a payment request, the request unit 1015 transmits a request for payment processing to the payment execution device 301 corresponding to the payment business operator. The request unit 1015 may relay information so that the user terminal 201 can access the payment execution device 301 via the payment management device 101, or may provide the user terminal 201 with information for the user terminal 201 to directly access the payment execution device 301.
[0063] The payment result acquisition unit 1016 acquires the processing result of the payment process from the payment execution device 301 corresponding to the specified payment company.
[0064] The payment result storage unit 1017 stores payment result information in which the processing result is associated with the payment identification information and the payment amount information in the payment result DB 10121.
[0065] The notification unit 1018 notifies the user terminal 201 that sent the payment request of the result of the payment process.
[0066] The user terminal 201 has a communication unit 2011, a storage unit 2012, a display unit 2013, and an input unit 2014. The communication unit 2011 controls communication between the user terminal 201 and external devices such as the payment management device 101 and the payment execution device 301. The storage unit 2012 stores programs and the like required for the operation of the user terminal 201. The display unit 2013 is, for example, a display, and presents a screen to a user who operates the user terminal 201. The input unit 2014 controls input of information to the user terminal 201. The input unit 2014 accepts input of information from a user through, for example, a screen displayed on the display unit 2013. The input unit 2014 also accepts input of image information through an imaging device of the user terminal 201. When a code is read as an image, the input unit 2014 extracts information based on information included in the code. In accordance with the extracted information, the user terminal 201 can communicate with the payment management device 101 and the like.
[0067] The payment execution device 301 is a server that performs payment processing, and has a payment unit 3011. The payment execution device 301 also has components necessary for various information processing, such as a communication unit and a memory unit. The payment unit 3011 obtains information necessary for settling the payment amount (e.g., credit card information, account information for payment service, etc.) from the payment management device 101 or the user terminal 201, and performs payment processing. The payment execution device 301 transmits the payment result to the payment management device 101.
[0068] The business operator terminal 401 has a communication unit 4011, a storage unit 4012, a display unit 4013, and an input unit 4014. The communication unit 4011 controls communication between the business operator terminal 401 and external devices such as the payment management device 101. The storage unit 4012 stores programs and the like required for the operation of the business operator terminal 401. The display unit 4013 is, for example, a display, and presents a screen to a user operating the business operator terminal 401. The input unit 4014 controls input of information to the business operator terminal 401.
[0069] 6, 7, 8 and 9, the process relating to payment in the payment management system 10 will be described. Here, the case where payment identification information and payment amount information are embedded in the code will be described as an example.
[0070] In step S601, the user terminal 201 reads the code.
[0071] In step S602, the payment information acquisition unit 1013 acquires from the user terminal 201 a payment confirmation screen request, payment identification information, and payment amount information.
[0072] In step S603, the reception unit 1014 generates information for a payment confirmation screen. In step S604, the reception unit 1014 transmits the information for the payment confirmation screen to the user terminal 201.
[0073] In step S605, the user terminal 201 displays a payment confirmation screen on the display unit 2013. Here, the payment confirmation screen 701 will be described with reference to FIG.
[0074] The payment confirmation screen 701 has a payment destination information display area 7011 , a receipt number display area 7012 , a payment amount display area 7013 , and buttons 7014 .
[0075] In the payment information display area 7011, information about the payee is displayed based on the information embedded in the code. In the example of Fig. 7, the business information of the payee indicates that the business is "XX Service Co., Ltd." and the person in charge information indicates that the person in charge is "XXXX." The information displayed in the payment information display area 7011 may be based on information read from the code and stored in the user terminal 201, or may be information included in the information on the payment confirmation screen after the business information and person in charge information are transmitted from the user terminal 201 to the payment management device 101.
[0076] The receipt number is displayed as payment identification information in receipt number display area 7012. The payment amount display area 7013 displays the payment amount as payment amount information.
[0077] When the user checks the payment confirmation screen 701 and presses a button 7014 , a confirmation input indicating that the payment confirmation screen 701 has been checked is sent to the payment management apparatus 101 .
[0078] In step S 606 , the reception unit 1014 acquires a confirmation input from the user terminal 201 .
[0079] In step S607, the reception unit 1014 generates information for a payment service provider selection screen. In step S608, the reception unit 1014 transmits the information for the payment service provider selection screen to the user terminal 201.
[0080] In step S609, the user terminal 201 displays a payment service provider selection screen on the display unit 2013. Here, the payment service provider selection screen 801 will be described with reference to FIG.
[0081] The payment service provider selection screen 801 has a payment details display area 8011, selection buttons 8012a, 8012b, 8012c, and button 8013. The payment details display area 8011 displays information indicating the payment details confirmed on the payment confirmation screen 701. The selection buttons 8012a, 8012b, 8012c are buttons for selecting a payment method selectable by the user. For example, when the user selects the selection button 8012a, credit card payment is designated as the payment method. When the user presses button 8013, a payment request using the designated payment method is transmitted to the payment management device 101.
[0082] In step S610, the accepting unit 1014 receives a payment request from the user terminal 201.
[0083] In step S611, the request unit 1015 transmits a request for payment processing to the payment execution device 301 of the specified payment business operator based on the payment request.
[0084] In step S612, the settlement unit 3011 performs settlement processing. At this time, the settlement execution device 301 may obtain information necessary for settlement from the user terminal 201 as necessary.
[0085] In step S 613 , the payment result acquisition unit 1016 acquires the payment result from the payment execution device 301 .
[0086] In step S614, the payment result storage unit 1017 updates the payment result information stored in the payment result DB 10121 based on the payment identification information, the payment amount information, and the payment result.
[0087] In step S615, the notification unit 1018 notifies the user terminal 201 of the result of the payment.
[0088] In step S616, a payment result screen is displayed on the display unit 2013 of the user terminal 201. Here, the payment result screen 901 will be described with reference to FIG. 9. The payment result screen 901 has a result display area 9011. The result display area 9011 displays business information or provider information, payment identification information, payment amount information, and payment business information indicating the payment business. For example, the payment result screen 901 displays information such as "Payee: XX Service Co., Ltd.", "Reception number: 123456", "Payment amount: 5,000 yen", and "Payment method: Credit card". The user can know whether the payment process has been completed by checking the payment result screen 901. If the payment fails, a screen indicating the payment failure is displayed on the user terminal 201.
[0089] An example of another process in the payment management system 10 will be described with reference to Fig. 10. Here, a case will be described in which payment identification information and payment amount information are input to the user terminal 201 and acquired by the payment management device 101.
[0090] In step S1001, the user terminal 201 reads the code.
[0091] In step S1002, the payment information acquisition unit 1013 acquires a request for a payment confirmation screen from the user terminal 201.
[0092] In step S1003, the payment information acquisition unit 1013 generates information for the input screen. In step S1004, the payment information acquisition unit 1013 transmits the information for the input screen to the user terminal 201.
[0093] In step S1005, the user terminal 201 displays a payment confirmation screen on the display unit 2013. Here, the payment confirmation screen 1101 will be described with reference to FIG.
[0094] The payment confirmation screen 1101 has a payment destination information display area 11011 , a receipt number input area 11012 , a payment amount input area 11013 , and buttons 11014 .
[0095] The payment destination information display area 11011 displays information about the payment destination based on the information embedded in the code. The reception number input area 11012 accepts input of the reception number via the input unit 2014. The payment amount input area 11013 accepts input of the payment amount via the input unit 2014. The example in FIG. 11 shows a situation in which the reception number has been partially input up to "12345" and the payment amount has been partially input up to "5.00". After the user has finished inputting the reception number and payment amount, they press button 7014, which sends the input payment identification information and payment amount information to the payment management device 101.
[0096] In step S1006, the reception unit 1014 acquires payment identification information and payment amount information from the user terminal 201. In step S1007, the reception unit 1014 generates information for a payment service provider selection screen. After this, the processing from step S608 described with reference to Fig. 6 is performed to execute processing related to the payment.
[0097] With reference to Fig. 12, the process for confirming the payment result via the business operator terminal 401 will be described. In step S1201, the business operator terminal 401 sends a request for payment result information to the payment management device 101. In step S1202, the payment management device 101 refers to the payment result DB 10121 and sends the payment result information to the business operator terminal 401. In step S1203, the business operator terminal 401 displays a payment result confirmation screen on the display unit 4013.
[0098] The payment result confirmation screen 1301 will be described with reference to Fig. 13. The payment result confirmation screen 1301 has the fields "payment company", "payment identification information", "payment amount", and "payment result". The payment result confirmation screen 1301 may display payment result information extracted by payment company as shown in Figs. 13(a) and (b), or may display payment result information without extraction by payment company as shown in Fig. 13(c). Businesses can understand the payment results through the payment result confirmation screen 1301.
[0099] The process related to the additional payment (additional payment process) will be described with reference to Fig. 14. Here, the additional payment refers to a payment made in relation to a certain payment identification information after a payment related to the same payment identification information has been made.
[0100] In step S1401, the user terminal 201 displays an additional payment screen in response to a user operation. On the additional payment screen, for example, a button is displayed for the user to input that he / she wishes to make an additional payment. In step S1402, the user terminal 201 acquires additional amount information. The additional amount information may be acquired, for example, by the user terminal 201 reading a code for the additional payment.
[0101] In step S1403, the payment information acquisition unit 1013 acquires a payment confirmation screen request and additional payment amount information from the user terminal 201.
[0102] In step S1404, the reception unit 1014 generates information for a payment confirmation screen based on the acquired payment confirmation screen request and additional payment amount information. An example of the payment confirmation screen is shown in FIG. 15. Here, a payment confirmation screen 1501 for additional payment will be described with reference to FIG. 15. The payment confirmation screen 1501 has a payment destination information display area 15011, a receipt number display area 15012, a payment amount display area 15013, and a button 15014. The payment destination information display area 15011 displays information about the payment destination. The receipt number display area 15012 displays payment identification information that is the subject of the additional payment. The payment identification information may be transmitted to the payment management device 101 so as to be included in the payment confirmation screen request, or may be held in the user terminal 201. The payment amount display area 15013 displays the additional payment amount.
[0103] When the user confirms the payment confirmation screen 1501 and presses a button 15014 , a confirmation input indicating that the payment confirmation screen 1501 has been confirmed is sent to the payment management apparatus 101 .
[0104] In step S1407, the reception unit 1014 acquires a confirmation input from the user terminal 201. After that, the process from step S607 described with reference to Fig. 6 is carried out and the process related to the payment is executed.
[0105] In this way, the payment management device 101 also allows additional payments to be made, which improves the convenience of payments for users.
[0106] In this way, payment is made through the payment management system 10. The payment management system 10 allows the user to select from multiple payment providers and stores the payment identification information along with the payment result. This allows the user to easily understand the payment result while maintaining the convenience of payment.
[0107] The above-described embodiment is intended to facilitate understanding of the present invention, and is not intended to limit the present invention. The elements of the embodiment, as well as their arrangement, conditions, shape, size, etc., are not limited to those exemplified, and may be modified as appropriate. [Explanation of symbols]
[0108] 10: payment management system, 101: payment management device, 201: user terminal, 301: payment execution device, 401: business operator terminal, 1013: payment information acquisition unit, 1014: acceptance unit, 1015: request unit, 1016: payment result acquisition unit, 1017: payment result storage unit
Claims
1. An information processing device in a system in which a payment is made by reading a predetermined code associated with a plurality of payment service providers that are candidates for a payment service provider that executes a payment process, using an application installed on a user terminal used by a user making a payment, a payment information acquisition unit that acquires, in response to reading of the predetermined code by the user terminal, payment identification information that identifies the payment and payment amount information that indicates an amount of the payment from the user terminal; a reception unit that, in response to reading the predetermined code by the user terminal, presents information of the plurality of payment service providers associated with the predetermined code to the user through the user terminal, and receives a payment request from the user terminal that specifies one of the plurality of payment service providers to execute the payment process; a request unit that transmits a request for the payment process to a payment execution device corresponding to the payment business operator when the reception unit receives the payment request; a payment result acquisition unit that acquires a processing result of the payment process from a payment execution device corresponding to the payment business operator; a payment result storage unit that stores payment result information in which the processing result is associated with the payment identification information and the payment amount information; An information processing device comprising:
2. 2. The information processing device according to claim 1, The payment information acquisition unit acquires the payment identification information and the payment amount information in response to reading the specified code generated based on the payment identification information and the payment amount information.
3. 2. The information processing device according to claim 1, The payment information acquisition unit, generating input screen information for displaying an input screen for accepting input of the payment identification information and the payment amount information on the user terminal; An information processing device that acquires the payment identification information and the payment amount information from the user terminal via the input screen.
4. 2. The information processing device according to claim 1, The receiving unit receives a request to refer to the payment result information from a terminal of a seller in the payment, and notifies the seller's terminal of the payment result information related to the seller.
5. 2. The information processing device according to claim 1, An information processing device, wherein the predetermined code is a code including business information identifying a business of a seller in the payment.
6. 6. The information processing device according to claim 5, An information processing device, wherein the predetermined code is a code including provider information that identifies a provider of a service when the subject of the payment is the provision of the service.
7. 2. The information processing device according to claim 1, a notification unit that notifies the user terminal of a processing result of the payment processing; The information processing device further comprises:
8. 2. The information processing device according to claim 1, The information processing device, wherein the payment result acquisition unit acquires the processing result including information of the payment service provider that executed the payment processing.
9. 2. The information processing device according to claim 1, The payment information acquisition unit acquires additional amount information from the user terminal, the additional amount indicating a payment amount of an additional payment that occurred after the payment and associated with the payment identification information, The reception unit receives, from the user terminal, a payment request that designates one of a plurality of payment providers to execute an additional payment process, which is the payment process for the additional payment, and The request unit transmits a request for the additional payment process to a payment execution device corresponding to the payment business operator, The payment result acquisition unit acquires a processing result of the additional payment process from a payment execution device corresponding to the payment business operator, the payment result storage unit stores payment result information in which the processing result of the additional payment process is associated with the payment identification information and the additional amount information; Information processing device.
10. In a system in which a payment is made by reading a predetermined code associated with a plurality of payment service providers that are candidates for a payment service provider that executes a payment process, using an application installed on a user terminal used by a user making a payment, On the computer, acquiring, from the user terminal in response to reading the predetermined code by the user terminal, payment identification information that identifies the payment and payment amount information that indicates an amount of the payment; In response to reading the predetermined code by the user terminal, presenting information of the plurality of payment service providers associated with the predetermined code to the user through the user terminal, and accepting a payment request from the user terminal designating one of the plurality of payment service providers to execute the payment process; When the payment request is received, transmitting a request for the payment process to a payment execution device corresponding to the payment business operator; Obtaining a processing result of the payment processing from a payment execution device corresponding to the payment business operator; storing payment result information in which the processing result is associated with the payment identification information and the payment amount information; A program to execute.
11. An information processing method in which a payment is made by reading a predetermined code associated with a plurality of payment service providers that are candidates for a payment service provider that executes a payment process, using an application installed on a user terminal used by a user making a payment, comprising: The computer acquiring, from the user terminal in response to reading the predetermined code by the user terminal, payment identification information that identifies the payment and payment amount information that indicates an amount of the payment; In response to reading the predetermined code by the user terminal, presenting information of the plurality of payment service providers associated with the predetermined code to the user through the user terminal, and accepting a payment request from the user terminal designating one of the plurality of payment service providers to execute the payment process; When the payment request is received, transmitting a request for the payment process to a payment execution device corresponding to the payment business operator; Obtaining a processing result of the payment processing from a payment execution device corresponding to the payment business operator; storing payment result information in which the processing result is associated with the payment identification information and the payment amount information; An information processing method comprising:
Citation Information
Patent Citations
Payment Codes for Enhanced Consumer Experience
JP2016522938A
Information processing program, information processing method, and information processing device
JP2020091763A
Information processing device, information processing method and program
JP2020187589A
Service management system, service management device, service management method, and program
JP2021033801A
MPM settlement system, user terminal, store business operator server, and program
JP2023012590A