WO2018219047A1

WO2018219047A1 - Payment method, equipment and device

Info

Publication number: WO2018219047A1
Application number: PCT/CN2018/082523
Authority: WO
Inventors: 李江
Original assignee: 口碑(上海)信息技术有限公司
Priority date: 2017-06-02
Filing date: 2018-04-10
Publication date: 2018-12-06
Also published as: CN111325536A; CN111325536B; CN107392620A; CN107392620B

Abstract

Disclosed by the embodiments of the present application are a payment method, equipment and device. A first device is associated with first user information and a second device is associated with second user information, wherein the method comprises: the first device monitors the second device which is related to a service; when monitoring the second device, the first device obtains the second user information and payment information which matches the service, executes the service, executes the service according to a service operation, and generates a payment request which is sent to a settlement terminal according to the first user information, the second user information and the payment information. By means of the described method, the payment process is fused with the process of a user obtaining a service, wherein the user does not need to actively initiate an additional payment operation, thereby reducing the operation required by the user in the process of obtaining the service, thus increasing convenience.

Description

Payment method, device and device

Technical field

The present application relates to the field of computer technologies, and in particular, to a payment method, device, and device.

Background technique

With the popularity of Internet technology, payment methods such as scan code payment and sonic payment have been widely used due to their safety, convenience and speed.

In an actual payment scenario, if a consumer uses a business service provided by a service provider (eg, a merchant) (eg, purchasing a product), the consumer needs to pay the service provider, and at this time, the consumer can use the corresponding The payment instrument (eg payment application) completes the payment. Taking the scan code payment as an example, the specific process may be: the user unlocks the terminal (eg, a smart phone), launches an application with a payment function, selects a scan code function in the application, and provides a digital object identifier (Digital Object) for the merchant. The Identifier (DOI) performs the scan code, and the terminal displays the payment interface, and the consumer inputs the amount to be paid in the payment interface, and then performs payment.

However, for existing payment methods, whether it is the above-mentioned scan code payment method, or sonic payment or other payment method based payment means, the consumer is required to perform business-related operations (ie, business operations). In addition, an additional payment operation is performed to complete the payment. For example, in the case of a consumer purchasing a product, the consumer needs to select the product to be purchased (the process of the consumer selecting the product can be regarded as a business operation), after which the consumer needs to pay the checkout for the selected product (ie, Issue payment action). Through business operations, consumers can obtain services or goods provided by the merchant, and then pay for the goods or services through payment operations.

Obviously, this way increases the amount of operation of the consumer, which is cumbersome for the consumer.

Summary of the invention

The embodiment of the present application provides a payment method for solving the problem that the payment process in a part of the service scenario is cumbersome.

The embodiment of the present application provides a payment device for solving the problem that the payment process in a part of the service scenario is cumbersome.

The embodiments of the present application adopt the following technical solutions:

The embodiment of the present application provides a payment method, where the first device is associated with the first user information, and the second device is associated with the second user information, the method includes:

The first device monitors a second device related to the service;

Obtaining the second user information and payment information matching the service when the second device is monitored;

The service is executed, and a payment request is generated and sent to the settlement terminal according to the first user information, the second user information, and the payment information.

The embodiment of the present application further provides a payment method, where the first device is associated with the first user information, and the second device is associated with the second user information; the method includes:

Receiving, by the settlement device, a payment request sent by the first device, where the payment request is generated by the first device based on the monitored second device related to the service;

Performing payment according to the payment request, and detecting a payment status;

The payment request is recorded when the payment status is abnormal.

The embodiment of the present application further provides a payment method, including: the second device is associated with the second user information; and the method includes:

The second device establishes a communication connection with the first device under the action of the first device;

Sending the second user information to the first device based on the communication connection.

The embodiment of the present application further provides a payment method, including:

The second device receives the abnormality identification information sent by the settlement terminal; wherein the abnormality identification information is received by the settlement terminal by the first device based on the monitored second device, and the payment status is detected according to the payment request. Generated when an exception occurs;

An abnormal prompt is performed according to the abnormality identification information.

The embodiment of the present application provides a payment device, which is associated with the first user information, and the second device is associated with the second user information; the device includes:

a monitoring module for monitoring a second device related to the service;

An information acquiring module, when the second device is monitored, acquiring the second user information and payment information that matches the service;

Business component, performing business;

The request transmission module generates a payment request and sends the payment request to the settlement terminal according to the first user information, the second user information, and the payment information.

The embodiment of the present application further provides a payment device, where the first device is associated with the first user information, and the second device is associated with the second user information; the device includes:

Receiving, by the receiving module, a payment request sent by the first device, where the payment request is generated by the first device based on the monitored second device related to the service;

Processing a module, performing payment according to the payment request, and detecting a payment status;

The recording module records the payment request when the payment status is abnormal.

The embodiment of the present application further provides a payment device, which is associated with the second user information, where the device includes:

The device body carries the communication module;

The communication module establishes a communication connection with the first device under the action of the first device, and sends the second user information to the first device based on the communication connection.

The embodiment of the present application further provides a payment device, including:

a device body, carrying a receiving module and a prompting module;

The receiving module receives the abnormality identification information sent by the settlement terminal, wherein the abnormality identification information is received by the settlement terminal by the first device based on the monitored second device, and the payment status is detected according to the payment request. Generated when an exception occurs;

The prompting module performs an abnormal prompt according to the abnormality identification information.

The above at least one technical solution adopted by the embodiment of the present application can achieve the following beneficial effects:

In a business scenario involving payment in part, the individual user (ie, the second user) may use the second device that is bound to the user's own user information, and the first device that belongs to the service provider user (ie, the first user). The devices interact to obtain the corresponding business services. In such a business scenario, the first device will monitor the second device used by the individual user to obtain the business service. After monitoring the second device, the first device will automatically obtain the user information of the individual user and the payment information bound to the second device. In the embodiment of the present application, the process of acquiring the information by the first device is weakly perceived or unperceived to the individual user, and the individual user does not need to actively issue the payment operation. Thereafter, the first device sends the obtained information and the user information of the service provider user to the settlement terminal that provides the payment service, so that the settlement terminal completes the payment process based on the information.

Compared with the prior art, the payment process in the embodiment of the present application is merged with the process of the user obtaining the service service, and the user does not need to initiate an additional payment operation, thereby reducing the operations required by the user to obtain the business process. Increased convenience.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the present application, and are intended to be a part of this application. In the drawing:

FIG. 1 is a schematic structural diagram of a payment method according to an embodiment of the present disclosure;

2 is a schematic diagram of a payment process based on a first device side according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a server-side payment process according to an embodiment of the present application;

4a and 4b are schematic diagrams of a payment process based on a second device side according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a payment process in an actual payment scenario according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a payment device according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a server-side payment device according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a payment device according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of another payment device according to an embodiment of the present application.

detailed description

The technical solutions of the present application will be clearly and completely described in the following with reference to the specific embodiments of the present application and the corresponding drawings. It is apparent that the described embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

As described above, in the current actual payment scenario, the process of the user performing the payment is generally independent of the process in which the user obtains the service. In other words, the user needs to perform the operation related to the payment in addition to the corresponding business operation. Obviously, this way is more cumbersome.

To this end, a payment method is provided in the embodiment of the present application to combine the operation process of the user to obtain the service service and the payment process in the service scenario partially involved in the payment, thereby reducing the operation of the user, and at the same time, the payment process is performed on the user. In terms of weak perception or no perception.

It should be noted that, in the embodiment of the present application, an architecture as shown in FIG. 1 may be adopted. As can be seen from FIG. 1, the architecture includes a first user, a second user, a first device, a second device, and a settlement terminal.

The first user may be considered as a service provider user, and may include: a store, a hotel, a restaurant, a coffee shop, a gas station, and the like, and is not specifically limited herein. The second user can be considered as a business demand side user (eg, a consumer), and usually, the second user is an individual user. In an actual service scenario, the first user may provide a corresponding service service for the second user, and correspondingly, the second user may perform payment to the first user.

The first device may include: a device capable of providing a service service for a second user, such as a smart coffee machine in a coffee shop, a smart meal picking machine in a restaurant, a smart tanker in a gas station, and a vending machine. Such equipment, or equipment related to business services, such as: smart door locks in hotel rooms. The second user interacts with the first device in the embodiment of the present application in the process of obtaining the service.

The second device may be considered as a device required by the second user to obtain a service service (that is, the second user will use the second device in the process of performing service interaction with the first device), and the second user The second device cannot directly initiate a payment operation. Corresponding to the first device in the above example, the second device may be, for example, a smart water cup, a smart lunch box, a smart car, a smart shopping card, a smart door card, or the like. It can be seen that, in some embodiments of the present application, the second device is not a mobile communication terminal (such as a smart phone, a tablet computer, etc.) or a smart wearable device.

The settlement end is configured to provide a payment service, that is, complete payment settlement between the first user and the second user. The settlement end in the embodiment of the present application may be a server, a server cluster, a computer, or the like. In a more common application scenario, the settlement end may be a service server in the background of the service provider (in this case, the service server can provide a payment service), or may be a payment server corresponding to the third-party payment platform, where the third party The payment platform may include: a payment website, a bank, and the like. In addition, in the scenario of using the blockchain technology, the settlement end in FIG. 1 may also be a certain network node in the blockchain network, and the other blockchain network nodes undergo a consensus process to implement payment settlement. . Of course, I won't go into too much detail here. In the following embodiments, a scenario in which the settlement side is a server will be described.

It should be further noted that, in order to enable payment, in an actual business scenario, the first device may be associated with the first user information, and the second device is associated with the second user information.

The first user information may include: a user ID of the first user, account information registered by the first user on the service server or a payment server of the third-party payment platform, and the like. Similarly, the second user information may include: a user ID of the second user, account information registered by the second user at the foregoing service server or a payment server of the third-party payment platform, and the like. Of course, this does not constitute a limitation on the present application.

Based on the architecture described in FIG. 1 above, the technical solutions provided by the embodiments of the present application are described in detail below.

In the embodiment of the present application, the payment process based on the first device side may be as shown in FIG. 2, and specifically includes the following steps:

Step S201: The first device monitors the second device related to the service.

As described above, in the process of performing a service interaction with the first device, the second user needs to use the second device (ie, the second device is related to the service to be obtained by the second user) to obtain the corresponding service service. . Then, the first device can monitor the second device used by the second user. In the embodiment of the present application, the first device may establish a communication connection with the second device by using a communication technology such as Bluetooth communication, Near Field Communication (NFC), Radio Frequency Identification (RFID) communication, or the like. To achieve monitoring of the second device. Of course, this does not constitute a limitation on the present application.

Step S202: When the second device is detected, acquiring the second user information and payment information that matches the service.

As described above, the second device is bound with the second user information, and then the first device can establish a communication connection with the second device to obtain the second user information. The manner of communication connection is as described above, and will not be described here.

In addition, the services to be obtained by the second user often correspond to different payment information. For example, if a user uses different types of business services, the amount they need to pay is different, and the amount here can be regarded as a kind of payment information.

In the embodiment of the present application, the payment information may include: the amount information to be paid, the order number, the service type information, and the like, which are not specifically limited herein.

Step S203: Perform a service, and generate a payment request to the server according to the first user information, the second user information, and the payment information, so that the server processes the payment request.

As described above, when the first device is a device capable of directly providing a service service, the service is performed, and the first device can be considered to directly provide a corresponding service service to the second user, for example, an automatic coffee machine for making a coffee drink, Intelligent fuel dispensers deliver oil to automobiles, vending machines, etc. When the first device is a device related to the service service, the service is executed, and the first device can be regarded as performing an operation that enables the second user to obtain the service service, for example, the smart door lock performs automatic unlocking, so that the user can enable the user to Use the hotel room.

In addition, in the embodiment of the present application, the first device maintains a network connection with the server. The processing of the payment request by the server may be considered as deducting the corresponding amount of the amount from the account of the second user according to the payment amount carried in the payment information, and transferring to the account of the first user. I won’t go into too much detail here.

It can be understood that, because the first device can automatically monitor and obtain the second user information and the corresponding payment information, the second user is reduced or prevented from performing the corresponding payment operation after performing the business operation. So that the user has weak perception or even no perception of the payment process.

Through the above steps, in a service scenario involving a part of the payment, the individual user (ie, the second user) can use the second device that is bound to the user's own user information, and the user that belongs to the service provider (ie, the first user) The first device interacts to obtain the corresponding business service. In such a business scenario, the first device will monitor the second device used by the individual user to obtain the business service. After monitoring the second device, the first device will automatically obtain the user information of the individual user and the payment information bound to the second device. In the embodiment of the present application, the process of acquiring the information by the first device is weakly perceived or unperceived to the individual user, and the individual user does not need to actively issue the payment operation. Thereafter, the first device sends the obtained information and the user information of the service provider user to the server providing the payment service, so that the server completes the payment process based on the information.

As another application scenario in the embodiment of the present application, the second user may also perform a corresponding service operation in the process of obtaining the service service by using the second device, for example, the second user may select a corresponding category on the smart coffee machine. Coffee, where the second user's selection operation is a business operation. That is, in the embodiment of the present application, the service operation may be considered as a behavior, an instruction, and the like issued by the second user to obtain a service, and it should be noted that the service operation in the embodiment of the present application does not include Payment operations, in other words, users do not need to use any payment tools.

Then, the first device monitors the second device related to the service, and specifically, the first device monitors a service operation sent by the second user, and a second device related to the service operation.

As described above, the user needs to use the second device in the process of obtaining the service service. In this scenario, the user sends a corresponding service operation to obtain the service service, and then the second device related to the service can be used. It is considered to be a second device related to business operations.

Of course, in actual operation, the first device can monitor the business operation issued by the second user through a sensor such as its own, a signal acquisition unit, and the like. There is no specific limit here.

Based on this, in the foregoing step S202, acquiring the second user information and the payment information that matches the service may be: acquiring the second user information and the payment information generated based on the service operation.

The business operations issued by the second user generally correspond to corresponding business services, and in the actual business scenario, different business services correspond to different payment information. For example, the user selects the corresponding type of coffee drink on the automatic coffee machine, and the amount of different types of coffee drinks is different. Then, the first device can further obtain the payment information generated by the business operation.

Of course, in the actual service scenario, the first device may fail to obtain the second user information due to the problem of the communication connection with the second device. In this case, the first device may perform the retry operation. After the second user information is not successfully obtained after the set number of retries, the first device may interrupt the business process and prompt.

Take the smart coffee machine as an example: suppose the user selects a certain type of coffee on the smart coffee machine, and puts the smart water cup that is bound to the user's own payment account in the water outlet of the smart coffee machine, if the smart coffee machine is If the user's payment account bound to the smart water cup is not successfully obtained, then the smart coffee machine will not perform the production of the coffee.

That is to say, in the embodiment of the present application, the first device will execute the business process after acquiring the second user information.

In addition, during the stage of providing the service service, the first device may fail to perform successfully due to a malfunction or the like. But at this time, the first device has sent the corresponding payment request to the server, and the server may have completed the payment. In this case, the first device monitors the service status. If the service status is detected as unsuccessful execution, the first device sends a cancel payment request to the server, so that the server cancels the completed payment process (ie, the rollback transaction) ). This should not be construed as limiting the application.

The above is based on the payment process on the first device side. On the server side, the payment method is also provided in the embodiment of the present application. The same can be based on the architecture shown in FIG. :

Step S301: The server receives the payment request sent by the first device.

The payment request is generated by the first device based on the monitored service operation of the second user and the second device related to the service operation. Certainly, based on the foregoing content, the first user information, the second user information, and the payment information may be included in the payment request.

Step S302: Perform payment according to the payment request, and detect a payment status.

In the actual payment scenario, after receiving the payment request, the server will process the payment request, that is, perform the payment according to the payment request. However, the second user's payment account may be in a situation such as insufficient balance, the account is frozen, etc., and the first user's payment account may also have an abnormal account, which will cause the payment to fail. Therefore, the server will check the payment status after the payment is executed.

In the case where the payment status is abnormal, the service performs the following step S303.

Step S303: When the payment status is abnormal, the payment request is recorded.

For step S303, the server records for the payment request to perform the payment based on the recorded payment request at a later time. It can be seen that the way in which the server records the payment request when the payment status is abnormal can be regarded as a kind of “credit” processing manner, that is, although the payment fails, the second user can still obtain the first device. The business service provided, the server can perform payment deduction at some time in the future.

Obviously, it is precisely because of the "selling" payment method that the user can obtain the corresponding business service normally, which helps to enhance the user's business experience.

In the actual operation process, the server may perform a payment attempt based on the recorded payment request according to the set period until the payment status after the payment is performed is normal, or the server may adopt a corresponding monitoring function to trigger the corresponding payment condition. Monitoring is performed to perform payment based on the recorded payment request when the payment trigger condition is monitored. The payment triggering condition may include: the payment account of the first user or the payment account of the second user is thawed, the balance in the payment account of the second user is not less than the payment amount corresponding to the payment request, etc., of course, here It is not intended to limit the application.

In addition, as a feasible manner in the embodiment of the present application, the server may generate corresponding abnormal identifier information, establish a corresponding relationship with the second user information, and send the corresponding information to the second device. Abnormal identification information. After receiving the abnormal identifier information, the second device prompts based on the abnormal identifier information. For example, the second device may prompt by using a light display, a sound, or the like to prompt the second user to pay an abnormality.

On the second device side, a payment method is also provided in the embodiment of the present application, which may also be based on the architecture shown in FIG. 1. The specific process may be as shown in FIG. 4a, including the following steps:

Step S401: The second device establishes a communication connection with the first device by using the first device.

As described above, the first device monitors the second device and, after monitoring the second device, acquires second user information associated with the second device. The process of acquiring the second user information by the first device is actually a process of establishing a communication connection between the first device and the second device and transmitting data.

The communication connection may be the aforementioned Bluetooth, NFC, RFID, etc. connection.

Step S402: Send the second user information to the first device based on the communication connection.

In addition, on the second device side, a payment method is further provided in the embodiment of the present application. The specific process may be as shown in FIG. 4b, and includes the following steps:

Step S411: Receive abnormality identification information sent by the server.

As described above, the abnormality identification information is generated by the server when the first device sends a payment request based on the monitored second device, and detects an abnormality according to the payment request.

Step S412: Perform an abnormality prompt according to the abnormality identification information.

The prompts for the abnormal identification information may be, for example, a light prompt, an audible prompt, etc., and are not specifically limited herein. The prompt for the abnormal identification information is to inform the user that after a certain business operation, the payment is not successful.

In the actual payment scenario, the foregoing payment method in the embodiment of the present application may be as shown in FIG. 5, and includes the following steps:

Step S501: The user issues a business operation for the first device.

Step S502: The first device monitors a service operation sent by the user, and monitors the second device.

Step S503: Acquire account information of the user bound to the second device.

Step S504: The first device determines that the payment status of the user's account is normal.

Step S505: The first device initiates a payment request to the server.

Step S506: The server performs payment according to the payment request, and detects the payment status.

Step S507: When detecting that the payment status is abnormal, the server records the payment request, and generates abnormal identification information corresponding to the account information of the user, and sends the information to the second device.

Step S508: The second device prompts according to the abnormality identification information.

Step S509: The server performs payment for the recorded payment information.

Step S510: The abnormality identification information is eliminated after the payment of the recorded payment information is successful.

It should be understood that the foregoing steps shown in FIG. 5 are only a general procedure in the actual payment scenario in the embodiment of the present application, and the ordering of the execution steps should not constitute a limitation on the present application. Specifically, the step execution sequence adjustment may be performed according to the needs of the actual application.

Based on the payment process in Figure 5, the following describes several specific application examples:

First, the payment scenario based on smart coffee machine

In this scenario, a coffee shop (ie, a merchant) is provided with a smart coffee machine (ie, a first device) that is capable of producing and providing different types of coffee drinks for the consumer (ie, the second user). Consumers use smart water cups (ie, second equipment) as containers for coffee. In addition, the smart water cup is tied to the consumer's payment account, and the smart coffee machine is tied to the merchant's payment account.

On this basis, the consumer selects a certain type of coffee on the smart coffee machine (ie, issues a business operation) and places the smart water cup on the water outlet of the smart coffee machine. The smart coffee machine determines the amount of coffee selected by the consumer and establishes a communication connection with the smart water cup through near field communication to obtain a payment account of the consumer of the smart cup binding. After successfully obtaining the consumer's payment account, the smart coffee machine makes the coffee. At the same time, the smart coffee machine sends the amount to be paid, the payment account of the consumer, and the payment account of the merchant to the payment server to apply for payment of the deduction.

The payment server deducts the corresponding amount from the consumer's payment account according to the amount to be paid, and transfers it to the merchant's payment account. If the balance in the consumer account is insufficient or the set number of attempts have not been successfully paid, then the payment server will record the payment and form a "credit" record. When the payment terms are met, the payment server will prioritize payment for the "credit" record. At the same time, the payment server will send an abnormality identifier to the smart water cup, and the smart water cup will make an abnormal prompt according to the abnormality identifier. For example, if the smart water cup is provided with a prompt light, the smart water cup can display the prompt light as red according to the abnormality identifier to indicate payment. Abnormal.

The smart coffee machine also monitors whether the coffee is normally served. If the coffee is not poured normally, the smart coffee machine also sends a transaction revocation request to the payment server to cause the server to roll back the transaction.

Second, the payment scenario based on smart door lock

In this scenario, a smart door lock (ie, a first device) is provided on each of the guest rooms of the hotel (ie, the merchant), and the consumer (ie, the second user) can use the consumer's own payment account. The smart door card (ie, the second device) is swiped (ie, business operation) for the smart door lock. The smart door lock acquires the payment account of the consumer bound to the smart door card during the consumer performing the card swipe operation, and sends the payment account of the consumer, the payment account of the hotel, and the pre-set payment amount to the payment server, and simultaneously The smart door lock automatically performs unlocking.

In this example, the process of the server performing the payment may refer to the foregoing content, and details are not described herein again.

Third, based on the smart tanker payment scenario

In this scenario, the gas station (ie, the merchant) is equipped with a smart tanker (ie, the first device), and the user (ie, the second user) can use the smart tanker as the smart car of the user (ie, the second device) ) Come on. Among them, the smart car is bound to the user's payment account. When the user docks the refueling gun of the smart refueling machine to the oil delivery port of the smart car, the smart refueling machine establishes a communication connection with the smart car through the communication chip installed on the refueling gun, and acquires the user's payment account. At the same time, as the user presses the valve of the refueling gun, the smart refueling machine delivers oil to the smart car. The fuel gauge on the refueling gun will count the amount of fuel delivered and use this to generate the required payment amount. Thereafter, the smart dispenser sends the user's payment account, the payment account of the gas station, and the amount of money required to be paid to the payment server.

Of course, in addition to the examples listed above, the payment scene based on the smart food machine, the payment scenario based on the vending machine, and the like are also applicable to the above payment method of the present application. For details, refer to the above example. More details.

It can be seen from the above example that the above payment method of the present application is adopted, so that the user only needs to perform corresponding business operations in the process of acquiring the business service without performing an additional payment operation.

The above is the payment method provided by the embodiment of the present application. Based on the same idea, the embodiment of the present application further provides a payment device (ie, the foregoing first device).

As shown in FIG. 6, the payment device is associated with the first user information, and the second device is associated with the second user information, the payment device includes:

The monitoring module 601 monitors a second device related to the service;

The information obtaining module 602 is configured to acquire the second user information and payment information that matches the service when the second device is monitored;

The processing module 603 generates a payment request to the server according to the first user information, the second user information, and the payment information, so that the server processes the payment request.

Business component 600, performing business.

It should be noted here that the service component 600 is a hardware structure on the payment device shown in FIG. 6 capable of providing a service service or related to a service service. For example: smart coffee machines, vending machines, etc.

The service component 600 and the foregoing modules may be independent of each other, or the modules may be wholly or partially carried on the service component 600. This is not specifically limited.

The monitoring module 601 monitors a service operation sent by a second user, and a second device related to the service operation;

The information obtaining module 602 acquires the second user information and payment information generated based on the service operation.

The payment information includes at least: a payment amount. The processing module 603 determines a service type corresponding to the service operation, determines a payment amount matching the service operation according to a correspondence between a preset service type and a payment amount, and generates a payment amount according to the payment amount. Payment information for the business operation.

The apparatus further includes a payment revocation module 604 that monitors a service status and, when it is detected that the service status is unsuccessfully executed, sends a revocation request to the server to cause the server to revoke processing of the payment request.

The device further includes: a determining module 605, before determining that the payment status corresponding to the second user information is normal, before performing the service according to the service operation.

The device shown in FIG. 6 may specifically include: a device for providing a service service for the second user, or a device related to a service service; wherein the payment device is capable of issuing a payment request to the server. Such as: smart door locks, smart coffee machines, smart food pickers, smart tankers, vending machines.

The second device includes: the device required by the second user to obtain a service service provided by the first device or related to the first device. Such as: smart door card, smart water cup, smart lunch box, smart car, smart shopping card.

The embodiment of the present application further provides a server-side payment device. As shown in FIG. 7, the device includes:

The receiving module 701 is configured to receive a payment request sent by the first device, where the payment request is generated by the first device based on the monitored second device related to the service;

The processing module 702 performs payment according to the payment request, and detects a payment status;

The recording module 703 records the payment request when it is detected that the payment status is abnormal.

The processing module 702 performs payment according to the recorded payment request according to the set period until the payment status is normal, or monitors the payment trigger condition, and when the payment trigger condition is monitored, based on the record The payment request performs payment.

The device further includes: an abnormality marking module 704, when the processing module detects that the payment status of the second user information corresponding to the second device is abnormal, generating abnormal identification information for the second user information, so that The second device bound to the second user information performs an abnormal prompt based on the abnormality identification information.

The embodiment of the present application further provides a payment device (ie, the foregoing second device). As shown in FIG. 8, the payment device is associated with the second user information, and the payment device includes:

The device body 800 carries a communication module 801;

The communication module 801 establishes a communication connection with the first device under the action of the first device, and sends the second user information to the first device based on the communication connection.

Based on the payment device shown in FIG. 8 , the embodiment of the present application further provides a payment device (also a second device), as shown in FIG. 9 , including:

The device body 900, the bearer receiving module 901 and the prompting module 902;

The receiving module 901 receives the abnormality identifier information sent by the server, where the abnormality identifier information is received by the server, and the payment request sent by the first device based on the monitored second device is received, and the payment state is detected abnormally according to the payment request. Generated at the time.

The prompting module 902 performs an abnormality prompt according to the abnormality identification information.

Corresponding to the application examples listed in the foregoing method content:

First, the payment scenario based on smart coffee machine

The embodiment of the present application provides a smart coffee machine (ie, a first device), including:

The body can make coffee drinks according to the operation of the consumer.

Monitoring module to monitor smart water cups.

The information acquisition module acquires consumer information and payment information associated with the smart water cup when the smart water cup is monitored.

The processing module generates a payment request and sends the payment request to the settlement terminal according to the merchant information, the consumer information, and the payment information associated with the smart coffee machine.

The embodiment of the present application further provides a smart water cup (ie, a second device), including:

Cup body for drinks.

The communication module establishes a communication connection with the smart coffee machine, and sends the consumer information associated with the smart water cup to the smart coffee machine based on the communication connection; and the abnormal identification information sent by the settlement terminal is also received.

Second, the payment scenario based on smart door lock

An embodiment of the present application provides a smart door lock (ie, a first device), including:

A door lock component that performs physical locking and physical unlocking.

Monitoring module to monitor smart door cards.

The information acquisition module acquires consumer information and payment information associated with the smart door card when the smart door card is detected.

The processing module generates a payment request and sends the payment request to the settlement terminal according to the merchant information, the consumer information, and the payment information associated with the smart door lock.

The embodiment of the present application further provides a smart door card (ie, a second device), including:

Physical card.

The communication module establishes a communication connection with the smart door lock, and sends the consumer information associated with the smart door card to the smart door lock based on the communication connection; and the abnormal identification information sent by the settlement terminal is also received.

Third, based on the smart tanker payment scenario

The embodiment of the present application provides a smart fuel dispenser (ie, a first device), including:

The body and oil delivery components can be used for oil storage and delivery.

Monitoring module to monitor smart cars and oil delivery.

The information acquisition module acquires consumer information associated with the smart car and payment information corresponding to the amount of oil delivered when the smart car and the fuel quantity are monitored.

The processing module generates a payment request and sends the payment request to the settlement terminal according to the merchant information, the consumer information, and the payment information associated with the smart tanker.

The embodiment of the present application further provides a smart car (ie, a second device), including:

Car body.

The communication module establishes a communication connection with the smart tanker, and sends the consumer information associated with the smart car to the smart tanker based on the communication connection; and the abnormal identifier information sent by the settlement terminal is also received.

Of course, the payment device provided by the embodiment of the present application is not limited to the above example, and details are not described herein again.

In the 1990s, improvements to a technology could clearly distinguish between hardware improvements (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (for process flow improvements). However, as technology advances, many of today's method flow improvements can be seen as direct improvements in hardware circuit architecture. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented by hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by the user programming the device. Designers program themselves to "integrate" a digital system on a single PLD without having to ask the chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, today, instead of manually making integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in programming development, but before compiling The original code has to be written in a specific programming language. This is called the Hardware Description Language (HDL). HDL is not the only one, but there are many kinds, such as ABEL (Advanced Boolean Expression Language). AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be apparent to those skilled in the art that the hardware flow for implementing the logic method flow can be easily obtained by simply programming the method flow into the integrated circuit with a few hardware description languages.

The controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. In the form of logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art will also appreciate that in addition to implementing the controller in purely computer readable program code, the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding. The form of a microcontroller or the like to achieve the same function. Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component. Or even a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit may be implemented in the same software or software and/or hardware when implementing the present application.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. 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 device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

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

The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium.

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

It is also to be understood that the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, Other elements not explicitly listed, or elements that are inherent to such a process, method, commodity, or equipment. An element defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device including the element.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular transactions or implement particular abstract data types. The present application can also be practiced in distributed computing environments where transactions are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The above description is only an embodiment of the present application and is not intended to limit the application. Various changes and modifications can be made to the present application by those skilled in the art. Any modifications, equivalents, improvements, etc. made within the spirit and scope of the present application are intended to be included within the scope of the appended claims.

Claims

A payment method, the first device is associated with the first user information, and the second device is associated with the second user information; the method includes:

The first device monitors a second device related to the service;

Obtaining the second user information and payment information matching the service when the second device is monitored;

The service is executed, and a payment request is generated and sent to the settlement terminal according to the first user information, the second user information, and the payment information.
The method of claim 1, the first device monitoring the second device related to the service, specifically comprising:

The first device monitors a service operation sent by a second user, and a second device related to the service operation;

Obtaining the second user information and the payment information that matches the service, specifically:

Obtaining the second user information and payment information generated based on the business operation.
The method of claim 2, wherein the payment information comprises at least: a payment amount;

The generating the payment information based on the service operation includes:

Determining a service type corresponding to the service operation;

Determining a payment amount matching the business operation according to a correspondence between a preset service type and a payment amount;

The payment information of the business operation is generated according to the payment amount.
The method of claim 1 further comprising:

The first device monitors a service status;

When it is detected that the service status is unsuccessful execution, the revocation request is sent to the settlement terminal, so that the settlement terminal cancels the processing of the payment request.
The method of claim 1 further comprising: before performing the service, the method further comprising:

The first device determines that the payment status corresponding to the second user information is normal.
The method according to any one of claims 1 to 5, wherein the first device comprises: a device for providing a service service to the second user, or a device related to a service service; wherein the first device The device is also used to issue a payment request to the settlement terminal;

The second device includes: the device required by the second user to obtain a service service provided by the first device or related to the first device.
A payment method, the first device is associated with the first user information, and the second device is associated with the second user information; the method includes:

Receiving, by the settlement device, a payment request sent by the first device, where the payment request is generated by the first device based on the monitored second device related to the service;

Performing payment according to the payment request, and detecting a payment status;

The payment request is recorded when the payment status is abnormal.
The method of claim 7 further comprising:

Performing payment based on the recorded payment request according to the set period until the payment status is normal; or

The payment trigger condition is monitored, and when the payment trigger condition is monitored, the payment is performed based on the recorded payment request.
The method of claim 7 further comprising:

When detecting that the payment status of the second user information corresponding to the second device is abnormal, generating abnormality identification information for the second user information, and notifying the second device, so that the second user information is The bound second device performs an abnormal prompt based on the abnormal identifier information.
A payment method, the second device is associated with the second user information; the method includes:

The second device establishes a communication connection with the first device under the action of the first device;

Sending the second user information to the first device based on the communication connection.
A payment method comprising:

The second device receives the abnormality identification information sent by the settlement terminal; wherein the abnormality identification information is received by the settlement terminal by the first device based on the monitored second device, and the payment status is detected according to the payment request. Generated when an exception occurs;

An abnormal prompt is performed according to the abnormality identification information.
A payment device, associated with the first user information, the second device being associated with the second user information; the device comprising:

a monitoring module for monitoring a second device related to the service;

An information acquiring module, when the second device is monitored, acquiring the second user information and payment information that matches the service;

Business component, performing business;

The request transmission module generates a payment request and sends the payment request to the settlement terminal according to the first user information, the second user information, and the payment information.
The device according to claim 12, wherein the monitoring module monitors a service operation sent by the second user and a second device related to the service operation;

The information acquiring module acquires the second user information and payment information generated based on the service operation.
The device according to claim 13, wherein the payment information includes at least: a payment amount;

Determining, by the processing module, a service type corresponding to the service operation, determining, according to a correspondence between a preset service type and a payment amount, a payment amount matching the service operation, and generating a location according to the payment amount The payment information of the business operation.
The apparatus according to claim 12, said apparatus further comprising: a payment revocation module, monitoring a service status, and transmitting a revocation request to said settlement terminal to cause said settlement when said service status is detected as unsuccessfully executed The processing of the payment request is revoked.
The apparatus of claim 12, the apparatus further comprising: a determining module that determines that the payment status corresponding to the second user information is normal before performing the service according to the service operation.
A payment device, the first device is associated with the first user information, and the second device is associated with the second user information; the device comprises:

Receiving, by the receiving module, a payment request sent by the first device, where the payment request is generated by the first device based on the monitored second device related to the service;

Processing a module, performing payment according to the payment request, and detecting a payment status;

The recording module records the payment request when the payment status is abnormal.
The apparatus according to claim 17, wherein said processing module performs payment based on said recorded payment request in accordance with a set period until a payment status is normal; or

The payment trigger condition is monitored, and when the payment trigger condition is monitored, the payment is performed based on the recorded payment request.
The device according to claim 17, further comprising: an abnormality marking module, when the processing module detects that the payment status of the second user information corresponding to the second device is abnormal, for the second user The information generates the abnormality identification information, and notifies the second device, so that the second device that is bound to the second user information performs an abnormal prompt based on the abnormality identification information.
A payment device is associated with second user information, the device comprising:

The device body carries the communication module;

The communication module establishes a communication connection with the first device under the action of the first device, and sends the second user information to the first device based on the communication connection.
A payment device comprising:

a device body, carrying a receiving module and a prompting module;

The receiving module receives the abnormality identification information sent by the settlement terminal, wherein the abnormality identification information is received by the settlement terminal by the first device based on the monitored second device, and the payment status is detected according to the payment request. Generated when an exception occurs;

The prompting module performs an abnormal prompt according to the abnormality identification information.