CA3059719A1 - Payment processing method, device, medium and electronic device - Google Patents
Payment processing method, device, medium and electronic device Download PDFInfo
- Publication number
- CA3059719A1 CA3059719A1 CA3059719A CA3059719A CA3059719A1 CA 3059719 A1 CA3059719 A1 CA 3059719A1 CA 3059719 A CA3059719 A CA 3059719A CA 3059719 A CA3059719 A CA 3059719A CA 3059719 A1 CA3059719 A1 CA 3059719A1
- Authority
- CA
- Canada
- Prior art keywords
- payment
- verification
- payment request
- verification result
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 36
- 238000012795 verification Methods 0.000 claims abstract description 284
- 238000012545 processing Methods 0.000 claims abstract description 37
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000004590 computer program Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 abstract description 11
- 238000012423 maintenance Methods 0.000 abstract description 3
- 230000009467 reduction Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012954 risk control Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
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
-
- 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/38—Payment protocols; Details thereof
Abstract
The embodiments of the present disclosure provide a payment processing method, device, medium, and electronic device. The payment processing method includes: obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform; determining whether the payment request is verified according to the verification result of the payment request; and performing payment processing according to the payment request if it is determined that the payment request is verified. The technical solutions of the embodiments of the present disclosure can prevent a payment platform from repeatedly performing a verification process that has been completed in the same payment service, thereby effectively solving the problem that the same verification logic is repeatedly executed and thus causing the payment to take a long time. The present invention helps to achieve quick payments. At the same time, the implementation of repeated logic processes that may increase the processing load of a terminal device and payment platform can be avoided, thereby facilitating the reduction of maintenance costs.
Description
PAYMENT PROCESSING METHOD, DEVICE, MEDIUM AND ELECTRONIC
DEVICE
Technical Field [0001] The present disclosure relates to the field of computer technologies, and in particular, to a payment processing method, device, medium, and electronic device.
Back2round
DEVICE
Technical Field [0001] The present disclosure relates to the field of computer technologies, and in particular, to a payment processing method, device, medium, and electronic device.
Back2round
[0002] With the development of e-commerce platforms, online payment has become an indispensable payment method in people's everyday lives. The current payment method is to perform a series of logical judgments through a plurality of nodes, thereby implementing the payment. On this basis, developers improve the payment success rate of the entire system by continuously improving the reliability and stability of a single node. This payment method that improves the reliability and stability of a single node is more focused on a single node.
[0003] It is noted that the above information disclosed in this Background Art section is only for enhancement of understanding of the background of the present disclosure, and thus it may include information that does not constitute a prior art known to a person of ordinary skill in the art.
Summary
Summary
[0004] It is an object of the embodiments of the present disclosure to provide a payment processing method, device, medium, and electronic device, and at least to some extent overcome the problem of repeatedly performing the same logic verification in the same payment service.
[0005] Other features and advantages of the present disclosure will be apparent from the following detailed description, or learned in part by the practice of implementing the disclosure.
[0006] According to a first aspect of the present disclosure, a payment processing method is provided, the method comprising: obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform;
determining whether the payment request is verified according to the verification result of the payment request; and performing payment processing according to the payment request if it is determined that the payment request is verified.
determining whether the payment request is verified according to the verification result of the payment request; and performing payment processing according to the payment request if it is determined that the payment request is verified.
[0007] In some embodiments of the present disclosure, based on the foregoing solution, the obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform comprises: obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
[0008] In some embodiments of the present disclosure, based on the foregoing solution, the determining whether the payment request is verified according to the verification result of the payment request comprises: obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request; if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode; after the verification of the target verification mode is passed, determining that the payment request is verified.
[0009] In some embodiments of the present disclosure, based on the foregoing solution, the determining whether the payment request is verified according to the verification result of the payment request further comprises: if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
[0010] According to a second aspect of the present disclosure, a payment processing method is provided, the method comprising: verifying an obtained payment request to obtain a verification result of the payment request; and sharing the verification result of the payment request with each payment platform.
100111 In some embodiments of the present disclosure, based on the foregoing solution, the sharing the verification result of the payment request with payment platforms comprises: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0012] In some embodiments of the present disclosure, based on the foregoing solution, the sharing the verification result of the payment request with payment platforms comprises: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0013] According to a third aspect of the present disclosure, a payment processing device is provided, the device comprising: an obtaining unit, which is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform; a determining unit, which is used for determining whether the payment request is verified according to the verification result of the payment request; a processing unit, which is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
[0014] In some embodiments of the present disclosure, based on the foregoing solution, the obtaining unit is configured to perform: obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
[0015] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit is configured to perform: obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request; if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode; after the verification of the target verification mode is passed, determining that the payment request is verified.
[0016] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit is configured to perform: if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
[0017] According to a fourth aspect of the present disclosure, a payment processing device is provided, the device comprising: a verifying unit, which is used for verifying an obtained payment request to obtain a verification result of the payment request; and a sharing unit, which is used for sharing the verification result of the payment request with each payment platform.
[0018] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit is configured to perform: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0019] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit is configured to perform: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0020] According to a fifth aspect of the present disclosure, a computer readable medium is provided, the computer readable medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the payment processing method according to the above description.
[0021] According to a sixth aspect of the present disclosure, an electronic device is provided, the electronic device comprising: one or more processors; and a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement a payment processing method according to the above description.
[0022] The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:
[0023] In the technical solutions provided by some embodiments of the present disclosure, by means of verifying the payment request and sharing the verification result of the payment request with each payment platform, the payment platform can directly use the verified verification result. In this way, it can prevent a payment platform from repeatedly performing a verification process that has been completed in the same payment service, thereby effectively solving the problem that the same verification logic is repeatedly executed and thus causing the payment to take a long time. The present invention helps to achieve quick payments. At the same time, the implementation of repeated logic processes that may increase the processing load of a terminal device and payment platform can be avoided, thereby facilitating the reduction of maintenance costs.
[0024] It should be understood that the above general description and the following detailed description are merely exemplary and are not intended to limit the disclosure.
Brief Description of the Drawings [0025] The drawings herein are incorporated into the description and thus form a part of the description. The embodiments of the present disclosure are shown and used in conjunction with the description to explain the principles of the present disclosure.
Obviously, the drawings in the following description are only some embodiments of the present disclosure. For a person of ordinary skill in the art, other drawings can also be obtained from these figures without any inventive skill. In the drawings:
[0026] FIG. 1 schematically shows a flowchart of a payment processing method according to one embodiment of the present disclosure.
[0027] FIG. 2 is a flow chart showing determining whether a payment request is verified according to the verification result of a payment request.
[0028] FIG. 3 schematically shows a flowchart of a payment processing method according to an embodiment of the present disclosure.
[0029] FIG. 4 is a flowchart showing a payment processing method when the verification mode of a verification platform and that of a payment platform are the same according to an embodiment of the present disclosure.
[0030] FIG. 5 schematically shows a block diagram of a payment processing device according to an embodiment of the present disclosure.
[0031] FIG. 6 schematically shows a block diagram of a payment processing device according to another embodiment of the present disclosure.
[0032] FIG. 7 shows a block diagram of a computer system suitable in implementing an electronic device of an embodiment of the present disclosure.
Detailed Description [0033] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. However, these exemplary embodiments can be embodied in many forms and should not be construed that the present invention is limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete. The same reference numerals in the drawings denote the same or similar parts, and repeated description thereof will be omitted.
[0034] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details will be set forth; however, one skilled in the art will appreciate that the technical solution of the present disclosure may be practiced without one or more of the specific details, and other methods, components, devices, steps, etc. may be employed. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring the aspects of the present disclosure.
[0035] The block diagrams shown in the figures are merely functional entities and do not necessarily have to correspond to physically separate entities. That is, these functional entities may be implemented in software, or implemented in one or more hardware modules or integrated circuits. These functional entities may be implemented in different networks and/or processor devices and/or microcontroller devices.
[0036] The flowcharts shown in the figures are merely illustrative, and not all of the contents and operations/steps are necessarily included therein, and are not necessarily performed in the order described. For example, some operations/steps can be separated, while some operations/steps can be combined or partially combined. Therefore, the order of actual execution may change according to actual conditions.
[0037] At present, the common payment method is to implement the payment through a series of logical judgments on multiple platforms (for example, an order payment link may include multiple platforms such as an aggregate cashier and one or more third party payment cashiers).
[0038] But in fact, in the process of processing a payment, the logics executed by various payment platforms may overlap with each other, that is, it is possible that the same complex logic may be repeatedly executed on different platforms in a certain payment process. The process of repeatedly performing the same logic causes the problem that the payment takes a long time, which may affect a fast payment service. At the same time, the implementation of repeated work has also caused the problem of wasting the platform resources and increasing the maintenance costs. The present disclosure overcomes the above-mentioned problems caused by repeatedly executing the same verification logic in the same payment service by means of sharing the logical result of the part of logic that may overlap. The specific content of the present disclosure is as follows:
[0039] FIG. 1 schematically shows a flowchart of a payment processing method according to one embodiment of the present disclosure. The execution subject of this payment processing method includes the payment platform servers supported by the e-commerce providers.
100401 Referring to FIG. 1, a payment processing method according to one embodiment of the present disclosure includes the following steps S110 to S130, which will be explained in detail below:
[0041] Step 5110 is obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform.
[0042] In an embodiment of the present disclosure, the verification result for the payment request shared by the verification platform may be obtained in various ways, for example, obtaining the verification result from a storage space shared by the verification platform; for another example, receiving the verification result sent by the verification platform; for another example, obtaining the verification result issued by the verification platform from a blockchain network.
[0043] Step S120 is determining whether the payment request is verified according to the verification result of the payment request.
[0044] In an embodiment of the present disclosure, the step of determining, according to the verification result of the payment request, whether the payment request is verified, as shown in FIG. 2, may include the following steps S210 to S230, which will be explained in detail below:
[0045] Step S210 is obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request.
[0046] In an embodiment of the present disclosure, the verification modes corresponding to the payment request would include at least one verification mode, and the number of the verification modes is independent of the number of verification platform verification modes, and may be more than/less than/equal to the number of verification platform verification methods.
[0047] In an embodiment of the present disclosure, when the verification results of the verification modes are obtained from the verification result of the payment request, the verification results of these verification modes may be separately obtained from the verification result of the payment request in a certain order; or the verification results of these verification modes may be obtained from the verification result of the payment request at the same time. For example, in the case where it is required to perform the following types of verification: blacklist verification, anti-disturbance verification, and real-name verification on the payment platform, the payment platform may obtain the verification results of the blacklist verification, anti-disturbance verification and real name verification in the verification result of the payment request in the order of verification. Alternatively, the payment platform may simultaneously search and obtain the verification results of the three verification modes of blacklist verification, anti-disturbance verification and real name verification in the verification result of the payment request.
[0048] Step S220 is if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode.
[0049] In an embodiment of the present disclosure, if the number of verification modes of the payment platform is more than that of the verification modes of the verification platform, there is a target verification mode in which the verification result cannot be obtained; or if some verification modes are not passed on the verification platform, and the verification mode still needs to be verified on the payment platform, the verification mode is determined as the target verification mode, and is then re-verified.
[0050] Step S230 is after the verification of the target verification mode is passed, determining that the payment request is verified.
[0051] In an embodiment of the present disclosure, when it is determined, according to the verification result of the payment request, whether the payment request is verified, if the verification result of each verification mode is that the verification is passed, it would be determined that the payment request is verified.
[0052] With continued reference to FIG. 1, in step S130, if it is determined that the payment request verification is passed, the payment processing would be executed according to the payment request.
[0053] The technical solutions of the embodiments shown in FIG. 1 and FIG.
2 are the description of the payment processing method of the embodiments of the present disclosure from the perspective of a payment platform. The payment processing method of the embodiment of the present disclosure will be described below with reference to FIG. 3 from the perspective of a verification platform (that is, a platform that performs verification before invoking a specific payment platform, such as an aggregate cashier).
[0054] FIG. 3 schematically shows a flowchart of a payment processing method according to an embodiment of the present disclosure. The execution subject of the payment processing method may be a server or the like of each e-commerce platform.
[0055] Referring to FIG. 3, a payment processing method according to an embodiment of the present disclosure includes the following steps S310 to S320, which will be explained in detail below:
[0056] Step S310 is verifying an obtained payment request upon receiving the payment request to obtain a verification result of the payment request.
[0057] In an embodiment of the present disclosure, the verification of the payment request includes at least one verification mode, and the verification mode may be blacklist verification, anti-disturbance verification, real name verification, and card binding verification, risk control verification and so on.
[0058] In one embodiment of the present disclosure, a user may initiate a payment request in each e-commerce platform using a terminal device (for example, a smartphone, a tablet, a computer, or the like). The e-commerce platform may be an e-commerce web platform or an e-commerce client platform.
[0059] Step S320 is sharing the verification result of the payment request with each payment platform.
[0060] In one embodiment of the present disclosure, sharing the verification result of the payment request with each payment platform may be performed in various manners, for example, storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms;
or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0061] In an embodiment of the present disclosure, when the verification result of the payment request is being shared with each payment platform, it may be performed by asynchronous processing, for example, in the process of performing verification, if the verification mode, such as blacklist verification and anti-disturbance verification is completed, the verification results thereof may be asynchronously shared to each payment platform. In reference to FIG. 4, the implementation details of the technical solutions of the embodiments of the present disclosure will be described in detail with an example of a payment service in which the verification mode of the verification platform is the same as that of the payment platform.
The details include the following steps:
[0062] Step S410, after receiving a payment request, the verification platform sequentially performs blacklist verification, anti-disturbance verification, real name verification, card binding verification, and risk control verification with the payment request (the specific verification mode and the specific number of the verification modes are only uses as an example), and the verification result of the corresponding verification mode is obtained.
[0063] Step S420, the verification result is then asynchronously written into a verification result sharing platform, and is used to share the verification result of the payment request with the payment platforms.
[0064] Step S430, other business logics are executed before payment, for example, a corresponding payment platform may be invoked according to the target payment mode selected by the user, so that the payment platform processes the payment request accordingly.
[0065] The above are the steps performed by the verification platform in this embodiment.
The following describes the steps performed by the payment platform in this embodiment, which specifically includes the following steps:
[0066] Step S440, acquire, according to the received payment request, the verification results of the blacklist verification, the anti-disturbance verification, the real name verification, the card binding verification, and the risk control verification stored by a verification result sharing platform.
[00671 Step S450, determine, according to the verification result of the payment request, whether the blacklist verification, the anti-disturbance verification, the real name verification, the card binding verification, and the risk control verification have been passed, respectively.
[0068] Step S460, execute other business logics in the payment, for example, after determining that the payment request verification is passed, and perform payment processing according to the payment request.
[0069] It should be noted that the verification platform and the payment platform in the foregoing embodiment may be an aggregate cashier and a third party payment cashier in an order payment link.
[0070] The device embodiments of the present disclosure will be described below, and which can be used to perform the payment processing method described above in the present disclosure.
[0071] FIG. 5 schematically shows a block diagram of a payment processing device according to an embodiment of the present disclosure. The payment processing device can be disposed in a platform server of a payer.
[0072] Referring to FIG. 5, a payment processing device 500 according to an embodiment of the present disclosure includes an obtaining unit 501, a determining unit 502, and a processing unit 503.
[0073] The obtaining unit 501 is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform; the determining unit 502 is used for determining whether the payment request is verified according to the verification result of the payment request; and the processing unit 503 is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
[0074] In some embodiments of the present disclosure, based on the foregoing solution, the obtaining unit 501 is configured to perform: obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
[0075] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit 502 is configured to perform: obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request; if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode; after the verification of the target verification mode is passed, determining that the payment request is verified.
100111 In some embodiments of the present disclosure, based on the foregoing solution, the sharing the verification result of the payment request with payment platforms comprises: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0012] In some embodiments of the present disclosure, based on the foregoing solution, the sharing the verification result of the payment request with payment platforms comprises: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0013] According to a third aspect of the present disclosure, a payment processing device is provided, the device comprising: an obtaining unit, which is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform; a determining unit, which is used for determining whether the payment request is verified according to the verification result of the payment request; a processing unit, which is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
[0014] In some embodiments of the present disclosure, based on the foregoing solution, the obtaining unit is configured to perform: obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
[0015] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit is configured to perform: obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request; if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode; after the verification of the target verification mode is passed, determining that the payment request is verified.
[0016] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit is configured to perform: if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
[0017] According to a fourth aspect of the present disclosure, a payment processing device is provided, the device comprising: a verifying unit, which is used for verifying an obtained payment request to obtain a verification result of the payment request; and a sharing unit, which is used for sharing the verification result of the payment request with each payment platform.
[0018] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit is configured to perform: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0019] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit is configured to perform: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0020] According to a fifth aspect of the present disclosure, a computer readable medium is provided, the computer readable medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the payment processing method according to the above description.
[0021] According to a sixth aspect of the present disclosure, an electronic device is provided, the electronic device comprising: one or more processors; and a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement a payment processing method according to the above description.
[0022] The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:
[0023] In the technical solutions provided by some embodiments of the present disclosure, by means of verifying the payment request and sharing the verification result of the payment request with each payment platform, the payment platform can directly use the verified verification result. In this way, it can prevent a payment platform from repeatedly performing a verification process that has been completed in the same payment service, thereby effectively solving the problem that the same verification logic is repeatedly executed and thus causing the payment to take a long time. The present invention helps to achieve quick payments. At the same time, the implementation of repeated logic processes that may increase the processing load of a terminal device and payment platform can be avoided, thereby facilitating the reduction of maintenance costs.
[0024] It should be understood that the above general description and the following detailed description are merely exemplary and are not intended to limit the disclosure.
Brief Description of the Drawings [0025] The drawings herein are incorporated into the description and thus form a part of the description. The embodiments of the present disclosure are shown and used in conjunction with the description to explain the principles of the present disclosure.
Obviously, the drawings in the following description are only some embodiments of the present disclosure. For a person of ordinary skill in the art, other drawings can also be obtained from these figures without any inventive skill. In the drawings:
[0026] FIG. 1 schematically shows a flowchart of a payment processing method according to one embodiment of the present disclosure.
[0027] FIG. 2 is a flow chart showing determining whether a payment request is verified according to the verification result of a payment request.
[0028] FIG. 3 schematically shows a flowchart of a payment processing method according to an embodiment of the present disclosure.
[0029] FIG. 4 is a flowchart showing a payment processing method when the verification mode of a verification platform and that of a payment platform are the same according to an embodiment of the present disclosure.
[0030] FIG. 5 schematically shows a block diagram of a payment processing device according to an embodiment of the present disclosure.
[0031] FIG. 6 schematically shows a block diagram of a payment processing device according to another embodiment of the present disclosure.
[0032] FIG. 7 shows a block diagram of a computer system suitable in implementing an electronic device of an embodiment of the present disclosure.
Detailed Description [0033] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. However, these exemplary embodiments can be embodied in many forms and should not be construed that the present invention is limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete. The same reference numerals in the drawings denote the same or similar parts, and repeated description thereof will be omitted.
[0034] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details will be set forth; however, one skilled in the art will appreciate that the technical solution of the present disclosure may be practiced without one or more of the specific details, and other methods, components, devices, steps, etc. may be employed. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring the aspects of the present disclosure.
[0035] The block diagrams shown in the figures are merely functional entities and do not necessarily have to correspond to physically separate entities. That is, these functional entities may be implemented in software, or implemented in one or more hardware modules or integrated circuits. These functional entities may be implemented in different networks and/or processor devices and/or microcontroller devices.
[0036] The flowcharts shown in the figures are merely illustrative, and not all of the contents and operations/steps are necessarily included therein, and are not necessarily performed in the order described. For example, some operations/steps can be separated, while some operations/steps can be combined or partially combined. Therefore, the order of actual execution may change according to actual conditions.
[0037] At present, the common payment method is to implement the payment through a series of logical judgments on multiple platforms (for example, an order payment link may include multiple platforms such as an aggregate cashier and one or more third party payment cashiers).
[0038] But in fact, in the process of processing a payment, the logics executed by various payment platforms may overlap with each other, that is, it is possible that the same complex logic may be repeatedly executed on different platforms in a certain payment process. The process of repeatedly performing the same logic causes the problem that the payment takes a long time, which may affect a fast payment service. At the same time, the implementation of repeated work has also caused the problem of wasting the platform resources and increasing the maintenance costs. The present disclosure overcomes the above-mentioned problems caused by repeatedly executing the same verification logic in the same payment service by means of sharing the logical result of the part of logic that may overlap. The specific content of the present disclosure is as follows:
[0039] FIG. 1 schematically shows a flowchart of a payment processing method according to one embodiment of the present disclosure. The execution subject of this payment processing method includes the payment platform servers supported by the e-commerce providers.
100401 Referring to FIG. 1, a payment processing method according to one embodiment of the present disclosure includes the following steps S110 to S130, which will be explained in detail below:
[0041] Step 5110 is obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform.
[0042] In an embodiment of the present disclosure, the verification result for the payment request shared by the verification platform may be obtained in various ways, for example, obtaining the verification result from a storage space shared by the verification platform; for another example, receiving the verification result sent by the verification platform; for another example, obtaining the verification result issued by the verification platform from a blockchain network.
[0043] Step S120 is determining whether the payment request is verified according to the verification result of the payment request.
[0044] In an embodiment of the present disclosure, the step of determining, according to the verification result of the payment request, whether the payment request is verified, as shown in FIG. 2, may include the following steps S210 to S230, which will be explained in detail below:
[0045] Step S210 is obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request.
[0046] In an embodiment of the present disclosure, the verification modes corresponding to the payment request would include at least one verification mode, and the number of the verification modes is independent of the number of verification platform verification modes, and may be more than/less than/equal to the number of verification platform verification methods.
[0047] In an embodiment of the present disclosure, when the verification results of the verification modes are obtained from the verification result of the payment request, the verification results of these verification modes may be separately obtained from the verification result of the payment request in a certain order; or the verification results of these verification modes may be obtained from the verification result of the payment request at the same time. For example, in the case where it is required to perform the following types of verification: blacklist verification, anti-disturbance verification, and real-name verification on the payment platform, the payment platform may obtain the verification results of the blacklist verification, anti-disturbance verification and real name verification in the verification result of the payment request in the order of verification. Alternatively, the payment platform may simultaneously search and obtain the verification results of the three verification modes of blacklist verification, anti-disturbance verification and real name verification in the verification result of the payment request.
[0048] Step S220 is if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode.
[0049] In an embodiment of the present disclosure, if the number of verification modes of the payment platform is more than that of the verification modes of the verification platform, there is a target verification mode in which the verification result cannot be obtained; or if some verification modes are not passed on the verification platform, and the verification mode still needs to be verified on the payment platform, the verification mode is determined as the target verification mode, and is then re-verified.
[0050] Step S230 is after the verification of the target verification mode is passed, determining that the payment request is verified.
[0051] In an embodiment of the present disclosure, when it is determined, according to the verification result of the payment request, whether the payment request is verified, if the verification result of each verification mode is that the verification is passed, it would be determined that the payment request is verified.
[0052] With continued reference to FIG. 1, in step S130, if it is determined that the payment request verification is passed, the payment processing would be executed according to the payment request.
[0053] The technical solutions of the embodiments shown in FIG. 1 and FIG.
2 are the description of the payment processing method of the embodiments of the present disclosure from the perspective of a payment platform. The payment processing method of the embodiment of the present disclosure will be described below with reference to FIG. 3 from the perspective of a verification platform (that is, a platform that performs verification before invoking a specific payment platform, such as an aggregate cashier).
[0054] FIG. 3 schematically shows a flowchart of a payment processing method according to an embodiment of the present disclosure. The execution subject of the payment processing method may be a server or the like of each e-commerce platform.
[0055] Referring to FIG. 3, a payment processing method according to an embodiment of the present disclosure includes the following steps S310 to S320, which will be explained in detail below:
[0056] Step S310 is verifying an obtained payment request upon receiving the payment request to obtain a verification result of the payment request.
[0057] In an embodiment of the present disclosure, the verification of the payment request includes at least one verification mode, and the verification mode may be blacklist verification, anti-disturbance verification, real name verification, and card binding verification, risk control verification and so on.
[0058] In one embodiment of the present disclosure, a user may initiate a payment request in each e-commerce platform using a terminal device (for example, a smartphone, a tablet, a computer, or the like). The e-commerce platform may be an e-commerce web platform or an e-commerce client platform.
[0059] Step S320 is sharing the verification result of the payment request with each payment platform.
[0060] In one embodiment of the present disclosure, sharing the verification result of the payment request with each payment platform may be performed in various manners, for example, storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms;
or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0061] In an embodiment of the present disclosure, when the verification result of the payment request is being shared with each payment platform, it may be performed by asynchronous processing, for example, in the process of performing verification, if the verification mode, such as blacklist verification and anti-disturbance verification is completed, the verification results thereof may be asynchronously shared to each payment platform. In reference to FIG. 4, the implementation details of the technical solutions of the embodiments of the present disclosure will be described in detail with an example of a payment service in which the verification mode of the verification platform is the same as that of the payment platform.
The details include the following steps:
[0062] Step S410, after receiving a payment request, the verification platform sequentially performs blacklist verification, anti-disturbance verification, real name verification, card binding verification, and risk control verification with the payment request (the specific verification mode and the specific number of the verification modes are only uses as an example), and the verification result of the corresponding verification mode is obtained.
[0063] Step S420, the verification result is then asynchronously written into a verification result sharing platform, and is used to share the verification result of the payment request with the payment platforms.
[0064] Step S430, other business logics are executed before payment, for example, a corresponding payment platform may be invoked according to the target payment mode selected by the user, so that the payment platform processes the payment request accordingly.
[0065] The above are the steps performed by the verification platform in this embodiment.
The following describes the steps performed by the payment platform in this embodiment, which specifically includes the following steps:
[0066] Step S440, acquire, according to the received payment request, the verification results of the blacklist verification, the anti-disturbance verification, the real name verification, the card binding verification, and the risk control verification stored by a verification result sharing platform.
[00671 Step S450, determine, according to the verification result of the payment request, whether the blacklist verification, the anti-disturbance verification, the real name verification, the card binding verification, and the risk control verification have been passed, respectively.
[0068] Step S460, execute other business logics in the payment, for example, after determining that the payment request verification is passed, and perform payment processing according to the payment request.
[0069] It should be noted that the verification platform and the payment platform in the foregoing embodiment may be an aggregate cashier and a third party payment cashier in an order payment link.
[0070] The device embodiments of the present disclosure will be described below, and which can be used to perform the payment processing method described above in the present disclosure.
[0071] FIG. 5 schematically shows a block diagram of a payment processing device according to an embodiment of the present disclosure. The payment processing device can be disposed in a platform server of a payer.
[0072] Referring to FIG. 5, a payment processing device 500 according to an embodiment of the present disclosure includes an obtaining unit 501, a determining unit 502, and a processing unit 503.
[0073] The obtaining unit 501 is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform; the determining unit 502 is used for determining whether the payment request is verified according to the verification result of the payment request; and the processing unit 503 is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
[0074] In some embodiments of the present disclosure, based on the foregoing solution, the obtaining unit 501 is configured to perform: obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
[0075] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit 502 is configured to perform: obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request; if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode; after the verification of the target verification mode is passed, determining that the payment request is verified.
11 [0076] In some embodiments of the present disclosure, based on the foregoing solution, the determining unit 502 is configured to perform: if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
[0077] FIG. 6 schematically shows a block diagram of a payment processing device according to another embodiment of the present disclosure. The processing device can be arranged on a server of an e-commerce platform.
[0078] Referring to FIG. 6, a payment processing device 600 according to an embodiment of the present disclosure includes a verifying unit 601 and a sharing unit 602.
[0079] The verifying unit 601 is used for verifying an obtained payment request to obtain a verification result of the payment request; the sharing unit 602 is used for sharing the verification result of the payment request with each payment platform.
[0080] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit 602 is configured to perform: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0081] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit 602 is configured to perform: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0082] The respective functional modules of the payment processing device of the exemplary embodiment of the present disclosure correspond to the steps in the exemplary embodiment of the above-described payment processing method. Therefore, for the details not disclosed in this embodiment of the present disclosure, please refer to the embodiment of the payment processing method described above in the present disclosure.
[0083] Referring to FIG. 7, a block diagram of a computer system 700 suitable for use in implementing an electronic device of an embodiment of the present disclosure is shown. The computer system 700 of the electronic device illustrated in FIG. 7 is merely an example and should not impose any limitation on the function and scope of the embodiments of the present disclosure.
[0077] FIG. 6 schematically shows a block diagram of a payment processing device according to another embodiment of the present disclosure. The processing device can be arranged on a server of an e-commerce platform.
[0078] Referring to FIG. 6, a payment processing device 600 according to an embodiment of the present disclosure includes a verifying unit 601 and a sharing unit 602.
[0079] The verifying unit 601 is used for verifying an obtained payment request to obtain a verification result of the payment request; the sharing unit 602 is used for sharing the verification result of the payment request with each payment platform.
[0080] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit 602 is configured to perform: storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms; or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
[0081] In some embodiments of the present disclosure, based on the foregoing solution, the sharing unit 602 is configured to perform: sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
[0082] The respective functional modules of the payment processing device of the exemplary embodiment of the present disclosure correspond to the steps in the exemplary embodiment of the above-described payment processing method. Therefore, for the details not disclosed in this embodiment of the present disclosure, please refer to the embodiment of the payment processing method described above in the present disclosure.
[0083] Referring to FIG. 7, a block diagram of a computer system 700 suitable for use in implementing an electronic device of an embodiment of the present disclosure is shown. The computer system 700 of the electronic device illustrated in FIG. 7 is merely an example and should not impose any limitation on the function and scope of the embodiments of the present disclosure.
12 [0084] As shown in FIG. 7, the computer system 700 includes a central processing unit (CPU) 701 that can perform various appropriate actions and processes according to a program stored in read only memory (ROM) 702 or a program loaded in random access memory (RAM) 703 from a storage portion 708. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also coupled to the bus 704.
[0085] The following components are connected to the I/0 interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), a speaker, and the like; a storage portion 708 including a hard disk or the like; and a communication portion 709 including a network interface card such as a LAN card, a modem, and the like. The communication portion 709 performs communication processing via a network such as the Internet. A driver 710 may also be connected to the I/0 interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like, may be mounted on the drive 710 as needed so that a computer program read therefrom can be installed into the storage portion 708 as needed.
[0086] In particular, the processes described above with reference to the flowcharts may be implemented as a computer software program in accordance with an embodiment of the present disclosure. For example, an embodiment of the present disclosure includes a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for executing the method illustrated in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from the network via the communication portion 709, and/or installed from the removable media 711.
When the computer program is executed by the central processing unit (CPU) 701, the above-described functions defined in the system of the present application can be executed.
[0087] It should be noted that the computer readable medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, 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 having one or
[0085] The following components are connected to the I/0 interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), a speaker, and the like; a storage portion 708 including a hard disk or the like; and a communication portion 709 including a network interface card such as a LAN card, a modem, and the like. The communication portion 709 performs communication processing via a network such as the Internet. A driver 710 may also be connected to the I/0 interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like, may be mounted on the drive 710 as needed so that a computer program read therefrom can be installed into the storage portion 708 as needed.
[0086] In particular, the processes described above with reference to the flowcharts may be implemented as a computer software program in accordance with an embodiment of the present disclosure. For example, an embodiment of the present disclosure includes a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for executing the method illustrated in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from the network via the communication portion 709, and/or installed from the removable media 711.
When the computer program is executed by the central processing unit (CPU) 701, the above-described functions defined in the system of the present application can be executed.
[0087] It should be noted that the computer readable medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, 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 having one or
13 more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fibers, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain or store a program, which can be used by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, a computer readable signal medium may include a data signal that is propagated in the baseband or as part of a carrier, carrying computer readable program code. Such propagated data signals can take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing.
The computer readable signal medium can also be any computer readable medium other than a computer readable storage medium, which can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. Program code embodied on a computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
[0088] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products in accordance with various embodiments of the present disclosure. In this regard, each block of the flowchart or block diagrams can represent a module, a program segment, or a portion of code that includes one or more executable instructions. It should also be noted that in some alternative implementations, the functions noted in the blocks may also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowcharts, and combinations of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.
[0089] The units described in the embodiments of the present disclosure may be implemented by software, or may be implemented by hardware, and the described units may also
The computer readable signal medium can also be any computer readable medium other than a computer readable storage medium, which can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. Program code embodied on a computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
[0088] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products in accordance with various embodiments of the present disclosure. In this regard, each block of the flowchart or block diagrams can represent a module, a program segment, or a portion of code that includes one or more executable instructions. It should also be noted that in some alternative implementations, the functions noted in the blocks may also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowcharts, and combinations of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.
[0089] The units described in the embodiments of the present disclosure may be implemented by software, or may be implemented by hardware, and the described units may also
14 be disposed in the processor. The names of these units do not in any way constitute a limitation to the unit.
[0090] In another aspect, the present application further provides a computer readable medium, which may be included in an electronic device described in the above embodiments, or may be separately present without being assembled into the electronic device.
The computer readable medium carries one or more programs that, when executed by one of the electronic devices, cause the electronic device to implement the payment processing method as described in the above embodiments.
[0091] For example, the electronic device may be implemented as shown in FIG. 1: step 5110, acquiring, according to the received payment request, a verification result shared by a verification platform for the payment request; step S120, determining whether the payment request is verified according to the verification result of the payment request; and step S130, if it is determined that the payment request verification is passed, the payment processing would be executed according to the payment request.
[0092] As another example, the electronic device can implement various steps as shown in FIGS. 2 to 4.
[0093] It should be noted that although several modules or units of equipment for action execution are mentioned in the detailed description above, such division is not mandatory. In fact, in accordance with embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit.
Alternatively, the features and functions of one of the modules or units described above may be further divided into multiple modules or units.
[0094] Through the description of the above embodiments, a person skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software in combination with necessary hardware.
Therefore, the technical solution according to an embodiment of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, or the like.) or on a network, including several instructions, such that the method according to an embodiment of the present disclosure is performed by a computing device (which may be a personal computer, a server, a mobile terminal, a network device, or the like).
[0095] A person skilled in the art may easily achieve other solutions of the present disclosure after considering the description and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present disclosure, which are in accordance with the general principles of the disclosure and include common general knowledge or common technical means in the art that are not disclosed in the present disclosure. The description and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are defined by the claims.
[0096] It should be understood that the present disclosure is not limited to the precise structures that have been described above and illustrated in the drawings, and various modifications and changes can be made without departing from the scope thereof The scope of the disclosure is to be limited only by the appended claims.
[0090] In another aspect, the present application further provides a computer readable medium, which may be included in an electronic device described in the above embodiments, or may be separately present without being assembled into the electronic device.
The computer readable medium carries one or more programs that, when executed by one of the electronic devices, cause the electronic device to implement the payment processing method as described in the above embodiments.
[0091] For example, the electronic device may be implemented as shown in FIG. 1: step 5110, acquiring, according to the received payment request, a verification result shared by a verification platform for the payment request; step S120, determining whether the payment request is verified according to the verification result of the payment request; and step S130, if it is determined that the payment request verification is passed, the payment processing would be executed according to the payment request.
[0092] As another example, the electronic device can implement various steps as shown in FIGS. 2 to 4.
[0093] It should be noted that although several modules or units of equipment for action execution are mentioned in the detailed description above, such division is not mandatory. In fact, in accordance with embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit.
Alternatively, the features and functions of one of the modules or units described above may be further divided into multiple modules or units.
[0094] Through the description of the above embodiments, a person skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software in combination with necessary hardware.
Therefore, the technical solution according to an embodiment of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, or the like.) or on a network, including several instructions, such that the method according to an embodiment of the present disclosure is performed by a computing device (which may be a personal computer, a server, a mobile terminal, a network device, or the like).
[0095] A person skilled in the art may easily achieve other solutions of the present disclosure after considering the description and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present disclosure, which are in accordance with the general principles of the disclosure and include common general knowledge or common technical means in the art that are not disclosed in the present disclosure. The description and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are defined by the claims.
[0096] It should be understood that the present disclosure is not limited to the precise structures that have been described above and illustrated in the drawings, and various modifications and changes can be made without departing from the scope thereof The scope of the disclosure is to be limited only by the appended claims.
Claims (11)
1. A payment processing method, characterized in that the method comprises:
obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform;
determining whether the payment request is verified according to the verification result of the payment request;
performing payment processing according to the payment request if it is determined that the payment request is verified.
obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform;
determining whether the payment request is verified according to the verification result of the payment request;
performing payment processing according to the payment request if it is determined that the payment request is verified.
2. The payment processing method according to claim 1, characterized in that the obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform comprises:
obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
obtaining the verification result from a storage space shared with the verification platform; or receiving the verification result sent by the verification platform; or obtaining the verification result issued by the verification platform from a blockchain network.
3. The payment processing method according to claim 1, characterized in that the determining whether the payment request is verified according to the verification result of the payment request comprises:
obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request;
if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode;
after the verification of the target verification mode is passed, determining that the payment request is verified.
obtaining verification results of various verification modes in the verification result of the payment request according to the various verification modes corresponding to the payment request;
if there is a target verification mode having an unavailable verification result and/or a verification result that does not pass the verification, re-verifying the target verification mode;
after the verification of the target verification mode is passed, determining that the payment request is verified.
4. The payment processing method according to claim 3, characterized in that the determining whether the payment request is verified according to the verification result of the payment request further comprises:
if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
if the verification results of the verification modes all pass the verification, determining that the payment request is verified.
5. A payment processing method, characterized in that the method comprises:
verifying an obtained payment request to obtain a verification result of the payment request; and sharing the verification result of the payment request with each payment platform.
verifying an obtained payment request to obtain a verification result of the payment request; and sharing the verification result of the payment request with each payment platform.
6. The payment processing method according to claim 5, characterized in that the sharing the verification result of the payment request with payment platforms comprises:
storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms;
or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
storing the verification result of the payment request into a storage space of each of the payment platforms to share the verification result with the payment platforms;
or sending the verification result of the payment request to the payment platforms; or posting the verification result of the payment request to a blockchain network to share the verification result with the payment platforms through the blockchain network.
7. The payment processing method according to any one of claims 5 to 6, characterized in that the sharing the verification result of the payment request with payment platforms comprises:
sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
sharing the verification result of the payment request with the payment platforms by means of asynchronous processing.
8. A payment processing device, characterized in that the device comprises:
an obtaining unit, which is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform;
a determining unit, which is used for determining whether the payment request is verified according to the verification result of the payment request;
a processing unit, which is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
an obtaining unit, which is used for obtaining, according to a received payment request, a verification result for the payment request shared by a verification platform;
a determining unit, which is used for determining whether the payment request is verified according to the verification result of the payment request;
a processing unit, which is used for performing payment processing according to the payment request if it is determined that the payment request is verified.
9. A payment processing device, characterized in that the device comprises:
a verifying unit, which is used for verifying an obtained payment request to obtain a verification result of the payment request;
a sharing unit, which is used for sharing the verification result of the payment request with each payment platform.
a verifying unit, which is used for verifying an obtained payment request to obtain a verification result of the payment request;
a sharing unit, which is used for sharing the verification result of the payment request with each payment platform.
10. A computer readable medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the payment processing method according to any one of claims 1 to 4, and/or to implement the payment processing method according to any one of claims 5 to 7.
11. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement a payment processing method according to any of claims 1 to 4, and/or to implement a payment processing method according to any of claims 5 to 7.
one or more processors;
a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement a payment processing method according to any of claims 1 to 4, and/or to implement a payment processing method according to any of claims 5 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA3217578A CA3217578A1 (en) | 2018-10-23 | 2019-10-22 | Payment processing method, device, medium and electronic device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811237189.0A CN109325744B (en) | 2018-10-23 | 2018-10-23 | Payment processing method, payment processing device, payment processing medium and electronic equipment |
| CN201811237189.0 | 2018-10-23 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3217578A Division CA3217578A1 (en) | 2018-10-23 | 2019-10-22 | Payment processing method, device, medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA3059719A1 true CA3059719A1 (en) | 2020-04-23 |
Family
ID=65262806
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3217578A Pending CA3217578A1 (en) | 2018-10-23 | 2019-10-22 | Payment processing method, device, medium and electronic device |
| CA3059719A Granted CA3059719A1 (en) | 2018-10-23 | 2019-10-22 | Payment processing method, device, medium and electronic device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3217578A Pending CA3217578A1 (en) | 2018-10-23 | 2019-10-22 | Payment processing method, device, medium and electronic device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109325744B (en) |
| CA (2) | CA3217578A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110007904B (en) * | 2019-03-25 | 2020-11-20 | 腾讯科技（深圳）有限公司 | Data processing method, device and equipment |
| CN110060127A (en) * | 2019-04-18 | 2019-07-26 | 南京德通信息科技有限公司 | It is a kind of for medicine ecommerce information management system, method and apparatus |
| CN110060057A (en) * | 2019-04-18 | 2019-07-26 | 南京德通信息科技有限公司 | A kind of health care product based on big data chooses integration platform, method and apparatus |
| WO2021038580A1 (en) * | 2019-08-29 | 2021-03-04 | Panda Subhamaya | System and method for payment provision guarantee |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR3031613B1 (en) * | 2015-01-09 | 2018-04-06 | Ingenico Group | METHOD FOR PROCESSING A TRANSACTION FROM A COMMUNICATION TERMINAL |
| TWI643141B (en) * | 2015-09-04 | 2018-12-01 | 黃少風 | Payment service equipment that can perform payment operations with multiple third-party payment platforms and payment method |
| CN107403312B (en) * | 2016-05-18 | 2024-03-26 | 北京三星通信技术研究有限公司 | Quick payment method and device |
| CN107480963A (en) * | 2017-07-18 | 2017-12-15 | 阿里巴巴集团控股有限公司 | Payment processing method, device and electronic equipment |
| CN107862527A (en) * | 2017-10-27 | 2018-03-30 | 深圳市金立通信设备有限公司 | A kind of method of payment, terminal and server |
-
2018
- 2018-10-23 CN CN201811237189.0A patent/CN109325744B/en active Active
-
2019
- 2019-10-22 CA CA3217578A patent/CA3217578A1/en active Pending
- 2019-10-22 CA CA3059719A patent/CA3059719A1/en active Granted
Also Published As
| Publication number | Publication date |
|---|---|
| CN109325744B (en) | 2022-05-27 |
| CN109325744A (en) | 2019-02-12 |
| CA3217578A1 (en) | 2020-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108346028B (en) | Business approval processing method, device and system | |
| CA3059719A1 (en) | Payment processing method, device, medium and electronic device | |
| CN109146490B (en) | Block generation method, device and system | |
| CN110377522B (en) | Transaction scene testing method, device, computing equipment and medium | |
| CN109901987B (en) | Method and device for generating test data | |
| CN112036558A (en) | Model management method, electronic device, and medium | |
| CN112767133A (en) | Service decision method and device, storage medium and computer equipment | |
| CN114358921A (en) | System switching method, apparatus, device, medium, and program product | |
| CN114756877A (en) | Data management method, device, server and storage medium | |
| CN112288577B (en) | Transaction processing method, device, electronic equipment and medium for distributed service | |
| CN112965916B (en) | Page testing method, page testing device, electronic equipment and readable storage medium | |
| CN112152879B (en) | Network quality determination method, device, electronic equipment and readable storage medium | |
| CN110532810B (en) | Information processing method and device, electronic equipment and readable storage medium | |
| CA3059719C (en) | Payment processing method, device, medium and electronic device | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| CN108804442B (en) | Serial number generation method and device | |
| CN112506781B (en) | Test monitoring method, device, electronic equipment, storage medium and program product | |
| CN115134228A (en) | Environment link supply and detection method, device, equipment, medium and program product | |
| CN112181817B (en) | Test method and test device for SOA architecture platform | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| CN112882921B (en) | Fault simulation method and device | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN109657179B (en) | Service processing method, system and storage medium | |
| CN109840073B (en) | Method and device for realizing business process | |
| CN109712011B (en) | Community discovery method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |