Payment processing method, device and server

By preconfiguring and storing payment authorization information by the user, the payment service provider determines whether to receive payment from the receiving user, which solves the problem of insufficient payment convenience for non-registered users and realizes a convenient mobile payment experience.

CN113421087BActive Publication Date: 2024-11-08ADVANCED NEW TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110661593.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-06-12
Publication Date
2024-11-08
Estimated Expiration
2038-06-12

AI Technical Summary

Technical Problem

In the existing mobile payment technology, non-registered users need to carry portable terminals when making payments, which limits the convenience and user experience of payment.

Method used

Provide a payment processing method, where users can preconfigure payment authorization information for themselves or others and hand it over to the payment service provider to store. During the payment process, the payment requester provides the payment account identification and payment authorization information, and the payment service provider determines whether the payment is incurred. The payment user receives payment, including using designated images and password location information, biometric information, etc., to support non-registered users to complete payment without carrying a portable terminal.

Benefits of technology

It realizes that non-registered users can complete payments easily, improving the convenience and user experience of payments, and users can make mobile payments without carrying a portable terminal.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113421087B_ABST
    Figure CN113421087B_ABST
Patent Text Reader

Abstract

The embodiments of this specification provide a payment processing method, device and server. Users can pre-configure payment authorization information for themselves or others and store it in the payment service provider. During the payment process, the payment demander provides the payment account identifier and payment authorization information to the payee, and the payment service provider can determine whether to collect payment from the payee based on this information. In this embodiment, the payment demander can be a non-registered user, and can complete the payment even if he does not carry a portable terminal.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application with the application date of June 12, 2018, application number 201810599899.1, and the name of the invention being “Payment processing method, device and server”. Technical Field

[0002] This specification relates to the field of Internet technology, and in particular to payment processing methods, devices and servers. Background Art

[0003] With the development of Internet technology and terminal technology, mobile payment has become a common payment method in people's daily life. Users can register payment accounts on mobile payment platforms and use portable terminals such as smart phones to install APPs (applications) with payment functions. When users pay, APPs can display payment codes for the payee's scanning device to scan and complete the payment. Based on this, a more convenient payment processing solution is needed. Summary of the invention

[0004] To overcome the problems existing in the related art, the embodiments of this specification provide a payment processing method, device and server.

[0005] According to a first aspect of an embodiment of this specification, a payment processing method is provided, including:

[0006] The payee initiates a payment request to the payment service provider, and the payment request carries: the payment account identifier and payment authorization information provided by the payment demander;

[0007] After the payment service provider searches for the payment authorization information pre-configured by the payment user through the payment account identifier, it determines whether the searched payment authorization information matches the payment authorization information carried in the payment request, and determines whether to collect payment from the payment user based on the judgment result.

[0008] Optionally, the payment authorization information preconfigured by the paying user includes: a designated image and password location information in the designated image.

[0009] Optionally, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

[0010] Optionally, the payment authorization information carried in the payment request includes: an image taken by the payee, and location information triggered by the payment demander on the taken image.

[0011] Optionally, whether the searched payment authorization information matches the payment authorization information carried in the payment request is determined based on whether the captured image matches the designated image, and whether the triggered location information matches the password location information.

[0012] Optionally, the payment authorization information includes: biometric information.

[0013] Optionally, the payment user is different from the payment requester, or the payment user and the payment requester are the same party.

[0014] Optionally, the determination of whether to collect payment from the paying user is also based on one or more of the following information: the payment amount, the geographical location where the payment request is initiated, the payment time, or the user information of the payee.

[0015] Optionally, the method further includes: the payment service provider pushing a payment receipt message to the paying user.

[0016] According to a second aspect of the embodiments of this specification, a payment processing method is provided, including:

[0017] Receive a payment request initiated by a payee, wherein the payment request carries: a payment account identifier and payment authorization information provided by a payment demander;

[0018] After searching for the payment authorization information pre-configured by the payee through the payment account identifier, it is determined whether the searched payment authorization information matches the payment authorization information carried in the payment collection request, and whether to collect payment from the payee is determined based on the determination result.

[0019] Optionally, the payment authorization information preconfigured by the paying user includes: a designated image and password location information in the designated image.

[0020] Optionally, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

[0021] Optionally, the payment authorization information carried in the payment request includes: an image taken by the payee, and location information triggered by the payment demander on the taken image.

[0022] Optionally, whether the searched payment authorization information matches the payment authorization information carried in the payment request is determined based on whether the captured image matches the designated image, and whether the triggered location information matches the password location information.

[0023] Optionally, the preconfigured payment authorization information or the payment authorization information carried in the payment request includes: biometric information.

[0024] Optionally, the payment user is different from the payment requester, or the payment user and the payment requester are the same party.

[0025] Optionally, the determination of whether to collect payment from the paying user is also based on one or more of the following information: the payment amount, the geographical location where the payment request is initiated, the payment time, or the user information of the payee.

[0026] Optionally, the method further includes: pushing a payment collection message to the paying user.

[0027] According to a third aspect of the embodiments of this specification, a payment processing device is provided, including:

[0028] The receiving module is used to receive a payment request initiated by a payee, wherein the payment request carries a payment account identifier and payment authorization information provided by a payment demander;

[0029] The judgment module is used to: after searching for the payment authorization information pre-configured by the payee through the payment account identifier, determine whether the searched payment authorization information matches the payment authorization information carried by the payment collection request, and determine whether to collect payment from the payee based on the judgment result.

[0030] Optionally, the payment authorization information preconfigured by the paying user includes: a designated image and password location information in the designated image.

[0031] Optionally, the payment authorization information carried in the payment request includes: an image taken by the payee, and location information triggered by the payment demander on the taken image.

[0032] Optionally, whether the searched payment authorization information matches the payment authorization information carried in the payment request is determined based on whether the captured image matches the designated image, and whether the triggered location information matches the password location information.

[0033] Optionally, the preconfigured payment authorization information or the payment authorization information carried in the payment request includes: biometric information of the payment requester.

[0034] Optionally, the payment user is different from the payment requester, or the payment user and the payment requester are the same party.

[0035] Optionally, the determination of whether to collect payment from the paying user is also based on one or more of the following information: the payment amount, the geographical location where the payment request is initiated, the payment time, or the user information of the payee.

[0036] Optionally, the device further comprises a push module, configured to push a payment collection message to the paying user.

[0037] According to a fourth aspect of an embodiment of this specification, a server is provided, including:

[0038] processor;

[0039] a memory for storing processor-executable instructions;

[0040] Wherein, the processor is configured to:

[0041] Receive a payment request initiated by a payee, wherein the payment request carries: a payment account identifier and payment authorization information provided by a payment demander;

[0042] After searching for the payment authorization information pre-configured by the payee through the payment account identifier, it is determined whether the searched payment authorization information matches the payment authorization information carried in the payment collection request, and whether to collect payment from the payee is determined based on the determination result.

[0043] The technical solutions provided by the embodiments of this specification may have the following beneficial effects:

[0044] In the embodiments of this specification, users can pre-configure payment authorization information for themselves or others and store it in the payment service provider. During the payment process, the payment demander provides the payment account identifier and payment authorization information to the payee, and the payment service provider can determine whether to collect payment from the payee based on this information. In this embodiment, the payment demander can be a non-registered user and can complete the payment even if he does not carry a portable terminal.

[0045] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.

[0047] Figure 1 It is a schematic diagram of a payment processing scenario shown in this specification according to an exemplary embodiment.

[0048] Figure 2A It is a schematic diagram of an application scenario of a payment processing method shown in this specification according to an exemplary embodiment.

[0049] Figure 2B The figure is a schematic diagram of password position information of a specified image according to an exemplary embodiment of the present specification.

[0050] Figure 2C It is a flow chart of a payment processing method shown in this specification according to an exemplary embodiment.

[0051] Figure 3 It is a flow chart of another payment processing method shown in this specification according to an exemplary embodiment.

[0052] Figure 4 It is a hardware structure diagram of the server where the payment processing device of this manual is located.

[0053] Figure 5 It is a block diagram of a payment processing device shown in this specification according to an exemplary embodiment. DETAILED DESCRIPTION

[0054] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

[0055] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0056] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0057] like Figure 1 FIG. 1 is a schematic diagram of a payment processing scenario according to an exemplary embodiment of the present specification. Figure 1 The offline payment scenarios involved include payment service providers, users, and payees. For example, the portable terminal held by the user is a smartphone. Zhang San is a registered user of the payment service provider and can obtain payment, collection or fund transfer services provided by the payment service provider. Figure 1 Taking an offline store as an example, the payee is also a registered user of the payment service provider and can obtain payment, collection or fund transfer services provided by the payment service provider.

[0058] If user Zhang San needs to pay for goods purchased in the store, Zhang San can use the payment APP installed on his smartphone to initiate a payment request to the payment service provider by displaying a QR code with payment credentials, etc., and the store will scan the QR code, etc. The payment service provider will collect the payment from the user and then transfer the funds to the store's account.

[0059] As can be seen from the above payment scenarios, only registered users of the payment service provider can obtain payment services, and users also need to carry a portable terminal to complete the payment process. Based on this, the embodiments of this specification provide a payment processing solution, where users can pre-configure payment authorization information for themselves or others and store it in the payment service provider. During the payment process, the payment demander provides the payment account identifier and payment authorization information to the payee, and the payment service provider can determine whether to collect payment from the payee based on this. In this embodiment, the payment demander can be a non-registered user and can complete the payment without carrying a portable terminal.

[0060] like Figure 2A FIG. 1 is a schematic diagram of another payment processing scenario according to an exemplary embodiment of the present specification. Figure 2A The illustrated embodiment involves two aspects:

[0061] (1) User pre-configured payment authorization information:

[0062] like Figure 2A As shown, user Zhang San is a registered user of the payment service provider. Zhang San hopes that his mother can use his account to make mobile payments, and Zhang San also hopes to be able to make mobile payments without carrying a portable terminal. Based on the solution of the embodiment of the present application, user Zhang San can configure payment authorization information, which can be different from the payment password and is sent to the payment service provider to indicate that the user authorizes others or that the payment service provider can deduct money from his account when he does not carry a portable terminal.

[0063] In actual applications, there are many options for payment authorization information. For example, it can include biometric information, including but not limited to fingerprint information, iris information, face information or voiceprint information. These biometric information can be the user's own biometric information, or the biometric information of other people entered by the user. Of course, the use of the above biometric information requires that the payee's device has a function for collecting biometric information.

[0064] In other examples, the payment authorization information may also include: a designated image and password position information in the designated image. The designated image may be uploaded by the user. Since the image may be copied, the present embodiment requires the user to configure the password position on the designated image to obtain the password position information. As an example, there may be multiple password positions configured by the user. Based on the password positions configured by the user on the image, one or more of the following password position information may be obtained: the password position information may be determined by one or more combinations of pixel point information corresponding to the password position, the order in which the password positions are configured, and the trajectory of moving from one password position to another password position.

[0065] exist Figure 2A In the example, user Zhang San takes a photo of his mother's face as the designated image. Figure 2B FIG. 1 is a schematic diagram of configuring password positions according to an exemplary embodiment of the present specification. User Zhang San configures 4 password positions on the image. Figure 2C Taking points Q1 to Q4 as an example, the configuration process may be triggered by a user's finger on the touch screen, the device may detect the touch position of the user's finger on the touch screen, and the touch screen displays the image, so the password position on the image may be determined based on the touch position.

[0066] Based on this, the pixel information is determined by obtaining the password position information. For example, the four password positions Q1 to Q4 correspond to one or more pixel points respectively, wherein the pixel information may include but is not limited to: pixel value, brightness, gradient or grayscale, etc., and can be flexibly configured based on image recognition technology in practical applications. Optionally, in the case of multiple password positions, the order in which each password position is configured can also be obtained as a kind of password position information.

[0067] Figure 2B The configuration order of the four password positions and the tracks between the password positions are also shown with dotted lines. Optionally, in the case of multiple password positions, one or more combinations such as tracks moving from one password position to another password position can also be obtained as a type of password position information.

[0068] Optionally, user Zhang San can also set more designated images and password positions. For example, Zhang San can also take an image of his own palm or other objects as another designated image, and configure the password position accordingly.

[0069] In actual applications, the payment service provider can implement the configuration process through the client, which can be installed on the user's personal device. The client can provide a configuration interface for payment authorization information, receive the payment authorization information configured by the user through the interface, and then send it to the server for storage.

[0070] Optionally, in actual applications, based on stricter security considerations, users can configure more restriction information, so that the payment service provider can determine whether to deduct money based on more factors. As an example:

[0071] Based on the amount of the payment, the larger amount of the payment can be restricted, so the user can configure the amount range that can be paid;

[0072] Based on the consideration of active time, the payment time can be set, so that the time range of such payment processing can be limited, such as only on weekends, weekdays or daytime, etc.;

[0073] Based on the user's geographic location, you can set the payment location range, for example, you can limit payment to the user's residential city, etc.

[0074] Based on the user's consumption habits, the payee information can be set. For example, it can be set to allow only certain payers (convenience stores, supermarkets, etc.) to receive payments.

[0075] (2) Payment stage

[0076] Combination Figure 2C To explain, Figure 2C This is a schematic diagram of a payment processing method according to an exemplary embodiment of this specification. In this embodiment, the payee and the payment service provider cooperate with each other to perform the following process:

[0077] In step 202, the payee initiates a payment request to the payment service provider, and the payment request carries: the payment account identifier and payment authorization information provided by the payment demander.

[0078] In step 204, the payment service provider searches for the payment authorization information preconfigured by the payee through the payment account identifier, determines whether the searched payment authorization information matches the payment authorization information carried in the payment request, and determines whether to collect payment from the payee based on the judgment result.

[0079] Combination Figure 2A , the payment demander (Zhang San's mother) consumes in an offline store, and Zhang San's mother expects that the user Zhang San can pay the bill. Zhang San's mother can provide the payment account identifier and payment authorization information to the payee. In this embodiment, the payment user (Zhang San) is different from the payment demander (Zhang San's mother), while in other examples, the payment user and the payment demander can also be the same party, that is, Zhang San can also use the payment processing method of this embodiment to complete the payment.

[0080] Among them, the payment account identifier is used by the payment service provider to identify the registered user that the payment demander expects to pay. Therefore, the payment account identifier can be one or more network identity identification identifiers such as mobile phone number, ID number, account name, etc. that can uniquely distinguish users, so that the payment service provider can find the specific user. Optionally, in actual applications, the payment demander can inform the payee and the payee can enter it into the device. For greater security considerations, the payment demander can also use the payee's device to enter it. In this process, the payment demander can use various methods such as shielding to prevent others from peeping, and the payee's device can also use encryption and other security mechanisms to prevent the payment account identifier from being displayed in plain text and can be encrypted for storage or transmission.

[0081] In addition, the payment demander is also required to provide payment authorization information so that the payment service provider can determine whether the payment demander is the party pre-authorized by the registered user. If the payment authorization information includes biometric information, the payment demander's biometric information can be collected by the payee's device. Optionally, the payee's device can also use some security mechanisms such as encryption to encrypt, store or send the biometric information.

[0082] If the payment authorization information includes a designated image and password location information, the image can be captured by the payee's device, and optionally, Figure 2A For example, the payee's device takes a picture of Zhang San's mother's face; in other examples, Zhang San's mother may carry a device that stores her face image, and Zhang San's mother displays the image, and the payee's device takes the image displayed by the device as the designated image. It is understandable that if Zhang San pre-configures an image of his palm as the designated image, Zhang San can also be the payment demander, and the payee's device takes an image of Zhang San's palm.

[0083] After capturing an image, the payment demander needs to configure the location information on the captured image. For example, the payee's device has a touch screen, and the payment demander can touch the captured image, so that the payee's device can obtain the location triggered by the payment demander on the captured image, and then determine the location information. In actual applications, the payment demander can use various methods such as blocking to prevent others from peeping, and the payee's device can also use some security mechanisms such as encryption to encrypt and store the triggered location information.

[0084] Afterwards, the payee's device can send a payment request carrying the payment account identifier and payment authorization information to the payment service provider. The payment service provider can find the payee through the payment account identifier and the payment authorization information pre-configured by the payee, and then determine whether the found payment authorization information matches the payment authorization information carried in the payment request, and determine whether to collect payment from the payee based on the judgment result.

[0085] As an example, if the payment authorization information is biometric information, the pre-configured payment authorization information is compared with the payment authorization information carried by the payment request to see if they are the same. If the payment authorization information is a specified image and password location information, an image recognition algorithm can be used to determine whether the captured image matches the specified image. Whether the match can be determined based on the similarity of the two images. The specific implementation can use an existing image recognition algorithm, which is not limited in this embodiment; on the other hand, it is also necessary to determine whether the triggered location information matches the pre-configured password location information. For example, it can be determined based on one or more factors such as whether the pixel information is similar, whether the order in which each password location is configured is the same, and whether the trajectory from one password location to another password location is the same.

[0086] Optionally, the payment request may also carry other information, such as request time, user information of the payee, payment amount, geographic location of the payment request, etc. The payment service provider may also determine whether to collect the payment based on the restriction information pre-configured by the paying user. In actual applications, the payment service provider may also flexibly configure other risk control strategies as needed, and ultimately decide whether to deduct money from the user based on one or more factors.

[0087] Optionally, before or after the payment service provider deducts money from the paying user, the payment service provider may also push a payment receipt message to the paying user. The specific push method may be sending text messages, sending emails, pushing messages within the client, making phone calls, etc., which is not limited in this embodiment.

[0088] like Figure 3 FIG. 1 is a flowchart of another payment processing method according to an exemplary embodiment of the present specification. This embodiment describes the payment processing scheme from the perspective of the payment service provider. The method includes:

[0089] In step 302, a payment request initiated by the payee is received, and the payment request carries: a payment account identifier and payment authorization information provided by the payment demander.

[0090] In step 304, after searching for the payment authorization information pre-configured by the payee through the payment account identifier, it is determined whether the searched payment authorization information matches the payment authorization information carried in the payment request, and it is determined whether to collect payment from the payee based on the determination result.

[0091] Optionally, the payment authorization information preconfigured by the paying user includes: a designated image and password location information in the designated image.

[0092] Optionally, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

[0093] Optionally, the payment authorization information carried in the payment request includes: an image taken by the payee, and location information triggered by the payment demander on the taken image.

[0094] Optionally, whether the searched payment authorization information matches the payment authorization information carried in the payment request is determined based on whether the captured image matches the designated image, and whether the triggered location information matches the password location information.

[0095] Optionally, the preconfigured payment authorization information or the payment authorization information carried in the payment request includes: biometric information.

[0096] Optionally, the payment user is different from the payment requester, or the payment user and the payment requester are the same party.

[0097] Optionally, the determination of whether to collect payment from the paying user is also based on one or more of the following information: the payment amount, the geographical location where the payment request is initiated, the payment time, or the user information of the payee.

[0098] Optionally, the method further includes: pushing a payment collection message to the paying user.

[0099] Corresponding to the embodiments of the aforementioned payment processing method, this specification also provides embodiments of a payment processing device and a terminal used therein.

[0100] The embodiments of the payment processing device in this specification can be applied to devices such as servers. The device embodiments can be implemented by software, hardware, or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the payment processing where it is located reading the corresponding computer program instructions in the non-volatile memory into the memory and running them. From the hardware level, such as Figure 4 The figure is a hardware structure diagram of the server where the payment processing device of this specification is located, except Figure 4 In addition to the processor 410, memory 430, network interface 420, and non-volatile memory 440 shown, the server where the device 431 is located in the embodiment may also include other hardware according to the actual function of the server, which will not be described in detail.

[0101] like Figure 5 As shown, Figure 5is a block diagram of a payment processing device according to an exemplary embodiment of the present specification, the device comprising:

[0102] The receiving module 51 is used to receive a payment request initiated by a payee, wherein the payment request carries a payment account identifier and payment authorization information provided by a payment demander;

[0103] The judgment module 52 is used to: after searching for the payment authorization information pre-configured by the payee through the payment account identifier, determine whether the searched payment authorization information matches the payment authorization information carried in the payment collection request, and determine whether to collect payment from the payee based on the judgment result.

[0104] Optionally, the payment authorization information preconfigured by the paying user includes: a designated image and password location information in the designated image.

[0105] Optionally, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

[0106] Optionally, the payment authorization information carried in the payment request includes: an image taken by the payee, and location information triggered by the payment demander on the taken image.

[0107] Optionally, whether the searched payment authorization information matches the payment authorization information carried in the payment request is determined based on whether the captured image matches the designated image, and whether the triggered location information matches the password location information.

[0108] Optionally, the preconfigured payment authorization information or the payment authorization information carried in the payment request includes: biometric information of the payment requester.

[0109] Optionally, the payment user is different from the payment requester, or the payment user and the payment requester are the same party.

[0110] Optionally, the determination of whether to collect payment from the paying user is also based on one or more of the following information: the payment amount, the geographical location where the payment request is initiated, the payment time, or the user information of the payee.

[0111] Optionally, the device further comprises a push module, configured to push a payment collection message to the paying user.

[0112] Accordingly, the present specification also provides a server, the server comprising a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to:

[0113] Receive a payment request initiated by a payee, wherein the payment request carries: a payment account identifier and payment authorization information provided by a payment demander;

[0114] After searching for the payment authorization information pre-configured by the payee through the payment account identifier, it is determined whether the searched payment authorization information matches the payment authorization information carried in the payment collection request, and whether to collect payment from the payee is determined based on the determination result.

[0115] The implementation process of the functions and effects of each module in the above-mentioned payment processing device is specifically described in the implementation process of the corresponding steps in the above-mentioned payment processing method, which will not be repeated here.

[0116] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0117] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0118] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention claimed herein. The specification is intended to cover any variations, uses or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not claimed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.

[0119] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0120] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A payment processing method, applicable to a payee, comprising: During the payment process of the payment demander, the payment account identifier input by the payment demander through the user interaction interface of the terminal provided by the payee is obtained, and a first image is collected with the cooperation of the payment demander and displayed to the payment demander through the user interaction interface, so that the payment demander triggers the password position information on the first image; The payment account identifier and the first image carrying the password location information triggered by the payment demander are sent to the payment service provider, so that the payment service provider searches for the second image bound to the payment account identifier and pre-set with the password location information, and determines whether to collect payment from the payment account corresponding to the payment account identifier based on the matching result between the first image carrying the password location information triggered by the payment demander and the second image pre-set with the password location information.

2. According to the method of claim 1, the payment demander comprises: The user who registers the payment account; or One or more other users other than the user who registered the payment account.

3. The method according to claim 1, further comprising: Acquire the biometric information of the payment demander, and send the biometric information to the payment service provider, so that the payment demander can determine to collect the payment from the payment account when the first image matches the second image and the biometric information of the payment demander matches the pre-set biometric information, wherein the pre-set biometric information is found based on the payment account identifier.

4. The method according to claim 1, further comprising: Attribute information related to the collection of payment is obtained and sent to the payment service party, so that the payment demander can determine to collect payment from the payment account when the first image carrying the password location information triggered by the payment demander matches the second image pre-set with the password location information, and the attribute information meets the restriction conditions pre-set by the user, wherein the restriction conditions pre-set by the user are obtained by searching based on the payment account identifier, and the attribute information includes one or more of the following: the collection amount, the geographical location where the collection request is initiated, the collection time, or the user information of the recipient.

5. According to the method of claim 3 or 4, the matching of the first image carrying the password location information triggered by the payment demander and the second image pre-set with the password location information comprises: The content of the first image matches the content of the second image, and the password position information triggered by the payment demander in the first image matches the password position information preset in the second image.

6. According to the method of claim 1, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

7. A payment processing method, applicable to a payment service provider, the method comprising: Receive a payment account identifier sent by a payee and a first image carrying password location information triggered by a payment demander, wherein the payment account identifier is input by the payment demander through a user interaction interface of a terminal provided by the payee, the first image is collected by the payee with the cooperation of the payment demander, and the password location information carried in the first image is triggered by the payment demander on the first image after the payee displays the first image to the payment demander through the user interaction interface; Search for a second image with password location information pre-set and bound to the payment account identifier, and determine whether to collect payment from the payment account corresponding to the payment account identifier based on the matching result between the first image carrying the password location information triggered by the payment demander and the second image with password location information pre-set.

8. The method according to claim 7, wherein the payment demander comprises: the user who registered the payment account, or One or more other users other than the user who registered the payment account.

9. The method according to claim 7, further comprising: Receiving biometric information of the payment requester sent by the payee; Determining whether to collect payment from the payment account corresponding to the payment account identifier based on a matching result between the first image carrying the password location information triggered by the payment demander and the second image with the password location information preset therein comprises: When the first image carrying the password location information triggered by the payment demander matches the second image with the password location information preset, and the biometric information of the payment demander matches the preset biometric information, it is determined that the payment account is collected, wherein the preset biometric information is obtained by searching based on the payment account identifier.

10. The method according to claim 7, further comprising: Receiving attribute information related to payment sent by the payee, the attribute information including one or more of the following: payment amount, geographic location of initiating payment request, payment time or user information of the payee; Determining whether to collect payment from the payment account corresponding to the payment account identifier based on a matching result between the first image carrying the password location information triggered by the payment demander and the second image with the password location information preset therein comprises: When the first image carrying the password location information triggered by the payment demander matches the second image with the password location information preset, and the attribute information meets the restriction conditions preset by the user, it is determined that the payment account will be charged, wherein the restriction conditions preset by the user are obtained based on the payment account identifier.

11. The method according to claim 9 or 10, wherein the first image is matched with the second image, comprising: The content of the first image matches the content of the second image, and the password position information triggered by the payment demander in the first image matches the password position information preset in the second image.

12. According to the method of claim 7, the password position information includes one or more of the following: pixel point information corresponding to the password position, sequence information of each password position being configured, or trajectory information moving from one password position to another password position.

13. The method according to claim 7, further comprising: Push payment information to the user who registered the payment account.

14. A payment processing device, applicable to a payee, comprising: an acquisition module, used to acquire the payment account identifier input by the payment demander through the user interaction interface of the terminal provided by the payee during the payment process of the payment demander, and to collect the first image with the cooperation of the payment demander and display it to the payment demander through the user interaction interface, so that the payment demander triggers the password position information on the first image; A sending module is used to send the payment account identifier and the first image carrying the password location information triggered by the payment demander to the payment service provider, so that the payment service provider can search for the second image bound to the payment account identifier and pre-set with the password location information, and determine whether to collect payment from the payment account corresponding to the payment account identifier based on the matching result between the first image carrying the password location information triggered by the payment demander and the second image pre-set with the password location information.

15. A payment processing device, applicable to a payment service provider, the device comprising: A receiving module, used for receiving a payment account identifier sent by a payee and a first image carrying password location information triggered by a payment demander, wherein the payment account identifier is input by the payment demander through a user interaction interface of a terminal provided by the payee, the first image is acquired by the payee with the cooperation of the payment demander, and the password location information carried in the first image is acquired by the payment demander after the payee displays the first image to the payment demander through the user interaction interface and the payment demander is triggered on the first image; A payment collection module is used to search for a second image with password location information pre-set and bound to the payment account identifier, and determine whether to collect payment from the payment account corresponding to the payment account identifier based on the matching result between the first image carrying the password location information triggered by the payment demander and the second image with password location information pre-set.

16. A payment terminal, comprising a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 6 is implemented.

17. A server, comprising a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, the method according to any one of claims 7 to 13 is implemented.

18. A payment processing system, comprising a payee and a payment service provider, The payee is used to obtain the payment account identifier input by the payment demander through the user interaction interface of the terminal provided by the payee during the payment process of the payment demander, and to collect a first image with the cooperation of the payment demander and display it to the payment demander through the user interaction interface, so that the payment demander triggers the password location information on the first image; and send the payment account identifier and the first image carrying the password location information triggered by the payment demander to the payment service provider; The payment service provider is used to search for a second image with password location information pre-set and bound to the payment account identifier, and determine whether to collect payment from the payment account corresponding to the payment account identifier based on the matching result between the first image carrying the password location information triggered by the payment demander and the second image with password location information pre-set.