WO2025180482A1 - 订单支付处理 - Google Patents

订单支付处理

Info

Publication number
WO2025180482A1
WO2025180482A1 PCT/CN2025/079794 CN2025079794W WO2025180482A1 WO 2025180482 A1 WO2025180482 A1 WO 2025180482A1 CN 2025079794 W CN2025079794 W CN 2025079794W WO 2025180482 A1 WO2025180482 A1 WO 2025180482A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
location
institutional
order
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/079794
Other languages
English (en)
French (fr)
Inventor
舒杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Publication of WO2025180482A1 publication Critical patent/WO2025180482A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224—Transactions dependent on location of M-devices
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments

Definitions

  • This document relates to the field of data processing technology, and in particular to a method and device for order payment processing.
  • One or more embodiments of the present specification provide an order payment processing method, including: obtaining a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperation in identification collection, and reading an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; performing location detection according to a location detection link based on the payment information carried by the payment instruction, and using the object location information of the target location object obtained by the location detection as payment positioning information; performing location matching processing on the payment positioning information and the access locations in the access location set, determining a payment account according to the account type corresponding to the matching processing result, and performing order payment based on the payment account.
  • an order payment processing device including: an instruction acquisition module, configured to acquire a payment instruction for an order to be paid, which is submitted by an institutional user and a merchant after cooperation in identification collection, and read an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; a location detection module, configured to perform location detection according to a location detection link based on the payment information carried by the payment instruction, and use the object location information of the target location object obtained by the location detection as payment positioning information; an order payment module, configured to perform location matching processing on the payment positioning information and the access location in the access location set, determine a payment account according to the account type corresponding to the matching processing result, and perform order payment based on the payment account.
  • an instruction acquisition module configured to acquire a payment instruction for an order to be paid, which is submitted by an institutional user and a merchant after cooperation in identification collection, and read an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs
  • a location detection module configured to perform location detection according to a location detection link based on the
  • One or more embodiments of the present specification provide an order payment processing device, comprising: a processor; a memory configured to store computer-executable instructions, the processor executing the computer-executable instructions to achieve: obtaining a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperating to collect identifications, and reading an access location set configured in an institutional payment access policy of the institution to which the institutional user belongs; performing location detection according to a location detection link based on payment information carried by the payment instruction, and using the object location information of the target location object obtained by the location detection as payment positioning information; performing location matching processing on the payment positioning information and the access locations in the access location set, determining a payment account according to the account type corresponding to the matching processing result, and performing order payment based on the payment account.
  • One or more embodiments of the present specification provide a computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: obtaining a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperating to collect identification, and reading an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; performing location detection according to a location detection link based on the payment information carried by the payment instruction, and using the object location information of the target location object obtained by the location detection as payment positioning information; performing location matching processing on the payment positioning information and the access locations in the access location set, determining a payment account according to the account type corresponding to the matching processing result, and making order payment based on the payment account.
  • FIG1 is a schematic diagram of an implementation environment of an order payment processing method provided by one or more embodiments of this specification.
  • FIG2 is a flowchart of an order payment processing method provided by one or more embodiments of this specification.
  • FIG3 is a flowchart of an order payment processing method applied to an institutional payment scenario provided by one or more embodiments of this specification.
  • FIG4 is a processing flow chart of an order payment processing method applied to an identification payment scenario provided by one or more embodiments of this specification.
  • FIG5 is a schematic diagram of an embodiment of an order payment processing device provided by one or more embodiments of this specification.
  • FIG6 is a schematic diagram of the structure of an order payment processing device provided by one or more embodiments of this specification.
  • the order payment processing method can be applied to the implementation environment of order payment processing.
  • the implementation environment includes a server 101 for processing order payment for an order to be paid based on the payment instructions of the order to be paid submitted after the institutional user and the merchant cooperate to collect identifications, a user terminal 102 of the institutional user who cooperates in collecting identifications, and a merchant device 103 of the merchant.
  • the server 101 may be one or more servers, a server cluster consisting of several servers, or a cloud server of a cloud computing platform, and is used to process payment for orders submitted by the user terminal 102 and the merchant device 103 for identification collection.
  • the user terminal 102 can be a smart phone, tablet computer, e-book reader, wearable device, device for information interaction based on AR (Augmented Reality)/VR (Virtual Reality), etc., and can also be installed with an application or browser.
  • the user cooperates with the merchant device 103 through the application or browser to collect identification, and can also cooperate with the merchant device 103 to collect identification through the mechanism subroutine in the application.
  • the merchant device 103 can be a POS (point of sale) machine equipped with an identification collection component, or a material display component equipped with identification materials with the merchant's payment collection identification.
  • POS point of sale
  • the implementation environment may also include an institution terminal 104 for configuring the institution's payment access policy.
  • the server 101 reads the access location set configured in the institutional payment access policy of the institution to which the institutional user belongs, performs location detection according to the location detection link based on the payment information carried in the payment instruction, and uses the object location information of the target location object obtained by the location detection as the payment positioning information, performs location matching processing based on the payment positioning information and the access location in the access location set, determines the payment account based on the account type corresponding to the matching processing result, and makes order payment based on the payment account.
  • One or more embodiments of an order payment processing method provided in this specification are as follows.
  • This embodiment provides an order payment processing method.
  • position detection is performed according to the position detection link, and the object position information of the target position object obtained by the position detection is used as the payment positioning information.
  • the payment positioning information and the access position configured in the institutional payment access policy of the institution to which the institutional user belongs are position matched, the payment account is determined according to the account type corresponding to the matching processing result, and the order payment is made based on the payment account.
  • accurate payment positioning information is determined, and position matching processing is performed based on the accurate payment positioning information and the access position to ensure the effectiveness of the position matching processing, thereby improving the accuracy of the determined payment account.
  • the order payment processing method provided in this embodiment specifically includes steps S202 to S206 .
  • Step S202 obtaining a payment instruction for an order to be paid submitted by an institutional user after cooperating with a merchant to collect identifications, and reading an access position set configured in an institutional payment access policy of the institution to which the institutional user belongs.
  • the institutional users described in this embodiment include members of the institution.
  • Institutional users can apply for payment of expenses incurred based on the institutional account.
  • the institution can configure an institutional payment access strategy.
  • the payment processing of the order to be paid will be carried out based on the institutional account;
  • the institutional payment access strategy includes a set of access conditions configured by the institution on whether payment can be made based on the institutional account.
  • an institution can configure payment to be made only within certain locations. For example, if an institution member's business trip is designated as taking place in province P1, then the access locations include province P1. More specifically, if an institution member's business trip is designated as taking place in District T1, City X1, province P1, and District T2, City X1, province P1, then the access locations include District T1, City X1, province P1, and District T2, City X1, province P1. In this embodiment, the locations pre-configured by the institution for making payments are access locations.
  • the institutional user and the merchant cooperate to collect identifiers, then generate and submit a payment instruction for the order to be paid to the server.
  • the payment instruction is generated after the merchant device collects the institutional user's application payment identifier displayed by the payment application, or after the merchant device collects the institutional user's sub-program payment identifier displayed by the institutional sub-program configured in the payment application.
  • the payment instruction for the order to be paid is submitted after the merchant device collects the institutional user's application payment identifier displayed by the payment application, or after the merchant device collects the institutional user's sub-program payment identifier displayed by the institutional sub-program in the institutional application.
  • the institution subroutine in this embodiment can be an institution code subroutine. Users can view the payment identifier through the institution subroutine. Users who have successfully registered with the institution subroutine are institution users, and the subroutine payment identifier displayed through the institution subroutine is a payment identifier associated with the user identifier and carries an institution identifier tag.
  • the institution subroutine can be a subroutine installed in a payment application.
  • users can also display the application payment identifier through the payment application.
  • the user's application payment identifier is the payment identifier associated with the user identifier.
  • the user's application payment identifier and the subroutine payment identifier can simply differ in that the application payment identifier does not carry the institution identifier tag, while the subroutine payment identifier carries the institution identifier tag.
  • the subroutine payment identifier and application payment identifier in this embodiment can be a payment code in the form of a QR code, a bar code, or a sound code.
  • the payment instruction can also be generated by collecting the merchant's collection ID through the user terminal. Specifically, it can be the payment instruction for the order to be paid submitted after obtaining the merchant's collection ID collected by the user terminal.
  • the merchant's collection ID is collected by the user terminal or the merchant's device collects the payment ID based on the payment application of the user terminal to display the application payment ID and submit the payment instruction for the order to be paid.
  • the merchant's device collects the payment ID based on the payment application of the user terminal to display the application payment ID and submit the payment instruction for the order to be paid.
  • the organization can configure different access location sets for different scenarios; for example, if the location of the organization member's business trip is specified in P1 province and P2 province, the configured access locations under the accommodation scenario include P1 province and P2 province; if the specific business trip and office location of the organization member is specified in P1 City X1 City T1 District and P1 province X1 City T2 District, the configured access locations under the dining scenario include P1 province X1 City T1 District and P1 province X1 City T2 District.
  • the location for institutional payment pre-configured by the organization is the access location.
  • the following operations are performed: determine the order scenario of the order to be paid, and query the target access scenario that matches the order scenario in the institutional payment access policy; read the access location set under the target access scenario in the institutional payment access policy.
  • the admission position set matching the order scenario of the order to be paid is read in the institutional payment admission policy of the institution to which the institutional user belongs.
  • Step S204 Based on the payment information carried in the payment instruction, position detection is performed according to the position detection link, and the object position information of the target position object obtained by the position detection is used as payment positioning information.
  • the position detection link includes a link for performing position detection to obtain a target position object for position determination; optionally, the position detection link can be a link composed of one or more position objects having a sequential relationship; the position object in this embodiment can be an object capable of position determination, such as a merchant whose position does not generally change, a payment application that can collect terminal position, and an institution subroutine.
  • the position detection link can be a link composed of a merchant, an institution subroutine, and a payment application, a link composed of an institution subroutine and a payment application, a link composed of a merchant and a payment application, or a link composed of a payment application.
  • the payment location information includes the current location information of the institutional user.
  • a location detection link can be pre-configured. After reading the access location set configured in the institution's payment access policy, location detection is performed according to the location detection link to obtain the target location object, and the object location information of the target location object is used as payment positioning information.
  • the following operations are performed: reading the merchant identifier carried by the payment instruction, and querying whether the merchant carries a merchant authorization mark based on the merchant identifier; if so, determining that the merchant is the target position object, and reading the merchant position information associated with the merchant identifier as the payment positioning information; if not, based on the user identifier carried by the payment instruction, reading the terminal position information collected and stored when the institution user accesses the institution subprogram in the position information storage area of the institution subprogram; verifying whether the terminal position information is valid position information based on the collection time of the terminal position information and the acquisition time of the payment instruction; if so, determining the institution subprogram as the target position object, and using the terminal position information as the payment positioning information; if not, determining the payment application as the
  • the location detection link is composed of the merchant in the first place, the institutional subroutine in the second place, and the payment application in the third place; in the process of performing location detection according to the location detection link based on the payment information carried by the payment instruction, and using the object location information of the target location object obtained by the location detection as the payment positioning information, first query whether the merchant is an authorized merchant of the payment application based on the merchant identifier carried by the payment instruction. If so, the merchant is determined to be the target location object, and the merchant location information associated with the merchant identifier entered by the merchant during the merchant authorization process is used as the payment positioning information of the institutional user.
  • the merchant is not an authorized merchant of the payment application, that is, the merchant does not carry a merchant authorization mark, in order to avoid directly reading the institutional user's location information from the user terminal to affect the institutional user's payment perception, based on the user identifier carried by the payment instruction, the terminal location information collected and stored by the location collection component when the institutional user accesses the institutional subroutine is read in the location information storage area of the institutional subroutine.
  • the terminal location information cannot accurately represent the current location of the institutional user. Therefore, after reading the terminal location information, verify whether the time difference between the collection time of the terminal location information and the acquisition time of the payment instruction is less than the time threshold. If so, the institutional subroutine is determined as the target location object, and the terminal location information associated with the user identifier carried by the payment instruction read in the location storage area of the institutional subroutine is used as the payment location information.
  • the terminal location information read cannot be used as valid location information.
  • the payment application is identified as the target location object.
  • the location collection component configured on the institutional user's user terminal is called to collect the terminal location information, and the collected terminal location information is determined as the payment positioning information. It should be noted that terminal location information is, to a certain extent, private to the user. Therefore, calling the location collection component to collect terminal location information requires authorization from the institutional user.
  • the location collection component configured on the institutional user's user terminal is called based on this location authorization mark to collect the terminal location information. If the institutional user has not a location authorization mark for the payment application, a location authorization reminder is sent to the institutional user. After obtaining the location authorization instruction submitted by the institutional user, the institutional user is marked for location authorization, and the location collection component configured on the user terminal is called based on this location authorization mark to collect the terminal location information.
  • the merchant's object location information is obtained based on the merchant identification; when the organization subroutine is the target location object, the organization subroutine's object location information is obtained by reading from the organization subroutine's location information storage area based on the user identification; when the payment application is the target location object, the payment application's object location information is collected through the location component configured in the user terminal.
  • the above specifically describes the location detection process and the process of determining the payment positioning information of the location detection link including merchants, agency subroutines and payment applications.
  • location detection is performed according to the location detection link, and the object location information of the target location object obtained by the location detection is used as the payment positioning information.
  • the process can also be achieved in the following way: based on the identification mark category carried in the payment instruction, the location detection link for location detection is determined; location detection is performed according to the location detection link to obtain the target location object, and the object location information corresponding to the target location object is used as the payment positioning information.
  • the identification tag category refers to the category used to characterize the payment identifier displayed by the user terminal and collected by the merchant device. If the payment instruction is generated by the merchant device after collecting the application payment identifier of the institutional user based on the institutional user's application displayed by the payment application, the identification tag category is the identification tag category of the application payment identifier. If the payment instruction is generated by the merchant device after collecting the sub-program payment identifier of the institutional user based on the institutional sub-program configured by the payment application, the identification tag category is the identification tag category of the sub-program payment identifier. In addition, if the payment instruction is generated by the user terminal after collecting the merchant's collection identifier, the identification tag category may be the identification tag category of the collection identifier.
  • the application detection link is determined to be the location detection link; if the payment instruction carries the identification tag category of the subroutine payment identifier, the subroutine detection link is determined to be the location detection link; if the payment instruction carries the identification tag category of the collection identifier, the merchant detection link is determined to be the location detection link.
  • the application detection link consists of the payment application; the subroutine detection link consists of the institution subroutine and the payment application; and the merchant detection link consists of the merchant, the institution subroutine, and the payment application.
  • the application detection link is determined as the location detection link, in an optional implementation manner provided by this embodiment, in the process of performing location detection according to the location detection link, obtaining the target location object, and using the object location information corresponding to the target location object as the payment location information, the payment application is first determined as the target location object based on the application identifier of the payment application contained in the application detection link; and then, based on the location authorization mark of the institutional user for the payment application, the location collection component configured in the user terminal of the institutional user is called to collect the payment location information.
  • the application detection link can also be composed of merchants and payment applications.
  • the process of determining the payment location information it is first queried whether the merchant carries a merchant authorization mark based on the merchant identifier carried by the payment instruction. If so, the merchant is determined to be the target location object, and the merchant location information associated with the merchant identifier is read as the payment location information; if not, the payment application is determined as the target location object based on the application identifier of the payment application contained in the application detection link, and the location collection component configured on the user terminal of the institutional user is called to collect the payment location information.
  • the subroutine detection link is determined as a location detection link
  • the following operations are performed: reading the terminal location information stored in the location information storage channel of the institution subroutine in the subroutine detection link; verifying whether the collection time of the terminal location information meets the detection conditions; if so, taking the institution subroutine as the target location object, and using the terminal location information as the payment positioning information; if not, taking the payment application in the subroutine detection link as the target location object, and based on the location authorization mark of the institution user for the payment application, calling the location collection component of the user terminal to collect the payment positioning information.
  • the terminal location information is acquired by calling a location acquisition component of the user terminal when the institution user accesses the institution subprogram.
  • verifying whether the collection time of the terminal location information meets the detection conditions is to verify whether the terminal location information is valid location information.
  • the subroutine detection link can also be consistent with the merchant detection link, that is, first, based on the merchant identifier carried by the payment instruction, it is queried whether the merchant carries a merchant authorization mark. If so, the merchant is determined to be a target location object, and the merchant location information associated with the merchant identifier is read as the payment positioning information; if not, the terminal location information stored in the location information storage channel of the institution subroutine in the subroutine detection link is read; verify whether the collection time of the terminal location information meets the detection conditions; if so, the institution subroutine is used as the target location object, and the terminal location information is used as the payment positioning information; if not, the payment application in the subroutine detection link is used as the target location object, and based on the location authorization mark of the institution user for the payment application, the location collection component of the user terminal is called to collect the payment positioning information.
  • the application detection link is determined to be the location detection link based on the identification tag category of the application payment identifier; otherwise, the merchant detection link is determined to be the location detection link.
  • Step S206 performing location matching processing on the payment location information and the access location in the access location set, determining the payment account according to the account type corresponding to the matching processing result, and performing order payment based on the payment account.
  • the above-mentioned payment location information that can effectively and accurately represent the location information of the institutional user is obtained.
  • the payment location information and the access location in the access location set are position matched. If the matching result is a successful match, the institutional account of the institution is read according to the corresponding institutional account type, and the order payment is made based on the institutional account; if the matching result is a failed match, the user account of the institutional user is read according to the corresponding user account type, and the order payment is made based on the user account.
  • the institution can configure the institutional payment method of the institution and the merchant in the institutional payment access strategy, such as making payment based on the resource balance in the institutional account, making payment based on the resource balance in the institutional account and the rights and interests issued by the merchant, and making payment based on the number of times agreed in advance between the institution and the merchant.
  • the institution can first query the institutional payment method agreed upon by the institution and the merchant based on the account identifier of the institutional account and/or the merchant identifier of the merchant; and then make order payment for the order to be paid based on the institutional payment method.
  • the access position in the institutional payment access strategy in this embodiment can be represented based on the address code, such as a six-digit address code, in which the first and second digits represent the provincial level, the third and fourth digits represent the prefecture level, and the fifth and sixth digits represent the county level.
  • the address code such as a six-digit address code, in which the first and second digits represent the provincial level, the third and fourth digits represent the prefecture level, and the fifth and sixth digits represent the county level.
  • order payment processing method in addition to location matching processing, can also perform access detection based on other conditions configured in the institutional payment access policy, such as access detection in the time dimension, access detection in the merchant dimension, and access detection in the order resource amount dimension. If the access detection in each dimension is passed, order payment is made based on the institutional account.
  • the order payment processing method after obtaining the payment instruction for the order to be paid submitted by the institutional user and the merchant after the identification collection, first reads the access location set configured in the institutional payment access policy of the institution mentioned by the institutional user, and then based on the payment information carried by the payment instruction, according to the pre-configured location detection link, first inquires whether the merchant carries the merchant authorization mark based on the merchant identification carried by the payment instruction. If so, determines that the merchant is the target location object, and reads the merchant location information associated with the merchant identification as the payment positioning information.
  • the payment positioning information (the last time it was collected and stored) collected and stored by the institutional user when accessing the institutional subroutine in the location information storage area of the institutional subroutine, and verifies whether the terminal location information is Valid location information, if yes, the institution subroutine is determined as the target location object, and the terminal location information read is used as the payment positioning information, if not, the payment application is determined as the target location object, and the location collection component configured in the user terminal is called to collect the terminal location information and the collected terminal location information is determined as the payment positioning information, thereby improving the accuracy of the determined payment positioning information, so that the payment positioning information can accurately and effectively reflect the real location of the institution user, after obtaining the payment positioning information, the payment positioning information and the access location in the access location set are position matched, if the match is successful, the payment order is paid based on the institution's institutional account, thereby improving the effectiveness of the institution's payment, avoiding the loss of institutional resources, and at the same time,
  • the following further illustrates the order payment processing method provided in this embodiment by taking the application of an order payment processing method provided in this embodiment in an institutional payment scenario as an example.
  • the order payment processing method applied to the institutional payment scenario specifically includes the following steps.
  • Step S302 obtaining the payment instruction for the order to be paid submitted by the institutional user after the institutional user cooperates with the merchant to collect the identification, and reading the access position set configured in the institutional payment access policy of the institution to which the institutional user belongs.
  • Step S304 based on the merchant identifier carried in the payment instruction, query whether the merchant carries a merchant authorization mark; if so, read the merchant location information associated with the merchant identifier as payment positioning information and execute steps S314 to S314; if not, execute step S306.
  • Step S306 Based on the user identifier carried in the payment instruction, the terminal location information collected and stored when the institution user accesses the institution subprogram is read in the location information storage area of the institution subprogram.
  • Step S308 based on the time of collecting the terminal location information and the time of obtaining the payment instruction, verify whether the terminal location information is valid location information; if so, set the terminal location information as payment positioning information and execute steps S314 to S314; if not, execute steps S310 to S314.
  • Step S310 based on the location authorization mark of the institution user for the payment application, calling the location collection component configured on the user terminal of the institution user to collect the terminal location information, and determining the terminal location information as the payment positioning information.
  • Step S312 performing location matching processing on the payment location information and the admission location in the admission location set.
  • the access location set contains the payment location information. If so, it is determined that the match is successful; if not, it is determined that the match fails.
  • Step S314 If the match is successful, the payment order is processed according to the institution's institutional account.
  • the following takes the application of an order payment processing method provided by this embodiment in an identification payment scenario as an example, and further explains the order payment processing method provided by this embodiment. See Figure 4.
  • the order payment processing method applied to the identification payment scenario specifically includes the following steps.
  • Step S402 obtaining the payment instruction for the order to be paid submitted by the institutional user after the institutional user cooperates with the merchant to collect the identification, and reading the access position set configured in the institutional payment access policy of the institution to which the institutional user belongs.
  • Step S404 Read the identification mark type carried in the payment instruction.
  • Step S406 read the position detection link according to the identification mark category, and perform position detection according to the position detection link to obtain the target position object.
  • Step S408 Using the object location information of the target location object as payment positioning information.
  • Step S410 performing location matching processing on the payment location information and the admission location in the admission location set.
  • Step S412 Determine the payment account according to the account type corresponding to the matching processing result, and make order payment based on the payment account.
  • One or more embodiments of an order payment processing device provided in this specification are as follows.
  • FIG. 5 shows a schematic diagram of an embodiment of an order payment processing device provided by this embodiment.
  • the description is relatively simple.
  • the device embodiment described below is only illustrative.
  • This embodiment provides an order payment processing device, including: an instruction acquisition module 502, configured to obtain a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperation in identification collection, and read the access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; a position detection module 504, configured to perform position detection according to a position detection link based on the payment information carried by the payment instruction, and use the object position information of the target position object obtained by the position detection as payment positioning information; an order payment module 506, configured to perform position matching processing on the payment positioning information and the access location in the access location set, determine the payment account according to the account type corresponding to the matching processing result, and perform order payment based on the payment account.
  • an instruction acquisition module 502 configured to obtain a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperation in identification collection, and read the access location set configured in the institutional payment access policy of the institution to which the institutional user belongs
  • a position detection module 504 configured to perform position detection according to a position detection link
  • One or more embodiments of an order payment processing device provided in this specification are as follows.
  • FIG. 6 is a structural schematic diagram of an order payment processing device provided by one or more embodiments of this specification.
  • the order payment processing device may vary significantly depending on configuration or performance, and may include one or more processors 601 and memory 602.
  • Memory 602 may store one or more applications or data. Memory 602 may be either ephemeral or persistent.
  • the applications stored in memory 602 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for the order payment processing device.
  • processor 601 may be configured to communicate with memory 602 to execute the series of computer-executable instructions in memory 602 on the order payment processing device.
  • the order payment processing device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input/output interfaces 605, one or more keyboards 606, and the like.
  • an order payment processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the order payment processing device, and is configured to be executed by one or more processors.
  • the one or more programs include the following computer-executable instructions: obtaining a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperating to collect identification, and reading an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; performing location detection according to a location detection link based on the payment information carried in the payment instruction, and using the object location information of the target location object obtained by the location detection as payment positioning information; performing location matching processing on the payment positioning information and the access location in the access location set, determining a payment account according to the account type corresponding to the matching processing result, and performing order payment based on the payment account.
  • One or more embodiments of a computer-readable storage medium provided in this specification are as follows.
  • one or more embodiments of this specification also provide a computer-readable storage medium.
  • the computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which implement the following process when executed: obtaining a payment instruction for an order to be paid submitted by an institutional user and a merchant after cooperating to collect identifications, and reading an access location set configured in the institutional payment access policy of the institution to which the institutional user belongs; performing location detection according to a location detection link based on the payment information carried by the payment instruction, and using the object location information of the target location object obtained by the location detection as payment positioning information; performing location matching processing on the payment positioning information and the access locations in the access location set, determining a payment account according to the account type corresponding to the matching processing result, and making order payment based on the payment account.
  • the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other.
  • Each embodiment focuses on the differences from other embodiments.
  • the device embodiment, equipment embodiment and readable storage medium embodiment are similar to the method embodiment, so the description is relatively simple.
  • relevant content in the device embodiment, equipment embodiment and readable storage medium embodiment please refer to the partial description of the method embodiment.
  • a programmable logic device (such as a field programmable gate array (FPGA)) is an integrated circuit whose logical function is determined by user programming of the device.
  • HDL Hardware Description Language
  • HDL Very-High-Speed Integrated Circuit Hardware Description Language
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HDCal Joint C12
  • JHDL Java Hardware Description Language
  • Lava Lava
  • Lola MyHDL
  • PALASM RHDL
  • Verilog Verilog
  • the controller can be implemented in any suitable manner.
  • the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller.
  • computer-readable program code e.g., software or firmware
  • ASIC application-specific integrated circuit
  • controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320.
  • the memory controller can also be implemented as part of the control logic of the memory.
  • the controller in addition to implementing the controller in pure computer-readable program code, can also be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing the various functions included therein can also be considered as structures within the hardware component. Alternatively, the means for implementing the various functions can be considered both a software module implementing the method and a structure within the hardware component.
  • the systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or physical devices, or by software having certain functions.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
  • one or more embodiments of this specification may be provided as methods, systems, or computer program software.
  • one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects.
  • this specification may take the form of a computer program software implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information.
  • the information can be computer-readable instructions, data structures, program modules or other data.
  • Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media such as modulated data signals and carrier waves.
  • One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules.
  • program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network.
  • program modules may be located in local and remote computer storage media, including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Cash Registers Or Receiving Machines (AREA)

Abstract

本说明书实施例提供了订单支付处理方法及装置。其中，一种订单支付处理方法包括：在根据机构用户与商户配合进行标识采集后提交的待支付订单的支付指令进行订单支付的过程中，首先基于支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息，将支付定位信息和机构用户所属机构的机构支付准入策略中配置的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于支付账户进行订单支付。

Description

订单支付处理 技术领域
本文件涉及数据处理技术领域，尤其涉及订单支付处理的方法及装置。
背景技术
随着计算机以及互联网的发展，越来越多的用户通过线上支付的方式对商品或者服务进行支付，在线上支付越来越普及的情况下机构的机构成员在由于机构的原因进行支付的过程中，也会通过线上支付的方式对产生的待支付订单进行支付，但对由于机构的原因进行支付的费用通常不是由机构成员来承担的，而是由机构承担的，如何提升机构成员在由于机构的原因进行支付的感知程度是机构和机构成员关注的重点。
发明内容
本说明书一个或多个实施例提供了一种订单支付处理方法，包括：获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
本说明书一个或多个实施例提供了一种订单支付处理装置，包括：指令获取模块，被配置为获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；位置检测模块，被配置为基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；订单支付模块，被配置为将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
本说明书一个或多个实施例提供了一种订单支付处理设备，包括：处理器；被配置为存储计算机可执行指令的存储器，所述处理器执行所述计算机可执行指令以实现：获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
本说明书一个或多个实施例提供了一种计算机可读存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的一种订单支付处理方法实施环境的示意图。
图2为本说明书一个或多个实施例提供的一种订单支付处理方法处理流程图。
图3为本说明书一个或多个实施例提供的一种应用于机构支付场景的订单支付处理方法处理流程图。
图4为本说明书一个或多个实施例提供的一种应用于标识支付场景的订单支付处理方法处理流程图。
图5为本说明书一个或多个实施例提供的一种订单支付处理装置实施例的示意图。
图6为本说明书一个或多个实施例提供的一种订单支付处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书一个或多个实施例提供的订单支付处理方法，可适用于订单支付处理这一实施环境，如图1所示，该实施环境包括用于根据机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令对待支付订单进行订单支付处理的服务器101，配合进行标识采集的机构用户的用户终端102和商户的商户设备103。
其中，服务器101可以是一台或者多台服务器，若干台服务器组成的服务器集群，或者是云计算平台的云服务器，用于对用户终端102和商户设备103配合进行标识采集提交的待支付订单进行订单支付。
用户终端102，可以是智能手机、平板电脑、电子书阅读器、可穿戴设备、基于AR(Augmented Reality，增强现实)/VR(Virtual Reality，虚拟现实)进行信息交互的设备等，还可安装有应用程序或者浏览器，用户通过应用程序或者浏览器与商户设备103配合进行标识采集，还可通过应用程序中的机构子程序与商户设备103配合进行标识采集。
商户设备103可以是配置由标识采集组件的POS(point of sale，销售终端)机，或者是配置有商户的收款标识的标识物料的物料展示组件。
此外，该实施环境还可包含有机构终端104，用于进行机构支付准入策略的配置。
该实施环境中，服务器101在获取到用户终端102和商户设备103配合进行标识采集后提交的对待支付订单的支付指令后，读取机构用户所属机构的机构支付准入策略中配置的准入位置集合，基于支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息，根据支付定位信息和准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于支付账户进行订单支付。
本说明书提供的一种订单支付处理方法的一个或者多个实施例如下。
本实施例提供的一种订单支付处理方法，在根据机构用户与商户进行标识采集后提交的对待支付订单的支付指令进行订单支付的过程中，首先基于支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息，将支付定位信息和机构用户所属机构的机构支付准入策略中配置的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于支付账户进行订单支付，以此，确定准确的支付定位信息，基于准确的支付定位信息和准入位置进行位置匹配处理，保证位置匹配处理的有效性，进而提升确定的支付账户的准确性。
参照图2，本实施例提供的订单支付处理方法，具体包括步骤S202至步骤S206。
步骤S202，获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合。
本实施例所述机构用户，包括机构中的成员。
实际应用中，机构用户因为机构的原因出差，进行各种各样的消费的费用由机构承担，不是由机构用户自己承担，但无法让每个机构用户都管理机构账户，机构用户可申请基于机构账户进行产生的费用的支付，为了保证机构用户基于机构账户进行支付的有效性，避免机构用户将用户自己的消费作为机构的消费利用机构账户进行支付导致机构资源的损失，机构可配置机构支付准入策略，在待支付订单满足机构支付准入策略的情况下，再基于机构账户进行待支付订单的支付处理；所述机构支付准入策略，包括机构配置的是否能基于机构账户进行支付的准入条件的集合。
机构在配置机构支付准入策略的过程中，可配置仅在某些位置区域内，可以进行机构支付，例如，机构成员出差的位置指定在p1省，则准入位置包括p1省，更具体的，机构成员出差的位置指定在p1省x1市t1区和p1省x1市t2区，则准入位置包括p1省x1市t1区和p1省x1市t2区。本实施例中，机构预先配置的进行机构支付的位置为准入位置。
具体实施时，机构用户与商户配合进行标识采集后生成对待支付订单的支付指令并向服务器提交，可选的，所述支付指令，在商户设备采集所述机构用户基于支付应用展示的所述机构用户的应用付款标识后生成，或者，在商户设备采集所述机构用户基于支付应用配置的机构子程序展示所述用户的子程序付款标识后生成。也即是，获取商户设备采集机构用户基于支付应用展示的所述机构用户的应用付款标识后提交的对待支付订单的支付指令，或者获取商户设备采集机构用户基于机构应用中机构子程序展示的子程序付款标识后提交的对待支付订单的支付指令。
需要说明的是，本实施例中的机构子程序，可以是机构码子程序，用户可通过机构子程序查看付款标识，在机构子程序注册成功的用户为机构用户，且通过机构子程序展示的子程序付款标识，为与用户标识关联的，携带有机构标识标签的付款标识；机构子程序可以是搭载于支付应用的子程序。此外，用户还可通过支付应用进行应用付款标识的展示，用户的应用付款标识，为与用户标识关联的付款标识。可选的，用户的应用付款标识和子程序付款标识可以仅仅是应用付款标记未携带机构标识标签，子程序付款标识携带机构标识标签的区别。
本实施例中的子程序付款标识和应用付款标识，可以是二维码、条形码或者声音码等形式的付款码。
除了上述商户设备采集机构用户的付款标识进行支付指令的生成之外，还可通过用户终端采集商户的收款标识进行支付指令的生成，具体的，可以是获取用户终端采集商户的收款标识后提交的对待支付订单的支付指令。
在具体执行过程中，还存在通过用户终端采集商户的收款标识或者商户设备采集基于用户终端的支付应用进行应用付款标识的展示进行针对待支付订单的支付指令的提交，都无法知道用户是否为机构用户的情况，针对于此，在获取到用户与商户配合进行标识采集后提交的对待支付订单的支付指令后，可根据支付指令中携带的用户标识查询用户是否为机构用户，若是，确定机构用户所属机构，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；若否，基于用户标识关联的用户账户对待支付订单进行支付处理。
本实施例中，机构可针对不同的场景，配置不同的准入位置集合；例如，机构成员出差的位置指定在p1省和P2省，则配置的住宿场景下的准入位置包括p1省和p2省；机构成员具体的出差办公的位置指定在p1省x1市t1区和p1省x1市t2区，则配置的餐饮场景下的准入位置包括p1省x1市t1区和p1省x1市t2区。本实施例中，机构预先配置的进行机构支付的位置为准入位置。基于此，本实施例提供的一种可选实施方式中，在读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合的过程中，执行如下操作：确定所述待支付订单的订单场景，并在所述机构支付准入策略中查询与所述订单场景匹配的目标准入场景；在所述机构支付准入策略中读取所述目标准入场景下的准入位置集合。
具体的，读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合的过程中，在所述机构用户所属机构的机构支付准入策略中读取与所属待支付订单的订单场景匹配的准入位置集合。
步骤S204，基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息。
所述位置检测链路，包括进行位置检测以获得进行位置确定的目标位置对象的链路；可选的，所述位置检测链路可以是一个由具有顺序关系的一个或者多个位置对象组成的链路；本实施例中的位置对象，可以是能进行位置确定的对象，例如，位置在一般情况下不会发生变化的商户、可以进行终端位置采集的支付应用和机构子程序。位置检测链路可以是由商户、机构子程序和支付应用组成的链路，也可以是由机构子程序和支付应用组成的链路，还可以是由商户和支付应用组成的链路，还可以是由支付应用组成的链路。
所述支付定位信息，包括机构用户当前的定位信息。
本实施例中，可预先配置一个位置检测链路，在读取到机构的机构支付准入策略中配置的准入位置集合后，按照该位置检测链路进行位置检测，获得目标位置对象，并将目标位置对象的对象位置信息作为支付定位信息。
本实施例提供的一种可选实施方式中，在基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息的过程中，执行如下操作：读取所述支付指令携带的商户标识，并基于所述商户标识查询所述商户是否携带商户授权标记；若是，确定所述商户为目标位置对象，读取所述商户标识关联的商户位置信息作为所述支付定位信息；若否，基于所述支付指令携带的用户标识，在机构子程序的位置信息存储区域读取所述机构用户访问所述机构子程序时采集并存储的终端位置信息；根据所述终端位置信息的采集时间和所述支付指令的获取时间，核验所述终端位置信息是否为有效位置信息；若是，将所述机构子程序确定为目标位置对象，并将所述终端位置信息作为所述支付定位信息；若否，将支付应用确定为目标位置对象，根据所述机构用户对支付应用的位置授权标记，调用所述机构用户的用户终端配置的位置采集组件采集终端位置信息；将采集的终端位置信息确定为所述支付定位信息。
具体的，位置检测链路由第一位次的商户、第二位次的机构子程序和第三位次的支付应用构成；在基于支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息的过程中，首先根据支付指令携带的商户标识查询所述商户是否为支付应用的授权商户，若是，则确定商户为目标位置对象，并将商户在进行商户授权的过程中录入的与商户标识关联的商户位置信息作为机构用户的支付定位信息。
若商户不是支付应用的授权商户，也即是商户未携带商户授权标记，为了避免直接从用户终端读取机构用户的定位信息影响机构用户的支付感知，基于支付指令携带的用户标识，在机构子程序的位置信息存储区域读取机构用户访问机构子程序时调用位置采集组件采集并存储的终端位置信息，为了避免读取到的终端位置信息与支付指令的获取时间的时间差距较长，终端位置信息不能准确的表征机构用户当前所处的位置，因此，在读取到终端位置信息后，核验终端位置信息的采集时间与支付指令的获取时间的时间差值是否小于时间阈值，若是，将机构子程序确定为目标位置对象，并将在机构子程序的位置此那次存储区域读取到的与支付指令携带的用户标识关联的终端位置信息作为支付定位信息。
进一步，若终端位置信息的采集时间与支付指令的获取时间的时间差值大于或者等于时间阈值，则说明读取到的终端位置信息不能作为有效位置信息，为了获得更加准确的机构用户的位置信息，将支付应用确定为目标位置对象，在将支付应用确定为目标位置对象之后，调用机构用户的用户终端配置的位置采集组件采集终端位置信息，并将采集的终端位置信息确定为支付定位信息。需要说明的是，终端位置信息在一定程序上属于用户的隐私，因此，调用位置采集组件采集终端位置信息，需要得到机构用户的授权，若存在机构用户对支付应用的位置授权标记，则根据该位置授权标记，调用机构用户的用户终端配置的位置采集组件采集终端位置信息，若未存在机构用户对支付应用的位置授权标记，则向机构用户发送位置授权提醒，在获取到机构用户提交的位置授权指令后对机构用户进行位置授权标记，并根据该位置授权标记调用用户终端配置的位置采集组件采集终端位置信息。
可选的，在商户为目标位置对象的情况下，商户的对象位置信息基于商户标识读取获得；在机构子程序为目标位置对象的情况下，机构子程序的对象位置信息基于用户标识从机构子程序的位置信息存储区域读取获得，在支付应用为目标位置对象的情况下，支付应用的对象位置信息通过用户终端配置的位置组件采集。
上述对包含商户、机构子程序和支付应用这三者的位置检测链路的位置检测过程和确定支付定位信息的过程进行了具体说明，此外，为了提升位置检测效率，避免所有的支付指令都通过上述位置检测链路进行位置检测造成资源浪费，本实施例中，在基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息的过程，还可通过如下方式实现：基于所述支付指令中携带的标识标记类别，确定进行位置检测的位置检测链路；按照所述位置检测链路进行位置检测，获得目标位置对象，并将所述目标位置对象对应的对象位置信息作为支付定位信息。
具体的，首先根据支付指令中携带的标识标记类别，确定进行位置检测的位置检测链路，然后按照确定的位置检测链路进行位置检测，获得目标位置对象，并将目标位置对象的对象位置信息作为支付定位信息。
可选的，所述标识标记类别，是指用来表征商户设备采集的用户终端展示的付款标识的类别。若支付指令是在商户设备采集机构用户基于支付应用展示的机构用户的应用付款标识后生成的，则标识标记类别为应用付款标识的标识标记类别，若支付指令是商户设备采集机构用户基于支付应用配置的机构子程序展示的机构用户的子程序付款标识后生成的，则标识标记类别为子程序付款标识的标识标记类别；此外，若支付指令是用户终端采集商户的收款标识后生成的，则标识标记类别可以是收款标识的标识标记类别。
可选的，若支付指令中携带应用付款标识的标识标记类别，则基于所述应用付款标识的标识标记类别，将应用检测链路确定为位置检测链路；若支付指令中携带子程序付款标识的标识标记类别，将子程序检测链路确定为位置检测链路；若支付指令中携带收款标识的标识标记类别，将商户检测链路确定为位置检测链路。其中，应用检测链路由支付应用组成；子程序检测链路由机构子程序和支付应用组成，商户检测链路由商户、机构子程序和支付应用组成。
在将应用检测链路确定为位置检测链路后，本实施例提供的一种可选实施方式中，在按照位置检测链路进行位置检测，获得目标位置对象，并将目标位置对象对应的对象位置信息作为支付定位信息的过程中，首先根据所述应用检测链路中包含的所述支付应用的应用标识，将所述支付应用确定为所述目标位置对象；然后根据所述机构用户对所述支付应用的位置授权标记，调用所述机构用户的用户终端配置的位置采集组件采集所述支付定位信息。
此外，应用检测链路还可由商户和支付应用组成，可选的，在确定支付定位信息的过程中，首先基于支付指令携带的商户标识查询商户是否携带商户授权标记，若是，确定商户为目标位置对象，读取商户标识关联的商户位置信息作为支付定位信息；若否，根据所述应用检测链路中包含的所述支付应用的应用标识，将支付应用确定为目标位置对象，并调用机构用户的用户终端配置的位置采集组件采集支付定位信息。
在将子程序检测链路确定为位置检测链路后，本实施例提供的一种可选实施方式中，在按照位置检测链路进行位置检测，获得目标位置对象，并将目标位置对象对应的对象位置信息作为支付定位信息的过程中，执行如下操作：读取在所述子程序检测链路中的机构子程序的位置信息存储渠道存储的终端位置信息；核验所述终端位置信息的采集时间是否符合检测条件；若是，将所述机构子程序作为目标位置对象，并将所述终端位置信息作为所述支付定位信息；若否，将所述子程序检测链路中所述支付应用作为所述目标位置对象，并基于所述机构用户对所述支付应用的位置授权标记，调用所述用户终端的位置采集组件采集支付定位信息。
可选的，所述终端位置信息在所述机构用户访问所述机构子程序时调用用户终端的位置采集组件采集获得。
其中，核验终端位置信息的采集时间是否符合检测条件，也即是核验终端位置信息是否为有效位置信息。
此外，子程序检测链路还可与商户检测链路一致，也即是，首先基于支付指令携带的商户标识查询商户是否携带商户授权标记，若是，确定商户为目标位置对象，读取商户标识关联的商户位置信息作为支付定位信息；若否，读取在所述子程序检测链路中的机构子程序的位置信息存储渠道存储的终端位置信息；核验所述终端位置信息的采集时间是否符合检测条件；若是，将所述机构子程序作为目标位置对象，并将所述终端位置信息作为所述支付定位信息；若否，将所述子程序检测链路中所述支付应用作为所述目标位置对象，并基于所述机构用户对所述支付应用的位置授权标记，调用所述用户终端的位置采集组件采集支付定位信息。
也即是，若支付指令中携带应用付款标识的标识标记类别，则基于所述应用付款标识的标识标记类别，将应用检测链路确定为位置检测链路；否则，将商户检测链路确定为位置检测链路。
步骤S206，将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
上述获得了能够有效且准确的表征机构用户的定位信息的支付定位信息，本步骤中，将支付定位信息和准入位置集合中准入位置进行位置匹配处理，若匹配处理结果为匹配成功，根据对应的机构账户类型读取所述机构的机构账户，并基于所述机构账户进行订单支付；若匹配处理结果为匹配失败，根据对应的用户账户类型读取所述机构用户的用户账户，并基于所述用户账户进行订单支付。
本实施例中，机构可机构支付准入策略中配置机构与商户的机构支付方式，例如基于机构账户中的资源余额进行支付，基于机构账户中的资源余额和商户发放的权益进行支付，基于机构与商户预先约定的次数进行支付，在具体基于机构账户进行订单支付的过程中，可首先根据所述机构账户的账户标识和/或所述商户的商户标识，查询所述机构与所述商户约定的机构支付方式；再基于所述机构支付方式对所述待支付订单进行订单支付。
例如，机构向商户预先向商户支付了10次的费用，该机构用户基于机构账户进行订单支付时，扣除1次预先支付的费用即可。
需要说明的是，本实施例中的机构支付准入策略中的准入位置，可基于地址编码表示，例如六位数字的地址编码，其中，第一、二位表示省级，第三、四位表示地级，第五、六位表示县级。
还需要说明的是，本实施例提供的订单支付处理方法，除了进行位置匹配处理外，还可根据机构支付准入策略中配置的其他条件进行准入检测，例如时间维度的准入检测、商户维度的准入检测、订单资源数额维度的准入检测，并在各维度的准入检测都通过的情况下，基于机构账户进行订单支付。
综上所述，本实施例提供的订单支付处理方法，在获取到机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令后，首先读取机构用户所述机构的机构支付准入策略中配置的准入位置集合，然后基于支付指令携带的支付信息，按照预先配置的位置检测链路，首先基于支付指令携带的商户标识查询商户是否携带商户授权标记，若是，确定商户为目标位置对象，读取商户标识关联的商户位置信息作为支付定位信息，若否，基于支付指令携带的用户标识，在机构子程序的位置信息存储区域读取机构用户访问机构子程序是采集并存储的终端位置信息(最后一次采集并存储的)，并核验终端位置信息是否为有效位置信息，若是，将机构子程序确定为目标位置对象，并将读取到的终端位置信息作为支付定位信息，若否，将支付应用确定为目标位置对象，并调用用户终端配置的位置采集组件采集终端位置信息并将采集的终端位置信息确定为支付定位信息，以此，提升确定的支付定位信息的准确性，使支付定位信息能够准确有效的反映机构用户的真实位置，在获得支付定位信息后，将支付定位信息和准入位置集合中的准入位置进行位置匹配处理，若匹配成功，基于机构的机构账户对待支付订单进行订单支付，以此，提升机构支付的有效性，避免机构的资源损失，同时，提升机构用户基于机构账户进行支付的便捷性。
下述以本实施例提供的一种订单支付处理方法在机构支付场景的应用为例，对本实施例提供的订单支付处理方法进行进一步说明，参见图3，应用于机构支付场景的订单支付处理方法，具体包括如下步骤。
步骤S302，获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取机构用户所属机构的机构支付准入策略中配置的准入位置集合。
步骤S304，基于支付指令携带的商户标识，查询商户是否携带商户授权标记；若是，读取商户标识关联的商户位置信息作为支付定位信息并执行步骤S314至步骤S314；若否，执行步骤S306。
步骤S306，基于支付指令携带的用户标识，在机构子程序的位置信息存储区域读取机构用户访问机构子程序是采集并存储的终端位置信息。
步骤S308，根据终端位置信息的采集时间和支付指令的获取时间，核验终端位置信息是否为有效位置信息；若是，将终端位置信息为支付定位信息并执行步骤S314至步骤S314；若否，执行步骤S310至步骤S314。
步骤S310，根据机构用户对支付应用的位置授权标记，调用机构用户的用户终端配置的位置采集组件采集终端位置信息，并将终端位置信息确定为支付定位信息。
步骤S312，将支付定位信息和准入位置集合中的准入位置进行位置匹配处理。
也即是，查询准入位置集合中是否包含支付定位信息，若是，确定匹配成功；若否，确定匹配失败。
步骤S314，若匹配成功，根据机构的机构账户对待支付订单进行支付处理。
下述以本实施例提供的一种订单支付处理方法在标识支付场景的应用为例，结合对本实施例提供的订单支付处理方法进行进一步说明，参见图4，应用于标识支付场景的订单支付处理方法，具体包括如下步骤。
步骤S402，获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取机构用户所属机构的机构支付准入策略中配置的准入位置集合。
步骤S404，读取支付指令携带的标识标记类别。
步骤S406，根据标识标记类别读取位置检测链路，并按照位置检测链路进行位置检测，获得目标位置对象。
步骤S408，将目标位置对象的对象位置信息作为支付定位信息。
步骤S410，将支付定位信息和准入位置集合中的准入位置进行位置匹配处理。
步骤S412，根据匹配处理结果对应的账户类型确定支付账户，并基于支付账户进行订单支付。
本说明书提供的一种订单支付处理装置的一个或者多个实施例如下。
在上述的实施例中，提供了一种订单支付处理方法，与之相对应的，还提供了一种订单支付处理装置，下面结合附图进行说明。
参照图5，其示出了本实施例提供的一种订单支付处理装置实施例的示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种订单支付处理装置，包括：指令获取模块502，被配置为获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；位置检测模块504，被配置为基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；订单支付模块506，被配置为将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
本说明书提供的一种订单支付处理设备的一个或者多个实施例如下。
对应上述描述的一种订单支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种订单支付处理设备，该订单支付处理设备用于执行上述提供的订单支付处理方法，图6为本说明书一个或多个实施例提供的一种订单支付处理设备的结构示意图。
本实施例提供的一种订单支付处理设备，包括：如图6所示，订单支付处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器601和存储器602，存储器602中可以存储有一个或一个以上存储应用程序或数据。其中，存储器602可以是短暂存储或持久存储。存储在存储器602的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括订单支付处理设备中的一系列计算机可执行指令。更进一步地，处理器601可以设置为与存储器602通信，在订单支付处理设备上执行存储器602中的一系列计算机可执行指令。订单支付处理设备还可以包括一个或一个以上电源603，一个或一个以上有线或无线网络接口604，一个或一个以上输入/输出接口605，一个或一个以上键盘606等。
在一个具体的实施例中，订单支付处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对订单支付处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
本说明书提供的一种计算机可读存储介质的一个或者多个实施例如下。
对应上述描述的一种订单支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种计算机可读存储介质。
本实施例提供的计算机可读存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
需要说明的是，本说明书中关于计算机可读存储介质的实施例与本说明书中关于订单支付处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或者相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处，比如装置实施例、设备实施例和可读存储介质实施例，三者均相似于方法实施例，所以描述地比较简单，阅读装置实施例、设备实施例和可读存储介质实施例中的相关内容请参照方法实施例的部分说明即可。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的软件来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个实施例可提供为方法、系统或计算机程序软件。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书可采用在一个或多个其中包含有计算机可用程序代码的计算机可读存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序软件的形式。
本说明书是参照根据本说明书实施例的方法、设备(系统)、和计算机程序软件的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的可读存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (15)

  1. 一种订单支付处理方法，包括：
    获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；
    基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；
    将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
  2. 根据权利要求1所述的订单支付处理方法，所述基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息，包括：
    读取所述支付指令携带的商户标识，并基于所述商户标识查询所述商户是否携带商户授权标记；
    若是，确定所述商户为目标位置对象，读取所述商户标识关联的商户位置信息作为所述支付定位信息。
  3. 根据权利要求2所述的订单支付处理方法，若所述基于所述商户标识查询所述商户是否携带商户授权标记操作执行之后的执行结果为否，则执行如下操作：
    基于所述支付指令携带的用户标识，在机构子程序的位置信息存储区域读取所述机构用户访问所述机构子程序时采集并存储的终端位置信息；
    根据所述终端位置信息的采集时间和所述支付指令的获取时间，核验所述终端位置信息是否为有效位置信息；
    若是，将所述机构子程序确定为目标位置对象，并将所述终端位置信息作为所述支付定位信息。
  4. 根据权利要求3所述的订单支付处理方法，若所述根据所述终端位置信息的采集时间和所述支付指令的获取时间，核验所述终端位置信息是否为有效位置信息操作执行之后的执行结果为否，则执行如下操作：
    将支付应用确定为目标位置对象，根据所述机构用户对支付应用的位置授权标记，调用所述机构用户的用户终端配置的位置采集组件采集终端位置信息；
    将采集的终端位置信息确定为所述支付定位信息。
  5. 根据权利要求1所述的订单支付处理方法，所述基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息，包括：
    基于所述支付指令中携带的标识标记类别，确定进行位置检测的位置检测链路；
    按照所述位置检测链路进行位置检测，获得目标位置对象，并将所述目标位置对象对应的对象位置信息作为所述支付定位信息。
  6. 根据权利要求5所述的订单支付处理方法，所述支付指令，在商户设备采集所述机构用户基于支付应用展示的所述机构用户的应用付款标识后生成；
    相应的，所述基于所述支付指令中携带的标识标记类别，确定进行位置检测的位置检测链路，包括：
    基于所述支付指令中携带的应用付款标识的标识标记类别，将应用检测链路确定为位置检测链路。
  7. 根据权利要求6所述的订单支付处理方法，所述按照所述位置检测链路进行位置检测，获得目标位置对象，并将所述目标位置对象对应的对象位置信息作为支付定位信息，包括：
    根据所述应用检测链路中包含的所述支付应用的应用标识，将所述支付应用确定为所述目标位置对象；
    根据所述机构用户对所述支付应用的位置授权标记，调用所述机构用户的用户终端配置的位置采集组件采集终端位置信息，将所述终端位置信息作为所述支付定位信息。
  8. 根据权利要求5所述的订单支付处理方法，所述支付指令，在商户设备采集所述机构用户基于支付应用配置的机构子程序展示所述机构用户的子程序付款标识后生成；
    相应的，所述基于所述支付指令中携带的标识标记类别，确定进行位置检测的位置检测链路，包括：
    基于所述支付指令中携带的子程序付款标识的标识标记类别，将子程序检测链路确定为位置检测链路。
  9. 根据权利要求8所述的订单支付处理方法，所述按照所述位置检测链路进行位置检测，获得目标位置对象，并将所述目标位置对象对应的对象位置信息作为支付定位信息，包括：
    读取在所述子程序检测链路中的机构子程序的位置信息存储渠道存储的终端位置信息；所述终端位置信息在所述机构用户访问所述机构子程序时调用用户终端的位置采集组件采集获得；
    核验所述终端位置信息的采集时间是否符合检测条件；
    若是，将所述机构子程序作为目标位置对象，并将所述终端位置信息作为所述支付定位信息；
    若否，将所述子程序检测链路中所述支付应用作为所述目标位置对象，并基于所述机构用户对所述支付应用的位置授权标记，调用所述用户终端的位置采集组件采集支付定位信息。
  10. 根据权利要求1所述的订单支付处理方法，所述读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合，包括：
    确定所述待支付订单的订单场景，并在所述机构支付准入策略中查询与所述订单场景匹配的目标准入场景；
    在所述机构支付准入策略中读取所述目标准入场景下的准入位置集合。
  11. 根据权利要求1所述的订单支付处理方法，所述根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付，包括：
    若所述匹配处理结果为匹配成功，根据对应的机构账户类型读取所述机构的机构账户，并基于所述机构账户进行订单支付；
    若所述匹配处理结果为匹配失败，根据对应的用户账户类型读取所述机构用户的用户账户，并基于所述用户账户进行订单支付。
  12. 根据权利要求11所述的订单支付处理方法，所述基于所述机构账户进行订单支付，包括：
    根据所述机构账户的账户标识和/或所述商户的商户标识，查询所述机构与所述商户约定的机构支付方式；
    基于所述机构支付方式对所述待支付订单进行订单支付。
  13. 一种订单支付处理装置，包括：
    指令获取模块，被配置为获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；
    位置检测模块，被配置为基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；
    订单支付模块，被配置为将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
  14. 一种订单支付处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述处理器执行所述计算机可执行指令以实现以下流程：
    获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；
    基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；
    将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
  15. 一种计算机可读存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    获取机构用户与商户配合进行标识采集后提交的对待支付订单的支付指令，并读取所述机构用户所属机构的机构支付准入策略中配置的准入位置集合；
    基于所述支付指令携带的支付信息，按照位置检测链路进行位置检测，并将位置检测获得的目标位置对象的对象位置信息作为支付定位信息；
    将所述支付定位信息和所述准入位置集合中的准入位置进行位置匹配处理，根据匹配处理结果对应的账户类型确定支付账户，并基于所述支付账户进行订单支付。
PCT/CN2025/079794 2024-03-01 2025-02-28 订单支付处理 Pending WO2025180482A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410240344.3A CN118172057A (zh) 2024-03-01 2024-03-01 订单支付处理方法及装置
CN202410240344.3 2024-03-01

Publications (1)

Publication Number Publication Date
WO2025180482A1 true WO2025180482A1 (zh) 2025-09-04

Family

ID=91355797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/079794 Pending WO2025180482A1 (zh) 2024-03-01 2025-02-28 订单支付处理

Country Status (2)

Country Link
CN (1) CN118172057A (zh)
WO (1) WO2025180482A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118172057A (zh) * 2024-03-01 2024-06-11 支付宝(杭州)信息技术有限公司 订单支付处理方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150332264A1 (en) * 2014-05-16 2015-11-19 Bank Of America Corporation Tokenization of user accounts for direct payment authorization channel
CN110782331A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种打车方法及装置、电子设备、存储介质
CN110852828A (zh) * 2019-09-27 2020-02-28 口碑(上海)信息技术有限公司 一种数据处理方法、装置及系统
CN113205331A (zh) * 2020-11-24 2021-08-03 支付宝(杭州)信息技术有限公司 一种支付方法及装置、电子设备和存储介质
CN116384983A (zh) * 2023-03-31 2023-07-04 支付宝(杭州)信息技术有限公司 支付处理方法及装置
CN118172057A (zh) * 2024-03-01 2024-06-11 支付宝(杭州)信息技术有限公司 订单支付处理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150332264A1 (en) * 2014-05-16 2015-11-19 Bank Of America Corporation Tokenization of user accounts for direct payment authorization channel
CN110852828A (zh) * 2019-09-27 2020-02-28 口碑(上海)信息技术有限公司 一种数据处理方法、装置及系统
CN110782331A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种打车方法及装置、电子设备、存储介质
CN113205331A (zh) * 2020-11-24 2021-08-03 支付宝(杭州)信息技术有限公司 一种支付方法及装置、电子设备和存储介质
CN116384983A (zh) * 2023-03-31 2023-07-04 支付宝(杭州)信息技术有限公司 支付处理方法及装置
CN118172057A (zh) * 2024-03-01 2024-06-11 支付宝(杭州)信息技术有限公司 订单支付处理方法及装置

Also Published As

Publication number Publication date
CN118172057A (zh) 2024-06-11

Similar Documents

Publication Publication Date Title
CN107038042B (zh) 一种业务执行的方法及装置
CN111489145A (zh) 一种基于区块链的资源转移方法、装置及设备
CN110097468A (zh) 基金赎回方法、装置、设备及系统
CN114548963B (zh) 支付交互处理方法及装置
WO2025077657A1 (zh) 基于信用的交易处理方法及装置
CN110390182A (zh) 一种确定小程序类目的方法、系统及设备
WO2025180482A1 (zh) 订单支付处理
WO2025185576A1 (zh) 基于虚拟邮箱的电子发票处理
WO2024198539A1 (zh) 支付处理方法及装置
CN116596529A (zh) 交易处理方法及装置
WO2025185577A1 (zh) 资金处理
WO2025256378A1 (zh) 资金处理
CN116188123A (zh) 基于信用的租物管理方法及装置
WO2025256377A1 (zh) 转账处理
WO2026037157A1 (zh) 一种交易处理和权益资产查询及处理方法、装置及设备
WO2025180479A1 (zh) 资源额度处理
WO2025060761A1 (zh) 订单结算处理
WO2024152846A1 (zh) 支付处理方法及装置
CN111798242A (zh) 一种业务处理的方法及装置
CN107483534B (zh) 一种业务处理的方法及装置
CN110413614A (zh) 一种数据表生成的方法及装置
CN115423461A (zh) 账单处理方法及装置
CN110046954B (zh) 一种卡片申请的处理方法、装置、设备及系统
CN113807888A (zh) 营销处理方法及装置
HK40097373A (zh) 订单支付处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25761116

Country of ref document: EP

Kind code of ref document: A1