WO2021199209A1 - サーバー装置、プログラム及び方法 - Google Patents

サーバー装置、プログラム及び方法 Download PDF

Info

Publication number
WO2021199209A1
WO2021199209A1 PCT/JP2020/014688 JP2020014688W WO2021199209A1 WO 2021199209 A1 WO2021199209 A1 WO 2021199209A1 JP 2020014688 W JP2020014688 W JP 2020014688W WO 2021199209 A1 WO2021199209 A1 WO 2021199209A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
information
payment
claimant
billing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2020/014688
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
敬三 藤原
リクリク ケイ
悦 張
亮佑 澤井
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Takeme
Takeme Co ltd
Original Assignee
Takeme
Takeme Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Takeme, Takeme Co ltd filed Critical Takeme
Priority to JP2021528367A priority Critical patent/JPWO2021199209A1/ja
Priority to PCT/JP2020/014688 priority patent/WO2021199209A1/ja
Publication of WO2021199209A1 publication Critical patent/WO2021199209A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Definitions

  • This disclosure relates to a server device, a program, and a method for settling billing content information requested by a claimant to a payer using a claimant terminal device.
  • a system that simplifies payment processing from a payer to a claimant using, for example, a two-dimensional bar code.
  • a two-dimensional bar code including transfer destination account identification information and a billing amount is generated on the claimant's mobile phone and displayed on the display unit, and the two-dimensional bar code is displayed on the payer's mobile phone.
  • a system is described in which payment is made by net banking based on the read transfer destination account specific information and the billed amount.
  • the present disclosure provides server devices, programs, and methods that are more convenient for payers and claimants by various embodiments.
  • a communication interface configured to send and receive predetermined information between a payer terminal device and a claimant terminal device communicably connected through a network, and a predetermined instruction.
  • the billing content information indicating the content to be billed from the claimant using the claimant terminal device to the payer using the payer terminal device, and the billing code information specifying the billing content information are provided. It is generated by receiving the billing content information from the claimant terminal device through the communication interface based on the memory configured to be stored and the instruction command stored in the memory, or the claimant.
  • the billing code information generated by the claimant terminal device and received through the communication interface is stored together with the billing content information in the memory or an external memory connected via the communication interface, and at least said.
  • the billing code information is transmitted to the billing terminal device, and the billing code information transmitted to the billing terminal device is transmitted to the billing terminal device via the communication interface, or the billing terminal device is transmitted. Notifies the claimant terminal device of the result of the payment process performed by reading the access information for accessing the place where the billing content information stored in advance is read in the payer terminal device.
  • a server device including a processor configured to perform processing for the above is provided.
  • a communication interface configured to send and receive predetermined information between a payer terminal device and a claimant terminal device communicably connected to each other through a network, and the above-mentioned claim. It is configured to store billing content information indicating the content to be billed from the claimant using the person terminal device to the payer using the payer terminal device, and billing code information specifying the billing content information.
  • the computer including the memory is generated by receiving the billing content information from the claimant terminal device through the communication interface, or is generated by the claimant terminal device by accepting input by the claimant.
  • the billing code information received through the communication interface is stored together with the billing content information in the memory or an external memory connected via the communication interface, and at least the billing code information is transmitted to the claimant terminal device, and the billing code information is transmitted to the claimant terminal device.
  • a place where the billing code information transmitted to the claimant terminal device and the billing content information transmitted to the claimant terminal device via the communication interface or stored in advance in the claimant terminal device are stored.
  • Provided is a program that functions as a processor configured to notify the claimant terminal device of the result of payment processing performed by reading the access information for accessing the payer terminal device. Will be done.
  • a communication interface configured to send and receive predetermined information between a payer terminal device and a claimant terminal device communicably connected to each other through a network, and a predetermined
  • billing content information indicating the content to be billed from the claimant using the claimant terminal device to the payer using the payer terminal device
  • billing code information specifying the billing content information.
  • the billing code information generated by the requester or generated by the claimant terminal device upon acceptance of input by the claimant and received through the communication interface is connected to the billing content information together with the billing content information via the memory or the communication interface.
  • a step of storing the billing code information in the external memory at least a step of transmitting the billing code information to the billing terminal device, the billing code information transmitted to the billing terminal device, and the billing via the communication interface. This was done by being transmitted to the person terminal device or by reading the access information for accessing the place where the billing content information stored in advance in the claimant terminal device is stored in the payer terminal device.
  • a method including a step of notifying the claimant terminal device of the result of the payment process and a method including the step are provided.
  • server devices, programs and methods that are more convenient for payers and claimants.
  • FIG. 1 is a conceptual diagram schematically showing the configuration of the payment system 1 according to the first embodiment of the present disclosure.
  • FIG. 2 is a block diagram showing an example of the configuration of the payment server device 100 according to the first embodiment of the present disclosure.
  • FIG. 3 is a block diagram showing an example of the configuration of the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 4A is a diagram conceptually showing a billing information table stored in the payment server device 100 according to the first embodiment of the present disclosure.
  • FIG. 4B is a diagram showing an example of a recording medium according to the first embodiment of the present disclosure.
  • FIG. 5 is a diagram showing a processing sequence executed in the payment system 1 according to the first embodiment of the present disclosure.
  • FIG. 6 is a diagram showing a processing flow executed in the payment server device 100 according to the first embodiment of the present disclosure.
  • FIG. 7 is a diagram showing a processing flow executed in the payment server device 100 according to the first embodiment of the present disclosure.
  • FIG. 8 is a diagram showing a processing flow executed in the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 9 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 10 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 11 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 11 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 12 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 13 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • FIG. 14 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the second embodiment of the present disclosure.
  • Systems according to various embodiments of the present disclosure primarily include server devices, payer terminal devices, claimant terminal devices and service server devices.
  • a billing content such as a billing amount
  • the server device for example, a two-dimensional bar code in which information capable of specifying the billing content is recorded is generated, and the generated two-dimensional bar code is transmitted to the claimant terminal device.
  • the claimant terminal device When it is received by the claimant terminal device, it is displayed, for example, on a display and read by the payer terminal device. Then, the settlement process proceeds based on the read information.
  • the claimant terminal device simply inputs the billing content and outputs the received two-dimensional bar code. Therefore, it is possible to proceed with a plurality of payment processes in parallel. Further, in the payer terminal device, it is possible to proceed with the payment process based on the information that can identify the billing content recorded in the two-dimensional bar code, so that it is not necessary to perform complicated input operations. Further, in the server device, since the progress of the payment process can be managed by the information that can specify the billing content, the payment history and the like can be efficiently managed. In addition, there are various payment service providers such as credit cards, bank transfers, and smartphone payments. By connecting the service server device operated by each provider and the payment server device, the claimant terminal device can be used. It is possible to proceed with the payment process even if it is not in a state where it can directly communicate with the service server device.
  • the system is used for payment processing with a server device, a claimant terminal device, and the like.
  • the payment system 1 will be described as an example of the system. However, this does not mean that the system is used only for payment purposes. That is, the system of the present disclosure and the payment system 1 described in the following embodiments may be any system that can be used for payment processing, and may naturally include a system having other uses and functions.
  • the server device is used for payment processing with a service server device, a claimant terminal device, and the like.
  • the payment server device 100 will be described as an example of the server device. However, this does not mean that the server device is used only for payment purposes. That is, the server device of the present disclosure and the payment server device 100 described in the following embodiments may be any server device that can be used for payment processing, and of course, the server device has other uses and functions. Can be included in.
  • the claimant terminal device is a terminal device that can be used by the claimant who makes a claim for money or the like to the payer.
  • various terminal devices such as a terminal device such as a cash register installed in a store, an operator device for operating a virtual store (online shopping), and a portable terminal device that can be carried by a claimant can be mentioned.
  • the claimant terminal device may be any terminal device that can be used by the claimant who makes a claim to the payer, and is not limited to a specific device such as a register.
  • the claimant means a person or an organization that can use the claimant terminal device, and does not mean only one specific individual.
  • the payer terminal device is a terminal device that can be used by the payer who has received a request from the claimant, although the detailed configuration thereof will be described later. Examples include smartphones and laptop computers, but the device is not limited to a specific device as long as it is a terminal device that can be used by the payer. Further, in the present disclosure, the payer means a person or an organization that can use the payer terminal device, and does not mean only one specific individual.
  • the service server device is used for the purpose of payment processing with the server device, the claimant terminal device, and the like.
  • the payment service server device 400 will be described as an example of the service server device. However, this does not mean that the service server device is used only for payment purposes. That is, the service server device of the present disclosure and the payment service server device 400 described in the following embodiments may be any service server device that can be used for payment processing, and are service server devices having other uses and functions. Of course, it can be included.
  • the program and method according to the present disclosure are executed by being processed by a server device or the like.
  • a payment program and a payment method will be described as an example of the program and method. However, these do not mean that the programs and methods are used solely for payment purposes. That is, the program and method of the present disclosure may be any program and method that can be used for payment processing, and are processed as a part of a program having another use or function, or a method having another use or function. It may be executed as part of.
  • FIG. 1 is a conceptual diagram schematically showing the configuration of the payment system 1 according to the first embodiment of the present disclosure.
  • the payment system 1 includes a payment server device 100, a claimant terminal device 200, a payer terminal device 300, and a payment service server device 400. Then, the payment server device 100 is communicably connected to each device through a network.
  • the claimant terminal device 200 and the payer terminal device 300 and the claimant terminal device 200 and the payment service server device 400 are directly communicable. ..
  • the payment server device 100 and the payment service server device 400 are described as a single one, each component and process can be distributed to a plurality of server devices and can be connected to various databases.
  • FIG. 2 is a block diagram showing an example of the configuration of payment server device 100 according to the first embodiment of the present disclosure.
  • the payment server device 100 does not need to include all of the components shown in FIG. 2, and may have a configuration in which some of the components are omitted, or other components may be added.
  • the payment server device 100 includes a RAM, a ROM, a memory 111 including a non-volatile memory, an HDD and the like, a processor 112 composed of a CPU and the like, an output interface 113, and a communication interface 114. Each of these components is then electrically connected to each other via a control line and a data line.
  • the database 115 that stores various information may be connected via the communication interface 114. That is, the payment server device 100 may or may not include the database 115.
  • the memory 111 includes a RAM, a ROM, a non-volatile memory, and an HDD, and functions as a storage unit.
  • the memory 111 stores instruction commands for executing the application or OS according to the present embodiment as a program. Such a program is loaded and executed by processor 312.
  • the memory 111 stores the billing information table shown in FIG.
  • the memory 111 (particularly RAM) is temporarily used to write and read data while the program is being executed by the processor 312.
  • the memory 111 particularly receives the billing content information indicating the content that the claimant charges the payer from the claimant terminal device 200 through the communication interface 114, and the billing code information for identifying the billing content information.
  • the process of generating the billing code information the process of associating the generated billing code information with the billing content information and storing it in the memory 111 or the database 115, the process of transmitting at least the billing code information to the claimant terminal device, and the process of transmitting the billing code information to the claimant terminal device 200.
  • a program for executing a process of notifying the claimant terminal device of the result of the payment process performed by reading the billing code information and the access information in the payer terminal device 300 is stored.
  • the processor 312 is composed of a CPU (microcomputer: microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 111.
  • the processor 312 receives the billing content information indicating the content that the claimant charges the payer from the claimant terminal device 200 through the communication interface 114, the billing code information for identifying the billing content information.
  • a process of notifying the claimant terminal device of the result of the settlement process performed by reading the billing code information and the access information in the payer terminal device 300 is executed.
  • the processor 312 may be configured by a single CPU, or may be configured by a plurality of CPUs.
  • the communication interface 114 is used, for example, in the system according to the present embodiment via a network with the claimant terminal device 200, the payer terminal device 300, and the payment service server device 400, or via a network with another server device. Performs processing such as modulation and demodulation in order to send and receive programs and various information.
  • the communication interface 114 communicates with each terminal device and other server devices according to the above-mentioned wireless communication method and known wired communication method.
  • information related to billing content information is received from the claimant terminal device 200 via the communication interface 114, and information such as billing code information, access information, and payment result information is sent to the claimant terminal device 200. Is sent.
  • a request for billing content information, a selected payment method, a payment result request, and the like are received from the payer terminal device 300 via the communication interface 114, and the payer ID information and payment service are received by the payer terminal device 300. Information such as information and payment result information is transmitted. Further, the payment result notification is received from the payment service server device 400 via the communication interface 114.
  • the output interface 113 functions as an information input / output unit for inputting / outputting information to / from various external devices such as a printer and a display.
  • the output interface 113 can adopt a known connection form such as a serial port, a parallel port, or USB, if desired.
  • FIG. 3 is a block diagram showing an example of the configuration of the payer terminal device 300 according to the first embodiment of the present disclosure.
  • the payer terminal device 300 does not need to include all of the components shown in FIG. 3, and may have a configuration in which some of the components are omitted, or other components may be added.
  • An example of the payer terminal device 300 is a portable terminal device capable of wireless communication represented by a smartphone.
  • any device that can execute the payment program according to the present disclosure such as a feature phone, a mobile information terminal, a PDA, a laptop personal computer, a desktop personal computer, a portable game machine, and a stationary game machine, will be used. However, it can be suitably applied.
  • the payer terminal devices 300 do not necessarily have to be the same or the same type.
  • one payer terminal device 300 may be a smartphone and the other payer terminal device 300 may be a laptop computer.
  • the payer terminal device 300 includes a display 311, a processor 112, a sensor 313 including a camera 314 and an infrared sensor 315, a communication interface 316 including a communication processing circuit 317 and an antenna, a RAM, a ROM, or a non-volatile memory. In some cases, it includes a memory 318 including HDD) and the like, an input interface 319 including a touch panel 320 and a hard key 321. Each of these components is then electrically connected to each other via a control line and a data line.
  • the display 311 reads out the image information stored in the memory 318 in response to the instruction of the processor 312, and various displays (for example, FIGS. 9 to 14 and the like) output by executing the program according to the present embodiment. It functions as a display unit that performs.
  • the display 311 is composed of, for example, a liquid crystal display, an organic EL display, electronic paper, or the like.
  • the input interface 319 is composed of a touch panel 320 and / or a hard key 321 and the like, and inputs a payer's instruction for execution of a program according to the present embodiment, that is, activation of a payment application, selection of a payment method, progress of payment processing, and the like.
  • the touch panel 320 is arranged so as to cover the display 311 and outputs position coordinate information corresponding to the image data displayed by the display 311 to the processor 312.
  • known methods such as a resistive film method, a capacitance coupling method, and an ultrasonic surface acoustic wave method can be used.
  • the touch panel 320 detects a swipe operation or a tap operation for each icon or the like displayed on the display 311 by the indicator.
  • the input interface 319 provided in the payer terminal device 300 is used, but it is also possible to use an input interface 319 connected wirelessly or by wire to a main body including a processor 312 or the like, for example, a mouse. Is.
  • the processor 312 is composed of a CPU (microcomputer: microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 318. Specifically, the processor 312 reads a program for executing the application according to the present embodiment and a program for executing the OS from the memory 318 and executes the program. In the present embodiment, the processor 312 activates the sensor 313 (eg, camera 314) based on the payer's instruction input received by the input interface 319, the claim received by the sensor 313 at the claimant terminal device. The process of reading the code information and the access information, the process of proceeding with the settlement for the billing content based on the read billing code information and the access information, and the like are executed.
  • the processor 312 may be configured by a single CPU, but may be configured by a plurality of CPUs. Further, other types of processors such as a GPU specialized in image processing may be appropriately combined.
  • the memory 318 is composed of a ROM, a RAM, a non-volatile memory, an HDD, etc., and functions as a storage unit.
  • the ROM stores instructions and instructions for executing the application and the OS according to the present embodiment as a program.
  • the RAM is a memory used for writing and reading data while the program stored in the ROM is being processed by the processor 312.
  • the non-volatile memory is a memory in which data is written and read by the execution of the program, and the data written here is saved even after the execution of the program is completed.
  • the memory 318 is, in particular, a process of activating the sensor 313 (eg, camera 314) based on the payer's instruction input received by the input interface 319, received by the sensor 313 at the claimant terminal device.
  • a program for reading the billing code information and the access information, and proceeding with the settlement for the billing content based on the read billing code information and the access information is stored.
  • the memory 318 stores information such as billing code information and access information read by the sensor 313, payer ID information received from the payment server device 100, payment service information, and payment result information at any time.
  • the communication interface 316 functions as a communication unit that transmits / receives information to / from a remote payment server device 100 or another terminal device via a communication processing circuit 317 and an antenna.
  • the communication processing circuit 317 performs a process for receiving a program, various information, and the like used in the system according to the present embodiment from the payment server device 100 and the payment service server device 400 according to the progress of the payment processing.
  • a request for billing content information, a selected payment method, a payment result request, and the like are transmitted to the payment server device 100 via the communication interface 316, and the payment server device 100 sends a payer ID.
  • Information such as information, payment service information, and payment result information is received.
  • a payment request is transmitted to the payment service server device 400 via the communication interface 316, and a payment end notification is received from the payment service server device 400.
  • the communication processing circuit 317 is processed based on a wideband wireless communication system represented by the LTE system, but has a narrow band such as a wireless LAN represented by IEEE802.11 or Bluetooth®. It is also possible to process based on the method related to wireless communication. It is also possible to use wired communication instead of or in addition to wireless communication.
  • the sensor 313 is composed of a camera 314, an infrared sensor 315, and the like, and functions as a detection unit that detects an image such as a billing code information output from the claimant terminal device 200 and a two-dimensional code in which a storage location is recorded.
  • the camera 117 includes an image sensor such as a CCD image sensor or a CMOS image sensor, and captures an image such as a two-dimensional bar code. The captured image is analyzed by a known method by the processor 112, the information recognized from the image is read, and the billing code information and the recording location information recorded on the two-dimensional bar code are read.
  • the infrared sensor 315 is also used to capture an image such as a billing code information and a one-dimensional barcode in which a storage location is recorded and read the recorded information, similarly to the camera 314.
  • any sensor that can read the recording medium on which the information is recorded may be used, and it is not always necessary to include both the camera 314 and the infrared sensor 315.
  • the recording medium may be any recording medium as long as it can be read by the sensor 313. That is, in the following description, a case where a two-dimensional bar code is used as a recording medium will be described, but the present invention is not limited to this, and various recording media such as a one-dimensional bar code and a three-dimensional bar code can be used. ..
  • FIG. 4A is a diagram conceptually showing a billing information table stored in the payment server device 100 according to the first embodiment of the present disclosure.
  • the table when billing content information is received from the billing terminal device 200 from the payment server device 100, when a billing content request is received from the payer terminal device 300, the payment result is settled from the payment service server device 400.
  • the received information is stored in association with the billing code information.
  • the case where the billing information table is stored in the payment server device 100 will be described, but even if the table is stored in the database communicably connected to the payment server device 100 via the network. good.
  • the payment server device 100 temporarily reads and processes these information stored in the database into the memory 111 in the payment server device 100 at any time as the processing progresses.
  • the billing content information, the payer ID information, and the payment result information are stored in the billing information table in association with the billing code information.
  • the "billing code” information is generated by the control of the processor 112 of the payment server device 100 when the billing content information is received from the claimant terminal device 200, and is unique information given for each received billing content information. This is information for specifying the content information.
  • the "billing content” information is information indicating the content that the claimant charges the payer, and is generated by accepting the input by the claimant in the claimant terminal device 200.
  • the invoice amount may include at least information related to the invoice amount, and if necessary, information such as the name of the store that is the invoice, the time when the invoice was issued, the breakdown, the tax amount, the name of the purchased item, and the name of the payer. good.
  • the "payer ID” information is generated by the control of the processor 112 of the payment server device 100 by receiving the billing content request including the billing code information from the payer terminal device 300, and the payer terminal device 300 that transmits the information is generated. It is the information specific to the payer to be used and is the information for identifying the payer.
  • the "payment result” information is information generated in the payment service server device 400 after the payment processing is performed in the payment service server device 400, and is information indicating whether or not the payment is normally completed.
  • the billing code information is generated by the control of the processor 112 of the payment server device 100, but may be generated by the control of the processor of the claimant terminal device 200, for example.
  • the billing code information unique to the billing content information received by the processor of the claimant terminal device 200 is generated.
  • the billing code information is also transmitted.
  • the payment server device 100 stores the received billing code information in the billing information table.
  • the payer ID information is generated by the control of the processor 112 of the payment server device 100 by receiving the billing content request.
  • the payer registered in advance provides the service by the payment system 1 of the present embodiment. It may be granted by logging in to.
  • FIG. 4B is a diagram showing an example of a recording medium according to the first embodiment of the present disclosure.
  • the recording medium is generated by receiving the billing content information from the claimant terminal device 200 in the payment server device 100, and is transmitted to the claimant terminal device 200.
  • a two-dimensional bar code is used as the recording medium, but the recording medium is not limited to this, and various recording media such as a one-dimensional bar code and a three-dimensional bar code can be used.
  • the two-dimensional bar code receives billing code information (“Q1” in the example of FIG. 4B) generated by the payment server device 100 and stored in the memory 111 and received from the claimant terminal device 200. Access information for accessing the place where the billing content information and the like are stored, that is, address information indicating the access destination of the payment server device 100 (“xxxxxx” in the example of FIG. 4B) is recorded.
  • the recording medium can also be generated by the claimant terminal device 200.
  • the access information is received from the payment server device 100 in advance and stored in the memory of the claimant terminal device 200. Then, after the billing code information is generated in the payment server device 100 and received in the billing terminal device 200, or after the billing code information is generated in the billing terminal device 200, the billing is made by the processor of the billing terminal device 200. A recording medium on which code information and access information are recorded is generated.
  • FIG. 5 is a diagram showing a processing sequence executed in the payment system 1 according to the first embodiment of the present disclosure. Specifically, FIG. 5 is a diagram showing processing sequences of various processes executed between the payment server device 100, the claimant terminal device 200, the payer terminal device 300, and the payment service server device 400.
  • the processing sequence is started by receiving an instruction input by the claimant in the claimant terminal device 200 (S11). Specifically, the claimant terminal device 200 receives input of billing content information including the billing amount by the claimant via the input interface. After that, the claimant terminal device 200 transmits the input billing content information (T11) to the payment server device 100 via the communication interface.
  • the payment server device 100 that has received the billing content information generates billing code information that is unique to the received billing content information and that identifies the information (S12).
  • the payment server device 100 stores the received billing content information in the billing information table in association with the generated billing code information (S13). Then, the payment server device 100 shows the stored billing code information and the access information for accessing the place where the billing content information and the like are stored, that is, the address information indicating the access destination of the payment server device 100, as shown in FIG. 4B. It records on a recording medium (T12) and transmits this to the claimant terminal device 200.
  • the claimant terminal device 200 that has received the recording medium outputs the received recording medium (S14).
  • the claimant terminal device 200 and the payer terminal device 300 do not necessarily have to be communicably connected through a network. Therefore, the claimant terminal device 200 outputs the received recording medium by displaying it on the display included in the claimant terminal device 200.
  • the example of this output is an example, and it is also possible to print and output on a paper medium by the printer included in the claimant terminal device 200.
  • the payer terminal device 300 reads the recording medium output from the claimant terminal device 200 by the sensor 313 (S15). Then, the payer terminal device 300 acquires the billing code information and the access information recorded on the recording medium, and includes the billing code information in the access destination (that is, the payment server device 100) specified based on the access information.
  • the billing content request (T13) is transmitted.
  • the request includes billing code information for specifying billing content information in the payment server device 100 as described above, but identifies the payer who uses the payer terminal device 300 or the payer terminal device 300. Specific information for the purpose may be included as appropriate.
  • the payment server device 100 that has received the billing content request generates payer ID information for identifying the payer who uses the transmitted payer terminal device (S16), and the billing code received in the billing information table of the memory 111. Store in association with information. (S17). Then, the payment server device 100 transmits the generated payer ID information (T14) to the payer terminal device 300 so that the payer can select the billing content information and the payment method.
  • the payer terminal device 300 that has received the payer ID information displays a selection screen on the display based on the received billing content information, information for selecting a payment method, and the like. Then, the payer terminal device 300 accepts the selection of the payment method desired by the payer from the payment methods provided by various payment service providers such as credit card, bank transfer, and smartphone payment (S18), and indicates the selected payment method.
  • the payment method information (T15) is transmitted to the payment server device 100.
  • the payment server device 100 that has received the payment method information generates payment service information according to the payment method (S19). As an example, information such as address information indicating the access destination of the payment service provided by the payment service provider and a request to start the payment application provided by the payment service provider is generated according to the selected payment method. .. Then, the payment server device 100 transmits the generated payment service information (T16) to the payer terminal device 300.
  • the payer terminal device 300 that has received the payment service information performs payment processing based on the screen displayed based on the received payment service information (S20).
  • the payment service information As an example, when credit card payment is selected, the credit card number input is accepted on the credit card number input screen.
  • smartphone payment is selected, the smartphone payment application is started, the payment confirmation screen is displayed, and the payment instruction from the payer is accepted. Then, the payer terminal device 300 transmits payment request information (T17) including at least the billing code information read in S15 in response to the acceptance of the instruction input from the payer.
  • the payment service server device 400 that has received the payment request information receives the request and proceeds with the payment process (S21). Then, the payment service server device 400 transmits the payment result information (T18) including the processing result and the billing code information to the payment server device 100. At the same time, the payment service server device 400 transmits a payment end notification (T19) indicating that the payment process has been completed to the payer terminal device 300.
  • the payment server device 100 that has received the payment result information stores the payment result information included in the received payment result information in the billing information table of the memory 111 in association with the received billing code information (S22).
  • the payer terminal device 300 that has received the payment end notification is controlled to access the payment server device 100 based on the access information indicating the access destination of the payment server device 100 included in the received payment end notification (S23). ). Then, the payer terminal device 300 transmits a payment result request (T20) including billing code information to the payment server device 100.
  • the payment server device 100 that has received the payment result request refers to the billing information table and acquires the payment result information based on the billing code information included in the payment result request (S24). Then, the payment server device 100 transmits the acquired payment result information (T21) to the claimant terminal device 200 and the payer terminal device 300, respectively.
  • the claimant terminal device 200 and the payer terminal device 300 that have received the payment result information output the received payment results to each display or the like (S25 and S26). Then, for example, the claimant who uses the claimant terminal device 200 browses the result information displayed on the display of the payer terminal device 300, and the payer who also uses the payer terminal device 300 similarly browses the result information displayed on the display of the payer terminal device 300. By viewing the result information displayed on the display of, both parties can confirm that the payment has been completed normally. This ends this processing sequence.
  • the payment server device 100, the biller terminal device 200, the payer terminal device 300, and the payment service server device 400 use common billing code information in one billing / payment processing to make various information and requests. It is transmitted and the information is stored in the billing information table of the payment server device 100. Therefore, even if different billing / settlement processing is performed at the same time or at the same time, different billing code information is given and management is performed based on the billing code information, so that a plurality of billing / settlement processing can be efficiently executed. Is possible.
  • information is transmitted between the claimant terminal device 200 and the payer terminal device 300 via the recording medium. Therefore, it is not necessary that the two are connected in a communicable state in advance, and it is possible to save the trouble of both.
  • the payment server device 100 sends and receives information to and from each payment service provider that provides these methods. Therefore, it is not necessary to construct a complicated system such that the claimant terminal device 200 communicates with each payment service provider individually. Further, since the payer terminal device 300 reads the billing code information and the like via the recording medium, it is not necessary for the payer to input such information each time, and the time and effort of the payer can be saved.
  • FIG. 5 describes the case where the billing code information is generated by the payment server device 100 in S12, but as described in FIG. 4A, the billing code information is generated by the claimant terminal device 200. You may.
  • the billing content information is transmitted from the claimant terminal device 200 to the payment server device 100, and the billing code information generated together with the billing content information is transmitted.
  • the payer ID information is generated by the control of the processor 112 of the payment server device 100 by receiving the billing content request.
  • a pre-registered payer performs the present implementation. It may be granted by logging in to the service provided by the payment system 1 of the form.
  • the recording medium (T12) generated by the payment server device 100 is received and then the recording medium is output.
  • the claimant terminal device 200 is at the timing when the billing code information is generated in the claimant terminal device 200 or when the billing code information is received from the payment server device 100 instead of the recording medium of T12.
  • a recording medium may be generated and output.
  • the recording medium is typically output via the display, printer, or the like of the claimant terminal device 200. Therefore, the claimant terminal device 200 and the payer terminal device 300 do not necessarily have to be communicably connected to each other through the network in advance.
  • the present invention is not limited to this, and both terminal devices may be connected in a communicable manner, or billing code information or access information may be transmitted to the payer terminal device 300 via the payment server device 100.
  • the payment result is transmitted from the payment server device 100 to the claimant terminal device 200 and the payer terminal device 300 by receiving the payment result request (T20).
  • the payment result may be transmitted from the payment service server device 400 to each terminal device.
  • the payment result request is transmitted from the payer terminal device 300 after the processing of S23 is completed, but the subject and timing of transmitting the request may be any.
  • the claimant terminal device 200 may transmit the settlement result request at the timing when the instruction input for the display of the bill list screen for which the settlement process is performed is received in the claimant terminal device 200.
  • the payment result request may be transmitted from the payer terminal device 300 at the timing when the instruction input for the display of the list screen of the payment process performed by the payer terminal device 300 is received.
  • FIG. 6 is a diagram showing a processing flow executed by the payment server device 100 according to the first embodiment of the present disclosure. Specifically, it is a processing flow performed by the payment server device 100 in S11 to S14 in the processing flow of FIG. The processing flow is performed by the processor 112 of the payment server device 100 reading and executing the program stored in the memory 111 at a predetermined cycle.
  • the processor 112 first determines whether or not the billing content information has been received from the claimant terminal device 200 via the communication interface 114 (S101).
  • the billing content information includes information indicating the content that the claimant charges the payer.
  • the billing content information includes at least information related to the billing amount, and if necessary, the name of the store that is the claimant, the time when the invoice was issued, the breakdown, the tax amount, the name of the purchased item, and the name of the payer. Information such as may be included.
  • the processor 112 when the processor 112 receives the billing content information, the processor 112 generates billing code information which is a unique identification code for the billing content information (S102).
  • this billing code information an arbitrary character string may be generated each time, or a terminal identification number may be received from the claimant terminal device 200 and generated using the number. That is, any format may be used as long as the individual billing content information can be identified.
  • the processor 112 stores the billing code in the billing information table, and also stores the billing content information received in association with the stored billing code information in the billing information table (S103). ..
  • the processor 112 When each information is stored in the billing information table, the processor 112 indicates the stored billing code information and the access information for accessing the place where the information is stored, that is, the address indicating the access destination of the payment server device 100. A process of reading out information and recording it on a recording medium is performed (S104). Then, the processor 112 transmits the recording medium on which these information is recorded to the claimant terminal device 200 that has transmitted the billing content information (S105). As a result, the processing flow ends.
  • FIG. 7 is a diagram showing a processing flow executed in the payment server device 100 according to the first embodiment of the present disclosure. Specifically, it is a processing flow performed by the payment server device 100 in S15 to S26 in the processing flow of FIG. The processing flow is performed by the processor 112 of the payment server device 100 reading and executing the program stored in the memory 111 at a predetermined cycle.
  • the processor 112 determines whether or not the billing content request is received from the payer terminal device 300 via the communication interface 114 (S201).
  • the billing content request includes at least billing code information recorded on a recording medium read by the payer terminal device 300.
  • the processor 112 generates payer ID information unique to the payer who uses the payer terminal device 300 that has transmitted the request.
  • the payer ID information may be generated from an arbitrary character string by the processor 112 each time a request is made, or the terminal identification number of the payer terminal device or the like may be used. Further, if the payer has performed the payment process in the past, the process can be omitted by transmitting the payer ID information already generated together with the billing code information from the payer terminal device. Then, the processor 112 stores the generated payer ID information in the billing information table in association with the received billing code information.
  • the processor transmits the generated payer ID information to the payer terminal device 300 that has sent the billing content request (S204).
  • the payment server device 100 transmits the information to the payer terminal device 300 so that the payer can select the billing content information and the payment method.
  • the payment method selection screen is displayed on the payer terminal device 300, and the billing amount and the like can be automatically input.
  • the processor 112 determines whether or not the payment method information indicating the payment method selected by the payer has been received from the payer terminal device 300 (S205).
  • the processor 112 generates payment service information (S206).
  • the payment server device 100 or the database 115 connected to the payment server device 100 is associated with the payment method ID information that specifies the payment method in advance, and the payment is provided by the payment service provider.
  • the address information of the access destination of the service, the activation request information of the payment application provided by the payment service provider, etc. are stored.
  • the processor 112 refers to the information stored based on the received payment method (that is, the payment method ID information), and generates the payment service information necessary for the payment process.
  • the processor 112 transmits the generated payment service information to the payer terminal device 300 that has transmitted the payment method information (S207).
  • the processor 112 determines whether or not the payment result information including the billing code information has been received from the payment service server device 400 (S208).
  • the payment result information includes billing code information and information indicating the result of payment processing performed between the payer terminal device 300 and the payment service server device 400. Then, when the payment result information is received, the processor 112 stores the received payment result information in the billing information table in association with the billing code information (S209).
  • the processor 112 determines whether or not the payment result request has been received from the payer terminal device 300 (S210).
  • the payment result request includes billing code information. Therefore, when the request is received, the processor 112 refers to the billing information table and acquires the settlement result information based on the received billing code information (S211). Then, the processor 112 transmits the acquired payment result information to the claimant terminal device 200 and the payer terminal device 300 (S212). As a result, the processing flow ends.
  • FIG. 8 is a diagram showing a processing flow executed by the payer terminal device 300 according to the first embodiment of the present disclosure. Specifically, in the processing flow of FIG. 5, it is a processing flow performed by the payer terminal device 300. The processing flow is performed by the processor 312 of the payer terminal device 300 reading and executing the program stored in the memory 318.
  • the claimant terminal device 200 when the claimant terminal device 200 receives the recording medium in which the billing code information and the access information are recorded from the payment server device 100, the claimant terminal device 200 outputs the received recording medium.
  • the received recording medium is displayed on the display so that the payer can see it.
  • the claimant terminal device 200 includes a printer, the recording medium received by the printer is printed on paper. The paper on which the recording medium is printed is handed to the payer and made available to the payer.
  • the processor 312 activates the payment application based on the instruction input received via the input interface 319 (S301). Then, when the input interface 319 receives an instruction input for selecting the scan menu of the recording medium on the menu screen after the payment application is started, the processor 312 activates the sensor 313 (camera 314 in the present embodiment). The scan screen of the recording medium is displayed on the display 311 (S302).
  • FIG. 9 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure.
  • S302 of FIG. 8 an example of a recording medium scan screen displayed on the display 311 when the processor 312 activates the sensor 313 is shown.
  • the sensor image display area 20 of the display 311 is displayed, and the image scanned by the sensor 313 is displayed in the area in real time.
  • a frame 25 as an index for reading the recording medium satisfactorily is displayed, and the payer can display the recording medium in the frame 25 so that the payer terminal device 300 Move the position of.
  • the sensor 313 adjusts the focal position and the like of the image captured in the sensor 313, and automatically stores the image as a recording medium image in the memory 318 when a good image is captured. Then, the processor 312 analyzes the stored recording medium image, reads the information recorded in the recording medium, and stores the acquired billing code information and access information in the memory 318.
  • the processor 312 transmits the billing content request including the billing code read from the recording medium to the location specified based on the read access information, that is, the payment server device 100 as the access destination ( S303).
  • the processor 312 transmits the payer ID information, the billing content information, and the payment method generated in the payment server device 100 to the payer terminal device 300 so that the payer can select the payment method.
  • the payer terminal device 300 stores the received information in the memory 318 (S304), and then displays the payment method selection screen on the display 311 based on the information for selecting the payment method and the like (S304). Then, on the screen, the processor 312 accepts the input of the payer via the input interface 319 and selects the payment method desired by the payer (S305). Then, when the payment method is selected, the processor 312 transmits the payment method information including the selected payment method and the billing code information to the payment server device 100 (S306).
  • FIG. 10 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure. Specifically, in S305 and S306 of FIG. 8, an example of a payment method selection screen for accepting a payment method selection by a payer is shown. According to FIG. 10, the selection screen includes the access location display area 21, and information indicating the location where the area was accessed in S303, that is, the payment server device 100 is displayed. In addition, one or more payment method icons 12 for selecting a payment method are displayed on the selection screen, and the payer taps on the icon corresponding to the desired payment method to select the payment method. It becomes possible to select.
  • FIG. 11 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure. Specifically, an example of a payment method confirmation screen for selecting a payment method on the payment method selection screen of FIG. 10 and confirming the selection is shown.
  • the confirmation screen includes the access location display area 21, and information indicating the location where the area was accessed in S303, that is, the payment server device 100 is displayed.
  • a billing amount display area for the payer to enter the billing amount is displayed, and the payer can enter the billing amount via the input interface 319. It should be noted that the amount can be automatically entered when the billing content information has been received.
  • the confirmation screen includes the coupon selection area 23, and the payer can select a desired coupon that can be used by tapping the icon of the lower triangle of the area.
  • the confirmation screen includes the payment method display area 24, and the payment method selected on the payment method selection screen of FIG. 10 is displayed. By tapping the lower triangle icon in the area, the payment method selection screen of FIG. 10 can be returned and the payment method can be selected again. Further, a settlement confirmation icon 13 and a cancellation icon 14 are displayed on the confirmation screen.
  • the payment method displayed in the payment method display area 24 is transmitted to the payment server device 100 as payment method information.
  • the series of payment processes can be canceled.
  • the processor 312 receives the payment service information from the payment server device 100 (S307), and stores the received payment service information in the memory 318.
  • the payment service information the address information of the access destination of the payment service provided by the payment service provider and the activation of the payment application provided by the payment service provider corresponding to the payment method selected in S305 and transmitted in S306. Includes request information and so on.
  • the payment service server device 400 operated by the payment service provider is accessed, the payment application is started, and the payment screen is displayed (S308).
  • the processor 312 accepts the instruction input of the payer according to the procedure displayed on the payment screen, and proceeds with the payment process in the payer terminal device 300 (S309).
  • the processor 312 transmits a payment request including the billing code information to the payment service server device 400 (S310).
  • FIG. 12 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure. Specifically, an example of the payment screen displayed in S308 to S310 of FIG. 8 is shown. According to FIG. 12, the payment screen displayed by activating the payment application of the "A Pay service" is displayed based on the payment service information received in S308 of FIG. On the payment screen, in addition to the display 17 such as the billing amount input based on the billing content information, the balance charged in advance when using the service is displayed. Then, if there is no mistake in the contents displayed on the payment screen, the payer taps the payment icon 18 to send the payment request including the billing code to the payment service server device 400. ..
  • the processor 312 when the processor 312 receives the payment end notification indicating that the payment process has been completed from the payment service server device 400 (S311), the processor 312 is based on the access information of the payment server device 100 included in the notification.
  • the payment server device 100 is accessed and controlled to send a payment result request (S312).
  • the payment result request includes billing code information. Therefore, in the payment server device 100, the payment result information stored in the billing information table is referred to based on the billing code information, and the specified payment result information is transmitted to the payer terminal device 300 and the biller terminal device 200. Send.
  • the processor 312 of the payer terminal device 300 receives the payment result information, it stores it in the memory 318 (S313) and displays the received payment result information on the display 311 (S314). As a result, the processing flow ends.
  • FIG. 13 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the first embodiment of the present disclosure. Specifically, an example of the payment result information display screen displayed in S314 of FIG. 8 is shown. According to FIG. 13, the display screen includes the access location display area 21, and information indicating the access location included in the notification received in S311, that is, the payment server device 100 is displayed in the area. Further, on the display screen, various information 19 such as the amount settled is displayed based on the billing content information specified by the settled billing code information. In addition, the display screen is displayed to urge the claimant who uses the claimant terminal device 200 to show the screen.
  • the payment result information is transmitted to the claimant terminal device 200, and the payment result information can be output via the display or printer of the claimant terminal device 200. Then, the claimant terminal device 200 displays a display prompting the payer who uses the payer terminal device 300 to show the output payment result information. Therefore, it becomes possible for the claimant and the payer to confirm the payment result information received by each other, and it is possible to execute the payment processing reliably.
  • the payment server device 100, the claimant terminal device 200, the payer terminal device 300, and the payment service server device 400 use various billing code information in one billing / payment processing.
  • Information and requests are transmitted, and the information is stored in the billing information table of the payment server device 100. Therefore, even if different billing / settlement processing is performed at the same time or at the same time, different billing code information is given and management is performed based on the billing code information, so that a plurality of billing / settlement processing can be efficiently executed. Is possible.
  • information is transmitted between the claimant terminal device 200 and the payer terminal device 300 via the recording medium. Therefore, it is not necessary that the two are connected in a communicable state in advance, and it is possible to save the trouble of both.
  • FIG. 14 is a diagram showing an example of a screen displayed on the payer terminal device 300 according to the second embodiment of the present disclosure.
  • the payment method confirmation screen shown in FIG. 11 it is an example of a claimant confirmation screen that transitions after receiving the input of the payer for the payment confirmation icon 13.
  • Information such as the payment method selected by the payer, the usage status of the coupon, and the payment amount is displayed on the claimant confirmation screen, and the claimant can confirm the payment details through the screen.
  • the requester approval icon 15 and the cancel icon 16 are displayed on the confirmation screen.
  • the processor 312 controls to transmit the selected payment method information to the payment server device 100. (S306 in FIG. 8).
  • the cancel icon 16 is clicked, the claimant can cancel the series of payment processes by himself / herself.
  • the payment server device 100, the claimant terminal device 200, the payer terminal device 300, and the payment service server device 400 use various billing code information in one billing / payment processing.
  • Information and requests are transmitted, and the information is stored in the billing information table of the payment server device 100. Therefore, even if different billing / settlement processing is performed at the same time or at the same time, different billing code information is given and management is performed based on the billing code information, so that a plurality of billing / settlement processing can be efficiently executed. Is possible.
  • information is transmitted between the claimant terminal device 200 and the payer terminal device 300 via the recording medium. Therefore, it is not necessary that the two are connected in a communicable state in advance, and it is possible to save the trouble of both.
  • the payment server device 100 sends and receives information to and from each payment service provider that provides these methods. Therefore, it is not necessary to construct a complicated system such that the claimant terminal device 200 communicates with each payment service provider individually. Further, since the payer terminal device 300 reads the billing code information and the like via the recording medium, it is not necessary for the payer to input such information each time, and the time and effort of the payer can be saved.
  • ⁇ Others> In any of the embodiments, a case where a recording medium such as a two-dimensional bar code is used for reading the billing code information has been described. However, without using a recording medium, information such as billing code information is transmitted to the claimant terminal device 200, and the claimant terminal device 200 outputs the billing code information itself and the like. Then, in the payer terminal device 300, the output billing code information may be directly input via the input interface 319.
  • the processes and procedures described herein can be realized not only by those explicitly described in the embodiments, but also by software, hardware or a combination thereof. Specifically, the processes and procedures described in the present specification are realized by implementing logic corresponding to the processes on a medium such as an integrated circuit, a volatile memory, a non-volatile memory, a magnetic disk, or an optical storage. Will be done. Further, the processes and procedures described in the present specification can be implemented as computer programs and executed by various computers including a terminal device and a server device.
  • Payment server device 100 Payment server device 200 Claimor terminal device 300 Payer terminal device 400 Payment service server device

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
PCT/JP2020/014688 2020-03-30 2020-03-30 サーバー装置、プログラム及び方法 Ceased WO2021199209A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2021528367A JPWO2021199209A1 (https=) 2020-03-30 2020-03-30
PCT/JP2020/014688 WO2021199209A1 (ja) 2020-03-30 2020-03-30 サーバー装置、プログラム及び方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/014688 WO2021199209A1 (ja) 2020-03-30 2020-03-30 サーバー装置、プログラム及び方法

Publications (1)

Publication Number Publication Date
WO2021199209A1 true WO2021199209A1 (ja) 2021-10-07

Family

ID=77929819

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/014688 Ceased WO2021199209A1 (ja) 2020-03-30 2020-03-30 サーバー装置、プログラム及び方法

Country Status (2)

Country Link
JP (1) JPWO2021199209A1 (https=)
WO (1) WO2021199209A1 (https=)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012216155A (ja) * 2011-04-01 2012-11-08 Japan Research Institute Ltd 決済サーバおよび決済システム
JP2017111835A (ja) * 2012-07-31 2017-06-22 エヌ・ティ・ティ・インターネット株式会社 決済サーバ、決済システム、及びプログラム
JP2019159676A (ja) * 2018-03-12 2019-09-19 国立研究開発法人産業技術総合研究所 伝票管理システム及び伝票管理装置
JP2019215687A (ja) * 2018-06-12 2019-12-19 株式会社アベニューディー 情報処理方法
JP2020009198A (ja) * 2018-07-09 2020-01-16 トッパン・フォームズ株式会社 決済システム、決済情報管理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012216155A (ja) * 2011-04-01 2012-11-08 Japan Research Institute Ltd 決済サーバおよび決済システム
JP2017111835A (ja) * 2012-07-31 2017-06-22 エヌ・ティ・ティ・インターネット株式会社 決済サーバ、決済システム、及びプログラム
JP2019159676A (ja) * 2018-03-12 2019-09-19 国立研究開発法人産業技術総合研究所 伝票管理システム及び伝票管理装置
JP2019215687A (ja) * 2018-06-12 2019-12-19 株式会社アベニューディー 情報処理方法
JP2020009198A (ja) * 2018-07-09 2020-01-16 トッパン・フォームズ株式会社 決済システム、決済情報管理方法

Also Published As

Publication number Publication date
JPWO2021199209A1 (https=) 2021-10-07

Similar Documents

Publication Publication Date Title
US11995626B2 (en) Expedited point-of-sale merchant payments
AU2018202908B2 (en) Controlling Access Based on Display Orientation
CN104603811B (zh) 匹配用于代理卡交易的付款票据的退款
EP2634737A1 (en) Payment transaction receipt system and method
WO2014162296A1 (en) Method and system for conducting pre-authorized financial transactions
JP5238229B2 (ja) 口座振替受付システム、受付装置、端末装置、及び、コンピュータプログラム
US12430622B2 (en) Cryptocurrency payment support apparatus, cryptocurrency payment support system, cryptocurrency payment support method, and non-transitory recording medium
WO2014155664A1 (ja) Ｉｄ管理装置、ｉｄ管理方法、およびｉｄ管理プログラム
JP2010039619A (ja) 収納システム、決済装置、及び、コンピュータプログラム
JP5433868B2 (ja) 電子決済システム
JP6857205B2 (ja) 決済管理装置、決済管理方法および端末
JP5672691B2 (ja) 携帯端末装置、支払い媒体選択方法及び支払い媒体選択プログラム
CN112785296B (zh) 钱包系统以及非临时性存储介质
JP2023131097A (ja) 情報処理装置、情報処理方法、およびプログラム
JP7673917B2 (ja) 決済統合装置、決済統合方法、および、決済統合プログラム
US20220058616A1 (en) Method for voice tagging an electronic receipt acquired after a transaction
WO2021199209A1 (ja) サーバー装置、プログラム及び方法
JP2021117897A (ja) 支援システム、プログラム
JP7015813B2 (ja) 送金システム、送金方法、及びプログラム
KR102033576B1 (ko) 전자 결제 시스템, 장치 및 방법
US20220051253A1 (en) Methods for remote transaction receipt capture based on evidence of a transaction in progress
US20230087986A1 (en) Inserting code into a document object model of a graphical user interface to enable sub-exchanges
WO2022009963A1 (ja) 情報処理装置、情報処理方法、プログラムおよび情報処理システム
US20220058612A1 (en) Method of electronic receipt capture for real-time transacted expenditures
KR20210147934A (ko) 결제 시스템, 결제 프로그램을 기록한 컴퓨터 판독 가능한 기록 매체 및 결제 서버

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021528367

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20928435

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04/01/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20928435

Country of ref document: EP

Kind code of ref document: A1