CN116128494A - Service order payment method, system, electronic equipment and storage medium - Google Patents

Abstract

The application provides a business order payment method, system, electronic equipment and storage medium, which relate to the field of computer technology, including receiving a user's business order, the business order includes order information and geographic location information; The order information and the geographical location information are verified; according to the verification result of the business order, payment is made to the payee of the business order, the payment approval verification process is optimized, and the convenience of paying the business order is improved.

Description

A business order payment method, system, electronic device and storage medium

technical field

The present invention relates to the field of computer technology, in particular to a business order payment method, system, electronic equipment and storage medium.

Background technique

In the payment process of supplies procurement, medical reimbursement, travel reimbursement, etc., the traditional mode is mainly that the employee pays in advance, and the audit department reviews the reimbursement form and invoice, and then pays the fee to the employee. This model requires employees to advance business orders first, and then go through the company's payment process, which makes employees' experience not high; moreover, as to whether the payment has actually occurred, it can only be checked one by one by the approval department, which is error-prone and increases the review process. Human and time costs.

Therefore, a business order payment method, system, electronic device and storage medium are proposed.

Contents of the invention

This manual provides a business order payment method, system, electronic equipment, and storage medium. Through the order information and geographic location information of the business order, the business order is automatically pre-approved through the payment approval model, and then the business order is paid. Optimized The payment approval and verification process improves the approval speed and improves the user experience.

A business order payment method provided by this application adopts the following technical solutions, including:

Receive the user's business order, the business order includes order information and geographic location information;

Verifying the order information and the geographic location information through a payment approval model;

According to the verification result of the business order, payment is made to the payee of the business order.

Optionally, the verification of the order information and the geographic location information through the payment approval model includes:

judging whether the user's business order meets preset business conditions according to the order information;

It is judged according to the geographic location information whether the user's business order meets a preset scene condition.

Optionally, the judging whether the user's business order meets preset business conditions according to the order information includes:

According to the business category of the order information, the preset scenario type corresponding to the business order is determined.

Optionally, the judging whether the user's business order meets a preset scenario condition according to the geographic location information includes:

According to the geographic location information, determine a corresponding first scene type, and judge whether the first scene type matches the preset scene type.

Optionally, the judging whether the user's business order conforms to preset scene conditions according to the geographic location information further includes:

Acquiring the scene photo taken by the user, and judging whether the scene photo matches the geographic location information.

Optionally, the judging whether the user's business order meets preset business conditions according to the order information further includes:

determine whether the user is a default user;

determining the preset reimbursement amount of the user according to the payment item;

It is judged whether the business amount falls within the range of the preset reimbursement amount.

Optionally, also include:

After the business order payment is completed, the order payment information is obtained, and it is judged whether the actual payment amount is consistent with the business amount.

A business order payment system provided by this application adopts the following technical solutions, including:

A receiving module, configured to receive a business order from a user, where the business order includes order information and geographic location information;

A verification module, configured to verify the order information and the geographic location information through a payment approval model;

The payment module is configured to make payment to the payee of the business order according to the verification result of the business order.

Optionally, the verification module includes:

An order information verification sub-module, configured to judge whether the user's business order meets preset business conditions according to the order information;

The location information checking submodule is used to judge whether the user's business order meets the preset scene condition according to the geographic location information.

Optionally, the order information verifier module includes:

The type checking unit is configured to determine the preset scenario type corresponding to the business order according to the business category of the order information.

Optionally, the location information verification submodule includes:

The geographic location checking unit is configured to determine the corresponding first scene type according to the geographic location information, and judge whether the first scene type matches the preset scene type.

Optionally, the location information verification submodule further includes:

The geographic location verification auxiliary unit is configured to acquire the scene photo taken by the user, and determine whether the scene photo matches the geographic location information.

Optionally, the order information verifier module further includes:

a user verification unit, configured to determine whether the user is a preset user;

A quota determination unit, configured to determine the user's preset reimbursement quota according to the payment item;

An amount approval unit, configured to determine whether the business amount falls within the range of the preset reimbursement amount.

Optionally, also include:

The feedback module is used to obtain order payment information after the business order payment is completed, and determine whether the actual payment amount is consistent with the business amount.

This specification also provides an electronic device, wherein the electronic device includes:

Processor; and,

A memory storing computer-executable instructions which, when executed, cause the processor to perform any of the methods described above.

This specification also provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and when the one or more programs are executed by a processor, any one of the above-mentioned methods is implemented.

In this application, by receiving the user's business order, the business order includes order information and geographic location information; the order information and the geographic location information are verified through the payment approval model; according to the verification result of the business order , make payment to the payee of the business order, optimize the payment approval and verification process, and improve the convenience of paying business orders.

Description of drawings

FIG. 1 is a schematic diagram of the principle of a business order payment method provided by an embodiment of this specification;

Fig. 2 is a schematic flow diagram of a business order payment method provided by a specific embodiment of this specification;

FIG. 3 is a schematic structural diagram of a business order payment system provided by an embodiment of this specification;

FIG. 4 is a schematic structural diagram of an electronic device provided by an embodiment of this specification;

Fig. 5 is a schematic diagram of the principle of a computer-readable medium provided by the embodiment of this specification.

Detailed ways

The following description serves to disclose the present invention to enable those skilled in the art to carry out the present invention. The preferred embodiments described below are only examples, and those skilled in the art can devise other obvious variations. The basic principles of the present invention defined in the following description can be applied to other embodiments, variations, improvements, equivalents and other technical solutions without departing from the spirit and scope of the present invention.

Exemplary embodiments of the present invention will now be described more fully with reference to the accompanying drawings. However, example embodiments may be embodied in many forms, and this invention should not be construed as limited to the embodiments set forth herein. On the contrary, providing these exemplary embodiments can make the present invention more comprehensive and complete, and facilitate the full transfer of the inventive concept to those skilled in the art. The same reference numerals denote the same or similar elements, components or parts in the drawings, and thus their repeated descriptions will be omitted.

On the premise of conforming to the technical concept of the present invention, the features, structures, characteristics or other details described in a specific embodiment do not exclude that they can be combined in one or more other embodiments in a suitable manner.

In the description of the specific embodiments, the features, structures, characteristics or other details described in the present invention are intended to enable those skilled in the art to fully understand the embodiments. However, it does not exclude that those skilled in the art can practice the technical solutions of the present invention without one or more of the specific features, structures, characteristics or other details.

The flow charts shown in the drawings are only exemplary illustrations, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, and some operations/steps can be combined or partly combined, so the actual order of execution may be changed according to the actual situation.

The block diagrams shown in the drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices entity.

The term "and/or" or "and/or" includes all combinations of any one or more of the associated listed items.

Figure 1 is a schematic diagram of the principle of a business order payment method provided by the embodiment of this specification, the method includes:

S1 receives a user's business order, where the business order includes order information and geographic location information;

S2 Verifying the order information and the geographic location information through the payment approval model;

S3 pays the payee of the business order according to the verification result of the business order.

In the payment of business orders of enterprises, the traditional payment mode is mainly that the employees advance the business orders first, and then the employees submit the bills to the audit department (finance) for review, and the audit department (finance) pays the employees after passing the review. Expenses, because the audit department only reimburses according to the bills provided by employees, which is separated from the real business link, making it difficult to restore the business scenario, which increases the manpower and time costs of the audit.

Based on this, this application conducts automatic approval verification through the approval verification model through the business order sent by the user, and then outputs the payment identification information according to the verification result, so as to facilitate payment to the merchant (payee), and through the prior automatic approval verification Experience, while improving the user experience, improve the efficiency of approval and supervision. Specifically, as shown in Figure 2, this application includes:

S1 receives a user's business order, where the business order includes order information and geographic location information;

First, the enterprise will pre-allocate the payment authority of the user for the relevant user, and the payment authority includes the payment limit and the type of business that can be paid.

Secondly, the user needs to register before using the system; after completing the user's personal information and associating with the user's company, obtain/synchronize the user's payment limit and payable business category. You can apply for payment for business orders only after the affiliated company completes them. Among them, the "user" in this manual refers to the user who can apply for payment business orders. The "enterprise self-setting" mentioned below refers to the personalized setting of this system by the relevant responsible personnel of the enterprise according to the instructions of the management personnel in the enterprise.

Since the user's real-time geographic location is one of the processes of the system's approval and verification of business orders, this system is applied to mobile terminals with the function of collecting geographic location information in real time, and the mobile terminal can be a mobile phone or a tablet computer , so that users can carry it with them, so that they can apply for a payment service order in a certain business scenario.

The order information of the business order in this application is not the information generated after the business transaction is successful, but the order information related to the business entered by the user before payment to the merchant. Specifically, according to the user's application operation, jump to the new business order page, so that the user can input the order information of this business transaction. In an embodiment of the present specification, the user's application operation includes clicking a new button, and the new button is used to jump to a new business order page.

In order to improve the accuracy of the approval verification model, the order information includes order number, applicant, business category, payment item and business amount. Wherein, the order number is automatically generated, and as the unique identification code of each business order, it is related to the specific content of the business order; in one embodiment of this specification, the order number includes the user identification code, order creation time and serial number. The user identification code is an identification code automatically assigned to the user by the system or an identification code set by the enterprise itself, so as to distinguish different business orders.

The applicant is the user who creates a new business order by default. In one embodiment of this manual, the applicant column defaults to the user logged in to the current system, and the "applicant" column is set to be unchangeable to prevent corporate employees from impersonating other users. Paying for business orders under the name of the user will consume the payment limit of other users, resulting in a discrepancy between the actual order information and the order information recorded by the user, and then there will be traceability problems in the later stage.

The business category and the payment item are preset, wherein the payment item is a subcategory corresponding to each business category, and each business category corresponds to a business scenario. The subcategories of each business category include at least one payment item.

In an embodiment of this specification, the business category is medical services, the corresponding business scenario is a hospital, and the payment types include: registration fees, diagnosis fees, and the like.

The business amount is manually entered by the user, and the verification of the actual payment amount is post-verification.

In order to facilitate the restoration of real business scenarios and prevent users from forging business orders, real-time geographic location information of users can be obtained. In one embodiment of this specification, after the user fills in and submits the order information for this transaction, the real-time geographic location information of the user is collected. In one embodiment of the present specification, a scene analysis library is constructed, and business categories and business scenarios are one-to-one corresponded, so that the corresponding preset business scenarios can be determined through the business categories.

S2 Verifying the order information and the geographic location information through the payment approval model;

Since this system is pre-approval, the qualification of each business order needs to be approved. Specifically include:

S21 judging whether the user's business order meets preset business conditions according to the order information;

Each item in the order information should be reviewed in the instruction manual, specifically:

S211 checks whether the order number of the order information is unique;

Since the order number is associated with the business order one by one, if the order number is repeated, the association between the order number and the business order will be confused, and effective post-supervision cannot be implemented. Therefore, check whether the order number of the order information is unique, if yes, the approval result of the order number is passed, and if not, the approval result of the order number is not passed.

S212 judging whether the user is a preset user;

Considering that employees resign, take vacations, etc., they may not independently untie the association between users and enterprises, and users can still create new business orders through this system. However, after the employee leaves or is on vacation, most of the transactions they generate do not fall within the scope of the company's reimbursement. In order to avoid the company's financial loss, the system updates the employee's employment status in real time, and performs approval verification. When checking whether the applicant is a default user, that is to judge whether the user is a default user, if so, the user approval result is passed, if not, the user approval result is not passed. Wherein, the preset user is a user whose employment status is normal.

S213 judging whether the payment item selected by the user is the payable payment item of the user;

Since this business order is essentially within the scope of reimbursement by the enterprise, the enterprise needs to set up the payable payment items by itself in advance, and even set different payable payment items for each user. In order to improve the accuracy of approval, when performing approval verification, it is judged whether the payment item selected by the user is the user's payable payment item, if yes, the payment item approval result is not passed, if not, the payment item approval result is not passed, It was sent for manual approval because it fell outside the pre-set range of payable items.

S214 Determine whether the business amount falls within the preset reimbursement amount.

In order to effectively implement fee control, the enterprise sets the user's payment limit by itself. As a preference, the corresponding payment limit is determined according to different payable payment items. When performing approval verification, determine the user's preset reimbursement amount according to the payment item; determine whether the business amount falls within the range of the preset reimbursement amount. Wherein, the user's payment limit may be a monthly payment limit or an annual payment limit. The user's preset reimbursement amount is the payment limit corresponding to the current payment item. If the business amount is less than or equal to the preset reimbursement amount, that is, whether the business amount is within the preset reimbursement amount, the approval result of the business amount is approved; if the business amount is greater than the preset reimbursement amount, that is, the business amount is not within the preset reimbursement amount, Then the business amount approval result is not passed, and manual approval is required to facilitate accurate implementation of cost control.

S22 Judging whether the user's business order meets a preset scene condition according to the geographic location information.

In order to improve the accuracy of approval verification and ensure the security of corporate funds in employee reimbursement, etc., geographic location information can be obtained to predict whether users are "on-site".

Specifically, S221 determines the preset scene type corresponding to the business order according to the business category of the order information;

Since each business category in the scenario analysis database corresponds to a preset scenario type, the corresponding preset scenario type can be quickly determined according to the business category of the user's order information.

S222 Determine a corresponding first scene type according to the geographic location information, and judge whether the first scene type matches the preset scene type.

Specifically, the scene analysis database records several address categories, the address categories include valid transaction locations, and the effective transaction locations include: hospitals, shopping malls, supermarkets, etc.; associating address categories with business categories, each address category Corresponds to a business category, for example, the address category is "hospital" corresponding to "medical service" in the business category. The address category also includes an invalid transaction location, so as to quickly determine whether the geographic location information corresponds to a valid transaction location, and improve the speed of approval and verification.

In one embodiment of this specification, according to the geographic location information, the current transaction address where the user is located is determined, the keyword of the current transaction address is extracted, the address category is matched, the actual business category corresponding to the address category is determined, and the business category corresponding to the address category is determined. The first preset scenario corresponding to the actual service category. In another embodiment of this specification, the scene analysis database stores all current geographic location information, and the address category is determined for each address in advance and updated regularly. Then, according to the geographic location information, determine the address category corresponding to the geographic location information, and then determine the actual service category corresponding to the address category, and the first preset scene corresponding to the actual service category.

Determine whether the first scene type matches the preset scene type; if they match, the location approval result is passed; if they do not match, it means that the user's geographic location information may not correspond to the service category selected by the user, and the location approval result Fail.

In one embodiment of this specification, the time for obtaining the geographic location information may be obtained automatically when switching to the new business order page, or a receive button is set up on the new business order page to receive real-time geographic location information based on the user's selection. location information.

In order to strengthen the approval and verification of the user's real-time geographic location information, in one embodiment of this specification, when making payment to the payee of the business order, the geographic location information is automatically obtained once for future reference. In another embodiment of this specification, the scene photo taken by the user is acquired, and it is judged whether the scene photo matches the geographic location information. Provide a shooting function to enable users to upload at least one scene photo in real time. Specifically, the user may be required to take a photo at a fixed location, for example, the user is required to take a photo containing the name of the current transaction location, and the name of the current transaction location in the photo is identified by character recognition technology, and the scene photo and the geographic location information are judged. Does it match.

Of course, the user may also be required to take a photo of a prominent location of the current transaction location, such as the gate of the current transaction location, identify the prominent location of the current transaction location in the photo through image recognition technology, and determine the scene photo and the geographic location Whether the information matches. .

S3 pays the payee of the business order according to the verification result of the business order.

If one of the approval results in the above-mentioned approval verification process fails, the verification result of this business order will be failed, and the business order cannot be paid, and the specific reason for the failure will be fed back. If all the approval results in the above approval and verification process pass, the verification result of this business order is passed, and the business order can be paid.

In one embodiment of this specification, if the verification result of the business order described this time is passed, the approval verification result is stored and the payment QR code is generated, and the user can display the payment code and realize the payment by scanning the code. , the amount is directly transferred from the designated account of the enterprise, without the need for the user to advance payment using a personal account, which improves the user experience.

The check on whether the actual payment amount matches the business amount entered by the user is an after-the-fact check. If the relevant inspector finds that there is a problem with an order, the relevant user is required to give a reasonable reason. Generally speaking, the business amount input by the user is consistent with the actual payment amount of the business order. However, due to the user's clerical error or other reasons, the business amount entered by the user may be inconsistent with the actual payment amount of the business order. Therefore, after the payment of the business order is completed, the order payment information is obtained to determine the actual payment amount. Whether the stated business amount is consistent. If the manual review finds that the user is maliciously consuming, strict post-event remedial measures can be taken to avoid the inconsistency between the business amount and the actual payment amount of the business order.

Fig. 3 is a schematic structural diagram of a business order payment system provided by the embodiment of this specification, the system includes:

A receiving module 301, configured to receive a user's business order, where the business order includes order information and geographic location information;

A verification module 302, configured to verify the order information and the geographic location information through a payment approval model;

The payment module 303 is configured to make payment to the payee of the business order according to the verification result of the business order.

Optionally, the verification module 302 includes:

An order information verification sub-module, configured to judge whether the user's business order meets preset business conditions according to the order information;

The location information checking submodule is used to judge whether the user's business order meets the preset scene condition according to the geographic location information.

Optionally, the order information verifier module includes:

The type checking unit is configured to determine the preset scenario type corresponding to the business order according to the business category of the order information.

Optionally, the location information verification submodule includes:

The geographic location checking unit is configured to determine the corresponding first scene type according to the geographic location information, and judge whether the first scene type matches the preset scene type.

Optionally, the location information verification submodule further includes:

The geographic location verification auxiliary unit is configured to acquire the scene photo taken by the user, and determine whether the scene photo matches the geographic location information.

Optionally, the order information verifier module further includes:

a user verification unit, configured to determine whether the user is a preset user;

A quota determination unit, configured to determine the user's preset reimbursement quota according to the payment item;

An amount approval unit, configured to determine whether the business amount falls within the range of the preset reimbursement amount.

Optionally, also include:

The feedback module is used to obtain order payment information after the business order payment is completed, and determine whether the actual payment amount is consistent with the business amount.

The functions of the system in the embodiment of the present invention have been described in the above-mentioned method embodiments, so for details not described in this embodiment, refer to the relevant descriptions in the foregoing embodiments, and details are not repeated here.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

An electronic device embodiment of the present invention will be described below, and the electronic device can be regarded as a physical form implementation of the above-mentioned method and device embodiments of the present invention. The details described in the electronic device embodiments of the present invention should be regarded as supplements to the above method or device embodiments; details not disclosed in the electronic device embodiments of the present invention can be implemented by referring to the above method or device embodiments.

Fig. 4 is a structural block diagram of an exemplary embodiment of a federated login system device according to the present invention. The computer device shown in FIG. 5 is only an example, and should not limit the functions and scope of use of this embodiment of the present invention.

As shown in FIG. 4, the computer device 400 of this exemplary embodiment takes the form of a general-purpose data processing device. Components of the computer device 400 may include, but are not limited to: at least one processor 410, at least one memory 420, a network interface 430, a display unit 440, an input component 450, and the like.

Wherein, the memory 420 stores computer-readable programs, which may be codes of source programs or read-only programs. The program may be executed by the processor element 410, causing the processor 410 to perform steps of various embodiments of the present invention. For example, the processor 410 may execute the steps shown in FIG. 1 .

The memory 420 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) and/or a cache storage unit, and may further include a read-only storage unit (ROM). The memory 420 may also include programs/utilities having a set (at least one) of program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, examples of which are Each or some combination of these may include implementations of network environments.

It also includes a bus (not shown) that can represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or use a variety of bus structures. Local bus of any bus structure.

Computer device 400 may also communicate with one or more external devices (such as a keyboard, display, network device, Bluetooth device, etc.) communicate with one or more other data processing devices (eg, routers, modems, etc.). Such communication may occur through network interface 430, and may also occur through a network adapter with one or more networks, such as a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet. The network adapter can communicate with other modules of the computer device 400 through the bus. It should be appreciated that although not shown, other hardware and/or software modules may be used in the computer device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives And data backup storage system, etc.

Figure 5 is a schematic diagram of a computer readable medium embodiment of the present invention. As shown in Figure 5, the computer program may be stored on one or more computer readable media. The computer readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. When the computer program is executed by one or more data processing devices, the computer-readable medium can implement the above-mentioned method of the present invention, that is, by receiving a business order from a user, the business order includes order information and geographic location information ; Verifying the order information and the geographical location information through the payment approval model; making payment to the payee of the business order according to the verification result of the business order.

Through the above description of the implementation manners, those skilled in the art can easily understand that the exemplary embodiments described in the present invention can be implemented by software, or by combining software with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, and the software product can be stored in a computer-readable storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on a network , including several instructions to make a data processing device (which may be a personal computer, a server, or a network device, etc.) execute the above-mentioned method according to the present invention.

The computer readable storage medium may include a data signal carrying readable program code in baseband or as part of a carrier wave traveling as a data signal. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium other than a readable storage medium that can send, propagate or transport a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the readable storage medium may be transmitted by any suitable medium, including but not limited to wireless, cable, optical cable, RF, etc., or any suitable combination of the above.

Program code for carrying out the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural programming languages. Programming language - such as "C" or a similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (for example, using an Internet service provider). business to connect via the Internet).

In summary, the present invention can be realized by a method, system, electronic device or computer readable medium for executing a computer program. Some or all of the functions of the present invention can be realized in practice by using general data processing equipment such as a microprocessor or a digital signal processor (DSP).

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the present invention is not inherently related to any specific computer, virtual device or electronic device, and various general devices are also The present invention can be realized. The above descriptions are only specific embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (9)

1. A method of payment for a business order, comprising:

receiving a service order of a user, wherein the service order comprises order information and geographic position information;

checking the order information and the geographic position information through a payment approval model;

and according to the verification result of the service order, paying to a payee of the service order.

2. A business order payment method as recited in claim 1, wherein said verifying said order information and said geographic location information by a payment approval model comprises:

judging whether the service order of the user accords with a preset service condition according to the order information;

and judging whether the service order of the user accords with a preset scene condition according to the geographic position information.

3. A method for payment of a service order according to claim 2, wherein said determining whether the service order of the user meets a preset service condition according to the order information comprises:

determining a preset scene type corresponding to the service order according to the service type of the order information;

the determining whether the service order of the user meets the preset scene condition according to the geographic position information comprises the following steps:

and determining a first scene type corresponding to the geographic position information according to the geographic position information, and judging whether the first scene type is matched with the preset scene type.

4. A method for payment of a service order according to claim 3, wherein said determining whether said user's service order meets a preset scenario condition according to said geographic location information further comprises:

and acquiring a scene photo shot by the user, and judging whether the scene photo is matched with the geographic position information.

5. A business order payment method as recited in claim 3, wherein said determining whether said user's business order meets a preset business condition based on said order information further comprises:

judging whether the user is a preset user or not;

determining a preset reimbursement limit of the user according to the payment item;

and judging whether the business amount belongs to the range of the preset reimbursement limit.

6. A business order payment method as recited in claim 5, further comprising:

and after the business order payment is completed, acquiring order payment information, and judging whether the actual payment amount is consistent with the business amount.

7. A business order payment system, comprising:

the receiving module is used for receiving a service order of a user, wherein the service order comprises order information and geographic position information;

the verification module is used for verifying the order information and the geographic position information through a payment approval model;

and the payment module is used for paying to the payee of the business order according to the verification result of the business order.

8. An electronic device, wherein the electronic device comprises:

a processor; the method comprises the steps of,

a memory storing computer executable instructions that, when executed, cause the processor to perform the method of any of claims 1-6.

9. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-6.

Images