WO2023033217A1 - Procédé de fonctionnement pour fournir des informations de processus de paiement, et dispositif électronique prenant en charge ledit procédé - Google Patents

Procédé de fonctionnement pour fournir des informations de processus de paiement, et dispositif électronique prenant en charge ledit procédé Download PDF

Info

Publication number
WO2023033217A1
WO2023033217A1 PCT/KR2021/012198 KR2021012198W WO2023033217A1 WO 2023033217 A1 WO2023033217 A1 WO 2023033217A1 KR 2021012198 W KR2021012198 W KR 2021012198W WO 2023033217 A1 WO2023033217 A1 WO 2023033217A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
payment
information
identification information
transaction
Prior art date
Application number
PCT/KR2021/012198
Other languages
English (en)
Korean (ko)
Inventor
양정권
한강수
박선영
박현식
윤찬미
이거성
김가연
Original Assignee
쿠팡 주식회사
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 쿠팡 주식회사 filed Critical 쿠팡 주식회사
Publication of WO2023033217A1 publication Critical patent/WO2023033217A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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

Definitions

  • the present invention relates to a method and apparatus for providing payment processing information, and more particularly, to a method and electronic device for providing information related to the processing of a transaction for a user's payment order.
  • an electronic device providing payment processing information may provide information related to transaction processing for a user's payment order.
  • Various embodiments may provide an operating method of an electronic device for providing payment processing information and an electronic device supporting the same.
  • a method for providing payment processing information by an electronic device comprising: checking information on a first transaction for a user in a service provided by the electronic device; obtaining information on one or more first payment domains corresponding to a payment procedure for processing the first transaction; For a first domain included in the one or more first payment domains, first transaction identification information for the first transaction, first identification information for the first domain, and second information for a previous domain of the first domain. Generating first payment processing information including identification information; and providing the first payment processing information.
  • the payment processing information providing method may include, when a difference in settlement amount occurs between the service and a payment service related to an external operator corresponding to a payment method used in the service, a first step corresponding to the difference in settlement amount. 2 determining the transaction; checking second transaction identification information for the second transaction; identifying one or more second payment domains corresponding to a payment procedure for processing the second transaction, based on the second transaction identification information; checking state information indicating whether third identification information for a previous domain of the second domain is included in second payment processing information generated for a second domain included in the one or more second payment domains; and providing the state information.
  • the payment processing information providing method may, when the third identification information is not included in the second payment processing information, assign the second domain and the previous domain of the second domain to the settlement amount difference. Determining a corresponding error-occurring domain; and providing error resolution information corresponding to the error generating domain.
  • the status information may be generated for the second payment processing information based on the fact that processing of the second transaction is completed.
  • the one or more first payment domains may be determined based on a payment method of the user for the first transaction.
  • the first transaction identification information may include information about the type of service.
  • the first transaction identification information may be commonly included in payment processing information for each of the one or more first payment domains.
  • the first payment processing information may include information about a date corresponding to the first transaction and information about an amount corresponding to the first transaction.
  • the first payment processing information may include fourth identification information for a domain following the first domain.
  • the one or more first payment domains when a first payment order for the first transaction is performed based on a first payment method of the user preset in the service, the first payment A service domain for processing first approval information for confirming approval on the service for an order, when the first approval information is processed, for confirming approval on the first payment method for the first payment order A payment method domain for processing the second approval information, and when the second approval information is processed, a method for checking whether the first payment order is approved for a payment service related to an external operator corresponding to the first payment method.
  • 3 may include an external operator connection domain for processing approval information, and an external operator domain corresponding to the payment service for receiving information on the first payment order when the third approval information is processed.
  • the first domain is the service domain
  • the first identification information is generated based on the identification information of the user and information at a time when the first payment order is requested
  • the fourth identification information may correspond to identification information for the payment means domain.
  • the first domain is the payment method domain
  • the first identification information is generated based on the identification information of the user and information at the time when the first authorization information is processed
  • the second identification information is generated.
  • Information may correspond to identification information on the service domain
  • the fourth identification information may correspond to identification information on the external operator connection domain.
  • the domain is the external operator connection domain
  • the first identification information is generated based on identification information of the external operator and information at a time when the second approval information is processed
  • the second identification information The information may correspond to identification information for the payment means domain
  • the fourth identification information may correspond to identification information for the external operator's domain.
  • the domain is the domain of the external operator
  • the first identification information is generated based on the identification information of the external operator and information at the time when the third approval information is processed
  • the second identification information may correspond to identification information for the external operator connection domain.
  • An electronic device providing payment processing information includes: a processor; and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, causes the processor to: perform a first transaction for a user in a service provided by the electronic device ) Checking the information of; obtaining information on one or more first payment domains corresponding to a payment procedure for processing the first transaction; For a first domain included in the one or more first payment domains, first transaction identification information for the first transaction, first identification information for the first domain, and second information for a previous domain of the first domain. Generating first payment processing information including identification information; and providing the first payment processing information.
  • the present invention provides a method in which an electronic device providing payment processing information provides information related to transaction processing for a user's payment order, thereby providing a technical effect in terms of promoting convenience in transaction management on a service.
  • FIG. 1 is a diagram for explaining a payment processing information providing system in which a method of operating an electronic device for providing payment processing information according to various embodiments may be implemented.
  • FIG. 2 is a diagram illustrating configurations of a server device and a device interlocked with the server device according to various embodiments.
  • FIG. 3 is a diagram illustrating an operating method of the server device 100 for providing payment processing information according to various embodiments.
  • FIG. 4 is a diagram illustrating an operating method in which the server device 100 provides status information on payment processing information of domains included in one or more payment domains corresponding to a transaction in which a settlement amount difference occurs.
  • FIG. 5 is a diagram illustrating an operating method in which the server device 100 provides error resolution information corresponding to an error occurrence domain in which a settlement amount difference occurs.
  • FIG. 6 is a diagram illustrating an example in which the device 200 interlocked with the server device 100 outputs payment processing information for a transaction based on an operation of the server device 100 according to various embodiments.
  • FIG. 7 is a diagram illustrating an example in which the device 200 interlocked with the server device 100 outputs payment processing information including domain identification information based on the operation of the server device 100 according to various embodiments. .
  • FIG. 8 is a view of a domain included in one or more payment domains corresponding to a transaction in which a difference in settlement amount occurs based on an operation of the server device 100 by a device 200 linked to the server device 100 according to various embodiments. It is a diagram showing an example of outputting status information about payment processing information.
  • each component or feature may be considered optional unless explicitly stated otherwise.
  • Each component or feature may be implemented in a form not combined with other components or features.
  • various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment.
  • FIG. 1 is a diagram for explaining a payment processing information providing system in which a method of operating an electronic device for providing payment processing information according to various embodiments may be implemented.
  • a system for providing payment processing information may be implemented in various types of electronic devices.
  • the payment processing information providing system may be implemented in the server device 100 and the device 200 linked to the server device 100 .
  • the server device 100 and the device 200 linked to the server device 100 may perform operations according to various embodiments of the present disclosure based on the payment processing information providing system implemented in each device.
  • the payment processing information providing system according to various embodiments is not limited to that shown in FIG. 1 and may be implemented in more various electronic devices and servers.
  • the server device 100 may be a device that performs wireless and wired communication with the device 200 interlocked with the server device 100 and includes a storage having a large storage capacity.
  • the server device 100 may be a cloud device connected to the device 200 linked to the server device 100 .
  • the device 200 linked to the server device 100 may be a device that can be used by an individual user such as a desktop PC, a tablet PC, or a mobile terminal.
  • other electronic devices performing similar functions may be used as the device 200 linked to the server device 100 .
  • a system for providing payment processing information may include various modules for operation.
  • Modules included in the payment processing information providing system are computer codes implemented so that a physical device (eg, server device 100) in which the payment processing information providing system is implemented (or included in a physical device) can perform a designated operation. or one or more instructions.
  • the physical device in which the payment processing information providing system is implemented stores a plurality of modules in a memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the plurality of modules correspond to the plurality of modules. to perform specified actions.
  • FIG. 2 is a diagram illustrating configurations of a server device and a device interlocked with the server device according to various embodiments.
  • a server device 100 and a device 200 linked to the server device 100 may include an input/output unit 210, a communication unit 220, a storage 230, and a processor 240.
  • an input/output unit 210 may include an input/output unit 210, a communication unit 220, a storage 230, and a processor 240.
  • the input/output unit 210 may be various interfaces or connection ports that receive user input or output information to the user.
  • the input/output unit 210 may include an input module and an output module, and the input module receives a user input from a user.
  • User input may be made in various forms including key input, touch input, and voice input.
  • Examples of input modules capable of receiving such user input include a traditional keypad, keyboard, and mouse, as well as a touch sensor that detects a user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, A proximity sensor including at least one of an illuminance sensor or an infrared sensor for detecting user approach, a motion sensor for recognizing a user's motion through an acceleration sensor or a gyro sensor, and various other types of sensors that detect or receive user input.
  • the input module may include at least one of the devices listed above.
  • the touch sensor may be implemented as a piezoelectric or capacitive touch sensor that detects a touch through a touch panel attached to a display panel or a touch film, an optical touch sensor that detects a touch by an optical method, and the like.
  • the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) connecting an external input device that receives a user input instead of a device that detects a user input by itself.
  • the output module may output various types of information.
  • the output module may include at least one of a display for outputting an image, a speaker for outputting sound, a haptic device for generating vibration, and other various types of output means.
  • the output module may be implemented in the form of a port type output interface connecting the above-described individual output means.
  • an output module in the form of a display may display text, still images, and moving images.
  • Displays include liquid crystal displays (LCDs), light emitting diodes (LEDs) displays, organic light emitting diodes (OLEDs) displays, flat panel displays (FPDs), and transparent displays.
  • LCDs liquid crystal displays
  • LEDs light emitting diodes
  • OLEDs organic light emitting diodes
  • FPDs flat panel displays
  • display transparent display
  • curved display flexible display
  • 3D display 3D display
  • holographic display projector
  • other various types of devices capable of performing image output functions. may contain at least one.
  • Such a display may be in the form of a touch display integrally formed with the touch sensor of the input module.
  • the communication unit 220 may communicate with other devices. Accordingly, the server device 100 and the device 200 interlocked with the server device 100 may transmit and receive information with other devices through a communication unit. For example, the server device 100 and the device 200 linked to the server device 100 may perform mutual communication using a communication unit or perform communication with other devices.
  • the communication unit includes a wired communication module that accesses the Internet through a LAN (Local Area Network), a mobile communication module that accesses a mobile communication network through a mobile communication base station to transmit and receive data, and a wireless local area network (WLAN) such as Wi-Fi.
  • WLAN Local Area Network
  • Area Network)-based communication method or WPAN (Wireless Personal Area Network)-based communication method such as Bluetooth or Zigbee, a short-distance communication module, or GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System) ), or a combination thereof.
  • LAN Local Area Network
  • WPAN Wireless Personal Area Network
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • the storage 230 may store various types of information. Storage may temporarily or semi-permanently store data.
  • the storage of the server 100 includes an operating system (OS) for driving the server 100, a program for generating data or braille for hosting a website, or an application (eg, a web application). ) may be stored.
  • OS operating system
  • application eg, a web application
  • the storage may store the modules in the form of computer code as described above.
  • Examples of the storage 230 include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), and the like. This can be. Such storage may be provided in a built-in type or a detachable type.
  • HDD hard disk drive
  • SSD solid state drive
  • flash memory a read-only memory
  • RAM random access memory
  • the processor 240 controls overall operations of the server device 100 and the device 200 interlocked with the server device 100 . To this end, the processor 240 may perform calculations and processing of various types of information and control operations of components of the server 100 . For example, the processor 240 may execute a program or application for providing payment processing information.
  • the processor 240 may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor 240 may be implemented in the form of an electronic circuit that performs a control function by processing electrical signals, and in terms of software, it may be implemented in the form of a program that drives the processor 240 in hardware.
  • operations of the server device 100 and the device 200 interlocked with the server device 100 may be interpreted as being performed under the control of the processor 240 . That is, when the modules implemented in the above-described payment processing information providing system are executed, the modules cause the processor 240 to cause the server device 100 and the device 200 linked to the server device 100 to perform the following operations. can be interpreted as controlling.
  • various embodiments may be implemented through various means.
  • various embodiments may be implemented by hardware, firmware, software, or a combination thereof.
  • the method includes one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs. (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, etc.
  • the method according to various embodiments may be implemented in the form of a module, procedure, or function that performs functions or operations described below.
  • software codes can be stored in memory and run by a processor.
  • the memory may be located inside or outside the processor, and may exchange data with the processor by various means known in the art.
  • the server device 100 performs a payment processing information providing operation, and according to various embodiments, the server device that obtains payment processing information from the server device 100
  • the device 200 linked to (100) may output payment processing information.
  • FIG. 3 is a diagram illustrating an operating method of the server device 100 for providing payment processing information according to various embodiments.
  • the server device 100 provides payment processing information, and in order to perform an operation of providing the payment processing information, the server device 100 checks the information of the first transaction for the user in the service provided. (301), obtaining information on one or more first payment domains corresponding to the payment procedure for processing the first transaction (303), and with respect to the first domain included in the one or more first payment domains, the first transaction Generating first payment processing information including first transaction identification information for, first identification information for a first domain, and second identification information for a previous domain of the first domain (305), and first payment processing information can be provided (307).
  • the server device 100 according to FIG. 3 generates and provides payment processing information for each of one or more payment domains corresponding to each transaction, as shown in FIG.
  • the server device 100 may provide error resolution information by determining an error domain that causes a difference in settlement amount as shown in FIG. 5 .
  • the server device 100 may check information on a first transaction for a user in a service related to the server device 100.
  • the service is a service related to the server device 100, and a user can search for, order, purchase, and receive delivery of desired items through the service.
  • the server device 100 may check and set information related to a series of payment procedures corresponding to the order for the corresponding item. That is, when a user pays for a specific item and a payment order for a specific item is obtained from the user, various information related to each payment procedure for processing the acquired payment order is used as transaction information corresponding to the payment order. can be checked or set.
  • transaction information may include various types of information to be described later in relation to one or more payment domains corresponding to a payment procedure for processing a corresponding transaction.
  • the server device 100 may obtain information about one or more first payment domains corresponding to a payment procedure for processing the first transaction.
  • one or more first payment domains corresponding to a payment procedure that processed the first transaction are payment domains for processing a payment order related to the first transaction according to a user's payment method, and the first transaction is a payment method. It may be processed by one or more payment procedures corresponding to , and the one or more first payment domains may include each domain for processing each payment procedure. At this time, since the payment procedure for processing the transaction corresponding to the payment order may vary depending on the user's payment method, one or more first payment domains corresponding to the payment procedure for processing the first transaction may be set according to the user's payment method. may also vary.
  • the user when a user pays for an item through a service related to the server device 100, the user directly utilizes an external operator's payment service, such as account transfer payment based on a specific bank company or card payment based on a specific card company, to pay for the item.
  • an external operator's payment service such as account transfer payment based on a specific bank company or card payment based on a specific card company
  • the payment order for the item is approved and processed on the service, and information on the approved payment order is transmitted to the payment service side of the external business operator to make the payment of the external business operator.
  • the corresponding payment order is finally approved by the service, the first transaction corresponding to the payment order for the item may be completed.
  • a payment method such as a bank account based on a specific bank company or a card based on a specific card company is preset on the service, or Points or service money according to the membership of the service may be accumulated in advance and used as a preset payment method.
  • the user can pay for the item through the preset payment method, and when using the preset payment method, when using the payment service of an external operator directly, such as skipping some verification procedures such as account number or card number confirmation You can pay for items with a simpler procedure.
  • the user selects a preset payment method to process payment for an item and the payment order for the item is approved and processed on the service, it is checked whether the payment order can be processed with the preset payment method and approved. Then, it is confirmed and approved whether the payment order approved for the preset payment method can be delivered to the payment service side of the external operator corresponding to the preset payment method, and accordingly, the information on the approved payment order is sent to the external operator.
  • the payment order is transmitted to the payment service side and the payment service of the external operator approves the payment order, the first transaction corresponding to the payment order for the item may be completed.
  • the first approval information may be processed, and if the first approval information is processed, a second approval for confirming whether the payment order for the item in the payment method domain corresponding to the preset payment method is approved on the preset payment method information can be processed.
  • the third approval information for confirming whether or not the payment order for the corresponding item can be processed for the payment service of the external operator corresponding to the preset payment method is transmitted to the external operator. It can be processed through the connection domain, and if the third approval information is processed, the information on the payment order for the item is delivered to the external operator domain, and the payment order is approved on the payment service of the external operator to complete the first transaction.
  • the server device 100 that obtains information on one or more first payment domains corresponding to a payment procedure for processing the first transaction in operation 303, the first transaction for each of the one or more first payment domains. You can set and manage related information.
  • the server device 100 provides first transaction identification information for a first transaction, first transaction identification information for a first transaction, and first transaction identification information for a first domain for a first domain included in one or more first payment domains.
  • First payment processing information including identification information and second identification information for a previous domain of the first domain may be generated.
  • first transaction identification information included in first payment processing information generated by the server device 100 for a first domain included in one or more first payment domains in operation 305 is the server device 100 It may include information about the type of service related to.
  • Services related to the server device 100 may be set in various types according to the type of item to be sold or the category of the item, and for example, the service corresponds to the type of item sales service that sells industrial products or other general products such as food. Alternatively, the service may correspond to a type of food item delivery service that sells and delivers food or other prepared food such as a dish menu. Since it is necessary to distinguish payment procedures or transactions according to the type of each service, transaction identification information for identifying a specific transaction may be set to include information about the type of service related to the server device 100 .
  • first transaction identification information included in first payment processing information generated by the server device 100 for a first domain included in one or more first payment domains in operation 305 may include one or more first payment processing information. It may be information commonly included in payment processing information generated by the server device 100 for each domain. That is, when generating payment processing information for each of one or more first payment domains, the server device 100 may set each payment processing information to include common first transaction identification information.
  • the first payment processing information generated by the server device 100 for a first domain included in one or more first payment domains in operation 305 is information about a date or time at which the first transaction was processed. and information on the payment amount for which payment has been completed according to the first transaction, and various information related to the payment of the item.
  • the first identification information for the first domain included in the first payment processing information may correspond to information for identifying the first domain, which is a target for which the first payment processing information is generated.
  • the second identification information for a previous domain of the first domain included in the first payment processing information may include the first payment processing among one or more first payment domains corresponding to a payment procedure that processed the first transaction. It may correspond to information for identifying a domain corresponding to a payment procedure immediately before the payment procedure on the first domain, which is a subject for which information is generated. That is, since the server device 100 creates and manages payment processing information in units of domains, in order to check the connection relationship between each domain, the payment processing information for one domain is combined with the identification information of the corresponding one domain. Identification information of the previous domain corresponding to the domain transfer procedure may be included.
  • one or more first payment domains may sequentially include a service domain and an external operator domain. If the first domain related to the first payment processing information corresponds to a service domain, the service domain is a domain corresponding to the first payment procedure, so the first payment processing information is the first identification for the service domain corresponding to the first domain. information may be included.
  • the first payment processing information when the first domain related to the first payment processing information corresponds to an external operator domain, the first payment processing information is an external operator domain corresponding to the first domain because a service domain corresponding to a transfer procedure of the external operator domain exists. It may include first identification information for and second identification information for a service domain corresponding to a previous domain of the first domain.
  • one or more first payment domains include a service domain, a payment method domain, an external operator connection domain, and an external operator.
  • the operator domain may be included in turn. If the first domain related to the first payment processing information corresponds to a service domain, the service domain is a domain corresponding to the first payment procedure, so the first payment processing information is the first identification for the service domain corresponding to the first domain. information may be included.
  • the first payment processing information corresponds to the payment method domain corresponding to the first domain because a service domain corresponding to the transfer procedure of the payment method domain exists. It may include first identification information for and second identification information for a service domain corresponding to a previous domain of the first domain.
  • the first payment processing information corresponds to the first domain because a payment method domain corresponding to the transfer procedure of the external operator connection domain exists. It may include first identification information for an external operator connection domain and second identification information for a payment means domain corresponding to a previous domain of the first domain.
  • the first payment processing information corresponds to an external operator domain corresponding to the first domain because an external operator connection domain corresponding to a transfer procedure of the external operator domain exists. It may include first identification information for an operator domain and second identification information for an external operator connection domain corresponding to a previous domain of the first domain.
  • the first payment processing information may include the next payment of a payment procedure on the first domain, which is a target for which the first payment processing information is generated, among one or more first payment domains corresponding to the payment procedure that processed the first transaction. It may further include information for identifying a domain corresponding to the procedure. That is, since the server device 100 generates and manages payment processing information in units of domains, the identification information of one domain corresponding to the payment processing information for one domain and the corresponding one domain in order to check the connection relationship between each domain. Along with the identification information of the previous domain corresponding to the preceding procedure, the identification information of the next domain corresponding to the subsequent procedure of the corresponding one domain may be included.
  • one or more first payment domains may sequentially include a service domain and an external operator domain. If the first domain related to the first payment processing information corresponds to a service domain, the service domain is a domain corresponding to the first payment procedure, so the first payment processing information is the first identification for the service domain corresponding to the first domain. information, and may further include identification information about an external operator's domain corresponding to a domain following the first domain.
  • the first payment processing information when the first domain related to the first payment processing information corresponds to an external operator domain, the first payment processing information is an external operator domain corresponding to the first domain because a service domain corresponding to a transfer procedure of the external operator domain exists. It may include first identification information for and second identification information for a service domain corresponding to a previous domain of the first domain.
  • one or more first payment domains include a service domain, a payment method domain, an external operator connection domain, and an external operator.
  • the operator domain may be included in turn. If the first domain related to the first payment processing information corresponds to a service domain, the service domain is a domain corresponding to the first payment procedure, so the first payment processing information is the first identification for the service domain corresponding to the first domain. information, and may further include identification information about a payment instrument domain corresponding to a domain following the first domain.
  • Payment processing information includes first identification information for a payment means domain corresponding to the first domain and second identification information for a service domain corresponding to a previous domain of the first domain, and corresponds to a domain following the first domain. It may additionally include identification information about an external operator connection domain to be used.
  • the first payment processing information includes first identification information for an external operator connection domain corresponding to the first domain and second identification information for a payment method domain corresponding to a previous domain of the first domain. It may additionally include identification information about an external operator's domain corresponding to the next domain of.
  • the first payment processing information corresponds to an external operator domain corresponding to the first domain because an external operator connection domain corresponding to a transfer procedure of the external operator domain exists. It may include first identification information for an operator domain and second identification information for an external operator connection domain corresponding to a previous domain of the first domain.
  • information on elements related to each domain in the payment procedure may be used.
  • identification information for a service domain for processing approval information for confirming whether a payment order corresponding to a transaction is approved on the service is the identification information of the user requesting the payment order and the time at which the payment order is requested. It can be created to reflect information, and through this, it can be distinguished from service domains for other transactions.
  • identification information on a payment method domain for processing approval information for confirming approval on a preset payment method for a payment order corresponding to a transaction is a service that is the identification information of the user who requested the payment order and the previous domain.
  • approval information related to the payment order may be generated to reflect information at the time when the payment order is processed, and through this, it may be distinguished from payment method domains for other transactions.
  • identification information on an external operator connection domain for processing approval information for confirming approval of a payment order corresponding to a transaction for a payment service related to an external operator corresponding to a predetermined payment method is included in the payment order. It can be generated to reflect the information at the time when the approval information related to the payment order is processed on the identification information of the external operator receiving the information about and the payment method domain, which is the previous domain. Through this, the external operator connection domain and can be distinguished.
  • the identification information on the external operator's domain corresponding to the payment service of the external operator for receiving information on the payment order is the identification information of the external operator receiving the information on the payment order and the connection to the external operator, which is the previous domain.
  • approval information related to the payment order may be generated to reflect information at the time when the payment order is processed, and through this, it may be distinguished from external business domains for other transactions.
  • the server device 100 may provide first payment processing information.
  • the first payment processing information provided by the server device 100 according to operation 307 may be generated based on operations 301 to 305 and include various information corresponding to operations 301 to 305 .
  • the server device 100 when a difference in settlement amount occurs between the service and the payment service associated with the external operator corresponding to the payment method used in the service, one corresponding to the transaction in which the difference in settlement amount occurs
  • An operation of providing status information on payment processing information of a domain included in the above payment domains may be performed as shown in FIG. 4 .
  • the difference between the settlement amount means the payment amount settled according to the payment of the item in the service related to the server device 100 that provides the sales service of various items and the external operator corresponding to the payment method used by the user to pay for the item.
  • the difference between the payment amount settled according to the payment of the item in the payment service of This may indicate that an error has occurred in the process.
  • FIG. 4 is a diagram illustrating an operating method in which the server device 100 provides status information on payment processing information of domains included in one or more payment domains corresponding to a transaction in which a settlement amount difference occurs.
  • the server device 100 provides state information on payment processing information of a domain, and in order to perform an operation of providing the state information, the server device 100 communicates with an external operator corresponding to a service and a payment method used in the service.
  • state information indicating whether identification information on the previous domain of the second domain is included is checked (407), and the checked state information may be provided (409).
  • the state information on the second payment processing information provided by the server device 100 according to operation 409 is information generated on the second payment processing information based on the fact that the processing of the second transaction is completed.
  • the operation of the server device 100 according to FIG. 4 corresponds to the difference in settlement amount when a difference in settlement amount occurs between a service and a payment service related to an external operator corresponding to a payment method used in the service. It may correspond to an operation for tracking the domain in which an error occurred in the payment processing process of the transaction, and the server device 100 identifies the previous domain in each payment processing information generated for each domain according to the operation as shown in FIG. You can determine if an error has occurred based on whether the information has been included correctly. That is, when the payment processing information of any one of the one or more payment domains included in the transaction corresponding to the difference in the settlement amount does not include the identification information of the previous domain, the server device 100 identifies the corresponding domain and the previous domain as an error. It can be determined by the domain where the error occurred.
  • the status information provided by the server device 100 according to operation 409 is not only identification information about a previous domain of a second domain included in one or more second payment domains, but also the first payment domain as in the embodiment of FIG. 3 . 2 may also include identification information for the next domain of the domain.
  • the server device 100 checks whether the identification information of the previous domain and the identification information of the next domain are correctly included in each payment processing information generated for each domain. Based on this, you can check if an error has occurred. That is, when the payment processing information of any one of the one or more payment domains included in the transaction corresponding to the difference in settlement amount does not include the identification information of the previous domain or the next domain, the server device 100 identifies the domain and the previous domain.
  • the domain or the next domain may be determined as an error occurrence domain in which an error occurs.
  • the server device 100 may perform an operation of providing error resolution information by determining an error domain that causes a difference in settlement amount, as shown in FIG. 5 .
  • FIG. 5 is a diagram illustrating an operating method in which the server device 100 provides error resolution information corresponding to an error occurrence domain in which a settlement amount difference occurs.
  • the server device 100 provides error resolution information corresponding to an error occurrence domain, and in order to perform an operation of providing the error resolution information, one or more payment domains related to a transaction corresponding to a settlement amount difference.
  • payment processing information generated for a specific domain included in whether or not identification information for the previous domain of the specific domain is included (501), and if the payment processing information does not include identification information for the previous domain,
  • the feature domain and the previous domain are determined as error-occurring domains in which a settlement amount difference occurs (503), and error resolution information corresponding to the error-occurring domain may be provided (505).
  • the server device 100 may determine the service domain or the payment method domain as an error-occurring domain in which a difference in settlement amount occurs.
  • the identification information for the previous domain of each domain is correctly included in the external operator connection domain or the payment processing information for the external operator domain corresponding to the subsequent payment procedure of the payment method domain, on the service related to the server device 100
  • the transaction is treated as failed, so the purchase confirmation, sending, and delivery of the item do not proceed, while the transaction is processed as completed in the payment service of the external operator, and the external operator will charge the payment amount to the user who paid for the item.
  • the device 100 may provide error resolution information including details of refunding the payment amount to the user or details of canceling the payment of the payment service of the external business operator.
  • the server device 100 may determine the payment method domain or the external operator connection domain as an error-occurring domain in which a settlement amount difference occurs.
  • the transaction is treated as failed on the service related to the server device 100 and the item While the purchase confirmation, sending, and delivery procedures do not proceed, the external operator's payment service will process the transaction as completed and the external operator will charge the user who paid for the item, so the server device 100 sends the payment amount. It is possible to provide the user with error-resolving information including details of refund or cancellation of payment by an external operator's payment service.
  • the server device 100 may determine the external operator connection domain or the external operator domain as an error occurrence domain in which a difference in settlement amount occurs.
  • the external operator's domain is the final step of the payment procedure. If the external operator's domain does not correctly include the identification information of the previous domain, the transaction may be treated as failed in the payment service of the external operator, while the server device 100 related to the server device 100 In the service, it is determined that there is no abnormality in the service domain, the payment method domain, and the external business connection domain, and the transaction may be processed as completed. In this case, the payment processing is completed on the service, and the purchase confirmation, dispatch, and delivery procedures of the item are performed, whereas the external business operator will not charge the user for the payment of the item by the external business operator, so the server device 100 Error solving information including contents instructing the user to charge the user for the payment amount may be provided.
  • FIGS. 6 to 8 are diagrams illustrating an example of a UI/UX for providing payment processing information according to various embodiments.
  • the examples of FIGS. 6 to 8 may be UI/UX (user interface/user experience) for the device 200 interlocked with the server device 100 according to the embodiment described above in FIGS. 3 to 5.
  • each of the embodiments described in the following drawings may be performed based on the operation of the server device 100 described above with reference to FIGS. 3 to 5 .
  • the device 200 linked to the server device 100 receives input information and serves as a server When transmitted to the device 100, the server device 100 provides information corresponding to the input information to the device 200 linked to the server device 100 based on the operations described above in FIGS. 3 to 5 This may be performed in a form in which the device 200 linked to the server device 100 outputs it.
  • each embodiment of UI / UX described in the following drawings is not limited to this form and can be performed in all forms that can implement each embodiment of UI / UX.
  • FIG. 6 is a diagram illustrating an example in which the device 200 interlocked with the server device 100 outputs payment processing information for a transaction based on an operation of the server device 100 according to various embodiments.
  • the device 200 linked to the server device 100 may output summary information about the transaction for the user's payment order, as in 601, and the summary information includes a transaction ID (Identifier) identifying the transaction, Type of service, payment order ID identifying the payment order corresponding to the transaction, payment method of the user, whether the payment has been completed or cancelled, external operator corresponding to the payment method, processing status of the transaction, amount of the payment order corresponding to the transaction, and payment The date of the order may be included.
  • a transaction ID Identifier
  • the device 200 linked to the server device 100 may output payment processing information for each of one or more payment domains corresponding to the payment procedure that processed the transaction, as shown in 603 .
  • the payment processing information for each domain may include transaction identification information, identification information of each domain, and identification information of the previous domain or next domain of each domain, as mentioned in the embodiments of FIGS. 3 to 5.
  • information such as the amount of the payment order corresponding to the transaction and the date of the payment order may also be included.
  • the server device 100 may integrate and manage payment processing information for each payment domain corresponding to a payment procedure that processed the transaction through one transaction ID, and may include the previous domain or Depending on whether or not the identification information of the following domains is correctly included, it can be judged whether the payment process in each domain has been properly processed.
  • FIG. 7 is a diagram illustrating an example in which the device 200 interlocked with the server device 100 outputs payment processing information including domain identification information based on the operation of the server device 100 according to various embodiments. . 7 may also be understood as outputting the payment processing information output in FIG. 6 as a different type of UI/UX.
  • the device 200 linked to the server device 100 may output payment processing information for a service domain among one or more payment domains corresponding to a payment procedure for processing a transaction, as in 701, and payment processing information for the service domain. contains the identification information of the service domain and the identification information of the payment method domain corresponding to the next domain. Since the service domain is the domain corresponding to the first payment procedure for processing a transaction, the identification information for the previous domain is null. You can check that it is set.
  • the device 200 linked to the server device 100 may output payment processing information for a payment method domain among one or more payment domains corresponding to a payment procedure for processing a transaction, as in 703, and payment for the payment method domain. It can be confirmed that the processing information includes identification information of the payment method domain, identification information of a service domain corresponding to the previous domain, and identification information of an external operator connection domain corresponding to the next domain.
  • the device 200 linked to the server device 100 may output payment processing information for an external operator connection domain among one or more payment domains corresponding to a payment procedure that processed a transaction as in 705, and may output payment processing information for an external operator connection domain. It can be confirmed that the payment processing information for the payment process includes identification information of an external operator connection domain, identification information of a payment method domain corresponding to the previous domain, and identification information of an external operator domain corresponding to the next domain.
  • the device 200 linked to the server device 100 may output payment processing information for an external operator's domain among one or more payment domains corresponding to a payment procedure for processing a transaction as in 707, and may output payment processing information for an external operator's domain.
  • the processing information includes the identification information of the external operator domain and the identification information of the domain associated with the external operator corresponding to the previous domain. Since the external operator domain is the domain corresponding to the last payment procedure for processing the transaction, It can be confirmed that the identification information is set as a null type.
  • FIG. 8 is a view of a domain included in one or more payment domains corresponding to a transaction in which a difference in settlement amount occurs based on an operation of the server device 100 by a device 200 linked to the server device 100 according to various embodiments. It is a diagram showing an example of outputting status information about payment processing information.
  • the device 200 linked to the server device 100 outputs information about the difference in settlement amount generated in the transaction between the service related to the server device 100 and the payment service of the external operator corresponding to the user's payment method. can do.
  • Such information includes an ID for the settlement amount difference to identify the settlement amount difference as an item, the service type of the transaction, a transaction ID (Identifier) that identifies the transaction, the user's payment method, an external operator corresponding to the payment method, and the transaction
  • the amount and date of the payment order corresponding to , and the date when the settlement amount difference occurred may be included.
  • the device 200 linked to the server device 100 may output status information about payment processing information for each of one or more payment domains corresponding to the payment procedure for processing the transaction in which the settlement amount difference occurred, as in step 803. there is.
  • the status information for each payment processing information may indicate whether the identification information of the previous domain or the next domain of each domain is correctly included in each payment processing information, and if the identification information of the previous domain or the next domain is correctly included, Confirm that the payment was normally processed in each domain, but if the identification information of the previous domain or the next domain is not correctly included, it can be confirmed that the identification information of the previous domain or the next domain is missing.
  • the identification information of the service domain corresponding to the previous domain is included in the payment processing information for the original payment method domain. It should be included, but includes information indicating that the identification information of the service domain is missing, and the server device 100 can confirm the payment method domain and the service domain as error-occurring domains by checking such information.
  • the operation of the UI / UX for the device 200 linked to the server device 100 of FIGS. 6 to 8 and the operation of the device 200 linked to the server device 100 is the server device ( 100), and the UI/UX examples of FIGS. 6 to 8 are examples for the disclosure of the present invention, and various embodiments of the present invention may be performed in the UI/UX form of FIGS. 6 to 8 It is not limited to and can be performed according to all types of UI / UX that can implement various embodiments of the present invention.
  • the method according to the system according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium.
  • various embodiments of the present invention may be implemented as computer readable codes in a computer readable recording medium from a specific point of view.
  • a computer readable recording medium is any data storage device capable of storing data readable by a computer system. Examples of computer readable recording media include read only memory (ROM), random access memory (RAM), and compact disk-read only memory (CD-ROM). ), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet).
  • the computer readable recording medium may also be distributed across networked computer systems, so that computer readable code is stored and executed in a distributed manner.
  • functional programs, code, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.
  • Such software may include, for example, volatile or non-volatile storage devices, such as RAM, memory chips, devices or integrated circuits, whether erasable or rewritable. Or, for example, a compact disk (CD), DVD, magnetic disk or magnetic tape, such as optically or magnetically recordable and at the same time machine (eg, computer) readable storage medium may be stored. .
  • volatile or non-volatile storage devices such as RAM, memory chips, devices or integrated circuits, whether erasable or rewritable.
  • a compact disk (CD), DVD, magnetic disk or magnetic tape such as optically or magnetically recordable and at the same time machine (eg, computer) readable storage medium may be stored.
  • Methods according to various embodiments of the present invention may be implemented by a computer including a control unit and a memory, or a vehicle including such a memory or computer, and the memory may include a program including instructions for implementing the embodiments of the present invention. or an example of a machine-readable storage medium suitable for storing programs.
  • the present invention includes a program including code for implementing the device or method described in the claims of this specification and a storage medium readable by a machine (such as a computer) storing such a program.
  • a program may be transmitted electronically through any medium, such as a communication signal transmitted through a wired or wireless connection, and the present invention appropriately includes equivalents thereto.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un procédé par lequel un dispositif électronique fournit des informations de processus de paiement, le procédé comprenant les étapes consistant à : vérifier des informations sur une première transaction pour un utilisateur dans un service fourni par le dispositif électronique ; obtenir des informations sur au moins un premier domaine de paiement correspondant à une procédure de paiement selon laquelle la première transaction a été traitée ; par rapport à un premier domaine inclus dans ledit au moins un premier domaine de paiement, générer des premières informations de processus de paiement comprenant des premières informations d'identification de transaction pour la première transaction, des premières informations d'identification pour le premier domaine, et des secondes informations d'identification pour un domaine précédent du premier domaine ; et fournir les premières informations de processus de paiement.
PCT/KR2021/012198 2021-08-31 2021-09-08 Procédé de fonctionnement pour fournir des informations de processus de paiement, et dispositif électronique prenant en charge ledit procédé WO2023033217A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020210115439A KR102407253B1 (ko) 2021-08-31 2021-08-31 결제 처리 정보 제공을 위한 동작 방법 및 이를 지원하는 전자 장치
KR10-2021-0115439 2021-08-31

Publications (1)

Publication Number Publication Date
WO2023033217A1 true WO2023033217A1 (fr) 2023-03-09

Family

ID=81986609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/012198 WO2023033217A1 (fr) 2021-08-31 2021-09-08 Procédé de fonctionnement pour fournir des informations de processus de paiement, et dispositif électronique prenant en charge ledit procédé

Country Status (2)

Country Link
KR (2) KR102407253B1 (fr)
WO (1) WO2023033217A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101057016B1 (ko) * 2009-04-10 2011-08-17 엔에이치엔비즈니스플랫폼 주식회사 인터넷 중개 사이트를 이용한 인터넷 쇼핑 서비스 제공 방법 및 시스템
KR101074617B1 (ko) * 2004-01-15 2011-10-17 엔에이치엔비즈니스플랫폼 주식회사 인터넷을 이용한 전자 상거래에서의 분할 결제 제공 방법 및 시스템
KR101505031B1 (ko) * 2014-09-03 2015-03-24 유대희 Ｕｒｌ을 이용한 전자상거래 관리서버 및 그 관리방법
KR20160062239A (ko) * 2014-11-24 2016-06-02 주식회사 케이지이니시스 비동기식 지역 분산형 지불게이트웨이 운영 방법
JP2018110024A (ja) * 2018-03-05 2018-07-12 任天堂株式会社 決済システム、販売サーバ装置、決済サーバ装置及びサーバプログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101074617B1 (ko) * 2004-01-15 2011-10-17 엔에이치엔비즈니스플랫폼 주식회사 인터넷을 이용한 전자 상거래에서의 분할 결제 제공 방법 및 시스템
KR101057016B1 (ko) * 2009-04-10 2011-08-17 엔에이치엔비즈니스플랫폼 주식회사 인터넷 중개 사이트를 이용한 인터넷 쇼핑 서비스 제공 방법 및 시스템
KR101505031B1 (ko) * 2014-09-03 2015-03-24 유대희 Ｕｒｌ을 이용한 전자상거래 관리서버 및 그 관리방법
KR20160062239A (ko) * 2014-11-24 2016-06-02 주식회사 케이지이니시스 비동기식 지역 분산형 지불게이트웨이 운영 방법
JP2018110024A (ja) * 2018-03-05 2018-07-12 任天堂株式会社 決済システム、販売サーバ装置、決済サーバ装置及びサーバプログラム

Also Published As

Publication number Publication date
KR102407253B1 (ko) 2022-06-10
TW202316340A (zh) 2023-04-16
KR20230032862A (ko) 2023-03-07

Similar Documents

Publication Publication Date Title
WO2023068424A1 (fr) Procédé de fonctionnement permettant de fournir des informations de page et dispositif électronique le prenant en charge
WO2022215781A1 (fr) Procédé de mise en oeuvre d'un dispositif électronique en vue de gérer des informations de commande, et dispositif électronique les prenant en charge
WO2023033217A1 (fr) Procédé de fonctionnement pour fournir des informations de processus de paiement, et dispositif électronique prenant en charge ledit procédé
WO2024117384A1 (fr) Procédé de gestion d'informations de test et dispositif électronique le prenant en charge
WO2023033219A1 (fr) Procédé de fonctionnement pour fournir des informations relatives à un service et dispositif électronique le prenant en charge
WO2023106489A1 (fr) Procédé de fonctionnement permettant de fournir des informations de page et dispositif électronique le prenant en charge
WO2023008630A1 (fr) Procédé de fonctionnement pour la fourniture d'informations relatives à un service et dispositif électronique le prenant en charge
WO2023106492A1 (fr) Procédé de fonctionnement pour une configuration de structure de desserte de données et dispositif électronique pour sa prise en charge
WO2023008629A1 (fr) Procédé de fonctionnement pour fournir des informations relatives à un service et dispositif électronique le prenant en charge
WO2023022275A1 (fr) Procédé de fonctionnement pour fournir des informations relatives à un article, et dispositif électronique le prenant en charge
WO2024010116A1 (fr) Procédé pour commander un dispositif électronique fournissant des informations, et dispositif électronique le prenant en charge
WO2024075887A1 (fr) Procédé de gestion d'informations de paiement et dispositif électronique le prenant en charge
WO2023017877A1 (fr) Procédé de fonctionnement d'un dispositif électronique permettant de fournir des informations de recherche, et dispositif électronique le prenant en charge
WO2024025022A1 (fr) Procédé permettant de faire fonctionner un dispositif électronique pour fournir des informations, et dispositif électronique le prenant en charge
WO2023033218A1 (fr) Procédé de fonctionnement pour la fourniture d'informations relatives à un service et dispositif électronique le prenant en charge
WO2023249150A1 (fr) Procédé permettant de faire fonctionner un dispositif électronique fournissant des informations, et dispositif électronique le prenant en charge
WO2023136391A1 (fr) Procédé de fonctionnement permettant de fournir une page de catégorie d'articles et dispositif électronique le prenant en charge
WO2023017878A1 (fr) Procédé de fonctionnement pour fournir des informations de groupe d'articles et dispositif électronique pour le prendre en charge
WO2023022276A1 (fr) Procédé de fonctionnement permettant de fournir des informations de page et dispositif électronique le prenant en charge
WO2024058293A1 (fr) Procédé permettant de faire fonctionner un dispositif électronique pour fournir des informations, et dispositif électronique prenant en charge celui-ci
WO2023191156A1 (fr) Procédé de fonctionnement de dispositif électronique pour fournir des informations d'article, et dispositif électronique de prise en charge associé
WO2024150870A1 (fr) Procédé d'exploitation d'un dispositif électronique pour la fourniture d'informations, et dispositif électronique le prenant en charge
WO2022265145A1 (fr) Procédé de fonctionnement de dispositif électronique pour fournir un message publicitaire, et dispositif électronique le prenant en charge
WO2023191157A1 (fr) Procédé de fonctionnement d'un dispositif électronique pour fournir une page, et dispositif électronique le prenant en charge
WO2024135932A1 (fr) Procédé de fonctionnement d'un dispositif électronique de fourniture d'informations et dispositif électronique le prenant en charge

Legal Events

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

Ref document number: 21956145

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21956145

Country of ref document: EP

Kind code of ref document: A1