CN115994763A - Trusted intelligent payment method and system - Google Patents
Trusted intelligent payment method and system Download PDFInfo
- Publication number
- CN115994763A CN115994763A CN202310292424.9A CN202310292424A CN115994763A CN 115994763 A CN115994763 A CN 115994763A CN 202310292424 A CN202310292424 A CN 202310292424A CN 115994763 A CN115994763 A CN 115994763A
- Authority
- CN
- China
- Prior art keywords
- payment
- trusted
- request
- information
- payer
- 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
Images
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention provides a trusted intelligent payment method and a system. A trusted smart payment method, the method comprising: after receiving the payment request, collecting payment verification information, carrying out identity verification on the payer based on the payer information, carrying out identity verification on the payee based on the payer information to complete first verification on the payment request, obtaining a first verification result, and judging whether to carry out second verification on the payment request according to the first verification result. According to the trusted intelligent payment method and system, the payment request sent by the payer is audited based on the pre-established trusted database, when the request place corresponding to the payment request and the paid party are recorded in the trusted database, the payment request is agreed and executed, the payment work is completed more conveniently, and if at least one of the request place corresponding to the payment request and the paid party is not recorded in the database, the payment request is verified more strictly, and the payment safety is improved.
Description
Technical Field
The invention relates to the technical field of network payment, in particular to a trusted intelligent payment method and a system.
Background
Payment may be a financial exchange that occurs between a purchaser and a consumer, and has become one of the payment means that people use daily with the large-scale construction of networks and the popularity of various electronic devices.
In some network payment processes, the payment information is encrypted and decrypted between the payer and the payee based on an encryption and decryption algorithm, so that identity authentication of the payer and the payee and safety detection of the payment process are completed.
Disclosure of Invention
The invention provides a trusted intelligent payment method and a trusted intelligent payment system, which are used for solving at least one technical problem in the background technology.
As one aspect of the present invention, there is provided a trusted smart payment method, the method comprising:
after receiving the payment request, collecting payment verification information, wherein the payment verification information comprises payer information and paid party information;
carrying out identity verification on a payer based on payer information, wherein the payer information comprises payer basic information, a current payment place and a trusted payment place, and matching the current payment place with the trusted payment place to obtain a first matching result; carrying out identity verification on a paid party based on the information of the paid party, wherein the information of the paid party comprises trusted payment object information and current payment object information, matching the current payment object information with the trusted payment object information to obtain a second matching result, completing first verification of a payment request, and obtaining a first verification result, wherein the first verification result comprises a first matching result and a second matching result;
judging whether to carry out second verification on the payment request according to the first verification result, and if the first matching result and the second matching result are both successful in matching, completing the payment through the payment request; if the first matching result and the second matching result are both matching failure, rejecting the payment request; otherwise, carrying out second verification on the payment request;
the second validation of the payment request includes:
if the first matching result is successful matching and the second matching result is failed matching, generating a payment object authorization request based on the information of the paid party, if the payment object authorization request passing information is received within a preset duration, completing the payment through the payment request, otherwise rejecting the payment request;
if the first matching result is failed in matching and the second matching result is successful in matching, acquiring travel information, calculating a reference speed according to the travel information, judging whether the reference speed is greater than a preset speed threshold, rejecting the payment request if yes, otherwise judging whether the payment amount corresponding to the payment request is less than the preset payment threshold, and if the payment amount corresponding to the payment request is less than the preset payment threshold, completing the payment by the payment request;
if the payment amount corresponding to the payment request is larger than or equal to a preset payment threshold value, a payment authorization request is generated based on the payment request, if the payment authorization request passing information is received within a preset duration, the payment is completed through the payment request, and otherwise, the payment request is refused.
Further, the collecting payment verification information includes:
the payment request comprises payment party basic information, payment request time, current payment place, current payment object information and payment amount, the payment party basic information, the current payment place and the current payment object information are extracted from the payment request, the trusted payment place and the trusted payment object information are extracted from the trusted database, and payment verification information is acquired.
Further, the establishment of the trusted database includes:
acquiring historical payment data of a payer, wherein the historical payment data comprises a plurality of payment transaction items, and any payment transaction item comprises a payment number, a payment place, a payment object, a payment amount and a payment time;
dividing the historical payment data according to the payment places and establishing m place subsets Ai, i=1, 2 ⋯, m, m are the total number of different payment places in the historical payment data; dividing historical payment data according to the payment objects and establishing n object subsets Bj, j=1, 2 ⋯, n, n are the total number of different payment objects in the historical payment data, and payment transaction items in m place subsets and n object subsets are arranged in time sequence;
for any place subset Ai, traversing the place subset Ai by using a preset time length range, wherein the step length is 1, and if the number of payment transaction items in any preset time length range is greater than or equal to the preset credible number, marking the payment place corresponding to the place subset Ai as a credible payment place;
traversing the object subset Bj by using a preset duration range for any one object subset Bj, wherein the step length is 1, and if the number of payment transaction items in any preset duration range is greater than or equal to the preset trusted number, marking the payment object corresponding to the object subset Bj as a trusted payment object;
after traversing m place subsets Ai and n object subsets Bj by using a preset duration range, constructing and obtaining a trusted database based on all trusted payment places and all trusted payment objects obtained by marking.
Further, for the trusted database, further comprising:
for the trusted payment location and the trusted payment object stored in the trusted database, performing a time-dependent check of the trusted payment location and the trusted payment object based on historical payment data of the payer;
for any one of the trusted payment locations, based on historical payment data of a payer, if it is monitored that the payment location of any one payment transaction item does not exist within a preset risk duration is the trusted payment location, marking the trusted payment location as a risk payment location;
for any one of the trusted payment objects, based on historical payment data of a payer, if the fact that the payment object of any one payment transaction item does not exist within the preset risk duration is monitored to be the trusted payment object, marking the trusted payment object as a risk payment object;
after receiving any payment request, if the collected payment verification information corresponding to the payment request has a risk payment place and/or a risk payment object, the payer needs to perform trusted payment authorization on the risk payment place and/or the risk payment object in the payment verification information corresponding to the payment request, otherwise, the payment request is refused.
Further, the method further comprises the following steps:
for any trusted payment object stored in the trusted database, the trusted payment amount of the trusted payment object can also be determined according to the historical payment data of the payer;
for the target payment request, if the target payment object corresponding to the target payment request is successfully matched with the trusted payment object, the target payment amount is also compared with the trusted payment amount corresponding to the target payment object, if the target payment amount is smaller than or equal to the trusted payment amount corresponding to the target payment object, the target payment request is passed, and if the target payment amount is not smaller than or equal to the trusted payment amount corresponding to the target payment object, the excessive payment permission is granted to the payer, and then the target payment request can be passed.
Further, the determining the trusted payment amount of the trusted payment object based on the historical payment data of the payer includes:
extracting a target payment transaction item related to the trusted payment object from historical payment data of a payment party, calculating an average value Qj of the payment amount corresponding to the target payment transaction item, calculating a standard deviation Qb of the payment amount corresponding to the target payment transaction item, taking the ratio of the standard deviation of the payment amount to the average value of the payment amount as a fluctuation coefficient alpha, comparing the maximum value Qz of the payment amount corresponding to the target payment transaction item with Qj (1+alpha), and taking the maximum value of the two as the trusted payment amount of the trusted payment object;
only after the number of target payment transaction items related to the trusted payment object is greater than a preset trusted number, determining a trusted payment amount of the trusted payment object according to historical payment data of a payer;
the trusted payment amount of any trusted payment object will be redetermined after the payer grants excess payment rights to that trusted payment object.
As another aspect of the present invention, there is provided a trusted smart payment system applied to a trusted smart payment method provided in any one of the above, the system comprising:
the information receiving module is used for receiving a payment request sent by a payment party;
the database construction module is used for constructing a trusted database according to historical payment data of a payer;
the information acquisition module is used for extracting payment verification information corresponding to the payment request from the payment request and the trusted database;
and the identity verification module is used for verifying the payment request according to the payment verification information.
Further, for the database construction module, the method further includes:
and the parameter calculation unit is used for calculating the trusted payment amount of the trusted payment object according to the historical payment data of the payer.
Compared with the prior art, the invention has the beneficial effects that:
according to the invention, the payment request sent by the payer is audited based on the pre-established trusted database, when the request place corresponding to the payment request and the paid party are recorded in the trusted database, the payment request is agreed and executed, the payment work is completed more conveniently, and if at least one of the request place corresponding to the payment request and the paid party is not recorded in the database, the payment request is verified more strictly, and the payment safety is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the structures shown in these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a trusted intelligent payment method provided in embodiment 1 of the present invention.
Fig. 2 is a schematic structural diagram of a trusted intelligent payment system provided in embodiment 2 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, some embodiments of the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application. However, those of ordinary skill in the art will understand that in the various embodiments of the present application, numerous technical details have been set forth in order to provide a better understanding of the present application. However, the technical solutions claimed in the present application can be implemented without these technical details and with various changes and modifications based on the following embodiments.
Example 1
Referring to fig. 1, embodiment 1 of the present invention provides a trusted smart payment method, including the following steps:
s1, after a payment request is received, collecting payment verification information;
illustratively, the payment request includes at least payment party base information, a payment request time, a current payment location, current payment object information, and a payment amount, wherein the payment party base information is used to represent an identity of a payment party, and the current payment location is a location where the payment request is issued; the payment verification information comprises payer information and payee information, wherein the payment verification information can be acquired from a payment request and a trusted database, and the trusted payment place and trusted payment object information are recorded in the payment database; it should be added that the location described in this solution is not a specific location, but a marked area, such as a town, street, campus, etc.
S2, performing first verification on the payment request to obtain a first verification result; the first verification result comprises a first matching result and a second matching result;
the first verification of the payment request is specifically, illustratively, an authentication of the payer based on the payer information and an authentication of the payee based on the payee information;
specifically, the payer information at least comprises payer basic information, a current payment location and a trusted payment location, the current payment location and the trusted payment location are matched to obtain a first matching result, the paid party information at least comprises trusted payment object information and current payment object information, the current payment object information and the trusted payment object information are matched to obtain a second matching result, and the first matching result and the second matching result are both represented as successful matching or failed matching.
S3, judging whether to perform second verification on the payment request according to the first verification result;
for example, if the first matching result and the second matching result are both successful in matching, the payment request is passed; if the first matching result and the second matching result are both matching failure, rejecting the payment request; otherwise, performing a second verification on the payment request;
s4, completing verification of the payment request.
For step S3, the second verification of the payment request includes:
if the first matching result is successful matching and the second matching result is failed matching, generating a payment object authorization request based on the information of the paid party, if the payment object authorization request passing information is received within a preset duration, completing the payment through the payment request, otherwise rejecting the payment request;
illustratively, a second match result of a match failure indicates that the payee does not belong to a trusted payment object, indicating that there is a risk of payment, in which case the payee needs to make an authorization if he/she needs to pay to the payee.
If the first matching result is failed in matching and the second matching result is successful in matching, acquiring travel information, calculating a reference speed according to the travel information, judging whether the reference speed is greater than a preset speed threshold, rejecting the payment request if yes, otherwise judging whether the payment amount corresponding to the payment request is less than the preset payment threshold, and if the payment amount corresponding to the payment request is less than the preset payment threshold, completing the payment by the payment request;
if the payment amount corresponding to the payment request is larger than or equal to a preset payment threshold value, a payment authorization request is generated based on the payment request, if the payment authorization request passing information is received within a preset duration, the payment is completed through the payment request, and otherwise, the payment request is refused.
The first matching result is that the location where the payment request is sent is not in a trusted payment location, which may be the case when the payment account logs in elsewhere, for example, the travel information may be collected in this case, it is required to supplement that the travel information may be collected by a mobile device bound to the payer, the current payment location and the payment request time are the first reference point, and the collected travel information may be calculated to obtain a reference speed, the preset speed threshold may be set with reference to the speed of the current travel device, and the reference speed is greater than the preset speed threshold, which indicates that the payment account logs in elsewhere, and the payment request is rejected for ensuring payment security; the reference speed being less than or equal to the preset speed threshold indicates that the travel of the payer is reasonable, but because the location from which the payment request is issued does not belong to a trusted payment location, in order to ensure security, if the payment amount corresponding to the payment request is greater than the preset payment threshold, the payer needs to be authorized.
It should be added that the payment party authorization can be verification authorization by means of face recognition, password verification, fingerprint identification and the like, and it is conceivable that the payment party authorization needs to be operated by trusted equipment in order to ensure security.
According to the trusted intelligent payment method provided by the embodiment 1 of the invention, the payment request sent by the payer is audited based on the trusted database, when the request place corresponding to the payment request and the paid party are recorded in the trusted database, the payment request is agreed and executed, the payment work is completed more conveniently, the more complex verification of the payment process is not needed, and if at least one of the request place corresponding to the payment request and the paid party is not recorded in the database, the more strict verification of the payment request is carried out, and the payment safety is improved.
As a preferred embodiment, the establishment of the trusted database comprises the following:
acquiring historical payment data of a payer;
illustratively, the historical payment data includes a plurality of payment transaction items, any one of which includes information including at least a payment number, a payment location, a payment object, a payment amount, and a payment time; it should be added that, in order to ensure the validity of the data, only data within a certain range is acquired in the process of acquiring the historical payment data of the payer, which is exemplified by three years in the present embodiment.
Dividing the historical payment data according to the payment places and establishing m place subsets Ai, i=1, 2 ⋯, m, m are the total number of different payment places in the historical payment data; dividing historical payment data according to the payment objects and establishing n object subsets Bj, j=1, 2 ⋯, n, n are the total number of different payment objects in the historical payment data, wherein payment transaction items in m place subsets and n object subsets are arranged in time sequence; specifically, in the present embodiment, payment transaction items are ordered in a near-far manner in time.
For any place subset Ai, traversing the place subset Ai by using a preset time length range, wherein the step length is 1, and if the number of payment transaction items in any preset time length range is greater than or equal to the preset credible number, marking the payment place corresponding to the place subset Ai as a credible payment place;
for any place subset Ai, a first element is taken as a reference point, a first reference time can be obtained according to a payment time corresponding to the first element and a preset duration range, the number of payment transaction items in the payment time corresponding to the first element and the first reference time range is counted, if the number of the payment transaction items is smaller than the preset trusted number, the next element is taken as the reference point, the operation is stopped until a counted number is larger than or equal to the preset trusted number, the payment place corresponding to the place subset Ai is marked as a trusted payment place, and similarly, for the following, whether the payment object corresponding to any one object subset Bj belongs to a trusted payment object is determined in the same manner.
Traversing the object subset Bj by using a preset duration range for any one object subset Bj, wherein the step length is 1, and if the number of payment transaction items in any preset duration range is greater than or equal to the preset trusted number, marking the payment object corresponding to the object subset Bj as a trusted payment object;
after traversing m place subsets Ai and n object subsets Bj by using a preset duration range, constructing and obtaining a trusted database based on all trusted payment places and all trusted payment objects obtained by marking, and completing the establishment of the trusted database.
It should be added that the payer may manually add the trusted payment location and all trusted payment objects to the trusted database according to actual needs, but the addition process needs to be strictly authenticated, such as biometric authentication, password authentication, etc. at the same time.
As a preferred embodiment, for the trusted database, further comprising:
for the trusted payment place and the trusted payment object stored in the trusted database, performing timeliness check on the trusted payment place and the trusted payment object based on the historical payment data of the payer, wherein the timeliness check comprises the following specific contents:
for any one of the trusted payment locations, based on historical payment data of a payer, if it is monitored that the payment location of any one payment transaction item does not exist within a preset risk duration is the trusted payment location, marking the trusted payment location as a risk payment location;
and for any one of the trusted payment objects, based on the historical payment data of the payer, if the fact that the payment object of any one payment transaction item does not exist within the preset risk duration is monitored to be the trusted payment object, marking the trusted payment object as a risk payment object.
For any trusted payspot or trusted payment object, when it is detected that the payor has no payment transaction item related to the trusted payspot or trusted payment object for six consecutive months, risk marking is performed for the corresponding trusted payspot or trusted payment object in order to ensure the payment security.
After receiving any payment request, if the collected payment verification information corresponding to the payment request has a risk payment place and/or a risk payment object, in order to ensure the payment security, a payer needs to perform trusted payment authorization on the risk payment place and/or the risk payment object in the payment verification information corresponding to the payment request, otherwise, the payment request is refused.
As a more preferred embodiment, for any trusted payment object stored in the trusted database, the trusted payment amount of the trusted payment object may also be determined from historical payment data of the payer; illustratively, the trusted payment amount is determined by:
extracting a target payment transaction item related to the trusted payment object from historical payment data of a payment party, calculating an average value Qj of the payment amount corresponding to the target payment transaction item, calculating a standard deviation Qb of the payment amount corresponding to the target payment transaction item, taking the ratio of the standard deviation of the payment amount to the average value of the payment amount as a fluctuation coefficient alpha, comparing the maximum value Qz of the payment amount corresponding to the target payment transaction item with Qj (1+alpha), and taking the maximum value of the two as the trusted payment amount of the trusted payment object;
it should be added that, the payment level is measured by the average value Qj of the payment amount, the fluctuation of the payment is measured by the standard deviation Qb of the payment amount, and the glass-plastic coefficient alpha is calculated based on the average value Qj and the standard deviation Qb, wherein: α=qb/Qj, taking Qj (1+α) as a reference value in consideration of fluctuation of the payment amount, and taking a larger value of both Qj (1+α) and the maximum value Qz of the payment amount as an amount reference value in consideration of the difference of the payment amounts, i.e., a trusted payment amount.
It should be added that, for any trusted payment object, in order to ensure that the data has a more reference value, the trusted payment amount of the trusted payment object is determined according to the historical payment data of the payer only after the number of target payment transaction items related to the trusted payment object is greater than the preset trusted number.
In a preferred embodiment, in the process of verifying the target payment request, after the target payment object corresponding to the target payment request is successfully matched with the trusted payment object, the target payment amount is compared with the trusted payment amount corresponding to the target payment object, if the target payment amount is smaller than or equal to the trusted payment amount corresponding to the target payment object, the target payment request is passed, and otherwise, the excessive payment permission is granted to the payer.
It is necessary to supplement that the above operation is only performed for the target payment object with the trusted payment amount, and when the payer grants excess payment authority to any one of the trusted payment objects, the above method is repeated to redetermine the trusted payment amount of the trusted payment object, thereby ensuring the validity of the data.
Example 2
Referring to fig. 2, on the basis of embodiment 1, embodiment 2 of the present invention provides a trusted smart payment system, the system comprising:
the information receiving module is used for receiving a payment request sent by a payer, wherein the payment request at least comprises base information of the payer, payment request time, current payment place, current payment object information and payment amount;
the database construction module is used for constructing a trusted database according to historical payment data of a payer;
the information acquisition module is used for extracting payment verification information corresponding to the payment request from the payment request and the trusted database, wherein the payment verification information comprises payer information and payee information, and the payer information at least comprises payer basic information, a current payment place and a trusted payment place; the paid party information at least comprises trusted payment object information and current payment object information;
the identity verification module is used for verifying the payment request according to the payment verification information;
specifically, verifying the payment request according to the payment verification information comprises verifying the payment request for the first time to obtain a first verification result, wherein the first verification result comprises a first matching result and a second matching result, and if the first matching result and the second matching result are both successful in matching, the payment request is passed; if the first matching result and the second matching result are both matching failure, rejecting the payment request; otherwise, performing a second verification on the payment request;
for the database construction module, further comprising:
a parameter calculation unit for calculating a trusted payment amount of the trusted payment object from the historical payment data of the payer, specifically, obtaining the trusted payment amount by:
extracting a target payment transaction item related to the trusted payment object from historical payment data of a payment party, calculating an average value Qj of the payment amount corresponding to the target payment transaction item, calculating a standard deviation Qb of the payment amount corresponding to the target payment transaction item, taking the ratio of the standard deviation of the payment amount to the average value of the payment amount as a fluctuation coefficient alpha, comparing the maximum value Qz of the payment amount corresponding to the target payment transaction item with Qj (1+alpha), and taking the maximum value of the two as the trusted payment amount of the trusted payment object.
It will be understood that modifications and variations will be apparent to those skilled in the art from the foregoing description, and it is intended that all such modifications and variations be included within the scope of the following claims. Parts of the specification not described in detail belong to the prior art known to those skilled in the art.
Claims (8)
1. A trusted intelligent payment method, the method comprising:
after receiving the payment request, collecting payment verification information, wherein the payment verification information comprises payer information and paid party information;
carrying out identity verification on a payer based on payer information, wherein the payer information comprises payer basic information, a current payment place and a trusted payment place, and matching the current payment place with the trusted payment place to obtain a first matching result; carrying out identity verification on a paid party based on the information of the paid party, wherein the information of the paid party comprises trusted payment object information and current payment object information, matching the current payment object information with the trusted payment object information to obtain a second matching result, completing first verification of a payment request, and obtaining a first verification result, wherein the first verification result comprises a first matching result and a second matching result;
judging whether to carry out second verification on the payment request according to the first verification result, and if the first matching result and the second matching result are both successful in matching, completing the payment through the payment request; if the first matching result and the second matching result are both matching failure, rejecting the payment request; otherwise, carrying out second verification on the payment request;
the second validation of the payment request includes:
if the first matching result is successful matching and the second matching result is failed matching, generating a payment object authorization request based on the information of the paid party, if the payment object authorization request passing information is received within a preset duration, completing the payment through the payment request, otherwise rejecting the payment request;
if the first matching result is failed in matching and the second matching result is successful in matching, acquiring travel information, calculating a reference speed according to the travel information, judging whether the reference speed is greater than a preset speed threshold, rejecting the payment request if yes, otherwise judging whether the payment amount corresponding to the payment request is less than the preset payment threshold, and if the payment amount corresponding to the payment request is less than the preset payment threshold, completing the payment by the payment request;
if the payment amount corresponding to the payment request is larger than or equal to a preset payment threshold value, a payment authorization request is generated based on the payment request, if the payment authorization request passing information is received within a preset duration, the payment is completed through the payment request, and otherwise, the payment request is refused.
2. A trusted smart payment method as claimed in claim 1, wherein said collecting payment verification information comprises:
the payment request comprises payment party basic information, payment request time, current payment place, current payment object information and payment amount, the payment party basic information, the current payment place and the current payment object information are extracted from the payment request, the trusted payment place and the trusted payment object information are extracted from a trusted database corresponding to the payment party, and payment verification information is acquired.
3. A trusted smart payment method as claimed in claim 2, wherein the establishment of the trusted database comprises:
acquiring historical payment data of a payer, wherein the historical payment data comprises a plurality of payment transaction items, and any payment transaction item comprises a payment number, a payment place, a payment object, a payment amount and a payment time;
dividing the historical payment data according to the payment places and establishing m place subsets Ai, i=1, 2 ⋯, m, m are the total number of different payment places in the historical payment data; dividing historical payment data according to the payment objects and establishing n object subsets Bj, j=1, 2 ⋯, n, n are the total number of different payment objects in the historical payment data, and payment transaction items in m place subsets and n object subsets are arranged in time sequence;
for any place subset Ai, traversing the place subset Ai by using a preset time length range, wherein the step length is 1, and if the number of payment transaction items in any preset time length range is greater than or equal to the preset credible number, marking the payment place corresponding to the place subset Ai as a credible payment place;
traversing the object subset Bj by using a preset duration range for any one object subset Bj, wherein the step length is 1, and if the number of payment transaction items in any preset duration range is greater than or equal to the preset trusted number, marking the payment object corresponding to the object subset Bj as a trusted payment object;
after traversing m place subsets Ai and n object subsets Bj by using a preset duration range, constructing and obtaining a trusted database based on all trusted payment places and all trusted payment objects obtained by marking.
4. A trusted smart payment method as claimed in claim 3, wherein for the trusted database, further comprising:
for the trusted payment location and the trusted payment object stored in the trusted database, performing a time-dependent check of the trusted payment location and the trusted payment object based on historical payment data of the payer;
for any one of the trusted payment locations, based on historical payment data of a payer, if it is monitored that the payment location of any one payment transaction item does not exist within a preset risk duration is the trusted payment location, marking the trusted payment location as a risk payment location;
for any one of the trusted payment objects, based on historical payment data of a payer, if the fact that the payment object of any one payment transaction item does not exist within the preset risk duration is monitored to be the trusted payment object, marking the trusted payment object as a risk payment object;
after receiving any payment request, if the collected payment verification information corresponding to the payment request has a risk payment place and/or a risk payment object, the payer needs to perform trusted payment authorization on the risk payment place and/or the risk payment object in the payment verification information corresponding to the payment request, otherwise, the payment request is refused.
5. A trusted smart payment method as claimed in claim 4, further comprising:
for any trusted payment object stored in the trusted database, the trusted payment amount of the trusted payment object can also be determined according to the historical payment data of the payer;
for the target payment request, if the target payment object corresponding to the target payment request is successfully matched with the trusted payment object, the target payment amount is also compared with the trusted payment amount corresponding to the target payment object, if the target payment amount is smaller than or equal to the trusted payment amount corresponding to the target payment object, the target payment request is passed, and if the target payment amount is not smaller than or equal to the trusted payment amount corresponding to the target payment object, the excessive payment permission is granted to the payer, and then the target payment request can be passed.
6. The trusted smart payment method of claim 5, wherein said determining a trusted payment amount for the trusted payment object based on historical payment data for the payer includes:
extracting a target payment transaction item related to the trusted payment object from historical payment data of a payment party, calculating an average value Qj of the payment amount corresponding to the target payment transaction item, calculating a standard deviation Qb of the payment amount corresponding to the target payment transaction item, taking the ratio of the standard deviation of the payment amount to the average value of the payment amount as a fluctuation coefficient alpha, comparing the maximum value Qz of the payment amount corresponding to the target payment transaction item with Qj (1+alpha), and taking the maximum value of the two as the trusted payment amount of the trusted payment object;
only after the number of target payment transaction items related to the trusted payment object is greater than a preset trusted number, determining a trusted payment amount of the trusted payment object according to historical payment data of a payer;
the trusted payment amount of any trusted payment object will be redetermined after the payer grants excess payment rights to that trusted payment object.
7. A trusted smart payment system for use in a trusted smart payment method as claimed in any one of claims 1 to 6, said system comprising:
the information receiving module is used for receiving a payment request sent by a payment party;
the database construction module is used for constructing a trusted database according to historical payment data of a payer;
the information acquisition module is used for extracting payment verification information corresponding to the payment request from the payment request and the trusted database;
and the identity verification module is used for verifying the payment request according to the payment verification information.
8. A trusted smart payment system as claimed in claim 7, wherein for the database building module, further comprising:
and the parameter calculation unit is used for calculating the trusted payment amount of the trusted payment object according to the historical payment data of the payer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310292424.9A CN115994763B (en) | 2023-03-23 | 2023-03-23 | Trusted intelligent payment method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310292424.9A CN115994763B (en) | 2023-03-23 | 2023-03-23 | Trusted intelligent payment method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115994763A true CN115994763A (en) | 2023-04-21 |
| CN115994763B CN115994763B (en) | 2023-09-01 |
Family
ID=85995422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310292424.9A Active CN115994763B (en) | 2023-03-23 | 2023-03-23 | Trusted intelligent payment method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115994763B (en) |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855555A (en) * | 2012-08-06 | 2013-01-02 | 北京中科金财电子商务有限公司 | System and method for identifying payment risks based on position transformation |
| WO2015062229A1 (en) * | 2013-10-30 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus, and system for secure payment |
| CA2992421A1 (en) * | 2015-07-21 | 2017-01-26 | Early Warning Services, Llc | Secure real-time payment transactions |
| CN107730255A (en) * | 2017-09-28 | 2018-02-23 | 努比亚技术有限公司 | A kind of safe payment method, terminal and computer-readable recording medium |
| CN108256853A (en) * | 2018-01-11 | 2018-07-06 | 维沃移动通信有限公司 | A kind of method of payment and mobile terminal |
| CN109165942A (en) * | 2018-08-17 | 2019-01-08 | 苏州诚满信息技术有限公司 | A kind of user ID authentication method and its system for mobile payment |
| CN110751488A (en) * | 2019-10-21 | 2020-02-04 | 深圳传音控股股份有限公司 | Intelligent terminal safety payment method, terminal and medium |
| CN111784356A (en) * | 2020-07-22 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | Payment verification method, device, equipment and storage medium |
| CN112184239A (en) * | 2020-09-23 | 2021-01-05 | 支付宝(杭州)信息技术有限公司 | Secure payment method, device, equipment and readable medium |
| CN112669042A (en) * | 2021-03-15 | 2021-04-16 | ***股份有限公司 | Payment method, server, user terminal, system and storage medium |
| CN113065870A (en) * | 2021-04-13 | 2021-07-02 | 梁万钢 | Safety payment method and system based on artificial intelligence and big data and cloud platform |
| CN113112274A (en) * | 2021-04-12 | 2021-07-13 | 支付宝(杭州)信息技术有限公司 | Payment information processing method, device, equipment and medium |
| CN114358761A (en) * | 2022-03-16 | 2022-04-15 | 深圳市微克科技有限公司 | Intelligent wearing-based safe off-line payment system and method |
| CN115345615A (en) * | 2022-08-09 | 2022-11-15 | 平安银行股份有限公司 | Request verification method and device, electronic equipment and storage medium |
| CN115409518A (en) * | 2022-10-09 | 2022-11-29 | 中国工商银行股份有限公司 | User transaction risk early warning method and device |
| WO2023283349A1 (en) * | 2021-07-07 | 2023-01-12 | Brightwell Payments, Inc. | Fraud detection and prevention system |
-
2023
- 2023-03-23 CN CN202310292424.9A patent/CN115994763B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855555A (en) * | 2012-08-06 | 2013-01-02 | 北京中科金财电子商务有限公司 | System and method for identifying payment risks based on position transformation |
| WO2015062229A1 (en) * | 2013-10-30 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus, and system for secure payment |
| CA2992421A1 (en) * | 2015-07-21 | 2017-01-26 | Early Warning Services, Llc | Secure real-time payment transactions |
| CN107730255A (en) * | 2017-09-28 | 2018-02-23 | 努比亚技术有限公司 | A kind of safe payment method, terminal and computer-readable recording medium |
| CN108256853A (en) * | 2018-01-11 | 2018-07-06 | 维沃移动通信有限公司 | A kind of method of payment and mobile terminal |
| CN109165942A (en) * | 2018-08-17 | 2019-01-08 | 苏州诚满信息技术有限公司 | A kind of user ID authentication method and its system for mobile payment |
| CN110751488A (en) * | 2019-10-21 | 2020-02-04 | 深圳传音控股股份有限公司 | Intelligent terminal safety payment method, terminal and medium |
| CN111784356A (en) * | 2020-07-22 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | Payment verification method, device, equipment and storage medium |
| CN112184239A (en) * | 2020-09-23 | 2021-01-05 | 支付宝(杭州)信息技术有限公司 | Secure payment method, device, equipment and readable medium |
| CN112669042A (en) * | 2021-03-15 | 2021-04-16 | ***股份有限公司 | Payment method, server, user terminal, system and storage medium |
| CN113112274A (en) * | 2021-04-12 | 2021-07-13 | 支付宝(杭州)信息技术有限公司 | Payment information processing method, device, equipment and medium |
| CN113065870A (en) * | 2021-04-13 | 2021-07-02 | 梁万钢 | Safety payment method and system based on artificial intelligence and big data and cloud platform |
| WO2023283349A1 (en) * | 2021-07-07 | 2023-01-12 | Brightwell Payments, Inc. | Fraud detection and prevention system |
| CN114358761A (en) * | 2022-03-16 | 2022-04-15 | 深圳市微克科技有限公司 | Intelligent wearing-based safe off-line payment system and method |
| CN115345615A (en) * | 2022-08-09 | 2022-11-15 | 平安银行股份有限公司 | Request verification method and device, electronic equipment and storage medium |
| CN115409518A (en) * | 2022-10-09 | 2022-11-29 | 中国工商银行股份有限公司 | User transaction risk early warning method and device |
Non-Patent Citations (1)
| Title |
|---|
| 安宝怡: "开放***环境下的可信移动群智感知数据交易机制研究", 《中国优秀博硕士学位论文全文数据库（博士）信息科技辑》, no. 03, pages 1 - 146 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115994763B (en) | 2023-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108780390B (en) | System and method for providing identity scores | |
| CN107833052B (en) | Block chain-based aggregated payment system and working method | |
| CN102394896A (en) | Privacy-protection fingerprint authentication method and system based on token | |
| CN103338188A (en) | Dynamic authentication method of client side suitable for mobile cloud | |
| CN101095144A (en) | Presentation instrument security arrangement and methods | |
| US20050060263A1 (en) | System and method for authentication | |
| CN102663549A (en) | Entrance ticket management system with high security and entrance ticket management method thereof | |
| JP2002502186A (en) | One-way authentication communication system | |
| CN106682905B (en) | Application unlocking method | |
| CN107248212A (en) | A kind of intelligent lock system and its method for unlocking based on NFC | |
| CN104361494A (en) | Bank counter authorization and certification method and system based on fingerprint recognition | |
| CN103646200A (en) | Encoding encryption application method for human face information | |
| CN115994763B (en) | Trusted intelligent payment method and system | |
| CN112329004A (en) | Method and device for face recognition and face password | |
| WO1999065175A1 (en) | Method for generating, storing, and verifying a binding between an authorized user and a token | |
| CN101443722A (en) | Wireless telecommunication device with output control function and transaction authentication system using the same | |
| RU2573235C2 (en) | System and method for checking authenticity of identity of person accessing data over computer network | |
| KR20030042639A (en) | Multi-certification system and the method using smart card | |
| CN114780984A (en) | Intelligent money box handover management method and system | |
| CN1862556B (en) | Method and apparatus for controlling computer 10g-in by contactless smart card | |
| CN105427143B (en) | Method and device for carrying out system security control | |
| CN115804063A (en) | Engine for configuring access request authentication | |
| CN110581820B (en) | Financial technology application system and method based on IPV6 and biological recognition technology | |
| CN113132380A (en) | Security evaluation system, method, device and medium for cryptographic algorithm | |
| KR20080109118A (en) | Method for certificating fingerprint information using smart card, and system therefor |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |