CN106779702A - Method of payment and payment system - Google Patents
Method of payment and payment system Download PDFInfo
- Publication number
- CN106779702A CN106779702A CN201611061175.9A CN201611061175A CN106779702A CN 106779702 A CN106779702 A CN 106779702A CN 201611061175 A CN201611061175 A CN 201611061175A CN 106779702 A CN106779702 A CN 106779702A
- Authority
- CN
- China
- Prior art keywords
- payment
- client
- sending
- information
- order information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012011 method of payment Methods 0.000 title abstract 2
- 238000000034 method Methods 0.000 claims abstract description 33
- 238000012795 verification Methods 0.000 claims description 10
- 230000003993 interaction Effects 0.000 abstract 2
- 230000005540 biological transmission Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 230000002452 interceptive effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000717 retained effect Effects 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
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- 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
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present invention discloses a kind of method of payment and payment system, and methods described includes：Client receives the request that places an order of user input；The request that places an order is signed to generate sequence information by the beneficiary server according to default signature rule；The sequence information is generated request data by the client according to default form；The payment platform decrypts the request data, obtains the sequence information；The signature of the sequence information is verified, and evidence for payment is generated after being proved to be successful；The evidence for payment is encrypted according to default cipher mode；The client decrypts the evidence for payment, and payment information in the evidence for payment calls the means of payment to carry out delivery operation.Technical scheme, is encrypted in different ways by the interaction data between client, beneficiary server and payment platform, the security of interaction data has been effectively ensured, and then ensure that the security for improving delivery operation.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a payment method and a payment system.
Background
With the development of the mobile internet technology, the popularity of the mobile terminal is higher and higher, the frequency of using the mobile terminal by a user is higher and higher in the transaction process of the electronic transaction platform, and more people pay through the mobile terminal in the transaction link of the electronic transaction platform.
In the electronic transaction process, the security of the payment operation is mainly considered by the user, and how to improve the security of the payment operation in the electronic transaction becomes a technical problem to be solved urgently.
Disclosure of Invention
The invention mainly aims to provide a payment method and a payment system, aiming at effectively improving the safety of payment operation.
In order to achieve the above purpose, the payment method provided by the invention comprises the following steps:
the client receives a ordering request input by a user and sends the ordering request to a payee server;
the payee server signs the order placing request according to a preset signature rule to generate order information and sends the order information to the client;
the client generates request data according to the order information in a preset format and sends the request data to a payment platform;
the payment platform decrypts the request data to acquire the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; encrypting the payment certificate according to a preset encryption mode, and sending the encrypted payment certificate to the client;
and the client decrypts the payment certificate and calls a payment tool to carry out payment operation according to the payment information in the payment certificate.
Optionally, the step of the client generating the request data according to the order information in a preset format includes:
and adding a binary protocol header in the order information.
Optionally, the step of encrypting the preset encryption mode of the payment credential includes:
adding a binary protocol header to the payment credential.
Optionally, the payment method further includes:
and after the payment is successful, the payment platform feeds back payment success information to the payee server.
Optionally, the step of feeding back payment success information to the payee server includes:
the payment platform receives payment success information fed back by the payment tool and sends the payment success information to the payee server;
judging whether the payment success information is successfully sent or not;
if not, recording the reason of the failure of sending, and sending the payment success information again when the preset time is reached;
and when the sending failure times are larger than or equal to the preset times, keeping the reason of the last sending failure, and sending an early warning mail to the payee server.
In order to achieve the above object, the present invention provides a payment system, which includes a client, a payee server, a payment platform and a payment tool; wherein,
the client is used for receiving a ordering request input by a user and sending the ordering request to the payee server;
the payee server is used for signing the order placing request according to a preset signature rule to generate order information and sending the order information to the client;
the client is used for generating request data according to the order information in a preset format and sending the request data to a payment platform;
the payment platform is used for decrypting the request data and acquiring the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; encrypting the payment certificate according to a preset encryption mode, and sending the encrypted payment certificate to the client;
the client is used for decrypting the payment voucher and calling a payment tool according to the payment information in the payment voucher;
the payment tool is used for executing payment operation.
Optionally, the client is configured to add a binary protocol header to the request data.
Optionally, the payment platform is configured to add a binary protocol header to the payment credential.
Optionally, the payment platform is further configured to feed back payment success information to the payee server after the payment is successful.
Optionally, the payment platform includes: an execution module and a judgment module; wherein,
the execution module is used for receiving payment success information fed back by the payment tool and sending the payment success information to the payee server;
the judging module is used for judging whether the payment success information is successfully sent;
the execution module is further used for recording the reason of the failure in sending after the successful payment information is failed to be sent, and sending the successful payment information again when the preset time is reached;
and the execution module is also used for keeping the reason of the last sending failure when the sending failure times are more than or equal to the preset times, and sending an early warning mail to the payee server.
According to the technical scheme, the interactive data among the client, the payee server and the payment platform are encrypted in different modes, so that the safety of the interactive data is effectively guaranteed, and the safety of payment operation is further guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
FIG. 1 is a flow chart of one embodiment of a payment method of the present invention;
FIG. 2 is a flow chart of another embodiment of a payment method of the present invention;
FIG. 3 is a flowchart of the step of FIG. 2 of feeding back payment success information to the payee server;
FIG. 4 is a block diagram of an embodiment of a payment system of the present invention;
FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a payment system embodying the present invention;
fig. 6 is a block diagram of an embodiment of the payment platform in fig. 4.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
The invention provides a payment method. The payment method of the invention is applied to the mobile terminal, but is not limited to the mobile terminal. The following description will be made by taking a mobile terminal as an example:
as shown in fig. 1, fig. 1 is a flowchart of an embodiment of a payment method of the present invention.
The payment method comprises the following steps:
step S100, the client receives a placing request input by a user and sends the placing request to a payee server.
Specifically, the client is installed in the mobile terminal. The client is an application (e.g., a game client) corresponding to the payee server. The user downloads a client corresponding to a server provided by a game provider on the mobile terminal.
When the user needs to perform payment actions such as recharging and the like on the client, the user can trigger a recharging interface through a recharging module on the client, and select or automatically input recharging types, recharging amounts and the like for determination. The client generates a bill placing request according to the recharging type and the recharging amount input by the user and sends the bill placing request to the payee server.
And step S200, the payee server signs the order placing request according to a preset signature rule to generate order information and sends the order information to the client.
Specifically, the payee server needs to register with a third-party payment platform to obtain the relevant information: appId, appKey, appsource, etc., where appId is used to represent a different application and appsource is used to sign an order request.
And after receiving the order placing request, the payee server signs the order request according to the following signature rules, and further generates order information.
Signature rules:
1, sorting parameters, namely sorting all parameter names in alphabetical order, and if the same initial is met, looking at a second letter, and not allowing parameters without values (such as null and 'case') to participate in signature;
2, the data participating in the signature does not need to be subjected to URL Encoding, and is uniformly encoded by UTF-8 to participate in the signature;
3, a field data _ timestamp is required in the data participating in the signature;
4, parameter splicing, namely splicing all parameters according to a format of k 1-v 1& k 2-v 2& k 3-v 3 …;
and 5, adding:', appId and appsource to the character string obtained in the step 4 to obtain a new character string, and performing summary calculation on the new character string by using md5 to obtain a signature character string (namely, order information with a signature).
Step S300, the client generates request data according to the order information in a preset format, and sends the request data to a payment platform (i.e. the third party payment platform).
Specifically, after the client receives the order information sent by the payee server, a binary protocol header is added to the order information to generate encrypted request data, and the request data is sent to the third-party payment platform.
In this step, the binary protocol header contains 64 bytes, wherein 0-3 bytes represent appId; 4-5 bytes represent the interface number; bytes 6-7 represent the version number; bytes 8-39 represent a session; 40 bytes represent an encryption mode; 41-42 are used for verification; and other byte numbers are reserved. That is, the request data includes a binary protocol header and order information with a signature.
S400, the payment platform decrypts the request data to acquire the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; and encrypting the payment certificate according to a preset encryption mode, and sending the encrypted payment certificate to the client.
Specifically, after the payment platform receives the request data, the payment platform decrypts and analyzes the request data to obtain the order information with the signature included in the request data. And then, verifying the signature, storing the order information after the verification is passed, and generating a payment voucher according to the order information. Then, a binary protocol header is added to the payment credential to encrypt the payment credential. And finally, sending the encrypted payment voucher to the client.
In this step, the binary protocol header contains 32 bytes, where 0-1 byte represents the interface number; 2 bytes represent an encryption mode; 3-4 byte user check; bytes 8-11 represent error codes; the other bytes are reserved. That is, locking the payment credential includes the binary protocol header and the true information of the payment credential.
And S500, the client decrypts the payment certificate and calls a payment tool to carry out payment operation according to the payment information in the payment certificate.
Specifically, after the client receives the payment certificate, the client decrypts the payment certificate to obtain real information contained in the payment certificate, and invokes a payment tool (an application program installed in the mobile terminal, such as a wechat, a payment treasure, a mobile banking, and the like) to perform payment operation according to the real information.
According to the payment method, the interactive data among the client, the payee server and the payment platform are encrypted in different modes, so that the safety of the interactive data is effectively guaranteed, and the safety of payment operation is further guaranteed.
Further, as shown in fig. 2 and fig. 3, fig. 2 is a flowchart of another embodiment of the payment method of the present invention; fig. 3 is a flowchart of the step of feeding back payment success information to the payee server in fig. 2.
Based on the foregoing embodiment, in this embodiment, the payment method further includes:
and S600, after the payment is successful, the payment platform feeds back payment success information to the payee server.
In this embodiment, the step of feeding back payment success information to the payee server includes:
step S610, the payment platform receives the payment success information fed back by the payment instrument, and sends the payment success information to the payee server.
Specifically, after the payment is successful, the payment tool feeds back payment success information to the payment platform to inform the payment platform of changing the order state. And after the payment platform changes the order state into the paid state, sending payment success information to the payee server to inform the payee server of changing the order state.
Step S620, judging whether the payment success information is successfully sent;
if so, the process ends.
If not, step S630 is performed.
And step S630, recording the reason of the failure of the transmission, and transmitting the payment success information again when the preset time is reached.
Specifically, after the payment platform sends the payment success information to the payee server, whether corresponding feedback is received or not is judged, and if not, the sending is determined to be failed. And when the sending is judged to fail, recording the reason of the sending failure, and sending the payment success information to the payee server again after the preset time is up. And circulating the steps until the transmission is successful, or stopping the transmission after the transmission failure times are greater than or equal to the preset times (such as 8 times).
And step S640, when the sending failure times are larger than or equal to the preset times, keeping the reason of the last sending failure, and sending an early warning mail to the payee server.
Specifically, when the number of failed sending times is greater than or equal to the preset number, the reason of the last failed sending time is reserved, and an early warning mail is sent to the payee server
It is worth mentioning that a callback mechanism is arranged in the early warning mail, so that after the operator receives the sent early warning mail, the problem of error is changed, and the manual callback button can be clicked in the mail to execute the step of notifying the payee server of successful payment again.
According to the technical scheme of the embodiment, the success rate of payment is greatly improved through multiple delivery and mail early warning mechanisms, and the experience degree of a user is guaranteed.
The invention further provides a payment system. The payment system of the invention is applied to mobile terminals, but is not limited to mobile terminals. The following description will be made by taking a mobile terminal as an example:
fig. 4 is a block diagram of a payment system according to an embodiment of the present invention, as shown in fig. 4.
The payment system of the embodiment includes a client 110, a payee server 120, a payment platform 130 and a payment tool 140; the client 110 is configured to receive an order placing request input by a user, and send the order placing request to the payee server 120; the payee server 120 is configured to sign the order placing request according to a preset signature rule to generate order information, and send the order information to the client 110; the client 110 is configured to generate request data according to a preset format from the order information, and send the request data to the payment platform 130; the payment platform 130 is configured to decrypt the request data and obtain the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; encrypting the payment voucher according to a preset encryption mode, and sending the encrypted payment voucher to the client 110; the client 110 is configured to decrypt the payment credential and invoke the payment tool 140 according to the payment information in the payment credential; the payment tool 140 is used for performing payment operations.
Specifically, the client 110 is installed in the mobile terminal. The client 110 is an application (e.g., game client 110, etc.) corresponding to the payee server 120. The user downloads a client 110 corresponding to a server provided by a game provider on the mobile terminal. When the user needs to perform payment actions such as recharging on the client 110, the user can trigger a recharging interface through a recharging module on the client 110, and select or automatically input a recharging type, a recharging amount and the like, and determine the recharging type, the recharging amount and the like. The client 110 generates a placing request according to the recharging type and the recharging amount input by the user, and sends the placing request to the payee server 120.
The payee server 120 needs to register with the third party payment platform 130 to obtain the relevant information: appId, appKey, appsource, etc., where appId is used to represent a different application and appsource is used to sign an order request. After the payee server 120 receives the order request, the order request is signed according to the following signature rule, and then order information is generated.
Signature rules:
1, sorting parameters, namely sorting all parameter names in alphabetical order, and if the same initial is met, looking at a second letter, and not allowing parameters without values (such as null and 'case') to participate in signature;
2, the data participating in the signature does not need to be subjected to URL Encoding, and is uniformly encoded by UTF-8 to participate in the signature;
3, a field data _ timestamp is required in the data participating in the signature;
4, parameter splicing, namely splicing all parameters according to a format of k 1-v 1& k 2-v 2& k 3-v 3 …;
and 5, adding:', appId and appsource to the character string obtained in the step 4 to obtain a new character string, and performing summary calculation on the new character string by using md5 to obtain a signature character string (namely, order information with a signature).
After the client 110 receives the order information sent by the payee server 120, a binary protocol header is added to the order information to generate encrypted request data, and the request data is sent to the third party payment platform 130. The binary protocol header comprises 64 bytes, wherein 0-3 bytes represent appId; 4-5 bytes represent the interface number; bytes 6-7 represent the version number; bytes 8-39 represent a session; 40 bytes represent an encryption mode; 41-42 are used for verification; and other byte numbers are reserved. That is, the request data includes a binary protocol header and order information with a signature.
When the payment platform 130 receives the request data, it first decrypts and analyzes the request data to obtain the order information with signature included in the request data. And then, verifying the signature, storing the order information after the signature passes the verification, and generating a payment voucher according to the order information. Then, a binary protocol header is added to the payment credential to encrypt the payment credential. Finally, the encrypted payment credentials are sent to the client 110. The binary protocol header comprises 32 bytes, wherein 0-1 byte represents an interface number; 2 bytes represent an encryption mode; 3-4 byte user check; bytes 8-11 represent error codes; the other bytes are reserved. That is, locking the payment credential includes the binary protocol header and the true information of the payment credential.
After the client 110 receives the payment certificate, it decrypts the payment certificate to obtain the real information contained in the payment certificate, and invokes a payment tool 140 (an application installed in the mobile terminal, such as wechat, a payment treasure, a mobile banking, etc.) to perform a payment operation according to the real information.
The payment system of the embodiment effectively ensures the security of the interactive data by encrypting the interactive data among the client 110, the payee server 120 and the payment platform 130 in different ways, thereby ensuring that the security of the payment operation is improved.
Further, as shown in fig. 5 and 6, fig. 5 is a schematic flow chart of an embodiment of a payment system implementing the present invention; fig. 6 is a block diagram of an embodiment of the payment platform in fig. 4.
Based on the above embodiment, in this embodiment, the payment platform 130 is further configured to feed back payment success information to the payee server 120 after the payment is successful.
The payment platform 130 includes: an execution module 132 and a determination module 134; the execution module 132 is configured to receive payment success information fed back by the payment instrument 140, and send the payment success information to the payee server 120; the judging module 134 is configured to judge whether the payment success information is successfully sent; the executing module 132 is further configured to record a reason for the failure in sending the payment success information after the failure in sending the payment success information, and send the payment success information again when a preset time is reached; the executing module 132 is further configured to, when the sending failure times are greater than or equal to the preset times, reserve the reason of the last sending failure, and send an early warning mail to the payee server 120.
Specifically, after the payment is successful, the payment tool 140 feeds back the payment success information to the payment platform 130 to notify the payment platform 130 of changing the order status. After the payment platform 130 changes the order status to paid, it sends a payment success message to the payee server 120 to notify the payee server 120 of the change of the order status.
After the payment platform 130 sends the payment success information to the payee server 120, it is determined whether a corresponding feedback is received, if yes, the process is ended, and if not, the sending is determined to be failed. When the transmission is determined to fail, the reason of the transmission failure is recorded, and the payment success information is transmitted to the payee server 120 again after the preset time is reached. And circulating the steps until the transmission is successful, or stopping the transmission after the transmission failure times are greater than or equal to the preset times (such as 8 times).
When the number of failed transmissions is greater than or equal to a preset number, the reason of the last failed transmission is retained, and an early warning mail is transmitted to the payee server 120
It should be noted that, a callback mechanism is provided in the early warning mail, so that after receiving the sent early warning mail, the operator changes the problem of error, and can click a "manual callback" button in the mail to execute the above step of notifying the payee server 120 of the successful payment information again.
According to the technical scheme of the embodiment, the success rate of payment is greatly improved through multiple delivery and mail early warning mechanisms, and the experience degree of a user is guaranteed.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (which may be a mobile terminal, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A payment method, comprising the steps of:
the client receives a ordering request input by a user and sends the ordering request to a payee server;
the payee server signs the order placing request according to a preset signature rule to generate order information and sends the order information to the client;
the client generates request data according to the order information in a preset format and sends the request data to a payment platform;
the payment platform decrypts the request data to acquire the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; encrypting the payment certificate according to a preset encryption mode, and sending the encrypted payment certificate to the client;
and the client decrypts the payment certificate and calls a payment tool to carry out payment operation according to the payment information in the payment certificate.
2. A payment method as recited in claim 1, wherein the step of the client generating the order information into request data in a predetermined format comprises:
and adding a binary protocol header in the order information.
3. A payment method as recited in claim 1, wherein the step of encrypting the preset encryption scheme of the payment credential comprises:
adding a binary protocol header to the payment credential.
4. A payment method as recited in any one of claims 1 to 3, further comprising:
and after the payment is successful, the payment platform feeds back payment success information to the payee server.
5. A payment method as recited in claim 4, wherein the step of feeding back payment success information to the payee server comprises:
the payment platform receives payment success information fed back by the payment tool and sends the payment success information to the payee server;
judging whether the payment success information is successfully sent or not;
if not, recording the reason of the failure of sending, and sending the payment success information again when the preset time is reached;
and when the sending failure times are larger than or equal to the preset times, keeping the reason of the last sending failure, and sending an early warning mail to the payee server.
6. A payment system is characterized by comprising a client, a payee server, a payment platform and a payment tool; wherein,
the client is used for receiving a ordering request input by a user and sending the ordering request to the payee server;
the payee server is used for signing the order placing request according to a preset signature rule to generate order information and sending the order information to the client;
the client is used for generating request data according to the order information in a preset format and sending the request data to a payment platform;
the payment platform is used for decrypting the request data and acquiring the order information; verifying the signature of the order information, and generating a payment voucher after the verification is successful; encrypting the payment certificate according to a preset encryption mode, and sending the encrypted payment certificate to the client;
the client is used for decrypting the payment voucher and calling a payment tool according to the payment information in the payment voucher;
the payment tool is used for executing payment operation.
7. A payment system as recited in claim 6, wherein the client is to add a binary protocol header to the request data.
8. A payment system as recited in claim 6, wherein the payment platform is to add a binary protocol header to the payment credential.
9. Payment system according to any one of claims 6 to 8,
and the payment platform is also used for feeding back payment success information to the payee server after the payment is successful.
10. A payment system as recited in claim 9, wherein the payment platform comprises: an execution module and a judgment module; wherein,
the execution module is used for receiving payment success information fed back by the payment tool and sending the payment success information to the payee server;
the judging module is used for judging whether the payment success information is successfully sent;
the execution module is further used for recording the reason of the failure in sending after the successful payment information is failed to be sent, and sending the successful payment information again when the preset time is reached;
and the execution module is also used for keeping the reason of the last sending failure when the sending failure times are more than or equal to the preset times, and sending an early warning mail to the payee server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611061175.9A CN106779702A (en) | 2016-11-28 | 2016-11-28 | Method of payment and payment system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611061175.9A CN106779702A (en) | 2016-11-28 | 2016-11-28 | Method of payment and payment system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106779702A true CN106779702A (en) | 2017-05-31 |
Family
ID=58913361
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611061175.9A Pending CN106779702A (en) | 2016-11-28 | 2016-11-28 | Method of payment and payment system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106779702A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203880A (en) * | 2017-06-01 | 2017-09-26 | 徐涛 | A kind of method and apparatus paid based on order |
| CN107862587A (en) * | 2017-12-04 | 2018-03-30 | 深圳春沐源控股有限公司 | A kind of ordering method and system |
| CN108596715A (en) * | 2018-04-10 | 2018-09-28 | 沈文策 | A kind of method of network payment, device, electronic equipment and readable storage medium storing program for executing |
| CN109104283A (en) * | 2018-06-26 | 2018-12-28 | 北京云迹科技有限公司 | intelligent distribution system communication encryption method and device |
| CN110097349A (en) * | 2018-01-29 | 2019-08-06 | 腾讯科技（深圳）有限公司 | Method for processing resource, device and storage medium |
| WO2019218817A1 (en) * | 2018-05-15 | 2019-11-21 | 腾讯科技（深圳）有限公司 | Payment method, apparatus, related device, and system |
| CN110956474A (en) * | 2019-01-29 | 2020-04-03 | 深圳市智税链科技有限公司 | Electronic invoice system based on block chain |
| CN112101937A (en) * | 2020-09-01 | 2020-12-18 | 武汉华盛美业科技有限公司 | Order safety payment method and system |
| CN112633883A (en) * | 2020-12-30 | 2021-04-09 | 爱驰汽车有限公司 | Secure payment method, device, server and storage medium |
| CN112950178A (en) * | 2021-02-25 | 2021-06-11 | 中钞信用卡产业发展有限公司 | B2B proxy payment method and system based on license chain |
| CN115018486A (en) * | 2022-06-06 | 2022-09-06 | 易联支付有限公司 | Unified payment system |
| CN116629871A (en) * | 2023-07-21 | 2023-08-22 | 济南正浩软件科技有限公司 | Order online payment system and payment method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008099138A (en) * | 2006-10-13 | 2008-04-24 | Toshiba Corp | Anonymous order system, apparatus and program |
| CN102194176A (en) * | 2010-03-19 | 2011-09-21 | 中国工商银行股份有限公司 | Method and system for feeding back payment result information by online bank |
| CN102801710A (en) * | 2012-07-04 | 2012-11-28 | 北京天龙融和软件有限公司 | Networked transaction method and system |
| CN103607339A (en) * | 2013-09-11 | 2014-02-26 | 北京京东尚科信息技术有限公司 | Method and system based on content automatic adjustment mail sending strategy |
-
2016
- 2016-11-28 CN CN201611061175.9A patent/CN106779702A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008099138A (en) * | 2006-10-13 | 2008-04-24 | Toshiba Corp | Anonymous order system, apparatus and program |
| CN102194176A (en) * | 2010-03-19 | 2011-09-21 | 中国工商银行股份有限公司 | Method and system for feeding back payment result information by online bank |
| CN102801710A (en) * | 2012-07-04 | 2012-11-28 | 北京天龙融和软件有限公司 | Networked transaction method and system |
| CN103607339A (en) * | 2013-09-11 | 2014-02-26 | 北京京东尚科信息技术有限公司 | Method and system based on content automatic adjustment mail sending strategy |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203880A (en) * | 2017-06-01 | 2017-09-26 | 徐涛 | A kind of method and apparatus paid based on order |
| CN107862587A (en) * | 2017-12-04 | 2018-03-30 | 深圳春沐源控股有限公司 | A kind of ordering method and system |
| CN110097349B (en) * | 2018-01-29 | 2023-08-04 | 腾讯科技（深圳）有限公司 | Resource processing method, device and storage medium |
| CN110097349A (en) * | 2018-01-29 | 2019-08-06 | 腾讯科技（深圳）有限公司 | Method for processing resource, device and storage medium |
| CN108596715A (en) * | 2018-04-10 | 2018-09-28 | 沈文策 | A kind of method of network payment, device, electronic equipment and readable storage medium storing program for executing |
| US11461745B2 (en) | 2018-05-15 | 2022-10-04 | Tencent Technology (Shenzhen) Company Ltd | Payment method and apparatus, related device, and system |
| US11769123B2 (en) | 2018-05-15 | 2023-09-26 | Tencent Technology (Shenzhen) Company Ltd | Payment method and apparatus, related device, and system |
| WO2019218817A1 (en) * | 2018-05-15 | 2019-11-21 | 腾讯科技（深圳）有限公司 | Payment method, apparatus, related device, and system |
| CN109104283B (en) * | 2018-06-26 | 2022-01-11 | 北京云迹科技有限公司 | Intelligent distribution system communication encryption method and device |
| CN109104283A (en) * | 2018-06-26 | 2018-12-28 | 北京云迹科技有限公司 | intelligent distribution system communication encryption method and device |
| CN110956474A (en) * | 2019-01-29 | 2020-04-03 | 深圳市智税链科技有限公司 | Electronic invoice system based on block chain |
| CN110956474B (en) * | 2019-01-29 | 2024-02-27 | 深圳市智税链科技有限公司 | Electronic invoice system based on block chain |
| CN112101937A (en) * | 2020-09-01 | 2020-12-18 | 武汉华盛美业科技有限公司 | Order safety payment method and system |
| CN112633883A (en) * | 2020-12-30 | 2021-04-09 | 爱驰汽车有限公司 | Secure payment method, device, server and storage medium |
| CN112950178A (en) * | 2021-02-25 | 2021-06-11 | 中钞信用卡产业发展有限公司 | B2B proxy payment method and system based on license chain |
| CN112950178B (en) * | 2021-02-25 | 2023-09-12 | 中钞信用卡产业发展有限公司 | B2B proxy payment method and system based on license chain |
| CN115018486A (en) * | 2022-06-06 | 2022-09-06 | 易联支付有限公司 | Unified payment system |
| CN116629871A (en) * | 2023-07-21 | 2023-08-22 | 济南正浩软件科技有限公司 | Order online payment system and payment method |
| CN116629871B (en) * | 2023-07-21 | 2023-10-17 | 济南正浩软件科技有限公司 | Order online payment system and payment method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106779702A (en) | Method of payment and payment system | |
| KR101354898B1 (en) | Electronic commerce transactions over a peer-to-peer communications channel | |
| US8949935B2 (en) | Secure account creation | |
| CN102065077B (en) | Method and system for distributing application software to terminal | |
| US8261080B2 (en) | System and method for managing digital certificates on a remote device | |
| CN110414190B (en) | Signature method of application installation package, related device, storage medium and electronic equipment | |
| WO2007058907A2 (en) | Systems and methods for trusted information exchange | |
| CN106296144A (en) | Payment processes server, client and payment processing method | |
| US20090063859A1 (en) | Content distribution server and content distribution system using the same | |
| CA2355928C (en) | Method and system for implementing a digital signature | |
| WO2023005838A1 (en) | Data sharing method and electronic device | |
| CN109460247B (en) | Software package upgrading method, software client, storage medium and device | |
| CN112887340B (en) | Password resetting method and device, service management terminal and storage medium | |
| CN111970109A (en) | Data transmission method and system | |
| CN107645481B (en) | Data processing method, system and device | |
| CN112261002B (en) | Data interface docking method and device | |
| CN104426865A (en) | Method, device and system for controlling presentation of application | |
| CN112927026A (en) | Coupon processing method and device, electronic equipment and computer storage medium | |
| KR20100019165A (en) | System and method for providing internet banking service | |
| CN109151068B (en) | Method and system for processing cloud-end data request based on client-end application | |
| CN109471723B (en) | Method and system for verifying processing result of task | |
| CN102006567A (en) | Push-message processing method and system and equipment for implementing push-message processing method | |
| CN112994882B (en) | Authentication method, device, medium and equipment based on block chain | |
| CN113221074B (en) | Offline authorization method | |
| CN112583816B (en) | Login verification method, login verification device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170531 |