Payment capability expansion processing method, device and equipment

Abstract

The invention discloses a payment capacity expansion processing method, device and equipment, which are applied to external payment equipment configured for a cash register, and the external payment equipment provides at least one expansion payment mode which is not possessed by the cash register. The method comprises the following steps: determining whether the cash register is in a connected state or not; if yes, a state triggering instruction is sent to the cash register through an HID protocol to trigger the cash register to open a console of the cash register and enter a command input waiting state; the method comprises the steps of sending simulation typing information to a cash register through an HID protocol to trigger the cash register, automatically inputting and executing the simulation typing information in a command input waiting state, and enabling the cash register to obtain and install a payment capacity extension program indicated by the simulation typing information through execution; through interaction with the cash register based on the payment capability extension program, the capability corresponding to the extended payment mode is used for the cash register.

Description

Technical Field

[0001] This specification relates to the field of electronic payment technology, and in particular to a payment capability expansion processing method, apparatus, and device. Background Technology

[0002] In daily life, merchants typically use cash registers deployed at checkout counters to collect payments from customers. These cash registers usually support traditional payment methods such as bank cards, credit cards, and cash. However, with the rise and increasing popularity of new payment methods, such as QR code payments, near-field communication (NFC) based payments, facial recognition payments, and palm-swipe payments, the capabilities and convenience of cash registers are being challenged.

[0003] To fully leverage the existing POS terminals at numerous merchants and promote new payment methods, payment service providers for these new methods have launched various corresponding external payment devices to extend the payment capabilities of POS terminals. This allows POS terminals to indirectly utilize the extended payment capabilities provided by these external payment devices, thereby supporting the corresponding new payment methods. For example, one type of external payment device is a near-field communication (NFC) based payment device, which, by connecting to a POS terminal, extends the POS terminal's NFC-based payment capabilities.

[0004] Since external payment devices and cash registers are often provided by different service providers, payment service providers offering external payment devices, in order to minimize modifications to the cash registers themselves, should primarily install a payment capability extension program provided by the payment service provider on the cash register. Then, the payment capability extension program will handle the interaction with the external payment device on behalf of the cash register, while the cash register's own data will be obtained by the payment capability extension program through methods such as screenshot recognition. This way, the cash register does not need to actively cooperate, which helps reduce the integration cost and increases merchants' willingness to adopt external payment devices.

[0005] Currently, the installation of payment capability extensions is primarily handled by merchants' or payment service providers' own staff, who use a USB drive containing a copy of the extension to plug into the POS terminal and perform the installation. However, in practice, this process is cumbersome for merchants and prone to problems. Having payment service providers send staff to do it is also costly in terms of manpower. Furthermore, subsequent upgrades and maintenance of the payment capability extensions may continue to face these issues.

[0006] Therefore, solutions are needed to improve the access efficiency of external payment devices for cash registers and reduce access costs. Summary of the Invention

[0007] This specification provides one or more embodiments of a payment capability extension processing method, apparatus, and device to solve the following technical problem: the need for a solution that helps improve the access efficiency of external payment devices for cash registers and reduce access costs.

[0008] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows: This specification provides a payment capability extension processing method according to one or more embodiments, applied to an external payment device configured for a cash register, wherein the external payment device provides at least one extended payment method not present in the cash register itself, and the method includes: Determine whether the connection to the cash register is established. If so, a status trigger command is sent to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; The cash register is sent simulated typing information via the HID protocol to trigger it. In the command input waiting state, the simulated typing information is automatically entered and executed. Through this execution, the cash register acquires and installs the payment capability extension program indicated by the simulated typing information. By interacting with the cash register based on the payment capability extension program, the capabilities corresponding to the extended payment method are used for the cash register.

[0009] This specification provides one or more embodiments of a payment capability extension processing apparatus, applied to an external payment device configured for a cash register, wherein the external payment device provides at least one extended payment method not present in the cash register itself, and the apparatus includes: The connection status confirmation module determines whether the connection with the cash register is established. If the input status trigger module is active, it sends a status trigger command to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state. The simulated keying execution module sends simulated keying information to the cash register via the HID protocol to trigger the cash register to automatically input and execute the simulated keying information in the command input waiting state. Through the execution, the cash register obtains and installs the payment capability extension program indicated by the simulated keying information. The extended capability module interacts with the cash register based on the payment capability extension program to use the capabilities corresponding to the extended payment method for the cash register.

[0010] This specification provides one or more embodiments of a payment capability extension processing device, applied to an external payment device configured for a cash register. The external payment device provides at least one extended payment method not present in the cash register itself. The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: Determine whether the connection to the cash register is established. If so, a status trigger command is sent to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; The cash register is sent simulated typing information via the HID protocol to trigger it. In the command input waiting state, the simulated typing information is automatically entered and executed. Through this execution, the cash register acquires and installs the payment capability extension program indicated by the simulated typing information. By interacting with the cash register based on the payment capability extension program, the capabilities corresponding to the extended payment method are used for the cash register.

[0011] The above-mentioned at least one technical solution adopted in one or more embodiments of this specification can achieve the following beneficial effects: it can automatically simulate an external payment device as a keyboard, enabling it to send and execute commands to the connected cash register as if they were entered through a keyboard via the HID protocol, so as to automatically bring up the command input interface on the cash register, and further automatically input and execute the command to obtain and install the payment capability extension program, thereby conveniently completing the installation of the payment capability extension program on the cash register, and thus enabling the cash register to use the external payment device smoothly to expand support for more payment methods. This installation scheme does not require the payment service provider to send staff to the site, nor does it require merchants to perform cumbersome operations, does not require a USB flash drive, is low in cost, high in efficiency, has good reliability, and is also convenient for subsequent upgrades and maintenance. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1A flowchart illustrating a payment capacity expansion processing method provided in one or more embodiments of this specification; Figure 2 Provided for one or more embodiments of this specification Figure 1 A flowchart illustrating the implementation of this method in a scenario where the cash register uses the Windows operating system; Figure 3 A flowchart illustrating a non-pre-emptive payment capability extension program installation process provided for one or more embodiments of this specification; Figure 4 A flowchart illustrating a deferred settlement order processing scheme provided in one or more embodiments of this specification; Figure 5 A schematic diagram of a payment capacity expansion processing device provided for one or more embodiments of this specification; Figure 6 This is a schematic diagram of the structure of a payment capability expansion processing device provided for one or more embodiments of this specification. Detailed Implementation

[0014] This specification provides an embodiment of a payment capability expansion processing method, apparatus, device, and storage medium.

[0015] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0016] To address the issues in the background technology, the applicant initially considered remote downloading and installation of the payment capability extension program. This eliminates the need for USB drives and payment service provider personnel, allowing merchants to operate the program themselves on their POS machines. Merchants can open a browser using the POS mouse, then enter the download URL for the payment capability extension program using the keyboard to access the website and obtain the latest version. The download URL can be obtained from the payment service provider's official website. However, this solution proved unsuccessful after trials with some merchants. The reason is that POS operators often only perform routine POS-related operations and are unfamiliar with the additional operations mentioned above. This leads to low efficiency, a high risk of errors, and a fear of making mistakes, resulting in low willingness to participate, let alone subsequent upgrades and maintenance. Moreover, these additional operations remain quite cumbersome.

[0017] Based on this, the applicant further considered having an external payment device simulate keyboard operations (or other human-computer interaction devices such as a mouse) to automate the keyboard operations that originally needed to be performed on the cash register. This would send corresponding simulated human-computer interaction commands via the HID protocol and automatically install payment capability extension programs on the cash register. This would eliminate the need for merchants to perform these operations themselves, thus solving the aforementioned problems.

[0018] Based on this overall approach, the solution proposed in this application will be further explained below.

[0019] Figure 1 This is a flowchart illustrating a payment capability extension processing method provided in one or more embodiments of this specification. The method is applied to an external payment device configured for a cash register. The external payment device can provide one or more payment methods not present in the cash register itself, referred to as extended payment methods, thereby enabling the cash register to extend its additional payment capabilities. Examples include near-field communication (NFC) based payment (based on touch sensing recognition), facial recognition payment (based on face recognition), palm recognition payment (based on palmprint recognition), iris recognition payment, etc. Accordingly, the external payment device may be at least one of the following types of devices: NFC-based payment device, facial recognition payment device, palm recognition payment device, iris recognition payment device, etc.

[0020] External payment devices are particularly portable and compact, making them easier to deploy with cash registers. Cash registers are already in use, resulting in lower retrofit costs. Cash registers and external payment devices can be provided by different service providers (meaning they are not from the same company). For example, the external payment device might be provided by a third-party payment service provider, while the cash register might be provided by a traditional financial equipment manufacturer.

[0021] Figure 1 The process includes the following steps: S102: Determine whether the connection with the cash register is established.

[0022] The cash register itself supports one or more relatively standard and universal interfaces, such as Bluetooth, USB (including Type-C), serial port, WiFi, etc. These can be hardware interfaces or wireless interfaces. Of course, the support for different cash registers may vary. In addition, these interfaces may overlap and be supported in different ways. For example, a serial port may also be implemented based on a USB interface, and so on.

[0023] The external payment device needs to be connected to the cash register first for subsequent information exchange. Taking a serial port (such as RS232, RS485, or other standard serial interfaces) as an example, the cash register and the external payment device can be connected via a serial data cable. Of course, a wireless serial port may also be used.

[0024] S104: If so, a status trigger command is sent to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state.

[0025] The HID protocol (Human Interface Device Protocol) is a device communication protocol defined in the Universal Serial Bus standard. It primarily supports data transmission between human-computer interaction devices (such as keyboards, mice, game controllers, and touchscreens) and computers or other host devices. Its core objective is to achieve plug-and-play functionality, allowing these devices to be recognized and used by the operating system without the need for additional drivers. External payment devices and cash registers support the HID protocol; however, the HID protocol alone is insufficient for payment-related business interactions between them. Therefore, payment capability extensions are needed to support higher-level protocols (such as custom lightweight communication protocols) to enable efficient exchange of data with specific business semantics.

[0026] To facilitate more convenient and applicable use of the HID protocol, external payment devices and cash registers can be connected via USB or Bluetooth. In the case of Bluetooth, wireless interaction can be supported through Bluetooth HID.

[0027] In one or more embodiments of this specification, the external payment device may be keyboard- and mouse-free, making it more compact and lightweight for easy portability and deployment, and also lower in cost. The external payment device may simulate a keyboard and / or mouse, automatically sending "instructions as if generated and issued by human operation of the keyboard and / or mouse" to the cash register via the HID protocol, without actually requiring manual operation (e.g., manually clicking the keyboard, manually clicking the mouse, etc.) to send the corresponding instructions.

[0028] For the manual operation part, merchants only need to connect the external payment device to the cash register via wired connection or pair it for wireless connection to ensure the connection status in step S102. The subsequent steps can be automatically executed by the external payment device.

[0029] In one or more embodiments of this specification, the external payment device may have pre-built instructions to be sent to the cash register, or these instructions may be automatically generated in real time when they are to be sent. These instructions are automatically sent in a timely manner based on predefined logic; for example, the sending of these instructions may be automatically triggered when the external payment device is first connected to the cash register.

[0030] Alternatively, more flexibly, the payment provider's server can generate at least some of the aforementioned instructions and send them to the external payment device as needed. The external payment device then forwards these instructions to the cash register via the HID protocol. Alternatively, the external payment device can process the received instructions as needed before sending them to the cash register (subsequent simulated input information can also be processed in a similar way, thus fully leveraging the server's advantages). This server-based approach facilitates efficient subsequent upgrades and maintenance, and also allows for parallel service to multiple, numerous, or even massive numbers of external payment devices (corresponding to the same payment service provider) and cash registers (e.g., located at numerous different merchants), thereby more efficiently completing the installation of large-scale payment capability expansion programs.

[0031] In one or more embodiments of this specification, the HID protocol is considered to ultimately simulate sending commands (mainly command-line commands) from the keyboard to the cash register and trigger the execution of the commands to complete the installation of the payment capability extension program. However, cash registers are not typically in a natural state of waiting to receive command lines; therefore, a status trigger command is first sent to the cash register via the HID protocol to trigger entry into this interface, that is, the triggering of the cash register to open its own console and enter a command input waiting state mentioned in step S104. There can be one or more status trigger commands. The specific content of the status trigger commands may differ for different cash register operating systems.

[0032] It should be noted that external payment devices can also simulate a mouse to send commands. However, this method requires more precise determination of the coordinates of the command on the cash register interface, making it more difficult to implement. As for the keyboard simulation solution, since cash registers support some keyboard shortcuts and shortcut combinations, it is relatively easier to issue commands accurately, and the cash register can respond more reliably and correctly. Therefore, this application prefers to have the external payment device simulate a keyboard to issue commands that mimic human keyboard operation.

[0033] S106: Send simulated typing information (essentially an instruction) to the cash register via the HID protocol to trigger the cash register to automatically input and execute the simulated typing information in the command input waiting state. Through the execution, the cash register acquires and installs the payment capability extension program indicated by the simulated typing information.

[0034] In one or more embodiments of this specification, after the cash register enters the command input waiting state and before the external payment device sends simulated keying information, the external payment device may send more instructions to the cash register via the HID protocol, depending on actual needs. For example, it may send a command to trigger the cash register to execute the command first while in the command input waiting state, and then wait for the external payment device to send further simulated keying information. Simulated keying information, in form, appears to be an executable command entered via a keyboard, but in reality, it is sent via simulated keyboard input; therefore, it is simply referred to here as "simulated keying."

[0035] The simulated input information can include the download address of the payment capability extension. In response to the execution of the simulated input information, the cash register automatically downloads the payment capability extension from the download address and automatically installs the downloaded payment capability extension, avoiding tedious manual operations, such as eliminating the need for manual input of the download address.

[0036] S108: By interacting with the cash register based on the payment capability extension program, the capabilities corresponding to the extended payment method are used for the cash register.

[0037] After successful installation on the cash register, the payment capability extension program can be used to conduct higher-level protocol business interactions between the external payment device and the cash register. For example, based on the cashier's specified business operation on the cash register, payment-related information (such as the amount to be paid, payment interface call request, member number, or auxiliary screenshots) can be transmitted to the external payment device to trigger the external payment device to use its supported extended payment methods to deduct money from the current user or perform other business processing.

[0038] The specified business operations include, for example, requesting payment, requesting membership login, or requesting registration of biometric information. It should be noted that these business operations can be newly defined based on or beyond the existing business semantics of the cash register, corresponding to new business semantics, through intent recognition or other methods. This firstly extends the functionality of the cash register in terms of operational form, allowing cashiers to primarily operate the cash register itself; the actual functionality is implemented by an external payment device.

[0039] Going forward, if an upgrade to the payment capability extension program is needed, it can be done online based on the existing version's capabilities, or it can continue to use... Figure 1 The solution involves installing a higher version. Of course, the payment capability extension itself may also be divided into different parts; you can install one part based on your actual needs, similar to the solution described above.

[0040] In one or more embodiments of this specification, the risks of interaction reliability are further considered. For example, on the one hand, due to problems such as weak network signals or delays, the instructions automatically entered by the cash register may be incomplete or even incorrect. On the other hand, due to the diverse types of cash registers on the market, some instructions may not be executed correctly, resulting in compatibility issues. Therefore, an exemplary solution is provided here. This includes: determining whether the connection to the cash register is established, wherein the camera of the external payment device is capturing the screen of the cash register; if so, determining the required simulated input information based on the captured screen display content; acquiring the simulated input information and sending it to the cash register via the HID protocol to trigger the cash register to automatically input and execute the simulated input information; through execution, enabling the cash register to acquire and install the payment capability extension program indicated by the simulated input information; and through interaction with the cash register based on the payment capability extension program, using the capabilities corresponding to the extended payment method for the cash register.

[0041] Real-time screen capture analysis based on external devices can promptly detect potential abnormal input situations and make corresponding adjustments, thereby improving reliability. Furthermore, it helps to identify and select more appropriate simulated input information for different cash registers, thus improving compatibility.

[0042] pass Figure 1 This method automatically simulates an external payment device as a keyboard, enabling it to send and execute commands via the HID protocol to the connected cash register as if inputting through a keyboard. This automatically brings up the command input interface on the cash register and further automatically inputs and executes commands to acquire and install the payment capability extension program. This conveniently completes the installation of the payment capability extension program on the cash register, allowing the cash register to smoothly use the external payment device to support more payment methods. This installation solution eliminates the need for payment service providers to send staff to the site, and also eliminates the need for merchants to perform cumbersome operations. It does not require a USB drive, is low-cost, highly efficient, and reliable, and also facilitates subsequent upgrades and maintenance.

[0043] based on Figure 1 In addition to the method described herein, this specification also provides some specific implementation schemes and extension schemes of this method, which will be further explained below.

[0044] In one or more embodiments of this specification, in order to more reliably enter the command input waiting state, the above-mentioned state triggering instruction is subdivided into a first shortcut sub-instruction, a second shortcut sub-instruction, and a simulated typing sub-instruction, which are used to sequentially and reliably achieve different segmented objectives.

[0045] In this scenario, after confirming a connection with the cash register, if a payment capability extension program needs to be installed, for external payment devices, a first shortcut sub-command can be sent to the cash register via the HID protocol to trigger the cash register to display its desktop (this can mean keeping the desktop on the foreground; this prevents subsequent commands from being difficult to execute correctly, for example, if the device remains on a specific business page within the cash register software, subsequent commands may not be executed as intended). After successfully displaying the desktop, a second shortcut sub-command is sent to the cash register via the HID protocol to trigger the cash register to display a running window on the desktop (this can mean a window where command lines can be entered and run). After successfully displaying the running window, a simulated typing sub-command is sent to the cash register (this can mean the name of the command-line program to be run, i.e., the console), triggering the automatic input and execution of the simulated typing sub-command in the running window. Through execution, the cash register's own console is opened, entering a command input waiting state.

[0046] The first and second shortcut sub-instructions can be simulated keyboard and / or mouse shortcut operation instructions. Taking the keyboard as an example, the shortcut operation instruction can be the instruction triggered by pressing a specified key combination on the keyboard; taking the mouse as another example, the shortcut operation instruction can be the instruction triggered by clicking a specified system key or clicking a physical button on the mouse that is bound to a specified macro.

[0047] The specific solution described above for entering the command input waiting state is particularly suitable for scenarios where the running window needs to be brought up from the desktop. For example, this would be the case if the cash register uses a Windows operating system. For ease of implementation and greater clarity, one or more embodiments in this specification also provide... Figure 1 See the flowchart illustrating the implementation of the method in this scenario. Figure 2 .

[0048] Figure 2 The instructions in the system do not require manual operation by the merchant. They can be automatically sent to the cash register by an external payment device through the HID protocol, simulating keyboard input.

[0049] First, send the first shortcut sub-command, which is a command that simulates the keyboard shortcut "win+d". The cash register will then respond to this command and switch to the desktop. Then, send the second shortcut sub-command, which is a command that simulates the key combination "win+r" on the keyboard. The cash register will respond to the command and pop up a run window on the desktop. In the input box of the run window, it will wait to receive the next sub-command. Next, a simulated typing subcommand is sent, specifically the command triggered by simulating keyboard input of the text "CMD" and pressing the Enter key. The cash register then responds to this command, starts the console, and arrives at the "Command Prompt" in the console interface, waiting for command input; it can be considered that it has entered the command input waiting state at this time. Next, a simulated typing message is sent, specifically simulating keyboard input of a specific command line. This simulated typing triggers the execution of the command line, which instructs the download of the corresponding program (i.e., the payment capability extension program) from the specified download address and installs the program.

[0050] based on Figure 2 The solution is simple to operate and can be triggered by an external payment device to execute automatically without manual input. It is more reliable than manual keyboard input and can also perform batch operations with the support of a remote server, making it more efficient.

[0051] Besides cash registers using the Windows operating system, cash registers using other operating systems (such as Linux) can also be handled in a similar way. The main difference lies in the specific content of the corresponding sub-instructions or simulated input information.

[0052] The above mainly considers how to efficiently and automatically install payment capability extension programs for cash registers. Such operations can be performed in advance to prepare for receiving users who may need to use the corresponding extended payment methods.

[0053] However, this application also considers the scenario where the payment capability extension program is not installed in advance, or where the payment capability extension program is not permanently installed on the cash register, which may be necessary in practical applications.

[0054] For example, many cash registers have relatively weak performance (especially some customized small cash registers), and payment capability extension programs may increase the burden on these registers; furthermore, some payment capability extension programs may have many optional modules, and only some modules may be needed in different scenarios; still others may have security policy requirements for external software; and so on. In these cases, there may be the aforementioned needs, and payment capability extension programs may only be considered for installation when extended payment methods are needed, or when extended payment methods are needed frequently, and such installation may only be temporary. This helps to reduce the impact on the cash register, allowing it to perform its original functions more normally.

[0055] To meet these requirements while minimizing disruption to users' access to extended payment capabilities (the availability, usage patterns, and frequency of use can vary significantly across different merchants), this specification provides a flowchart illustrating a non-pre-installed payment capability extension program installation process in one or more embodiments. See [link / reference]. Figure 3 .

[0056] Figure 3 The process includes the following steps: S302: After confirming that the connection with the cash register is established, if a user's payment interaction operation for the external payment device is received, it is determined whether the cash register has installed the payment capability extension program.

[0057] For example, you can use the payment capability extension program on the external payment device itself to try to send a probe message to the cash register to determine if the other party has responded correctly. The cash register needs to have the payment capability extension program installed in order to respond correctly through the payment capability extension program.

[0058] If it is already installed, you can interact normally as described in step S108. However, if it is not installed, the cash register and the external payment device cannot effectively communicate, and the cash register cannot utilize the capabilities of the external payment device. In this situation, since the user is currently waiting to pay at the cash register and wants to use the extended payment methods available on the external payment device, the following special handling is implemented to enable the merchant to complete the transaction normally through the cash register.

[0059] S304: If not, then generate a deferred settlement order for the payment interaction operation.

[0060] In one or more embodiments of this specification, the delayed settlement here refers to the cash register. Compared to the normal checkout process at the cash register, the checkout process for this payment interaction operation will actually be completed more slowly for the merchant. It should be emphasized that, however, this has little impact on the user and may even result in a better experience.

[0061] To further determine the voucher information corresponding to the deferred settlement order (for example, using the order number as voucher information; for enhanced security, this can be encrypted or additional identifying information can be generated), the voucher information can be sent to the cash register via the HID protocol. This voucher information can also be simulated typed information, thus requiring no high-level protocol support. It may include, for example, an identifying string representing the deferred settlement order (which can be unique within the relevant business scope, for example, uniquely identifying an order). This voucher information can be entered into the cash register through simulated keyboard operations, causing the cash register to save the voucher information; for example, by triggering the cash register to open a log or other text file and write the voucher information to it.

[0062] S306: Send a payment success trigger instruction carrying the voucher information corresponding to the deferred settlement order to the cash register via the HID protocol, triggering the cash register to forcibly and successfully end the current cash register process for the user.

[0063] In one or more embodiments of this specification, the cash register has a control that can be triggered to indicate successful payment. This control can be triggered by simulating keyboard and / or mouse operations to automatically and successfully end the payment process. Alternatively, the cashier can manually force the process to end. It should be noted that normally, the payment process is not actually finished because the cash register and external payment device have not completed a full and effective payment transaction; therefore, this is referred to as a forced successful end.

[0064] In some scenarios, cash registers may require a correct response from the server to automatically and successfully end the checkout process. For example, in card payment, the process can only end after receiving a successful transaction notification from the bank or credit card issuer's server. Therefore, to prevent the cash register from being unable to successfully end the checkout process through manual local controls, the checkout method can be forcibly switched to change this state. For instance, the cash register could be automatically switched to cash payment and automatically confirm that the user has successfully paid the outstanding amount in cash. Of course, the user doesn't actually pay with cash; this switch is simply to facilitate a forced and successful end to the checkout process.

[0065] S308: Request the payment provider's server to send the status trigger command and the simulated input information; or, it may only request a portion of the command, with the remainder obtained and sent locally by the external payment device.

[0066] To facilitate normal business interactions between the POS terminal and external payment devices for deferred settlement orders and to ensure the complete fulfillment of related tasks such as correct settlement, the POS terminal needs to install a payment capability extension program. Therefore, it can actively request the server to perform the installation. Here, we take the server issuing a command to trigger the installation as an example. Of course, it is also possible to use a method where the installation is triggered only by the external payment device. In this case, after the deferred settlement order is generated or the POS process is forcibly and successfully ended, the external payment device can trigger the installation in a timely manner (for example, as soon as possible when idle).

[0067] S310: After the payment capability extension program is installed, the cash register requests the corresponding settlement from the external payment device or its server based on the payment capability extension program and the voucher information.

[0068] The cash register uses the voucher information to indicate the corresponding checkout process and deferred settlement orders. In fact, it belongs to its own business, and therefore needs to complete the settlement correctly to protect the interests of merchants.

[0069] pass Figure 3 The proposed solution allows for more flexible decision-making regarding when to install payment capability extensions, without necessarily requiring them to be installed in advance. Furthermore, payment capability extensions do not necessarily need to be permanently installed on the cash register, thus reducing the burden on the cash register and not affecting users' use of extended payment methods with external payment devices.

[0070] Furthermore, in Figure 3 In this solution, because the payment capability extension program is not installed, the external payment device may not be able to obtain the correct amount to be paid in a timely manner, which may affect the generation of deferred settlement orders. To solve this problem, one or more embodiments of this specification also provide a flowchart of a deferred settlement order processing solution, see [link to flowchart]. Figure 4 .

[0071] Figure 4 The process includes the following steps: S402: After generating a deferred settlement order for the payment interaction operation, determine the estimated first amount to be paid in the deferred settlement order, wherein the first amount to be paid is estimated to be less than the second amount to be paid by the user in this transaction.

[0072] To facilitate differentiation, the amount the user should actually pay in this transaction is referred to as the second outstanding payment amount. However, since the external payment device has not yet installed the payment capability extension program, it may not currently know the second outstanding payment amount. To address this issue, the external payment device conservatively estimates the outstanding payment amount, which is then included in the deferred settlement order as the first outstanding payment amount.

[0073] The desired outcome is that the first outstanding payment amount should not exceed the second outstanding payment amount. However, accurately estimating the second outstanding payment amount may not be easy. Therefore, as a compromise, it is desirable that the estimated first outstanding payment amount is less than and relatively close to the second outstanding payment amount. This ensures that most of the amount is collected on time, protecting the merchant's interests, while also preventing users from being mistakenly overcharged, which would negatively impact the user experience.

[0074] In one or more embodiments of this specification, the external payment device has a camera, and the cash register's corresponding payment-pending goods display stand is within the camera's field of view; based on this, when generating a deferred settlement order for the payment interaction operation, the specific steps include: estimating the price of the goods based on the goods photographed within the field of view; determining a first payment amount that is less than and close to the price based on the price; and generating a deferred settlement order indicating the first payment amount for the payment interaction operation.

[0075] Besides image recognition-based order amount estimation, other methods can also be used, such as estimating based on the user's current shopping history, etc.

[0076] S404: Deduct the first amount to be paid from the user.

[0077] To avoid user confusion, it is also possible to more clearly inform users that only a portion of the amount has been deducted at this time, and the remaining amount will be deducted in due course.

[0078] S406: After requesting the corresponding settlement from the external payment device or its server using the voucher information, the remaining unpaid amount is determined and deducted from the user according to the request, so as to settle the payment to the merchant corresponding to the cash register.

[0079] The unpaid amount, for example, is equal to the difference between the second unpaid amount and the first unpaid amount. Alternatively, assuming the user pays in this situation, to improve the user experience, additional discounts (such as a reduction in the amount) can be given to the user when the payment is made later, then the unpaid amount will be less than the difference between the second unpaid amount and the first unpaid amount.

[0080] pass Figure 4 The proposed solution allows cash registers to temporarily and indirectly rely on the ability to borrow external payment devices to serve users, even if the payment capability extension program has not yet been installed. This is particularly beneficial for cash registers.

[0081] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figure 5 , Figure 6As shown. The apparatus and equipment are capable of performing the above methods and related alternatives accordingly.

[0082] Figure 5 This is a schematic diagram of a payment capability extension processing device provided in one or more embodiments of this specification. It is applied to an external payment device configured for a cash register, wherein the external payment device provides at least one extended payment method not present in the cash register itself. The device includes: The connection status confirmation module 502 determines whether the connection with the cash register is in a connected state. If the input status trigger module 504 is correct, it sends a status trigger command to the cash register via the HID protocol to trigger the cash register to open its own console and enter the command input waiting state. The simulated keying execution module 506 sends simulated keying information to the cash register via the HID protocol to trigger the cash register to automatically input and execute the simulated keying information in the command input waiting state. Through the execution, the cash register obtains and installs the payment capability extension program indicated by the simulated keying information. The extended capability module 508 interacts with the cash register based on the payment capability extension program to use the capabilities corresponding to the extended payment method for the cash register.

[0083] Optionally, the external payment device itself does not have a keyboard and mouse.

[0084] Optionally, the status triggering instruction includes a first shortcut sub-instruction, a second shortcut sub-instruction, and a simulated typing sub-instruction; The simulated typing execution module 506 sends the first shortcut sub-command to the cash register via the HID protocol to trigger the cash register to display the desktop. Send the second shortcut sub-command to the cash register to trigger the cash register to display a running window on the desktop; The simulated typing sub-command is sent to the cash register to trigger the automatic input and execution of the simulated typing sub-command in the running window. Through the execution, the cash register's own console is opened and enters the command input waiting state.

[0085] Optionally, the simulated typing information includes the download address of the payment capability extension program; The simulated input execution module 506 enables the cash register to download the payment capability extension program from the download address and install the payment capability extension program.

[0086] Optionally, there are multiple external payment devices, each corresponding to the same payment provider, and these multiple devices are distributed across multiple different merchants; Before the simulated typing execution module 506 uses the capability corresponding to the extended payment method for the cash register by interacting with the cash register based on the payment capability extension program, it receives the simulated typing information remotely sent by the server of the payment provider. The corresponding triggering of the cash register is completed by forwarding the simulated typing information to the cash register.

[0087] Optionally, the extended capability module 508, after determining whether it is connected to the cash register, if it receives a user's payment interaction operation for the external payment device, determines whether the cash register has installed the payment capability extension program. If not, a deferred settlement order is generated for the payment interaction operation, and the voucher information corresponding to the deferred settlement order is sent to the cash register via the HID protocol, so that after the cash register installs the payment capability extension program, it can use the voucher information to request the corresponding settlement from the external payment device or its server based on the payment capability extension program.

[0088] Optionally, the extended capability module 508 sends a payment success trigger instruction carrying the voucher information to the cash register, triggering the cash register to forcibly and successfully end the current cash register process for the user; The server of the payment provider is requested to send the simulated typing information.

[0089] Optionally, the extended capability module 508 triggers the cash register to automatically switch to cash payment mode and automatically determines that the user has successfully paid the amount to be paid in cash this time.

[0090] Optionally, the extended capability module 508, after generating a deferred settlement order for the payment interaction operation, determines the estimated first amount to be paid in the deferred settlement order, wherein the first amount to be paid is estimated to be less than the second amount to be paid by the user in this transaction. The first amount to be paid will be deducted from the user's account. After requesting settlement from the external payment device or its server using the voucher information, the remaining unpaid amount is determined and deducted from the user based on the request, so as to settle the payment to the merchant corresponding to the cash register.

[0091] Optionally, the external payment device has a camera, and the cash register's corresponding payment item display stand is within the camera's field of view; The extended capability module 508 estimates the price of the product based on the product captured in the field of view; Based on the price, determine a first amount to be paid that is less than and close to the price; A deferred settlement order indicating the first amount to be paid is generated for the payment interaction operation.

[0092] Optionally, the cash register uses a Windows operating system.

[0093] Optionally, the extended payment method includes a near-field communication-based payment method.

[0094] Figure 6 This is a schematic diagram of a payment capability extension processing device provided in one or more embodiments of this specification. It is applied to an external payment device configured for a cash register, wherein the external payment device provides at least one extended payment method not present in the cash register itself. The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: Determine whether the connection to the cash register is established. If so, a status trigger command is sent to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; The cash register is sent simulated typing information via the HID protocol to trigger it. In the command input waiting state, the simulated typing information is automatically entered and executed. Through this execution, the cash register acquires and installs the payment capability extension program indicated by the simulated typing information. By interacting with the cash register based on the payment capability extension program, the capabilities corresponding to the extended payment method are used for the cash register.

[0095] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium for use with an external payment device configured for a cash register. The external payment device provides at least one extended payment method not present in the cash register itself. The medium stores computer-executable instructions configured as follows: Determine whether the connection to the cash register is established. If so, a status trigger command is sent to the cash register via the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; The cash register is sent simulated typing information via the HID protocol to trigger it. In the command input waiting state, the simulated typing information is automatically entered and executed. Through this execution, the cash register acquires and installs the payment capability extension program indicated by the simulated typing information. By interacting with the cash register based on the payment capability extension program, the capabilities corresponding to the extended payment method are used for the cash register.

[0096] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0097] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0098] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0099] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0100] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0101] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0102] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0103] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0104] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0105] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0106] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0107] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0108] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0109] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0110] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0111] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A payment capability extension processing method, applied to an external payment device configured for a cash register, the external payment device providing at least one extended payment method that the cash register itself does not have, the method comprising: Determine whether the cash register is connected; If yes, a status trigger instruction is sent to the cash register through the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; Sending simulated typing information to the cash register through the HID protocol to trigger the cash register, and automatically receiving and executing the simulated typing information in the command input waiting state, so that the cash register acquires and installs the payment capability extension program indicated by the simulated typing information through the execution; By interacting with the cash register based on the payment capability extension program, the capability corresponding to the extended payment method is used for the cash register.

2. According to the method of claim 1, the external payment device itself does not have a keyboard and a mouse.

3. The method of claim 1, wherein the state trigger instruction comprises a first shortcut sub-instruction, a second shortcut sub-instruction, and a simulated typing sub-instruction; The sending of a status trigger instruction to the cash register through the HID protocol to trigger the cash register to open its own console and enter a command input waiting state specifically includes: Sending the first shortcut sub-command to the cash register through the HID protocol to trigger the cash register to display the desktop; Sending the second shortcut sub-instruction to the cash register to trigger the cash register to display a running window on the desktop; The simulated typing sub-instruction is sent to the cash register to trigger the automatic input and execution of the simulated typing sub-instruction in the running window. Through the execution, the cash register's own console is opened to enter a command input waiting state.

4. The method according to claim 1, wherein the simulated input information includes a download address of the payment capability extension program; The step of causing the cash register to obtain and install the payment capability extension program indicated by the simulated input information specifically includes: The cash register is enabled to download the payment capability extension program from the download address and install the payment capability extension program.

5. The method according to claim 1, wherein there are multiple external payment devices corresponding to the same payment provider, and the multiple devices are distributed at multiple different merchants; Before using the capability corresponding to the extended payment method for the cash register by interacting with the cash register based on the payment capability extension program, the method further includes: Receiving the simulated key-in information remotely sent by the server of the payment provider; The corresponding triggering of the cash register is completed by forwarding the simulated input information to the cash register.

6. The method according to claim 1 or 5, after determining whether the cash register is in a connected state, the method further comprises: After determining that the cash register is connected, if a payment interaction operation of the user for the external payment device is received, determining whether the cash register has installed the payment capability extension program; If not, a deferred settlement order is generated for the payment interaction operation, and the credential information corresponding to the deferred settlement order is sent to the cash register through the HID protocol, so that after the cash register installs the payment capability extension program, it can use the credential information to request corresponding settlement from the external payment device or its server based on the payment capability extension program.

7. The method according to claim 6, wherein sending the voucher information corresponding to the deferred settlement order to the cash register specifically comprises: Sending a payment success trigger instruction carrying the credential information to the cash register, triggering the cash register to forcefully successfully end the cash register process for the user; A request is made to the server of the payment provider to send the simulated key-in information.

8. The method according to claim 7, wherein the triggering of the cash register to forcibly successfully end the cash register process for the user comprises: The cash register is triggered to automatically switch to a cash payment mode, and automatically determines that the user has successfully paid the amount to be paid in cash this time.

9. The method according to claim 7, after generating a deferred settlement order for the payment interaction operation, the method further comprises: Determining an estimated first amount to be paid in the deferred settlement order, where the first amount to be paid is estimated to be less than a second amount to be paid that the user should actually pay this time; deducting the first amount to be paid from the user; After using the credential information to request corresponding settlement from the external payment device or its server, the method further includes: Based on the request, the remaining unpaid amount is determined and deducted from the user so as to be settled to the merchant corresponding to the cash register.

10. The method according to claim 7, wherein the external payment device has a camera, and the commodity storage table to be paid corresponding to the cash register is within the viewing range of the camera; The generating of a deferred settlement order for the payment interaction operation specifically includes: estimating the price of the commodity according to the commodity photographed within the framing range; According to the price, determining a first amount to be paid that is smaller than and close to the price; A deferred settlement order indicating the first amount to be paid is generated for the payment interaction operation.

11. The method according to claim 3, wherein the cash register adopts Windows operating system.

12. The method according to any one of claims 1 to 5, wherein the extended payment method includes a payment method based on near field communication.

13. A payment capability extension processing device, applied to an external payment device configured for a cash register, the external payment device providing at least one extended payment method that the cash register itself does not have, the device comprising: A connection status confirmation module determines whether the cash register is in a connected state; The input status trigger module, if yes, sends a status trigger instruction to the cash register through the HID protocol to trigger the cash register to open its own console and enter the command input waiting state; A simulated typing execution module, which sends simulated typing information to the cash register through the HID protocol to trigger the cash register to automatically input and execute the simulated typing information in the command input waiting state, and through the execution, the cash register obtains and installs the payment capability extension program indicated by the simulated typing information; The extended capability using module uses the capability corresponding to the extended payment method for the cash register by interacting with the cash register based on the payment capability extension program.

14. The apparatus as claimed in claim 13, wherein the external payment device itself does not have a keyboard and a mouse.

15. The device of claim 13, wherein the state trigger instruction comprises a first shortcut sub-instruction, a second shortcut sub-instruction, and a simulated typing sub-instruction; The simulated input execution module sends the first shortcut sub-instruction to the cash register through the HID protocol to trigger the cash register to display the desktop; Sending the second shortcut sub-instruction to the cash register to trigger the cash register to display a running window on the desktop; The simulated typing sub-instruction is sent to the cash register to trigger the automatic input and execution of the simulated typing sub-instruction in the running window. Through the execution, the cash register's own console is opened to enter a command input waiting state.

16. The device according to claim 13, wherein the simulated input information includes a download address of the payment capability extension program; The simulated key-in execution module enables the cash register to download the payment capability extension program from the download address and install the payment capability extension program.

17. The apparatus of claim 13, wherein the external payment devices include multiple devices corresponding to the same payment provider, and the multiple devices are distributed at multiple different merchants; The simulated typing execution module receives the simulated typing information remotely sent by the server of the payment provider before the cash register is interacted with based on the payment capability extension program to use the capability corresponding to the extended payment method for the cash register; The corresponding triggering of the cash register is completed by forwarding the simulated input information to the cash register.

18. The apparatus according to claim 13 or 17, wherein the extended capability using module, after determining whether the cash register is in a connected state, if a payment interaction operation of the user for the external payment device is received, determines whether the cash register has installed the payment capability extension program; If not, a deferred settlement order is generated for the payment interaction operation, and the credential information corresponding to the deferred settlement order is sent to the cash register through the HID protocol, so that after the cash register installs the payment capability extension program, it can use the credential information to request corresponding settlement from the external payment device or its server based on the payment capability extension program.

19. The device according to claim 18, wherein the extended capability using module sends a payment success trigger instruction carrying the credential information to the cash register, triggering the cash register to force the cash register to successfully end the cash register process for the user; A request is made to the server of the payment provider to send the simulated key-in information.

20. The device of claim 19, wherein the extended capability utilization module triggers the cash register to automatically switch to a cash payment method, and automatically determines that the user has successfully paid the amount to be paid in cash this time.

21. The apparatus of claim 19, wherein the extended capability using module, after generating the deferred settlement order for the payment interaction operation, determines an estimated first amount to be paid in the deferred settlement order, wherein the first amount to be paid is estimated to be less than a second amount to be paid that the user should actually pay this time; deducting the first amount to be paid from the user; After the corresponding settlement is requested from the external payment device or its server using the credential information, the remaining unpaid amount is determined and deducted from the user according to the request so as to settle the amount with the merchant corresponding to the cash register.

22. The apparatus according to claim 19, wherein the external payment device has a camera, and the commodity storage table to be paid corresponding to the cash register is within the viewing range of the camera; The extended capability using module estimates the price of the commodity according to the commodity photographed within the framing range; According to the price, determining a first amount to be paid that is smaller than and close to the price; A deferred settlement order indicating the first amount to be paid is generated for the payment interaction operation.

23. The device according to claim 15, wherein the cash register adopts Windows operating system.

24. The device according to any one of claims 13 to 17, wherein the extended payment method includes a payment method based on near field communication.

25. A payment capability extension processing device, applied to an external payment device configured for a cash register, the external payment device providing at least one extended payment method that the cash register itself does not have, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Determine whether the cash register is connected; If yes, a status trigger instruction is sent to the cash register through the HID protocol to trigger the cash register to open its own console and enter a command input waiting state; Sending simulated typing information to the cash register through the HID protocol to trigger the cash register, and automatically receiving and executing the simulated typing information in the command input waiting state, so that the cash register acquires and installs the payment capability extension program indicated by the simulated typing information through the execution; By interacting with the cash register based on the payment capability extension program, the capability corresponding to the extended payment method is used for the cash register.

Images