Payment method and device, and storage medium

Abstract

Provided in one or more embodiments of the present description are a payment method, a payment device, and a storage medium. The payment device comprises a near-field communication module and a code scanning module. The payment method is applied to the payment device, and can determine the payment mode of a target device, the target device referring to a terminal device that is close to the payment device and triggers a payment operation. On this basis, when it is determined that the payment mode of the target device is not a code scanning payment mode, a near-field communication function of the near-field communication module is enabled, and then payment is made on the basis of the near-field communication module.

Description

Payment method, device and storage medium TECHNICAL FIELD

[0001] One or more embodiments of the present specification relate to the technical field of payment, and in particular to a payment method, device and storage medium. BACKGROUND

[0002] With the popularity of near field communication (NFC) technology, more and more mobile terminals (such as smart phones, smart watches, etc.) have NFC functions. NFC refers to the transfer of information through electromagnetic induction coupling in the wireless frequency part of the frequency spectrum. In terms of application, it is not only low in cost, but also very convenient, especially in the field of payment. By using NFC technology on traditional card readers, card swipers and other payment devices, users only need to touch or approach the payment device with a mobile terminal with NFC function to complete the payment. The whole process is simple and fast.

[0003] However, due to the diversification of payment modes, there may be interference recognition between the payment mode based on the NFC function and other payment modes in the same payment device.

[0004] SUMMARY

[0005] One or more embodiments of the present specification provide a payment method, device and storage medium to solve the problem of mutual interference between the payment mode based on the NFC function and other payment modes in the payment device.

[0006] In a first aspect, one or more embodiments of the present specification provide a payment method for a payment device, the payment device comprising a near field communication module and a code scanning module, the method comprising: determining a payment mode of a target device, the target device being a terminal device that approaches the payment device and triggers a payment operation; in the case that the payment mode of the target device is not a code scanning payment mode, starting a near field communication function of the near field communication module; and performing payment based on the near field communication module.

[0007] In an optional embodiment, determining the payment mode of the target device comprises: acquiring a first image of the target device; determining a target component in the target device that faces the payment device based on the first image; in the case that the target component is a display screen, determining that the payment mode of the target device is a code scanning payment mode; or in the case that the target component is a backboard, determining that the payment mode of the target device is not a code scanning payment mode.

[0008] In an optional embodiment, determining the payment mode of the target device comprises: acquiring a second image of the target device; determining whether the second image includes an image of a payment identifier; in the case that the second image includes an image of a payment identifier, determining that the payment mode of the target device is a code scanning payment mode; or in the case that the second image does not include an image of a payment identifier, determining that the payment mode of the target device is not a code scanning payment mode.

[0009] In an optional embodiment, determining the payment mode of the target device comprises: determining whether the target device is in a camera mode; in the case that the target device is in a camera mode, determining that the payment mode of the target device is a code scanning payment mode; or in the case that the target device is not in a camera mode, determining that the payment mode of the target device is not a code scanning payment mode.

[0010] In an optional embodiment, determining the payment mode of the target device comprises: determining whether a minimum distance between the target device and the near field communication module is greater than or equal to a first preset distance; in the case that the minimum distance is greater than or equal to the first preset distance, determining that the payment mode of the target device is a code scanning payment mode; or in the case that the minimum distance is less than the first preset distance, determining that the payment mode of the target device is not a code scanning payment mode.

[0011] In an optional embodiment, determining the payment mode of the target device comprises: determining an actual speed at which the target device approaches the payment device; in the case that the actual speed is less than or equal to a preset speed, determining that the payment mode of the target device is a code scanning payment mode; or in the case that the actual speed is greater than the preset speed, determining that the payment mode of the target device is not a code scanning payment mode.

[0012] In an optional embodiment, making a payment based on the near field communication module comprises: sending, by the near field communication module, label information containing payment access information to the target device, so that the target device sends a payment authorization request to a server associated with the payment access information based on the label information; receiving payment identifier information issued by the server based on the payment authorization request; the payment identifier information contains information of a payment identifier corresponding to a payment account of the target device; initiating a payment request to the server according to the payment identifier information, and completing the payment.

[0013] In an optional embodiment, the payment based on the near field communication module comprises: sending, by the near field communication module, label information containing payment access information and collection identification information to the target device, so that the target device sends a payment identification acquisition request to a server associated with the payment access information based on the label information, and the target device initiates a payment request to the server and completes the payment according to information containing a payment identification returned by the server based on the payment identification acquisition request and the collection identification information.

[0014] In an optional embodiment, the payment based on the near field communication module comprises: sending, by the near field communication module, label information containing payment access information and collection identification information to the target device, so that the target device sends a payment identification acquisition request to a server associated with the payment access information based on the label information, and the target device initiates a payment request to the server and completes the payment according to information containing a payment identification returned by the server based on the payment identification acquisition request and the collection identification information.

[0015] In an optional embodiment, the first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are oriented in the same direction, and the distance between the two in the height direction is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

[0016] In an optional embodiment, the first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are coplanar, and the distance between the adjacent edges of the two is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

[0017] In an optional embodiment, in the case that the payment device is oriented towards the user for payment use, the near field communication module is located at one end close to the user, and the code scanning module is located at one end away from the user.

[0018] In a second aspect, one or more embodiments of the present specification provide a payment device, comprising a processor, a near field communication module and a code scanning module, wherein the processor is configured to: determine the payment mode of a target device, the target device being a terminal device close to the payment device and triggering a payment operation; in the case that the payment mode of the target device is not a code scanning payment mode, turn on the near field communication function of the near field communication module; and perform payment based on the near field communication module.

[0019] In an optional embodiment, when determining the payment mode of the target device, the processor is configured to: acquire a first image of the target device; determine a target component in the target device facing the payment device based on the first image; in the case that the target component is a display screen, determine that the payment mode of the target device is a code scanning payment mode; or in the case that the target component is a backboard, determine that the payment mode of the target device is not a code scanning payment mode.

[0020] In an optional embodiment, the processor, when determining the payment mode of the target device, is configured to: acquire a second image of the target device; determine whether the second image includes an image of a payment identifier; in the case that the second image includes an image of a payment identifier, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the second image does not include an image of a payment identifier, determine that the payment mode of the target device is not the code scanning payment mode.

[0021] In an optional embodiment, the processor, when determining the payment mode of the target device, is configured to: determine whether the target device is in a camera mode; in the case that the target device is in the camera mode, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the target device is not in the camera mode, determine that the payment mode of the target device is not the code scanning payment mode.

[0022] In an optional embodiment, the processor, when determining the payment mode of the target device, is configured to: determine whether the minimum distance between the target device and the near field communication module is greater than or equal to a first preset distance; in the case that the minimum distance is greater than or equal to the first preset distance, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the minimum distance is less than the first preset distance, determine that the payment mode of the target device is not the code scanning payment mode.

[0023] In an optional embodiment, the processor, when determining the payment mode of the target device, is configured to: determine an actual speed at which the target device approaches the payment device; in the case that the actual speed is less than or equal to a preset speed, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the actual speed is greater than the preset speed, determine that the payment mode of the target device is not the code scanning payment mode.

[0024] In an optional embodiment, the processor, when performing payment based on the near field communication module, is configured to: send, by the near field communication module, label information containing payment access information to the target device, so that the target device sends a payment authorization request to a server associated with the payment access information based on the label information; receive payment identifier information issued by the server based on the payment authorization request; the payment identifier information contains information of a payment identifier corresponding to a payment account of the target device; initiate a payment request to the server according to the payment identifier information, and complete payment.

[0025] In an optional embodiment, the processor is configured to, when making payment based on the near field communication module, send, by the near field communication module, label information containing payment access information and payment receiving identification information to the target device, so that the target device sends a payment identification obtaining request to a server associated with the payment access information based on the label information, and initiates a payment request to the server and completes payment according to information containing payment identification returned by the server based on the payment identification obtaining request and the payment receiving identification information.

[0026] In an optional embodiment, the processor is further configured to, when the payment mode of the target device is a code scanning payment mode, keep the near field communication function of the near field communication module closed, and make payment by the code scanning module.

[0027] In an optional embodiment, the first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are oriented in the same direction, and the distance between the two in the height direction is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

[0028] In an optional embodiment, the first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are coplanar, and the distance between the adjacent edges of the two is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

[0029] In an optional embodiment, when the payment device is oriented towards the user for payment use, the near field communication module is located at one end close to the user, and the code scanning module is located at one end away from the user.

[0030] In a third aspect, one or more embodiments of the present specification provide a computer readable storage medium, and the computer readable storage medium stores computer program instructions, and the computer program instructions are executed to implement the payment method of the first aspect.

[0031] In summary, the payment method provided by one or more embodiments of the present specification is targeted at a payment device with a specific structure and supporting an NFC-based payment mode and a code scanning payment mode. By identifying the payment mode of the target device, in the case where the payment mode of the target device is not the code scanning payment mode, the near field communication function of the near field communication module is started. This can effectively avoid the near field communication module from misidentifying the NFC-based payment mode for payment, thereby avoiding interference with the code scanning payment mode originally used by the user. As can be seen, the payment method provided by one or more embodiments of the present specification not only improves the accuracy of identifying the payment mode while ensuring low device cost, but also very conveniently solves the problem of payment confusion caused by mutual interference between the NFC-based payment mode and the code scanning payment mode. BRIEF DESCRIPTION OF DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of one or more embodiments of the present specification, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of one or more embodiments of the present specification, and other drawings can be obtained by those skilled in the art without creative labor.

[0033] FIG. 1 is a flowchart of a payment method provided by one or more embodiments of the present specification;

[0034] FIG. 2 is a system architecture diagram of a payment system provided by one or more embodiments of the present specification;

[0035] FIG. 3 is a structural schematic diagram of a payment device used in the payment system of FIG. 2 provided by one or more embodiments of the present specification;

[0036] FIG. 4 is a communication process schematic diagram corresponding to a payment process provided by one or more embodiments of the present specification;

[0037] FIG. 5 is a communication process schematic diagram corresponding to another payment process provided by one or more embodiments of the present specification;

[0038] FIG. 6 is a communication process schematic diagram corresponding to another payment process provided by one or more embodiments of the present specification;

[0039] FIG. 7 is a communication process schematic diagram corresponding to another payment process provided by one or more embodiments of the present specification;

[0040] FIG. 8 is a structural schematic diagram of a setting mode of a near field communication module and a code scanning module in a payment device provided by one or more embodiments of the present specification;

[0041] FIG. 9 is a structural schematic diagram of another arrangement of a near field communication module and a code scanning module in a payment device according to one or more embodiments of the present specification;

[0042] FIG. 10 is a structural schematic diagram of another arrangement of a near field communication module and a code scanning module in a payment device according to one or more embodiments of the present specification;

[0043] FIG. 11 is a system architecture diagram of another payment system according to one or more embodiments of the present specification;

[0044] FIG. 12 is a structural block diagram of a payment device according to one or more embodiments of the present specification. DETAILED DESCRIPTION

[0045] The one or more embodiments of the present specification will be further described in detail by the accompanying drawings and embodiments. The features and advantages of the one or more embodiments of the present specification will become more apparent from these descriptions.

[0046] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations. Although various aspects of embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale.

[0047] Furthermore, the technical features involved in the different implementations of the one or more embodiments of the present specification described below can be combined with each other as long as there is no conflict.

[0048] In order to facilitate understanding, the application scenarios of the technical solutions provided by the one or more embodiments of the present specification will be described first.

[0049] With the continuous development and popularization of Internet mobile payment technology, the mobile payment mode has become the mainstream payment mode in today's society, and more and more mobile applications support mobile payment functions, such as code scanning payment, face scanning payment, etc. In addition, due to the characteristics of low cost, easy application, high security, etc. in the application of near field communication (NFC) technology, NFC technology is also widely used in daily consumption, public transportation and other payment scenarios, for example, using NFC technology on traditional card readers, POS (point of sales) machines and other payment devices to complete payment operations with mobile terminals (smartphones, smartwatches, etc.) supporting NFC functions has become increasingly common, and in order to facilitate user operation, many payment devices also support multiple mobile payment modes for users to choose flexibly. However, in a diversified payment scenario, for a payment device that supports both NFC-enabled payment mode and other payment modes (such as code scanning payment), payment mode interference may occur. For example, in the case where the user wants to make a code scanning payment, the payment device may make a payment based on the NFC function due to the mis-triggering of the NFC function during the code scanning process, thereby affecting the user's payment experience.

[0050] To this end, one or more embodiments of the specification provide a payment method, a payment device and a storage medium for improving the accuracy of the payment device in identifying NFC-enabled payment mode and avoiding adverse user experience caused by payment mode crosstalk.

[0051] It should be noted that in order to solve the problem of interference between NFC-enabled payment mode and other payment modes in the case where the payment device supports multiple payment modes including NFC-enabled payment mode, one or more embodiments of the specification take NFC-enabled payment mode and code scanning payment as examples for illustration, but in application, it is not limited thereto. In addition to NFC-enabled payment mode, the payment device can also support other payment modes, which can be determined according to the actual functions of the payment device, and will not be described in detail here.

[0052] Next, the payment method provided by one or more embodiments of the specification will be described in conjunction with the accompanying drawings.

[0053] FIG. 1 is a flowchart of a payment method provided by one or more embodiments of the specification, which can be used for a payment device including a near field communication module and a code scanning module. As shown in FIG. 1, the payment method includes S102 to S106.

[0054] S102, determine the payment mode of the target device, the target device being a terminal device close to the payment device and triggering a payment operation.

[0055] S104, in a case where the payment mode of the target device is not the code scanning payment mode, starting the near field communication function of the near field communication module.

[0056] S106, performing payment based on the near field communication module.

[0057] In one or more embodiments of the present specification, the payment mode based on the near field communication function is referred to as the NFC-based payment mode (may also be referred to as the NFC function-based payment mode, etc.), and the payment mode based on the code scanning function is referred to as the code scanning payment mode. For ease of illustration, the process of the payment device performing the above payment method is illustrated by taking the above two payment modes as examples, but in the application, the payment device specifically supports which payment modes can be determined according to actual functions. Based on this, the payment device provided by one or more embodiments of the present specification includes a near field communication module and a code scanning module, wherein the near field communication function of the near field communication module is started in a case where the near field communication function is started, and the terminal device identified within the communication distance can be paid in the NFC-based payment mode. The code scanning module is in a default open state, and in a case where a payment identifier is identified, payment can be performed in the code scanning payment mode.

[0058] It should be noted that the specific structure of the payment device will be described separately in subsequent embodiments and will not be described in detail here.

[0059] For ease of illustration, in one or more embodiments of the present specification, the terminal device close to the payment device and triggering the payment operation is referred to as the target device, that is, the target device is about to perform the payment operation with the payment device to complete the payment between the payee and the payer. Based on this, in order to make the NFC-based payment mode and the code scanning payment mode not interfere with each other, the payment mode of the target device is determined during the process in which the target device approaches the payment device. Further, in a case where the payment mode of the target device is determined to be the code scanning payment mode, the near field communication function of the near field communication module is started, and payment is performed based on the near field communication module. The payment mode of the target device refers to the payment mode used by the user when performing the payment operation using the target device. For example, if the user uses the payment code of the payment application to perform the payment operation, the corresponding payment mode is the code scanning payment mode, and if the user uses the NFC function of the smart phone to perform the payment operation, the corresponding payment mode is the NFC-based payment mode.

[0060] In one or more embodiments of the present specification, the specific way in which the payment device determines the payment mode of the target device is not limited, and the following examples are illustratively described by taking the target device as the payer and the payment device as the payee in an actual payment scenario.

[0061] In an actual payment scenario, for the NFC-based payment mode, since the NFC chip is usually built-in in the mobile terminal close to the back plate side, when the user uses the NFC-based payment mode to make payment, the back plate side of the terminal device is close to or attached to the near field communication module of the payment device to complete the payment by data transmission with the near field communication module. For the code scanning payment mode, one way is that the mobile terminal presents the payment code to the payment device, the user directs the display screen of the terminal device to the code scanning module of the payment device, so that the code scanning module recognizes the payment code (such as the payment code, etc.) displayed in the display screen to complete the payment; another way is that the payment device presents the payment code to the mobile terminal, the user opens the camera function of the terminal device to recognize the payment code presented by the payment device to complete the payment.

[0062] Based on this, in an optional way, the first image of the target device can be taken during the target device approaching the payment device, for determining the placement state of the target device relative to the payment device. Based on this, the payment device can first acquire the first image of the target device when determining the payment mode of the target device, and determine the target component of the target device facing the payment device according to the content of the first image. The target component can be the display screen or the back plate of the target device, so that the placement state of the target device relative to the payment device can be determined according to the type of the target component in the first image, and the payment mode of the target device is determined as the code scanning payment mode when the target component in the first image is determined as the display screen; correspondingly, the payment mode of the target device is determined as not the code scanning payment mode when the target component in the first image is determined as the back plate.

[0063] Alternatively, in another optional way, the second image of the target device can be taken during the target device approaching the payment device, for determining whether the target device presents the payment identifier to the payment device. Based on this, the payment device can first acquire the second image of the target device when determining the payment mode of the target device, and then determine whether the image of the payment identifier is included in the second image according to the content of the second image; the payment identifier can be the payment code corresponding to the payment application in the target device. In this way, when the image of the payment identifier is included in the second image, it is determined that the payment mode of the target device is the code scanning payment mode; correspondingly, when the image of the payment identifier is not included in the second image, it is determined that the payment mode of the target device is not the code scanning payment mode.

[0064] In another optional mode, for the case that the payment device presents the collection code to the terminal device, the payment device can first determine whether the target device is in camera shooting mode when determining the payment mode of the target device, and in the case that the target device is in camera shooting mode, determine that the payment mode of the target device is the scan code payment mode; correspondingly, in the case that the target device is not in camera shooting mode, determine that the payment mode of the target device is not the scan code payment mode. Wherein, the specific mode of the payment device to determine whether the target device is in camera shooting mode is not limited in the embodiment, and optionally, the camera shooting mode can be determined by recognizing the flash state of the target device, or the relative position relationship between the camera of the target device and the scan code module of the payment device. Further optionally, the recognition result of the flash state or the camera position can also be obtained through the first image or the second image taken in the process of the target device approaching the payment device, and the specific mode is not limited.

[0065] In actual payment scenarios, whether the user adopts the NFC-based payment mode or the scan code payment mode, the terminal device needs to be placed in the perceptible range of the payment device. For example, for the NFC-based payment mode, the perceptible range of the payment device can be a range formed by the communication distance of the near field communication module, and for the scan code payment mode, the perceptible range of the payment device can be a range formed by the maximum distance at which the scan code module can recognize the payment identifier (such as a payment code). Generally, the communication distance of the near field communication module is less than the maximum distance at which the scan code module can recognize the payment identifier. In order to avoid payment crosstalk between the NFC-based payment mode and the scan code payment mode, a first preset distance greater than the communication distance of the near field communication module and less than the maximum distance at which the scan code module can recognize the payment identifier (such as a payment code) can be preset in the embodiment, so as to more accurately determine the payment mode used by the user.

[0066] Wherein, the communication distance of the near field communication module refers to the maximum distance at which the near field communication module can establish effective communication with other devices. That is, if the distance between the near field communication module and other devices is greater than the communication distance of the near field communication module, the near field communication module and other devices cannot establish effective communication. The maximum distance at which the scan code module can recognize the payment identifier refers to the distance between the payment identifier and the scan code module, and if the distance is greater than the maximum distance, the scan code module cannot effectively recognize the payment identifier.

[0067] Based on this, in another optional mode, the payment device can first determine whether the minimum distance between the target device and the near field communication module is greater than or equal to the first preset distance when determining the payment mode of the target device, and in the case where the minimum distance between the target device and the near field communication module is greater than or equal to the first preset distance, determine that the payment mode of the target device is the code scanning payment mode; correspondingly, in the case where the minimum distance between the target device and the near field communication module is less than the first preset distance, determine that the payment mode of the target device is not the code scanning payment mode.

[0068] Of course, in order to improve accuracy, in the case where the minimum distance between the target device and the near field communication module is greater than or equal to the first preset distance, it can be further determined whether the minimum distance between the target device and the code scanning module is less than or equal to the maximum distance at which the code scanning module can identify the payment identifier, and in the case where the minimum distance between the target device and the code scanning module is less than or equal to the maximum distance at which the code scanning module can identify the payment identifier, determine that the payment mode of the target device is the code scanning payment mode. The specific determination method can be selected according to actual needs.

[0069] In actual scenarios, the speed at which the terminal device moves in different situations is usually different during the process of the terminal device approaching the payment device. For example, for the case where the user holds the terminal device and passes by the payment device, due to the user's walking, arm swinging and other actions, the speed at which the terminal device moves is relatively large, and for the case where the user uses the terminal device to perform a payment operation, the user will stay near the payment device and accurately move the terminal device into the perceptible range of the payment device, so the speed at which the terminal device moves is relatively small.

[0070] Based on this, for the case where the terminal device approaches the payment device and performs a payment operation, the corresponding preset speed can be set for the process of the terminal device moving, and the actual value of the preset speed is not limited, which can be the average speed of the user holding the terminal device to approach the payment device and perform a payment operation in an actual payment scenario. Further optionally, the preset speeds corresponding to the code scanning payment mode and the NFC-based payment mode can be the same or different, which is not limited here. In actual payment scenarios, since the NFC-based payment mode is more efficient than the code scanning payment mode, the preset speed corresponding to the NFC-based payment mode can also be set to be larger when setting.

[0071] In this embodiment, for ease of illustration, the preset speed corresponding to the code scanning payment mode is taken as an example for illustration as a benchmark. Based on this, when determining the payment mode of the target device, the payment device can first determine the actual speed at which the target device approaches the payment device. Further, in a case where the actual speed at which the target device approaches the payment device is less than or equal to the preset speed, it is determined that the payment mode of the target device is the code scanning payment mode. Correspondingly, in a case where the actual speed at which the target device approaches the payment device is greater than the preset speed, it is determined that the payment mode of the target device is not the code scanning payment mode. The specific manner in which the payment device determines the actual speed at which the target device approaches the payment device is not limited, and can alternatively be determined by means of continuously shooting videos or images during the approach of the target device to the payment device.

[0072] Based on the above, in a case where it is determined that the payment mode of the target device is not the code scanning payment mode, the near field communication function of the near field communication module is enabled, and payment is performed based on the near field communication function. Correspondingly, in a case where it is determined that the payment mode of the target device is the code scanning payment mode, the near field communication function of the near field communication module is kept disabled, and payment is performed through the code scanning module.

[0073] For ease of illustration of the payment process based on the NFC payment mode, the system architecture to which the above payment method is applied is described below. Alternatively, the above payment method can be applied to a payment system, and the system architecture of the payment system and the execution functions of each device subject in the system architecture are not limited. The system architecture in one or more embodiments described below is only illustrative, and as long as the system architecture is applicable to the above payment method, it is considered to be within the protection scope of one or more embodiments of the present specification, and is not described herein.

[0074] Alternatively, FIG. 2 is a system architecture diagram of a payment system provided by one or more embodiments of the present specification. As shown in FIG. 2, the payment system can include a card reading device 10, a payment device 20, and a server 30. The card reading device 10 has a near field communication function and a code scanning function. In a payment scenario, a user can use the card reading device 10 to perform payment operations such as receiving payment and paying with a payment device 20 of a merchant. Correspondingly, the payment device 20 also has a near field communication function and a code scanning function. In a payment scenario, a merchant can use the payment device 20 to perform payment operations such as receiving payment and paying with a card reading device 10 of a user. In this process, the data processing operations involved in the payment process between the card reading device 10 and the payment device 20 are completed by the server 30. That is, the card reading device 10 and the payment device 20 can perform network communication with the server 30 to obtain payment-related information required by the payment process from the server 30, and complete payment.

[0075] It should be noted that in the above payment system, the specific form of the card reading device 10 is not limited, and can alternatively be a mobile terminal with near field communication function and code scanning function, including but not limited to a smart phone or a smart watch; correspondingly, the specific form of the payment device 20 is also not limited, and can alternatively be an electronic device with near field communication function and code scanning function, including but not limited to a POS machine, a smart payment terminal, a payment box, etc. Further, the manner of network communication between the card reading device 10 and the payment device 20 and the server 30 is also not limited, and can be determined according to actual payment needs, and will be exemplarily described in the following embodiments in two optional manners, see the following embodiments.

[0076] FIG. 3 is a structural schematic diagram of the payment device 20 applied to the payment system shown in FIG. 2. As shown in FIG. 3, the payment device 20 can include a near field communication module 21 and a code scanning module 22. In a traditional payment scenario, a user uses a card reading device, for example, a target device 40 shown in FIG. 3, to perform a payment operation and places the target device 40 close to the near field communication module 21 or the code scanning module 22. If the distance between the target device 40 and the near field communication module 21 is less than or equal to the communication distance of the near field communication module 21, the near field communication module 21 will identify the target device 40 in the case that the near field communication function of the near field communication module 21 is turned on, and then performs payment in an NFC-based payment mode. However, if the user wants to perform payment in a code scanning payment mode, the NFC-based payment mode and the code scanning payment mode will interfere with each other, causing payment confusion.

[0077] For example, in the process that the user uses the target device 40 to perform code scanning payment, the target device 40 passes above the near field communication module 21, and the minimum distance between the target device 40 and the near field communication module 21 is less than the communication distance of the near field communication module 21. In the case that the near field communication function of the near field communication module 21 is turned on, the payment device is most likely to trigger NFC-based payment, thereby causing payment interference and affecting the user's payment experience.

[0078] Therefore, in order to solve the problem that the near field communication module 21 and the code scanning module 22 may cause payment confusion due to mutual interference, as shown in FIG. 3, the near field communication module 21 of the payment device 20 provided by one or more embodiments of the present specification can include a sensor 23, or the sensor 23 is arranged in the near field communication module 21, for monitoring the payment mode of the target device 40. The specific type of the sensor 23 is not limited, and can alternatively include but is not limited to a proximity sensor, an infrared sensor, an ultrasonic sensor, a laser sensor, a millimeter wave radar sensor, a camera, etc. The specific type can be selected flexibly according to actual needs.

[0079] It should be noted that in addition to the above functional modules, as shown in FIG. 3, the payment device 20 can further include a processor 24 for controlling the working of the near field communication module 21, the code scanning module 22, the sensor 23 and other functional modules. Accordingly, the above payment method can be executed by the processor 24, and thus in the following embodiments, the execution principle of the payment method will be described from the perspective of the processor 24 executing the payment method.

[0080] Based on the above, the processor 24 can obtain the sensing information collected by the sensor 23, and then determine whether the target device 40 exists according to the obtained sensing information, and determine the corresponding payment mode of the target device 40 in the case that the target device 40 exists. For how the processor 24 determines the payment mode of the target device 40, please refer to the description in the above embodiments, which will not be repeated here.

[0081] The process of how the processor 24 obtains the sensing information and determines whether the target device 40 exists based on the sensing information will be described exemplarily below.

[0082] In an optional manner, the processor 24 actively obtains the sensing information collected by the sensor 23. In this case, the processor 24 can continuously monitor whether the sensor 23 collects the sensing information, and obtain the sensing information collected by the sensor 23 when it is monitored that the sensor 23 collects the sensing information. In another optional manner, the sensor 23 actively reports the collected sensing information to the processor 24. In this case, the sensor 23 directly sends the collected sensing information to the processor 24 after collecting the sensing information.

[0083] It should be noted that no matter which acquisition manner is adopted, after the processor 24 obtains the sensing information collected by the sensor 23, it can determine whether the target device 40 exists according to the obtained sensing information. Optionally, the processor 24 can determine whether the target device 40 exists within the perceptible range of the payment device 20 according to the sensing information, for example, determine whether the target device 40 exists within the communication distance of the near field communication module 21 or within the maximum distance range in which the code scanning module 22 can identify the payment identifier. Further, in the case that the target device 40 exists, it is further determined whether the payment mode of the target device 40 is the code scanning payment mode by the way in the above embodiments, and in the case that it is not the code scanning payment mode, the near field communication function of the near field communication module 21 is started, and the payment is made in the NFC-based payment mode based on the near field communication module 21.

[0084] That is, the payment device 20 is in the standby state, the near field communication function of the near field communication module 21 is kept in the closed state, only in the case that the target device 40 is close to the payment device 20 and the payment mode of the target device 40 is not the code scanning payment mode, the processor 24 will open the near field communication function of the near field communication module 21, and in other cases, the near field communication function of the near field communication module 21 is kept in the closed state. After opening the near field communication function of the near field communication module 21, the processor 24 can make payment based on the near field communication module 21.

[0085] It should be noted that in the above embodiment, the payment mode of the target device 40 is determined whether it is a code scanning payment mode, but in actual application, it is not limited to this, and the above payment method can also be realized from the perspective of determining whether the payment mode of the target device 40 is an NFC-based payment mode, and the near field communication function of the near field communication module 21 is opened to complete payment when it is determined that the payment mode of the target device 40 is an NFC-based payment mode.

[0086] Optionally, whether the payment mode of the target device 40 is an NFC-based payment mode can be determined by the minimum distance between the target device 40 and the near field communication module 21, in which case the target device 40 is very close to the near field communication module 21, far less than the communication distance of the near field communication module 21, and the minimum distance between the target device 40 and the near field communication module 21 is 20% or 30% of the communication distance of the near field communication module 21, or even a smaller percentage, for example, the minimum distance between the target device 40 and the near field communication module 21 is 10 millimeters (mm), in which case the near field communication function of the near field communication module 21 is opened; otherwise, the near field communication function of the near field communication module 21 is kept closed.

[0087] Based on the above, when the processor 24 determines that there is a target device 40 based on the obtained sensing information and determines that the corresponding payment mode is not a code scanning payment mode, or determines that the payment mode of the target device is an NFC-based payment mode, the near field communication function of the near field communication module 21 can be opened, and payment can be made in an NFC-based payment mode. Wherein the specific process of making payment in an NFC-based payment mode is not limited, and the process of making payment in an NFC-based payment mode can also be different according to the role and processing function of the payment device 20 in the payment system.

[0088] Optionally, in the following embodiments, the roles of the target device 40 and the payment device 20 in the payment system are described by taking the target device 40 as the payer and the payment device 20 as the payee, and the processing functions performed by the target device 40 and the payment device 20 in the payment system are described by taking the payment device 20 and the target device 40 as initiators of the payment request, and the process of payment in the NFC-based payment mode is described.

[0089] In an optional embodiment, the payment request is initiated by the payment device 20.

[0090] FIG. 4 is a schematic diagram of a communication process corresponding to the payment process described above. As shown in FIG. 4, in this embodiment, the payment request is initiated by the payment device 20. In this case, the payment device 20 can send the tag information containing the payment access information to the target device 40 through the near field communication module 21, so that the target device 40 sends the payment authorization request to the server 30 associated with the payment access information based on the tag information. After receiving the payment authorization request sent by the target device 40, the server 30 can issue the payment identification information to the processor 24 of the payment device 20, which can include the information of the payment identifier (such as the payment code, etc.) of the payment account corresponding to the target device 40. It should be understood that the payment identification information can also include other information, such as the information of the payment account, etc. After receiving the payment identification information issued by the server 30, the processor 24 can initiate the payment request to the server 30 based on the payment identification information, and complete the payment.

[0091] In this embodiment, the specific content of the payment access information sent by the payment device 20 to the target device 40 through the near field communication module 21 is not limited, and the payment access information can optionally include but is not limited to the link information for starting the payment application and the identification information of the payment device 20. Based on this, the target device 40 can start the corresponding payment application according to the link information, and initiate the payment authorization request to the server 30 based on the corresponding payment application. Optionally, the payment authorization request can carry the identification information corresponding to the target device 40 and the payment device 20, respectively, so that the server 30 grants the payment authority based on the identification information of the two devices. The specific content of the identification information corresponding to the target device 40 and the payment device 20 is not limited, and the identification information of the target device 40 can be the account identifier of the payment account corresponding to the target device 40 or the user identifier for logging into the corresponding payment application; correspondingly, the identification information of the payment device 20 can be the account identifier of the payment account corresponding to the payment device 20 or the merchant identifier bound to the payment device 20, etc.

[0092] In this embodiment, the account identifier of the payment account corresponding to the target device 40 and the account identifier of the payment account corresponding to the payment device 20 are taken as examples of the identification information.

[0093] Further optionally, as shown in FIG. 5, before initiating the payment authorization request to the server 30 based on the corresponding payment application, the target device 40 can also send a page acquisition request to the server 30 based on the payment application, wherein the page acquisition request at least includes the identification information corresponding to the target device 40 and the payment device 20 respectively, so that the server 30 determines the transaction parties, generates the payment page information containing the transaction party information and returns the target device 40. Based on this, after receiving the payment page information returned by the server 30, the target device 40 can render the corresponding payment page according to the payment page information and display it to the user. After the user inputs the corresponding payment amount in the corresponding payment page, the target device 40 can initiate the payment authorization request to the server 30 based on the payment page filled with the payment amount.

[0094] Based on this, after receiving the payment authorization request initiated by the target device 40, the server 30 can determine the payment account corresponding to the target device 40 according to the identification information of the target device 40 carried in the payment authorization request. Further, the server 30 can issue payment identification information containing the above-mentioned payment identification to the processor 24 of the payment device 20, so that the processor 24 initiates a payment request to the server 30 based on the above-mentioned payment identification information containing the payment identification. Optionally, the payment request can carry the above-mentioned payment identification, and can also carry the identification information corresponding to the payment device 20. Based on this, the server 30 can determine the payment account corresponding to the payment device 20 according to the identification information, and then execute the deduction operation on the payment account corresponding to the target device 40 according to the above-mentioned payment identification and the collection identification, and execute the transfer operation on the payment account corresponding to the payment device 20, to complete the payment process.

[0095] In another optional embodiment, the payment request is initiated by the target device.

[0096] FIG. 6 is another communication process diagram corresponding to the payment flow, as shown in FIG. 6, in the embodiment, the payment request is initiated by the target device 40. In this case, the payment device 20 can send the target device 40 label information containing payment access information and payee identification information through the near field communication module 21, so that the target device 40 sends a payment identifier acquisition request to the server 30 associated with the payment access information based on the label information, and receives the information containing the payment identifier returned by the server 30 based on the payment identifier acquisition request, further, the target device 40 can initiate a payment request to the server 30 according to the information containing the payment identifier received from the server 30 and the payee identification information, and complete the payment. Wherein, the label information can be pre-written in the near field communication module 21 of the payment device 20, that is, the near field communication module 21 can be used as a label. Alternatively, the merchant can also send the label information to the processor 24 of the payment device 20 through the merchant device, and transmit it to the near field communication module 21 through the processor 24. The specific way is optional according to the application scene, and the application does not limit it.

[0097] Correspondingly, the payment access information sent by the payment device 20 to the target device 40 through the near field communication module 21 includes but is not limited to link information for starting the payment application and identification information of the payment device 20, based on which the target device 40 can start the corresponding payment application according to the link information, and initiate a payment identifier acquisition request to the server 30 based on the corresponding payment application. Further optionally, as shown in FIG. 7, before the target device 40 initiates a payment identifier acquisition request to the server 30 based on the corresponding payment application, it can also send a page acquisition request to the server 30 based on the payment application to obtain payment page information containing transaction information from the server 30, and then render it into a corresponding payment page for display, so that the user can input the corresponding payment amount in the corresponding payment page, and initiate a payment identifier acquisition request to the server 30 based on the payment page filled with the payment amount.

[0098] Based on this, after receiving the payment identifier obtaining request initiated by the target device 40, the server 30 can optionally carry the identification information corresponding to the target device 40 in the payment identifier obtaining request. Based on this, as shown in FIG. 7, the server 30 can determine the payment identifier (for example, a payment code) of the payment account corresponding to the target device 40 according to the identification information corresponding to the target device 40 after receiving the payment identifier obtaining request. Further, the server 30 issues the information containing the above-mentioned payment identifier to the target device 40. Based on this, the target device 40 can initiate a payment request to the server 30 based on the above-mentioned information containing the payment identifier and the payment identifier information carrying the payment identifier in the tag information. Optionally, the payment request can carry the above-mentioned payment identifier and payment identifier, and then the server 30 can perform a deduction operation on the payment account corresponding to the target device 40 and a transfer operation on the payment account corresponding to the payment device 20 according to the payment identifier and the payment identifier, thereby completing the payment process.

[0099] It should be noted that the specific form of the identification information corresponding to the target device 40 and the payment device 20 in the embodiment can be referred to the description of the above-mentioned embodiment, which will not be repeated here.

[0100] In the above-mentioned embodiment, the communication process initiated by the payment device 20 or the target device 40 and the various information carried in the whole communication process are only exemplary descriptions, which are not limited in actual application. For example, for the case of initiating a payment request by the target device 40, the target device 40 can also send a payment request to the server 30 directly after starting the corresponding payment application after receiving the tag information sent by the payment device 20 through the near field communication module 21. The payment request can carry the payment identifier sent by the payment device 20 through the near field communication module 21 and the identification information corresponding to the target device 40. Based on this, the server 30 can directly determine the payment identifier (for example, a payment code) of the payment account corresponding to the target device 40 according to the identification information corresponding to the target device 40 carried by the payment request after receiving the payment request. Further, the server 30 can perform a deduction operation on the payment account corresponding to the target device 40 and a transfer operation on the payment account corresponding to the payment device 20 according to the payment identifier and the payment identifier carried by the payment request, thereby completing the payment process.

[0101] It should be further noted that in one or more embodiments of the present specification, the setting mode between the near field communication module 21 and the code scanning module 22 of the payment device 20 is not limited, which can be flexibly set according to the design needs of the structure of the payment device 20 in actual application. Next, taking three setting modes suitable for the above-mentioned payment method principle as an example, the relative position relationship between the near field communication module 21 and the code scanning module 22 in the payment device 20 is described.

[0102] FIG. 8 is a structural schematic diagram of a setting mode of the near field communication module 21 and the code scanning module 22 in the payment device 20. As shown in FIG. 8, in the embodiment, the first contact surface 210 for near field induction in the near field communication module 21 and the second contact surface 220 for code scanning induction in the code scanning module 22 are towards the same direction, and the height distance between the two is a second preset distance, wherein the second preset distance is less than or equal to the communication distance of the near field communication module 21. In this setting mode, if the user presents a payment code (for example, a payment code) through a terminal device and wants to complete payment in a code scanning payment mode through the second contact surface 220, in the process of approaching the terminal device above the first contact surface 210 to the second contact surface 220, or when the terminal device stays above the second contact surface 220, since the height distance between the first contact surface 210 and the second contact surface 220 is the second preset distance, which is less than or equal to the communication distance of the near field communication module 21, if the near field communication function of the near field communication module 21 is turned on, the terminal device can be monitored as the target device 40, and payment is then made in the NFC-based payment mode. If the code scanning module 22 also senses the payment code above the second contact surface 220 and makes payment in the code scanning mode, payment confusion will occur.

[0103] Therefore, in the case that it is determined that the terminal device held by the user approaches the payment device 20 and the payment mode of the terminal device is not the code scanning payment mode, the near field communication function of the near field communication module 21 is turned on and payment is made in the NFC-based payment mode, which can effectively solve the problem of payment confusion.

[0104] FIG. 9 is a structural schematic diagram of another setting mode of the near field communication module 21 and the code scanning module 22 in the payment device 20. As shown in FIG. 9, in the embodiment, the first contact surface 210 for near field induction in the near field communication module 21 and the second contact surface 220 for code scanning induction in the code scanning module 22 are coplanar, and the adjacent edges of the two are apart by a second preset distance. In this setting mode, if the user presents a payment code through a terminal device and wants to complete payment in a code scanning payment mode through the second contact surface 220, in the process of approaching the terminal device above the first contact surface 210 to the second contact surface 220, or when the terminal device stays above the second contact surface 220, since the second preset distance between the adjacent edges of the first contact surface 210 and the second contact surface 220 is less than or equal to the communication distance of the near field communication module 21, if the near field communication function of the near field communication module 21 is turned on at this time, the terminal device can be monitored as the target device 40, and payment is then made in the NFC-based payment mode. If the code scanning module 22 also senses the payment code above the second contact surface 220 and makes payment in the code scanning mode, payment mode confusion will occur.

[0105] Therefore, in the case that it is determined that the terminal device held by the user is close to the payment device 20 and the payment mode of the terminal device is not the code scanning payment mode, the near field communication function of the near field communication module 21 is started and payment is made in the NFC-based payment mode, which can effectively solve the problem of payment mode confusion.

[0106] In actual application scenarios, since the NFC-based payment mode is more convenient than the code scanning payment mode, when designing the structure of the payment device 20, the device structure can be designed to facilitate the user to make payment in the NFC-based payment mode. Based on this, FIG. 10 provides another structure schematic diagram of the arrangement of the near field communication module 21 and the code scanning module 22 in the payment device 20. As shown in FIG. 10, in the embodiment, in the case that the payment device 20 is used by the user for payment, the near field communication module 21 is located at the end close to the user, and the code scanning module 22 is located at the end away from the user, so as to facilitate the user to preferentially make payment in the NFC-based payment mode.

[0107] It should be noted that in the embodiment, the relative height relationship between the first contact surface 210 for near field induction and the second contact surface 220 for code scanning induction is not limited. Alternatively, the first contact surface 210 can be lower than the second contact surface 220 by a second preset distance, or the heights of the two are the same but the distance between the adjacent edges is less than or equal to the second preset distance, or the first contact surface 210 is higher than the second contact surface 220, as long as the relative position relationship that the near field communication module 21 is located at the end close to the user and the code scanning module 22 is located at the end away from the user is applicable to the embodiment.

[0108] In the embodiment, the first contact surface 210 is lower than the second contact surface 220 by a second preset distance as an example. In this arrangement, if the user wants to make payment in the code scanning payment mode through the second contact surface 220 by presenting a payment code through the terminal device, in the process of approaching the second contact surface 220 through the first contact surface 210, or when the terminal device stays above the second contact surface 220, since the first contact surface 210 and the second contact surface 220 are apart by the second preset distance in height, which is less than or equal to the communication distance of the near field communication module 21, if the near field communication function of the near field communication module 21 is started at this time, the terminal device can be monitored as the target device 40, and payment is made in the NFC-based payment mode. If the code scanning module 22 also senses the payment code above the second contact surface 220 and makes payment in the code scanning mode, payment confusion will be caused.

[0109] Therefore, the near field communication function of the near field communication module 21 is started and the payment is made in the NFC-based payment mode only when it is determined that the terminal device held by the user is close to the payment device 20 and the payment mode of the terminal device is not the code scanning payment mode, which can effectively solve the problem of payment confusion.

[0110] It should be noted that the structures shown in FIGS. 8-10 are only exemplary, and the specific communication process of the corresponding payment device in use can be referred to the description in the foregoing embodiments, which will not be described here again.

[0111] It should be further noted that in the one or more embodiments described above, the ownership relationship between the near field communication module 21 and the code scanning module 22 and the payment device 20 is not limited, and it can be understood that the one or more embodiments are described by taking the near field communication module 21 and the code scanning module 22 integrated in the payment device 20 as an example, but in actual application, it is not limited thereto.

[0112] Optionally, FIG. 11 is a system architecture diagram of another payment system provided by the embodiment of the present specification, as shown in FIG. 11, the near field communication module 21 and the code scanning module 22 are independent of the payment device 20 and are set as a payment tag 50 associated with the payment device 20, and the payment tag 50 only has an identification function. Based on this, the payment tag 50 can send tag information to the target device, for example, the card reading device 10, after identifying the existence of the target device. Further, if the payment request is initiated by the payment device 20, the server 30 can issue payment identification information to the payment device 20 associated with the payment tag 50 through the payment authorization request initiated by the target device, so that the payment device 20 initiates a payment request based on the payment identification information to complete the payment. The communication process between the payment device 20, the card reading device 10 and the server 30 in the payment system shown in FIG. 11 can be referred to the description of the foregoing embodiments, which will not be described here again.

[0113] In the one or more embodiments described above, the execution principle of the payment method is described by taking the target device 40 as the payer and the payment device 20 as the payee, but in actual application, the target device 40 can also be the payee, and correspondingly, the payment device 20 can be the payer. In this case, the communication process between the payment device 20, the target device 40 and the server 30 is similar to the communication process when the target device 40 is the payer and the payment device 20 is the payee, and the specific process can be referred to the foregoing embodiments.

[0114] In one or more embodiments of the present specification, in a case where the payment mode of the target device 40 is determined to be the code scanning payment mode, the near field communication function of the near field communication module 21 is kept closed, and the code scanning payment is performed through the code scanning module 22. For the specific process of the code scanning payment, please refer to the general code scanning payment implementation mode, which will not be described in detail here.

[0115] In summary, the payment method provided by one or more embodiments of the present specification is for a payment device with a specific structure and supporting the NFC-based payment mode and the code scanning payment mode. By identifying the payment mode of the target device, in a case where the payment mode of the target device is not the code scanning payment mode, the near field communication function of the near field communication module is turned on. This can effectively avoid the near field communication module from misidentifying the NFC-based payment mode for payment, thereby avoiding interference with the originally used code scanning payment mode of the user. As can be seen, the payment method provided by one or more embodiments of the present specification not only improves the accuracy of identifying the payment mode while ensuring low device cost, but also very conveniently solves the problem of payment confusion caused by mutual interference between the NFC-based payment mode and the code scanning payment mode.

[0116] It can be understood that the above embodiments are only examples, and the above embodiments can be deformed in actual implementation. Those skilled in the art can understand that the deformed methods of the above embodiments without creative labor all fall within the protection scope of one or more embodiments of the present specification, and will not be described in detail in the embodiments.

[0117] Based on the same inventive concept, one or more embodiments of the present specification also provide a payment device, as shown in FIG. 12, the payment device 300 can include a processor 301, a near field communication module 302, and a code scanning module 303, wherein the processor 301 performs the following operations:

[0118] determining the payment mode of the target device, wherein the target device is a terminal device close to the payment device 300 and triggering a payment operation; in a case where the payment mode of the target device is not the code scanning payment mode, turning on the near field communication function of the near field communication module 302, and performing payment based on the near field communication module 302.

[0119] In an optional embodiment, the processor 301, when determining the payment mode of the target device, is configured to: acquire a first image of the target device; determine a target component in the target device facing the payment device 300 based on the first image; in a case where the target component is a display screen, determine that the payment mode of the target device is the code scanning payment mode; or in a case where the target component is a backboard, determine that the payment mode of the target device is not the code scanning payment mode.

[0120] In an optional embodiment, the processor 301, when determining the payment mode of the target device, is configured to: acquire a second image of the target device; determine whether the second image includes an image of a payment identifier; in the case that the second image includes the image of the payment identifier, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the second image does not include the image of the payment identifier, determine that the payment mode of the target device is not the code scanning payment mode.

[0121] In an optional embodiment, the processor 301, when determining the payment mode of the target device, is configured to: determine whether the target device is in a camera mode; in the case that the target device is in the camera mode, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the target device is not in the camera mode, determine that the payment mode of the target device is not the code scanning payment mode.

[0122] In an optional embodiment, the processor 301, when determining the payment mode of the target device, is configured to: determine whether a minimum distance between the target device and the near field communication module 302 is greater than or equal to a first preset distance; in the case that the minimum distance is greater than or equal to the first preset distance, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the minimum distance is less than the first preset distance, determine that the payment mode of the target device is not the code scanning payment mode.

[0123] In an optional embodiment, the processor 301, when determining the payment mode of the target device, is configured to: determine an actual speed at which the target device approaches the payment device 300; in the case that the actual speed is less than or equal to a preset speed, determine that the payment mode of the target device is the code scanning payment mode; or in the case that the actual speed is greater than the preset speed, determine that the payment mode of the target device is not the code scanning payment mode.

[0124] In an optional embodiment, the processor 301, when performing payment based on the near field communication module 302, is configured to: send, by the near field communication module 302, label information containing payment access information to the target device, so that the target device sends a payment authorization request to a server associated with the payment access information based on the label information; receive payment identifier information issued by the server based on the payment authorization request, wherein the payment identifier information contains information of a payment identifier of a payment account corresponding to the target device; and initiate a payment request to the server according to the payment identifier information, and complete the payment.

[0125] In an optional embodiment, the processor 301 is configured to, when the payment is made based on the near field communication module 302, send, by the near field communication module 302, tag information containing payment access information and payment receiving identification information to a target device, so that the target device sends a payment identification obtaining request to a server associated with the payment access information based on the tag information, and initiates a payment request to the server and completes the payment according to information containing the payment identification returned by the server based on the payment identification obtaining request and the payment receiving identification information.

[0126] In an optional embodiment, the processor 301 is further configured to, when the payment mode of the target device is a code scanning payment mode, keep the near field communication function of the near field communication module 302 closed, and make the payment by the code scanning module 303.

[0127] In an optional embodiment, the first contact surface for near field induction in the near field communication module 302 and the second contact surface for code scanning induction in the code scanning module are oriented in the same direction, and the distance between the two in the height direction is a second preset distance, wherein the second preset distance is less than or equal to the communication distance of the near field communication module 302.

[0128] In an optional embodiment, the first contact surface for near field induction in the near field communication module 302 and the second contact surface for code scanning induction in the code scanning module are coplanar, and the distance between the two adjacent edges is a second preset distance, wherein the second preset distance is less than or equal to the communication distance of the near field communication module 302.

[0129] In an optional embodiment, when the payment device 300 is oriented towards the user for payment use, the near field communication module 302 is located at one end close to the user, and the code scanning module 303 is located at one end away from the user.

[0130] It should be noted that the functions of the components in the payment device described above are the same as the implementation principles of the corresponding steps in the payment method, and the specific descriptions can be referred to the descriptions of the corresponding parts in the method embodiments described above, which will not be repeated here. In addition, the specific structure of the payment device 300 can also be referred to the structure of the payment device in the foregoing embodiments.

[0131] In some optional implementations, the processor 301, also known as a controller or operation control, can include a microprocessor or other processor device and / or a logic device, which receives input and controls the operation of various components of the payment device 300.

[0132] It should be noted that the components shown in FIG. 12 are exemplary, and other types of structures can also be used to supplement or replace the structures to implement telecommunication functions or other functions. Of course, the payment device 300 does not necessarily include all the components shown in FIG. 12; in addition, the payment device 300 can also include components not shown in FIG. 12, which can be referred to the prior art.

[0133] In some optional implementations, the payment device 300 can further include a memory, a communication module, an input unit, an audio processor, a display, a power supply, and the like.

[0134] The memory can be coupled to the processor 301, and can be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. Programs related to the above-described information regarding payment method execution can be stored. The processor 301 can execute the programs stored in the memory to achieve information storage or processing, and the like.

[0135] The memory can be a solid state memory such as a read only memory (ROM), a random access memory (RAM), a SIM card, and the like. It can also be a memory that retains information even when power is off, can be selectively erased, and is provided with more data, examples of which are sometimes referred to as an EPROM, and the like. The memory can also be some other type of device. The memory includes a buffer memory (sometimes referred to as a buffer). The memory can include an application / function storage section for storing application programs and function programs or for executing a flow of the operation of the payment device 300 by the processor 301.

[0136] The memory can further include a data storage section for storing data such as contacts, digital data, pictures, sounds, and / or any other data used by the payment device. A driver storage section of the memory can include various drivers of the computer device for communication functions and / or for executing other functions of the computer device such as a messaging application, an address book application, and the like.

[0137] The input unit can provide input to the processor 301. The input unit is, for example, a key or a touch input device. The power supply can be used to provide power to the payment device 300. The display can be used to display display objects such as images and text. The display can be, for example, an LCD display, but is not limited thereto.

[0138] The communication module is a transmitter / receiver that transmits and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor 301 to provide input signals and receive output signals, which can be the same as in the case of a conventional mobile communication terminal.

[0139] Based on different communication technologies, multiple communication modules, such as a cellular network module, a Bluetooth module, and / or a wireless local area network module, etc., can be provided in the same computer device. The communication modules (transmitters / receivers) are also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and to receive audio input from the microphone to implement the usual telecommunication functions. The audio processor can include any suitable buffers, decoders, amplifiers, etc. In addition, the audio processor is also coupled to the processor 301 to enable recording on the local device via the microphone and to enable playing of stored sounds on the local device via the speaker.

[0140] One or more embodiments of the present specification also provide a computer readable storage medium capable of implementing all steps of the payment method in the above-mentioned embodiments, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement all steps of the payment method in the above-mentioned embodiments, for example, the processor executes the computer program to implement the following steps:

[0141] Determining a payment mode of a target device, wherein the target device is a terminal device that is close to the payment device and triggers the payment operation;

[0142] In a case where the payment mode of the target device is not a code scanning payment mode, enabling a near field communication function of a near field communication module;

[0143] Performing payment based on the near field communication module.

[0144] Although the present specification one or more embodiments provide method operation steps such as embodiments or flowcharts, more or fewer operation steps can be included based on conventional or non-inventive labor. The order of steps listed in the embodiments is only one of the many step execution orders, and does not represent the only execution order. When the device or client product in the actual execution, it can be executed according to the method order shown in the embodiment or in parallel (for example, parallel processor or multi-thread processing environment).

[0145] Those skilled in the art should understand that the embodiments of the present specification can be provided as a method, device (system) or computer program product. Therefore, the embodiments of the present specification can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of the present specification can take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0146] This specification describes one or more embodiments of a method, apparatus (system), and computer program product according to one or more embodiments of this specification with reference to flowchart illustrations and / or block diagrams. 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, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams.

[0147] 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 that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0148] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0149] 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 device and system embodiments 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.

[0150] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, 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. Those skilled in the art will understand the specific meaning of the above terms in one or more embodiments of this specification, depending on the specific circumstances.

[0151] It should be noted that the features of one or more embodiments and embodiments described in the specification above can be combined with each other and / or replaced by other features in order to provide one or more other embodiments and embodiments.

[0152] Finally, it should be noted that the above-described embodiments are merely intended to illustrate the technical solutions of the one or more embodiments of the specification, rather than limit them. Although the one or more embodiments of the specification are described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that the technical solutions recorded in the foregoing embodiments can still be modified, or some or all of the technical features can be replaced by equivalents. Such modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the one or more embodiments of the specification, and should be included in the scope of the one or more embodiments of the specification.

[0153] The one or more embodiments of the specification are described above in combination with optional embodiments, but these embodiments are only exemplary and serve only to illustrate. On this basis, various substitutions and improvements can be made to the one or more embodiments of the specification, and these all fall within the protection scope of the one or more embodiments of the specification.

Claims

1. A payment method, characterized in that, The method is applied to a payment device, the payment device comprises a near field communication module and a code scanning module, and the method comprises the following steps: Determining a payment mode of a target device, the target device being a terminal device close to the payment device and triggering a payment operation; In the case that the payment mode of the target device is not a code scanning payment mode, starting a near field communication function of the near field communication module; Performing payment based on the near field communication module.

2. The method of claim 1, wherein, The method for determining the payment mode of the target device comprises the following steps: Obtaining a first image of the target device; Determining a target component in the target device facing the payment device based on the first image; In the case that the target component is a display screen, determining that the payment mode of the target device is a code scanning payment mode; or In the case that the target component is a backboard, determining that the payment mode of the target device is not a code scanning payment mode.

3. The method of claim 1, wherein, The method for determining the payment mode of the target device comprises the following steps: Obtaining a second image of the target device; Determining whether the second image comprises an image of a payment identifier; In the case that the second image comprises an image of a payment identifier, determining that the payment mode of the target device is a code scanning payment mode; or In the case that the second image does not comprise an image of a payment identifier, determining that the payment mode of the target device is not a code scanning payment mode.

4. The method of claim 1, wherein, The method for determining the payment mode of the target device comprises the following steps: Determining whether the target device is in a camera mode; In the case that the target device is in a camera mode, determining that the payment mode of the target device is a code scanning payment mode; or In the case that the target device is not in a camera mode, determining that the payment mode of the target device is not a code scanning payment mode.

5. The method of claim 1, wherein, The method for determining the payment mode of the target device comprises the following steps: Determining whether a minimum distance between the target device and the near field communication module is greater than or equal to a first preset distance; In the case that the minimum distance is greater than or equal to the first preset distance, determining that the payment mode of the target device is a code scanning payment mode; or In the case that the minimum distance is less than the first preset distance, determining that the payment mode of the target device is not a code scanning payment mode.

6. The method of claim 1, wherein, The method for determining the payment mode of the target device comprises the following steps: Determining an actual speed at which the target device approaches the payment device; In the case that the actual speed is less than or equal to a preset speed, determining that the payment mode of the target device is a code scanning payment mode; or In the case that the actual speed is greater than the preset speed, determining that the payment mode of the target device is not a code scanning payment mode.

7. The method according to any one of claims 1 to 6, characterized in that, The method for performing payment based on the near field communication module comprises the following steps: Sending, by the near field communication module, label information containing payment access information to the target device, so that the target device sends a payment authorization request to a server associated with the payment access information based on the label information; Receiving payment identifier information issued by the server based on the payment authorization request; the payment identifier information contains information of a payment identifier of a payment account corresponding to the target device; Initiating a payment request to the server according to the payment identifier information, and completing payment.

8. The method according to any one of claims 1 to 6, characterized in that, The method for performing payment based on the near field communication module comprises the following steps: The near field communication module is used for sending label information containing payment access information and collection identification information to the target device, so that the target device sends a payment identification acquisition request to a server associated with the payment access information based on the label information, and initiates a payment request to the server and completes payment according to information containing a payment identification returned by the server based on the payment identification acquisition request and the collection identification information.

9. The method according to any one of claims 1-6, characterized in that, Further comprising: In a case where the payment mode of the target device is a code scanning payment mode, keeping the near field communication function of the near field communication module closed; Payment is made through the code scanning module.

10. The method according to any one of claims 1-6, characterized in that, The first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are oriented in the same direction, and the distance between the two in height is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

11. The method according to any one of claims 1-6, characterized in that, The first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are coplanar, and the distance between the adjacent edges of the two is a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

12. The method of any of claims 1-6, wherein, In a case where the payment device is oriented towards the user for payment use, the near field communication module is located at one end close to the user, and the code scanning module is located at one end away from the user.

13. A payment device, characterized by A payment device comprises a processor, a near field communication module and a code scanning module, and the processor is configured to: Determine the payment mode of a target device, the target device being a terminal device that approaches the payment device and triggers a payment operation; In a case where the payment mode of the target device is not a code scanning payment mode, turn on the near field communication function of the near field communication module; Payment is made based on the near field communication module.

14. The payment device of claim 13, wherein, When determining the payment mode of the target device, the processor is configured to: Obtain a first image of the target device; Determine a target component in the target device that faces the payment device based on the first image; In a case where the target component is a display screen, determine that the payment mode of the target device is a code scanning payment mode; or In a case where the target component is a back plate, determine that the payment mode of the target device is not a code scanning payment mode.

15. The payment device of claim 13, wherein, When determining the payment mode of the target device, the processor is configured to: Obtain a second image of the target device; Determine whether the second image includes an image of a payment identification; In a case where the second image includes an image of a payment identification, determine that the payment mode of the target device is a code scanning payment mode; or In a case where the second image does not include an image of a payment identification, determine that the payment mode of the target device is not a code scanning payment mode.

16. The payment device of claim 13, wherein, When determining the payment mode of the target device, the processor is configured to: Determine whether the target device is in a camera mode; In a case where the target device is in a camera mode, determine that the payment mode of the target device is a code scanning payment mode; or In a case where the target device is not in a camera mode, determine that the payment mode of the target device is not a code scanning payment mode.

17. The payment device of claim 13, wherein, The processor is configured to: determine whether the minimum distance between the target device and the near field communication module is greater than or equal to a first preset distance; in a case where the minimum distance is greater than or equal to the first preset distance, determine that the payment mode of the target device is a code scanning payment mode; or in a case where the minimum distance is less than the first preset distance, determine that the payment mode of the target device is not the code scanning payment mode.

18. The payment device of claim 13, wherein, The processor is configured to: determine an actual rate at which the target device approaches the payment device; in a case where the actual rate is less than or equal to a preset rate, determine that the payment mode of the target device is a code scanning payment mode; or in a case where the actual rate is greater than the preset rate, determine that the payment mode of the target device is not the code scanning payment mode.

19. The payment device of any of claims 13-18, wherein, The processor is configured to: send, by the near field communication module, label information containing payment access information to the target device, so that the target device sends a payment authorization request to a server associated with the payment access information based on the label information; receive payment identification information issued by the server based on the payment authorization request; the payment identification information contains information of a payment account corresponding to the target device; and initiate a payment request to the server based on the payment identification information, and complete payment.

20. The payment device of any of claims 13-18, wherein, The processor is configured to: send, by the near field communication module, label information containing payment access information and payment identification information to the target device, so that the target device sends a payment identification acquisition request to a server associated with the payment access information based on the label information, and the target device initiates a payment request to the server based on information containing a payment identification returned by the server based on the payment identification acquisition request and the payment identification information, and completes payment.

21. The payment device of any of claims 13-18, wherein, The processor is further configured to: in a case where the payment mode of the target device is a code scanning payment mode, keep the near field communication function of the near field communication module closed; and perform payment by the code scanning module.

22. The payment device of any of claims 13-18, wherein, A first contact surface for near field induction in the near field communication module and a second contact surface for code scanning induction in the code scanning module face the same direction, and the two are separated by a second preset distance in height; the second preset distance is less than or equal to the communication distance of the near field communication module.

23. The payment device of any of claims 13-18, wherein, The first contact surface for near field induction in the near field communication module and the second contact surface for code scanning induction in the code scanning module are coplanar, and the edges adjacent to each other are separated by a second preset distance; the second preset distance is less than or equal to the communication distance of the near field communication module.

24. The payment device of any of claims 13-18, wherein, In a case where the payment device faces the user for payment, the near field communication module is located at one end close to the user, and the code scanning module is located at one end away from the user.

25. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, which, when executed, implement the method of any one of claims 1-12.

Images