WO2023033217A1

WO2023033217A1 - Operation method for providing payment process inforamtion, and electronic device supporting same

Info

Publication number: WO2023033217A1
Application number: PCT/KR2021/012198
Authority: WO
Inventors: 양정권; 한강수; 박선영; 박현식; 윤찬미; 이거성; 김가연
Original assignee: 쿠팡 주식회사
Priority date: 2021-08-31
Filing date: 2021-09-08
Publication date: 2023-03-09
Also published as: KR102407253B1; TW202316340A; KR20230032862A

Abstract

Disclosed is a method by which an electronic device provides payment process information, the method comprising the steps of: checking information on a first transaction for a user in a service provided by the electronic device; obtaining information on at least one first payment domain corresponding to a payment procedure by which the first transaction was processed; with respect to a first domain included in the at least one first payment domain, generating first payment process information including first transaction identification information for the first transaction, first identification information for the first domain, and second identification information for a previous domain of the first domain; and providing the first payment process information.

Description

Operation method for providing payment processing information and electronic device supporting the same

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.

With the development of electronic technology, e-commerce has become a part of shopping. Customers can purchase products online without going directly to a shopping mall or market, and the products purchased online are delivered to the delivery address requested by the customer.

In the case of e-commerce, since the provision of detailed and accurate information about products has a significant impact on service satisfaction, various methods for providing more detailed and accurate information are being discussed.

In this regard, reference may be made to prior literature such as KR101756594B1 or KR101500849B1.

According to the method of the present invention, an electronic device providing payment processing information may provide information related to transaction processing for a user's payment order.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

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 according to various embodiments of the present disclosure, 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.

In an exemplary embodiment, 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.

In an exemplary embodiment, 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.

In an exemplary embodiment, the status information may be generated for the second payment processing information based on the fact that processing of the second transaction is completed.

In an exemplary embodiment, the one or more first payment domains may be determined based on a payment method of the user for the first transaction.

In an exemplary embodiment, the first transaction identification information may include information about the type of service.

In an exemplary embodiment, the first transaction identification information may be commonly included in payment processing information for each of the one or more first payment domains.

In an exemplary embodiment, 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.

In an exemplary embodiment, the first payment processing information may include fourth identification information for a domain following the first domain.

In an exemplary embodiment, 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.

In an exemplary embodiment, 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, and the fourth identification information may correspond to identification information for the payment means domain.

In an exemplary embodiment, 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, and the second identification information is generated. Information may correspond to identification information on the service domain, and the fourth identification information may correspond to identification information on the external operator connection domain.

In an exemplary embodiment, 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, and the second identification information The information may correspond to identification information for the payment means domain, and the fourth identification information may correspond to identification information for the external operator's domain.

In an exemplary embodiment, 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, and the second identification information may correspond to identification information for the external operator connection domain.

An electronic device providing payment processing information according to various embodiments of the present disclosure 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 various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be made by those skilled in the art. It can be derived and understood based on the detailed description to be described below.

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. have

The effects obtainable in the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

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.

2 is a diagram illustrating configurations of a server device and a device interlocked with the server device according to various embodiments.

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.

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.

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.

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. .

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 following embodiments combine elements and features of various embodiments in a predetermined form. 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. In addition, 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.

In the description of the drawings, procedures or steps that may obscure the gist of various embodiments are not described, and procedures or steps that can be understood by those skilled in the art are not described. did

Throughout the specification, when a part is said to "comprising" or "including" a certain element, it means that it may further include other elements, not excluding other elements, unless otherwise stated. do. In addition, terms such as “… unit”, “… unit”, and “module” described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. can be implemented as Also, “a or an”, “one”, “the” and like terms are used herein in the context of describing various embodiments (particularly in the context of the claims below). Unless otherwise indicated or clearly contradicted by context, both the singular and the plural can be used.

Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The detailed description set forth below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of various embodiments, and is not intended to represent a single embodiment.

In addition, specific terms used in various embodiments are provided to help understanding of various embodiments, and the use of these specific terms may be changed into other forms without departing from the technical spirit of various embodiments. .

Referring to FIG. 1 , a system for providing payment processing information according to various embodiments may be implemented in various types of electronic devices. For example, the payment processing information providing system may be implemented in the server device 100 and the device 200 linked to the server device 100 . In other words, 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. can Meanwhile, 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 according to various embodiments 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. For example, 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 according to various embodiments may be a device that can be used by an individual user such as a desktop PC, a tablet PC, or a mobile terminal. In addition, 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 according to various embodiments 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. In other words, 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.

Referring to FIG. 2 , 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. can

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. There is an input means, and the input module according to the embodiment of the present disclosure may include at least one of the devices listed above. Here, 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. In addition, 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. Also, 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. In addition, the output module may be implemented in the form of a port type output interface connecting the above-described individual output means.

For example, 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. display), curved display, flexible display, 3D display, holographic display, projector, and 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.

Here, communication, that is, transmission and reception of data may be performed by wire or wireless. To this end, 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. 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.

The storage 230 may store various types of information. Storage may temporarily or semi-permanently store data. For example, 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. In addition, 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.

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. Meanwhile, in the following description, unless otherwise noted, 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.

In summary, various embodiments may be implemented through various means. For example, various embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to various embodiments 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.

In the case of implementation by firmware or software, 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. For example, 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.

Hereinafter, various embodiments will be described in more detail based on the above technical idea. The above-described contents may be applied to various embodiments described below. For example, operations, functions, and terms that are not defined in various embodiments described below may be performed and described based on the contents described above.

In the following description, various embodiments will be described on the premise that 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.

According to FIG. 3, 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). At this time, 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. 4 to be described later, and the payment used in the service and the service. When a difference in settlement amount between payment services related to an external operator corresponding to a means occurs, an operation of providing status information on payment processing information of domains included in one or more payment domains corresponding to a transaction in which a difference in settlement amount occurs may be performed. And, based on the status information confirmed and provided according to FIG. 4 , 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 .

According to various embodiments, in operation 301, the server device 100 may check information on a first transaction for a user in a service related to the server device 100.

For example, 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.

For example, when a user orders an item, 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. Such 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.

According to various embodiments, in operation 303, the server device 100 may obtain information about one or more first payment domains corresponding to a payment procedure for processing the first transaction.

For example, 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.

For example, 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. In this case, in order to process the payment of the item, 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. When the corresponding payment order is finally approved by the service, the first transaction corresponding to the payment order for the item may be completed. That is, when a user pays for an item by directly utilizing a payment service of an external operator, approval information for confirming whether a payment order for a corresponding item is approved on the service in a service domain corresponding to a service related to the server device 100. If the approval information is processed in this way, information on the payment order for the item is transmitted to the external operator's domain corresponding to the payment service of the external operator, and the payment order is approved on the payment service of the external operator. A first transaction may be completed.

Or, as another example, when a user pays for an item through a service related to the server device 100, 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.

When 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. When 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.

That is, when a user pays for an item by using a payment method preset on a service related to the server device 100, checking whether the payment order for the item is approved on the service in the service domain corresponding to the service 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. In this way, when the second approval information is processed in the payment method domain, 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. can

For example, 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.

According to various embodiments, in operation 305, 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.

For example, 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 .

For example, 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.

For example, 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.

For example, 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.

For example, 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.

For example, when a user directly uses a payment service of an external operator to pay for an item, 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.

Alternatively, 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.

As another example, when a user pays for an item by using a preset payment method on a service related to the server device 100, 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.

Alternatively, when the first domain related to the first payment processing information corresponds to the payment method domain, 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.

Alternatively, when the first domain related to the first payment processing information corresponds to an external operator connection 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.

Alternatively, when the first domain related to the first payment processing information corresponds to an external operator 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.

For example, 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.

For example, when a user directly uses a payment service of an external operator to pay for an item, 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.

As another example, when a user pays for an item by using a preset payment method on a service related to the server device 100, 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.

Alternatively, if the first domain related to the first payment processing information corresponds to the payment method domain, there is a service domain corresponding to the previous procedure of the payment method domain and an external operator connection domain corresponding to the next procedure of the payment method domain. 1 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.

Alternatively, when the first domain related to the first payment processing information corresponds to an external operator connection domain, a payment means domain corresponding to the transfer procedure of the external operator connection domain and an external operator domain corresponding to the next procedure of the external operator connection domain exist. Therefore, 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.

At this time, in order to generate identification information for each domain, information on elements related to each domain in the payment procedure may be used.

For example, 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.

For example, 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. On the 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.

For example, 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.

For example, 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. On the 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.

According to various embodiments, in operation 307, the server device 100 may provide first payment processing information.

For example, 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 .

It is obvious that information generated or provided by the server device 100 performing the operation of FIG. 3 according to the above-described embodiments in relation to payment processing may be combined and generated or provided in various forms.

On the other hand, as described above, the server device 100 according to FIG. 3, 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 . Here, 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. means 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.

According to FIG. 4, 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. When a difference in settlement amount between related payment services occurs, determining a second transaction corresponding to the difference in settlement amount (401), checking second transaction identification information for the second transaction (403), and determining the second transaction identification information Based on, check one or more second payment domains corresponding to the payment procedure that processed the second transaction (405), and in the second payment processing information generated for the second domain included in the one or more second payment domains. , 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).

For example, 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. can be

For example, 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.

For example, 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. In this case, 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.

At this time, the server device 100 according to FIG. 4 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 .

According to FIG. 5 , 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. For 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).

For example, with respect to a transaction corresponding to a payment order for an item of a user on a service related to the server device 100, if payment processing information for a payment method domain among one or more payment domains according to a payment procedure corresponding to the transaction When the identification information of the service domain corresponding to the previous domain is not included in , 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.

At this time, if 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.

For example, for a transaction corresponding to a user's payment order for an item on a service related to the server device 100, if payment processing information for an external operator connection domain among one or more payment domains according to a payment procedure corresponding to the transaction If the identification information of the payment method domain corresponding to the previous domain is not included in the image, 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.

At this time, if the identification information of the previous domain is correctly included in the payment processing information for the external operator domain corresponding to the subsequent payment procedure of the external operator connection domain, 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.

For example, for a transaction corresponding to a user's payment order for an item on a service related to the server device 100, if payment processing information for an external operator's domain among one or more payment domains according to a payment procedure corresponding to the transaction When the identification information of the external operator connection domain corresponding to the previous domain is not included, 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.

At this time, 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.

6 to 8 are diagrams illustrating an example of a UI/UX for providing payment processing information according to various embodiments. For example, 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. And, 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 .

Specifically, in each embodiment of the UI/UX for the device 200 linked to the server device 100 described in the following drawings, 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. However, 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.

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.

In addition, 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. , In addition, 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.

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.

As in step 801, 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.

In addition, 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.

Since the status information output by the device 200 linked to the server device 100 through 805 confirms that the payment has been approved, 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.

Embodiments of the present invention disclosed in this specification and drawings are only presented as specific examples to easily explain the technical content of the present invention and help understanding of the present invention, and are not intended to limit the scope of the present invention. That is, it is obvious to those skilled in the art that other modified examples based on the technical idea of the present invention can be implemented. In addition, each of the above embodiments can be operated in combination with each other as needed. For example, all embodiments of the present invention may be implemented by a system in which parts are combined with each other.

In addition, 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.

As such, 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. In addition, 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.

It will also be appreciated that the apparatus and method according to various embodiments of the present invention can be realized in the form of hardware, software, or a combination of hardware and software. 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. . 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.

Accordingly, 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. In addition, such 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.

Although the above has been described with reference to the embodiments of the present invention, the embodiments of the present invention disclosed in this specification and drawings are only presented as specific examples to easily explain the technical content of the present invention and help understanding of the present invention. It is not intended to limit the scope of In addition, the embodiments according to the present invention described above are merely illustrative, and those skilled in the art will understand that various modifications and embodiments of equivalent scope are possible therefrom. Therefore, the true technical protection scope of the present invention should be defined by the following claims.

Claims

A method for providing payment processing information by an electronic device,

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

Including providing the first payment processing information,

How to Provide Payment Processing Information.
According to claim 1,

The payment processing information providing method,

Determining a second transaction corresponding to the difference in settlement amount 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;

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

Further comprising providing the status information,

How to Provide Payment Processing Information.
According to claim 2,

The payment processing information providing method,

if the third identification information is not included in the second payment processing information, determining the second domain and the previous domain of the second domain as an error-occurring domain corresponding to the difference in the settlement amount; and

Further comprising providing error resolution information corresponding to the error occurrence domain,

How to Provide Payment Processing Information.
According to claim 2,

Wherein the status information is generated for the second payment processing information based on the fact that the processing of the second transaction is completed.

How to Provide Payment Processing Information.
According to claim 1,

The one or more first payment domains are determined based on the user's payment method for the first transaction.

How to Provide Payment Processing Information.
According to claim 1,

The first transaction identification information includes information about the type of service,

How to Provide Payment Processing Information.
According to claim 1,

The first transaction identification information is commonly included in the payment processing information for each of the one or more first payment domains.

How to Provide Payment Processing Information.
According to claim 1,

The first payment processing information includes information about a date corresponding to the first transaction and information about an amount corresponding to the first transaction,

How to Provide Payment Processing Information.
According to claim 1,

The first payment processing information includes fourth identification information for a domain next to the first domain,

How to Provide Payment Processing Information.
According to claim 9,

The one or more first payment domains,

When the first payment order for the first transaction is performed based on the user's first payment method preset on the service, first approval information confirming whether the first payment order is approved on the service. A service domain for processing,

When the first approval information is processed, a payment means domain for processing second approval information for checking whether the first payment order is approved on the first payment method;

When the second approval information is processed, an external operator connection domain for processing third approval information for checking whether the first payment order is approved for a payment service related to an external operator corresponding to the first payment method; and

When the third approval information is processed, including an external operator domain corresponding to the payment service for receiving information on the first payment order,

How to Provide Payment Processing Information.
According to claim 10,

The first domain is the service domain,

The first identification information is generated based on the identification information of the user and information at the time when the first payment order is requested,

The fourth identification information corresponds to identification information for the payment method domain,

How to Provide Payment Processing Information.
According to claim 10,

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 approval information is processed,

The second identification information corresponds to identification information for the service domain,

The fourth identification information corresponds to identification information for the external operator connection domain,

How to Provide Payment Processing Information.
According to claim 10,

The domain is the external operator connection domain,

The first identification information is generated based on the identification information of the external operator and the information at the time when the second approval information is processed,

The second identification information corresponds to identification information for the payment method domain,

The fourth identification information corresponds to identification information for the external operator domain,

How to Provide Payment Processing Information.
According to claim 10,

The domain is the external operator domain,

The first identification information is generated based on the identification information of the external operator and the information at the time when the third approval information is processed,

The second identification information corresponds to identification information for the external operator connection domain,

How to Provide Payment Processing Information.
In an electronic device providing payment processing information,

processor; and

comprising one or more memories for storing one or more instructions;

The one or more instructions, when executed, cause the processor to:

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

Controlling the processor to perform the step of providing the first payment processing information,

electronic device.