WO2024198539A1 - 支付处理方法及装置 - Google Patents

支付处理方法及装置 Download PDF

Info

Publication number
WO2024198539A1
WO2024198539A1 PCT/CN2023/139397 CN2023139397W WO2024198539A1 WO 2024198539 A1 WO2024198539 A1 WO 2024198539A1 CN 2023139397 W CN2023139397 W CN 2023139397W WO 2024198539 A1 WO2024198539 A1 WO 2024198539A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
institution
order
paid
location 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.)
Ceased
Application number
PCT/CN2023/139397
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 WO2024198539A1 publication Critical patent/WO2024198539A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • 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/327—Short range or proximity payments by means 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4015—Transaction verification using location information

Definitions

  • This document relates to the field of data processing technology, and in particular to a payment processing method and device.
  • One or more embodiments of the present specification provide a payment processing method, which is applied to an institution code platform, and the method includes: obtaining a payment access request for an order to be paid of an institution member sent by a payment platform.
  • the payment access request carries payment location information.
  • the order to be paid is submitted based on the institution code of the institution to which the institution member belongs.
  • the location distance is calculated based on the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • One or more embodiments of the present specification provide another payment processing method, which is applied to a payment platform, and the method includes: obtaining an order to be paid and payment location information of an institutional member.
  • the order to be paid is submitted based on the institutional code of the institution to which the institutional member belongs.
  • a payment access request for the order to be paid carrying the payment location information is generated and sent to the institutional code platform. If a payment access result sent by the institutional code platform is received, payment processing is performed on the order to be paid based on the institutional account bound to the institutional code.
  • the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store. The location distance is calculated based on the payment location information and the location information of the merchant store.
  • One or more embodiments of the present specification provide a payment processing device, which runs on an institution code platform, and the device includes: a request acquisition module, which is configured to obtain a payment access request for an order to be paid of an institution member sent by a payment platform.
  • the payment access request carries payment location information.
  • the order to be paid is submitted based on the institution code of the institution to which the institution member belongs.
  • a distance calculation module is configured to respond to the payment access request and calculate the location distance based on the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • a distance judgment module is configured to judge whether the location distance is within a preset distance range for institutional payment at the merchant store; if so, a result sending module is run, and the result sending module is configured to determine that the payment access of the order to be paid is successful and send a payment access result to the payment platform, so as to perform payment processing on the order to be paid based on the institution account bound to the institution code.
  • One or more embodiments of the present specification provide another payment processing device, which runs on a payment platform, and the device includes: an information acquisition module, which is configured to obtain the pending payment orders and payment location information of the institutional members. The pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong.
  • a request sending module is configured to generate a payment access request for the pending payment order carrying the payment location information and send it to the institutional code platform.
  • the payment processing module is configured to perform payment processing on the pending payment order based on the institutional account bound to the institutional code if a payment access result sent by the institutional code platform is received.
  • the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store.
  • the location distance is calculated based on the payment location information and the location information of the merchant store.
  • One or more embodiments of the present specification provide a payment processing device, including: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: obtains a payment access request for an order to be paid of an institutional member sent by a payment platform.
  • the payment access request carries payment location information.
  • the order to be paid is submitted based on the institution code of the institution to which the institutional member belongs.
  • the location distance is calculated based on the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • One or more embodiments of the present specification provide another payment processing device, including: a processor; and a memory configured to store computer executable instructions, which, when executed, cause the processor to: obtain an order to be paid and payment location information of an institutional member.
  • the order to be paid is submitted based on the institutional code of the institution to which the institutional member belongs.
  • a payment access request for the order to be paid carrying the payment location information is generated and sent to an institutional code platform. If a payment access result sent by the institutional code platform is received, payment processing is performed on the order to be paid based on the institutional account bound to the institutional code.
  • the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store.
  • the location distance is calculated based on the payment location information and the location information of the merchant store.
  • One or more embodiments of the present specification provide a storage medium for storing computer-executable instructions.
  • the execution instruction implements the following process when executed by the processor: obtain the payment access request of the pending payment order of the institutional member sent by the payment platform.
  • the payment access request carries payment location information.
  • the pending payment order is submitted based on the institutional code of the institution to which the institutional member belongs.
  • the location distance is calculated according to the payment location information and the location information of the merchant store corresponding to the pending payment order.
  • One or more embodiments of the present specification provide another storage medium for storing computer-executable instructions, which implement the following process when executed by a processor: obtaining the pending payment orders and payment location information of the institutional members.
  • the pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong.
  • a payment access request for the pending payment order carrying the payment location information is generated and sent to the institutional code platform. If a payment access result sent by the institutional code platform is received, payment processing is performed on the pending payment order based on the institutional account bound to the institutional code.
  • the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store. The location distance is calculated based on the payment location information and the location information of the merchant store.
  • FIG. 1 is a schematic diagram of an implementation environment of a payment processing method provided by one or more embodiments of this specification.
  • FIG. 2 is a processing flow chart of a payment processing method provided by one or more embodiments of this specification.
  • FIG3 is a processing flow chart of a payment processing method applied to a business travel scenario provided by one or more embodiments of this specification.
  • FIG. 4 is a processing flow chart of another payment processing method provided by one or more embodiments of this specification.
  • FIG5 is a processing flow chart of another payment processing method applied to a business travel scenario provided by one or more embodiments of this specification.
  • FIG. 6 is a schematic diagram of an embodiment of a payment processing device provided in one or more embodiments of this specification.
  • FIG. 7 is a schematic diagram of another payment processing device embodiment provided by one or more embodiments of this specification.
  • FIG8 is a schematic diagram of the structure of a payment processing device provided in one or more embodiments of this specification.
  • FIG. 9 is a schematic diagram of the structure of another payment processing device provided in one or more embodiments of this specification.
  • FIG. 1 is a schematic diagram of an implementation environment of a payment processing method provided by one or more embodiments of this specification.
  • the payment processing method provided in one or more embodiments of the present specification may be applicable to the implementation environment of order payment, which implementation environment includes at least the institution code server 101 of the institution code platform, or at least the payment server 102 of the payment platform.
  • the implementation environment may also include a member terminal 103 of an organization member.
  • the member terminal 103 may be configured with a client of an organization code.
  • the specific form of the client may be an application, a subroutine within an application, a service module within an application, or a web program.
  • the institution code server 101 can be a server, or a server cluster composed of several servers, or one or more cloud servers in a cloud computing platform, which is used for payment access processing.
  • the number and method of server deployment can be determined according to the magnitude of the number of payment access requests submitted within a time period. For example, when the number of requests is small, one or more servers can be deployed; for another example, when the number of requests reaches a certain magnitude, a server cluster composed of several servers can be deployed.
  • the payment server 102 may be a single server, or a server cluster consisting of a plurality of servers, or one or more cloud servers in a cloud computing platform, for performing payment processing.
  • the member terminal 103 can be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality), a vehicle-mounted terminal, an IoT device, a wearable smart device, a laptop computer and a desktop computer, etc.
  • the member terminal 103 can be installed with an application or a browser.
  • the payment server 102 may send a payment access request for the order to be paid to the institution code server 101.
  • the institution code server 101 calculates the location distance based on the location information of the merchant store corresponding to each order to be paid in the payment location information, and sends the payment access result to the payment server 102 when the location distance is within the preset distance range for institutional payment at the merchant store, so that the payment server can process the payment for the order to be paid based on the institution code.
  • One or more embodiments of a payment processing method provided in this specification are as follows: The payment processing method provided in this embodiment, After obtaining the payment access request for the pending payment order of the institutional member sent by the payment platform, the location distance is calculated based on the payment location information and the location information of the merchant store corresponding to the pending payment order. When the location distance is within the preset distance range for institutional payment at the merchant store, the payment access of the pending payment order is determined to be successful and the payment access result is sent to the payment platform to process the payment for the pending payment order based on the institutional code. In this way, the verification of the location distance can effectively avoid the situation where the institutional member makes institutional payment at the merchant store not designated by the institution, thereby reducing the financial loss of the merchant store or the institution and improving the security of the institutional payment.
  • the payment processing method provided in this embodiment specifically includes steps S202 to S208 .
  • Step S202 obtaining a payment access request for an order to be paid of an institution member sent by the payment platform.
  • the institutions in this embodiment include various forms of organizations such as enterprises, institutions, and social groups.
  • institutions include not only organizations at this level, but also internal organizations of institutions, such as enterprise departments or branches.
  • the members of the institutions include institutional staff and related personnel.
  • This embodiment can be applied to the institution code platform.
  • the payment platform includes a platform for paying for payment orders.
  • the institution code platform includes a platform that provides institution code related services.
  • the payment access request carries payment location information; the order to be paid is submitted based on the organization code of the organization to which the organization member belongs.
  • the organization code refers to an identification code set by the organization for the payment of organization members, etc.
  • the organization code can uniquely identify the organization.
  • the organization code can be in the form of identification codes such as QR code, bar code, and sound code.
  • Organization members can use the organization code to implement organization payment.
  • the organization code can also be used for invoicing, reimbursement and other processing, and can also be used to identify the membership of organization members in the organization.
  • the organization code is used as a digital ID card for corporate employees, and corporate employees can use the organization code as a voucher to receive benefits and subsidies issued by the company.
  • the order to be paid includes orders waiting for payment; the order to be paid may be a commodity order to be paid, or a service order to be paid, such as a beauty order to be paid, a training course order to be paid, etc.
  • the order to be paid is submitted after scanning the institution code with a code scanning device configured at the merchant store.
  • the payment location information includes the location information of the organization members when submitting the order to be paid based on the organization code. For example, when the organization members submit the order to be paid at a merchant store by displaying the code, the location information of the organization members is the payment location information.
  • the payment location information is read from the order to be paid, or the payment location information is obtained by screening the payment location information set obtained by the timed task detection; for example, the location information whose detection time span meets the preset conditions is screened in the payment location information set as the payment location information; wherein the detection time span includes the time span from the detection time to the screening time when the location information is detected, and the preset condition includes the condition that the detection time span is the minimum.
  • the merchant store can submit the order to be paid to the payment platform after scanning the institution code displayed on the member terminal of the institution member through the configured scanning device.
  • the member terminal of the institution member can submit the order to be paid to the payment platform based on the institution code by scanning the merchant identification code of the merchant store.
  • the payment platform can send a request to the institution code platform to verify whether the order to be paid can be paid through institutional payment.
  • the request is a payment access request, that is, a payment access verification request for paying the order to be paid through institutional payment, thereby improving the security of institutional payment.
  • the payment platform obtains the pending payment orders and payment location information of the institution members, generates a payment access request for the pending payment orders carrying the payment location information and sends it to the institution code platform.
  • the institution code platform can obtain the payment access request for the pending payment orders of the institution members sent by the payment platform.
  • the organization may realize the organization payment of the organization members in the merchant stores by associating with the merchant stores.
  • the organization is associated with at least one merchant store where the organization members make the organization payment;
  • the at least one merchant store is associated with the organization in the following manner: obtaining the access instruction to the merchant store set submitted by the organization through the web page corresponding to the network address of the organization code platform; issuing the merchant store set to the organization based on the access instruction, so as to associate the at least one merchant store with the organization based on the selection instruction of the organization to the at least one merchant store in the merchant store set.
  • the merchant store set refers to a store set consisting of one merchant store or multiple merchant stores; the merchant store set includes a store set associated with the institution code platform.
  • the institutional payment includes a payment method at a merchant store based on an institutional payment channel. During the payment process, institutional members make institutional payments at merchant stores by displaying the institution code on the member terminal; the institutional payment may also include official payments.
  • an institution code page containing the channel identifier of the institutional payment channel is sent to the institutional member to submit the pending payment order based on the institution code and the institutional payment channel displayed on the institution code page; in the first optional implementation mode provided by this embodiment, before obtaining the payment access request for the pending payment order of the institutional member sent by the payment platform, the following operations are also performed: detecting the submission time of the code display instruction submitted by the institutional member for the institution code; judging whether the submission time is within the time value range for the institutional member to make the institutional payment The time range for the institution member to make institution payment is within the range; if so, an institution code page containing the channel identifier of the institution payment channel is sent to the institution member to submit the order to be
  • the time value range includes the time value range set by the institution to the institution members for institutional payment, such as the time value range set by the institution to the institution members for institutional payment from 16:00 to 20:00.
  • the institutional payment channel includes a channel for paying the order to be paid based on the institutional account bound to the institution; specifically, the order to be paid can be submitted based on the institution code and institutional payment channel displayed on the institution code page, so that after the payment platform receives the payment access result of the order to be paid, the payment processing of the order to be paid is performed based on the institutional account bound to the institutional payment channel.
  • the following operation can also be performed: if the merchant store corresponding to the pending payment order is in at least one merchant store associated with the institution, determine whether the submission time of the pending payment order is within the time value range for the institutional member to make institutional payment. If so, mark the pending payment order as paid for official business; if not, do not process it. Accordingly, in the process of obtaining the payment access request for the pending payment order of the institutional member sent by the payment platform, the following operation can be performed: obtain the payment access request for the pending payment order submitted by the payment platform based on the pending payment mark of the institutional member's pending payment order.
  • the second optional implementation method provided in this embodiment before obtaining the payment access request for the institutional member's order to be paid sent by the payment platform, also performs the following operations: based on the travel area of the institutional member, query at least one merchant store associated with the institution; based on the at least one merchant store, make a recommendation to the institutional member, so as to select the merchant store from the at least one merchant store to submit the order to be paid.
  • the travel area includes the geographical area where the organization members travel, that is, the area where the organization members travel.
  • the travel area can be a city, a district or a county in a city, or a smaller address unit.
  • At least one merchant store associated with the organization in the travel area of the organization members is queried, and recommendation processing is performed to the organization members based on the at least one merchant store, so that the merchant store is selected from the at least one merchant store to submit the order to be paid.
  • the collection identifier of the merchant store recorded in the order to be paid can be verified first. Specifically, it can be determined whether the collection identifier of the merchant store in the order to be paid is consistent with the collection identifier of the merchant store associated with the institution.
  • step S204 in an optional implementation provided by this embodiment, after obtaining the payment access request for the order to be paid of the institutional member sent by the payment platform, the following operation is also performed: read the collection identifier of the merchant store from the order to be paid; determine whether the collection identifier is consistent with the collection identifier of the merchant store associated with the institution; if so, execute the following step S204, if not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • the payment identification of the merchant store includes an identification indicating that the merchant store collects payment, such as a payment account. It should be noted that the payment identification in this embodiment can also be replaced by the store name and/or store address of the merchant store, and in addition, the payment identification can also be replaced by other types of information.
  • the location distance may be calculated when the payment location information matches the travel area in the travel application of the member of the organization.
  • the following operation is also performed: determine whether the payment location information matches the travel area in the travel application of the member of the organization; if so, execute the following step S204; if not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • the payment location information is b1 district in a1 city
  • the travel area in the travel application is b2 district in a2 city. Determine whether b1 district in a1 city is consistent with b2 district in a2 city. If so, execute the following step S204. If not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • the following operations are performed: a travel application template is issued to the organization member, and a target travel application submitted by the organization member through the travel application template is obtained; if the payment location information matches the travel area in the target travel application, the following step S204 is performed; if the payment location information does not match the travel area in the target travel application, it is determined that the payment access of the order to be paid has failed and the payment access failure result is returned to the payment platform or no processing is performed.
  • the credit value of the organization member is updated to update the geographic area for the organization member to make the organization payment or the amount of funds for the organization member to make the organization payment based on the updated credit value. Or update the merchant store type where institutional members make institutional payments.
  • Step S204 in response to the payment access request, calculating the location distance according to the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • the above-mentioned payment access request of the order to be paid of the institution member sent by the payment platform is obtained.
  • the location distance is calculated with the help of the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • the payment location information of this embodiment includes the location information of the organization member when submitting the order to be paid based on the organization code.
  • the payment location information includes the payment location longitude and/or the payment location latitude.
  • the location information includes the location longitude and/or the location latitude.
  • the location information of the merchant store is obtained by at least one of the following methods: entering into a web page corresponding to the network address of the institution code platform, entering into a merchant subroutine, or passing in by calling a data interface of the institution code platform.
  • the location distance includes the distance between the payment location corresponding to the payment location information and the merchant location corresponding to the location information of the merchant store.
  • the location information of the merchant stores can be obtained by the front-end method, that is, the location information of the merchant stores is entered through the merchant subroutine.
  • the location information of the merchant stores can also be obtained by the back-end method, that is, the location information of the merchant stores is entered into the web page corresponding to the network address of the institution code platform or the location information of the merchant stores is passed in by calling the data interface of the institution code platform.
  • the location distance in order to improve the accuracy and effectiveness of the location distance, can be calculated comprehensively from the two perspectives of longitude and latitude.
  • the following operations are performed: based on the payment location latitude in the payment location information and the location latitude in the location information, the latitude feature parameters are calculated, and based on the payment location longitude in the payment location information and the location longitude in the location information, the longitude feature parameters are calculated; the location distance is calculated based on the latitude feature parameters and the longitude feature parameters.
  • the latitude characteristic parameters include characteristic parameters calculated from the latitude dimension, that is, the characteristic parameters calculated using the latitude data, and the latitude characteristic parameters include latitude characteristic values;
  • the longitude characteristic parameters include characteristic parameters calculated from the longitude dimension, that is, the characteristic parameters calculated using the longitude data, and the longitude characteristic parameters include longitude characteristic values.
  • Step S206 determining whether the location distance is within a preset distance range for performing institutional payment at the merchant store.
  • step S208 it is determined whether the location distance is within the preset distance range for institutional payment at the merchant store. If so, the following step S208 is executed. If not, it is determined that the payment access of the order to be paid has failed, and the payment access failure result is returned to the payment platform or no processing is performed.
  • the preset distance range includes the distance range of the merchant store for institutional payment, for example, the preset distance range is 20m.
  • the preset distance range is determined based on the store characteristic data of the merchant store;
  • the store characteristic data includes at least one of the following: store area, store popularity, and the geographical area where the merchant store is located.
  • the store area and store popularity may be proportional to the preset distance range of the merchant store, and the geographical area where the merchant store is located may include the flow of people in the geographical area where the merchant store is located, and the flow of people may also be proportional to the preset distance range of the merchant store.
  • the following operations may also be performed: updating the number of payment access failures of the institutional members, and adjusting the amount of funds of the institutional members in the institution based on the updated number of payment access failures, or adjusting the number of merchant stores where the institutional members make institutional payments based on the updated number of payment access failures, or adjusting the type of merchant stores where the institutional members make institutional payments based on the updated number of payment access failures, or adjusting the geographical area where the institutional members make institutional payments based on the updated number of payment access failures.
  • Step S208 determining that the payment access of the order to be paid is successful and sending the payment access result to the payment platform, so as to perform payment processing on the order to be paid based on the institution account bound to the institution code.
  • the payment access success described in this embodiment includes successful access to institutional payment for the order to be paid; the payment access result includes the access result of institutional payment for the order to be paid; and the payment access failure result includes the access failure result of institutional payment for the order to be paid.
  • the institution code platform determines that the payment access of the order to be paid is successful and sends the payment access result to the payment platform.
  • the payment platform processes the payment for the order to be paid based on the institution account bound to the institution code. Specifically, the payment can be deducted from the institution account bound to the institution code based on the order amount of the order to be paid.
  • step S202 the travel application submitted by the institutional member of the organization and the target travel application submitted by the target institutional member can be obtained.
  • the target institutional member is associated with the institutional member; after step S206 is executed, the following operations can also be performed: If so, the second location distance is calculated based on the payment location information of the target institutional member and the location information of the merchant store corresponding to the order to be paid of the target institutional member. When the second location distance is within the preset distance range for institutional payment at the merchant store, it is determined that the payment access of the order to be paid of the institutional member is successful and the payment access result is sent to the payment platform, so that the payment processing of the order to be paid is performed based on the institutional account bound to the institutional code.
  • the target order matching the pending payment order is queried according to the merchant store corresponding to the pending payment order (specifically, the target order matching the merchant store corresponding to the pending payment order is queried according to the merchant store corresponding to the pending payment order), and the submission time of the target order is after the submission time of the pending payment order or is the same as the submission time of the pending payment order; when the first position distance is within the preset distance range for institutional payment at the merchant store corresponding to the pending payment order, and the second position distance is within the preset distance range for institutional payment at the merchant store, it is determined that the payment access of the pending payment order and the target order is successful and the payment access result is sent to the payment platform, so as to perform combined
  • the following operations can also be performed: obtain the permission revocation request of the institution to which the institutional member belongs submitted by the target merchant store; revoke the payment authority of the institutional member of the institution to make institutional payments at the target merchant store based on the permission revocation request; optionally, the permission revocation request is submitted based on the permission revocation entrance; the permission revocation entrance is opened to the target merchant store upon detecting that the number of payment access failures of the institution at the target merchant store exceeds a threshold number.
  • the following further illustrates the payment processing method provided in this embodiment by taking the application of a payment processing method provided in this embodiment in a business travel scenario as an example.
  • the payment processing method applied to the business travel scenario specifically includes steps S302 to S318.
  • Step S302 detecting the time when the organization member submits the code display instruction of the organization code.
  • Step S304 determine whether the submission time is within the time range for institutional members to make institutional payments; if so, execute steps S306 to S310; if not, do nothing.
  • Step S306 sending an institution code page including a channel identifier of the institution's payment channel to the institution members, so as to submit the order to be paid based on the institution code and the institution's payment channel displayed on the institution code page.
  • Step S308 obtaining the payment access request of the institution member's order to be paid sent by the payment platform.
  • the payment admission request carries payment location information.
  • Step S310 in response to the payment access request, determine whether the payment location information matches the travel area in the travel application of the organization member; if so, execute the following steps S312 to S316; if not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • Step S312 calculating the latitude feature value based on the payment location latitude in the payment location information and the location latitude in the location information of the merchant store corresponding to the order to be paid, and calculating the longitude feature value based on the payment location longitude in the payment location information and the location longitude in the location information.
  • Step S314 calculating the position distance according to the latitude characteristic value and the longitude characteristic value.
  • Step S316 determine whether the location distance is within the preset distance range for institutional payment at the merchant store; if so, execute step S318; if not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • Step S318, determining that the payment access of the order to be paid is successful and sending the payment access result to the payment platform, and performing payment processing on the order to be paid based on the institutional account bound to the institutional code.
  • One or more embodiments of another payment processing method provided in this specification are as follows: Referring to Figure 4, the payment processing method provided in this embodiment specifically includes steps S402 to S406.
  • the payment processing method provided in this embodiment can be applied to a payment platform.
  • the payment processing method provided in the above-mentioned embodiments can be applied to an institution code platform.
  • the payment processing method provided in this embodiment and applicable to a payment platform cooperates with the payment processing method applicable to an institution code platform provided in the above-mentioned embodiments during execution.
  • the relevant contents of the above-mentioned embodiments can be referred to when reading this embodiment.
  • the relevant contents of this embodiment can also be referred to when reading the above-mentioned embodiments.
  • Step S402 obtaining the order to be paid and payment location information of the institution members.
  • the institutions in this embodiment include various forms of organizations such as enterprises, institutions, and social groups.
  • institutions include not only organizations at this level, but also internal organizations of institutions, such as enterprise departments or branches.
  • the members of the institutions include institutional staff and related personnel.
  • This embodiment can be applied to an institution code platform.
  • the payment platform includes a platform for paying orders to be paid.
  • the institution code platform includes a platform that provides institution code related services.
  • the order to be paid is submitted based on the institution code of the institution to which the institution members belong.
  • the organization code refers to an identification code set by the organization for the payment of its members, etc.
  • the organization code can uniquely identify the organization, and the organization code can exist in the form of identification codes such as QR code, bar code, and sound code, and the organization members can use the organization code to make the organization payment.
  • the organization code can also be used for invoicing, reimbursement and other processing, and can also be used to identify the membership of the organization members in the organization.
  • the organization code is used as a digital ID card for corporate employees, and corporate employees can use the organization code as a voucher to receive benefits and subsidies issued by the company.
  • the order to be paid includes orders waiting for payment; the order to be paid may be a commodity order to be paid, or a service order to be paid, such as a beauty order to be paid, a training course order to be paid, etc.
  • the order to be paid is submitted after scanning the institution code with a code scanning device configured at the merchant store.
  • the payment location information includes the location information of the organization members when submitting the order to be paid based on the organization code. For example, when the organization members submit the order to be paid at a merchant store by displaying the code, the location information of the organization members is the payment location information.
  • the payment location information is read from the order to be paid, or the payment location information is obtained by screening the payment location information set obtained by the timed task detection; for example, the location information whose detection time span meets the preset conditions is screened in the payment location information set as the payment location information; wherein the detection time span includes the time span from the detection time to the screening time when the location information is detected, and the preset condition includes the condition that the detection time span is the minimum.
  • the payment platform obtains the pending payment orders and payment location information of the institution members.
  • the specific payment platform can obtain multiple payment location information through scheduled tasks, and filter the target payment location information from the multiple payment location information as the payment location information of the institution members, such as selecting the target payment location information with the most recent time as the payment location information of the institution members; in addition, the payment location information can also be recorded in the pending payment orders, and the payment location information of the institution members can be obtained through the pending payment orders.
  • Step S404 Generate a payment access request for the order to be paid that carries the payment location information and send it to the institution code platform.
  • the above-mentioned payment platform obtains the pending payment orders and payment location information of the institutional members.
  • a payment access request for the pending payment orders carrying the payment location information is generated and sent to the institutional code platform.
  • the institutional code platform obtains the payment access request for the pending payment orders of the institutional members sent by the payment platform, and in response to the payment access request, calculates the location distance according to the payment location information and the location information of the merchant store corresponding to the pending payment order, and determines whether the location distance is within the preset distance range for institutional payment at the merchant store.
  • the merchant store can submit the order to be paid to the payment platform after scanning the institution code displayed on the member terminal of the institution member through the configured scanning device.
  • the member terminal of the institution member can submit the order to be paid to the payment platform based on the institution code by scanning the merchant identification code of the merchant store.
  • the payment platform can send a request to the institution code platform to verify whether the order to be paid can be paid through institutional payment.
  • the request is a payment access request, that is, a payment access verification request for paying the order to be paid through institutional payment, thereby improving the security of institutional payment.
  • the organization may realize the payment mechanism of the organization members in the merchant stores by associating merchant stores.
  • the organization is associated with at least one merchant store where the organization members make organization payments;
  • the at least one merchant store is associated with the organization in the following manner: obtaining an access instruction to a merchant store set submitted by the organization through a web page corresponding to the network address of the organization code platform; based on the access instruction, the merchant store set is issued to the organization, so as to associate the at least one merchant store with the organization based on the organization's selection instruction for at least one merchant store in the merchant store set.
  • the merchant store set refers to a store set consisting of one merchant store or multiple merchant stores; the merchant store set includes a store set associated with the institution code platform.
  • the institutional payment includes a payment method at a merchant store based on an institutional payment channel. During the payment process, institutional members make institutional payments at merchant stores by displaying the institution code on the member terminal; the institutional payment may also include official payments.
  • the institution code platform before the institution code platform obtains the payment access request of the institution member's pending payment order sent by the payment platform, in order to improve the security and effectiveness of the institution's payment, when it is detected that the submission time of the institution member's code display instruction is within the time value range of the institution member's institution payment, the institution code page containing the channel identifier of the institution's payment channel is sent to the institution member, so as to submit the pending payment order based on the institution code and the institution's payment channel displayed on the institution code page; specifically, the institution code page Before obtaining the payment access request for the pending payment order of the institutional member sent by the payment platform, the coding platform may also perform the following operations: detecting the submission time of the institutional member's code display instruction for the institutional code; judging whether the submission time is within the time value range for the institutional member to make institutional payment; if so, sending the institutional code page containing the channel identifier of the institutional payment channel to the institutional member to submit the pending payment order based on the institutional code and the institutional payment
  • the time value range includes the time value range set by the institution to the institution members for institutional payment, such as the time value range set by the institution to the institution members for institutional payment from 16:00 to 20:00.
  • the institutional payment channel includes a channel for paying the order to be paid based on the institutional account bound to the institution; specifically, the order to be paid can be submitted based on the institution code and institutional payment channel displayed on the institution code page, so that after the payment platform receives the payment access result of the order to be paid, the payment processing of the order to be paid is performed based on the institutional account bound to the institutional payment channel.
  • the institution code platform may also perform the following operations: if the merchant store corresponding to the pending payment order is in at least one merchant store associated with the institution, determine whether the submission time of the pending payment order is within the time value range for the institution member to make institutional payment. If so, mark the pending payment order as paid for official business; if not, do not process it. Accordingly, in the process of obtaining the payment access request for the pending payment order of the institution member sent by the payment platform, the following operations may be performed: obtain the payment access request for the pending payment order submitted by the payment platform based on the pending payment mark of the institution member's pending payment order.
  • institutional members may have the need to make institutional payments in travel areas.
  • the institutional code platform may also perform the following operations before obtaining the payment access request for the institutional member's order to be paid sent by the payment platform: query at least one merchant store associated with the institution based on the travel area of the institutional member; make recommendations to the institutional member based on the at least one merchant store, so as to select the merchant store from the at least one merchant store to submit the order to be paid.
  • the travel area includes the geographical area where the organization members travel, that is, the area where the organization members travel.
  • the institution code platform can query at least one merchant store associated with the institution in the travel area of the institution members, and make recommendations to the institution members based on the at least one merchant store so that the merchant store is selected from the at least one merchant store to submit the order to be paid.
  • the institution code platform obtains the payment access request for the order to be paid of the institution member sent by the payment platform, in order to reduce the number of calculation times of the location distance calculated based on the payment location information and the location information of the merchant store, the payment collection identifier of the merchant store recorded in the order to be paid can be verified first. Specifically, it can be determined whether the payment collection identifier of the merchant store in the order to be paid is consistent with the payment collection identifier of the merchant store associated with the institution.
  • the step of calculating the location distance according to the payment location information and the location information of the merchant store corresponding to the order to be paid in response to the payment access request is executed; specifically, after the institution code platform obtains the payment access request for the order to be paid of the institution member sent by the payment platform, the following operations can be performed: reading the payment collection identifier of the merchant store from the order to be paid; determining whether the payment collection identifier is consistent with the payment collection identifier of the merchant store associated with the institution; if so, the step of calculating the location distance according to the payment location information and the location information of the merchant store corresponding to the order to be paid is performed in response to the payment access request; if not, determining that the payment access of the order to be paid has failed and returning the payment access failure result to the payment platform or not processing it.
  • the payment identification of the merchant store includes an identification indicating that the merchant store collects payment, such as a payment account. It should be noted that the payment identification in this embodiment can also be replaced by the store name and/or store address of the merchant store, and in addition, the payment identification can also be replaced by other types of information.
  • the payment location information may be matched with the travel area in the travel application of the organization member before the location distance calculation is performed.
  • the organization code platform may also perform the following operations: determine whether the payment location information matches the travel area in the travel application of the organization member; if so, execute the step of calculating the location distance according to the payment location information and the location information of the merchant store corresponding to the order to be paid in response to the payment access request; if not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • the payment location information is b1 district of a1 city
  • the travel area in the travel application is b2 district of a2 city.
  • the organization code platform determines whether b1 district of a1 city is consistent with b2 district of a2 city. If so, execute the following step S204. If not, determine that the payment access of the order to be paid has failed and return the payment access failure result to the payment platform or do not process it.
  • the organization code platform may perform the following operations: issue a travel application template to the organization member, and obtain the target travel application submitted by the organization member using the travel application template; if the payment location information matches the travel area in the target travel application, execute a response to the payment access request, and calculate the payment location information based on the payment location information and the to-be-paid order.
  • the step of calculating the location distance based on the location information of the merchant store corresponding to the order; if the payment location information does not match the travel area in the target travel application, determining that the payment access of the order to be paid has failed and returning the payment access failure result to the payment platform or not processing it.
  • the above-mentioned institution code platform obtains the payment access request of the institution member's order to be paid sent by the payment platform. After that, the institution code platform responds to the payment access request and calculates the location distance with the help of the payment location information and the location information of the merchant store corresponding to the order to be paid.
  • the payment location information described in this embodiment includes the location information of the organization member when submitting the order to be paid by displaying the organization code. For example, if the organization member submits the order to be paid at a certain merchant store by displaying the code, the location information of the merchant store is the location information of the organization member.
  • the payment location information includes the payment location longitude and/or the payment location latitude.
  • the location information includes the location longitude and/or the location latitude.
  • the location information of the merchant store is obtained by at least one of the following methods: entering into a web page corresponding to the network address of the institution code platform, entering into a merchant subroutine, or passing in by calling a data interface of the institution code platform.
  • the location distance includes the distance between the payment location corresponding to the payment location information and the merchant location corresponding to the location information of the merchant store.
  • the above-mentioned institution code platform calculates the location distance with the help of the payment location information and the location information of the merchant store corresponding to the order to be paid. After that, the institution code platform determines whether the location distance is within the preset distance range for institutional payment at the merchant store. If so, it determines that the payment access of the order to be paid is successful and sends the payment access result to the payment platform, so as to process the payment of the order to be paid based on the institution account bound to the institution code. If not, it determines that the payment access of the order to be paid has failed, and returns the payment access failure result to the payment platform or does not process it.
  • the preset distance range includes the distance range of the merchant store for institutional payment, for example, the preset distance range is 20m.
  • the preset distance range is determined based on the store characteristic data of the merchant store;
  • the store characteristic data includes at least one of the following: store area, store popularity, and the geographical area where the merchant store is located.
  • the store area and store popularity may be proportional to the preset distance range of the merchant store, and the geographical area where the merchant store is located may include the flow of people in the geographical area where the merchant store is located, and the flow of people may also be proportional to the preset distance range of the merchant store.
  • the institution code platform determines whether the location distance is within the preset distance range for institutional payment at the merchant store and the execution result is no, it can perform the following operations: determine that the payment access of the order to be paid has failed, and return the payment access failure result to the payment platform.
  • the above-mentioned institution code platform determines whether the location distance is within the preset distance range for institutional payment at the merchant store. If so, it determines that the payment access of the order to be paid is successful and sends the payment access result to the payment platform, so as to process the payment of the order to be paid based on the institution account bound to the institution code. If not, it determines that the payment access of the order to be paid has failed, and returns the payment access failure result to the payment platform or does not process it.
  • the payment access success described in this embodiment includes successful access to institutional payment for the order to be paid; the payment access result includes the access result of institutional payment for the order to be paid; and the payment access failure result includes the access failure result of institutional payment for the order to be paid.
  • Step S406 If the payment access result sent by the institution code platform is received, payment processing is performed on the order to be paid based on the institution account bound to the institution code.
  • the payment platform receives the payment access result sent by the institution code platform, it will process the payment for the order to be paid based on the institution account bound to the institution code. If it receives the payment access failure result returned by the institution code platform, it will send a payment access failure reminder to the institution members.
  • the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store; the location distance is calculated based on the payment location information and the location information of the merchant store.
  • the location distance in order to improve the accuracy and effectiveness of the location distance, may be calculated comprehensively from the two perspectives of longitude and latitude, and the location distance is calculated in the following manner: latitude characteristic parameters are calculated based on the payment location latitude in the payment location information and the location latitude in the location information, and longitude characteristic parameters are calculated based on the payment location longitude in the payment location information and the location longitude in the location information; the location distance is calculated based on the latitude characteristic parameters and the longitude characteristic parameters.
  • the latitude characteristic parameters include characteristic parameters calculated from the latitude dimension, that is, the characteristic parameters calculated using the latitude data, and the latitude characteristic parameters include latitude characteristic values;
  • the longitude characteristic parameters include characteristic parameters calculated from the longitude dimension, that is, the characteristic parameters calculated using the longitude data, and the longitude characteristic parameters include longitude characteristic values.
  • the institution code platform can determine that the payment access of the order to be paid is successful and send the payment access result to the payment platform.
  • the payment platform can process the payment for the order to be paid based on the institution account bound to the institution code. Specifically, it can deduct money from the institution account bound to the institution code based on the order amount of the order to be paid.
  • the following takes the application of another payment processing method provided in this embodiment in a business trip scenario as an example to explain the payment processing method provided in this embodiment.
  • the payment processing method is further described in FIG. 5 , and the payment processing method applied to the business travel scenario specifically includes the following steps.
  • Step S502 obtaining the order to be paid and payment location information submitted after the scanning device configured in the merchant store scans the organization code displayed on the member terminal of the organization member.
  • the order is submitted based on the institution code and institution payment channel displayed on the institution code page.
  • Step S504 Generate a payment access request for the order to be paid that carries the payment location information and send it to the institution code platform.
  • Step S506 If the payment access result sent by the institution code platform is received, deduction processing is performed from the institution account bound to the institution code based on the order amount of the order to be paid.
  • a payment access result is generated when the payment location information matches the travel area in the travel application of the institution member and the location distance is within a preset distance range for institutional payment at a merchant store; the location distance is calculated based on the payment location information and the location information of the merchant store.
  • An embodiment of a payment processing device provided in this specification is as follows: In the above-mentioned embodiment, a payment processing method is provided, and correspondingly, a payment processing device is also provided, which is described below in conjunction with the accompanying drawings.
  • FIG. 6 there is shown a schematic diagram of an embodiment of a payment processing device provided in this embodiment.
  • the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above.
  • the device embodiment described below is only illustrative.
  • This embodiment provides a payment processing device, which runs on an institution code platform, and includes: a request acquisition module 602, which is configured to acquire a payment access request of an order to be paid of an institution member sent by a payment platform; the payment access request carries payment location information; the order to be paid is submitted based on the institution code of the institution to which the institution member belongs; a distance calculation module 604, which is configured to calculate the location distance according to the payment location information and the location information of the merchant store corresponding to the order to be paid in response to the payment access request;
  • the distance judgment module 606 is configured to judge whether the location distance is within the preset distance range for institutional payment at the merchant store; if so, run the result sending module 608, and the result sending module 608 is configured to determine that the payment access of the order to be paid is successful and send the payment access result to the payment platform, so as to process the payment of the order to be paid based on the institutional account bound to the institutional code.
  • Another payment processing device embodiment provided in this specification is as follows: In the above embodiment, another payment processing method is provided, and correspondingly, another payment processing device is also provided, which is described below in conjunction with the accompanying drawings.
  • FIG. 7 there is shown a schematic diagram of an embodiment of a payment processing device provided in this embodiment.
  • the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above.
  • the device embodiment described below is only illustrative.
  • This embodiment provides a payment processing device, which runs on a payment platform, and the device includes: an information acquisition module 702, which is configured to obtain the pending payment orders and payment location information of institutional members; the pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong; a request sending module 704, which is configured to generate a payment access request for the pending payment order carrying the payment location information and send it to the institutional code platform; a payment processing module 706, which is configured to, if a payment access result sent by the institutional code platform is received, perform payment processing on the pending payment order based on the institutional account bound to the institutional code; wherein the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store; the location distance is calculated based on the payment location information and the location information of the merchant store.
  • an information acquisition module 702 which is configured to obtain the pending payment orders and payment location information of institutional members; the pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong
  • FIG. 8 is a structural schematic diagram of a payment processing device provided in one or more embodiments of this specification.
  • a payment processing device provided in this embodiment includes: As shown in FIG8, the payment processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and the memory 802 may store one or more storage applications or data. Among them, the memory 802 may be a short-term storage or a persistent storage.
  • the application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the payment processing device.
  • the processor 801 may be configured to communicate with the memory 802 and execute a series of computer executable instructions in the memory 802 on the payment processing device.
  • the payment processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input/output interfaces 805, one or more keyboards 806, etc.
  • the 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 payment processing device, and the one or more programs are configured to be executed by one or more processors and include computer executable instructions for performing the following: obtaining the mechanism sent by the payment platform a payment access request for a member's order to be paid; the payment access request carries payment location information; the order to be paid is submitted based on the institution code of the institution to which the institutional member belongs; in response to the payment access request, calculating the location distance based on the payment location information and the location information of the merchant store corresponding to the order to be paid; determining whether the location distance is within a preset distance range for institutional payment at the merchant store; if so, determining that the payment access of the order to be paid is successful and sending the payment access result to the payment platform, so as to process the payment of the order to be paid based on the
  • FIG. 9 is a structural schematic diagram of a payment processing device provided in one or more embodiments of this specification.
  • a payment processing device includes: As shown in FIG. 9, the payment processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 901 and memory 902, and the memory 902 may store one or more storage applications or data. Among them, the memory 902 may be a short-term storage or a persistent storage.
  • the application stored in the memory 902 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the payment processing device.
  • the processor 901 may be configured to communicate with the memory 902 and execute a series of computer executable instructions in the memory 902 on the payment processing device.
  • the payment processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input/output interfaces 905, one or more keyboards 906, etc.
  • a 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 in the 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 the pending payment orders and payment location information of institutional members; the pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong; generating a payment access request for the pending payment order carrying the payment location information and sending it to the institutional code platform; if the payment access result sent by the institutional code platform is received, performing payment processing on the pending payment order based on the institutional account bound to the institutional code; wherein the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store; the location distance is calculated based on the payment location information and the location information of the merchant store.
  • An embodiment of a storage medium provided in this specification is as follows: Corresponding to the payment processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium provided in this embodiment is used to store computer-executable instructions, which implement the following process when executed by a processor: obtaining a payment access request for an order to be paid of an institutional member sent by a payment platform; the payment access request carries payment location information; the order to be paid is submitted based on the institutional code of the institution to which the institutional member belongs; in response to the payment access request, calculating the location distance based on the payment location information and the location information of the merchant store corresponding to the order to be paid; determining whether the location distance is within a preset distance range for institutional payment at the merchant store; if so, determining that payment access of the order to be paid is successful and sending a payment access result to the payment platform, so as to process payment for the order to be paid based on the institutional account bound to the institutional code.
  • Another storage medium embodiment provided in this specification is as follows: Corresponding to the other payment processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another storage medium.
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and the computer-executable instructions implement the following process when executed by the processor: obtaining the pending payment orders and payment location information of the institutional members; the pending payment orders are submitted based on the institutional code of the institution to which the institutional members belong; generating a payment access request for the pending payment order carrying the payment location information and sending it to the institutional code platform; if the payment access result sent by the institutional code platform is received, the payment processing of the pending payment order is performed based on the institutional account bound to the institutional code; wherein the payment access result is generated when the location distance is within a preset distance range for institutional payment at a merchant store; the location distance is calculated based on the payment location information and the location information of the merchant store.
  • a hardware improvement for example, improvements to the circuit structure of diodes, transistors, switches, etc.
  • a software improvement improvement of the method flow.
  • PLD programmable logic device
  • FPGA field programmable gate array
  • 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 CHDL
  • JHDL Java Hardware Description Language
  • Lava Lava
  • Lola MyHDL
  • PALASM RHDL
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer readable medium storing a computer readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory.
  • a computer readable program code e.g., software or firmware
  • the controller may be implemented in the form of a logic gate, a switch, an application specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the means for implementing various functions included therein may also be considered as a structure within the hardware component. Or even, the means for implementing various functions may be considered as both a software module for implementing the method and a structure within the hardware component.
  • 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 smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
  • the above device is described by dividing it into various units according to its functions.
  • the functions of each unit can be implemented in the same or multiple software and/or hardware.
  • one or more embodiments of this specification may be provided as a method, system or computer program product. Therefore, 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. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • 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 work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured 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 into a computer or other programmable data processing device so that A series of operational steps are performed on a programming 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 flows of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • 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 memory (flash RAM). Memory is an example of a computer-readable medium.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information.
  • Information can be computer readable instructions, data structures, program modules or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, 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 temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
  • One or more embodiments of the present 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, etc. that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network.
  • program modules may be located in local and remote computer storage media, including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

提供了一种支付处理方法及装置，其中，所述支付处理方法包括：在获取到支付平台发送的机构成员的待支付订单的支付准入请求后，根据支付位置信息和待支付订单对应的商家门店的位置信息计算位置距离，并在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下，确定待支付订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码绑定的机构账户对待支付订单进行支付处理。

Description

支付处理方法及装置 技术领域
本文件涉及数据处理技术领域，尤其涉及一种支付处理方法及装置。
背景技术
随着计算机以及互联网的发展，越来越多的用户逐渐采用线上支付的方式对商品或者服务进行支付，在线上支付越来越普及的情况下，机构的机构成员也通过线上支付的方式对生成的待支付订单进行支付，而机构向机构成员提供多种支付场景，比如餐饮支付场景，出行支付场景，机构成员按照机构的要求在商家门店进行支付，在此过程中，如何更好地管理机构成员在商家门店的订单支付成为各方关注的重点。
发明内容
本说明书一个或多个实施例提供了一种支付处理方法，应用于机构码平台，所述方法包括：获取支付平台发送的机构成员的待支付订单的支付准入请求。所述支付准入请求中携带支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离。判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书一个或多个实施例提供了另一种支付处理方法，应用于支付平台，所述方法包括：获取机构成员的待支付订单和支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送。若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成。所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本说明书一个或多个实施例提供了一种支付处理装置，运行于机构码平台，所述装置包括：请求获取模块，被配置为获取支付平台发送的机构成员的待支付订单的支付准入请求。所述支付准入请求中携带支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。距离计算模块，被配置为响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离。距离判断模块，被配置为判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，运行结果发送模块，所述结果发送模块，被配置为确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书一个或多个实施例提供了另一种支付处理装置，运行于支付平台，所述装置包括：信息获取模块，被配置为获取机构成员的待支付订单和支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。请求发送模块，被配置为生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送。支付处理模块，被配置为若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成。所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本说明书一个或多个实施例提供了一种支付处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：获取支付平台发送的机构成员的待支付订单的支付准入请求。所述支付准入请求中携带支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离。判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书一个或多个实施例提供了另一种支付处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：获取机构成员的待支付订单和支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送。若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成。所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本说明书一个或多个实施例提供了一种存储介质，用于存储计算机可执行指令，所述计算机可 执行指令在被处理器执行时实现以下流程：获取支付平台发送的机构成员的待支付订单的支付准入请求。所述支付准入请求中携带支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离。判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书一个或多个实施例提供了另一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：获取机构成员的待支付订单和支付位置信息。所述待支付订单基于所述机构成员所属机构的机构码提交。生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送。若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成。所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
附图说明
为了更清楚地说明本说明书一个或多个实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的一种支付处理方法实施环境的示意图。
图2为本说明书一个或多个实施例提供的一种支付处理方法处理流程图。
图3为本说明书一个或多个实施例提供的一种应用于差旅场景的支付处理方法处理流程图。
图4为本说明书一个或多个实施例提供的另一种支付处理方法处理流程图。
图5为本说明书一个或多个实施例提供的另一种应用于差旅场景的支付处理方法处理流程图。
图6为本说明书一个或多个实施例提供的一种支付处理装置实施例的示意图。
图7为本说明书一个或多个实施例提供的另一种支付处理装置实施例的示意图。
图8为本说明书一个或多个实施例提供的一种支付处理设备的结构示意图。
图9为本说明书一个或多个实施例提供的另一种支付处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
参照图1，本说明书一个或多个实施例提供的支付处理方法实施环境的示意图。
本说明书一个或多个实施例提供的支付处理方法，可适用于订单支付这一实施环境，该实施环境至少包括机构码平台的机构码服务器101，或者，至少包括支付平台的支付服务器102。
此外，该实施环境还可包括机构成员的成员终端103，成员终端103可配置机构码的客户端，该客户端的具体形式可以是应用程序、应用程序内的子程序、应用程序内的服务模块或者网页程序。
其中，机构码服务器101可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是云计算平台中的一个或者多个云服务器，用于进行支付准入处理，结合实际支付准入处理场景来看，可根据时间周期内提交的支付准入请求的请求数量的量级来确定服务器的部署数目和部署方式，比如在请求数量较少的情况下，可部署一台或者多台服务器；再比如，在请求数量达到一定量级的情况下，部署由若干台服务器组成的服务器集群。
支付服务器102可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是云计算平台中的一个或者多个云服务器，用于进行支付处理。
成员终端103可以是手机、个人电脑、平板电脑、电子书阅读器、基于VR(Virtual Reality，虚拟现实技术)进行信息交互的设备、车载终端、IoT设备、穿戴式智能设备、膝上型便携计算机和台式计算机等等，成员终端103可以安装有应用程序或者浏览器。
该实施环境中，在基于成员终端103展示的机构成员所属机构的机构码向支付服务器102提交待支付订单后，支付服务器102可向机构码服务器101发送待支付订单的支付准入请求，机构码服务器101接收到支付准入请求后，从支付位置信息各待支付订单对应的商家门店的位置信息出发，计算位置距离，并在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下，向支付服务器102发送支付准入结果，以在支付服务器基于机构码对待支付订单进行支付处理。
本说明书提供的一种支付处理方法的一个或者多个实施例如下：本实施例提供的支付处理方法， 在获取到支付平台发送的机构成员的待支付订单的支付准入请求后，从支付位置信息和待支付订单对应的商家门店的位置信息出发，计算位置距离，并在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下，确定待支付订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码对待支付订单进行支付处理，以此，通过位置距离的核验有效避免机构成员在机构未指定的商家门店进行机构支付的情况发生，进而减少商家门店或者机构的资金损失，提升机构支付的安全性。
参照图2，本实施例提供的支付处理方法，具体包括步骤S202至步骤S208。
步骤S202，获取支付平台发送的机构成员的待支付订单的支付准入请求。
本实施例中的机构，包括企业、事业单位、社会团体等各种形式的组织，此外，机构不仅包括本级组织，还包括机构的内部组织，比如企业部门或者分部。所述机构成员包括机构工作人员以及相关人员。本实施例可应用于机构码平台。所述支付平台，包括对待支付订单进行支付的平台。所述机构码平台包括提供机构码相关服务的平台。
可选的，所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交。所述机构码，是指机构为机构成员的支付等所设置的标识码，该机构码能够唯一标识机构，机构码的存在形式可以是二维码、条形码、声音码等标识码，机构成员可通过该机构码实现机构支付。此外，所述机构码也可用于开票、报销等处理，还可用于标识机构成员在机构的成员身份，比如将机构码用作企业员工的数字工牌，企业员工可以机构码为凭证领取企业发放的福利和补贴。
所述待支付订单，包括等待进行支付的订单；所述待支付订单可以是待支付商品订单，也可以是待支付服务订单，比如待支付美容订单、待支付培训课程订单等。可选的，所述待支付订单，在所述商家门店配置的扫码设备扫描所述机构码后提交。
所述支付位置信息，包括基于机构码提交待支付订单时机构成员的位置信息，比如机构成员通过展码在某个商家门店提交待支付订单，则机构成员的位置信息即为支付位置信息。可选的，所述支付位置信息从所述待支付订单中读取获得，或者，所述支付位置信息在通过定时任务检测获得的支付位置信息集合中筛选获得；比如在支付位置信息集合中筛选检测时间跨度满足预设条件的位置信息作为所述支付位置信息；其中，所述检测时间跨度包括检测位置信息时的检测时间至筛选时间的时间跨度，所述预设条件包括检测时间跨度为最小的条件。
实际应用中，一种情况下，商家门店可通过配置的扫码设备扫描机构成员的成员终端展示的机构码后向支付平台提交待支付订单，另一种情况下，机构成员的成员终端可通过扫描商家门店的商家标识码基于机构码向支付平台提交待支付订单，为了提升机构支付的有效性，避免机构成员在机构未关联的商家门店进行机构支付造成机构的资金损失，支付平台获取到机构成员的待支付订单后，支付平台可向机构码平台发送请求，以用于核验通过机构支付对待支付订单是否能进行支付，其中，该请求即为支付准入请求，即通过机构支付对待支付订单进行支付的支付准入核验请求，以此提升机构支付的安全性。
具体实施时，支付平台获取机构成员的待支付订单和支付位置信息，生成携带支付位置信息的针对待支付订单的支付准入请求并向机构码平台发送，机构码平台可获取支付平台发送的机构成员的待支付订单的支付准入请求。
在实际的应用过程中，机构为了提升机构成员的工作积极性，可通过关联商家门店实现机构成员在商家门店的机构支付，可选的，所述机构关联有机构成员进行机构支付的至少一个商家门店；可选的，所述至少一个商家门店，通过如下方式与所述机构进行关联：获取所述机构通过所述机构码平台的网络地址对应的网页提交的对商家门店集合的访问指令；基于所述访问指令向所述机构下发所述商家门店集合，以基于所述机构对所述商家门店集合中所述至少一个商家门店的选择指令，将所述至少一个商家门店与所述机构进行关联。
其中，所述商家门店集合是指由一个商家门店或者多个商家门店组成的门店集合；所述商家门店集合包括与机构码平台关联的门店集合。所述机构支付，包括基于机构支付渠道在商家门店进行支付的方式，在支付的过程中，机构成员通过在成员终端展示机构码在商家门店进行机构支付；所述机构支付还可包括因公付。
具体实施时，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，为了提升机构支付的安全性和有效性，可在检测到机构成员提交机构码的展码指令的提交时间处于机构成员进行机构支付的时间取值范围内的情况下，向机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的机构码和机构支付渠道提交待支付订单；本实施例提供的第一种可选实施方式中，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，还执行如下操作：检测所述机构成员提交所述机构码的展码指令的提交时间；判断所述提交时间是否处于 所述机构成员进行机构支付的时间取值范围内；若是，向所述机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的所述机构码和所述机构支付渠道提交所述待支付订单，若否，不作处理即可。
其中，所述时间取值范围，包括机构向机构成员设置的进行机构支付的时间取值范围，比如机构向机构成员设置的进行机构支付的时间取值范围为16:00至20:00。所述机构支付渠道包括基于机构绑定的机构账户对待支付订单进行支付的渠道；具体的，可基于机构码页面展示的机构码和机构支付渠道提交待支付订单，以在支付平台接收到待支付订单的支付准入结果后基于机构支付渠道绑定的机构账户进行待支付订单的支付处理。
此外，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，还可执行如下操作：若待支付订单对应的商家门店处于机构关联的至少一个商家门店中，判断待支付订单的提交时间是否处于机构成员进行机构支付的时间取值范围内，若是，将所述待支付订单进行因公付标记，若否，不作处理即可；相应的，在获取支付平台发送的机构成员的待支付订单的支付准入请求的过程中，可执行如下操作：获取支付平台发送的基于机构成员的待支付订单的因公付标记提交的待支付订单的支付准入请求。
实际应用中，机构成员可能有在差旅地区进行机构支付的需求，为了提升机构成员在差旅地区的差旅体验，避免机构成员进行机构支付的无效性，造成机构成员的时间等成本的浪费，本实施例提供的第二种可选实施方式中，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，还执行如下操作：基于所述机构成员的差旅地区查询与所述机构关联的至少一个商家门店；根据所述至少一个商家门店向所述机构成员进行推荐处理，以在所述至少一个商家门店中选择所述商家门店提交所述待支付订单。
其中，所述差旅地区包括机构成员进行差旅的地理区域，即机构成员出差的地区。所述差旅地区可以是一个城市，也可以是城市中的一个区或者县，还可以是更小的地址单位。
具体的，查询机构关联的在机构成员的差旅地区的至少一个商家门店，根据至少一个商家门店向机构成员进行推荐处理，以在至少一个商家门店中选择所述商家门店提交待支付订单。
具体实施时，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，为了减少基于支付位置信息与商家门店的位置信息计算位置距离的计算次数，可先对待支付订单中记录的商家门店的收款标识进行核验，具体可判断待支付订单中商家门店的收款标识与所述机构关联的所述商家门店的收款标识是否一致，若是，执行下述步骤S204；本实施例提供的一种可选实施方式中，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，还执行如下操作：从所述待支付订单中读取所述商家门店的收款标识；判断所述收款标识与所述机构关联的所述商家门店的收款标识是否一致；若是，执行下述步骤S204，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或者不作处理即可。
其中，所述商家门店的收款标识包括表征商家门店进行收款的标识，比如收款账号。需要说明的是，本实施例中的收款标识还可被替换为商家门店的门店名称和/或商家门店的门店地址，此外，收款标识也可被替换为其他类型的信息。
实际应用中，机构成员存在出差需求，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，为了减少位置距离的计算频次，减少计算量，可在支付位置信息与机构成员的差旅申请中的差旅地区匹配的情况下，进行位置距离的计算；本实施例提供的另一种可选实施方式中，在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，还执行如下操作：判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区匹配；若是，执行下述步骤S204，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或不作处理即可。
例如，支付位置信息为a1市b1区，差旅申请中的差旅地区为a2市b2区，判断a1市b1区与a2市b2区是否一致，若是，执行下述步骤S204，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或者不作处理即可。
本实施例提供的一种可选实施方式中，在上述判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区是否匹配执行之后的执行结果为否的情况下，执行如下操作：向所述机构成员下发差旅申请模板，并获取所述机构成员通过所述差旅申请模板提交的目标差旅申请；若所述支付位置信息与所述目标差旅申请中的差旅地区匹配，执行下述步骤S204；若所述支付位置信息与所述目标差旅申请中的差旅地区不匹配，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或不作处理即可。
此外，在上述判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区是否匹配执行之后的执行结果为否的情况下，还可执行如下操作：对机构成员的信用值进行更新处理，以基于更新后的信用值更新机构成员进行机构支付的地理区域或者更新机构成员进行机构支付的资金额度 或者更新机构成员进行机构支付的商家门店类型。
步骤S204，响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离。
上述获取支付平台发送的机构成员的待支付订单的支付准入请求，本步骤中，响应于所述支付准入请求，借助支付位置信息和待支付订单对应的商家门店的位置信息计算位置距离。
本实施例所述支付位置信息，包括基于机构码提交待支付订单时机构成员所处的位置信息。可选的，所述支付位置信息包括支付位置经度和/或支付位置纬度。所述位置信息包括位置经度和/或位置纬度。
可选的，所述商家门店的位置信息，采用下述至少一种方式获得：基于所述机构码平台的网络地址对应的网页录入，通过商家子程序录入，通过调用所述机构码平台的数据接口传入。
所述位置距离，包括支付位置信息对应的支付位置与商家门店的位置信息对应的商家位置之间的距离。
具体的，可采用前端方式获得商家门店的位置信息，即通过商家子程序录入商家门店的位置信息，此外，也可采用后端方式获得商家门店的位置信息，即基于机构码平台的网络地址对应的网页录入商家门店的位置信息或者通过调用机构码平台的数据接口传入商家门店的位置信息。
具体实施时，为了提升位置距离的精准度和有效性，可从经度和纬度两个角度综合来计算位置距离，本实施例提供的一种可选实施方式中，在根据支付位置信息和待支付订单对应的商家门店的位置信息计算位置距离的过程中，执行如下操作：基于所述支付位置信息中的支付位置纬度和所述位置信息中的位置纬度，计算纬度特征参数，以及基于所述支付位置信息中的支付位置经度和所述位置信息中的位置经度计算经度特征参数；根据所述纬度特征参数和所述经度特征参数计算所述位置距离。
其中，所述纬度特征参数，包括从纬度维度计算获得的特征参数，即利用纬度数据计算获得的特征参数，所述纬度特征参数包括纬度特征值；所述经度特征参数包括从经度维度计算获得的特征参数，即利用经度数据计算获得的特征参数，所述经度特征参数包括经度特征值。
步骤S206，判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内。
本步骤中，判断位置距离是否处于在商家门店进行机构支付的预设距离范围内，若是，执行下述步骤S208，若否，确定待支付订单的支付准入失败，并向支付平台返回支付准入失败结果或者不作处理即可。
可选的，所述预设距离范围包括商家门店进行机构支付的距离范围，比如预设距离范围为20m。可选的，所述预设距离范围，基于所述商家门店的门店特征数据确定；可选的，所述门店特征数据，包括下述至少一项：门店面积、门店热度、所述商家门店所处地理区域。所述门店面积、门店热度可与商家门店的预设距离范围具有正比关系，所述商家门店所处地理区域可包括商家门店所处地理区域的人流量，人流量也可与商家门店的预设距离范围具有正比关系。
本实施例提供的一种可选实施方式中，若所述判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内执行之后的执行结果为否，执行如下操作：确定所述待支付订单的支付准入失败，并向所述支付平台返回支付准入失败结果。
此外，在判断位置距离是否处于在商家门店进行机构支付的预设距离范围内执行之后的执行结果为否的情况下，还可执行如下操作：对所述机构成员的支付准入失败次数进行更新，并基于更新后的支付准入失败次数调整所述机构成员在机构的资金额度或者基于更新后的支付准入失败次数调整所述机构成员进行机构支付的商家门店数目或者基于更新后的支付准入失败次数调整机构成员进行机构支付的商家门店类型或者基于更新后的支付准入失败次数调整机构成员进行机构支付的地理区域。
步骤S208，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
上述判断所述位置距离是否处于在商家门店进行机构支付的预设距离范围内，本步骤中，若是，确定待支付订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码绑定的机构账户对待支付订单进行支付处理，若否，确定待支付订单的支付准入失败，并向支付平台返回支付准入失败结果或者不作处理即可；相应的，支付平台若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理，若接收到所述机构码平台返回的支付准入失败结果，向所述机构成员下发支付准入失败提醒。
本实施例所述支付准入成功包括对待支付订单进行机构支付的准入成功；所述支付准入结果包括对待支付订单进行机构支付的准入结果；所述支付准入失败结果包括对待支付订单进行机构支付的准入失败结果。
具体实施时，机构码平台确定待支付订单的支付准入成功并向支付平台发送支付准入结果，支付平台基于机构码绑定的机构账户对待支付订单进行支付处理，具体可基于待支付订单的订单金额从机构码绑定的机构账户进行扣款处理。
需要补充的是，实际应用中，可能存在机构的机构成员和目标机构成员同时去出差的情况，并且出差地区等信息相同，为了进一步提升机构支付的安全性和有效性，在步骤S202执行之前，可获取机构的所述机构成员提交的差旅申请与目标机构成员提交的目标差旅申请，在差旅申请与目标差旅申请的相似度大于预设相似度阈值的情况下，将目标机构成员关联至所述机构成员；在步骤S206执行之后，还可执行如下操作：若是，根据目标机构成员的支付位置信息与目标机构成员的待支付订单对应的商家门店的位置信息计算第二位置距离，在第二位置距离处于在商家门店进行机构支付的预设距离范围内的情况下，确定机构成员的待支付订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码绑定的机构账户对待支付订单进行支付处理。
此外，实际中还可能遇到在预设时间周期内获取到机构的两个以上机构成员的待支付订单，为了提升待支付订单的机构支付的支付效率，在上述获取支付平台发送的机构成员的待支付订单的支付准入请求后，根据所述待支付订单对应的商家门店查询与所述待支付订单匹配的目标订单(具体根据待支付订单对应的商家门店查询与待支付订单对应的商家门店匹配的目标订单)，所述目标订单的提交时间处于所述待支付订单的提交时间之后或者与所述待支付订单的提交时间相同；在第一位置距离处于在待支付订单对应的商家门店进行机构支付的预设距离范围内，且第二位置距离处于在所述商家门店进行机构支付的预设距离范围内的情况下，确定待支付订单和目标订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码绑定的机构账户对待支付订单和目标订单进行合并支付处理。
除此之外，为了提升商家门店的使用体验，还可执行如下操作：获取目标商家门店提交的所述机构成员所属机构的权限撤销请求；基于所述权限撤销请求撤销所述机构的机构成员在目标商家门店进行机构支付的支付权限；可选的，所述权限撤销请求基于权限撤销入口提交；所述权限撤销入口在检测到所述机构在目标商家门店的支付准入失败次数超过次数阈值的情况下向所述目标商家门店开放。
下述以本实施例提供的一种支付处理方法在差旅场景的应用为例，对本实施例提供的支付处理方法进行进一步说明，参见图3，应用于差旅场景的支付处理方法，具体包括步骤S302至步骤S318。
步骤S302，检测机构成员提交机构码的展码指令的提交时间。
步骤S304，判断提交时间是否处于机构成员进行机构支付的时间取值范围内；若是，执行步骤S306至步骤S310；若否，不作处理即可。
步骤S306，向机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的机构码和机构支付渠道提交待支付订单。
步骤S308，获取支付平台发送的机构成员的待支付订单的支付准入请求。
可选的，支付准入请求中携带支付位置信息。
步骤S310，响应于支付准入请求，判断支付位置信息是否与机构成员的差旅申请中的差旅地区匹配；若是，执行下述步骤S312至步骤S316；若否，确定待支付订单的支付准入失败并向支付平台返回支付准入失败结果或者不作处理即可。
步骤S312，基于支付位置信息中的支付位置纬度和待支付订单对应的商家门店的位置信息中的位置纬度计算纬度特征值，以及基于支付位置信息中的支付位置经度和位置信息中的位置经度计算经度特征值。
步骤S314，根据纬度特征值和经度特征值计算位置距离。
步骤S316，判断位置距离是否处于在商家门店进行机构支付的预设距离范围内；若是，执行步骤S318；若否，确定待支付订单的支付准入失败并向支付平台返回支付准入失败结果或者不作处理即可。
步骤S318，确定待支付订单的支付准入成功并向支付平台发送支付准入结果，以基于机构码绑定的机构账户对待支付订单进行支付处理。
本说明书提供的另一种支付处理方法的一个或者多个实施例如下：参照图4，本实施例提供的支付处理方法，具体包括步骤S402至步骤S406。
本实施例提供的支付处理方法，可应用于支付平台，上述实施例提供的支付处理方法，可应用于机构码平台，本实施例提供的可应用于支付平台的支付处理方法，在执行过程中与上述实施例提供的可应用于机构码平台的支付处理方法相互配合，阅读本实施例可参照上述实施例的相关内容，相应的，阅读上述实施例也可参照本实施例的相应内容。
步骤S402，获取机构成员的待支付订单和支付位置信息。
本实施例中的机构，包括企业、事业单位、社会团体等各种形式的组织，此外，机构不仅包括本级组织，还包括机构的内部组织，比如企业部门或者分部。所述机构成员包括机构工作人员以及相关人员。本实施例可应用于机构码平台。所述支付平台，包括对待支付订单进行支付的平台。所述机构码平台包括提供机构码相关服务的平台。可选的，所述待支付订单基于所述机构成员所属机构的机构码提交。
可选的，所述机构码，是指机构为机构成员的支付等所设置的标识码，该机构码能够唯一标识机构，机构码的存在形式可以是二维码、条形码、声音码等标识码，机构成员可通过该机构码实现机构支付。此外，所述机构码也可用于开票、报销等处理，还可用于标识机构成员在机构的成员身份，比如将机构码用作企业员工的数字工牌，企业员工可以机构码为凭证领取企业发放的福利和补贴。
所述待支付订单，包括等待进行支付的订单；所述待支付订单可以是待支付商品订单，也可以是待支付服务订单，比如待支付美容订单、待支付培训课程订单等。可选的，所述待支付订单，在所述商家门店配置的扫码设备扫描所述机构码后提交。
所述支付位置信息，包括基于机构码提交待支付订单时机构成员的位置信息，比如机构成员通过展码在某个商家门店提交待支付订单，则机构成员的位置信息即为支付位置信息。可选的，所述支付位置信息从所述待支付订单中读取获得，或者，所述支付位置信息在通过定时任务检测获得的支付位置信息集合中筛选获得；比如在支付位置信息集合中筛选检测时间跨度满足预设条件的位置信息作为所述支付位置信息；其中，所述检测时间跨度包括检测位置信息时的检测时间至筛选时间的时间跨度，所述预设条件包括检测时间跨度为最小的条件。
具体实施时，支付平台获取机构成员的待支付订单和支付位置信息，具体支付平台可通过定时任务获取多个支付位置信息，在多个支付位置信息中筛选目标支付位置信息作为机构成员的支付位置信息，比如选取时间最近的目标支付位置信息作为机构成员的支付位置信息；此外，待支付订单中还可记录支付位置信息，通过待支付订单获取机构成员的支付位置信息。
步骤S404，生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送。
上述支付平台获取机构成员的待支付订单和支付位置信息，本步骤中，生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送，机构码平台获取支付平台发送的机构成员的待支付订单的支付准入请求，响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离，判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内，若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或者不作处理即可。
实际应用中，一种情况下，商家门店可通过配置的扫码设备扫描机构成员的成员终端展示的机构码后向支付平台提交待支付订单，另一种情况下，机构成员的成员终端可通过扫描商家门店的商家标识码基于机构码向支付平台提交待支付订单，为了提升机构支付的有效性，避免机构成员在机构未关联的商家门店进行机构支付造成机构的资金损失，支付平台获取到机构成员的待支付订单后，支付平台可向机构码平台发送请求，以用于核验通过机构支付对待支付订单是否能进行支付，其中，该请求即为支付准入请求，即通过机构支付对待支付订单进行支付的支付准入核验请求，以此提升机构支付的安全性。
在实际的应用过程中，机构为了提升机构成员的工作积极性，可通过关联商家门店实现机构成员在商家门店的支付机构，可选的，所述机构关联有机构成员进行机构支付的至少一个商家门店；可选的，所述至少一个商家门店，通过如下方式与所述机构进行关联：获取所述机构通过所述机构码平台的网络地址对应的网页提交的对商家门店集合的访问指令；基于所述访问指令向所述机构下发所述商家门店集合，以基于所述机构对所述商家门店集合中所述至少一个商家门店的选择指令，将所述至少一个商家门店与所述机构进行关联。
其中，所述商家门店集合是指由一个商家门店或者多个商家门店组成的门店集合；所述商家门店集合包括与机构码平台关联的门店集合。所述机构支付，包括基于机构支付渠道在商家门店进行支付的方式，在支付的过程中，机构成员通过在成员终端展示机构码在商家门店进行机构支付；所述机构支付还可包括因公付。
具体实施时，在机构码平台获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，为了提升机构支付的安全性和有效性，可在检测到机构成员提交机构码的展码指令的提交时间处于机构成员进行机构支付的时间取值范围内的情况下，向机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的机构码和机构支付渠道提交待支付订单；具体的，机 构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，还可执行如下操作：检测所述机构成员提交所述机构码的展码指令的提交时间；判断所述提交时间是否处于所述机构成员进行机构支付的时间取值范围内；若是，向所述机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的所述机构码和所述机构支付渠道提交所述待支付订单，若否，不作处理即可。
其中，所述时间取值范围，包括机构向机构成员设置的进行机构支付的时间取值范围，比如机构向机构成员设置的进行机构支付的时间取值范围为16:00至20:00。所述机构支付渠道包括基于机构绑定的机构账户对待支付订单进行支付的渠道；具体的，可基于机构码页面展示的机构码和机构支付渠道提交待支付订单，以在支付平台接收到待支付订单的支付准入结果后基于机构支付渠道绑定的机构账户进行待支付订单的支付处理。
此外，机构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，还可执行如下操作：若待支付订单对应的商家门店处于机构关联的至少一个商家门店中，判断待支付订单的提交时间是否处于机构成员进行机构支付的时间取值范围内，若是，将所述待支付订单进行因公付标记，若否，不作处理即可；相应的，在获取支付平台发送的机构成员的待支付订单的支付准入请求的过程中，可执行如下操作：获取支付平台发送的基于机构成员的待支付订单的因公付标记提交的待支付订单的支付准入请求。
实际应用中，机构成员可能存在在差旅地区进行机构支付的需求，为了提升机构成员在差旅地区的差旅体验，避免机构成员进行机构支付的无效性，造成机构成员的时间等成本的浪费，机构码平台还可在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之前，执行如下操作：基于所述机构成员的差旅地区查询与所述机构关联的至少一个商家门店；根据所述至少一个商家门店向所述机构成员进行推荐处理，以在所述至少一个商家门店中选择所述商家门店提交所述待支付订单。
其中，所述差旅地区包括机构成员进行差旅的地理区域，即机构成员出差的地区。
具体的，机构码平台可查询机构关联的在机构成员的差旅地区的至少一个商家门店，根据至少一个商家门店向机构成员进行推荐处理，以在至少一个商家门店中选择所述商家门店提交待支付订单。
具体实施时，机构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，为了减少基于支付位置信息与商家门店的位置信息计算位置距离的计算次数，可先对待支付订单中记录的商家门店的收款标识进行核验，具体可判断待支付订单中商家门店的收款标识与所述机构关联的所述商家门店的收款标识是否一致，若是，执行响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤；具体机构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，还可执行如下操作：从所述待支付订单中读取所述商家门店的收款标识；判断所述收款标识与所述机构关联的所述商家门店的收款标识是否一致；若是，执行响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或者不作处理即可。
其中，所述商家门店的收款标识包括表征商家门店进行收款的标识，比如收款账号。需要说明的是，本实施例中的收款标识还可被替换为商家门店的门店名称和/或商家门店的门店地址，此外，收款标识也可被替换为其他类型的信息。
实际应用中，机构成员存在出差需求，机构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，为了减少位置距离的计算频次，减少计算量，可在支付位置信息与机构成员的差旅申请中的差旅地区匹配的情况下，进行位置距离的计算；机构码平台在获取支付平台发送的机构成员的待支付订单的支付准入请求执行之后，还可执行如下操作：判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区匹配；若是，执行响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或不作处理即可。
例如，支付位置信息为a1市b1区，差旅申请中的差旅地区为a2市b2区，机构码平台判断a1市b1区与a2市b2区是否一致，若是，执行下述步骤S204，若否，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或者不作处理即可。
机构码平台在上述判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区是否匹配执行之后的执行结果为否的情况下，可执行如下操作：向所述机构成员下发差旅申请模板，并获取所述机构成员通过所述差旅申请模板提交的目标差旅申请；若所述支付位置信息与所述目标差旅申请中的差旅地区匹配，执行响应于所述支付准入请求，根据所述支付位置信息和所述待支付订 单对应的商家门店的位置信息计算位置距离步骤；若所述支付位置信息与所述目标差旅申请中的差旅地区不匹配，确定所述待支付订单的支付准入失败并向所述支付平台返回支付准入失败结果或不作处理即可。
上述机构码平台获取支付平台发送的机构成员的待支付订单的支付准入请求，在此之后，机构码平台响应于所述支付准入请求，借助支付位置信息和待支付订单对应的商家门店的位置信息计算位置距离。
本实施例所述支付位置信息，包括机构成员通过展示机构码提交待支付订单时所处的位置信息，比如机构成员通过展码在某个商家门店提交待支付订单，则该商家门店的位置信息即为机构成员所处的位置信息。可选的，所述支付位置信息包括支付位置经度和/或支付位置纬度。所述位置信息包括位置经度和/或位置纬度。
可选的，所述商家门店的位置信息，采用下述至少一种方式获得：基于所述机构码平台的网络地址对应的网页录入，通过商家子程序录入，通过调用所述机构码平台的数据接口传入。
所述位置距离，包括支付位置信息对应的支付位置与商家门店的位置信息对应的商家位置之间的距离。
上述机构码平台借助支付位置信息和待支付订单对应的商家门店的位置信息计算位置距离，在此之后，机构码平台判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内，若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理，若否，确定待支付订单的支付准入失败，并向支付平台返回支付准入失败结果或者不作处理即可。
可选的，所述预设距离范围包括商家门店进行机构支付的距离范围，比如预设距离范围为20m。可选的，所述预设距离范围，基于所述商家门店的门店特征数据确定；可选的，所述门店特征数据，包括下述至少一项：门店面积、门店热度、所述商家门店所处地理区域。所述门店面积、门店热度可与商家门店的预设距离范围具有正比关系，所述商家门店所处地理区域可包括商家门店所处地理区域的人流量，人流量也可与商家门店的预设距离范围具有正比关系。
具体实施时，机构码平台在判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内执行之后的执行结果为否的情况下，可执行如下操作：确定所述待支付订单的支付准入失败，并向所述支付平台返回支付准入失败结果。
上述机构码平台判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内，若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理，若否，确定待支付订单的支付准入失败，并向支付平台返回支付准入失败结果或者不作处理即可。
本实施例所述支付准入成功包括对待支付订单进行机构支付的准入成功；所述支付准入结果包括对待支付订单进行机构支付的准入结果；所述支付准入失败结果包括对待支付订单进行机构支付的准入失败结果。
步骤S406，若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
支付平台若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理，若接收到所述机构码平台返回的支付准入失败结果，向所述机构成员下发支付准入失败提醒。
可选的，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本实施例提供的一种可选实施方式中，为了提升位置距离的精准度和有效性，可从经度和纬度两个角度综合来计算位置距离，所述位置距离，采用如下方式计算获得：基于所述支付位置信息中的支付位置纬度和所述位置信息中的位置纬度，计算纬度特征参数，以及基于所述支付位置信息中的支付位置经度和所述位置信息中的位置经度计算经度特征参数；根据所述纬度特征参数和所述经度特征参数计算所述位置距离。
其中，所述纬度特征参数，包括从纬度维度计算获得的特征参数，即利用纬度数据计算获得的特征参数，所述纬度特征参数包括纬度特征值；所述经度特征参数包括从经度维度计算获得的特征参数，即利用经度数据计算获得的特征参数，所述经度特征参数包括经度特征值。
具体实施时，机构码平台可确定待支付订单的支付准入成功并向支付平台发送支付准入结果，支付平台可基于机构码绑定的机构账户对待支付订单进行支付处理，具体可基于待支付订单的订单金额从机构码绑定的机构账户进行扣款处理。
下述以本实施例提供的另一种支付处理方法在差旅场景的应用为例，对本实施例提供的支付处 理方法进行进一步说明，参见图5，应用于差旅场景的支付处理方法，具体包括如下步骤。
步骤S502，获取商家门店配置的扫码设备扫描机构成员的成员终端展示的机构码后提交的待支付订单和支付位置信息。
可选的，待支付订单，在机构成员提交机构码的展码指令的提交时间处于机构成员进行机构支付的时间取值范围内的情况下，基于机构码页面展示的机构码和机构支付渠道提交。
步骤S504，生成携带支付位置信息的针对待支付订单的支付准入请求并向机构码平台发送。
步骤S506，若接收到机构码平台发送的支付准入结果，基于待支付订单的订单金额从机构码绑定的机构账户进行扣款处理。
可选的，支付准入结果，在支付位置信息与机构成员的差旅申请中的差旅地区匹配且位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于支付位置信息与商家门店的位置信息计算获得。
本说明书提供的一种支付处理装置实施例如下：在上述的实施例中，提供了一种支付处理方法，与之相对应的，还提供了一种支付处理装置，下面结合附图进行说明。
参照图6，其示出了本实施例提供的一种支付处理装置实施例的示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种支付处理装置，运行于机构码平台，所述装置包括：请求获取模块602，被配置为获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；距离计算模块604，被配置为响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；
距离判断模块606，被配置为判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，运行结果发送模块608，所述结果发送模块608，被配置为确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书提供的另一种支付处理装置实施例如下：在上述的实施例中，提供了另一种支付处理方法，与之相对应的，还提供了另一种支付处理装置，下面结合附图进行说明。
参照图7，其示出了本实施例提供的一种支付处理装置实施例的示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种支付处理装置，运行于支付平台，所述装置包括：信息获取模块702，被配置为获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；请求发送模块704，被配置为生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；支付处理模块706，被配置为若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本说明书提供的一种支付处理设备实施例如下：对应上述描述的一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种支付处理设备，该支付处理设备用于执行上述提供的一种支付处理方法，图8为本说明书一个或多个实施例提供的一种支付处理设备的结构示意图。
本实施例提供的一种支付处理设备，包括：如图8所示，支付处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器801和存储器802，存储器802中可以存储有一个或一个以上存储应用程序或数据。其中，存储器802可以是短暂存储或持久存储。存储在存储器802的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括支付处理设备中的一系列计算机可执行指令。更进一步地，处理器801可以设置为与存储器802通信，在支付处理设备上执行存储器802中的一系列计算机可执行指令。支付处理设备还可以包括一个或一个以上电源803，一个或一个以上有线或无线网络接口804，一个或一个以上输入/输出接口805，一个或一个以上键盘806等。
在一个具体的实施例中，支付处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对支付处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取支付平台发送的机构 成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
本说明书提供的另一种支付处理设备实施例如下：对应上述描述的另一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供另一种支付处理设备，该支付处理设备用于执行上述提供的一种支付处理方法，图9为本说明书一个或多个实施例提供的一种支付处理设备的结构示意图。
本实施例提供的一种支付处理设备，包括：如图9所示，支付处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器901和存储器902，存储器902中可以存储有一个或一个以上存储应用程序或数据。其中，存储器902可以是短暂存储或持久存储。存储在存储器902的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括支付处理设备中的一系列计算机可执行指令。更进一步地，处理器901可以设置为与存储器902通信，在支付处理设备上执行存储器902中的一系列计算机可执行指令。支付处理设备还可以包括一个或一个以上电源903，一个或一个以上有线或无线网络接口904，一个或一个以上输入/输出接口905，一个或一个以上键盘906等。
在一个具体的实施例中，支付处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对支付处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
需要说明的是，本说明书中关于一种存储介质的实施例与本说明书中关于一种支付处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的另一种存储介质实施例如下：对应上述描述的另一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供另一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
需要说明的是，本说明书中关于另一种存储介质的实施例与本说明书中关于另一种支付处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或者相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处，比如装置实施例、设备实施例和存储介质实施例，三者均相似于方法实施例，所以描述地比较简单，阅读装置实施例、设备实施例和 存储介质实施例中的相关内容请参照方法实施例的部分说明即可。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在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 (22)

  1. 一种支付处理方法，应用于机构码平台，所述方法包括：
    获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；
    判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；
    若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
  2. 根据权利要求1所述的支付处理方法，其中，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离，包括：
    基于所述支付位置信息中的支付位置纬度和所述位置信息中的位置纬度，计算纬度特征参数，以及基于所述支付位置信息中的支付位置经度和所述位置信息中的位置经度计算经度特征参数；
    根据所述纬度特征参数和所述经度特征参数计算所述位置距离。
  3. 根据权利要求1所述的支付处理方法，其中，获取所述支付平台发送的机构成员的待支付订单的支付准入请求步骤执行之前，还包括：
    检测所述机构成员提交所述机构码的展码指令的提交时间；
    判断所述提交时间是否处于所述机构成员进行机构支付的时间取值范围内；
    若是，向所述机构成员发送包含机构支付渠道的渠道标识的机构码页面，以基于机构码页面展示的所述机构码和所述机构支付渠道提交所述待支付订单。
  4. 根据权利要求1所述的支付处理方法，其中，获取所述支付平台发送的机构成员的待支付订单的支付准入请求步骤执行之后，且所述响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤执行之前，还包括：
    从所述待支付订单中读取所述商家门店的收款标识；
    判断所述收款标识与所述机构关联的所述商家门店的收款标识是否一致；
    若是，执行所述响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤。
  5. 根据权利要求1所述的支付处理方法，其中，所述商家门店的位置信息，采用下述至少一种方式获得：
    基于所述机构码平台的网络地址对应的网页录入，通过商家子程序录入，通过调用所述机构码平台的数据接口传入。
  6. 根据权利要求1所述的支付处理方法，其中，所述机构关联有机构成员进行机构支付的至少一个商家门店；
    其中，所述至少一个商家门店，通过如下方式与所述机构进行关联：
    获取所述机构通过所述机构码平台的网络地址对应的网页提交的对商家门店集合的访问指令；
    基于所述访问指令向所述机构下发所述商家门店集合，以基于所述机构对所述商家门店集合中所述至少一个商家门店的选择指令，将所述至少一个商家门店与所述机构进行关联。
  7. 根据权利要求1所述的支付处理方法，其中，获取所述支付平台发送的机构成员的待支付订单的支付准入请求步骤执行之前，还包括：
    基于所述机构成员的差旅地区查询与所述机构关联的至少一个商家门店；
    根据所述至少一个商家门店向所述机构成员进行推荐处理，以在所述至少一个商家门店中选择所述商家门店提交所述待支付订单。
  8. 根据权利要求1所述的支付处理方法，其中，获取所述支付平台发送的机构成员的待支付订单的支付准入请求步骤执行之后，且所述响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤执行之前，还包括：
    判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区匹配；
    若是，执行所述响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤。
  9. 根据权利要求8所述的支付处理方法，其中，若所述判断所述支付位置信息是否与所述机构成员的差旅申请中的差旅地区匹配步骤执行之后的执行结果为否，执行如下操作：
    向所述机构成员下发差旅申请模板，并获取所述机构成员通过所述差旅申请模板提交的目标差旅申请；
    若所述支付位置信息与所述目标差旅申请中的差旅地区匹配，执行所述响应于所述支付准入请 求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离步骤。
  10. 根据权利要求1所述的支付处理方法，其中，所述预设距离范围，基于所述商家门店的门店特征数据确定；
    其中，所述门店特征数据，包括下述至少一项：门店面积、门店热度、所述商家门店所处地理区域。
  11. 根据权利要求1所述的支付处理方法，其中，若所述判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内步骤执行之后的执行结果为否，执行如下操作：
    确定所述待支付订单的支付准入失败，并向所述支付平台返回支付准入失败结果。
  12. 一种支付处理方法，应用于支付平台，所述方法包括：
    获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；
    若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；
    其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
  13. 根据权利要求12所述的支付处理方法，其中，所述位置距离，采用如下方式计算获得：
    基于所述支付位置信息中的支付位置纬度和所述位置信息中的位置纬度，计算纬度特征参数，以及基于所述支付位置信息中的支付位置经度和所述位置信息中的位置经度计算经度特征参数；
    根据所述纬度特征参数和所述经度特征参数计算所述位置距离。
  14. 根据权利要求12所述的支付处理方法，其中，所述预设距离范围，基于所述商家门店的门店特征数据确定；
    其中，所述门店特征数据，包括下述至少一项：门店面积、门店热度、所述商家门店所处地理区域。
  15. 根据权利要求12所述的支付处理方法，其中，生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送步骤执行之后，还包括：
    若接收到所述机构码平台返回的支付准入失败结果，向所述机构成员下发支付准入失败提醒。
  16. 根据权利要求12所述的支付处理方法，其中，所述待支付订单，在所述商家门店配置的扫码设备扫描所述机构码后提交。
  17. 一种支付处理装置，运行于机构码平台，所述装置包括：
    请求获取模块，被配置为获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    距离计算模块，被配置为响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；
    距离判断模块，被配置为判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；
    若是，运行结果发送模块，所述结果发送模块，被配置为确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
  18. 一种支付处理装置，运行于支付平台，所述装置包括：
    信息获取模块，被配置为获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    请求发送模块，被配置为生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；
    支付处理模块，被配置为若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
  19. 一种支付处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；
    判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；
    若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
  20. 一种支付处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；
    若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；
    其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
  21. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
    获取支付平台发送的机构成员的待支付订单的支付准入请求；所述支付准入请求中携带支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    响应于所述支付准入请求，根据所述支付位置信息和所述待支付订单对应的商家门店的位置信息计算位置距离；
    判断所述位置距离是否处于在所述商家门店进行机构支付的预设距离范围内；
    若是，确定所述待支付订单的支付准入成功并向所述支付平台发送支付准入结果，以基于所述机构码绑定的机构账户对所述待支付订单进行支付处理。
  22. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
    获取机构成员的待支付订单和支付位置信息；所述待支付订单基于所述机构成员所属机构的机构码提交；
    生成携带所述支付位置信息的针对所述待支付订单的支付准入请求并向机构码平台发送；
    若接收到所述机构码平台发送的支付准入结果，基于所述机构码绑定的机构账户对所述待支付订单进行支付处理；
    其中，所述支付准入结果，在位置距离处于在商家门店进行机构支付的预设距离范围内的情况下生成；所述位置距离，基于所述支付位置信息与所述商家门店的位置信息计算获得。
PCT/CN2023/139397 2023-03-31 2023-12-18 支付处理方法及装置 Ceased WO2024198539A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310345567.1A CN116384983A (zh) 2023-03-31 2023-03-31 支付处理方法及装置
CN202310345567.1 2023-03-31

Publications (1)

Publication Number Publication Date
WO2024198539A1 true WO2024198539A1 (zh) 2024-10-03

Family

ID=86968852

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/139397 Ceased WO2024198539A1 (zh) 2023-03-31 2023-12-18 支付处理方法及装置

Country Status (2)

Country Link
CN (1) CN116384983A (zh)
WO (1) WO2024198539A1 (zh)

Families Citing this family (2)

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

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105654283A (zh) * 2015-04-20 2016-06-08 宇龙计算机通信科技(深圳)有限公司 一种安全支付方法及装置
CN106548339A (zh) * 2016-10-09 2017-03-29 努比亚技术有限公司 一种安全支付方法及设备
US20180276648A1 (en) * 2014-10-23 2018-09-27 Shunnosuke SHIMANO Payment system
CN108647957A (zh) * 2018-05-11 2018-10-12 维沃移动通信有限公司 一种支付方法、装置及移动终端
CN109615367A (zh) * 2018-12-03 2019-04-12 北京三快在线科技有限公司 用于支付的方法、装置、存储介质及电子设备
US20200051052A1 (en) * 2016-10-26 2020-02-13 Rakuten, Inc. Payment system, payment method, and program
CN111178868A (zh) * 2019-06-20 2020-05-19 腾讯科技（深圳）有限公司 一种支付验证的方法及相关装置
CN111475072A (zh) * 2020-04-08 2020-07-31 维沃移动通信有限公司 一种支付信息显示方法及电子设备
CN114186992A (zh) * 2021-12-13 2022-03-15 深圳市智百威科技发展有限公司 一种扫码支付结算系统及方法
CN116384983A (zh) * 2023-03-31 2023-07-04 支付宝(杭州)信息技术有限公司 支付处理方法及装置

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180276648A1 (en) * 2014-10-23 2018-09-27 Shunnosuke SHIMANO Payment system
CN105654283A (zh) * 2015-04-20 2016-06-08 宇龙计算机通信科技(深圳)有限公司 一种安全支付方法及装置
CN106548339A (zh) * 2016-10-09 2017-03-29 努比亚技术有限公司 一种安全支付方法及设备
US20200051052A1 (en) * 2016-10-26 2020-02-13 Rakuten, Inc. Payment system, payment method, and program
CN108647957A (zh) * 2018-05-11 2018-10-12 维沃移动通信有限公司 一种支付方法、装置及移动终端
CN109615367A (zh) * 2018-12-03 2019-04-12 北京三快在线科技有限公司 用于支付的方法、装置、存储介质及电子设备
CN111178868A (zh) * 2019-06-20 2020-05-19 腾讯科技（深圳）有限公司 一种支付验证的方法及相关装置
CN111475072A (zh) * 2020-04-08 2020-07-31 维沃移动通信有限公司 一种支付信息显示方法及电子设备
CN114186992A (zh) * 2021-12-13 2022-03-15 深圳市智百威科技发展有限公司 一种扫码支付结算系统及方法
CN116384983A (zh) * 2023-03-31 2023-07-04 支付宝(杭州)信息技术有限公司 支付处理方法及装置

Also Published As

Publication number Publication date
CN116384983A (zh) 2023-07-04

Similar Documents

Publication Publication Date Title
CN113222723B (zh) 票据处理方法、装置、设备和存储介质
WO2021259147A1 (zh) 基于区块链的资源转移方法、装置及设备
CN110503435A (zh) 基于区块链的交易预警方法、装置及设备
WO2024198539A1 (zh) 支付处理方法及装置
WO2022247968A1 (zh) 数据处理
CN113419794B (zh) 支付处理方法及装置
US20240257268A1 (en) Blockchain-based data processing
US20250117770A1 (en) Credit-based transaction processing method and apparatus
WO2024046121A1 (zh) 服务处理的方法及装置
US20250117862A1 (en) Receipt processing method and apparatus for transaction bill
CN115983845A (zh) 基于用户身份的支付方法及装置
CN114548963A (zh) 支付交互处理方法及装置
CN116485391A (zh) 支付推荐处理方法及装置
WO2025180482A1 (zh) 订单支付处理
WO2025185577A1 (zh) 资金处理
WO2025060761A1 (zh) 订单结算处理
WO2025256377A1 (zh) 转账处理
WO2025180479A1 (zh) 资源额度处理
CN110321752B (zh) 离线图形码的校验方法及装置
CN116645196A (zh) 信用预测处理方法及装置
WO2024152846A1 (zh) 支付处理方法及装置
CN110046954B (zh) 一种卡片申请的处理方法、装置、设备及系统
CN115238305A (zh) 一种营销信息发送方法、装置及设备
CN115099925A (zh) 一种基于区块链的风险评估方法、装置及设备
CN116823278A (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: 23930104

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23930104

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 23930104

Country of ref document: EP

Kind code of ref document: A1