TW202316340A - Operating method for providing payment process information and electronic apparatus supporting thereof - Google Patents

Abstract

Disclosed is a method of providing payment processing information in an electronic apparatus, the method including identifying information on a first transaction for a user in a service provided by the electronic apparatus, acquiring information on one or more first payment domains corresponding to a payment procedure through which the first transaction is processed, generating, for a first domain included in the one or more first payment domains, first payment processing information including first transaction identification information on the first transaction, first identification information on the first domain, and second identification information on a previous domain of the first domain, and providing the first payment processing information.

Description

Operation method for providing payment process information and electronic equipment supporting the operation method

The present invention relates to a method and apparatus for providing payment processing information and more particularly to a method of providing information associated with the processing of a transaction of a payment order by a user and a method for the Method for electronic equipment.

With the development of electronic technology, e-commerce has been established as a shopping field. Consumers can buy items online without going to a mall or market in person. Items purchased online are delivered to the delivery destination requested by the consumer.

In the case of electronic commerce, providing detailed and accurate information about items in a service has a significant impact on consumers' service satisfaction. Accordingly, various methods for providing more detailed and accurate information to consumers are discussed.

In this regard, relevant documents such as KR101756594B1, KR101500849B1 and the like may be incorporated by reference.

[Technical target]

According to an aspect, an electronic device for providing payment processing information may provide information associated with processing a transaction of a payment order by a user.

The technical goals to be achieved in the present invention are not limited to the technical goals described above, and other technical goals not mentioned herein will be clearly understood by those skilled in the art from the following description. [Technical solution]

Exemplary embodiments may provide a method of operating an electronic device for providing payment processing information and an electronic device supporting the method.

According to various exemplary embodiments, there is provided a method of providing payment processing information in an electronic device, the method comprising: identifying information about a first transaction by a user in a service provided by the electronic device; obtaining Information about one or more first payment domains corresponding to a payment process through which the first transaction is processed; for a first domain included in the one or more first payment domains, generating information including information about the first payment domain first transaction identification information of a transaction, first identification information about the first domain and second identification information about a previous domain of the first domain; and providing the first payment processing information.

The method may further include: when a settlement amount for the service is different from a settlement amount for a payment service associated with an external carrier corresponding to a payment option used in the service, determining that the settlement amount corresponds to one of the settlement amounts A second transaction of the difference; identifying second transaction identification information about the second transaction; identifying one or more second payment domains corresponding to a payment process through which the second transaction is processed based on the second transaction identification information ; for second payment processing information generated for a second domain included in the one or more second payment domains, identifying whether to include status information about third identification information for a previous domain of the second domain; and provide that status information.

The method may further include: when the third identification information is not included in the second payment processing information, an error occurs in determining the second field and the previous field of the second field as corresponding to the difference in settlement amount domain; and provide error resolution information corresponding to the domain where the error occurred.

The status information may be generated for the second payment processing information based on completion of processing for the second transaction.

The one or more first payment domains may be determined based on a payment option of the user for the first transaction.

The first transaction identification information may include information about a type of the service.

The first transaction identification information may be included in payment processing information common to 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 an amount corresponding to the first transaction.

The first payment processing information may include fourth identification information about a subsequent domain of the first domain.

The one or more first payment domains may include: a service domain, which is used to process the verification of the first payment order based on one of the user's first payment options set in the service. Whether to approve the first approval information of the first payment order of the first transaction in the service; a payment option field, which is used to verify whether the first payment is for the first payment when processing the first approval information The order approves the second approval information of the first payment option; an external operator connection domain, which is used for processing the second approval information to verify whether it corresponds to the first payment option a third approval information related to a payment service approval of the first payment order by an external carrier; The payment service for the order information.

The first domain may be the service domain, the first identification information may be generated based on the identification information about the user and information about a point in time when the first payment order is requested, and the fourth identification information may correspond to information about the Identification information of the payment option field.

The first field may be the payment option field, the first identification information may be generated based on identification information about the user and information about a point in time for processing the first approval information, and the second identification information may correspond to The identification information about the service domain, and the fourth identification information may correspond to the identification information about the external operator connection domain.

The first domain may be the external operator connection domain, the first identification information may be generated based on identification information about the external operator and information about a point in time of processing the second authorization information, the second identification information The fourth identification information may correspond to identification information on the payment option domain, and the fourth identification information may correspond to identification information on the external carrier domain.

The first domain may be the domain of the external operator, the first identification information may be generated based on identification information about the external operator and information about a point in time when the third authorization information is processed, and the second identification information may correspond to identifying information about the external carrier connection domain.

According to various exemplary embodiments, there is provided an electronic device for providing payment processing information, the electronic device comprising: a processor; and one or more memories storing one or more instructions, wherein when executed , the one or more instructions control the processor to perform: identifying information about a first transaction by a user in a service provided by the electronic device; Information about one or more first payment domains in the payment process; for one of the first domains included in the one or more first payment domains, generate first transaction identification information about the first transaction, about the first transaction first identification information of a domain and first payment processing information related to second identification information of a previous domain of the first domain; and providing the first payment processing information.

The exemplary embodiments of the present invention described above are only some of the exemplary embodiments of the present invention. Those skilled in the art should understand that various exemplary embodiments in which technical features of various exemplary embodiments of the present invention are reflected can be derived based on the following detailed description. [effect]

The invention has the technical effect in which a service can be achieved by presenting in an electronic device for providing payment processing information a method of providing information associated with the processing of a transaction of a payment order of a user Enhanced convenience of transaction management.

Effects to be obtained in the present invention are not limited to the above-mentioned effects, and other effects not mentioned herein will be clearly understood by those skilled in the art from the following description.

The following exemplary embodiments are obtained by combining constituent elements and features of each exemplary embodiment in a predetermined form. Each constituent element or feature may be regarded as optional unless clearly stated otherwise. Each constituent element or feature may be defined in a form that is not coupled with another constituent element or feature. In addition, some constituent elements and features may be combined with each other to implement various exemplary embodiments. The order of operations to be described in various exemplary embodiments may be changed. Some constituent elements or features of any exemplary embodiment may be included in other exemplary embodiments, or may be replaced with corresponding constituent elements or features of other exemplary embodiments.

In the description of the drawings, processes or steps that may obscure the gist of each exemplary embodiment and the like are not described, and processes or steps that can be understood by those skilled in the art are not described.

When a part "comprises or includes" a constituent element throughout the specification, it means that the part may further include other constituent elements rather than exclude other constituent elements, unless stated otherwise. In addition, terms such as "part", "device", "module" and the like used herein may refer to performing at least one function or operation, may be implemented as hardware or software, or may be implemented as hardware A unit of a combination of body and software. In addition, the words "a or an", "an", "the" and similar words may be used to include the singular or the plural unless describing the content of various exemplary embodiments (specifically, the invention application Contents in the patent scope) clearly indicate otherwise.

Hereinafter, some exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description to be disclosed below in conjunction with the accompanying drawings is intended to describe examples of various illustrative embodiments and not to be limiting thereto.

In addition, the terms used in each exemplary embodiment are provided to facilitate the overall understanding of each exemplary embodiment, and the use of these specific terms may be changed to other terms without departing from the technology of each exemplary embodiment idea.

FIG. 1 is a diagram illustrating a payment processing information providing system for implementing an operation method of an electronic device providing payment processing information explanations according to various exemplary embodiments.

Referring to FIG. 1, the payment processing information providing system according to various exemplary embodiments may be implemented using various types of electronic devices. For example, the payment processing information providing system can be implemented using a server device 100 and a device 200 linked to the server device 100 . In other words, each of the server device 100 and the devices 200 interlocked with the server device 100 can perform operations according to exemplary embodiments of the present invention based on a payment processing feed system implemented in each device. However, the payment processing information providing system according to various exemplary embodiments is not limited to the payment processing information providing system shown in FIG. 1 , but may be implemented using other various types of electronic devices and servers.

The server device 100 according to various exemplary embodiments may be an apparatus that performs wired and wireless communication with the devices 200 linked to the server device 100 and includes a large-capacity storage. For example, the server device 100 may be a cloud device connected to the device 200 linked with the server device 100 .

The device 200 interlocked with the server device 100 according to various exemplary embodiments may be a device usable by an individual user, such as a desktop personal computer (PC), a tablet PC, a mobile terminal or the like By. In addition, other electronic devices performing similar functions can be used as the device 200 interlocked with the server device 100 .

The payment processing information providing system according to various exemplary embodiments may include various operation modules. A module included in a payment processing feed system may be implemented to cause an entity device (eg, server device 100) implementing the payment processing feed system (or included in an entity device) to perform an operation assigned thereto Computer code or one or more instructions. In other words, in the physical device implementing the payment processing information providing system, a plurality of modules can be stored in a memory in the form of computer program codes. The plurality of modules stored in the memory, when executed by a computer, can be configured to cause the physical device to perform assigned operations corresponding to the plurality of modules.

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

Referring to FIG. 2 , each of the server device 100 and the devices 200 interlocked with the server device 100 may include an input/output section 210 , a communication section 220 , a storage 230 and a processor 240 .

The input/output part 210 may be various interfaces, various connection ports, or the like for receiving a user input or outputting information to the user. The input/output part 210 may include an input module and an output module. The input module receives a user input from a user. User input can be in various forms of input, including key input, touch input, and voice input. Examples of input modules that receive user input may include a conventional form of keypad or keyboard, a mouse, and touch sensors that sense a user's touch, microphones that receive an audio signal, A camera that recognizes a gesture or the like through image recognition, a proximity sensor that senses the user's approach including at least one of an illumination sensor or an infrared sensor, through an acceleration sensor Or a gyro sensor, a motion sensor for recognizing a user's motion, and various forms of input parts for sensing or inputting various forms of user input, and the input module according to an exemplary embodiment of the present invention A set may comprise at least one of the devices listed above. Here, the touch sensor may use a piezoelectric or capacitive touch sensor that senses a touch through a touch panel or a touch film attached to a display panel, by an optical method An optical touch sensor or the like is implemented for sensing a touch. Furthermore, instead of sensing user input by itself as a device, the input module may be implemented in the form of an input interface (USB port, PS/2 port or the like) connected to an external input device to which user input is received . In addition, the output module can output several pieces of various types of information. The output module may include at least one of a display for outputting an image, a speaker for outputting a sound, a haptic device for generating a vibration, and other various forms of output parts. In addition, the output module can also be implemented in the form of an output interface connected to the port types of the individual output parts mentioned above.

As an example, an output module in the form of a display can display a text, a static image and a moving image. The display may include a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible At least one of a display, a three-dimensional display, a holographic display, a projector, and other types of equipment capable of performing image output functions. Such a display may be in the form of a touch display configured integrally with the touch sensors of the input module.

The communication section 220 can communicate with another device. Accordingly, each of the server device 100 and the devices 200 linked with the server device 100 can transmit information to or receive information from another device via the communication section 220 . For example, the server device 100 and the device 200 linked with the server device 100 can communicate with each other or with another device using the communication section 220 .

Here, communication (ie, transmission and reception of data) can be performed in a wired or wireless manner. For this purpose, the communication section may include a wired communication module connected to the Internet or the like via a local area network (LAN), connected to a mobile communication network via a mobile communication base station to transmit and receive data A mobile communication module using one of a Wireless Area Network (WLAN) series of communication schemes (such as Wireless Fidelity (Wi-Fi)) or a Wireless Personal Area Network (WPAN) series of communication schemes (such as Bluetooth or Zigbee) A near field communication module, a satellite communication module using a global navigation satellite system (GNSS) such as a global positioning system, or a combination thereof.

The storage 230 can store various pieces of information. The storage 230 can store data temporarily or semi-permanently. For example, the operating system (OS) used to drive the server device 100, information used to host a website, information about a program or application (e.g., a web application) used to generate Braille Or the like can be stored in the memory of the server device 100 . In addition, the memory may store the modules in the form of computer code, as described above.

Examples of storage 230 may 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 memory can be provided as a built-in type or as a detachable type.

The processor 240 controls the overall operations of the server device 100 and the devices 200 interlocked with the server device 100 . For this purpose, the processor 240 may perform calculations of various information, and process and control operations of constituent elements of the server 100 . For example, the processor 240 may execute programs or applications for managing information. The processor 240 can be implemented using a computer or a device similar thereto along with a combination of hardware, software, or the like. The processor 240 can be implemented in hardware as an electronic circuit that processes electrical signals to perform control functions, and can be implemented in software as a program that drives the hardware processor 240 . Meanwhile, it can be interpreted that the operations of the server device 100 and the devices 200 interlocked with the server device 100 are executed under the control of the processor 240 unless otherwise stated in the following description. That is, the modules implemented in the information management system described above can be interpreted as the processor 240 controls the server device 100 and the devices 200 linked with the server device 100 to perform the following operations when executed.

In summary, the illustrative embodiments can be implemented in various ways. For example, the exemplary embodiments may be implemented by hardware, firmware, software, any combination thereof, or the like.

In the case of hardware implementation, a method according to the exemplary embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPs) ), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), processor, controller, microcontroller, microprocessor, or the like.

In the case of being implemented by firmware or software, a method according to various exemplary embodiments may be implemented in the form of a module, procedure or function for performing functions or operations to be described below. For example, software code may be stored in a memory and driven by a processor. Memory can be located inside or outside the processor and can transfer data to and receive data from the processor by various known means.

Hereinafter, exemplary embodiments will be described in more detail based on the technical idea as described above. The foregoing is applicable to various exemplary embodiments to be described below. For example, operations, functions, terms, or the like that are not defined in each exemplary embodiment to be described below may be performed and described based on the contents described above.

In the following description, an exemplary embodiment in which the server device 100 performs a payment processing information providing operation will be described. According to various exemplary embodiments, the server device 100 or the device 200 linked with the server device 100 that has received the payment processing information from the server device 100 may output the payment processing information.

FIG. 3 is a diagram illustrating an operation method of the server device 100 for providing payment processing information according to various exemplary embodiments.

Referring to FIG. 3 , the server device 100 can provide payment processing information. In order to perform the operation of providing payment processing information, the server device 100 may identify information about a user's first transaction in a service provided by the server device 100 in operation 301, and obtain information about a corresponding transaction in operation 303. Information about one or more first payment domains during a payment process through which the first transaction is processed, in operation 305, for one of the first domains included in the one or more first payment domains, generating information about the first The first transaction identification information of the transaction, the first identification information about the first domain, and the first payment processing information about the second identification information of a previous domain of the first domain, and the first payment processing information is provided in operation 307 . At this time, based on an operation of generating and providing payment processing information for each of one or more payment domains corresponding to each transaction, when a settlement amount of a service is different from one of the payment options corresponding to one of the payment options used in the service When a settlement amount of a payment service is related to an external operator, as described with reference to FIG. 4, the server device 100 of FIG. An operation for status information of payment processing information for a domain in a domain. In addition, based on the status information identified and provided according to FIG. 4 , the server device 100 can provide error resolution information by determining an error field that may cause a difference in the settlement amount, as described with reference to FIG. 5 .

According to various exemplary embodiments, in operation 301 , the server device 100 may identify information of a user's first transaction in a service related to the server device 100 .

For example, the service may be one related to the server device 100 and used by users to search, order, purchase and receive a desired item.

For example, when a user orders an item, the server device 100 may identify and set information associated with a series of payment processes corresponding to an order of the item. That is, when a payment order is placed for an ordered item in response to a user paying for the ordered item, various information associated with each payment process used to process the captured payment order may be identified or configured with respect to the corresponding Transaction information for one of the payment orders. This information about the transaction may include various information described below associated with one or more payment domains corresponding to one of the payment processes used to process the transaction.

According to various exemplary embodiments, in operation 303, the server device 100 may acquire information about one or more first payment domains corresponding to the payment process through which the first transaction is processed.

For example, one or more first payment domains corresponding to the payment process through which the first transaction is processed may be a payment domain for processing a payment order related to the first transaction based on a payment option of the user. The first transaction may be processed through one or more payment processes corresponding to the payment options. The one or more first payment domains may each comprise a domain for handling the payment process. At this time, the payment process for processing the transaction corresponding to the payment order may vary based on the user's payment options. Accordingly, the settings of one or more first payment domains corresponding to the payment process through which the first transaction is processed may also vary based on the user's payment options.

As an example, when paying for an item through a service related to the server device 100, the user can directly use the payment service of the external operator (such as an account transfer payment based on a specific bank company or a card based on a specific card company). Pay) to pay for items. In this case, in order to process the payment for the goods, the payment order for the goods may be approved and processed on the service, and the information about the approved payment order may be transmitted to the payment service of the external operator, and the payment of the external operator The service may approve the corresponding payment order. Through this, the first transaction corresponding to the payment order for the item can be completed. That is, when the user pays for the item by directly using the payment service of the external operator, the process for verifying whether the service is approved for the corresponding item can be processed in the service domain corresponding to the service related to the server device 100. Approval information for payment orders. In this case where the approval information is processed, the information about the payment order for the corresponding item may be transmitted to the external operator domain corresponding to the external operator's payment service. The first transaction may be completed when the corresponding payment order is approved on the external operator's payment service.

As another example, when paying for an item through a service associated with the server device 100, the user can set a payment option on the service (such as a bank account based on a specific banking company or a bank account based on a specific card company). card), or accrue points or service credits in advance according to the membership of the service and use it as a default payment option. Therefore, the user can pay for the item through the default payment option. When using the default payment option, some verification process (such as checking the account number or card number) can be omitted, so that the user can pay for the item with a simple process compared to the case of directly using the payment service of an external operator.

In a case where the user selects a default payment option to process payment for an item, once a payment order for an item is approved and processed on the Service, verify and approve whether the corresponding payment order can be processed by the default payment option . After that, verify and approve whether the payment order approved for the default payment option can be sent to the payment service of the external operator corresponding to the default payment option. Accordingly, information about the approved payment order can be transmitted to the payment service of the external operator, and the first transaction corresponding to the payment order for the item can be completed when the corresponding payment order is approved by the payment service of the external operator.

That is, when a user pays for an item by using a predetermined payment option on a service related to the server device 100, in a service domain corresponding to the service, a process for verifying whether the service is approved for the item may be processed. The first approval information of the payment order. When the first approval information is processed, in the payment option field corresponding to the predetermined payment option, the second approval information for verifying whether the payment order of the item is approved on the predetermined payment option can be processed. Thus, processing the second approval information in the payment option field, a third approval for verifying whether the payment order for the item is to be processed for the payment service of the external operator corresponding to the predetermined payment option can be processed through the external operator connection field Information. When the third approval information is processed, information about the payment order for the item can be transmitted to the external operator domain, and the payment order can be approved on the external operator's payment service such that the first transaction is completed.

For example, in operation 303, the server device 100 that acquires information about one or more first payment domains corresponding to the payment process used to process the first transaction may set and manage the information related to the one or more first payment domains Information related to the first transaction of each of them.

According to various exemplary embodiments, in operation 305, for the first domain included in one or more first payment domains, the server device 100 may generate information including first transaction identification information about the first transaction, information about the second transaction The first identification information of a domain and the first payment processing information of the second identification information of a previous domain of the first domain.

For example, in operation 305, the first transaction identification information included in the first payment processing information generated by the server device 100 for a first domain included in one or more first payment domains may include Information about a type of service associated with the device 100.

The service related to the server device 100 can be set to various types based on a type of an item for sale or a category of an item. For example, the service may correspond to a type of item sales service that sells general products such as industrial products or food. In addition, the service may correspond to a type of food delivery service that sells and delivers food or cooked food, such as a dish menu. Since the payment process or transaction is to be classified based on each service type, the transaction identification information used to identify a specific transaction can be configured to include information on the type of service associated with the server device 100 .

For example, in operation 305, the first transaction identification information included in the first payment processing information generated by the server device 100 for the first domain included in the one or more first payment domains may be included in the information in the payment processing information jointly generated by the device device 100 for each of the one or more first payment domains. That is, when generating the payment processing information of each of the one or more first payment domains, the server device 100 can set each payment processing information to include the common first transaction identification information.

For example, in operation 305, the first payment processing information generated by the server device 100 for a first domain included in one or more first payment domains may include various information associated with a payment for an item, such as information about Information on a date or time when the first transaction was processed or information on the payment amount of a payment made through the first transaction.

For example, the first identification information about the first domain included in the first payment processing information may correspond to information for identifying the first domain for which the first payment processing information is generated.

For example, the second identification information about the previous domain of the first domain included in the first payment processing information may correspond to information for identifying a domain corresponding to a previous payment process of the payment process in the first domain, which An object for which first payment processing information is generated in one or more first payment domains corresponding to the payment process through which the first transaction is processed. That is, the server device 100 can generate and manage payment processing information on a domain level, and thus, in order to identify a connection relationship between domains, allow payment processing information on a domain in addition to identification information on a domain Identification information about a previous domain corresponding to a previous process of a domain is also included.

As an example, when the user directly uses the payment service of the external operator to pay for the item, the one or more first payment domains may sequentially include the service domain and the external operator domain. When the first domain related to the first payment processing information corresponds to the service domain, since the service domain corresponds to a domain of the first payment process, the first payment processing information may include information about the service domain corresponding to the first domain The first identification information.

When the first domain associated with the first payment processing information corresponds to the external operator domain, the first payment processing information may contain information about the The first identification information of the external carrier domain and the second identification information about the service domain corresponding to the previous domain of the first domain.

As another example, when a user pays for an item using a predetermined payment option set on a service related to the server device 100, one or more first payment fields may sequentially include a service field, a payment option field, an external Carrier connection domain and external carrier domain. When the first domain related to the first payment processing information corresponds to the service domain, since the service domain corresponds to a domain of the first payment process, the first payment processing information may include information about the service domain corresponding to the first domain first identifying information.

When the first field related to the first payment processing information corresponds to the payment option field, since there is a service field corresponding to the previous process of the payment option field, the first payment processing information may include information on the payment option corresponding to the first field The first identification information of the domain and the second identification information about the service domain corresponding to the previous domain of the first domain.

When the first field associated with the first payment processing information corresponds to the external carrier connection field, since there is a payment option field corresponding to a previous process of the external carrier connection field, the first payment processing information may contain information about the The first identification information of the external carrier connection domain of the first domain and the second identification information about the payment option domain corresponding to the previous domain corresponding to the first domain.

When the first domain associated with the first payment processing information corresponds to the external operator domain, the first payment processing information may contain information about the external operator connection domain corresponding to a previous process of the external operator domain. The first identification information of the external carrier domain of the first domain and the second identification information of the external carrier connection domain corresponding to the previous domain of the first domain.

For example, the first payment processing information may further include information identifying a domain corresponding to a subsequent payment process of the payment process on the first domain corresponding to one of the payment processes through which the first transaction was processed or Among the plurality of first payment domains, an object for which the first payment processing information is generated. That is, the server device 100 can generate and manage payment processing information at a domain level, and thus, in order to identify a connection relationship between domains, allow identification information about a domain and about a previous process corresponding to a domain In addition to identification information for a previous domain, payment processing information for a domain also includes identification information for a subsequent domain corresponding to a subsequent process for a domain.

As an example, when the user directly uses the payment service of the external operator to pay for the item, the one or more first payment domains may sequentially include the service domain and the external operator domain. When the first domain related to the first payment processing information corresponds to the service domain, since the service domain corresponds to a domain of the first payment process, the first payment processing information may include information about the service domain corresponding to the first domain The first identification information further includes identification information about an external operator domain corresponding to a successor domain of the first domain.

When the first domain related to the first payment processing information corresponds to the external operator domain, since there is a service domain corresponding to the previous process of the external operator domain, the first payment processing information may contain information about the The first identification information of the external carrier domain and the second identification information about the service domain corresponding to the previous domain of the first domain.

As another example, when a user pays for an item using a predetermined payment option set on a service related to the server device 100, one or more first payment fields may sequentially include a service field, a payment option field, an external Carrier connection domain and external carrier domain. When the first domain related to the first payment processing information corresponds to the service domain, since the service domain corresponds to a domain of the first payment process, the first payment processing information may include information about the service domain corresponding to the first domain The first identification information further includes identification information about a payment option field corresponding to a subsequent field of the first field.

When the first field related to the first payment processing information corresponds to the payment option field, since there is a service field corresponding to a previous process of the payment option field and an external carrier connection field corresponding to a subsequent process of the payment option field, The first payment processing information may include first identification information about the payment options domain corresponding to the first domain and second identification information about the service domain corresponding to the previous domain of the first domain and additionally include information about the payment option domain corresponding to the first domain. The identification information of the external operator connection domain of the subsequent domain.

When the first field related to the first payment processing information corresponds to the external carrier connection field, since there is a payment option field corresponding to the previous process of the external carrier connection field and a subsequent process corresponding to the external carrier connection field an external carrier domain, so the first payment processing information may include first identification information about an external carrier connection domain corresponding to the first domain and second identification information about a payment options domain corresponding to a previous domain of the first domain and Additionally included is identification information about the external carrier domain corresponding to the successor domain of the first domain.

When the first domain associated with the first payment processing information corresponds to the external operator domain, the first payment processing information may contain information about the external operator connection domain corresponding to the First identification information of an external carrier domain of a domain and second identification information of an external carrier connection domain corresponding to a previous domain corresponding to the first domain.

At this time, in order to generate identification information of each field, information on an element related to each field on the payment process may be used.

For example, identifying information about the service domain used to process approval information for verifying whether a payment order corresponding to a transaction is approved on the service may be generated to reflect identifying information about the user requesting the payment order and about Information about a point in time for which a payment order is requested and, by this, can be distinguished from a service domain related to another transaction.

For example, identifying information about a payment option field used to process approval information for verifying whether a payment order corresponding to a transaction is approved on a predetermined payment option may be generated to reflect information about a user requesting a payment order Identification information and information about a point in time of processing the approval information associated with the payment order on the service domain corresponding to a previous domain, and by this, distinguishable from a payment option domain related to another transaction.

For example, an external carrier connection domain for processing approval information for verifying whether a payment order corresponding to a transaction is approved for a payment service associated with an external carrier corresponding to a predetermined payment option may be generated. identification information to reflect identification information about an external operator receiving information about a payment order and information about a point in time of processing approval information associated with a payment order on a payment option field corresponding to a previous field, And through this, it can be distinguished from an external carrier connection domain related to another transaction.

For example, identification information on the external operator domain corresponding to the payment service of the external operator for receiving information on payment orders may be generated to reflect the identification information on the external operator receiving information on payment orders and on the corresponding Information at a point in time when approval information associated with a payment order is processed on an external operator connection domain of a previous domain, and by this can be distinguished from an external operator domain related to another transaction.

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

For example, the first payment processing information provided by the server device 100 in operation 307 may be generated based on operations 301 to 305 and include various information corresponding to operations 301 to 305 .

Apparently, some pieces of information generated or provided by the server device 100 in connection with the payment processing performed according to the above-mentioned exemplary embodiment to execute the operation of FIG. 3 can be generated or provided in various forms through combinations thereof.

Meanwhile, as above, when a settlement amount of a service is different from a settlement amount of a payment service related to an external carrier corresponding to a payment option used in the service, the server device 100 of FIG. 3 may execute An operation of providing status information associated with payment processing information about one of the domains included in one or more payment domains corresponding to a transaction with a difference in settlement amount, as described with reference to FIG. 4 . Here, the difference in the settlement amount may refer to a payment amount based on a payment settlement for an item among services related to the server device 100 that provides a sale service of various items and a payment amount corresponding to the amount used by a user for the service. A discrepancy between a payment amount in a payment settlement of an item in a payment service of an external operator in a payment option of payment for an item. Additionally, a discrepancy in the settlement amount that occurs in a particular transaction may indicate that an error occurred in processing a domain of one or more payment domains corresponding to the payment process through which the particular transaction was processed.

FIG. 4 illustrates a method of operation of the server device 100 for providing status information associated with payment processing information associated with one of the payment domains or domains included in a transaction corresponding to a transaction in which a difference in settlement amount occurs. One schema.

Referring to FIG. 4, the server device 100 may provide status information associated with payment processing information for a domain. In order to perform an operation of providing state information, when a settlement amount of a service is different from a settlement amount of a payment service related to an external carrier corresponding to a payment option used in the service, the server device 100 may In operation 401, it is determined that a second transaction corresponding to a difference in the settlement amount is determined, in operation 403 second transaction identification information about the second transaction is identified, in operation 405 the information corresponding to the second transaction identification information for processing the second transaction based on the second transaction identification information is identified. One or more second payment domains in one payment process of two transactions, in operation 407, for the second payment processing information generated for one of the second domains included in the one or more second payment domains, identify whether the indication includes Status information is related to the third identification information of the previous domain of the second domain, and in operation 409, the status information is provided.

For example, the status information provided by the server device 100 in operation 409 may be information generated for the second payment processing information based on the processing completed for the second transaction.

For example, the operation of the server device 100 of FIG. 4 may correspond to when the settlement amount of a service is different from the settlement amount of a payment service associated with an external operator corresponding to a payment option used in the service, An operation performed to track a field in which an error occurred during payment processing of a transaction corresponding to a discrepancy in the settlement amount. According to the operation described with reference to FIG. 3 , the server device 100 can verify whether an error occurs based on whether identification information on a previous domain is correctly included in payment processing information generated for each domain. In other words, when the identification information on the previous domain is not included in the payment processing information on one of the one or more payment domains included in the transaction corresponding to the difference in the settlement amount, the server device 100 may determine that the corresponding domain and a preceding field of the corresponding field is an error occurrence field in which an error occurs.

For example, the state information provided by server device 100 in operation 409 may also include information about the successor of the second domain in addition to identification information about the previous domain of the second domain contained in one or more second payment domains. Domain identification information is as described with reference to FIG. 3 . In this case, the server device 100 can verify whether an error occurs based on whether identification information on a previous domain and identification information on a subsequent domain are correctly included in the payment processing information generated for each domain. In other words, when identification information on a previous domain and identification information on a subsequent domain are not included in the payment processing information on one of the one or more payment domains included in the transaction corresponding to the difference in the settlement amount The server device 100 may determine that the corresponding domain and a previous domain or a subsequent domain of the corresponding domain is an error occurrence domain in which an error occurs.

At this time, the server device 100 of FIG. 4 can determine an error occurrence field that causes the difference in the settlement amount and provide error solution information, as described below with reference to FIG. 5 .

FIG. 5 is a diagram illustrating an operation method for the server device 100 to provide error resolution information corresponding to an error occurrence field in which a difference in settlement amount occurs.

Referring to FIG. 5 , the server device 100 may provide error resolution information corresponding to an error domain. In order to perform the operation of providing error resolution information, the server device 100 may generate payment processing information for a specific one of one or more payment domains involved in a transaction corresponding to a difference in the settlement amount. In operation 501, it is verified whether the identification information about one of the previous domains of the specific domain is included in the payment processing information. In operation 503, when the identification information about the previous domain is not included in the payment processing information, it is determined that the specific domain and the previous domain are one. error domain, and provide error resolution information corresponding to the error domain in operation 505 .

For example, with respect to a transaction corresponding to a user's payment order for an item on a service related to the server device 100, when the identification information on a service domain corresponding to a previous domain is not included in the In the payment processing information corresponding to one of the payment processes of a transaction or one of the payment option fields among the multiple payment fields, the server device 100 may determine that the service field or the payment option field is an error in which a difference in the settlement amount occurs Occurrence domain.

At this time, if the identification information on one of the previous domains of the domains is correctly included in the payment processing information on an external carrier connection domain or an external carrier domain for a subsequent payment process corresponding to the payment option domain, then in In the services related to the server device 100, the transaction can be considered as a failure, so that the purchase confirmation, shipment and delivery process of an item can not proceed. However, in a payment service of an external operator, the transaction may be processed as complete, and the external operator may charge a payment amount to the user who paid for the item. Therefore, the server device 100 can provide error resolution information including refunding the payment amount to the user or canceling the payment on the payment service side of the external 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 the identification information about a payment option field corresponding to a previous field is not included in the corresponding In the payment process information of one or more payment domains of the external operator connection domain in the payment process of a transaction, the server device 100 can determine that the payment option field or the external operator connection domain is a difference in the settlement amount. One of the domains where the error occurred.

At this time, if the identification information on the previous domain is correctly included in the payment processing information on the external carrier domain corresponding to the subsequent payment process of the external carrier connection domain, in the service related to the server device 100, The transaction can be considered a failure so that the purchase confirmation, shipment and delivery process of an item cannot proceed. However, in the payment service of the external operator, the transaction may be processed as completed, and the external operator may charge a payment amount to the user who paid for the item. Therefore, the server device 100 can provide error resolution information including refunding the payment amount to the user or canceling the payment on the payment service side of the external 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 the identification information on the domain of the external operator corresponding to the previous domain is not included in the payment in accordance with the corresponding transaction In the payment processing information of the external operator connection domain among one or more payment domains, the server device 100 may determine that the external operator connection domain or the external operator domain is an error occurrence domain where a difference in settlement amount occurs.

At this point, the external operator domain may correspond to one of the final stages of the payment process. Thus, if identifying information about the previous domain is incorrectly included in the external operator domain, the transaction may be processed as a failure in one of the external operator's payment services. In contrast, in the service related to the server device 100, it can be determined that there is no abnormality in the service field, the payment option field, and the external carrier connection field, and the transaction can be processed as completed. In this case, the external carrier may not collect the payment amount from the user who paid for the item, although the purchase confirmation, shipping and delivery process of the item may proceed in response to completion of payment processing on the service. Therefore, the server device 100 can provide error resolution information including contents instructing the external operator to collect the payment amount from the user.

6-8 are diagrams illustrating examples of a user interface (UI)/user experience (UX) for providing payment processing information, according to various exemplary embodiments. For example, the examples of FIGS. 6 to 8 may be the UI/UX of the device 200 interlocked with the server device 100 according to the exemplary embodiment described with reference to FIGS. 3 to 5 . The exemplary embodiments described with reference to the accompanying drawings may be implemented based on the operation of the server device 100 described with reference to FIGS. 3 to 5 .

Specifically, the exemplary embodiment mentioned below of the UI/UX of the device 200 linked with the server device 100 can receive input information and transmit the input information to the device 200 linked with the server device 100 In one implementation, the server device 100 provides information corresponding to the input information to the device 200 linked with the server device 100 based on the operations described with reference to FIGS. Receive information. However, the exemplary embodiments described below in association with UI/UX are not limited thereto and may be implemented in any form that can implement the exemplary embodiments of UI/UX.

6 is a diagram illustrating an example in which a device 200 interlocked with a server device 100 outputs payment processing information about a transaction based on an operation of the server device 100 according to various exemplary embodiments.

As indicated by element numeral 601, the device 200 interlocked with the server device 100 can output summary information about a transaction of a payment order by a user. The summary information may include a transaction identifier (ID) for identifying the transaction, a service type, a payment order ID for identifying the payment order corresponding to the transaction, a payment option for the user, whether to complete or cancel a payment, An external carrier corresponding to the payment option, a processing status of the transaction, an amount of the payment order corresponding to the transaction, and a date of the payment order.

Additionally, as indicated by element numeral 603, the device 200 interlocked with the server device 100 may output payment processing information corresponding to each of one or more payment domains of a payment process through which a transaction is processed. As described in the exemplary embodiments of FIGS. 3-5 , payment processing information for domains may include identification information about a transaction, identification information about domains, and identification of a previous domain or a successor domain for each domain Information. In addition, the payment processing information of each field may also include an amount of the payment order and a date of the payment order corresponding to the transaction.

By using one transaction ID, the server device 100 can integrally manage payment processing information corresponding to each of the payment fields through which the payment process of the transaction is processed. In addition, the server device 100 can determine whether the payment process of each domain is properly processed based on whether the identification information about the previous domain or the subsequent domain of each domain is correctly included in the payment processing information.

7 is a diagram illustrating an example in which a device 200 interlocked with a server device 100 outputs an example of payment processing information including identification information on a domain based on an operation of the server device 100, according to various exemplary embodiments . The example of FIG. 7 is also understood as outputting the payment processing information on FIG. 6 in another form of a UI/UX.

As indicated by element numeral 701, the device 200 interlocked with the server device 100 may output payment processing information regarding one of the service domains of one or more payment domains corresponding to a payment process through which a transaction is processed. The payment processing information about the service domain may include identification information about a payment options domain corresponding to a successor domain and identification information about the service domain. Since the service domain corresponds to the domain of the first payment process used to process the transaction, it can be confirmed that the identification information on a previous domain is set to null.

As indicated by element numeral 703, the device 200 interlocked with the server device 100 may output payment processing information regarding the payment option field corresponding to one or more payment fields of the payment process through which the transaction is processed. In addition to the identification information on the payment option field, the payment processing information on the payment option field may also include identification information on the service domain corresponding to the previous domain and identification information on an external operator connection domain corresponding to the subsequent domain.

As indicated by reference numeral 705, the device 200 interlocked with the server device 100 may output payment processing information regarding an external carrier connection domain among one or more payment domains corresponding to a payment process through which a transaction is processed. In addition to identifying information about the external carrier connection domain, the payment processing information about the external carrier connection domain may also include identification information about the payment options field corresponding to the previous domain and about an external carrier domain corresponding to the subsequent domain identification information.

As indicated by element numeral 707, the device 200 interlocked with the server device 100 may output payment processing information regarding an external carrier domain among one or more payment domains corresponding to a payment process through which a transaction is processed. In addition to identifying information about the external carrier domain, the payment processing information about the external carrier domain may also include identifying information about the external carrier connection domain corresponding to the previous domain. Since the external carrier domain corresponds to the domain used to process the last payment process of the transaction, it can be confirmed that the identifying information on the subsequent domain is set to null.

FIG. 8 is a diagram illustrating a device 200 interlocked with the server device 100 based on an operation output of the server device 100 and one or more of the transactions included in a transaction corresponding to a difference with a settlement amount according to various exemplary embodiments. A schema for an instance of state information associated with payment processing information for one of multiple payment domains.

As indicated by reference numeral 801, the device 200 interlocked with the server device 100 may output information about a service occurring in relation to the server device 100 with a payment service of an external operator corresponding to a payment option of a user. Information on a difference in the settlement amount in one of the transactions. This information may include a settlement amount difference ID for identifying a difference in settlement amount as an item, a service type for a transaction, a transaction ID for identifying a transaction, a payment option for a user, a payment option corresponding to a payment An external carrier of options, a date corresponding to a payment order for a transaction and an amount and a date on which a difference in settlement amount occurs.

In addition, as indicated by element number 803, the device 200 interlocked with the server device 100 may output payment processing corresponding to one of the payment processes through which transactions having differences in settlement amounts are processed or each of a plurality of payment domains Status information associated with the information. Status information associated with the payment processing information may indicate whether identification information about a previous domain or a successor domain of each domain is correctly included in the payment processing information. When the identification information about the previous domain or the subsequent domain is correctly included, it is confirmed that a payment has been normally processed in each domain. When the identification information on the previous domain or the subsequent domain is incorrectly included, it is confirmed that the identification information on the previous domain or the subsequent domain is missing.

As indicated by element number 805, since the confirmation has been approved for payment based on the status information output by the device 200 interlocked with the server device 100, identification information about a service domain corresponding to the previous domain should have been included with a payment option in the payment processing information associated with the domain. However, since identifying information about the service domain is missing, information indicating it may be included. In this case, the server device 100 can recognize this information and identify the payment option field and the service field as an error occurrence field.

The UI/UX of the device 200 linked with the server device 100 described with reference to FIGS. 6 to 8 and the operation of the device 200 linked with the server device 100 can be associated with that of the server device 100 described with reference to FIGS. 3 to 5 . The operation is performed. The examples of UI/UX of FIGS. 6-8 are merely examples for implementing the present invention. Exemplary embodiments of the present invention are not limited to the examples of UI/UX of FIGS. 6-8 and are applicable to any form in which exemplary embodiments of the present invention can be implemented.

The exemplary embodiments of the present invention disclosed in the specification and drawings are only specific examples disclosed to easily explain the technical content of the present invention and further promote the overall understanding of the present invention, and are not intended to limit the scope of the present invention. That is, those skilled in the art will understand that other changes based on the technical idea of the present invention can be made. In addition, the respective exemplary embodiments described above may be implemented in combination with each other as necessary. For example, all exemplary embodiments of the invention may be implemented in combination with a system.

In addition, the method performed by the system or the like according to the present invention can be implemented in the form of program instructions that can be executed by various computer devices and recorded on a computer-readable medium.

As described above, from a specific point of view, various exemplary embodiments of the present invention can be implemented in a computer-readable recording medium using computer-readable codes. A computer readable recording medium is any data storage device that can store data that can be read by a computer system. Examples of the computer readable recording medium may include a read only memory (ROM), a random access memory (RAM), compact disc read only memory (CD-ROM), magnetic tape, floppy disc, optical data storage device, and carrier wave (such as data transmission via the Internet). In addition, the computer-readable recording medium can be distributed throughout a network-connected computer system. Thus, the computer readable code is stored and executed in a distributed fashion. In addition, the functional programs, codes, and code segments for implementing the exemplary embodiments of the present invention can be easily interpreted by those skilled in the field of applying the present invention.

In addition, it should be understood that the apparatuses and methods according to the various exemplary embodiments of the present invention are implemented in the form of hardware, software or a combination of hardware and software. The software may be stored in a volatile or non-volatile storage device such as a storage device such as a ROM or a memory such as a RAM, a memory chip, a device or an integrated circuit or such as a in an optical or magnetic recording storage medium or a machine (for example, a computer) readable storage medium (such as a compact disc (CD), a digital versatile disc (DVD), a magnetic disc or a magnetic tape) without reference to a Swappable or rewritable functions. It should be understood that the methods according to the exemplary embodiments of the present invention may be implemented by a computer comprising a controller and a memory, a tool comprising such a memory or a computer, or the like. A memory system may be an example of a storage medium suitable for storage by a machine readable by a program or programs including instructions for implementing an exemplary embodiment of the invention or storing a program.

Therefore, the present invention covers: a program including program codes for implementing an apparatus or method defined in the appended claims of this specification, and a machine (a computer or similar) readable storage medium, It stores this program. In addition, such a program may be electronically transmitted through any medium, such as a communication signal transmitted over a wired or wireless connection, and the present invention may suitably cover things equivalent thereto.

Although various exemplary embodiments of the present invention have been described above, the exemplary embodiments of the present invention disclosed in the specification and drawings are only disclosed to easily explain the technical content of the present invention and further promote the development of the present invention. Specific examples for general understanding and are not intended to limit the scope of the invention. In addition, the above-mentioned exemplary embodiments of the present invention are examples only, and those skilled in the art should understand that other changes and exemplary embodiments equivalent thereto can be made. Therefore, the true technical scope of the present invention should be defined by the appended patent scope of the invention application.

100: server device 200: A device linked to a server device 210: Input/Output Section 220: Communication part 230: Storage 240: Processor 301: Operation 303: Operation 305: Operation 307: Operation 401: Operation 403: operation 405: operation 407: Operation 409: Operation 501: Operation 503: Operation 505: Operation 601: block 603: block 701: block 703: block 705: block 707: block 801: cube 803: block 805: block

FIG. 1 is a diagram illustrating a payment processing information providing system for implementing an operation method of an electronic device providing payment processing information explanations according to various exemplary embodiments.

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

FIG. 3 is a diagram illustrating an operation method of the server device 100 for providing payment processing information according to various exemplary embodiments.

FIG. 4 illustrates a method of operation of the server device 100 for providing status information associated with payment processing information associated with one of the payment domains or domains included in a transaction corresponding to a transaction in which a difference in settlement amount occurs. One schema.

FIG. 5 is a diagram illustrating an operation method for the server device 100 to provide error resolution information corresponding to an error occurrence field in which a difference in settlement amount occurs.

6 is a diagram illustrating an example in which a device 200 interlocked with a server device 100 outputs payment processing information about a transaction based on an operation of the server device 100 according to various exemplary embodiments.

7 is a diagram illustrating an example in which a device 200 interlocked with a server device 100 outputs an example of payment processing information including identification information on a domain based on an operation of the server device 100, according to various exemplary embodiments .

FIG. 8 is a diagram illustrating a device 200 interlocked with the server device 100 based on an operation output of the server device 100 and one or more of the transactions included in a transaction corresponding to a difference with a settlement amount according to various exemplary embodiments. A schema for an instance of state information associated with payment processing information for one of multiple payment domains.

301: Operation

303: Operation

305: Operation

307: Operation

Claims (15)

A method of providing payment processing information in an electronic device, the method comprising: identifying information about a user's first transaction in a service provided by the electronic device; obtaining information about one or more first payment domains corresponding to a payment process through which the first transaction is processed; generating, for a first domain included in the one or more first payment domains, first transaction identification information about the first transaction, first identification information about the first domain, and the first payment processing information of the second identifying information of one of the preceding domains; and The first payment processing information is provided. The method of claim 1, further comprising: determining a second transaction corresponding to a difference in a settlement amount when a settlement amount of the service differs from a settlement amount of a payment service associated with an external operator corresponding to a payment option used in the service ; identifying second transaction identification information about the second transaction; identifying one or more second payment domains corresponding to a payment process through which the second transaction is processed based on the second transaction identification information; identifying, for second payment processing information generated for a second domain included in the one or more second payment domains, status information indicating whether third identifying information for a previous domain of the second domain is included; and Provide the status information. The method of claim 2, further comprising: When the third identification information is not included in the second payment processing information, determining that the second field and the previous field of the second field is an error occurrence field corresponding to the difference in settlement amount; and An error resolution domain corresponding to the error occurrence domain is provided. The method according to claim 2, wherein the status information is generated based on the completed processing of the second transaction for the second payment processing information. The method of claim 1, wherein the one or more first payment fields are determined based on a payment option of the user for the first transaction. The method of claim 1, wherein the first transaction identification information includes information about a type of the service. The method according to claim 1, wherein the first transaction identification information is included in the payment processing information common to each of the one or more first payment domains. The method of claim 1, wherein the first payment processing information includes information about a date corresponding to the first transaction and an amount corresponding to the first transaction. The method of claim 1, wherein the first payment processing information includes fourth identification information about a subsequent domain of the first domain. The method of claim 9, wherein the one or more first payment fields include: A service domain for processing a first payment order for verifying whether the first transaction is approved in the service when the first payment order is made based on a first payment option of the user set in the service - the first approval information of the payment order; A payment option field, used for processing the second approval information for verifying whether the first payment option is approved for the first payment order when processing the first approval information; an external carrier connection domain for, when processing the second approval information, processing for verifying whether the first payment is approved for a payment service associated with an external carrier corresponding to the first payment option third-party approval information for the order; and An external carrier domain corresponding to the payment service for receiving information about the first payment order when processing the third authorization information. The method of claim 10, wherein the first domain is the service domain, The first identification information is generated based on identification information about the user and information about a point in time when the first payment order is requested, and The fourth identification information corresponds to identification information about the payment option field. The method of claim 10, wherein the first field is the payment option field, The first identification information is generated based on the identification information about the user and information about the point in time when the first approval information is processed, The second identification information corresponds to identification information about the service domain, and The fourth identification information corresponds to identification information about the external operator connection domain. The method of claim 10, wherein the first domain is the external carrier connection domain, the first identification information is generated based on identification information about the external operator and information about a point in time when the second authorization information is processed, The second identification information corresponds to identification information about the payment option field, and The fourth identification information corresponds to identification information about the external operator domain. The method of claim 10, wherein the first domain is the external carrier domain, the first identification information is generated based on identification information about the external operator and information about a point in time when the third authorization information is processed, and The second identification information corresponds to identification information about the external operator connection domain. An electronic device for providing payment processing information, the electronic device comprising: a processor; and one or more memories in which one or more instructions are stored, Wherein when executed, the one or more instructions control the processor to perform: identifying information about a user's first transaction in a service provided by the electronic device; obtaining information about one or more first payment domains corresponding to a payment process through which the first transaction is processed; generating, for a first domain included in the one or more first payment domains, first transaction identification information about the first transaction, first identification information about the first domain, and the first payment processing information of the second identification information of one of the preceding domains; and The first payment processing information is provided.

Images