阅读说明：本技术 客户端收银方法、装置、设备及存储介质 (Client-side cash registering method, device, equipment and storage medium ) 是由 余鸿飞 于 2021-08-17 设计创作，主要内容包括：本申请涉及客户端技术领域,揭示了一种客户端收银方法、装置、设备及存储介质,其中方法包括：获取所述客户端发送的支付数据,根据所述支付数据获取校验数据；根据所述校验数据对所述支付数据进行校验,得到校验结果；当所述校验结果为通过时,根据所述支付数据生成支付请求,将所述支付请求发送给支付服务端；获取所述支付服务端根据所述支付请求发送的支付结果；根据所述支付结果生成支付提醒信息,根据所述支付提醒信息进行提醒。实现了采用接口向客户端提供支付服务,使支付交易和客户端的业务功能进行解耦合,客户端开发人员不需要撰写逻辑代码实现支付功能,减少了客户端开发人员的工作量,提高了支付功能的可维护性。(The application relates to the technical field of clients and discloses a client cash registering method, a client cash registering device and a client cash registering storage medium, wherein the method comprises the following steps: acquiring payment data sent by the client, and acquiring verification data according to the payment data; verifying the payment data according to the verification data to obtain a verification result; when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server; obtaining a payment result sent by the payment server according to the payment request; and generating payment reminding information according to the payment result, and reminding according to the payment reminding information. The payment service is provided for the client by adopting the interface, so that the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, the workload of the client developer is reduced, and the maintainability of the payment function is improved.)

1. A client cashier method, wherein the method is applied to a client, and the method comprises the following steps:

acquiring payment data sent by the client, and acquiring verification data according to the payment data;

verifying the payment data according to the verification data to obtain a verification result;

when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server;

obtaining a payment result sent by the payment server according to the payment request;

and generating payment reminding information according to the payment result, and reminding according to the payment reminding information.

2. The client-side cashier method according to claim 1, wherein the step of verifying the payment data according to the verification data to obtain a verification result comprises:

acquiring data from the check data as data to be judged;

searching the keywords of the data to be judged in the payment data to obtain a payment value to be judged;

acquiring a verification rule base, and acquiring a verification rule from the verification rule base according to the keyword of the data to be judged to obtain a target verification rule;

according to the value of the data to be judged and the target verification rule, verifying the payment value to be judged to obtain a single keyword verification result;

repeatedly executing the step of acquiring one datum from the check data as a datum to be judged until the extraction of the datum in the check data is completed;

when all the single keyword verification results pass, determining that the verification results pass;

and when any single keyword check result is failed, determining that the check result is failed.

3. The client cashier method according to claim 1, wherein the step of generating payment reminding information according to the payment result and reminding according to the payment reminding information comprises:

when the payment result is successful, generating payment success reminding information according to the payment result, performing page generation according to the payment success reminding information to obtain a payment success page, performing popup display on the payment success page, and sending the payment success reminding information to the client;

and when the payment result is failure, generating payment failure reminding information according to the payment result, generating a page according to the payment failure reminding information to obtain a payment failure page, performing popup window display on the payment failure page, and sending the payment failure reminding information to the client.

4. The client-side cashier method according to claim 1, wherein after the step of verifying the payment data according to the verification data to obtain a verification result, the method further comprises:

when the verification result is passed, generating a page resource acquisition request according to the verification result, sending the page resource acquisition request to a resource acquisition end, and acquiring a first page resource sent by the resource acquisition end according to the page resource acquisition request;

generating a page according to the first page resource to obtain a check-fail page, and performing popup display on the check-fail page, wherein the check-fail page comprises: the check does not pass the information and correction links.

5. The client-side cashier method according to claim 1, wherein the step of generating a payment request according to the payment data comprises:

calling the cashier desk calling page to acquire a fingerprint identification request sent by the client, and acquiring fingerprint data to be identified according to the fingerprint identification request;

and when the verification result is that the fingerprint data to be identified passes the verification, generating the payment request according to the payment data and the fingerprint data to be identified.

6. The client-side cashier method according to claim 1, wherein the step of generating a payment request according to the payment data comprises:

calling the cashier desk calling page to acquire a face recognition request sent by the client, and acquiring face data to be recognized according to the face recognition request;

and when the verification result is that the verification result is passed, generating the payment request according to the payment data and the face data to be identified.

7. The client cashier method according to claim 1, wherein the step of obtaining the payment data sent by the client is followed by further comprising:

and receiving the data of the buried point sent by the cash register calling page, and sending the data of the buried point to a data receiving end of the buried point.

8. A checkout counter apparatus, the apparatus being adapted for use at a client, the apparatus comprising:

the data acquisition unit is used for acquiring payment data sent by the client and acquiring verification data according to the payment data;

the verification result determining unit is used for verifying the payment data according to the verification data to obtain a verification result;

the payment processing unit is used for generating a payment request according to the payment data and sending the payment request to a payment server side when the verification result is that the payment request passes;

the payment result acquisition module is used for acquiring a payment result sent by the payment server according to the payment request;

and the reminding unit is used for generating payment reminding information according to the payment result and carrying out reminding according to the payment reminding information.

9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.

Technical Field

The present application relates to the field of client technologies, and in particular, to a client cashier method, device, equipment, and storage medium.

Background

With the development of internet technology, payment functions are widely applied. At present, a payment function is realized by writing a logic code when a client is developed, so that the payment function is highly coupled with the client, and the workload of a client developer is increased; and different versions of clients need to be developed in different application scenarios, and the maintainability of the payment function is poor due to the high coupling of the payment function and the clients.

Disclosure of Invention

The application mainly aims to provide a client cash registering method, a client cash registering device and a client cash registering storage medium, and aims to solve the technical problem that in the prior art, a payment function is realized by writing logic codes when a client is developed, so that the payment function is highly coupled with the client, the workload of a client developer is increased, and the maintainability of the payment function is poor.

In order to achieve the above object, the present application provides a client-side cashier method, where the method is applied to a client side, and the method includes:

acquiring payment data sent by the client, and acquiring verification data according to the payment data;

verifying the payment data according to the verification data to obtain a verification result;

when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server;

obtaining a payment result sent by the payment server according to the payment request;

and generating payment reminding information according to the payment result, and reminding according to the payment reminding information.

Further, the step of verifying the payment data according to the verification data to obtain a verification result includes:

acquiring data from the check data as data to be judged;

searching the keywords of the data to be judged in the payment data to obtain a payment value to be judged;

acquiring a verification rule base, and acquiring a verification rule from the verification rule base according to the keyword of the data to be judged to obtain a target verification rule;

according to the value of the data to be judged and the target verification rule, verifying the payment value to be judged to obtain a single keyword verification result;

repeatedly executing the step of acquiring one datum from the check data as a datum to be judged until the extraction of the datum in the check data is completed;

when all the single keyword verification results pass, determining that the verification results pass;

and when any single keyword check result is failed, determining that the check result is failed.

Further, the step of generating payment reminding information according to the payment result and reminding according to the payment reminding information includes:

when the payment result is successful, generating payment success reminding information according to the payment result, performing page generation according to the payment success reminding information to obtain a payment success page, performing popup display on the payment success page, and sending the payment success reminding information to the client;

and when the payment result is failure, generating payment failure reminding information according to the payment result, generating a page according to the payment failure reminding information to obtain a payment failure page, performing popup window display on the payment failure page, and sending the payment failure reminding information to the client.

Further, after the step of verifying the payment data according to the verification data to obtain a verification result, the method further includes:

when the verification result is passed, generating a page resource acquisition request according to the verification result, sending the page resource acquisition request to a resource acquisition end, and acquiring a first page resource sent by the resource acquisition end according to the page resource acquisition request;

generating a page according to the first page resource to obtain a check-fail page, and performing popup display on the check-fail page, wherein the check-fail page comprises: the check does not pass the information and correction links.

Further, the step of generating a payment request according to the payment data includes:

calling the cashier desk calling page to acquire a fingerprint identification request sent by the client, and acquiring fingerprint data to be identified according to the fingerprint identification request;

and when the verification result is that the fingerprint data to be identified passes the verification, generating the payment request according to the payment data and the fingerprint data to be identified.

Further, the step of generating a payment request according to the payment data includes:

calling the cashier desk calling page to acquire a face recognition request sent by the client, and acquiring face data to be recognized according to the face recognition request;

and when the verification result is that the verification result is passed, generating the payment request according to the payment data and the face data to be identified.

Further, after the step of obtaining the payment data sent by the client, the method further includes:

and receiving the data of the buried point sent by the cash register calling page, and sending the data of the buried point to a data receiving end of the buried point.

The application further provides a cash desk device, the device is applicable to the customer end, the device includes:

the data acquisition unit is used for acquiring payment data sent by the client and acquiring verification data according to the payment data;

the verification result determining unit is used for verifying the payment data according to the verification data to obtain a verification result;

the payment processing unit is used for generating a payment request according to the payment data and sending the payment request to a payment server side when the verification result is that the payment request passes;

the payment result acquisition module is used for acquiring a payment result sent by the payment server according to the payment request;

and the reminding unit is used for generating payment reminding information according to the payment result and carrying out reminding according to the payment reminding information.

The present application further proposes a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the steps of any of the above methods when executing the computer program.

The present application also proposes a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any of the above.

The method comprises the steps of obtaining payment data sent by a client, obtaining verification data according to the payment data, verifying the payment data according to the verification data to obtain a verification result, generating a payment request according to the payment data when the verification result is passed, sending the payment request to a payment server, obtaining the payment result sent by the payment server according to the payment request, generating payment reminding information according to the payment result, and reminding according to the payment reminding information, so that the payment service is provided to the client by adopting an interface, the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, and the workload of the client developer is reduced, the maintainability of the payment function is improved.

Drawings

Fig. 1 is a schematic flowchart of a client-side cashier method according to an embodiment of the application;

fig. 2 is a block diagram schematically illustrating a cash register station apparatus according to an embodiment of the present application;

fig. 3 is a block diagram illustrating a structure of a computer device according to an embodiment of the present application.

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Referring to fig. 1, an embodiment of the present application provides a client-side cashier method, where the method is applied to a client side, and the method includes:

s1: acquiring payment data sent by the client, and acquiring verification data according to the payment data;

s2: verifying the payment data according to the verification data to obtain a verification result;

s3: when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server;

s4: obtaining a payment result sent by the payment server according to the payment request;

s5: and generating payment reminding information according to the payment result, and reminding according to the payment reminding information.

The embodiment acquires the payment data sent by the client, acquires the verification data according to the payment data, verifies the payment data according to the verification data to obtain a verification result, generates a payment request according to the payment data when the verification result is passed, sends the payment request to the payment server, acquires the payment result sent by the payment server according to the payment request, generates payment reminding information according to the payment result, and reminds according to the payment reminding information, so that the payment service is provided to the client by adopting an interface, the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, the workload of a client developer is reduced, and the maintainability of the payment function is improved.

The client comprises: any one of a client of the mobile device, a browser of the mobile device, a client of the computer, and a browser of the computer.

The method and the device provide a service interface through a service interface module, and the service interface is used for providing payment service for the client.

And the client calls each service interface according to the calling specification of the service interface, and the payment transaction and the service function of the client are decoupled through the service interface.

The service interfaces include, but are not limited to: the system comprises a payment pre-verification interface, a transaction pre-ordering interface and a message pushing interface. The payment pre-verification interface is used for receiving a payment calling request sent by the client, and the transaction pre-ordering interface is used for receiving a transaction pre-ordering calling request sent by the client. And the payment pre-verification interface is used for acquiring the payment mode and the payment data input by the client. And the transaction ordering pre-ordering interface is used for receiving ordering pre-ordering data sent by the client. And the message pushing interface is used for pushing messages to the client.

And the cashier desk page rendering module acquires a plug-in calling request sent by the client according to the service interface, and generates a page according to the plug-in calling request to obtain a cashier desk calling page.

The service interface acquires a plug-in calling request sent by the client, when the service interface is an interface needing to generate a page, the plug-in calling request is sent to a cashier desk page rendering module, the cashier desk page rendering module generates a page according to parameters carried by the plug-in calling request, and the generated page is used as a cashier desk calling page. And when the service interface is not the interface needing to generate the page, the cashier page rendering module does not need to generate the page.

The plug-in call request comprises: payment calling request and transaction ordering calling request. The payment calling request is used for calling a payment request of the program realized by the application. The transaction order calling request is used for calling a program realized by the application to carry out a transaction order calling request. The transaction ordering refers to direct transaction when information is filled in advance before transaction, and the transaction is considered to be possible.

And providing a password payment SDK through a payment password management module, wherein the password payment SDK is used for generating a page by the cashier desk page rendering module.

The cryptographic payment SDK includes, but is not limited to: the password verification system comprises one or more of a mixed password component SDK, a 6-digit password component SDK, a safety keyboard component SDK, a fingerprint verification component SDK and a face verification component SDK. SDK, is a software package.

When the service interface is an interface needing to generate a page, the cashier desk page rendering module acquires page resources according to parameters carried by the plug-in calling request, and when the page resources are recorded with the identification of the password payment SDK, the cashier desk page rendering module acquires the password payment SDK from the payment password management module according to the identification of the password payment SDK recorded in the page resources to generate the page.

For S1, the payment data sent by the client through the service interface and/or the payment data sent through the cash register desk call page is obtained.

The payment data includes, but is not limited to: order identification, account identification, payment amount, payment account and payee account. The payment account includes: a bank card number. The payment account includes: a bank card number.

The verification data includes: a key and a value. The verification data and the verification rule together verify the payment data. And the verification rule is data which is dynamically configured by the payment server according to requirements and needs to be verified in advance. For example, the check rule includes: whether the payment amount is larger than the single limit of the bank corresponding to the bank card number is not specifically limited in this example.

It is understood that the verification rules may also be written in a program file implementing the present application.

And S2, comparing the payment data with the verification data, and determining that the verification result is passed when the comparison result meets the requirements of the verification rule, otherwise, determining that the verification result is not passed.

For S3, when the verification result is pass, it means that the comparison result of the comparison between the payment data and the verification data meets the requirement of the verification rule, at this time, a payment request is generated according to the payment data, and then the payment request is sent to the payment server according to the communication connection with the payment server.

For S4, the payment server performs payment service according to the payment request, generates a response value according to the payment result of the payment service and the payment request after completing the payment service, and sends the response value to the payment pre-verification module according to the communication connection with the program for realizing the application; and the payment pre-verification module analyzes the response value to obtain the payment result corresponding to the payment request.

For S5, generating payment reminding information according to the payment result through a payment completion management module, generating a page and popping up a window according to the payment reminding information, and sending the payment reminding information to the client, thereby realizing the reminding of the client and the feedback of the client according to the payment reminding information.

It is understood that steps S1 to S5 may be implemented in any form of plug-in, component, or device, and then integrated in the client.

Wherein, steps S1 to S4 may be packaged as a payment pre-verification module, and step S5 may be packaged as a payment completion management module.

The service interface module, the payment password management module, the payment pre-verification module and the payment completion management module are modules obtained based on JavaSpring; the cashier desk page rendering module is obtained based on React and Webpack. Therefore, a service interface module, the payment password management module, the payment pre-verification module and the payment completion management module are obtained based on JavaSpring, the cashier desk page rendering module is obtained based on React and Webpack, and front and back ends are separated; the stability of client cash collection is ensured through JavaSpring; interface optimization and front-end code management are facilitated by using React and Webpack as front-end frameworks.

That is to say, the program implementing the present application adopts JavaSpring as a back end framework, and React and Webpack as front end frameworks.

JavaSpring is the mainstream JavaWeb development framework, which is a lightweight application framework and has high cohesion and attraction. Java Web, is a technology stack that uses Java technology to address the relevant Web (global wide area network) internet domain.

React, is a JavaScript library used for building a user interface. JavaScript (JS), is a lightweight, interpreted, or just-in-time programming language with function precedence.

Webpack is a front-end resource modular management and packaging tool.

Optionally, the step of obtaining a module based on fact and Webpack includes: acquiring a program to be packaged, wherein the program to be packaged is a program developed by adopting the React; and packaging the program to be packaged by adopting the Webpack to obtain the cashier desk page rendering module.

In an embodiment, the step of verifying the payment data according to the verification data to obtain a verification result includes:

s211: acquiring data from the check data as data to be judged;

s212: searching the keywords of the data to be judged in the payment data to obtain a payment value to be judged;

s213: acquiring a verification rule base, and acquiring a verification rule from the verification rule base according to the keyword of the data to be judged to obtain a target verification rule;

s214: according to the value of the data to be judged and the target verification rule, verifying the payment value to be judged to obtain a single keyword verification result;

s215: repeatedly executing the step of acquiring one datum from the check data as a datum to be judged until the extraction of the datum in the check data is completed;

s216: when all the single keyword verification results pass, determining that the verification results pass;

s217: and when any single keyword check result is failed, determining that the check result is failed.

According to the embodiment, the payment data is verified according to the verification data, so that the payment data is verified in advance, the service pressure of the payment server is reduced, and the service stability of the payment server is improved.

And for S211, sequentially acquiring data corresponding to a keyword from the check data, and taking the acquired data as data to be judged. The data to be judged comprises: a key and a value.

For step S212, the keyword of the data to be determined is searched in the payment data, and a value corresponding to the keyword searched in the payment data is used as the payment value to be determined.

For S213, the check rule base may be obtained from the local storage space, or may be obtained from the payment server.

The checking rule base comprises the following steps: keywords and verification rules.

And searching the keyword corresponding to the data to be judged in the verification rule base, and taking the verification rule corresponding to the keyword searched in the verification rule base as the target verification rule.

For step S214, the payment value to be determined is checked according to the value of the data to be determined and the target check rule, that is, the payment value to be determined and the value of the data to be determined are compared, when the comparison result meets the target check rule, the single keyword check result is determined to be passed, and when the comparison result does not meet the target check rule, the single keyword check result is determined to be not passed.

For example, the keyword corresponding to the data to be determined is a single limit of bank a, the value of the data to be determined is 1000 yuan, the payment value to be determined is 2000 yuan, the target verification rule is that a single payment amount is less than or equal to the single limit, and the payment value to be determined is verified according to the value of the data to be determined and the target verification rule, where 2000 yuan is greater than 1000 yuan, and the comparison result is that the single payment amount is greater than the single limit, and the comparison result does not conform to the target verification rule, so that the single keyword verification result is determined to be failed, which is not specifically limited in this example.

For S215, steps S411 to S415 are repeatedly performed until the extraction of the data in the verification data is completed.

For S216, when all the single keyword verification results are passed, it means that all comparison results of the comparison between the payment data and the verification data meet the requirement of the verification rule, and it is determined that the verification result is passed.

For S217, when any single keyword verification result is not passed, it means that a comparison result of comparing the payment data with the verification data partially or completely fails to meet a requirement of a verification rule, and it is determined that the verification result is not passed.

In an embodiment, the step of generating payment reminding information according to the payment result and reminding according to the payment reminding information includes:

s51: when the payment result is successful, generating payment success reminding information according to the payment result, performing page generation according to the payment success reminding information to obtain a payment success page, performing popup display on the payment success page, and sending the payment success reminding information to the client;

s52: and when the payment result is failure, generating payment failure reminding information according to the payment result, generating a page according to the payment failure reminding information to obtain a payment failure page, performing popup window display on the payment failure page, and sending the payment failure reminding information to the client.

According to the embodiment, the payment reminding information is generated according to the payment result, and the page is generated and pops up according to the payment reminding information, so that the information synchronization with the client and the client is completed.

For S51, when the payment result is successful, it means that the payment has been successfully completed, so a payment success reminding message is generated according to the payment result; acquiring page resources according to the payment success reminding information, generating pages according to the acquired page resources, taking the generated pages as the payment success pages, and performing popup display on the payment success pages, thereby realizing successful reminding of customers according to the payment reminding information; and sending the payment success reminding information to the client, thereby realizing the feedback of the client according to the payment reminding information.

For S52, when the payment result is failure, it means that the payment is not successfully completed, so a payment failure reminding message is generated according to the payment result; acquiring page resources according to the payment failure reminding information, generating pages according to the acquired page resources, taking the generated pages as the payment failure pages, and displaying the payment failure pages in a popup mode, so that failure reminding is performed on a client according to the payment reminding information; and sending the payment failure reminding information to the client, thereby realizing the feedback of the client according to the payment reminding information.

In an embodiment, after the step of verifying the payment data according to the verification data to obtain a verification result, the method further includes:

s221: when the verification result is passed, generating a page resource acquisition request according to the verification result, sending the page resource acquisition request to a resource acquisition end, and acquiring a first page resource sent by the resource acquisition end according to the page resource acquisition request;

s222: generating a page according to the first page resource to obtain a check-fail page, and performing popup display on the check-fail page, wherein the check-fail page comprises: the check does not pass the information and correction links.

The embodiment realizes popup display when the check result is failed and provides correction link, thereby being beneficial to fast correction of customers and improving customer experience.

For S221, when the verification result is failed, the comparison result of the comparison between the payment data and the verification data does not completely meet the requirement of the verification rule, and a page resource acquisition request is generated by adopting a preset resource acquisition rule and the verification result; and sending the page resource acquisition request to a resource acquisition end, and taking the page resource sent by the resource acquisition end according to the page resource acquisition request as the first page resource.

Page resources, i.e. the resource files needed to load a page.

For step S222, a page is generated according to the first page resource, the generated page is used as the verification failing page, and the verification failing page is displayed in a popup manner, so that a verification result and a correction link are fed back to a client.

And the correction link is a link address determined according to the check data corresponding to the check result. And the customer can modify the data and send the payment data again without clicking the correction link on the page during the verification.

In an embodiment, the step of generating a payment request according to the payment data includes:

s231: calling the cashier desk calling page to acquire a fingerprint identification request sent by the client, and acquiring fingerprint data to be identified according to the fingerprint identification request;

s232: and when the verification result is that the fingerprint data to be identified passes the verification, generating the payment request according to the payment data and the fingerprint data to be identified.

According to the embodiment, the payment request is generated according to the payment data and the fingerprint data to be identified, so that the input mode of the payment password is enriched, and the customer experience is improved.

For step S231, the cashier desk calling page acquires the fingerprint identification request sent by the client through the cashier desk calling page, and sends the fingerprint identification request to the fingerprint identification module; and performing fingerprint acquisition popup according to the fingerprint identification request, acquiring fingerprint data input by a user in the fingerprint acquisition popup, and taking the acquired data as the fingerprint data to be identified.

For S232, when the verification result is pass, it means that all comparison results of the comparison between the payment data and the verification data meet requirements of a verification rule, and at this time, the payment request is generated according to the payment data and the fingerprint data to be identified. It is understood that, at this time, the payment data may or may not include the payment password.

The payment server side acquires a fingerprint database, matches the fingerprint data to be identified in the fingerprint database, determines that the payment result is successful when the matching is successful, and determines that the payment result is failed when the matching is failed.

In an embodiment, the step of generating a payment request according to the payment data includes:

s241: calling the cashier desk calling page to acquire a face recognition request sent by the client, and acquiring face data to be recognized according to the face recognition request;

s242: and when the verification result is that the verification result is passed, generating the payment request according to the payment data and the face data to be identified.

According to the embodiment, the payment request is generated according to the payment data and the face data to be recognized, so that the input mode of the payment password is enriched, and the customer experience is improved.

For step S441, the checkout counter calling page obtains a face identification request sent by the client through the checkout counter calling page, and sends the face identification request to the face identification module; and acquiring a face acquisition popup according to the face identification request, acquiring face data input by a user in the face acquisition popup, and taking the acquired data as face data to be identified.

For S442, when the verification result is that the verification result passes, it means that all comparison results of the comparison between the payment data and the verification data meet requirements of a verification rule, and at this time, the payment request is generated according to the payment data and the face data to be recognized. It is understood that, at this time, the payment data may or may not include the payment password.

The payment server side obtains a face image database, matches the face image data to be recognized in the face image database, determines that the payment result is successful when matching is successful, and determines that the payment result is failed when matching is failed.

In an embodiment, after the step of generating a page according to the plug-in calling request to obtain a cash register calling page, the method further includes:

s21: and receiving the data of the buried point sent by the cash register calling page, and sending the data of the buried point to a data receiving end of the buried point.

According to the embodiment, the collection of the buried point data sent by the cash register calling page through the buried point module is realized, so that a basis is provided for payment statistical analysis according to the buried point data.

And the buried point data receiving end carries out conversion rate statistical analysis according to each buried point data and each payment result to obtain a target conversion rate.

The buried point data includes, but is not limited to: page burial point data and page element burial point data. The page buried point data comprises: client identification, page expansion time. The page element buried point data comprises: client identification, page element identification, and page element click time. The client identification may be a client ID, a client name, or the like, which uniquely identifies a client. The page identification may be a page ID, a page name, or the like, which uniquely identifies a page. The page element identification may be a page element ID, a page element name, or the like, which uniquely identifies a page element. The page element is a page element of an HTML page.

Referring to fig. 2, the apparatus of the present application is applied to a client 200, and includes:

a data obtaining unit 110, configured to obtain payment data sent by the client 200, and obtain verification data according to the payment data;

a verification result determining unit 120, configured to verify the payment data according to the verification data to obtain a verification result;

the payment processing unit 130 is configured to generate a payment request according to the payment data and send the payment request to the payment server 300 when the verification result is that the payment request passes;

a payment result obtaining module 140, configured to obtain a payment result sent by the payment server 300 according to the payment request;

and the reminding unit 150 is configured to generate payment reminding information according to the payment result, and carry out reminding according to the payment reminding information.

According to the embodiment, the payment data sent by the client is obtained, the verification data is obtained according to the payment data, the payment data is verified according to the verification data to obtain the verification result, when the verification result is passed, the payment request is generated according to the payment data, the payment request is sent to the payment server, the payment server is obtained, the payment reminding information is generated according to the payment result, and the payment reminding information is reminded, so that the payment service is provided for the client by adopting an interface, the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, the workload of a client developer is reduced, and the maintainability of the payment function is improved.

Referring to fig. 3, a computer device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer equipment is used for storing data such as a client cash register method and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a client-side cashier method. The client-side cash registering method is suitable for a client side and comprises the following steps: acquiring payment data sent by the client, and acquiring verification data according to the payment data; verifying the payment data according to the verification data to obtain a verification result; when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server; obtaining a payment result sent by the payment server according to the payment request; and generating payment reminding information according to the payment result, and reminding according to the payment reminding information.

The embodiment acquires the payment data sent by the client, acquires the verification data according to the payment data, verifies the payment data according to the verification data to obtain a verification result, generates a payment request according to the payment data when the verification result is passed, sends the payment request to the payment server, acquires the payment result sent by the payment server according to the payment request, generates payment reminding information according to the payment result, and reminds according to the payment reminding information, so that the payment service is provided to the client by adopting an interface, the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, the workload of a client developer is reduced, and the maintainability of the payment function is improved.

An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing a client-side cashier method, the method being applicable to a client side, the method including: acquiring payment data sent by the client, and acquiring verification data according to the payment data; verifying the payment data according to the verification data to obtain a verification result; when the verification result is that the payment request passes the verification result, generating a payment request according to the payment data, and sending the payment request to a payment server; obtaining a payment result sent by the payment server according to the payment request; and generating payment reminding information according to the payment result, and reminding according to the payment reminding information.

The client cashier method comprises the steps of obtaining payment data sent by the client, obtaining verification data according to the payment data, verifying the payment data according to the verification data to obtain a verification result, and when the verification result is passed, generating a payment request according to the payment data, sending the payment request to a payment server, acquiring a payment result sent by the payment server according to the payment request, generating payment reminding information according to the payment result, reminding according to the payment reminding information, therefore, the payment service is provided for the client by adopting the interface, the payment transaction is decoupled from the service function of the client, a client developer does not need to write a logic code to realize the payment function, the workload of the client developer is reduced, and the maintainability of the payment function is improved.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.

The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.