WO2020088075A1 - 用于确定支付通道的方法和装置 - Google Patents

用于确定支付通道的方法和装置 Download PDF

Info

Publication number
WO2020088075A1
WO2020088075A1 PCT/CN2019/103579 CN2019103579W WO2020088075A1 WO 2020088075 A1 WO2020088075 A1 WO 2020088075A1 CN 2019103579 W CN2019103579 W CN 2019103579W WO 2020088075 A1 WO2020088075 A1 WO 2020088075A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
channel
candidate
verification code
historical
Prior art date
Application number
PCT/CN2019/103579
Other languages
English (en)
French (fr)
Inventor
肖雄
Original Assignee
京东数字科技控股有限公司
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 京东数字科技控股有限公司 filed Critical 京东数字科技控股有限公司
Publication of WO2020088075A1 publication Critical patent/WO2020088075A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems

Definitions

  • the embodiments of the present application relate to the field of computer technology, specifically to the field of Internet technology, and in particular to a method and device for determining a payment channel.
  • One payment platform can be connected to multiple payment channels, such as direct bank connection channels, UnionPay online (supporting multiple bank quick transactions), and quick money quick (supporting multiple bank quick transactions).
  • the payment channel provided by a payment platform to a front-end application is usually manually set.
  • the monitoring staff discovers that a payment channel has a problem, it usually informs the relevant staff member, and the relevant staff member switches the payment request corresponding to the payment channel to another payment channel.
  • An embodiment of the present application proposes a method and device for determining a payment channel.
  • an embodiment of the present application provides a method for determining a payment channel, the method includes: receiving a payment request, where the payment request includes information about a service type corresponding to the payment request; based on a preset channel corresponding to the service type The determination rule determines at least one candidate payment channel; obtaining the current channel quality parameters corresponding to each candidate payment channel; wherein, the current channel quality parameter of each candidate payment channel and the historical payment verification code acquisition success rate corresponding to the candidate payment channel and The historical payment success rate for payment based on the verification code is positively correlated; the target payment channel is determined from at least one candidate payment channel according to the current channel quality parameters.
  • the current channel quality parameter of each candidate payment channel is generated based on the steps of: assigning pre-set weights to the historical payment verification code acquisition success rate and historical payment success rate corresponding to the candidate payment channel; The historical payment verification code acquisition success rate and the weighted historical payment success rate generate the current channel quality parameter of the candidate channel.
  • the current channel quality parameter of each candidate payment channel is also positively correlated with the historical payment verification code acquisition time-consuming parameter and the historical payment time-consuming parameter; and the historical payment verification code acquisition success rate corresponding to the candidate payment channel And the historical payment success rate is assigned with pre-set weights respectively, including: assigning pre-set weights to the historical payment verification code acquisition time-consuming parameter and historical payment time-consuming parameter; and obtaining the success rate and weighting based on the weighted historical payment verification code
  • the current historical payment success rate generates the current channel quality parameter of the candidate payment channel, which also includes: obtaining the time-consuming parameter according to the weighted historical payment verification code and the weighted historical payment time-consuming parameter to generate the current channel of the candidate payment channel Quality parameter; wherein, the time-consuming parameter for obtaining the payment verification code is inversely related to the length of time used to obtain the payment verification code; the time-consuming parameter for payment is negatively related to the length of time used for payment using the verification code.
  • the current quality parameter of each candidate payment channel is also positively correlated with the historical payment verification code acquisition time rate corresponding to the candidate payment channel and the historical payment time rate of payment based on the verification code; and corresponding to the candidate payment channel
  • the historical payment verification code acquisition success rate and historical payment success rate are respectively assigned with pre-set weights, which also include: assigning pre-set weights to the historical payment verification code acquisition timely rate and historical payment timely rate; and according to the weighted historical payment verification
  • the code acquisition success rate and the weighted historical payment success rate generate the current channel quality parameters of the candidate payment channel, and also include: generating the payment channel ’s time channel based on the weighted historical payment verification code acquisition time rate and the weighted historical payment time rate Current channel quality parameters.
  • the current quality parameter of each candidate payment channel is also positively related to the concurrent number of payment verification code acquisition requests supported by the candidate payment channel, and the concurrent number of payment requests based on the verification code; and the candidate payment
  • the historical payment verification code acquisition success rate and historical payment success rate corresponding to the channel are respectively assigned with preset weights, and also include: assigning preset weights to the concurrent number of payment verification code acquisition requests and the concurrent number of payment requests based on the verification code ;
  • the current channel quality parameter of the candidate payment channel is generated according to the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate, and also includes: obtaining the concurrent number of requests and weighted according to the weighted payment verification code The number of concurrent requests for payment based on the verification code generates the current channel quality parameter of the candidate payment channel.
  • the method before determining the target payment channel from the at least one candidate payment channel according to the current channel quality parameter, the method further includes: obtaining fee information corresponding to each candidate payment channel; and according to the current channel quality parameter from at least The determination of the target payment channel in one candidate payment channel includes: determining the target payment channel from at least one candidate payment channel according to the current quality parameter and the fee indicated by the fee information of each candidate payment channel.
  • the payment request includes payment amount information; and before determining the target payment channel from at least one candidate payment channel according to the current channel quality parameter, the method further includes: obtaining payment limit information corresponding to each candidate payment channel ; And determining the target payment channel from at least one candidate payment channel according to the current channel quality parameters, including: the payment limit indicated by the current quality parameter, the payment limit information of each candidate payment channel, and the payment amount indicated by the payment amount information, The target payment channel is determined from at least one candidate payment channel.
  • the method further includes: in response to the acquired current channel quality parameter of any candidate payment channel being less than a preset threshold, generating alarm information.
  • an embodiment of the present application provides an apparatus for determining a payment channel
  • the apparatus includes: a receiving unit configured to receive a payment request, where the payment request includes information about a service type corresponding to the payment request; a first determination The unit is configured to determine at least one candidate payment channel based on a preset channel determination rule corresponding to the service type; the obtaining unit is configured to obtain current channel quality parameters corresponding to each candidate payment channel; wherein, each candidate payment channel The current channel quality parameter is positively related to the historical payment verification code acquisition success rate corresponding to the candidate payment channel and the historical payment success rate of payment based on the verification code; the second determination unit is configured to select from at least one candidate according to the current channel quality parameter The target payment channel is determined in the payment channel.
  • the apparatus further includes a quality parameter generating unit configured to: assign a pre-set weight to the historical payment verification code acquisition success rate and the historical payment success rate corresponding to the candidate payment channel respectively; The weighted historical payment verification code acquisition success rate and the weighted historical payment success rate generate the current channel quality parameter of the candidate channel.
  • the current channel quality parameter of each candidate payment channel is also inversely related to the historical payment verification code acquisition time-consuming parameter and historical payment time-consuming parameter; and the quality parameter generation unit is further configured to: verify the historical payment verification code Obtain time-consuming parameters and historical payment time-consuming parameters and assign preset weights; obtain time-consuming parameters and weighted historical payment time-consuming parameters according to the weighted historical payment verification code to generate the current channel quality parameter of the candidate payment channel; wherein, The time-consuming parameter for obtaining a payment verification code is negatively related to the time taken to obtain the payment verification code; the time-consuming parameter for payment is negatively related to the time used for payment using the verification code.
  • the current quality parameter of each candidate payment channel is also positively related to the historical payment verification code acquisition time rate corresponding to the candidate payment channel and the historical payment time rate of payment based on the verification code; and the quality parameter generation unit is further Configured to: assign a pre-set weight to the historical payment verification code acquisition time rate and historical payment timely rate; and generate the current channel of the candidate payment channel according to the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate
  • the quality parameter also includes: obtaining the timely rate according to the weighted historical payment verification code and generating the current channel quality parameter of the payment channel according to the weighted historical payment timely rate.
  • the current quality parameter of the candidate payment channel is also positively related to the concurrent number of payment verification code acquisition requests supported by the candidate payment channel, and the concurrent number of payment requests based on the verification code; and the quality parameter generation unit is further configured Cheng: Assign the pre-set weights to the number of concurrent requests for payment verification code acquisition and the number of concurrent requests for payment based on the verification code; obtain the number of concurrent requests based on the weighted payment verification code and the weighted payment according to the verification code The requested concurrent quantity generates the current channel quality parameter of the candidate payment channel.
  • the obtaining unit before the second determining unit determines the target payment channel from the at least one candidate payment channel according to the current channel quality parameter, is further configured to: obtain fee information corresponding to each candidate payment channel; and The second determining unit is further configured to determine the target payment channel from the at least one candidate payment channel according to the current quality parameter and the fee indicated by the fee information of each candidate payment channel.
  • the above payment request includes payment amount information; and before the second determination unit determines the target payment channel from the at least one candidate payment channel according to the current channel quality parameter, the obtaining unit is further configured to: obtain each candidate payment Payment limit information corresponding to the channels respectively; and the second determining unit is further configured to: from at least one candidate according to the current quality parameter, the payment limit indicated by the payment limit information of each candidate payment channel and the payment amount indicated by the payment amount information The target payment channel is determined in the payment channel.
  • the device further includes an alarm unit configured to generate alarm information in response to the acquired current channel quality parameter of any candidate payment channel being less than a preset threshold.
  • an embodiment of the present application provides an electronic device, the electronic device includes: one or more processors; a storage device, on which one or more programs are stored, when the one or more programs are When executed by one or more processors, the above one or more processors implement the method described in any one of the implementation manners of the first aspect.
  • an embodiment of the present application provides a computer-readable medium on which a computer program is stored, where the computer program is executed by a processor to implement the method described in any one of the implementation manners of the first aspect.
  • the method and device for determining a payment channel provided by an embodiment of the present application, by receiving a payment request, then determining at least one candidate payment channel based on a preset channel determination rule corresponding to the service type in the payment request, and then obtaining each candidate payment
  • the current channel quality parameters corresponding to the channels respectively, and finally the target payment channel is determined from the at least one candidate payment channel according to the current quality parameter.
  • the target payment channel corresponding to the payment request is determined according to the current quality parameters of each candidate payment channel.
  • the payment channel can be automatically switched through the determined target payment channel, which is beneficial to improve payment efficiency and payment success rate.
  • FIG. 1 is an exemplary system architecture diagram in which a method for determining a payment channel according to an embodiment of the present application can be applied;
  • FIG. 2 is a flowchart of an embodiment of a method for determining a payment channel according to the present application
  • FIG. 3 is a schematic diagram of an application scenario of a method for determining a payment channel according to this application;
  • FIG. 4 is a flowchart of still another embodiment of a method for determining a payment channel according to this application.
  • FIG. 5 is a schematic structural diagram of an embodiment of an apparatus for determining a payment channel according to the present application.
  • FIG. 6 is a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • FIG. 1 shows an exemplary system architecture 100 in which the method for determining a payment channel according to an embodiment of the present application can be applied.
  • the system architecture 100 may include terminal devices 101, 102, 103 and a first server 105, a second server 106, 107, 108, and a network 104, 109.
  • the network 104 is used as a medium for providing a communication link between the terminal devices 101, 102, 103 and the first server 105.
  • the network 109 is used as a medium for providing a communication link between the first server 105 and the second server 106, 107, 108.
  • the networks 104, 109 may include various connection types, such as wired, wireless communication links, or fiber optic cables.
  • the user may use the terminal devices 101, 102, 103 to interact with the first server 105 through the network 104 to receive or send messages, and so on.
  • Various client applications may be installed on the terminal devices 101, 102, and 103, such as payment applications, shopping applications, search applications, and instant messaging tools.
  • the terminal devices 101, 102, and 103 may be hardware or software.
  • the terminal devices 101, 102, and 103 may be various electronic devices that have a display screen and support web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and so on.
  • the terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services) or as a single software or software module. There is no specific limit here.
  • the first server 105 can provide various services, such as receiving payment requests sent by the terminal devices 101, 102, and 103; determining the payment channel corresponding to the payment request and performing information interaction with the second server where the payment channel is located to complete the payment operation.
  • the second server 106, 107, 108 may be a bank server corresponding to the payment channel; the second server 106, 107, 108 may provide various services, such as information exchange with the first server 105 through the network 109 to complete the terminal device 101, 102, 103
  • the payment request sent corresponds to the payment operation.
  • first server 105 and the second server 106, 107, 108 may be hardware or software.
  • first server 105 and the second server 106, 107, 108 are hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server.
  • first server 105 and the second server 106, 107, 108 are software, they can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or can be implemented as a single software or software Module. There is no specific limit here.
  • the method for determining the payment channel provided by the embodiment of the present application is generally executed by the first server 105, and accordingly, the device for determining the payment channel is generally provided in the first server 105.
  • terminal devices, networks, first servers, and second servers in FIG. 1 are only schematic. According to the implementation needs, there can be any number of terminal devices, networks and servers.
  • FIG. 2 shows a flow 200 of one embodiment of a method for determining a payment channel according to the present application.
  • the method for determining the payment channel includes the following steps:
  • Step 201 Receive a payment request.
  • the execution body of the method for determining the payment channel may receive the terminal device (such as the terminal device shown in FIG. 1) and send it through a wired connection or a wireless connection Payment request.
  • the above wireless connection methods may include, but are not limited to, 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods now known or developed in the future .
  • the user can initiate a payment request to the above-mentioned execution subject using the payment application client or browser installed on the terminal.
  • the above payment request may include the service type corresponding to the payment request.
  • the business types here may include, for example, general consumer business, insurance business, fund business, etc.
  • the above payment request may also include information such as payment amount, collection account number, user identification, terminal identification, etc.
  • the above-mentioned executive body can distinguish the payment requests of different users according to the user identification.
  • Step 202 Determine at least one candidate payment channel based on a preset channel determination rule corresponding to the service type.
  • the above-mentioned execution subject may first determine the preset channel determination rule corresponding to the service type, and then based on the preset The channel determination rule determines at least one candidate payment channel.
  • the payment channel may, for example, refer to a specific provider that provides payment acceptance capability or a channel party to which a three-party jumps, and may also be an acquirer or a clearing party.
  • the payment channel may include, for example, a bank fast direct connection channel (each bank fast direct connection channel), UnionPay Online (supports multiple bank fast transactions), fast money quick (supports multiple bank fast transactions), and so on.
  • Each payment channel can correspond to multiple attributes, for example, the payment channel supports the concurrent amount of payment requests, the handling fee corresponding to the payment channel, the payment channel, and the estimated time-consuming payment.
  • Each payment platform can correspond to multiple payment channels.
  • Each payment channel corresponds to a channel identifier.
  • Channel identification is used to distinguish different payment channels.
  • the channel identifier here can be represented by numbers or payments, or by a combination of numbers and payments.
  • Each channel identifier may correspond to a specific payment channel. For example, the channel identifier "01" corresponds to "Beijing Bank of China Express Direct Connect Channel".
  • the service types supported by different payment channels may be different.
  • the above-mentioned execution subject can access a preset comparison table of service type and channel determination rules.
  • the comparison table may be stored locally, or may be stored in other electronic devices that communicate with the execution subject through a wired connection or a wireless connection.
  • the above comparison table may include multiple service types and preset channel determination rules stored in association with each service type.
  • the channel determination rule here can set, for example, a payment time-consuming range, a payment rate range, and the like.
  • the execution subject may match the service type corresponding to the payment request in the comparison table, so as to extract the preset channel determination rule matching the service type corresponding to the payment request in the comparison table. Then, the execution subject may determine at least one candidate payment channel from the multiple payment channels according to the preset channel determination rule.
  • the above preset channel rule sets the payment time-consuming range of the channel to be less than 3 hours, multiple payment channels with an attribute value corresponding to the corresponding payment time-consuming attribute of less than 3 hours may be determined as the first pre-candidate Collection of payment channels; if the above predetermined channel determination rule also sets the payment rate range to be less than 0.3%, multiple payment channels with an attribute value corresponding to the corresponding payment rate attribute less than 0.3% can be determined as the second pre-payment channel Candidate payment channel set. Then, the above-mentioned execution subject may determine at least one candidate payment channel from the first set of pre-candidate payment channels and the second set of pre-candidate payment channels. For example, the intersection of the first set of pre-candidate payment channels and the second set of pre-candidate payment channels may be taken as the candidate payment channel of the above payment request.
  • the above payment request may further include a payment channel specified by the user in advance.
  • the main body may determine the payment channel specified by the user in advance as a candidate payment channel corresponding to the payment request.
  • Step 203 Obtain current channel quality parameters corresponding to each candidate payment channel.
  • the executing body of the method for determining the payment channel may obtain the current quality parameters corresponding to each candidate payment channel through various methods.
  • the current channel quality parameter of each candidate payment channel is positively related to the historical payment verification code acquisition success rate corresponding to the candidate payment channel and the historical payment success rate of payment based on the verification code.
  • the above historical payment verification code acquisition success rate and historical payment success rate refer to obtaining the result of each payment verification code for multiple payment requests within a preset time period from the current time point and paying according to the verification code
  • the payment results of are analyzed separately, and the success rate of obtaining the payment verification code and the payment success rate within the preset time period are obtained.
  • the 100 payment requests 80 payment requests successfully obtained the payment verification code through the payment channel, and 70 payment requests successfully paid through the verification code; then
  • the historical payment verification code acquisition success rate is 0.8; the historical payment success rate is 0.7.
  • the preset time period may be 1 second, 2 seconds, etc.
  • the preset time period may be set according to a specific application scenario, and is not limited here.
  • the above-mentioned execution agent may assign the pre-set weights to the historical payment verification code acquisition success rate and the historical payment success rate corresponding to the payment channel respectively, according to the weighted historical payment verification code The success rate and the weighted historical payment success rate are obtained to generate the current channel quality parameter of the candidate channel.
  • the above-mentioned executive body may use the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate cumulative sum as the current channel quality parameter.
  • the current channel quality parameter Q of the candidate payment channel described above can be expressed by the following formula:
  • A1 is the historical payment success code success rate corresponding to the candidate payment channel
  • A2 is the historical payment success rate corresponding to the candidate payment channel
  • W1 and W2 are the preset weights corresponding to A1 and A2, respectively.
  • A1 is greater than zero and less than or equal to 1
  • A2 is greater than zero and less than or equal to 1.
  • W1 and W2 are greater than zero.
  • the current quality parameter of each candidate payment channel is also positively related to the number of concurrent requests for payment verification code acquisition supported by the candidate payment channel, and the number of concurrent requests for payment based on the verification code Related.
  • the above-mentioned assigning pre-set weights to the historical payment verification code acquisition success rate and the historical payment success rate respectively also includes: allocating a pre-determined number of concurrent payment verification code acquisition requests and a concurrent payment request The set weights; and the current channel quality parameters of the payment channel are generated based on the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate, and also include: the number of concurrent requests to obtain the request based on the weighted payment verification code and The weighted concurrent number of payment requests according to the verification code generates the current channel quality parameter of the payment channel.
  • the current quality parameter of each candidate payment channel is equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment success rate, and the weighted payment verification supported by the candidate payment channel The cumulative number of the concurrent number of code acquisition requests and the weighted concurrent number of requests for payment based on the verification code supported by the candidate payment channel.
  • the current quality parameter Q of a candidate payment channel can be further expressed by the following formula:
  • N1 is the concurrent number of requests for payment verification codes supported by the candidate payment channel
  • N2 is the concurrent number of requests for payment based on the verification code supported by the candidate payment channel
  • Y1 and Y2 are the corresponding advances of N1 and N2 respectively Set weights.
  • N1 and N2 are positive integers. Y1, Y2 are greater than zero.
  • the current quality parameter of each candidate payment channel also corresponds to the historical payment verification code acquisition time rate corresponding to the candidate payment channel and the historical payment time rate of payment based on the verification code is positive Relevant; and the above assigns pre-set weights to the historical payment verification code acquisition success rate and historical payment success rate respectively, including: assigning pre-set weights to the historical payment verification code acquisition timely rate and historical payment timely rate; and The historical payment verification code acquisition success rate and the weighted historical payment success rate generate the current channel quality parameters of the payment channel, and also include: generating the weighted historical payment verification code acquisition timely rate and the weighted historical payment timely rate to generate the The current channel quality parameters of the payment channel.
  • the current quality parameters of each of the candidate payment channels mentioned above are equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment verification rate, the weighted historical payment verification code acquisition timeliness rate, and Weighted cumulative sum of historical payment and time rate.
  • the calculation method of the payment success time rate can be compared with the calculation method of the payment verification code to obtain the time rate, which will not be repeated here.
  • the current quality parameter Q of a candidate payment channel can be expressed by the following formula:
  • B1 is the historical payment payment code time rate corresponding to the candidate payment channel
  • B2 is the historical payment time rate for payment according to the verification code corresponding to the candidate payment channel
  • X1 and X2 are the preset settings corresponding to B1 and B2 respectively the weight of.
  • B2 and B2 are greater than zero and less than or equal to 1.
  • X1, X2 are greater than zero.
  • the current quality parameter of each candidate payment channel is also positively related to the concurrent number of payment verification code acquisition requests supported by the candidate payment channel, and the concurrent number of payment requests based on the verification code.
  • the above-mentioned assigning pre-set weights to the historical payment verification code acquisition success rate and the historical payment success rate respectively also includes: allocating a pre-determined number of concurrent payment verification code acquisition requests and a concurrent payment request The set weights; and the current channel quality parameters of the payment channel are generated based on the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate, and also include: the number of concurrent requests to obtain the request based on the weighted payment verification code and The weighted concurrent number of payment requests according to the verification code generates the current channel quality parameter of the payment channel.
  • the current quality parameter of each candidate payment channel is equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment verification rate, the weighted historical payment verification code acquisition timeliness rate, The cumulative sum of the weighted historical payment timely rate, the weighted concurrent number of payment verification code acquisition requests supported by the channel, and the weighted concurrent number of payment requests supported by the channel based on the verification code.
  • the current quality parameter Q of the candidate payment channel can be further expressed by the following formula:
  • N1 is the concurrent number of requests for payment verification codes supported by the candidate payment channel
  • N2 is the concurrent number of requests for payment based on the verification code supported by the candidate payment channel
  • Y1 and Y2 are the corresponding advances of N1 and N2 respectively Set weights.
  • Step 204 Determine a target payment channel from at least one candidate payment channel according to the current channel quality parameter.
  • the execution subject may select the candidate payment channel with the highest current channel quality parameter value from the at least one candidate payment channel as the target payment channel.
  • FIG. 3 is a schematic diagram 300 of an application scenario of a method for determining a payment channel according to an embodiment of the present application.
  • the user 301 initiates a payment request through the terminal device 302 (step 303).
  • the payment request includes the service type corresponding to the payment request.
  • the first server 304 determines at least one candidate payment channel corresponding to the payment request 303 based on the preset channel determination rule corresponding to the service type (step 305); then, the first server 304 obtains the current channel quality parameters corresponding to each candidate payment channel (Step 306); after that, the first server 304 determines the target payment channel from the at least one candidate payment channel according to the current channel quality parameter of each candidate payment channel (step 307).
  • the first server 304 calls the above-mentioned target payment channel to complete the payment operation corresponding to the payment request (step 308).
  • the method provided in the above embodiments of the present application receives a payment request, and then determines at least one candidate payment channel based on a preset channel determination rule corresponding to the service type in the payment request, and then obtains the current channel quality corresponding to each candidate payment channel Parameters, and finally determine the target payment channel from the at least one candidate payment channel according to the current quality parameter.
  • the target payment channel corresponding to the payment request is determined according to the current quality parameters of each candidate payment channel.
  • the payment channel can be automatically switched through the determined target payment channel, which is beneficial to improve payment efficiency and payment success rate.
  • FIG. 4 shows a flow 400 of yet another embodiment of a method for determining a payment channel.
  • the process 400 of the method for determining a payment channel includes the following steps:
  • Step 401 Receive a payment request.
  • Step 401 is the same as step 201 in the embodiment shown in FIG. 2 and will not be repeated here.
  • Step 402 Determine at least one candidate payment channel based on a preset channel determination rule corresponding to the service type.
  • Step 402 is the same as step 202 in the embodiment shown in FIG. 2 and will not be repeated here.
  • Step 403 Obtain current channel quality parameters corresponding to each candidate payment channel.
  • the execution body of the method for determining the payment channel may obtain the current quality parameters corresponding to each candidate payment channel through various methods.
  • the current channel quality parameter of each candidate payment channel is positively related to the historical payment verification code acquisition success rate corresponding to the candidate payment channel and the historical payment success rate of payment based on the verification code.
  • the above historical payment verification code acquisition success rate and historical payment success rate refer to the respective payment verification code acquisition results based on multiple payment requests before the current time point and within a preset time period from the current time point and The payment results of the payment based on the verification code are separately counted, and the success rate of obtaining the payment verification code and the payment success rate within the preset time period are obtained.
  • the above-mentioned execution agent may assign a pre-set weight to the historical payment verification code acquisition success rate and the historical payment success rate corresponding to the candidate payment channel respectively, and verify the weighted historical payment verification The code acquisition success rate and the weighted historical payment success rate generate the current channel quality parameter of the candidate channel.
  • the above-mentioned executive body may use the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate cumulative sum as the current channel quality parameter.
  • the current channel quality parameter Q of the above candidate payment channel can be expressed by the following formula:
  • A11 is the historical payment success code success rate corresponding to the candidate payment channel
  • A21 is the historical payment success rate corresponding to the candidate payment channel
  • W12 and W22 are the preset weights corresponding to A11 and A21, respectively. It should be noted that A11, A21, W12, and W22 in the above formula (5) may be the same as the acquisition methods and values of A1, A2, W1, and W2 in the formula (1), respectively.
  • the current channel quality parameter of each candidate payment channel is also positively related to the historical payment verification code acquisition time-consuming parameter and historical payment time-consuming parameter; and the above-mentioned historical payment verification code acquisition success rate and historical payment success rate Distribute the pre-set weights separately, and also include: assign the pre-set weights to the historical payment verification code acquisition time-consuming parameters and historical payment time-consuming parameters; and the above-mentioned weighted historical payment verification code acquisition success rate and weighted historical payment The success rate generates the current channel quality parameter of the payment channel, which also includes: obtaining the time-consuming parameter according to the weighted historical payment verification code and the weighted historical payment time-consuming parameter to generate the current channel quality parameter of the payment channel.
  • the time-consuming parameter for acquiring the payment verification code is negatively related to the time duration for acquiring the payment verification code; the time-consuming payment parameter is negatively related to the time duration for payment using the verification code.
  • the longer the payment verification code acquisition time the smaller the payment verification code acquisition time-consuming parameter; the longer the payment time for payment based on the verification code, the smaller the payment time-consuming parameter.
  • the length of time used to obtain the payment verification code can be determined by the statistical values of the TP50 indicator value, TP90 indicator value, TP99 indicator, and average value of the time used by the payment channel to respond to multiple payment verification code acquisition requests within a preset time period Characterization.
  • the current quality parameter of each candidate payment channel is equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment success rate, the weighted historical payment verification code acquisition time-consuming parameter, and the weighted The cumulative sum of time-consuming parameters of historical payment.
  • the current quality parameter Q of a payment channel can be expressed by the following formula:
  • T1 is the time-consuming parameter for acquiring the historical payment verification code corresponding to the candidate payment channel
  • T2 is the time-consuming parameter for historical payment corresponding to the candidate payment channel according to the verification code
  • the above Z1 and Z2 correspond to the above T1 and T2 respectively Of the preset parameters.
  • the current quality parameter of each candidate payment channel is also positively related to the historical payment verification code acquisition time rate corresponding to the candidate payment channel and the historical payment time rate for payment based on the verification code .
  • the above assigns pre-set weights to the historical payment verification code acquisition success rate and the historical payment success rate respectively, and also includes: assigning pre-set weights to the historical payment verification code acquisition timely rate and historical payment timely rate.
  • the above generates the current channel quality parameter of the payment channel according to the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate, and also includes: obtaining the timely rate and weighted historical payment according to the weighted historical payment verification code
  • the current channel quality parameter of the payment channel is generated in time.
  • the current quality parameters of each of the candidate payment channels mentioned above are equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment verification rate, the weighted historical payment verification code acquisition timeliness rate, and The weighted historical payment timely rate, the weighted historical payment verification code acquisition time-consuming parameter and the weighted historical payment time-consuming parameter cumulative sum.
  • the current quality parameter Q of a payment channel can be expressed by the following formula:
  • B11 is the historical payment payment code time rate corresponding to the candidate payment channel
  • B21 is the historical payment time rate for payment according to the verification code corresponding to the candidate payment channel
  • X11 and X21 are the preset settings corresponding to B11 and B21, respectively the weight of. It should be noted that X11, X21, B11, and B21 in the above formula (6) may be the same as the acquisition methods and values of X1, X2, B1, and B2 in the formula (1), respectively.
  • the current quality parameter of each candidate payment channel is also positively related to the concurrent number of payment verification code acquisition requests supported by the candidate payment channel and the concurrent number of payment requests based on the verification code.
  • the above-mentioned assigning pre-set weights to the historical payment verification code acquisition success rate and the historical payment success rate respectively also includes: allocating a pre-assignment to the concurrent number of payment verification code acquisition requests and the concurrent number of payment requests Set weights.
  • the above-mentioned generation of the current channel quality parameter of the payment channel based on the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate and also includes: obtaining the concurrent number of requests and the weighted after the weighted payment verification code
  • the current channel quality parameter of the payment channel is generated according to the number of concurrent payment requests made by the verification code.
  • the current quality parameters of each of the candidate payment channels mentioned above are equal to the weighted historical payment verification code acquisition success rate, the weighted historical payment verification rate, the weighted historical payment verification code acquisition timeliness rate, and Weighted historical payment timely rate, weighted historical payment verification code acquisition time-consuming parameter and weighted historical payment time-consuming parameter, weighted concurrent number of payment verification code acquisition requests supported by the candidate payment channel, and the candidate payment The cumulative sum of the weighted concurrent number of requests for payment based on the verification code supported by the channel.
  • the current quality parameter Q of a candidate payment channel can be further expressed by the following formula:
  • N11 is the concurrent number of requests for payment verification codes supported by the candidate payment channel
  • N21 is the concurrent number of requests for payment based on the verification code supported by the candidate payment channel
  • Y11 and Y21 are the corresponding advances of N11 and N21 respectively.
  • Set weights It should be noted that, N11, N21, Y11, and Y21 in formula (7) may have the same acquisition method and value of formula (2) in the embodiment shown in FIG. 2.
  • Step 404 Determine a target payment channel from at least one candidate payment channel according to the current channel quality parameter.
  • Step 404 is the same as step 204 in the embodiment shown in FIG. 2 and will not be repeated here.
  • the process 400 of the method for determining a payment channel in this embodiment introduces the time-consuming parameter and historical payment according to the historical payment verification code of the candidate payment channel Time-consuming parameters to determine the current quality parameters of the candidate payment channel. Therefore, the solution described in this embodiment can introduce more parameters to determine the current quality parameters of the candidate payment channel, so that the current quality parameters of the candidate payment channel can be determined from multiple dimensions, so that the current status of the generated candidate payment channel The quality parameters are more accurate. It can further contribute to improving payment efficiency and payment success rate.
  • the channel method may further include: obtaining fee information corresponding to each candidate payment channel; and step 204 of the embodiment shown in FIG. 2 and step 404 of the embodiment shown in FIG. 4 include: according to the current quality of each candidate payment channel The parameter and the fee indicated by the fee information of each candidate payment channel determine the target payment channel from the at least one candidate payment channel.
  • the above payment request includes payment amount information.
  • the method for determining a payment channel further includes: obtaining payment limit information corresponding to each candidate payment channel; and according to the current quality
  • the parameters, the payment limit indicated by the payment limit information of each candidate payment channel and the payment amount indicated by the payment amount information determine the target payment channel from at least one candidate payment channel.
  • Step 204 of the embodiment shown in FIG. 2 and step 404 of the embodiment shown in FIG. 4 include: according to the current quality parameter, the payment limit indicated by the payment limit information of each candidate payment channel and the payment amount indicated by the payment amount information, The target payment channel is determined from at least one candidate payment channel.
  • the payment limit of the candidate payment channel is also considered, so that the payment success rate can be further improved.
  • the method for determining a payment channel in the embodiment shown in FIG. 2 and the embodiment shown in FIG. 4 may further include: responding When the current channel quality parameter of any candidate payment channel obtained is less than a preset threshold, an alarm message is generated.
  • relevant personnel are alerted through the above-mentioned alarm information, and the candidate payment channel indicated by the alarm information has a problem, which may prompt relevant personnel to manually perform the above-mentioned candidate payment channel whose current channel quality parameter is less than a preset threshold Intervention can further improve payment efficiency.
  • the present application provides an embodiment of a device for determining a payment channel, which corresponds to the method embodiment shown in FIG. 2,
  • the device can be specifically applied to various electronic devices.
  • the apparatus 500 for determining a payment channel of this embodiment includes: a receiving unit 501, a first determining unit 502, an acquiring unit 503, and a second determining unit 504.
  • the receiving unit 501 is configured to receive a payment request, where the payment request includes information about the service type corresponding to the payment request;
  • the first determining unit 502 is configured to determine at least one based on a preset channel determination rule corresponding to the service type Candidate payment channels;
  • the obtaining unit 503 is configured to obtain the current channel quality parameters corresponding to each candidate payment channel; wherein, the current channel quality parameters of each candidate payment channel and the historical payment verification code corresponding to the candidate payment channel acquisition success rate And the historical payment success rate of payment according to the verification code is positively correlated;
  • the second determination unit 504 is configured to determine the target payment channel from at least one candidate payment channel according to the current channel quality parameter.
  • step 201, step 202, step 203 and step 204 in the embodiment will not be repeated here.
  • the apparatus 500 for determining a payment channel further includes a quality parameter generation unit (not shown in the figure).
  • the above quality parameter generating unit is configured to: for each candidate payment channel, assign a pre-set weight to the historical payment verification code acquisition success rate and the historical payment success rate corresponding to the candidate payment channel respectively; according to the weighted historical payment verification code The success rate and the weighted historical payment success rate are obtained to generate the current channel quality parameter of the candidate channel.
  • the current channel quality parameter of each candidate payment channel is also positively related to the time-consuming parameter for acquiring the historical payment verification code and the time-consuming parameter for historical payment; and the quality parameter generating unit is further configured Success: assign the pre-set weights to the time-consuming parameters of the historical payment verification code and the time-consuming parameters of historical payment; generate the candidate payment channel based on the weighted historical payment verification code and the time-consuming parameters of the historical payment The current channel quality parameter of; where the payment verification code acquisition time-consuming parameter is negatively correlated with the payment verification code acquisition time duration; the payment time verification parameter is negatively correlated with the verification code for payment duration.
  • the current quality parameter of each candidate payment channel is also positively related to the historical payment verification code acquisition time rate corresponding to the candidate payment channel and the historical payment time rate for payment based on the verification code;
  • the quality parameter generating unit is further configured to: assign a pre-set weight to the historical payment verification code acquisition time rate and historical payment timely rate; and generate the weighted historical payment verification code acquisition success rate and the weighted historical payment success rate generation
  • the current channel quality parameter of the candidate payment channel further includes: generating the current channel quality parameter of the payment channel according to the weighted historical payment verification code acquisition time rate and the weighted historical payment time rate.
  • the current quality parameter of the candidate payment channel is also positively related to the concurrent number of payment verification code acquisition requests supported by the candidate payment channel and the concurrent number of payment requests based on the verification code; and
  • the quality parameter generating unit is further configured to: assign a pre-set weight to the concurrent number of payment verification code acquisition requests and the number of concurrent payment requests based on the verification code; acquire the concurrent number of requests and weighted based on the weighted payment verification code The number of concurrent requests for payment based on the verification code generates the current channel quality parameter of the candidate payment channel.
  • the obtaining unit 503 is further configured to: obtain each candidate payment The fee information corresponding to the channels respectively; and the second determining unit 504 is further configured to determine the target payment channel from the at least one candidate payment channel according to the current quality parameter and the fee indicated by the fee information of each candidate payment channel.
  • the payment request includes payment amount information
  • the obtaining unit 503 further Is configured to: obtain payment limit information corresponding to each candidate payment channel; and the second determination unit 504 is further configured to: according to the current quality parameter, the payment limit indicated by the payment limit information of each candidate payment channel and the payment amount information The indicated payment amount determines the target payment channel from at least one candidate payment channel.
  • the apparatus 500 for determining a payment channel further includes: an alarm unit (not shown in the figure).
  • the alarm unit is configured to generate alarm information in response to the acquired current channel quality parameter of any candidate payment channel being less than a preset threshold.
  • FIG. 6 shows a schematic structural diagram of a computer system 600 suitable for implementing an electronic device according to an embodiment of the present application.
  • the electronic device shown in FIG. 6 is only an example, and should not bring any limitation to the functions and use scope of the embodiments of the present application.
  • the computer system 600 includes a central processing unit (CPU, Central Processing Unit) 601, which can be loaded into random access according to a program stored in a read-only memory (ROM, Read Only Memory) 602 or from the storage section 606
  • the program in the memory (RAM, Random Access) 603 executes various appropriate operations and processes.
  • RAM Random Access
  • various programs and data necessary for the operation of the system 600 are also stored.
  • the CPU 601, ROM 602, and RAM 603 are connected to each other through a bus 604.
  • An input / output (I / O, Input / Output) interface 605 is also connected to the bus 604.
  • the following components are connected to the I / O interface 605: a storage portion 606 including a hard disk and the like; and a communication portion 607 including a network interface card such as a LAN (Local Area Network) card, a modem, and the like.
  • the communication section 607 performs communication processing via a network such as the Internet.
  • the driver 608 is also connected to the I / O interface 605 as needed.
  • the process described above with reference to the flowchart may be implemented as a computer software program.
  • embodiments of the present disclosure include a computer program product that includes a computer program carried on a computer-readable medium, the computer program containing program code for performing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication section 607, and / or installed from the removable medium 609.
  • the central processing unit (CPU) 601 the above-mentioned functions defined in the method of the present application are executed.
  • the computer-readable medium described in this application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples of computer readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable removable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable signal medium may include a data signal that is propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried.
  • This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. .
  • the program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the foregoing.
  • the computer program code for performing the operations of the present application can be written in one or more programming languages or a combination thereof.
  • the programming languages include object-oriented programming languages such as Java, Smalltalk, C ++, and also include the conventional process Programming language-such as "C" language or similar programming language.
  • the program code may be executed entirely on the user's computer, partly on the user's computer, as an independent software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, through an Internet service provider Internet connection).
  • LAN local area network
  • WAN wide area network
  • Internet service provider Internet connection for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of code that contains one or more logic functions Executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks represented in succession may actually be executed in parallel, and they may sometimes be executed in reverse order, depending on the functions involved.
  • each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts can be implemented with dedicated hardware-based systems that perform specified functions or operations Or, it can be realized by a combination of dedicated hardware and computer instructions.
  • the units described in the embodiments of the present application may be implemented in software or hardware.
  • the described unit may also be provided in the processor.
  • a processor includes a receiving unit, a first determining unit, an acquiring unit, and a second determining unit.
  • the names of these units do not constitute a limitation on the unit itself under certain circumstances.
  • the receiving unit may also be described as a “unit that receives a payment request”.
  • the present application also provides a computer-readable medium, which may be included in the device described in the foregoing embodiments; or may exist alone without being assembled into the device.
  • the computer-readable medium carries one or more programs.
  • the device When the one or more programs are executed by the device, the device is caused to: receive a payment request, where the payment request includes information about the service type corresponding to the payment request;
  • the preset channel determination rule corresponding to the type determines at least one candidate payment channel; obtain the current channel quality parameters corresponding to each candidate payment channel; wherein, the current channel quality parameter of each candidate payment channel and the historical payment corresponding to the candidate payment channel
  • the verification code acquisition success rate is positively correlated with the historical payment success rate of payment based on the verification code; the target payment channel is determined from at least one candidate payment channel according to the current channel quality parameter.

Landscapes

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

Abstract

本申请实施例公开了用于确定支付通道的方法和装置。该方法的一具体实施方式包括：接收支付请求，其中支付请求包括支付请求对应的业务类型的信息；基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道；获取各候选支付通道分别对应的当前通道质量参数；根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。从而实现了根据各候选支付通道的当前质量参数确定出与支付请求对应的目标支付通道。进一步地，可以通过所确定的目标支付通道实现支付通道的自动切换，从而有利于提高支付效率和支付成功率。

Description

用于确定支付通道的方法和装置
本专利申请要求于2018年11月02日提交的、申请号为201811300935.6、发明名称为“用于确定支付通道的方法和装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本申请中。
技术领域
本申请实施例涉及计算机技术领域，具体涉及互联网技术领域，尤其涉及用于确定支付通道的方法和装置。
背景技术
一个支付平台可以接入多个支付通道，如银行快捷直联渠道、银联在线(支持多个银行快捷交易)、快钱快捷(支持多个银行快捷交易)。然而，一个支付平台提供给一个前端应用的支付通道通常都是人工进行设定的。当监控人员发现一个支付通道发生问题后，通常通过通知相关工作人员，由相关工作人员来将该支付通道对应的支付请求切换到其他支付通道中。
发明内容
本申请实施例提出了一种用于确定支付通道的方法和装置。
第一方面，本申请实施例提供了一种用于确定支付通道的方法，该方法包括：接收支付请求，其中支付请求包括支付请求对应的业务类型的信息；基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道；获取各候选支付通道分别对应的当前通道质量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，每一个候选支付通道的当前通道质量参数基于如下步骤生成：对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重；根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。
在一些实施例中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数正相关；以及对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对历史支付验证码获取耗时参数以及历史支付耗时参数分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数生成该候候选支付通道的当前通道质量参数；其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。
在一些实施例中，每一个候选支付通道当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关；以及对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对历史支付验证码获取及时率以及历史支付及时率分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
在一些实施例中，每一候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关；以及对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对支付验证码获取请求的并发数量以及根据验证码进行支付的 请求的并发数量分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该候选支付通道的当前通道质量参数。
在一些实施例中，在根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，该方法还包括：获取各候选支付通道分别对应的费用信息；以及根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道，包括：根据当前质量参数、各候选支付通道的费用信息所指示的费用，从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，支付请求包括支付金额信息；以及在根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，该方法还包括：获取各候选支付通道分别对应的支付限额信息；以及根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道，包括：根据当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及支付金额信息所指示的支付金额，从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，该方法还包括：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
第二方面，本申请实施例提供了一种用于确定支付通道的装置，该装置包括：接收单元，被配置成接收支付请求，其中支付请求包括支付请求对应的业务类型的信息；第一确定单元，被配置成基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道；获取单元，被配置成获取各候选支付通道分别对应的当前通道质量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；第二确定单元，被配置成根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，该装置还包括质量参数生成单元，质量参数生 成单元被配置成：对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重；根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。
在一些实施例中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数负相关；以及质量参数生成单元进一步被配置成：对历史支付验证码获取耗时参数以及历史支付耗时参数分配预先设置的权重；根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数生成该候选支付通道的当前通道质量参数；其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。
在一些实施例中，每一个候选支付通道当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关；以及质量参数生成单元进一步被配置成：对历史支付验证码获取及时率以及历史支付及时率分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
在一些实施例中，候选支付通道当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关；以及质量参数生成单元进一步被配置成：对支付验证码获取请求的并发数量以及根据验证码进行支付的请求的并发数量分配预先设置的权重；根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该候选支付通道的当前通道质量参数。
在一些实施例中，在第二确定单元根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，获取单元进一步被配置成：获取各候选支付通道分别对应的费用信息；以及第二确定单元 进一步被配置成：根据当前质量参数、各候选支付通道的费用信息所指示的费用，从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，上述支付请求包括支付金额信息；以及在第二确定单元根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，获取单元进一步被配置成：获取各候选支付通道分别对应的支付限额信息；以及第二确定单元进一步被配置成：根据当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及支付金额信息所指示的支付金额，从至少一个候选支付通道中确定出目标支付通道。
在一些实施例中，该装置还包括：报警单元，报警单元被配置成：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
第三方面，本申请实施例提供了一种电子设备，该电子设备包括：一个或多个处理器；存储装置，其上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个处理器实现如第一方面中任一实现方式描述的方法。
第四方面，本申请实施例提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现如第一方面中任一实现方式描述的方法。
本申请实施例提供的用于确定支付通道的方法和装置，通过接收支付请求，而后基于与支付请求中的业务类型对应的预设通道确定规则确定出至少一个候选支付通道，接着获取各候选支付通道分别对应的当前通道质量参数，最后根据当前质量参数从上述至少一个候选支付通道中确定出目标支付通道。从而实现了根据各候选支付通道的当前质量参数确定出与支付请求对应的目标支付通道。进一步地，可以通过所确定的目标支付通道实现支付通道的自动切换，从而有利于提高支付效率和支付成功率。
附图说明
通过阅读参照以下附图所作的对非限制性实施例所作的详细描 述，本申请的其它特征、目的和优点将会变得更明显：
图1是本申请的一个实施例的用于确定支付通道的方法可以应用于其中的示例性系统架构图；
图2是根据本申请的用于确定支付通道的方法的一个实施例的流程图；
图3是根据本申请的用于确定支付通道的方法的一个应用场景的示意图；
图4是根据本申请的用于确定支付通道的方法的又一个实施例的流程图；
图5是根据本申请的用于确定支付通道的装置的一个实施例的结构示意图；
图6是适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
具体实施方式
下面结合附图和实施例对本申请作进一步的详细说明。可以理解的是，此处所描述的具体实施例仅仅用于解释相关发明，而非对该发明的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与有关发明相关的部分。
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本申请。
图1示出了本申请的一个实施例的用于确定支付通道的方法可以应用于其中的示例性系统架构100。
如图1所示，系统架构100可以包括终端设备101、102、103和第一服务器105、第二服务器106、107、108和网络104、109。网络104用以在终端设备101、102、103和第一服务器105之间提供通信链路的介质。网络109用以在第一服务器105和第二服务器106、107、108之间提供通信链路的介质。网络104、109可以包括各种连接类型，例如有线、无线通信链路或者光纤电缆等等。
用户可以使用终端设备101、102、103通过网络104与第一服务器105交互，以接收或发送消息等。终端设备101、102、103上可以安装有各种客户端应用，例如支付类应用、购物类应用、搜索类应用、即时通信工具等。
终端设备101、102、103可以是硬件，也可以是软件。当终端设备101、102、103为硬件时，可以是具有显示屏并且支持网页浏览的各种电子设备，包括但不限于智能手机、平板电脑、膝上型便携计算机和台式计算机等等。当终端设备101、102、103为软件时，可以安装在上述所列举的电子设备中。其可以实现成多个软件或软件模块(例如用来提供分布式服务的软件或软件模块)，也可以实现成单个软件或软件模块。在此不做具体限定。
第一服务器105可以提供各种服务，例如接收终端设备101、102、103发送的支付请求；确定该支付请求对应的支付通道以及与支付通道所在第二服务器进行信息交互，以完成支付操作。
第二服务器106、107、108可以是支付通道对应的银行的服务器；第二服务器106、107、108可以提供各种服务，例如与第一服务器105通过网络109进行信息交互，完成终端设备101、102、103所发送的支付请求对应支付操作。
需要说明的是，第一服务器105和第二服务器106、107、108可以是硬件，也可以是软件。当第一服务器105和第二服务器106、107、108为硬件时，可以实现成多个服务器组成的分布式服务器集群，也可以实现成单个服务器。当第一服务器105和第二服务器106、107、108为软件时，可以实现成多个软件或软件模块(例如用来提供分布式服务的软件或软件模块)，也可以实现成单个软件或软件模块。在此不做具体限定。
需要说明的是，本申请实施例所提供的用于确定支付通道的方法一般由第一服务器105执行，相应地，用于确定支付通道的装置一般设置于第一服务器105中。
应该理解，图1中的终端设备、网络和第一服务器、第二服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的终端设 备、网络和服务器。
继续参考图2，其示出了根据本申请的用于确定支付通道的方法的一个实施例的流程200。该用于确定支付通道的方法，包括以下步骤：
步骤201，接收支付请求。
在本实施例中，用于确定支付通道的方法的执行主体(例如图1所示的第一服务器)可以接收终端设备(例如图1所示的终端设备)通过有线连接方式或者无线连接方式发送的支付请求。需要指出的是，上述无线连接方式可以包括但不限于3G/4G连接、WiFi连接、蓝牙连接、WiMAX连接、Zigbee连接、UWB(ultra wideband)连接、以及其他现在已知或将来开发的无线连接方式。
通常，用户可以利用终端上安装的支付应用客户端或者浏览器向上述执行主体发起支付请求。上述支付请求可以包括支付请求对应的业务类型。这里的业务类型例如可以包括：普通消费业务、保险业务、基金业务等。
此外，上述支付请求还可以包括支付金额、收款账号等信息、用户标识、终端标识等信息。上述执行主体可以根据用户标识来区分不同用户的支付请求。
步骤202，基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道。
在本实施例中，基于步骤201中得到的网址，上述执行主体(例如图1所示的第一服务器)可以首先确定出与该业务类型对应的预设通道确定规则，然后再基于上述预设通道确定规则确定出至少一个候选支付通道。
支付通道，例如可以是指提供支付受理能力的具体提供方或者三方跳转的通道方，也可以是收单方或者清算方。支付通道例如可以包括：银行快捷直连渠道(各银行快捷直连渠道)、银联在线(支持多个银行快捷交易)，快钱快捷(支持多个银行快捷交易)等。
每一个支付通道可以对应多个属性，例如支付通道支持支付请求并发量、该支付通道对应的手续费、支付通道、支付预计耗时等。
通常一个支付平台可以对应多个支付通道。每一个支付通道对应一个通道标识。通道标识用来区分不同的支付通道。这里的通道标识可以由数字或者支付来表示，或者由数字和支付的组合来表示。每一个通道标识可以与一个具体的支付通道一一对应。例如通道标识“01”与“北京中国银行快捷直连渠道”一一对应。
通常，不同的支付通道所支持的业务类型可以不相同。
在本实施例中，上述执行主体可以访问预先设置的业务类型与通道确定规则对照表。上述对照表可以存储在本地，也可以存储在与上述执行主体通过有线连接方式或者无线连接方式进行通信的其他电子设备中。
上述对照表可以包括多个业务类型，以及与每一个业务类型关联存储的预设通道确定规则。这里的通道确定规则例如可以设置支付耗时范围、支付费率范围等。
上述执行主体可以将上述支付请求对应的业务类型在上述对照表中进行匹配，从而在上述对照表中提取与上述支付请求对应的业务类型匹配的预设通道确定规则。然后，上述执行主体可以根据上述预设通道确定规则从多个支付通道中确定出至少一个候选支付通道。例如，若上述预设通道规则设定了通道的支付耗时范围为小于3小时，则可以将所对应的支付耗时属性对应的属性值小于3小时的多个支付通道确定为第一预候选支付通道集合；若上述预设通道确定规则还设定了支付费率范围小于0.3％，则可以将所对应的支付费率属性对应的属性值小于0.3％的多个支付通道确定为第二预候选支付通道集合。然后上述执行主体可以从第一预候选支付通道集合与第二预候选通道集合中确定出至少一个候选支付通道。例如可以取第一预候选支付通道集合与第二预候选支付通道集合的交集作为上述支付请求的候选支付通道。
此外，在一些应用场景中，上述支付请求还可以包括用户预先指定的支付通道。上述主体可以将上述用户预先指定的支付通道确定为与上述支付请求对应的候选支付通道。
步骤203，获取各候选支付通道分别对应的当前通道质量参数。
在本实施例中，用于确定支付通道的方法的执行主体可以通过各种方法来获取各候选支付通道分别对应的当前质量参数。其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关。
在这里，上述历史支付验证码获取成功率和历史支付成功率是指，通过对与当前时间点相距预设时间段之内的多个支付请求各自的支付验证码获取结果以及根据验证码进行支付的支付结果各自进行分析，而得到的该预设时间段内的获取支付验证码成功率以及支付成功率。例如，在上述预设时间段内共有100个支付请求，在这100个支付请求中，有80个支付请求通过支付通道成功获取了支付验证码，有70个支付请求通过验证码支付成功；则上述历史支付验证码获取成功率为0.8；历史支付成功率为0.7。此外，上述预设时间段可以为1秒、2秒等，上述预设时间段可以根据具体的应用场景进行设定，此处不进行限定。
在一些应用场景中，对于任意一个候选支付通道，上述执行主体可以对该支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。具体地，上述执行主体可以将加权后的历史支付验证码获取成功率以及加权后的历史支付成功率的累加和作为当前通道质量参数。
在这些应用场景中，上述该候选支付通道的当前通道质量参数Q可以使用如下公式来表示：
Q＝A1×W1+A2×W2    (1)；
其中，A1是该候选支付通道对应的历史获取支付验证码成功率；A2是该候选支付通道对应的历史支付成功率；W1、W2分别为A1、A2各自对应的预先设置的权重。A1大于零，小于等于1；A2大于零，小于等于1。W1、W2大于零。
在本实施例的一些可选的实现方式中，每一个候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数 量、根据验证码进行支付的请求的并发数量正相关。
在这些可选的实现方式中，上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对支付验证码获取请求的并发数量以及支付请求的并发数量分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该支付通道的当前通道质量参数。
在这些可选的实现方式中，上述每一个候选支付通道的当前质量参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的该候选支付通道支持的支付验证码获取请求的并发数量以及该候选支付通道支持的加权后的根据验证码进行支付的请求的并发数量的累加和。
在这些可选的实现方式中，一个候选支付通道的当前质量参数Q进一步可以由如下公式表示：
Q＝A1×W1+A2×W2+N1×Y1+N2×Y2   (2)；
其中，N1是该候选支付通道支持的获取支付验证码请求的并发数量；N2是该候选支付通道支持的根据验证码进行支付的请求的并发数量；Y1、Y2分别为N1、N2各自对应的预先设置的权重。N1、N2为正整数。Y1、Y2大于零。
在本实施例的另外一些可选的实现方式中，每一个候选支付通道的当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关；以及上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，包括：对历史支付验证码获取及时率以及历史支付及时率分配预先设置的权重；以及上述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
在这些可选的实现方式中，上述每一个候选支付通道的当前质量 参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的历史支付验证码获取及时率以及加权后的历史支付及时率的累加和。
若设置了支付验证码获取的参考响应时间，例如10毫秒，则上述支付验证码获取及时率可以按照如下方式确定：若上述预设时间段内的支付请求数量为100，在这100个支付请求中，有75个支付请求对应的支付验证码获取成功的时间小于等于上述参考响应时间(10毫秒)，则上述历史支付验证码获取及时率等于75/100＝0.75。支付成功及时率的计算方法，可以类比上述支付验证码获取及时率的计算方法，此处不赘述。
在这些可选的实现方式中，一个候选支付通道的当前质量参数Q可以由如下公式表示：
Q＝A1×W1+A2×W2+B1×X1+B2×X2    (3)；
其中，B1是该候选支付通道对应的历史获取支付验证码及时率；B2是该候选支付通道对应的根据验证码进行支付的历史支付及时率；X1、X2分别为B1、B2各自对应的预先设置的权重。B2、B2大于零，小于等于1。X1、X2大于零。
进一步可选的，每一个候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关。
在这些可选的实现方式中，上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对支付验证码获取请求的并发数量以及支付请求的并发数量分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该支付通道的当前通道质量参数。
在这些可选的实现方式中，上述每一个候选支付通道的当前质量参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的历史支付验证码获取及时率、加权后的历史支付及时 率、加权后的该通道支持的支付验证码获取请求的并发数量以及该通道支持的加权后的根据验证码进行支付的请求的并发数量的累加和。
在这些可选的实现方式中，该候选支付通道的当前质量参数Q进一步可以由如下公式表示：
Q＝A1×W1+A2×W2+B1×X1+B2×X2+N1×Y1+N2×Y2  (4)；
其中，N1是该候选支付通道支持的获取支付验证码请求的并发数量；N2是该候选支付通道支持的根据验证码进行支付的请求的并发数量；Y1、Y2分别为N1、N2各自对应的预先设置的权重。
步骤204，根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
在本实施例中，上述执行主体可以从上述至少一个候选支付通道中选取当前通道质量参数值最高的一个候选支付通道作为目标支付通道。
继续参见图3，图3是根据本申请的一个实施例的用于确定支付通道的方法的应用场景的一个示意图300。在图3的应用场景中，用户301通过终端设备302发起支付请求(步骤303)。支付请求包括该支付请求对应的业务类型。第一服务器304基于上述业务类型对应的预设通道确定规则确定出支付请求303对应的至少一个候选支付通道(步骤305)；接着，第一服务器304获取各候选支付通道分别对应的当前通道质量参数(步骤306)；之后，第一服务器304根据各候选支付通道的当前通道质量参数从上述至少一个候选支付通道中确定出目标支付通道(步骤307)。最后，第一服务器304调用上述目标支付通道完成支付请求对应的支付操作(步骤308)。
本申请的上述实施例提供的方法通过接收支付请求，而后基于与支付请求中的业务类型对应的预设通道确定规则确定出至少一个候选支付通道，接着获取各候选支付通道分别对应的当前通道质量参数，最后根据当前质量参数从上述至少一个候选支付通道中确定出目标支付通道。从而实现了根据各候选支付通道的当前质量参数确定出与支付请求对应的目标支付通道。进一步地，可以通过所确定的目标支付通道实现支付通道的自动切换，从而有利于提高支付效率和支付成功 率。
进一步参考图4，其示出了用于确定支付通道的方法的又一个实施例的流程400。该用于确定支付通道的方法的流程400，包括以下步骤：
步骤401，接收支付请求。
步骤401与图2所示实施例中的步骤201相同，此处不赘述。
步骤402，基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道。
步骤402与图2所示实施例中的步骤202相同，此处不赘述。
步骤403，获取各候选支付通道分别对应的当前通道质量参数。
在本实施例中，用于确定支付通道的方法的执行主体可以通过各种方法来获取各候选支付通道的分别对应的当前质量参数。其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关。
在这里，上述历史支付验证码获取成功率和历史支付成功率是指，根据在当前时间点之前、且与当前时间点相距预设时间段内的多个支付请求各自的支付验证码获取结果以及根据验证码进行支付的支付结果各自进行统计，得到的该预设时间段内的获取支付验证码成功率以及支付成功率。
在一些应用场景中，对于任意一个候选支付通道，上述执行主体可以对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。具体地，上述执行主体可以将加权后的历史支付验证码获取成功率以及加权后的历史支付成功率的累加和作为当前通道质量参数。
在这些应用场景中，上述候选支付通道的当前通道质量参数Q可以使用如下公式来表示：
Q＝A11×W12+A21×W22    (5)；
其中，A11是该候选支付通道对应的历史获取支付验证码成功率；A21是该候选支付通道对应的历史支付成功率；W12、W22分别为A11、A21各自对应的预先设置的权重。需要说明的是，上述公式(5)中的A11、A21、W12、W22可以分别和公式(1)中的A1、A2、W1、W2的获取方法以及数值相同。
在本实施例中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数正相关；以及上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对历史支付验证码获取耗时参数以及历史支付耗时参数分配预先设置的权重；以及上述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数生成该支付通道的当前通道质量参数。其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。也就是说，支付验证码获取时长越长，支付验证码获取耗时参数越小；根据验证码进行支付的支付耗时越长，支付耗时参数越小。
在一些应用场景中，上述支付验证码获取所用时长可以由预设时间段内支付通道响应多个支付验证码获取请求所用时长的TP50指标值、TP90指标值、TP99指标、平均值的统计值来表征。
在本实施例中，上述每一个候选支付通道的当前质量参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数的累加和。
在本实施例中，一个支付通道的当前质量参数Q可以由如下公式表示：
Q＝A11×W11+A21×W21+T1×Z1+T2×Z2    (5)；
其中，T1是该候选支付通道对应的历史支付验证码获取耗时参数；T2是该候选支付通道对应的根据验证码进行支付的历史支付耗时 参数；上述Z1、Z2为上述T1、T2各自对应的预先设置的参数。
在本实施例的一些可选的实现方式中，每一个候选支付通道的当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关。上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对历史支付验证码获取及时率以及历史支付及时率分配预先设置的权重。上述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
在这些可选的实现方式中，上述每一个候选支付通道的当前质量参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的历史支付验证码获取及时率以及加权后的历史支付及时率、加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数的累加和。
在这些可选的实现方式中，一个支付通道的当前质量参数Q可以由如下公式表示：
Q＝A11×W11+A21×W21+B11×X11+B21×X21+T1×Z1+T2×Z2    (6)；
其中，B11是该候选支付通道对应的历史获取支付验证码及时率；B21是该候选支付通道对应的根据验证码进行支付的历史支付及时率；X11、X21分别为B11、B21各自对应的预先设置的权重。需要说明的是，上述公式(6)中的X11、X21、B11、B21可以分别和公式(1)中的X1、X2、B1、B2的获取方法以及数值相同。
进一步可选地，每一个候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关。在这些可选的实现方式中，上述对历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：对支付验证码获取请求的并发数量以及支付请求的并发数量分配预先设置的权重。以及上述根据加权后的历史支付验证码获 取成功率以及加权后的历史支付成功率生成该支付通道的当前通道质量参数，还包括：根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该支付通道的当前通道质量参数。
在这些可选的实现方式中，上述每一个候选支付通道的当前质量参数等于加权后的历史支付验证码获取成功率、加权后的历史支付成功率、加权后的历史支付验证码获取及时率以及加权后的历史支付及时率、加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数、加权后的该候选支付通道支持的支付验证码获取请求的并发数量以及该候选支付通道支持的加权后的根据验证码进行支付的请求的并发数量的累加和。
在这些可选的实现方式中，一个候选支付通道的当前质量参数Q进一步可以由如下公式表示：
Q＝A11×W11+A21×W21+B11×X11+B21×X21+T1×Z1+T2×Z2+N11×Y11+N21×Y21    (7)；
其中，N11是该候选支付通道支持的获取支付验证码请求的并发数量；N21是该候选支付通道支持的根据验证码进行支付的请求的并发数量；Y11、Y21分别为N11、N21各自对应的预先设置的权重。需要说明的是，公式(7)中的N11、N21、Y11、Y21可以图2所示实施例中公式(2)的获取方法以及取值相同。
步骤404，根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
步骤404与图2所示实施例中的步骤204相同，此处不赘述。
从图4中可以看出，与图2对应的实施例相比，本实施例中的用于确定支付通道的方法的流程400引入了根据候选支付通道的历史支付验证码耗时参数以及历史支付耗时参数来确定候选支付通道的当前质量参数。由此，本实施例描述的方案可以引入更多的参数来确定候选支付通道的当前质量参数，从而可以实现从多个维度确定候选支付通道的当前质量参数，使得所生成的候选支付通道的当前质量参数更加精确。可以进一步有利于提高支付效率和支付成功率。
在本申请的用于确定支付通道的方法各实施例的一些可选的实现方式中，在图2所示实施例的步骤204以及在图4所示实施例的步骤404之前，用于确定支付通道的方法，还可以包括：获取各候选支付通道分别对应的费用信息；以及图2所示实施例的步骤204以及在图4所示实施例的步骤404包括：根据各候选支付通道的当前质量参数、各候选支付通道的费用信息所指示的费用，从上述至少一个候选支付通道中确定出目标支付通道。
在这些可选的实现方式中，在为支付请求分配支付通道时，除了考虑支付通道的当前质量参数之外，还考虑了支付通道的费用，从而在提高支付成功率以及支付效率的同时，还可以降低支付成本。
在本申请的用于确定支付通道的方法各实施例的另外一些可选的实现方式中，上述支付请求包括支付金额信息。在图2所示实施例的步骤204以及在图4所示实施例的步骤404之前，用于确定支付通道的方法，还包括：获取各候选支付通道分别对应的支付限额信息；以及根据当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及支付金额信息所指示的支付金额，从至少一个候选支付通道中确定出目标支付通道。图2所示实施例的步骤204以及在图4所示实施例的步骤404包括：根据当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及支付金额信息所指示的支付金额，从至少一个候选支付通道中确定出目标支付通道。
在这些可选的实现方式中，在为支付请求分配支付通道时，除了考虑候选支付通道的当前质量参数之外，还考虑了候选支付通道的支付限额，从而可以进一步提高支付成功率。
在本申请的用于确定支付通道的方法各实施例的另外一些可选的实现方式中，图2所示实施例和图4所示实施例的用于确定支付通道的方法可以进一步包括：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
在这些可选的实现方式中，通过上述报警信息来警示相关人员，报警信息所指示的候选支付通道出现问题，从而可以促使相关人员对上述当前通道质量参数小于预设阈值的候选支付通道进行人工干预， 从而可以进一步提高支付效率。
进一步参考图5，作为对上述各图所示方法的实现，本申请提供了一种用于确定支付通道的装置的一个实施例，该装置实施例与图2所示的方法实施例相对应，该装置具体可以应用于各种电子设备中。
如图5所示，本实施例的用于确定支付通道的装置500包括：接收单元501、第一确定单元502、获取单元503和第二确定单元504。其中，接收单元501，被配置成接收支付请求，其中支付请求包括支付请求对应的业务类型的信息；第一确定单元502，被配置成基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道；获取单元503，被配置成获取各候选支付通道分别对应的当前通道质量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；第二确定单元504，被配置成根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
在本实施例中，用于确定支付通道的装置500的接收单元501、第一确定单元502、获取单元503和第二确定单元504的具体处理及其所带来的技术效果可分别参考图2对应实施例中步骤201、步骤202、步骤203和步骤204的相关说明，在此不再赘述。
在本实施例的一些可选的实现方式中，用于确定支付通道的装置500还包括质量参数生成单元(图中未示出)。上述质量参数生成单元被配置成：对于每一个候选支付通道，对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重；根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。
在本实施例的一些可选的实现方式中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数正相关；以及质量参数生成单元进一步被配置成：对历史支付验证码获取耗时参数以及历史支付耗时参数分配预先设置的权重；根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参 数生成该候候选支付通道的当前通道质量参数；其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。
在本实施例的一些可选的实现方式中，每一个候选支付通道当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关；以及质量参数生成单元进一步被配置成：对历史支付验证码获取及时率以及历史支付及时率分配预先设置的权重；以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
在本实施例的一些可选的实现方式中，候选支付通道当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关；以及质量参数生成单元进一步被配置成：对支付验证码获取请求的并发数量以及根据验证码进行支付的请求的并发数量分配预先设置的权重；根据加权后的支付验证码获取请求的并发数量以及加权后的根据验证码进行支付的请求的并发数量生成该候选支付通道的当前通道质量参数。
在本实施例的一些可选的实现方式中，在第二确定单元504根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，获取单元503进一步被配置成：获取各候选支付通道分别对应的费用信息；以及第二确定单元504进一步被配置成：根据当前质量参数、各候选支付通道的费用信息所指示的费用，从至少一个候选支付通道中确定出目标支付通道。
在本实施例的一些可选的实现方式中，支付请求包括支付金额信息；以及在第二确定单元504根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道之前，获取单元503进一步被配置成：获取各候选支付通道分别对应的支付限额信息；以及第二确定单元504进一步被配置成：根据当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及支付金额信息所指示的支付金额，从至 少一个候选支付通道中确定出目标支付通道。
在本实施例的一些可选的实现方式中，用于确定支付通道的装置500还包括：报警单元(图中未示出)。报警单元被配置成：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
下面参考图6，其示出了适于用来实现本申请实施例的电子设备的计算机系统600的结构示意图。图6示出的电子设备仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图6所示，计算机系统600包括中央处理单元(CPU，Central Processing Unit)601，其可以根据存储在只读存储器(ROM，Read Only Memory)602中的程序或者从存储部分606加载到随机访问存储器(RAM，Random Access Memory)603中的程序而执行各种适当的动作和处理。在RAM 603中，还存储有系统600操作所需的各种程序和数据。CPU 601、ROM 602以及RAM 603通过总线604彼此相连。输入/输出(I/O，Input/Output)接口605也连接至总线604。
以下部件连接至I/O接口605：包括硬盘等的存储部分606；以及包括诸如LAN(局域网，Local Area Network)卡、调制解调器等的网络接口卡的通信部分607。通信部分607经由诸如因特网的网络执行通信处理。驱动器608也根据需要连接至I/O接口605。可拆卸介质609，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器608上，以便于从其上读出的计算机程序根据需要被安装入存储部分606。
特别地，根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分607从网络上被下载和安装，和/或从可拆卸介质609被安装。在该计算机程序被中央处理单元(CPU)601执行时，执行本申请的方法中限定的上述功能。需要说明的是，本申 请所述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请的操作的计算机程序代码，程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、 方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现。所描述的单元也可以设置在处理器中，例如，可以描述为：一种处理器包括接收单元、第一确定单元、获取单元和第二确定单元。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定，例如，接收单元还可以被描述为“接收支付请求的单元”。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的装置中所包含的；也可以是单独存在，而未装配入该装置中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该装置执行时，使得该装置：接收支付请求，其中支付请求包括支付请求对应的业务类型的信息；基于与业务类型对应的预设通道确定规则确定出至少一个候选支付通道；获取各候选支付通道分别对应的当前通道质量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；根据当前通道质量参数从至少一个候选支付通道中确定出目标支付通道。
以上描述仅为本申请的较佳实施例以及对所运用技术原理的说明。本领域技术人员应当理解，本申请中所涉及的发明范围，并不限于上述技术特征的特定组合而成的技术方案，同时也应涵盖在不脱离 上述发明构思的情况下，由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本申请中公开的(但不限于)具有类似功能的技术特征进行互相替换而形成的技术方案。

Claims (18)

  1. 一种用于确定支付通道的方法，包括：
    接收支付请求，其中所述支付请求包括所述支付请求对应的业务类型的信息；
    基于与所述业务类型对应的预设通道确定规则确定出至少一个候选支付通道；
    获取各候选支付通道分别对应的当前通道质量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；以及
    根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道。
  2. 根据权利要求1所述的方法，其中，每一个候选支付通道的当前通道质量参数基于如下步骤生成：
    对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重；以及
    根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。
  3. 根据权利要求2所述的方法，其中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数正相关；以及
    所述对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：
    对所述历史支付验证码获取耗时参数以及所述历史支付耗时参数分配预先设置的权重；以及
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数生成该候候选支付通道的当前通道质量参数；
    其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。
  4. 根据权利要求2或3所述的方法，其中，每一个候选支付通道当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关；以及
    所述对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：
    对所述历史支付验证码获取及时率以及所述历史支付及时率分配预先设置的权重；以及
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
  5. 根据权利要求4所述的方法，其中，每一候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关；以及
    所述对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重，还包括：
    对所述支付验证码获取请求的并发数量以及所述根据验证码进行支付的请求的并发数量分配预先设置的权重；以及
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的所述支付验证码获取请求的并发数量以及加权后的所述根据验证码进行支付的请求的并发数量生成该候选支付通道的当前通道质量参数。
  6. 根据权利要求1所述的方法，其中，在所述根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道之前，所述方法还包括：
    获取各候选支付通道分别对应的费用信息；以及
    所述根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道，包括：
    根据所述当前质量参数和各候选支付通道的费用信息所指示的费用，从所述至少一个候选支付通道中确定出目标支付通道。
  7. 根据权利要求1所述的方法，其中，所述支付请求包括支付金额信息；以及
    在所述根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道之前，所述方法还包括：
    获取各候选支付通道分别对应的支付限额信息；以及
    所述根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道，包括：
    根据所述当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及所述支付金额信息所指示的支付金额，从所述至少一个候选支付通道中确定出目标支付通道。
  8. 根据权利要求1所述的方法，其中，所述方法还包括：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
  9. 一种用于确定支付通道的装置，包括：
    接收单元，被配置成接收支付请求，其中所述支付请求包括支付请求对应的业务类型的信息；
    第一确定单元，被配置成基于与所述业务类型对应的预设通道确定规则确定出至少一个候选支付通道；
    获取单元，被配置成获取各候选支付通道分别对应的当前通道质 量参数；其中，每一个候选支付通道的当前通道质量参数与该候选支付通道对应的历史支付验证码获取成功率以及根据验证码进行支付的历史支付成功率正相关；
    第二确定单元，被配置成根据所述当前通道质量参数从所述至少一个候选支付通道中确定出目标支付通道。
  10. 根据权利要求9所述的装置，还包括质量参数生成单元，所述质量参数生成单元被配置成：
    对于每一个候选支付通道，对该候选支付通道对应的历史支付验证码获取成功率以及历史支付成功率分别分配预先设置的权重；
    以及根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选通道的当前通道质量参数。
  11. 根据权利要求10所述的装置，其中，每一个候选支付通道的当前通道质量参数还与历史支付验证码获取耗时参数以及历史支付耗时参数正相关，所述质量参数生成单元进一步被配置成:
    对所述历史支付验证码获取耗时参数以及所述历史支付耗时参数分配预先设置的权重；
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的历史支付验证码获取耗时参数以及加权后的历史支付耗时参数生成该候候选支付通道的当前通道质量参数,
    其中，支付验证码获取耗时参数与支付验证码获取所用时长负相关；支付耗时参数与使用验证码进行支付所用时长负相关。
  12. 根据权利要求10或11所述的装置，其中，每一个候选支付通道当前质量参数还与该候选支付通道对应的历史支付验证码获取及时率以及根据验证码进行支付的历史支付及时率正相关，所述质量参数生成单元进一步被配置成：
    对所述历史支付验证码获取及时率以及所述历史支付及时率分配 预先设置的权重；以及
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的历史支付验证码获取及时率以及加权后的历史支付及时率生成该支付通道的当前通道质量参数。
  13. 根据权利要求12所述的装置，其中，每一候选支付通道的当前质量参数还与该候选支付通道支持的支付验证码获取请求的并发数量、根据验证码进行支付的请求的并发数量正相关，所述质量参数生成单元进一步被配置成：
    对所述支付验证码获取请求的并发数量以及所述根据验证码进行支付的请求的并发数量分配预先设置的权重；以及
    所述根据加权后的历史支付验证码获取成功率以及加权后的历史支付成功率生成该候选支付通道的当前通道质量参数，还包括：
    根据加权后的所述支付验证码获取请求的并发数量以及加权后的所述根据验证码进行支付的请求的并发数量生成该候选支付通道的当前通道质量参数。
  14. 根据权利要求9所述的装置，所述获取单元进一步被配置成：获取各候选支付通道分别对应的费用信息；以及
    所述第二确定单元进一步被配置成：根据当前质量参数和各候选支付通道的费用信息所指示的费用，从至少一个候选支付通道中确定出目标支付通道。
  15. 根据权利要求9所述的装置，其中，所述支付请求包括支付金额信息，所述获取单元进一步被配置成：获取各候选支付通道分别对应的支付限额信息；以及
    所述第二确定单元进一步被配置成：根据所述当前质量参数、各候选支付通道的支付限额信息所指示的支付限额以及所述支付金额信息所指示的支付金额，从所述至少一个候选支付通道中确定出目标支 付通道。
  16. 根据权利要求9所述的装置，还包括报警单元，所述报警单元被配置成：响应于所获取到的任一候选支付通道的当前通道质量参数小于预设阈值，生成报警信息。
  17. 一种服务器，包括：
    一个或多个处理器；
    存储装置，其上存储有一个或多个程序，
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-8中任一所述的方法。
  18. 一种计算机可读介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如权利要求1-8中任一所述的方法。
PCT/CN2019/103579 2018-11-02 2019-08-30 用于确定支付通道的方法和装置 WO2020088075A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811300935.6A CN109447610A (zh) 2018-11-02 2018-11-02 用于确定支付通道的方法和装置
CN201811300935.6 2018-11-02

Publications (1)

Publication Number Publication Date
WO2020088075A1 true WO2020088075A1 (zh) 2020-05-07

Family

ID=65550352

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103579 WO2020088075A1 (zh) 2018-11-02 2019-08-30 用于确定支付通道的方法和装置

Country Status (2)

Country Link
CN (1) CN109447610A (zh)
WO (1) WO2020088075A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109447610A (zh) * 2018-11-02 2019-03-08 北京京东金融科技控股有限公司 用于确定支付通道的方法和装置
CN110490563A (zh) * 2019-07-12 2019-11-22 平安普惠企业管理有限公司 数据处理方法、装置、计算机设备和存储介质
CN110908746A (zh) * 2019-10-12 2020-03-24 平安银行股份有限公司 一种数据处理方法、系统、可读存储介质及终端设备
CN111010307A (zh) * 2019-10-24 2020-04-14 网银在线（北京）科技有限公司 信息传输方法、装置、电子设备及计算机可读存储介质
CN110852736B (zh) * 2019-11-26 2021-09-21 支付宝(杭州)信息技术有限公司 用车支付方法、装置、系统及电子设备
CN111130714B (zh) * 2019-11-28 2023-04-07 网银在线（北京）科技有限公司 数据传输方法、装置、电子设备以及计算机可读介质
CN112232803A (zh) * 2020-10-27 2021-01-15 云账户技术(天津)有限公司 一种支付订单预路由方法、装置和电子设备
CN112990906B (zh) * 2021-05-18 2021-09-21 浙江口碑网络技术有限公司 数据处理方法、装置和系统，计算机存储介质和电子设备
CN113469806B (zh) * 2021-07-21 2023-04-18 上海浦东发展银行股份有限公司 一种支付渠道确定方法、装置、设备及存储介质
CN114025332B (zh) * 2021-10-13 2023-12-29 深圳市新国都支付技术有限公司 支付业务通信方法、装置、计算机设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100211495A1 (en) * 2009-02-13 2010-08-19 Bank Of America Corporation Systems, methods and computer program products for improving foreign currency exchange in a comprehensive payment hub system
CN105741088A (zh) * 2016-01-27 2016-07-06 广州唯品会信息科技有限公司 路由匹配支付方法及装置
CN106127480A (zh) * 2016-06-16 2016-11-16 上海携程商务有限公司 交易支付方法及系统
CN107169756A (zh) * 2017-05-10 2017-09-15 北京凤凰理理它信息技术有限公司 支付通道分配方法、装置、存储介质和支付路由系统
CN107274163A (zh) * 2017-06-15 2017-10-20 北京奇艺世纪科技有限公司 一种话费支付的路由选择方法和装置
CN109447610A (zh) * 2018-11-02 2019-03-08 北京京东金融科技控股有限公司 用于确定支付通道的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107464108A (zh) * 2016-06-03 2017-12-12 上海点融信息科技有限责任公司 自动选择支付渠道的方法和设备
CN106845988A (zh) * 2017-01-23 2017-06-13 杭州恒生云融网络科技有限公司 用于选择支付通道的方法及装置
CN107871234A (zh) * 2017-09-25 2018-04-03 上海壹账通金融科技有限公司 电子支付方法及应用服务器
CN107818428A (zh) * 2017-11-28 2018-03-20 杭州龙盈互联网金融信息技术有限公司 业务渠道的决策方法以及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100211495A1 (en) * 2009-02-13 2010-08-19 Bank Of America Corporation Systems, methods and computer program products for improving foreign currency exchange in a comprehensive payment hub system
CN105741088A (zh) * 2016-01-27 2016-07-06 广州唯品会信息科技有限公司 路由匹配支付方法及装置
CN106127480A (zh) * 2016-06-16 2016-11-16 上海携程商务有限公司 交易支付方法及系统
CN107169756A (zh) * 2017-05-10 2017-09-15 北京凤凰理理它信息技术有限公司 支付通道分配方法、装置、存储介质和支付路由系统
CN107274163A (zh) * 2017-06-15 2017-10-20 北京奇艺世纪科技有限公司 一种话费支付的路由选择方法和装置
CN109447610A (zh) * 2018-11-02 2019-03-08 北京京东金融科技控股有限公司 用于确定支付通道的方法和装置

Also Published As

Publication number Publication date
CN109447610A (zh) 2019-03-08

Similar Documents

Publication Publication Date Title
WO2020088075A1 (zh) 用于确定支付通道的方法和装置
CN109190114B (zh) 用于生成回复信息的方法和装置
US8473352B2 (en) Consumer due diligence for money transfer systems and methods
US20160328685A1 (en) Resource reallocation method and server
US20150206131A1 (en) System and method for adaptive response protocol
US20190139049A1 (en) Order Information Processing Methods, Apparatuses and Systems
CN111857888B (zh) 一种交易处理方法及装置
CN111131356B (zh) 用于生成信息的方法和装置
CN110489195B (zh) 业务处理方法、装置、电子设备和计算机可读存储介质
TWI605396B (zh) Return resource processing method and device
CN112686528B (zh) 用于分配客服资源的方法、装置、服务器和介质
CN111105238A (zh) 一种交易风险控制方法和装置
CN111881329A (zh) 一种账户余额管理方法和系统
CN112381453A (zh) 信息处理方法、装置、电子设备和介质
CN115509754A (zh) 一种业务数据处理方法、装置、电子设备及存储介质
CN112541767B (zh) 刷脸支付方法、装置、刷脸设备和服务器
CN112181628B (zh) 资源转移方法、装置、系统和电子设备
JP2020113005A (ja) 情報処理方法、情報処理装置、及びプログラム
CN113052687A (zh) 一种交易路由分发方法和相关装置
CN116757816A (zh) 信息审批方法、装置、设备及存储介质
US10217087B2 (en) Multicomputer processing of client device request data using centralized event orchestrator
US12066997B2 (en) Determination of data consistency in distributed asynchronous architecture
CN110378785B (zh) 由服务器执行的交易处理方法、装置、计算设备以及介质
CN114581095A (zh) 一种支付的方法、收款终端和系统
US11169849B2 (en) Intelligent resource initiation and deployment system

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: 19877944

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: 19877944

Country of ref document: EP

Kind code of ref document: A1