Integrated payment method and integrated payment module, system, and recording medium utilizing the method
The integrated payment method and module address interoperability issues by standardizing payment requests and responses, enhancing scalability and stability across diverse payment environments.
Patent Information
- Application Number
- KR1020250212706
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2025-08-29
- Filing Date
- 2025-12-29
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2045-12-29
AI Technical Summary
POS systems and kiosks face interoperability challenges due to diverse payment service providers, varying interoperability standards, and complex authentication procedures, leading to increased maintenance and operational risks, especially when network environments and operating systems differ.
An integrated payment method and module that standardizes payment requests and responses using a predefined protocol, selects a target relay server based on transaction attributes, and establishes secure communication, enabling flexible integration across multiple VANs and PGs.
Reduces the need for application modifications and enhances scalability, portability, and operational stability by modularizing payment logic and improving diagnostic and maintainability, while ensuring security and flexibility in handling different payment infrastructure changes.
Smart Images

Figure 112025148269944-PAT00043_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to an integrated payment method and an integrated payment module, system, and recording medium utilizing the same. Background Technology
[0002] In conventional offline or unmanned store environments, POS systems and kiosks are integrated with payment processing infrastructure to provide various payment methods, such as card payments, simplified payments, and the issuance of cash receipts. Generally, when a payment request is generated from a service terminal (POS / kiosk), the request is transmitted to a card company (or financial institution) approval server via a Payment Gateway (PG) that performs payment processing or a Value Added Network (VAN) that relays the payment network, and the approval result is returned in the reverse direction. In this process, the PG can provide merchant settlement, transaction management, and value-added services, while the VAN can handle network-related roles such as relaying approval messages, connecting terminals to the approval network, and managing transaction logs. The card company server performs financial approval functions, including transaction approval, verification of limits and fraudulent use, and the generation of basic data for purchases and billing.
[0003] However, in actual field operations, payment service providers, intermediaries, card companies, and terminal environments are diverse, and interoperability standards, specialized formats, authentication procedures, and error code systems vary by provider. Consequently, terminal manufacturers or store operators may face a burden in reliably maintaining and expanding payment functions. Furthermore, even for the same terminal, interoperability methods can differ depending on the operating system, development language, peripheral configuration, and network environment; thus, additional development, verification, and maintenance are required during the introduction, replacement, upgrade, and fault response processes of payment functions. Moreover, since payment transactions involve sensitive financial processing, it is crucial to meet operational and security requirements such as communication stability, access control, and log management. To this end, it is necessary to establish sophisticated interoperability procedures and management systems among related components. The problem to be solved
[0004] Service terminals such as POS systems and kiosks are connected to credit card company authorization servers via VANs or PGs to provide various payment functions, including card payments, simplified payments, cash receipts, and cancellations. However, in the actual payment ecosystem, VAN / PG operators and the integration specifications, specialized formats, authentication and encryption procedures, error codes, and exception handling methods provided by them vary, and version changes, policy changes, and library replacements occur frequently even within the same operator. As a result, service terminal applications may include integration implementations dependent on specific operators, or face the problem of having to modify or redeploy applications whenever operators are changed or added. Furthermore, in situations where terminal operating environments (operating systems, development languages, process permissions, network restrictions, etc.) are diverse, if payment processing logic is excessively coupled to the application, fault analysis and maintenance become difficult, and operational risks may increase during on-site installation, updates, and rollback processes.
[0005] Accordingly, the present invention aims to provide an integrated payment method that can provide payment functions regardless of the type and change of business operator by accommodating payment requests generated at a service terminal in a standardized manner while absorbing different linkage procedures with multiple VANs (and PGs according to embodiments) into a single structure, and an integrated payment module, system, and recording medium that perform the same.
[0006] The problems of the present invention are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem
[0007] An integrated payment method according to an embodiment of the present invention for solving the above problem comprises: an integrated payment method performed by a payment terminal, the method comprising: a step of generating a payment request; a step of parsing the payment request and normalizing it into standard request data according to a predefined integrated protocol; a step of performing authentication and license verification based on the standard request data; a step of selecting a target relay server among a plurality of relay servers based on the transaction attributes and routing policy of the standard request data; a step of generating a target integration message by converting and mapping the standard request data to correspond to the integration specifications of the selected target relay server; and a step of establishing a secure communication channel with the target relay server and transmitting the target integration message to perform an approval transaction.
[0008] An approval response can be received from the target relay server, and the approval response can be normalized into an integrated response according to the integrated protocol to generate it. The integrated response can be returned to the application that generated the payment request. Log or diagnostic information can be generated and stored based on the processing information of the approval transaction.
[0009] Processing information including transaction success status and observation latency for each relay server can be recorded. Based on the recorded processing information, the estimated transaction success probability and latency for each relay server can be updated using an exponential moving average method. The updated estimates can be reflected in the subsequent selection of target relay servers or the determination of a priority sequence.
[0010] The service module of the above payment terminal can generate a payment request including a payment amount, transaction type, payment method, merchant identification information, and terminal identification information. The payment request can be transmitted to the integrated payment module through an integrated interface.
[0011] The above-described integrated interface may include at least one of (i) a DLL call method that calls a library provided by the above-described integrated payment module, or (ii) an Agent / local daemon method that transmits a request to a local service via localhost-based communication.
[0012] After validating the field format, encoding, length, and required items of the above payment request, the parameters of the above payment request can be mapped to standard request data according to the common schema of a predefined integrated protocol.
[0013] Based on the transaction attributes included in the standard request data and the routing policy of the payment terminal, a priority sequence for multiple relay servers can be determined. A target relay server can be selected according to the priority sequence.
[0014] The above priority sequence can be calculated based on the success probability estimate and the latency estimate for each relay server. The success probability estimate and the latency estimate can be updated based on the processing log of the approval transaction.
[0015] If a timeout or failure occurs during the execution of the above approval transaction, the integrated payment module can re-execute the approval transaction by selecting the next-ranked relay server in the above priority sequence as an alternative path and retransmitting the above target integration message.
[0016] A protocol version can be selected from a set of protocol versions corresponding to the selected target relay server to minimize mapping complexity and security risk. A target integration message can be generated by applying transformation parameters corresponding to the selected protocol version.
[0017] The transformation and mapping complexity can be calculated based on the difference between the common set of fields and the set of fields required by the target relay server. If multiple sets of protocol versions exist for the same relay server, the protocol version that minimizes the transformation and mapping complexity and version risk can be selected. A target integration message can be generated by applying transformation parameters corresponding to the selected protocol version.
[0018] A request feature vector can be generated from the above standard request data. A security satisfaction score for each relay server can be calculated based on the above request feature vector. Only relay servers whose security satisfaction score is greater than or equal to a threshold value can be filtered as eligible candidates. A target relay server can be selected from among the eligible candidates.
[0019] For each of the above-mentioned eligible candidates, the transaction success probability estimate, latency estimate, cost, security / policy risk, and transformation / mapping complexity can be calculated or referenced. A target relay server can be selected such that the evaluation value, to which weights are applied to the above-mentioned calculated values, is minimized.
[0020] An integrated payment module according to an embodiment of the present invention for solving the above problem comprises a processor and a memory for storing commands executed by the processor, wherein the processor is configured to receive a payment request transmitted from a service module of a payment terminal, parse the payment request to normalize it into standard request data according to a predefined integrated protocol, perform authentication and license verification based on the standard request data, select a target relay server among a plurality of relay servers based on the transaction attributes and routing policy of the standard request data, generate a target linkage message by converting and mapping the standard request data to correspond to the linkage specifications of the selected target relay server, and perform an approval transaction by transmitting the target linkage message after establishing a secure communication channel with the target relay server.
[0021] A computer program according to an embodiment of the present invention for solving the above problem is a computer program that performs an integrated payment method when executed by a processor of a payment terminal, and comprises the steps of: generating a payment request when the processor executes; parsing the payment request and normalizing it into standard request data according to a predefined integrated protocol; performing authentication and license verification based on the standard request data; selecting a target relay server among a plurality of relay servers based on the transaction attributes and routing policy of the standard request data; generating a target linkage message by converting and mapping the standard request data to correspond to the linkage specifications of the selected target relay server; and establishing a secure communication channel with the target relay server and transmitting the target linkage message to perform an approval transaction.
[0022] A non-transient computer-readable recording medium according to an embodiment of the present invention for solving the above problem is a non-transient computer-readable recording medium that stores a program for performing an integrated payment method when executed by a processor, wherein the integrated payment method comprises the steps of: generating a payment request; parsing the payment request and normalizing it into standard request data according to a predefined integrated protocol; performing authentication and license verification based on the standard request data; selecting a target relay server among a plurality of relay servers based on the transaction attributes and routing policy of the standard request data; generating a target linkage message by converting and mapping the standard request data to correspond to the linkage specifications of the selected target relay server; and establishing a secure communication channel with the target relay server and transmitting the target linkage message to perform an approval transaction.
[0023] An integrated payment system according to an embodiment of the present invention for solving the above problem comprises an integrated payment terminal including a service module and an integrated payment module, a plurality of relay servers configured to communicate with the integrated payment module via a network, and a card company server configured to communicate with the plurality of relay servers to perform payment approval processing. The service module of the integrated payment terminal is configured to generate a payment request. The integrated payment module of the integrated payment terminal is configured to receive the payment request from the service module, parse the payment request, and normalize it into standard request data according to a predefined integrated protocol. It is configured to perform authentication and license verification based on the standard request data. It is configured to select a target relay server among the plurality of relay servers based on the transaction attributes and routing policy of the standard request data. It is configured to generate a target integration message by converting and mapping the standard request data to correspond to the integration specifications of the selected target relay server. It is configured to establish a secure communication channel with the selected target relay server and transmit the target integration message to the selected target relay server to perform an approval transaction. The selected target relay server transmits the target integration message to the card company server and receives an approval response from the card company server. It is configured to receive and transmit to the integrated payment module, and the card company server is configured to generate the approval response and provide it to the selected target relay server. Effects of the invention
[0024] According to the present invention, a service terminal application can transmit a payment request through a standardized protocol or common interface provided by an integrated payment module, and after the integrated payment module internally selects and routes a target VAN (and PG), it can perform message conversion for each operator, perform authentication procedures, process approval transactions, and return a standardized response result.
[0025] As a result, the need for applications to implement different interoperability specifications for each operator is reduced, and the burden of modifying or redeploying applications is decreased even when new VANs are added or existing VANs are changed.
[0026] In addition, the payment logic is modularized, making it easier to separate the causes of failures (terminal application issues vs. payment integration issues), and enables common log and history management, thereby improving diagnostic and maintainability from an operational perspective.
[0027] Furthermore, in an embodiment where the integrated payment module is implemented as a local service or hardware combination, the payment processing section can be separated outside the terminal or into a separate execution layer to strengthen access control and integrity verification, and security requirements such as license-based execution control, security key protection, and communication path restriction can be systematically reflected.
[0028] Consequently, the present invention enhances the scalability, portability, and operational stability of payment functions, and achieves the effect of providing an integrated payment that can flexibly respond to various changes in payment infrastructure.
[0029] The effects according to the embodiments are not limited to those exemplified above, and a wider variety of effects are included in this specification. Brief explanation of the drawing
[0030] FIG. 1 is a schematic diagram illustrating an integrated payment system according to one embodiment of the present invention. Figure 2 is a block diagram illustrating the functional components of the service module of Figure 1. Figure 3 is a block diagram illustrating the functional components of the integrated payment module of Figure 1. FIG. 4 is a diagram illustrating a method of providing an integrated payment module according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating an integrated payment method according to an embodiment of the present invention. FIG. 6 is a schematic diagram illustrating an integrated payment system according to another embodiment of the present invention, showing a case where the integrated payment module is implemented in hardware. Figure 7 is a block diagram schematically illustrating the hardware configuration of the integrated payment module of Figure 6. Specific details for implementing the invention
[0031] The advantages and features of the present invention and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims.
[0032] Although terms such as "first," "second," etc., are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are used merely to distinguish one component from another. Therefore, it goes without saying that the first component mentioned below may be the second component within the technical scope of the present invention. A singular expression includes a plural expression unless the context clearly indicates otherwise.
[0033] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings. Identical or similar reference numerals are used for identical components in the drawings.
[0034] FIG. 1 is a schematic diagram illustrating an integrated payment system according to one embodiment of the present invention.
[0035] Referring to FIG. 1, the integrated payment system includes an integrated payment terminal (10), a plurality of relay servers (20), and a card company server (30). The integrated payment terminal (10) corresponds to a service terminal (POS or kiosk, etc.) where payment services are performed in a store, and includes a service module (11) and an integrated payment module (12) inside. The relay servers (20) correspond to a group of VAN servers (VAN 1, VAN 2, ..., VAN n) that perform payment approval and relay tasks, and may additionally include a PG server depending on the embodiment. The card company server (30) corresponds to a server system that performs financial approval processing, such as card approval, limit verification, fraud detection, and approval number issuance.
[0036] The service module (11) performs application functions on the integrated payment terminal (10), such as user interface, product / order processing, payment method selection, payment request generation, and payment result reflection. For example, when a user selects card payment, the service module (11) generates a payment request that includes parameters necessary for payment processing, such as the payment amount, transaction type (approval / cancellation / cash receipt, etc.), merchant identification information, and transaction identifier. The service module (11) transmits the generated payment request to the integrated payment module (12) and receives the payment approval result (approval success / failure, approval number, response code / message, original transaction identifier, etc.) returned from the integrated payment module (12), and performs subsequent operations such as printing a receipt, confirming the order, and rolling back the cancellation.
[0037] The integrated payment module (12) is a core component for payment integration located between the service module (11) and multiple relay servers (20). The integrated payment module (12) selects or routes a target relay server (VAN or PG) based on a payment request received from the service module (11), and converts and transmits the request according to the integration specifications of the selected relay server. At this time, the integrated payment module (12) may be configured to internally absorb differences such as different protocols, message formats, authentication procedures, and error code systems for each of the multiple VANs (20). As a result, the service module (11) can perform payment processing solely through integration with the integrated payment module (12) without being dependent on the implementation of a specific VAN or PG. Additionally, the integrated payment module (12) may further include functions such as common processing of payment requests / responses, transaction status management, retry or timeout processing, log recording for fault diagnosis, and masking of sensitive information.
[0038] The relay servers (20) transmit the approval request received from the integrated payment module (12) to the card company server (30) and return the approval response received from the card company server (30) to the integrated payment module (12). In FIG. 1, the bidirectional arrow between the relay servers (20) and the card company server (30) indicates a communication relationship in which approval requests and approval responses are mutually exchanged. According to the embodiment, if a PG is included, the integrated payment module (12) can route to be connected to a card company or another payment network through the PG, and the PG can perform additional functions such as settlement, transaction management, and value-added services. The card company server (30) provides the result of performing approval processing to the relay servers (20), and the relay servers (20) transmit the result to the integrated payment module (12). The integrated payment module (12) organizes the received response into a form suitable for processing by the service module (11) and returns it, thereby enabling the service module (11) to process payment results in a consistent manner even in various VAN / PG environments. As such, FIG. 1 schematically describes a system configuration in which an integrated payment module (12) of an integrated payment terminal (10) is linked with a plurality of VAN / PG (20), and the VAN / PG (20) is linked with a card company server (30) to complete an approval transaction.
[0039] Figure 2 is a block diagram illustrating the functional components of the service module of Figure 1.
[0040] The service module (11) corresponds to an application execution entity responsible for the business flow before and after payment at a service terminal such as a POS or kiosk, and can be configured to receive the user's order and payment input, generate a payment request, transmit a payment processing request to the integrated payment module (12), and reflect the approval result returned from the integrated payment module (12) in subsequent processing such as screen display, receipt printing, order confirmation, or cancellation rollback. Accordingly, the service module (11) provides an execution base that connects the hardware, operating system, and peripheral devices inside the terminal with the payment-related higher-level logic.
[0041] The computation and control layer (110) is a layer that provides the core execution environment of the service module (11). The computation and control layer (110) performs order processing logic executed on the processor (CPU), calculation of payment parameters (amount, VAT, service charge, discount, installment, etc.), transaction state machine (waiting / request / waiting for approval / completed / failed), timeout and retry policies, error handling, and exception flow control. Additionally, when a payment request is generated, the transaction identifier, merchant identification information, payment method classification, approval / cancellation classification, etc. are structured and configured into a form that can be transmitted to the integrated payment module (12), and after receiving an approval response, the approval number, response code, message, original transaction reference information, etc. are reflected in the internal data structure and propagated to subsequent modules. At this time, temporary buffering, local caching, setting value loading, log recording, etc. can also be performed using memory / storage resources.
[0042] The communication and connection layer (120) provides a means of connection for the service module (11) to exchange data with the integrated payment module (12) and external systems. For example, if the integrated payment module (12) is provided in the form of a DLL within the terminal, it may be configured for internal process calls or IPC, and if it is provided in the form of a local service, it may be configured to send and receive requests and responses through local endpoints such as localhost-based HTTP / Socket / WebSocket. Additionally, since communication with the store back office, order server, remote management server, etc., may be required depending on the operating environment, the communication and connection layer (120) may be responsible for network interface control, session management, connection status monitoring, transmission error handling, data serialization / deserialization, etc. This layering separates the payment processing logic itself from the details of the communication implementation, thereby facilitating maintenance and fault analysis.
[0043] The payment-dedicated peripheral layer (130) provides interoperability with payment-related peripheral devices such as a card reader (MSR / IC), NFC reader, PIN Pad, cash receipt device, receipt printer, barcode / QR scanner, cash drawer, or bill / coin deposit / withdrawal module. Since the service module (11) must perform procedures involving physical device operations such as card insertion / tag, password entry, and receipt output according to user input, the payment-dedicated peripheral layer (130) performs device driver calling, port (USB / serial, etc.) control, device status check (connection / error / paper shortage), event reception (card recognition complete, tag detection, signature input), and device-specific error code conversion. This layer serves as a basis for securing input data that is a prerequisite for generating a payment request and executing output actions based on the approval result.
[0044] The user interface layer (140) is responsible for screen configuration and input processing provided by the service module (11). The user interface layer (140) displays UI such as a product selection screen, a payment method selection screen, approval progress status, error notification, and cancellation / retry notification, and receives touch / key input and transmits it to the computation / control layer (110). Additionally, when a payment approval result is received, it clearly indicates approval success / failure and, if necessary, prompts for printing a receipt or reprinting a slip, or processing order confirmation / cancellation. In an unmanned environment, configurations such as guidance voice, progress animation, and a screen to call an administrator in case of failure may also be included.
[0045] The security hardware layer (150) provides hardware-based functions to satisfy the security requirements of payment transactions. The security hardware layer (150) can be implemented as a TPM, Secure Element, security MCU, etc., and performs functions such as key storage, integrity verification, signature / encryption / decryption operations, and debug port control. Since the service module (11) can use authentication tokens, license keys, terminal identification information, etc. during the process of linking with the integrated payment module (12), the security hardware layer (150) can operate in a way that protects these assets and suppresses tampering or unauthorized execution. This serves as a basis for reducing the risk of duplication or tampering due to the nature of the payment function being installed and operated on a field terminal.
[0046] The power and operation stability layer (160) supports stable operation in an environment where the service module (11) is operated continuously for a long time. The power and operation stability layer (160) provides recovery procedures for abnormal situations such as power failure, network disconnection, and device malfunction, and can support service process monitoring (watchdog), restart policies, log preservation, safe shutdown and state rollback in the event of an error. In addition, it is linked with a management function that allows an operator to check the service status on-site and restart or stop it as necessary, thereby reducing payment processing downtime and increasing fault responsiveness.
[0047] In this way, the service module (11) can be configured with functions separated into multiple layers, such as computation / control (110), communication / connection (120), payment-dedicated peripheral device (130), user interface (140), security hardware (150), and power / operation stability (160). With this configuration, the service module (11) can stably perform the generation, input, output, and operation of payment requests, while also providing an execution base that can consistently reflect payment approval processing results through linkage with the integrated payment module (12).
[0048] FIG. 3 is a block diagram illustrating the functional components of the integrated payment module (12) of FIG. 1.
[0049] The integrated payment module (12) is a component located between the service module (11) and a plurality of relay servers (20) (VAN and, according to the embodiment, PG) to provide an intermediate layer so that payment approval transactions are performed even if the service terminal application does not directly implement different interoperability standards for each operator. In FIG. 3, the integrated payment module (12) is divided into a payment core library (210), a local communication-based execution layer (220), an integrated protocol (230), a VAN interoperability layer (240), and an operation / diagnosis layer (250) to encompass the scope of functions regardless of the implementation type (library type / service type / mixed type).
[0050] The payment core library (210) is a layer containing the core processing logic of the integrated payment module (12). The payment core library (210) interprets payment requests transmitted from the service module (11), normalizes payment types (approval / cancellation / cash receipt / simple payment, etc.) and transaction parameters (amount, installment, transaction identifier, merchant information, etc.) into standard data structures, and manages the transaction status. Additionally, the payment core library (210) applies routing policies (settings, merchant mapping, alternative path in case of failure, etc.) to select a target relay server (20) and delegates processing to a downstream layer (240) according to the selected path. According to an embodiment, the payment core library (210) may further include common security and policy functions such as distinguishing execution modes like authentication (Auth) or demo authentication (DemoAuth), license verification, request integrity checks, and applying sensitive information masking rules. This ensures that the payment logic is not distributed within the service module (11) but is concentrated into a single core within the integrated payment module (12).
[0051] The local communication-based execution layer (220) is a layer that provides a form for the integrated payment module (12) to operate as an "execution unit" in a service terminal environment. In one embodiment, the integrated payment module (12) may be provided in the form of a library (DLL) that is called in the same process as the service module (11), and in another embodiment, it may be provided in the form of a local service (e.g., Windows service, daemon) that runs as a separate process. The local communication-based execution layer (220) is particularly useful in the latter case, and receives requests from the service module (11) through communication endpoints such as local host-based HTTP / socket / WebSocket, and returns processing results. This layer is responsible for execution-related controls such as service start / stop, process isolation, permission separation, processing multiple requests (concurrency), timeouts, retries, and queuing, and loads the payment core library (210) to connect for actual payment processing to be performed. As a result, the service module (11) is not dependent on a specific development language or runtime and can call payment functions using only local communication.
[0052] The integration protocol (230) is a layer that defines standardized request and response specifications used between the service module (11) and the integrated payment module (12). The integration protocol (230) specifies fields to be included in the payment request (e.g., payment method, amount, transaction type, terminal / merchant identifier, option value, etc.) and fields to be included in the response (e.g., approval success status, approval number, response code / message, original transaction reference information, etc.), and may include serialization formats (JSON, etc.) and error handling rules. When the integration protocol (230) is provided, the service module (11) only needs to configure the payment request using the "agreement single specification," and regardless of which VAN / PG is selected, it can receive result values in the same form and reuse them for screen display, receipt printing, and order confirmation / cancellation processing. This layer hides implementation details (which VAN is used, how it is converted into a message internally) from the service module (11).
[0053] The VAN integration layer (240) is a layer that performs actual integration with multiple relay servers (20). The VAN integration layer (240) includes an operator-specific adapter (or "VAN company-specific class") to convert standard requests based on the integrated protocol (230) into the specialized format, API call specifications, and authentication procedures required by each VAN / PG, transmits an approval request, and receives a response. At this time, even for the same VAN, specialized specifications may coexist as old / new versions or error code systems may differ, so the VAN integration layer (240) may include version identification and mapping rules. In addition, in some embodiments, integration with a VAN provider agent (e.g., a separate process / driver / device), serial-based device integration, or the establishment of a secure channel (TLS, key exchange, etc.) may be performed. The VAN integration layer (240) constitutes the actual path for approval transactions directed to the card company server (30) and is a core layer that enables the integrated payment module (12) to encompass multiple VANs.
[0054] The operation and diagnosis layer (250) is a layer that supports the installation, operation, maintenance, and failure response of the integrated payment module (12). The operation and diagnosis layer (250) records request / response logs, error logs, performance indicators (latency, failure rate), and transaction identifier-based tracking information, and preserves them as DB logs or file logs if necessary. It can also manage service status (start status, endpoint open status, connection status per VAN), configuration (routing table, merchant mapping, policy value), version information, and update application status. A UI (such as a tray-based tool) that allows an operator to start / stop the service, minimize it, and check its status on-site can be described as an example included in the operation and diagnosis layer (250). Through this layer, when a payment failure occurs, it becomes possible to separate the cause (whether it is a terminal UI / order logic problem, an integrated payment module (12) problem, or a specific VAN integration problem), and on-site response time and maintenance costs are reduced.
[0055] In this way, the integrated payment module (12) is configured by separating the core processing (210), execution form (220), standard interface (230), operator linkage (240), and operation / diagnosis (250), thereby providing a structure in which the service module (11) can call the payment function with a single protocol while flexibly responding to changes in multiple VAN / PG environments.
[0056] FIG. 4 is a diagram illustrating the operation method of an integrated payment module according to an embodiment of the present invention.
[0057] The integrated payment module (12) may be provided in a first method such that a service module (11) or a payment application directly calls the library (DLL) of the integrated payment module (12) to transmit a payment request and receive a payment result.
[0058] In addition, as a second method, the integrated payment module (12) may be operated as an agent or a local daemon (service), and the service module (11) may be provided in a form that transmits and receives requests and responses to the agent through local communication (e.g., localhost-based HTTP / socket / WebSocket, etc.). Accordingly, a suitable method may be selected depending on the operating system, development language, execution authority, distribution policy, etc. of the service terminal, and in both methods, multiple VANs (and PGs according to the embodiment) may be integrated based on an integrated protocol.
[0059] FIG. 5 is a flowchart illustrating an integrated payment method according to an embodiment of the present invention.
[0060] Referring to FIG. 5, the integrated payment method can be implemented in a flow in which, when a service module running on a service terminal such as a POS / kiosk generates a payment request, an integrated payment module (12) receives the request through a single integrated interface / protocol, selects a target relay server among a plurality of VANs (including PG according to the embodiment), performs an approval transaction, and returns an integrated response to the service module. In the following, each step is described in order for convenience of explanation, and some steps may be omitted, merged, or rearranged depending on the implementation type (DLL Call method or Agent / local daemon method), payment type (approval / cancellation / cash receipt, etc.), network status, policy settings, etc.
[0061] In the S301 (Generate Payment Request) step, the service module generates a payment request. The payment request includes parameters such as the payment amount, transaction type (approval / cancellation), payment method, installment / additional options, merchant or terminal identification information, transaction identifier, and request time. Additionally, the service module may determine the request parameters by reflecting card recognition events input from a dedicated payment peripheral device (card reader, NFC reader, PIN Pad, etc.) or user selection results. At this time, the payment request may be generated as an internal data structure of the service module or as a serialized message (JSON, etc.).
[0062] In the S302 (Integrated Interface Call) step, the service module calls the integrated interface. The integrated interface is a common call standard provided by the integrated payment module (12), and depending on the implementation, it may be (i) a method of directly calling a library (DLL), or (ii) a method of transmitting a request to a local service (Agent / daemon) via local communication (localhost-based HTTP / socket / WebSocket, etc.). In the DLL Call method, the service module transmits the payment request through a function call and receives a response in a synchronous / asynchronous manner. In the local service method, the service module transmits the request to a specified endpoint and receives a response based on a session or transaction identifier.
[0063] In the S303 (Local Service Reception and Session Initiation) step, the integrated payment module (12) performs local service reception and session initiation. This step is particularly effective in the local service method, whereby the local service receives a payment request message while in a reception waiting state and creates a transaction-unit session context. The session context may include a request message, processing status, timeout criteria, a retry counter, a log identifier, etc. Meanwhile, in the DLL Call method, since a separate "service reception" is not required, S303 may be omitted or replaced with the "internal transaction context creation" step.
[0064] In the S304 (request parsing and standardization) step, the integrated payment module (12) performs request parsing and standardization. The integrated payment module (12) extracts fields from the received request, validates their validity, and then normalizes them into an internal standard data structure. For example, it maps the format of the amount field, currency unit, payment method code, transaction classification code, etc., to a common schema. Additionally, if execution modes such as demo, development, or operation are provided, the test approval flow or the actual approval flow can be branched according to the mode. If a missing request, format error, or unsupported payment type is detected at this stage, the integrated payment module (12) can generate an error response and return it to the service module.
[0065] In the S305 (Authentication / License Verification) step, the integrated payment module (12) performs authentication / license verification. Authentication / license verification is a procedure to prevent payment functions from being executed in an unauthorized environment or from being duplicated or tampered with, and may include, for example, at least one of verifying the matching of terminal identification information and license key, verifying the signature of a request message, verifying a challenge-response-based token, and checking execution integrity. In addition, in an embodiment where secure hardware (secure element / TPM, etc.) is applied, the key may be stored inside the hardware and configured to perform cryptographic operations on the hardware. If verification fails, the integrated payment module (12) may stop payment processing and return an error response along with a reason code.
[0066] In step S306 (VAN selection and routing), the integrated payment module (12) performs VAN selection and routing. The integrated payment module (12) determines the target VAN (or PG) based on attributes of the payment request (merchant, terminal, payment method, transaction type, etc.) and routing policies (configuration file, table, rule engine, etc.). Routing policies may include priority VANs per merchant, alternative VANs in case of failure, time zone / load-based distribution, and dedicated paths for specific payment methods. Additionally, when a new VAN is added, the system may be configured so that the new path is selected solely by the routing policy without changing the service module.
[0067] In the S307 (VAN-specific conversion and mapping) step, the integrated payment module (12) performs VAN-specific conversion and mapping. The integrated payment module (12) converts standardized internal requests to match the integration specifications of the selected VAN / PG. The conversion may include conversion of the message format, conversion of field names, field lengths, and encodings, insertion of required authentication parameters, and application of an error code mapping table. Even for the same business operator, if the message specifications coexist as old and new versions, the integrated payment module (12) can determine the message version to apply and select a mapping rule based on the terminal environment or server response.
[0068] In step S308 (VAN integration execution), the integrated payment module (12) performs VAN integration execution. The integrated payment module (12) transmits an approval request using at least one of the following methods: calling a VAN provided library / SDK, linking with a VAN agent via IPC, or directly connecting via a socket-based protocol. At this time, the integrated payment module (12) performs communication control such as establishing a connection, maintaining a session, retransmitting, waiting for a response, and handling interruptions, and, if necessary, can reflect the integration status with a payment-dedicated peripheral device (e.g., whether card input is complete).
[0069] In the S309 (execution of secure communication and authorization transaction) step, the integrated payment module (12) handles the execution of secure communication and authorization transactions. This step includes procedures to ensure confidentiality, integrity, and authentication in the authorization network section, and may include, for example, establishing a TLS-based encryption channel, key exchange, adding a message integrity code, and applying a nonce / timestamp for replay prevention. The authorization transaction is transmitted to the card company server via the VAN / PG, and the card company server performs processing such as limit verification, fraud verification, and issuance of an authorization number, and then returns a response. The integrated payment module (12) manages a timeout until the response is received, and when a timeout occurs, it displays the transaction status as "undetermined" to connect to a subsequent inquiry / cancellation procedure.
[0070] In step S310 (receiving response and generating integrated response), the integrated payment module (12) performs receiving a response and generating an integrated response. The integrated payment module (12) interprets the response message received from the VAN / PG, extracts fields such as approval success status, approval number, response code / message, original transaction reference information, and VAN identifier, and normalizes them into a common response format. At this time, different error code systems for each operator can be mapped to a common error code system, and the service module can be generated in a form (such as JSON) that is easy to reuse for screen display and subsequent logic. Sensitive information (such as card numbers) may be partially exposed or treated as non-exposed according to masking rules.
[0071] In step S311 (log / DB recording and diagnostic information generation), the integrated payment module (12) performs log / DB recording and diagnostic information generation. The integrated payment module (12) records transaction identifiers, key request / response fields, processing time, selected routing path, point of error occurrence, number of retries, etc., as logs. Additionally, depending on the operation policy, the information may be stored in at least one of a file log, a local DB, or a remote collection server. The diagnostic information facilitates the analysis of the cause of failure (whether it is a service module problem, an integrated payment module (12) problem, or a specific VAN integration problem) and supports on-site maintenance and quality control.
[0072] In the S312 (client return and result processing) step, the integrated payment module (12) performs client return and result processing. The integrated payment module (12) returns the generated integrated response to the service module through the integrated interface, and the service module performs subsequent processing such as printing a receipt, confirming an order, retrying / canceling in case of failure, and displaying a user guidance screen according to the approval result. In the local service method, the session context can be terminated or maintained for a certain period of time after the response is returned to be used for inquiry / retransmission, and in the DLL call method, memory resources can be released along with the termination of the call context. Thus, the service module can provide payment functions based on the same call standard and the same response structure even in a multiple VAN / PG environment.
[0073] According to the integrated payment method of Fig. 5 as described above, the service terminal-side application can focus on generating payment requests and user interaction, and the integrated payment module (12) absorbs the differences in interoperability between operators, thereby implementing a transaction processing structure that flexibly responds to changes and additions in the payment infrastructure.
[0074] Next, we will explain in detail some steps of the integrated payment method, focusing on steps S306 (VAN selection and routing), S308 (VAN integration execution), and S309 (secure communication and authorization transaction execution).
[0075] - Definition of Terms and Variables
[0076] In one embodiment, the integrated payment module (12) has a request feature vector corresponding to a payment request t. Defined as. Request feature vector It may include, for example, payment type (approval / cancellation), payment method (IC / MSR / NFC, etc.), payment amount, merchant identifier, terminal identifier, time zone, network status, failure history, etc.
[0077] In addition, the integrated payment module (12) has a set of candidates for the relay server (20) that can be linked. Defined as, and each candidate Regarding, the estimated probability of a transaction success , delay time estimate , cost function , Security / Policy Risk , and transformation / mapping complexity Maintains and produces.
[0078] - Filtering Security and Policy Eligible Candidates
[0079] The integrated payment module (12) may set only candidates that satisfy security or policy requirements as eligible candidates before performing VAN selection and routing in step S306. For example, the security satisfaction score of candidate i Define as, and the described requirement level When defined as, the set of eligible candidates It can be defined by the following mathematical formula 1.
[0080]
[0081] In mathematical formula 1 It may be a value calculated by normalizing, for example, (i) whether encryption mode is supported, (ii) key storage method (whether security hardware is used), (iii) whether channel integrity is applied, (iv) whether terminal / module authentication is passed.
[0082] - S306 Step Execution: Objective Function-based VAN Selection and Routing
[0083] The integrated payment module (12) is a set of eligible candidates Among the candidates included, a target VAN can be selected by comprehensively evaluating the probability of payment success, latency, cost, mapping complexity, and risk. For example, the integrated payment module (12) selects candidate i that minimizes the objective function of the following mathematical formula 2. / * You can choose.
[0084]
[0085] Here, α, β, γ, δ, and η are weights, and " " is a term configured such that the penalty increases as the probability of success decreases. In one embodiment, the integrated payment module (12) may apply the following constraint (Equation 3) in addition to Equation 2.
[0086]
[0087] That is, the integrated payment module (12) can implement a routing policy to select the optimal candidate among them, leaving only candidates that satisfy the requirements for response time, success probability, and risk.
[0088] - Perform S307 Step: Formulating VAN-specific conversion / mapping complexity and version selection
[0089] The integrated payment module (12) has a common set of fields defined by an integration protocol with the service module (11). Defined as, and the set of fields required by VAN i It can be defined as. Integrated payment request It is called, and the VAN message (or API request) If so, the VAN conversion function It can be expressed as follows (Mathematical Equation 4).
[0090]
[0091] In mathematical formula 4 It includes VAN-specific conversion parameters such as field mapping rules, encoding rules, length / padding rules, and encryption / decryption / signature rules. In addition, the integrated payment module (12) has conversion / mapping complexity It can be defined as in the following mathematical formula 5 and used as the input for mathematical formula 2.
[0092]
[0093] The first term of mathematical formula 5 refers to a penalty for the existence of common fields that the VAN cannot directly accommodate, and the second term refers to a difficulty penalty in cases where transformations greater than simple copying (1:1), such as table mapping, derivative calculations, and encryption / decryption, are required. The third term This value may reflect the degree to which branch processing increases due to the coexistence of old / new version messages, multiple SDKs, and multiple paths within the same VAN.
[0094] Also, a set of protocol versions for the same VAN i In the case where it is defined as such, the integrated payment module (12) uses the following mathematical formula 6 to define version k / * You can select (Equation 6).
[0095]
[0096] That is, the integrated payment module (12) selects a version with minimum mapping complexity and version risk according to the transaction context, even if it is the same VAN, and a conversion parameter corresponding to the selected version You can configure it to generate a full text by applying it.
[0097] - Perform S308 Step: Optimize integration execution and fallback order in case of failure
[0098] The integrated payment module (12) transmits an approval request to the VAN selected in step S308, but can perform a fallback to sequentially attempt to an alternative VAN in the event of failure or a timeout. To this end, the integrated payment module (12) sets the attempt order as π= It can be defined as follows. In this case, the success probability of each candidate i is , delay time If set as such, the expected success probability of the sequential attempt policy can be expressed by the following mathematical formula 7.
[0099]
[0100] In addition, reflecting the condition that the next step is performed only when the previous step fails, the expected processing time can be expressed by the following mathematical formula 8.
[0101]
[0102] The integrated payment module (12) attempts, for example, in a sequence π such that the success probability is greater than or equal to a threshold while minimizing the expected processing time. / * It can be determined, and this can be defined as in the following mathematical formula 9.
[0103]
[0104] Accordingly, the integrated payment module (12) can be configured to calculate a priority sequence for multiple VANs based on the transaction context rather than selecting a single VAN, and to automatically select an alternative path in the event of failure to complete the payment approval transaction.
[0105] - Update estimate
[0106] The integrated payment module (12) uses the transaction log generated and stored in step S311 to determine the success probability and delay time The estimates of can be updated. For example, when using the Exponential Moving Average (EMA), the observation success status "1 [success]" and the observation latency Based on this, it can be updated with the following mathematical formulas 10 and 11.
[0107]
[0108]
[0109] In mathematical formulas 10 and 11, λ is an update factor between 0 and 1, and can be set to give greater weight to recent transactions.
[0110] FIG. 6 is a schematic diagram illustrating an integrated payment system according to another embodiment of the present invention. FIG. 7 is a block diagram schematically illustrating the hardware configuration of the integrated payment module of FIG. 6.
[0111] Referring to FIGS. 6 and 7, an integrated payment module (12_1) can be implemented in the form of hardware (HW) together with a service module (11) within an integrated payment terminal (10).
[0112] By configuring the integrated payment module (12_1) as hardware, it provides an execution / security boundary separated from the terminal operating system or application environment, and can independently perform functions such as payment integration and license, authentication, and integrity verification. The relay servers (20) communicate with the card company server (30) to receive approval / rejection results, and the integrated payment module (12_1) can normalize the response into an integrated response and provide it to the service module (11).
[0113] The integrated payment module (12_1) may include a host interface unit (401), a protocol bridge unit (402), a control processor unit (403), a memory unit (404), a storage unit (405), an external network communication interface unit (406), a firewall / session control unit (407), a hardware root of trust (408), a secure boot / integrity verification unit (409), a license execution control unit (410), a tamper detection / key erasure unit (411), a management interface unit (412), a display / notification unit (413), a power unit and backup unit (414), and a time synchronization / audit trail support unit (415). The host interface unit (401) transmits and receives payment requests and responses through a wired / wireless connection (e.g., USB, UART, PCIe, Ethernet, etc.) with the service module (11), and the protocol bridge unit (402) performs conversion between the integrated protocol and VAN-specific messages / standards. The control processor unit (403) controls the overall transaction flow, routing, error handling, and retries, and the external network communication interface unit (406) and the firewall / session control unit (407) manage secure communication channels and sessions with VAN / PG. The hardware root of trust (408), the secure boot / integrity verification unit (409), the license execution control unit (410), and the tamper detection / key erasure unit (411) support key protection, prevention of firmware tampering, suppression of unauthorized execution, and response to physical attacks, and the time synchronization / audit trail support unit (415) can enhance the reliability and traceability of transaction logs. With this configuration, the integrated payment module (12_1) can provide integrated interoperability in multiple VAN environments while securing a security and operational foundation separated from the payment terminal environment.
[0114] Meanwhile, the above-described integrated payment method may be implemented in the form of a computer program as a command for implementing the method, and the program is configured to be executed by an integrated payment terminal (e.g., POS, kiosk, PC for terminal control, or processor within the integrated payment module (12)) to perform each step of FIG. 5. For example, the program includes a command to generate or receive a payment request from a service module, a command to call an integrated interface (DLL Call or local service-based interface) to transmit the payment request to the integrated payment module (12), a command to initiate a session and create a transaction context in a local service method, a command to parse the payment request and normalize it into standard request data according to the integrated protocol, and a command to perform authentication and license verification. In addition, the program may include a command to select a target VAN from among a plurality of VAN candidates (including PG according to the embodiment) based on transaction attributes and routing policies, or to determine a priority sequence to sequentially attempt to use an alternative VAN in the event of failure or timeout. Furthermore, the above program includes a command to generate a VAN integration message by converting and mapping standard request data to correspond to the integration specifications of the selected VAN, a command to establish a secure communication channel through an external network communication interface and perform an approval transaction, a command to receive an approval response and normalize it into an integrated response, and a command to return the integrated response to a service module. In this process, the program may further include a command to generate and store logs and diagnostic information including processing paths, processing times, error codes, number of retries, and selected VAN identification information, and may further include a command to update the success probability or latency estimate per VAN based on the transaction log and reflect it in the subsequent routing policy.
[0115] The above program may be stored on a volatile or non-volatile recording medium, and the recording medium may be a non-transitory computer-readable recording medium on which the program is stored. For example, the recording medium may include ROM, RAM, flash memory, SSD, HDD, magnetic disk, optical disk (CD-ROM, DVD, etc.), memory card, embedded storage (eMMC, etc.), or a combination thereof. Additionally, the above program may be provided in the form of a single file or a combination of multiple modules, and may be distributed in the form of a package including a service module-side library, an integrated payment module (12)-side executable file, a local daemon (including Windows services), a configuration file (routing table, mapping rule, version selection rule, etc.), and security components (key, certificate, policy data, etc.). Depending on the embodiment, the above program may be installed and executed inside the terminal, or downloaded and installed / updated via a network, and if the integrated payment module (12) is implemented in hardware, it may be configured to be stored as executable code verified by firmware or a secure boot chain and executed by a control processor. In this way, payment interoperability in a multiple VAN environment can be implemented based on a single integrated protocol and integrated interface by means of a program including the method (command) of FIG. 5 and a recording medium storing the program, and routing, conversion, secure communication, response normalization, and operational diagnosis can be implemented to be executed in a consistent procedure.
[0116] Although embodiments according to the technical concept of the present invention have been described above with reference to the attached drawings, those skilled in the art will understand that the present invention may be implemented in other specific forms without changing its technical concept or essential features. The embodiments described above should be understood as illustrative in all respects and not restrictive. Explanation of the symbols
[0117] 10: Integrated payment terminal 11: Service Module 12, 12_1: Integrated Payment Module 20: Relay servers 30: Credit card company server 110: Computation and Control Layer 120: Communication and Connection Layer 130: Payment-only peripheral layer 140: User Interface Layer 150: Security Hardware Layer 160: Power and Operational Stability Hierarchy 210: Payment Core Library 220: Local Communication-Based Execution Layer 230: Integration Protocol 240: VAN Interconnection Layer 250: Operations and Diagnosis Layer 401: Host Interface 402: Protocol Bridge 403: Control Processor Unit 404: Memory section 405: Storage 406: External network communication interface section 407: Firewall / Session Control Unit 408: Hardware Root of Trust 409: Security Boot and Integrity Verification Unit 410: License Execution Control Unit 411: Tamper Detect / Key Denial 412: Management Interface Section 413: Display / Notification Section 414: Power supply and backup unit 415: Time Synchronization and Audit Trail Support Department
Claims
Claim 1 An integrated payment method performed by a payment terminal, comprising: a step in which a service module of the payment terminal generates a payment request including a payment amount, transaction type, payment method, merchant identification information, and terminal identification information, and transmits the payment request to an integrated payment module through an integrated interface; a step in which the payment request is parsed to verify the validity of the field format, encoding, length, and required items of the payment request, and then normalizes the parameters of the payment request into standard request data according to a common schema of a predefined integrated protocol; a step in which authentication and license verification are performed based on the standard request data, including terminal authentication and license validity verification of the payment module; a step in which a priority sequence for a plurality of relay servers is determined based on the transaction attributes of the standard request data and the routing policy of the payment terminal among a plurality of relay servers, and a target relay server is selected according to the priority sequence; a step in which the standard request data is converted and mapped to correspond to the integration specifications of the selected target relay server to generate a target integration message of the target relay server specifications; and a step in which a secure communication channel is established with the target relay server and the target integration message is transmitted to perform an approval transaction. Claim 2 An integrated payment method according to claim 1, further comprising: receiving an approval response from the target relay server and normalizing the approval response into an integrated response according to the integrated protocol; returning the integrated response to an application that generated a payment request; and generating and storing log or diagnostic information based on processing information of the approval transaction. Claim 3 In claim 2, the step of generating and storing the log or diagnostic information comprises the step of recording processing information including whether a transaction is successful and observation delay time for each relay server, updating the transaction success probability estimate and delay time estimate for each relay server using an exponential moving average method based on the recorded processing information, and reflecting the updated estimate in the subsequent selection of target relay servers or determination of priority sequences. Claim 4 In claim 1, the step of selecting the target relay server is a payment request The request feature vector corresponding to , a set of candidate relay servers that can be integrated , candidate security satisfaction score , required level When saying that, the set of eligible candidates Define according to the following mathematical formula 1, and <Mathematical Formula 1> , the above set of eligible candidates An integrated payment method comprising filtering only relay servers included in as selection candidates for target relay servers. Claim 5 In claim 4, the integrated interface comprises at least one of (i) a DLL Call method that calls a library provided by the integrated payment module, or (ii) an Agent / Local Daemon method that transmits a request to a local service via local host-based communication. Claim 6 In claim 1, the step of generating the target integration message comprises a common field set defined by an integration protocol with a service module. , target relay server The set of fields required by , request for integrated payment , target integration text , the above target relay server The transformation parameters for Let's say, including generating a target linkage message according to the following mathematical formula 2, <Mathematical Formula 2> , integrated payment method. Claim 7 In claim 1, the step of selecting the target relay server comprises the attempt order for a plurality of relay servers. Defined as, and each candidate The estimated success probability of , the delay time estimate When given, the expected success probability of the sequential attempt policy Calculate according to the following mathematical formula 3, and <Mathematical Formula 3> ,expected processing time is calculated according to the following mathematical formula 4, and <Mathematical Formula 4> The above priority sequence <Equation 5> including a step of determining such that, as shown in Equation 5 below, the expected processing time is minimized while the expected success probability is greater than or equal to a threshold and the expected processing time is less than or equal to an allowable limit. , integrated payment method. Claim 8 In claim 7, based on the transaction log generated and stored after the execution of the above approval transaction, each candidate Estimated success probability of and delay time estimates Updating using the exponential moving average method according to the following mathematical formulas 6 and 7, <Mathematical Formula 6> <Mathematical Formula 7> , integrated payment method. Claim 9 An integrated payment method according to claim 7, wherein if a timeout or failure occurs during the execution of the approval transaction, the integrated payment module further includes the step of re-executing the approval transaction by selecting the next-ranked relay server in the priority sequence as an alternative path and retransmitting the target integration message. Claim 10 An integrated payment method according to claim 1, wherein the step of generating the linkage message comprises selecting a protocol version from a set of protocol versions corresponding to a selected target relay server such that mapping complexity and security risk are minimized, and generating a target linkage message by applying a conversion parameter corresponding to the selected protocol version. Claim 11 In claim 10, the step of generating the above-mentioned integration message comprises calculating a transformation and mapping complexity based on the difference between a common set of fields and a set of fields required by a target relay server, selecting a protocol version that minimizes the transformation and mapping complexity and version risk when multiple sets of protocol versions exist for the same relay server, and then generating a target integration message by applying a transformation parameter corresponding to the selected protocol version. Claim 12 In claim 4, the security satisfaction score for each candidate relay server included in the candidate set is calculated based on the degree of correspondence between the request feature vector generated from the standard request data and the security requirement profile of each candidate relay server, and the request feature vector includes features corresponding to at least transaction classification, payment method, merchant identification information and terminal identification information, in an integrated payment method. Claim 13 In claim 4, the step of selecting the target relay server comprises calculating or referencing the transaction success probability estimate, latency estimate, cost, security / policy risk, and transformation / mapping complexity for each of the eligible candidates, and selecting the target relay server such that the evaluation value to which weights are applied to the calculated values is minimized. Claim 14 In the integrated payment module, the processor; An integrated payment module comprising a memory for storing commands executed by the processor, wherein the processor is configured to receive a payment request including a payment amount, transaction type, payment method, merchant identification information, and terminal identification information from a service module of a payment terminal through an integrated interface, and is configured to parse the payment request to verify the validity of the field format, encoding, length, and required items of the payment request, and then normalize the parameters of the payment request into standard request data according to a common schema of a predefined integrated protocol, and is configured to perform authentication and license verification including terminal authentication and license validity verification of the payment module based on the standard request data, and is configured to determine a priority sequence for a plurality of relay servers based on the transaction attributes of the standard request data and the routing policy of the payment terminal among a plurality of relay servers, and is configured to select a target relay server according to the priority sequence, and is configured to convert and map the standard request data to correspond to the integration specifications of the selected target relay server to generate a target integration message of the target relay server specifications, and is configured to perform an approval transaction by transmitting the target integration message after establishing a secure communication channel with the target relay server. Claim 15 delete Claim 16 A non-transitory computer-readable recording medium storing a program that enables an integrated payment method to be performed when executed by a processor, wherein the integrated payment method comprises: a step in which a service module of a payment terminal generates a payment request including a payment amount, transaction type, payment method, merchant identification information, and terminal identification information, and transmits the payment request to an integrated payment module through an integrated interface; a step in which the payment request is parsed to verify the validity of the field format, encoding, length, and required items of the payment request, and then normalizes the parameters of the payment request into standard request data according to a common schema of a predefined integrated protocol; a step in which authentication and license verification are performed based on the standard request data, including terminal authentication and license validity verification of the payment module; a step in which a priority sequence for a plurality of relay servers is determined among a plurality of relay servers based on the transaction attributes of the standard request data and the routing policy of the payment terminal, and a target relay server is selected according to the priority sequence; and a step in which the standard request data is converted and mapped to correspond to the interoperability specifications of the selected target relay server to generate a target interoperability message of the target relay server specifications. A non-transient computer-readable recording medium comprising the step of establishing a secure communication channel with the target relay server and transmitting the target linkage message to perform an approval transaction. Claim 17 In an integrated payment system, an integrated payment terminal including a service module and an integrated payment module; a plurality of relay servers configured to communicate with the integrated payment module via a network; The system includes a card company server configured to communicate with the plurality of relay servers and perform payment approval processing. The service module of the integrated payment terminal is configured to generate a payment request including a payment amount, transaction type, payment method, merchant identification information, and terminal identification information, and to transmit the payment request to the integrated payment module through an integrated interface. The integrated payment module of the integrated payment terminal is configured to parse the payment request, verify the validity of the field format, encoding, length, and required items of the payment request, and then normalize the parameters of the payment request into standard request data according to a common schema of a predefined integrated protocol. It is configured to perform authentication and license verification, including terminal authentication and license validity verification of the payment module, based on the standard request data. Among the plurality of relay servers, it is configured to determine a priority sequence for the plurality of relay servers based on the transaction attributes of the standard request data and the routing policy of the integrated payment terminal, and to select a target relay server according to the priority sequence. It is configured to convert and map the standard request data to correspond to the integration specifications of the selected target relay server to generate a target integration message of the target relay server specifications. The selected target relay An integrated payment system configured to establish a secure communication channel with a server and to perform an approval transaction by transmitting the target integration message to the selected target relay server, wherein the selected target relay server is configured to transmit the target integration message to the card company server, receive an approval response from the card company server, and transmit it to the integrated payment module, and wherein the card company server is configured to generate the approval response and provide it to the selected target relay server.
Citation Information
Patent Citations
System and method for engaging credit card payment services using a plularity of van servers
KR101853343B1
System for executing payment
KR1020080010477A
Operating method of payment terminal, operating method of server and the payment terminal
KR1020210108713A
