CN115330373A - Resource transaction processing method and device - Google Patents

Resource transaction processing method and device Download PDF

Info

Publication number
CN115330373A
CN115330373A CN202211019288.8A CN202211019288A CN115330373A CN 115330373 A CN115330373 A CN 115330373A CN 202211019288 A CN202211019288 A CN 202211019288A CN 115330373 A CN115330373 A CN 115330373A
Authority
CN
China
Prior art keywords
transaction
resource
candidate
resource account
transaction object
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
Application number
CN202211019288.8A
Other languages
Chinese (zh)
Inventor
万晓伟
吴铭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202211019288.8A priority Critical patent/CN115330373A/en
Publication of CN115330373A publication Critical patent/CN115330373A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4014Identity check for transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Landscapes

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

Abstract

The embodiment of the specification provides a resource transaction processing method and a device, wherein the resource transaction processing method comprises the following steps: acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel; verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result; and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.

Description

Resource transaction processing method and device
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a resource transaction processing method and device.
Background
With the continuous development of internet technology and information technology, more and more services can be realized online, and with the continuous improvement of online services, users use the online services to perform services such as service consumption, resource management, resource planning and the like; with the development of various resource management mechanisms, the service coverage rate of the resource management mechanism is improved by opening the resource account of the mechanism for the user; in this case, the user has a plurality of resource accounts, each of which stores resources, and performs resource transactions based on the unused resource accounts.
Disclosure of Invention
One or more embodiments of the present specification provide a first resource transaction processing method, including: and acquiring a historical transaction object of the logged resource account, and inquiring the identity authentication information of the resource account and the bound transaction channel. And verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result. And constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
One or more embodiments of the present specification provide a second resource transaction processing method, including: and according to the resource transaction request submitted by the user, acquiring a candidate transaction object set which is the same as the logged-in resource account and is the same as the user, and displaying the candidate transaction object set. And receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set. And performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
One or more embodiments of the present specification provide a resource transaction processing apparatus including: the acquisition module is configured to acquire a historical transaction object of the logged resource account, and query the identity authentication information of the resource account and the bound transaction channel. And the verification module is configured to verify the identity authentication information and the identity authentication information of the historical transaction object, and determine the target transaction object which is the same as the resource account and is the same as the user according to a verification result. And the construction module is configured to construct a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object so as to conduct resource transaction of the same user according to the candidate transaction object set.
One or more embodiments of the present specification provide another resource transaction processing apparatus, including: and the acquisition module is configured to acquire a candidate transaction object set which is the same as the logged-in resource account and is used as the user according to the resource transaction request submitted by the user, and perform display processing. A receiving module configured to receive a transaction instruction of the user for any one of the candidate transaction objects in the candidate transaction object set. A resource transaction module configured to perform a resource transaction of the resource account with the same user as the candidate transaction object based on the transaction instruction.
One or more embodiments of the present specification provide a resource transaction processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and acquiring a historical transaction object of the logged resource account, and inquiring the identity authentication information of the resource account and the bound transaction channel. And verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result. And constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
One or more embodiments of the present specification provide another resource transaction processing apparatus, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and according to the resource transaction request submitted by the user, acquiring a candidate transaction object set which is the same as the logged-in resource account and is the same as the user, and displaying the candidate transaction object set. And receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set. And performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and acquiring a historical transaction object of the logged resource account, and inquiring the identity authentication information of the resource account and the bound transaction channel. And verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result. And constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
One or more embodiments of the present specification provide another storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and according to the resource transaction request submitted by the user, acquiring a candidate transaction object set which is the same as the logged-in resource account and is the same as the user, and displaying the candidate transaction object set. And receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set. And performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, 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 described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;
FIG. 1 is a flow diagram of a first resource transaction processing method provided in one or more embodiments of the present disclosure;
FIG. 2 is a schematic diagram of a transaction list presentation page provided in one or more embodiments of the present disclosure;
FIG. 3 is a schematic illustration of a candidate transaction object presentation page provided in one or more embodiments of the disclosure;
FIG. 4 is a schematic illustration of an object management presentation page provided in one or more embodiments of the specification;
FIG. 5 is a schematic diagram of a real-name reminder page provided in one or more embodiments of the present disclosure;
FIG. 6 is a schematic diagram of a channel binding reminder page according to one or more embodiments of the present disclosure;
FIG. 7 is a schematic diagram of another real-name reminder page provided in one or more embodiments of the present description;
FIG. 8 is a schematic view of another transaction list presentation page provided in one or more embodiments of the present specification;
FIG. 9 is a schematic illustration of another candidate transaction object presentation page provided by one or more embodiments of the present disclosure;
FIG. 10 is a process flow diagram of a resource transaction processing method applied to a fund transaction scenario according to one or more embodiments of the present disclosure;
FIG. 11 is a flowchart of a resource transaction processing method applied to a equity transaction scenario according to one or more embodiments of the present disclosure;
FIG. 12 is a process flow diagram of a second resource transaction processing method provided in one or more embodiments of the present disclosure;
FIG. 13 is a process flow diagram of a third resource transaction processing method provided in one or more embodiments of the present specification;
FIG. 14 is a process flow diagram of a fourth resource transaction processing method provided in one or more embodiments of the present disclosure;
FIG. 15 is a schematic diagram of a resource transaction processing device according to one or more embodiments of the present disclosure;
FIG. 16 is a schematic view of another resource transaction processing arrangement provided in one or more embodiments of the present disclosure;
fig. 17 is a schematic structural diagram of a resource transaction processing apparatus according to one or more embodiments of the present disclosure;
fig. 18 is a schematic structural diagram of another resource transaction processing device according to one or more embodiments of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
The first resource transaction processing method embodiment provided by this specification:
according to the resource transaction processing method, a transaction channel and a target transaction object which are the same as a resource account are constructed into a candidate transaction object set, so that resource transaction of the same user is carried out through the candidate transaction object set; specifically, the historical transaction object is verified based on the identity authentication information of the logged-in resource account and the identity authentication of the historical transaction object of the resource account, a target transaction object which is the same as the resource account in the historical transaction object is determined according to a verification result, and a transaction channel containing the resource account and a candidate transaction object set of the target transaction object are constructed; the candidate transaction object set and the resource account are the same user, so that the transaction channel and the target transaction object which are the same user with the resource account are managed in the mode of the candidate transaction object set, the perception degree of the user to which the resource account belongs on the transaction channel and the target transaction object of the same user is improved, and the efficiency of resource transfer between the same users is improved.
Referring to fig. 1, the resource transaction processing method provided in this embodiment specifically includes steps S102 to S106.
Step S102, obtaining a historical transaction object of the logged resource account, and inquiring the identity authentication information of the resource account and the bound transaction channel.
In practical application, in order to improve the convenience of managing resources by a user and improve the perception degree of the user to resource services, the resource management and the perception of related services can be carried out by participating in the resource services; specifically, in order to ensure that resources of different users are effectively managed, the resource service opens a resource account for each user, so that the resource management of each user and the convenience and effectiveness of resource service participation of each user are improved, and the resource loss of the users is avoided; further, in order to ensure the authenticity of the identity of the user and avoid the user from using the resource service to perform a behavior violating the service regulation, the identity authentication is performed on the resource account opened to the user, and the identity authentication information is stored; the identity authentication can be performed on the user through the biological characteristic information of the user, the identity document number, the cross-border travel document number, the user contact channel information and the like, and the corresponding information is identity authentication information. After applying for the resource account, the user can participate in the resource service by logging in the resource account and perform resource management under the resource account.
The resource account described in this embodiment may be, in addition to the account provided by the user for logging in the resource service, a fund account of the user, for example, an account opened in a financial institution for resource management; but also an equity account of the user, e.g. an account holding coupons or full discount coupons issued to the user.
After the user logs in the resource account, resource transaction can be carried out through resource service based on the resource account; in this embodiment, the historical transaction object is determined based on a historical transaction record of a resource account of a user; for example, if the user u1 transfers resources to the resource account of the user u2 through the resource account, the user u1 is the historical transaction object of the user u2, and the user u2 is also the historical transaction object of the user u 1. I.e., historical transaction objects that have a historical transaction record with the logged-in resource account.
Optionally, the historical transaction object includes: historical resource accounts and/or historical transaction channels for resource transaction exist between the resource accounts and the resource accounts within a preset time range; wherein the historical resource accounts include at least one of: fund accounts, equity accounts, service accounts. The fund account comprises an account which is opened in a financial institution or a resource service and manages total resources; the right and interest accounts comprise opened accounts managed together with other users; the service account comprises an account generated based on the service.
Further, a target transaction object which is the same as the resource account and is the same as the resource account is determined in the historical transaction object, namely, the target transaction object which is the same as the resource account and is the fund account, the equity account, the service account and the transaction channel of the historical transaction object is determined, and after the target transaction object is determined, resource combination is carried out on the fund account, the equity account and the service account in the target transaction object; in the process of resource combination, the resource combination can be performed based on the account type, and the resource combination can also be performed based on the resource type stored in the account, so as to realize the combination of the total resources of the resource account.
For example, the target transaction object which is the same user with the resource account comprises a group fund account, a financing fund account and a equity account, the fund amount in the group fund account and the financing fund account is combined to obtain the total fund amount of the resource account, and the equity resources in the group fund account, the financing fund account and the equity account are combined to obtain the total equity resources of the resource account. For the total fund amount and the total equity resources, the perception degree of the user on the total fund amount and the total equity resources can be improved by showing the user to which the resource account belongs.
In this embodiment, in the process of resource transaction by a user based on a resource account, the resource in the resource service may be transacted by binding the transaction channel of the user, for example, a bank card account of the user to the resource account; therefore, the transaction channel in this embodiment includes a bank card payment channel and/or a credit granting payment channel bound to the resource account; in addition, the transaction channels can also comprise other channels for storing the resources of the users bound to the resource account; for example, a channel for storing and transferring resources for purchasing financial products after the users purchase the financial products; or, the user participates in a group service, a payment channel for the group service, etc.
In specific implementation, in order to improve the effectiveness of determining a target transaction object and a transaction channel of the same user of the resource account, a historical transaction object of the logged-in resource account is obtained, and identity authentication information of the resource account and a bound resource channel are inquired; the function of inquiring the identity authentication information of the resource account is to perform the same-user verification on the historical transaction object based on the identity authentication information of the resource account.
In addition, step S102 may be replaced by acquiring a historical transaction object of the resource account according to a resource transaction request submitted by a login terminal of the resource account, and querying the identity authentication information of the resource account and a bound transaction channel; and forms a new implementation with other processing steps provided by the embodiment.
And step S104, verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result.
The same user includes the same user, and also includes the same user with the same identity, or the user of the associated identity authentication information. For example, if the authenticated user of the resource account is user u1 and the authenticated user of the transaction channel is user u1, the transaction channel and the resource account are the same user.
The target transaction object which is the same as the resource account and is the same as the user is identified to the resource account, and the target transaction object which has the same identification user as the identification user of the resource account is included; for example, if the authenticated user of the resource account is the user u1, the historical transaction object that authenticates the user as the user u1 among the historical transaction objects is the target transaction object of the same user as the resource account.
In specific implementation, in order to determine that the resource account is the target transaction object of the same user in the historical transaction objects, the target transaction object of the same user is screened from the historical transaction objects on the basis of the identity authentication information of the resource account; in a specific implementation, for different transaction objects, for example: in order to improve the verification efficiency of the historical transaction object of the user, in an optional implementation manner provided in this embodiment, the target transaction object is determined in the following manner:
determining a verification mode for verifying the identity authentication information of the historical transaction object according to the object type of the historical transaction object;
verifying whether the identity authentication information of the historical transaction object is matched with the identity authentication element of the identity authentication information of the resource account or not according to the verification mode;
if yes, determining the matched historical transaction object as a target transaction object which is the same as the resource account and is the same as the user;
if not, the processing is not required.
Specifically, after a historical transaction object of a logged resource account and a bound transaction channel are obtained, a target transaction object which is the same as the resource account and is the same as a user is screened from the historical transaction object; in the process of screening a target transaction object which is the same as the resource account in the historical transaction object, verifying the identity authentication information of the historical transaction object according to the object type of the historical transaction object, and verifying whether the identity authentication information of the corresponding historical transaction object is matched with the identity authentication element of the identity authentication information of the resource account according to the determined verification mode;
the identity authentication element comprises an element which is contained in the identity authentication information and used for checking with the user; including user identification and/or identity.
In other words, according to the object type of each historical transaction object, determining a verification mode for verifying the identity authentication information of each historical transaction object; and matching and checking the identity authentication information of each historical transaction object and the identity authentication element of the identity authentication information of the resource account according to the checking mode of each historical transaction object, and determining the historical transaction object of which the identity authentication information is matched with the identity authentication element in the historical transaction object as a target transaction object which is the same as the resource account and is the same as the user.
That is, the step S104 may be replaced by verifying the identity authentication information and the identity authentication information of the historical transaction object according to the object type of the historical transaction object, and determining the target transaction object which is the same as the resource account and is the same as the user according to a verification result; and forms a new implementation with other processing steps provided by the embodiment.
Specifically, in the process of determining a target transaction object that is the same as the resource account for the same user, the following description will be given of a process of verifying according to the object type by taking the resource account type and the transaction channel type as an example.
(1) If the object type of the historical transaction object is the resource account type, verifying the identity authentication information and the identity authentication information of the historical transaction object according to a first verification mode, and determining a target transaction object which is the same as the resource account and is the same as the user according to a verification result; optionally, the first verification manner includes identity matching and identity authentication manner matching; specifically, the first verification method includes: verifying whether the identity of the resource account is matched with the identity of the historical resource account; if not, no processing is carried out; and if so, verifying whether the identity authentication mode of the resource account is the same as that of the historical resource account, if so, determining the historical resource account as a target resource account of the same user as the resource account, and if not, not processing.
For example, for a historical resource account in a historical transaction object, whether a user name in the identity authentication information of the historical resource account is the same as a user name in the identity authentication information of the resource account is checked; if not, the treatment is not needed; if so, further verifying whether the identity authentication mode of the historical resource account is the same as or corresponds to the identity authentication mode of the resource account; if not, the processing is not required; and if so, determining the historical resource account as a target transaction object of the same user as the resource account.
That is, in the step S104, if the historical transaction object is a historical resource account, matching an identity identifier in the identity authentication information in the historical resource account with an identity identifier in the identity authentication information in the resource account, and determining the historical resource account whose identity authentication manner corresponds to the identity authentication manner of the resource account as the target transaction object that is the same as the resource account; and forms a new implementation with other processing steps provided by the present embodiment. Or, in the step S104, the identity identifier in the identity information in the historical transaction object may be matched with the identity identifier in the identity authentication information of the resource account, and the historical transaction object whose identity authentication manner is the same as that of the resource account is determined as the target transaction object that is the same as the resource account; and forms a new implementation with other processing steps provided by the embodiment.
(2) In practical application, the condition that the identity authentication mode provided for the resource account is inconsistent with the identity authentication mode provided for the transaction channel exists; for example, there are m1 authentication types for the resource account to perform identity authentication, and m2 authentication types for the transaction channel to perform identity authentication, so that there is an error if the resource account and the transaction channel are verified by the same user according to the authentication method;
on the basis, if the object type of the historical transaction object is the transaction channel type, the identity authentication information and the identity authentication information of the historical transaction object are verified according to a second verification mode, and the target transaction object which is the same as the resource account and is the same as the user is determined according to a verification result; optionally, the second verification method includes identity matching; specifically, whether the identity of the resource account is matched with the identity of the historical transaction channel is checked; if so, determining the identity of the resource account as a target transaction channel with the same identity as the resource account; if not, no processing is carried out.
For example, for a bank card channel in a historical transaction object, whether a user name in the identity authentication information of the bank card channel is the same as a user name in the identity authentication information of the resource account is checked; if not, the treatment is not needed; if the transaction objects are the same, the bank card channel is determined to be the target transaction object of the same user as the resource account.
That is, in the step S104, if the historical transaction object is a historical transaction channel, the historical transaction channel in which the identity identifier in the identity authentication information in the historical transaction channel is matched with the identity identifier in the identity authentication information in the resource account is determined as the target transaction object that is the same as the resource account; and forms a new implementation with other processing steps provided by the embodiment. Alternatively, in step S104, the historical transaction object whose identity in the identity authentication information in the historical transaction object matches the identity in the identity authentication information in the resource account may be determined as the target transaction object that is the same as the resource account.
In addition, in the embodiment of determining the target transaction object, an identity authentication element for verifying the identity authentication information of the historical transaction object may be determined according to the object type of the historical transaction object; verifying whether the identity authentication element contained in the identity authentication information of the historical transaction object is matched with the identity authentication element contained in the identity authentication information of the resource account;
specifically, if the object type of the historical transaction object is the resource account type, reading the identity identification and the identity authentication mode of the historical transaction object; verifying whether the identity identification is matched with the identity identification in the identity authentication information and whether the identity authentication mode is matched with the identity authentication mode in the identity authentication information; if yes, determining that the historical transaction object is a target transaction object which is the same as the resource account and is the same as the user; if not, no processing is carried out;
if the object type of the historical trading object is the trading channel type, reading the identity of the historical trading object; verifying whether the identity is matched with the identity in the identity authentication information; if yes, determining that the historical transaction object is a target transaction object which is the same as the resource account and is the same as the user; if not, no processing is carried out.
It should be noted that the two manners of performing verification provided above are only exemplary, and the verification may also be performed in the same manner for different types of historical transaction objects, that is, the verification may be performed only according to any manner described above without distinguishing object types; for the historical transaction object of the resource account type, only the identity can be verified; for the historical transaction object of the transaction channel, the identity identifier and the identity authentication mode may also be verified, and in addition, verification of other information in other identity authentication information may also be performed, the verification of other information is similar to the verification in the two provided above, and the process of performing verification based on other information may refer to the verification process, which is not repeated herein.
In this step, the same-user verification is performed on the historical transaction object based on the identity authentication information, and a target transaction object which is the same user as the resource account in the historical transaction object is determined. After the target transaction object is determined, in order to ensure the validity of the determined target transaction object, in an optional implementation manner provided in this embodiment, a secondary verification is performed on the determined target transaction object, specifically, the secondary verification is performed on the target transaction object by the following method:
verifying whether the identity certificate information of the transaction channel and/or the target transaction object for identity authentication is matched with the identity certificate information associated with the resource account;
if yes, executing the following step S106;
if not, removing the unmatched transaction channels and/or the target transaction objects.
Specifically, in the process of performing the secondary verification, the queried transaction channel bound to the resource account and the determined identity of the target transaction object are verified with the identity associated with the resource account, if the identities of the transaction channel and the target transaction object are matched with (same as) the identity of the resource account, the verification is determined to be passed, and the following step S106 is executed; if not, removing the unmatched transaction channel and the unmatched target transaction object.
In addition to the process of the secondary verification provided above, the secondary verification may be performed by sending the queried transaction channel and target transaction object to the user to which the resource account belongs, and determining that the secondary verification passes in case that the user submits a confirmation instruction.
In addition, the step S102 may be replaced by acquiring a historical transaction object of the logged resource account and a bound transaction channel; correspondingly, step S104 may be replaced by performing same-user verification on the historical transaction object, and determining that the resource account is a target transaction object of the same user according to a verification result; and constitutes a new implementation with step S106 described below. Optionally, the identity verification includes performing identity verification based on the identity authentication information of the historical transaction object and the identity authentication of the resource account. Specifically, please refer to the relevant content of verifying the identity authentication and the identity authentication information of the historical transaction object in the step S104 for specific implementation of identity verification, which is not described herein again.
And step S106, constructing a candidate transaction object set which is the same as the resource account and is the same as the user based on the transaction channel and the target transaction object, and performing resource transaction of the same user according to the candidate transaction object set.
The same user comprises users with the same user identity or associated identity authentication information. For example, if the authenticated user of the resource account is user u1 and the authenticated user of the transaction channel is user u1, the transaction channel and the resource account are the same user.
Verifying the identity authentication information and the identity authentication information of the historical transaction object, determining a target transaction object which is the same user with the resource account according to a verification result, namely verifying the same user with the resource account for the historical transaction object based on the identity authentication information, and constructing a candidate transaction object set which is the same user with the resource account based on a transaction channel bound with the inquired resource account and the target transaction object which is the same user with the resource account after determining the target transaction object; optionally, performing resource transaction with the user according to the candidate transaction object set;
that is, step S106 may be replaced by constructing a candidate transaction object set that is the same as the resource account based on the transaction channel and the target transaction object; and forms a new implementation mode with other processing steps provided by the embodiment; or, alternatively, a candidate transaction object set that is the same user as the resource account is constructed based on the transaction channel and the target transaction object, resource transaction of the same user is performed based on the candidate transaction object set, and a new implementation manner is formed with other processing steps provided in this embodiment.
In the specific implementation process, in order to improve the perception degree of a user to which a resource account belongs to the transaction channels and the target transaction objects in the candidate transaction object set and the perception degree of the historical transaction condition in the process of constructing the candidate transaction object set, the display priorities of the transaction channels and the target transaction objects are determined according to the transaction time spans of the transaction channels, the target transaction objects and the resource account, and the candidate transaction object set is constructed on the basis of the transaction channels, the target transaction objects and the display priorities. Based on this, in an optional implementation manner provided by this embodiment, the set of candidate transaction objects is constructed in the following manner:
determining a transaction time span according to the transaction channel and the transaction records of the target transaction object and the resource account;
constructing the candidate transaction object set by taking the transaction channel and the target transaction object as candidate transaction objects, and determining the display priority of the candidate transaction objects contained in the candidate transaction object set based on the transaction time span;
wherein the transaction time span is negatively correlated with the presentation priority.
Specifically, determining the transaction time span between the transaction time of the transaction channel and the resource account and the current time, and determining the transaction time span between the transaction time of the target transaction object and the current time; taking the transaction channel and the target transaction object as candidate transaction objects to construct the candidate transaction object set; and determining the display priority of the candidate transaction objects according to the respective transaction time span.
For example, the transaction channels comprise a first bank card channel and a second bank card channel, the target transaction object comprises another resource account A and a third bank card channel of the user to which the resource account belongs, the display priorities of the resource account A, the first bank card, the second bank card and the third bank card are respectively determined according to the transaction span time of the transaction channels and the target transaction object, and a candidate transaction object set comprising the transaction channels and the target transaction object is constructed; the transaction time span between the resource account A and the resource account is the minimum from the current time, and the transaction time span between the third bank card and the resource account is the maximum from the current time.
Further, after a candidate transaction object set which is the same as the resource account is constructed, resource transaction of the same user can be carried out according to the candidate transaction object set. The resource transaction with the user comprises resource circulation between a resource account and a candidate transaction object. In this embodiment, the process of resource transaction with a user is specifically described with the fund flow and the interest flow of a resource account and a candidate transaction object.
In a first optional implementation manner provided by this embodiment, performing resource transaction with a user according to a candidate transaction object set is implemented by:
transferring funds in the resource account to any selected one of the candidate transaction objects in the set of candidate transaction objects;
or,
transferring funds from any one of the selected candidate transaction objects from the set of candidate transaction objects to the resource account.
Specifically, funds in the resource account are transferred to the selected candidate transaction objects in the set of candidate transaction objects, or the funds of the selected candidate transaction objects in the set of candidate transaction objects are transferred to the resource account.
The candidate transaction objects comprise transaction channels and other types of resource accounts; optionally, the set of candidate transaction objects includes a group account created by the user participating in the group service based on the resource account; the group account is a resource account included in the candidate transaction object; for example, a family account in the family group charges the family account based on the resource account, i.e., funds in the resource account are transferred to the family account. Or the candidate transaction object comprises a financial account obtained by opening a financial service based on the resource account by the user; the financial account may be opened based on the resource account.
In addition, in addition to performing resource flow processing on the resource account and the candidate transaction objects in the candidate transaction object set, resource flow may also be performed based on the candidate transaction objects in the candidate transaction object set.
For example, the candidate transaction object set which is the same user as the resource account includes four candidate transaction objects of the resource account a, the first bank card, the second bank card and the third bank card. The fund of the first bank card can be transferred to the second bank card, and the fund of the third bank card can also be transferred to the resource account A; other fund flows are similar to the above-mentioned flow process, and the description of this embodiment is omitted here.
In a second optional implementation manner provided by this embodiment, performing resource transaction with the user according to the candidate transaction object set is implemented by:
transferring the rights and interests in the resource account to any selected candidate transaction object in the candidate transaction object set;
or,
and transferring the right to the resource account from any selected candidate transaction object in the candidate transaction object set.
Specifically, in order to increase the utilization rate of the rights issued to the resource account, the rights and interests can be circulated between the resource account and the candidate transaction object set; that is, the rights and interests in the resource account are transferred to the selected candidate transaction objects in the candidate transaction object set, or the rights and interests of the selected candidate transaction objects in the candidate transaction object set are transferred to the resource account.
In addition, fund and/or equity flow can be conducted in the candidate transaction object set; for example, funds and/or benefits of a first candidate transaction object in the set of candidate transaction objects are transferred to a second candidate transaction object in the set of candidate transaction objects.
Specifically, in the execution process, in order to improve the perception degree of the user, after a candidate transaction object set that is the same as the resource account and is the same as the user is constructed, in an optional implementation manner provided by this embodiment, the following operations may also be performed:
issuing the candidate transaction object set to a login terminal of the resource account so as to display the candidate transaction object set at the login terminal;
receiving a trading instruction aiming at any one candidate trading object contained in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
Specifically, after a candidate transaction object set is constructed, the candidate transaction object set is issued to a login terminal of a resource account, and the login terminal acquires and displays the candidate transaction object set which is the same as the logged-in resource account; optionally, the display processing includes: displaying the identity information corresponding to the candidate transaction object set in a historical transaction list of the resource account; optionally, after an access entry of a resource transaction service of an application installed in the login terminal is triggered, displaying the identity information corresponding to the candidate transaction object set in a historical transaction list of the resource account; wherein the historical transaction list is generated based on the set of candidate transaction objects and the historical transaction object.
Further, in order to improve the perception degree of the user on the candidate transaction object of the same user, optionally, the identity information is located at the head of the list in the historical transaction list; and if the identity identification information in the historical transaction list is triggered, displaying the candidate transaction objects contained in the candidate transaction object set.
For example, a user u1 accesses a resource transaction (transfer) service through a login terminal for logging in a resource account, wherein after detecting an access instruction for the resource transfer service, the login terminal equivalently acquires a resource transaction request submitted by the user u1, and submits the resource transaction request to a server to construct a candidate transaction object set of the same user as the resource account; the login terminal receives a historical transaction object identifier which is issued by the server and contains a candidate transaction object set; presenting a transaction list presentation page as shown in fig. 2 to the user u 1; the user u1 is a user to which the resource account belongs and is located at the head of the list, and the arrangement sequence of the historical trading object identifications is determined based on the trading time span of each historical trading object. And if the fact that the identity identification information aiming at the user u1 is triggered is detected, jumping to a candidate transaction object display page shown in fig. 3, and displaying the candidate transaction objects contained in the candidate transaction object set.
It should be noted that, in order to ensure the privacy of the historical transaction object, in the process of displaying the historical transaction object identifier, the account name of the historical transaction object is displayed, and the desensitization result of the real user identifier (actual user name) of the historical transaction object is displayed; as shown in fig. 2.
In practical application, if a user u to which a resource account belongs has two resource accounts, one is a logged-in resource account and the other is a resource account a, the user has multiple bank cards, for example, a first bank card and a second bank card bound to the logged-in resource account and a third bank card bound to the resource account a, because the users bound to the first bank card, the second bank card and the third bank card are the same, optionally, in the process of constructing the candidate transaction object set, a transaction channel bound to the resource account which is the same as the logged-in resource account is determined as the transaction channel of the logged-in resource account.
As shown in fig. 3, the first bank is shown as a transaction channel bound to a logged-in resource account; the second bank is the transaction channel bound to resource account a.
In order to further improve the perception degree of the user on the transaction records of the candidate transaction object of the same user, optionally, the user can operate the candidate transaction object through the candidate transaction object displayed by the sliding login terminal; optionally, if a first touch action for the candidate transaction object is detected, the transaction record of the candidate transaction object and the resource account for which the first touch action is directed is obtained and displayed. And if a second touch action aiming at the candidate transaction object is detected, deleting the candidate transaction object aiming at the second touch action from the historical transaction list, and/or deleting the candidate transaction object aiming at the second touch action from the candidate transaction object set.
Specifically, the user may manage the historical transaction list through a page as shown in fig. 2 or fig. 3, where the management includes viewing transaction records of target historical transaction objects in the historical transaction list and deleting the target historical transaction objects.
Along the above example, the user u1 slides the resource account a shown in fig. 3, and the login terminal displays the management control for the resource account a shown in fig. 4; the method comprises a transaction record control and a deletion control for checking transaction records, wherein if a touch action on the transaction record control is detected, historical transaction records of a resource account and a resource account A are obtained and displayed; and if the touch action on the deletion control is detected, deleting the resource account A from the list.
In addition, the aaa1 shown in fig. 2 may be slid to manage aaa1, which is similar to the management of the resource account a described above, and the details of this embodiment are not repeated herein.
For a user applying for a resource account but not performing identity authentication (real-name authentication) on the resource account, in order to ensure the security of the user participating in resource service and protect the privacy of the user, a transaction channel can be bound after the user performs identity authentication and identity authorization, and the bound transaction channel and a historical transaction object are read; in the case that the user does not perform identity authentication, since the identity authentication information of the user cannot be obtained, and the historical transaction object and the user identity of the user cannot be obtained, in order to improve the user's experience of participating in resource services or resource transaction services and improve the user's mind, in an optional implementation manner provided by this embodiment, if the resource account does not perform identity authentication, identity authentication prompting information is displayed in the historical transaction list of the resource account; after the identity authentication reminding information is triggered, identity authentication processing of the resource account is carried out; and/or if the resource account is not bound with a transaction channel, displaying the identity information corresponding to the resource account in a historical transaction list of the resource account; and performing transaction channel binding processing of the resource account after the identity identification information is triggered.
Specifically, under the condition that the resource account is not subjected to identity authentication, and under the condition that a user accesses the resource transaction service, identity authentication reminding information is displayed in a historical transaction list; further, after the user performs identity authentication, only the identity identification information of the user to which the resource account belongs is displayed in a historical transaction list under the condition that the resource account is not bound to a transaction channel, namely, an unbound bank card; and if the fact that the identity identification information is triggered is detected, displaying a channel binding reminder to the user. In addition, the user can also perform transaction channel binding processing by triggering a channel binding reminder.
For example, the user u1 accesses the resource transaction service through the login terminal of the resource account, if the login terminal detects that the resource account is not authenticated, the real-name reminding page shown in fig. 5 is displayed, and the user u1 can perform identity authentication processing by triggering "deauthentication"; after the identity authentication processing is carried out, a transaction list display page shown in fig. 2 is displayed through interaction data with a server, a channel binding reminder shown in fig. 6 is displayed under the condition that it is detected that a user u1 is triggered by the user u1 and a transaction channel is not bound to the resource account, and if it is detected that the reminding content of the channel binding reminder is triggered, the transaction channel binding processing is carried out.
In addition, since the historical transaction records are the privacy of the data user to a certain extent, and the resource of the user can be transferred through the resource account after the identity authentication is performed, in order to ensure the data security of the user, the user accesses the resource transaction service, and if the login terminal detects that the resource account is not authenticated, the real-name reminding page only containing the real-name reminding content is displayed.
That is, in the above example, the user u1 accesses the resource transaction service through the login terminal of the resource account, and if the login terminal detects that the resource account is not authenticated, the real-name reminding page shown in fig. 7 is displayed; similar to the above examples, the present embodiment is not described herein again.
In the execution process, resource transaction from a resource account to a first resource account and a second resource account of the same user exists in a historical transaction object; the method comprises the steps that a user has two resource accounts, the resource accounts respectively conduct resource transaction on the two resource accounts of the user, in order to avoid that the perception degree of the user to which the resource accounts belong is low due to the fact that the two resource accounts are separately displayed, the same-user processing can be conducted on historical transaction objects except for target transaction objects of the same user, which are the resource accounts, in the historical transaction objects, and a second candidate transaction object set is constructed on the basis of the historical transaction objects of the same user.
In an optional implementation manner provided by this embodiment, taking the historical transaction object including the historical resource account and the historical transaction channel as an example, a manner of constructing the second candidate transaction object set is as follows:
inquiring the identity authentication information of the historical resource account and the historical transaction channel;
and determining the historical resource account and the historical transaction channel of the same user based on the identity authentication information of the historical resource account and the historical transaction channel, and constructing a second candidate transaction object set based on the historical resource account and the historical transaction channel of the same user.
Specifically, a historical transaction object of a logged resource account is obtained, and identity authentication information of the resource account and a bound transaction channel are inquired; carrying out dialect on the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to a verification result; constructing a candidate transaction object set which is the same as the resource account and is the same as the user based on the transaction channel and the target transaction object; processing the remaining historical transaction objects except the target transaction object in the historical transaction objects by the same user, determining the historical transaction objects of the same user in the remaining historical transaction objects, and constructing a second candidate transaction object set of the user to which the historical transaction object of the same user belongs on the basis of the historical transaction objects of the same user; creating a trading object list containing the second set of candidate trading objects and other historical trading objects for the set of candidate trading objects.
For example, the desensitized identification information of aaa1 and aaa2 shown in the transaction list display page shown in fig. 2 is xxx, and aaa1 and aaa2 are resource accounts of xxx processed by the same user, and then aaa1 and aaa2 are constructed as a set of xxx candidate transaction objects; specifically, the transaction list display page shown in fig. 2 may be replaced with the transaction list display page shown in fig. 8, and if it is detected that the xxx character of the transaction list display page shown in fig. 8 is triggered, the candidate transaction object display page shown in fig. 9 is displayed, and if it is detected that the user u1 of the transaction list display page shown in fig. 8 is triggered, the candidate transaction object display page shown in fig. 3 is displayed.
In addition, step S106 may be replaced by constructing a candidate transaction object set that is the same as the resource account and is the same as the resource account based on the transaction channel and the target transaction object, and sending a historical transaction list including the candidate transaction object set to a login terminal of the resource account; and forms a new implementation with other processing steps provided by the embodiment.
In summary, the resource transaction processing method provided in this embodiment acquires the historical resource account and the historical transaction channel of the logged-in resource account, and queries the identity authentication information of the resource account and the bound transaction channel;
for the historical resource account, matching and verifying the identity of the historical resource account and the identity of the resource account, performing the same verification on the identity authentication mode of the historical resource account and the identity authentication mode of the resource account, and determining the historical resource account which passes the matching verification and the same verification as the target resource account which is the same user as the resource account;
for the historical transaction channel, matching and checking the identity of the historical transaction channel and the identity of the resource account, and determining the historical transaction channel passing the matching and checking as a target transaction channel which is the same as the resource account;
taking the determined target resource account and the target transaction channel as target transaction objects of the resource account, performing secondary verification on the target transaction objects and the transaction channel of the resource account, and constructing a candidate transaction object set which is the same as the resource account as a user on the basis of the target transaction objects and the transaction channel under the condition that the verification is passed;
therefore, the resource account is collectively displayed as a target transaction object and a transaction channel of the same user, the identity identification information of the same user is displayed at the head of the list when the historical transaction list is displayed so as to check the candidate transaction object, the perception degree of the user on the candidate transaction object set is improved, the transaction channel of the same user with the resource account and the target transaction object are also combined together, the resource transaction efficiency of the account of the same user is improved, and the intelligence of the user is improved.
The following takes an application of the resource transaction processing method provided in this embodiment in a fund transaction scenario as an example, and further describes the resource transaction processing method provided in this embodiment with reference to fig. 10, and with reference to fig. 10, the resource transaction processing method applied in the fund transaction scenario specifically includes the following steps.
Step S1002, obtaining the historical transaction object of the logged-in fund account, and inquiring the identity authentication information of the fund account and the bound transaction channel.
The historical transaction object comprises a historical fund account and a historical transaction channel which have fund transactions with the fund account within a preset time range. Historical transaction channels such as bank card channels.
Step S1004, reading the identity identifier in the identity authentication information and reading the object identity identifier in the identity authentication information of the historical transaction object.
Step S1006, checking whether the object identification is matched with the identification;
if yes, go to step S1008 to step S1016;
if not, no processing is carried out.
In step S1008, the historical transaction object is determined as the target transaction object of the same user as the fund account.
In addition, the foregoing steps S1006 to S1008 may be replaced by determining that the object id and the id match the historical transaction object in the historical transaction object, as the target transaction object for the same user as the fund account.
And step S1010, performing secondary identical user verification on the target transaction object and the transaction channel.
The second-time same-user verification comprises the steps of verifying whether the identity in the identity authentication information of the target transaction object is matched with the identity of the fund account or not and verifying whether the identity in the identity authentication information of the transaction channel is matched with the identity of the fund account or not; if yes, the verification is confirmed to be passed, and processing is not carried out; if not, rejecting unmatched target trading objects and trading channels.
Step S1012, determining the display priority of the target transaction object and the transaction channel according to the transaction time span between the target transaction object and the transaction channel that are approved by the second identical user and the fund account.
Step S1014, constructing a candidate transaction object set which is the same as the fund account and is the same as the fund account based on the target transaction object, the transaction object and the respective display priority.
Step S1016, transferring the resource in the resource account to the target candidate transaction object according to the fund transfer instruction of the user belonging to the fund account to the target candidate transaction object in the candidate transaction object set.
In addition, step S1016 may be replaced by transferring the funds in the first candidate transaction object to the second candidate transaction object according to the resource transfer instruction of the user to which the fund account belongs to the first candidate transaction object to the second candidate transaction object in the candidate transaction object set.
The following takes an application of the resource transaction processing method provided in this embodiment in a rights and interests transaction scenario as an example, and further describes the resource transaction processing method provided in this embodiment with reference to fig. 11, and with reference to fig. 11, the resource transaction processing method applied in the rights and interests transaction scenario specifically includes the following steps.
Step S1102, acquiring a historical transaction object of the logged equity account, and querying the identity authentication information of the equity account and the bound transaction channel.
Step S1104, the identity identifier and the identity authentication method in the identity authentication information are read, and the object identity identifier and the object identity authentication method in the identity authentication information of the historical transaction object are read.
Step S1106, checking whether the object identification is matched with the identification;
if yes, go to step S1108;
if not, no processing is carried out.
Step S1108, checking whether the identity authentication mode of the object is matched with the identity authentication mode;
if yes, go to step S1110 to step S1116;
if not, no processing is carried out.
In step S1110, the historical transaction object is determined as the target transaction object of the same user as the equity account.
In addition, the above steps S1106 to S1110 may be replaced by determining, in the historical transaction object, that the object identity matches the identity, and the historical transaction object whose object identity authentication manner matches the identity authentication manner is used as the target transaction object for the same user as the equity account; and forms a new implementation with other processing steps provided by the embodiment.
Step S1112, performing a second verification with the user on the target transaction object and the transaction channel.
The second-time same-user verification comprises the steps of verifying whether the identity in the identity authentication information of the target transaction object is matched with the identity of the equity account or not and whether the identity in the identity authentication information of the transaction channel is matched with the identity of the equity account or not; if yes, the verification is determined to be passed, and the processing is not carried out; if not, rejecting unmatched target transaction objects and transaction channels.
Step S1114 constructs a set of candidate transaction objects for the same user as the equity account based on the target transaction object and the transaction object.
Step S1116, according to the transfer instruction from the user to the equity account, the equity resources of the target candidate transaction object in the candidate transaction object set are transferred to the equity account.
In addition, step S1116 may be replaced by transferring the interest in the first candidate transaction object to the second candidate transaction object according to a resource transfer instruction of the user to which the interest account belongs to the first candidate transaction object to the second candidate transaction object in the candidate transaction object set; and forms a new implementation with other processing steps provided by the embodiment.
Another embodiment of a resource transaction processing method provided in this specification:
the resource transaction processing method provided by the application obtains the candidate transaction object set which is communicated with the logged-in resource account and displays the candidate transaction object set, and conducts resource transaction of the same user of the resource account and the candidate transaction object according to the transaction instruction of the user for any candidate transaction object in the candidate transaction object set, so that the transaction channel and the target transaction object which are the same user with the resource account are managed in the mode of the candidate transaction object set, the perception degree of the user to which the resource account belongs to the transaction channel and the target transaction object of the same user is improved, and the efficiency of resource transfer between the same users is improved.
Referring to fig. 12, the resource transaction processing method provided in this embodiment specifically includes steps S1202 to S1206.
And step S1202, acquiring a candidate transaction object set which is the same as the logged-in resource account and is used as the user according to the resource transaction request submitted by the user, and displaying the candidate transaction object set.
In practical application, in order to improve the convenience of managing resources by a user and improve the perception degree of the user on resource services, the resource management and the perception of related services can be carried out by participating in the resource services; specifically, the resource service opens a resource account for each user in order to ensure that resources of different users are effectively managed, so that convenience and effectiveness of resource management of each user and participation of each user in the resource service are improved, and user resource loss is avoided; further, in order to ensure the authenticity of the identity of the user and avoid the user from using the resource service to perform behavior violating the service regulation, the identity authentication is performed on the resource account opened to the user, and the identity authentication information is stored; the identity authentication can be performed on the user through the biological characteristic information of the user, the identity document number, the cross-border travel document number, the user contact channel information and the like, and the corresponding information is identity authentication information. After applying for the resource account, the user can participate in the resource service by logging in the resource account and perform resource management under the resource account.
The resource account described in this embodiment may be, in addition to the account provided by the user for logging in the resource service, a fund account of the user, for example, an account opened in a financial institution for resource management; but also an equity account of the user, e.g. an account holding coupons or full discount coupons issued to the user.
Optionally, the candidate transaction object set is obtained by constructing a transaction channel bound to the resource account and a target transaction object which is the same as the resource account and is the same as the resource account;
and determining the verification result of verifying the identity authentication information of the resource account and the identity authentication information of the historical transaction object.
In specific implementation, a login terminal of a resource account can send a resource transaction request submitted by a user to a server according to the resource transaction request submitted by the user, and the server acquires a historical transaction object of the logged-in resource account based on the resource transaction request and inquires identity authentication information of the resource account and a bound transaction channel; verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result; and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, and sending the candidate transaction object set to a login terminal. In addition, the candidate transaction object set can be obtained by the login terminal executing the resource transaction processing method provided by the embodiment in the above manner.
The following describes a process for obtaining a set of candidate transaction objects for the same user as the resource account.
(1) Obtaining a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel
After the user logs in the resource account, resource transaction can be carried out through resource service based on the resource account; in this embodiment, the historical transaction object is determined based on a historical transaction record of a resource account of a user; for example, if the user u1 transfers resources to the resource account of the user u2 through the resource account, the user u1 is the historical transaction object of the user u2, and the user u2 is also the historical transaction object of the user u 1. I.e., historical transaction objects that have a historical transaction record with the logged-in resource account.
Optionally, the historical transaction object includes: historical resource accounts and/or historical transaction channels for resource transaction exist between the resource accounts and the resource accounts within a preset time range; wherein the historical resource accounts include at least one of: fund accounts, equity accounts, service accounts. The fund account comprises an account which is opened in a financial institution or a resource service and manages total resources; the right and interest accounts comprise opened accounts managed together with other users; the service account comprises an account generated based on the service.
Further, a target transaction object which is the same as the resource account and is the same as the resource account is determined in the historical transaction object, namely, the target transaction object which is the same as the resource account and is the fund account, the equity account, the service account and the transaction channel of the historical transaction object is determined, and after the target transaction object is determined, resource combination is carried out on the fund account, the equity account and the service account in the target transaction object; in the process of resource combination, the resource combination can be performed based on the account type, and the resource combination can also be performed based on the resource type stored in the account, so as to realize the combination of the total resources of the resource account.
For example, the target transaction object which is the same user with the resource account comprises a group fund account, a financing fund account and a equity account, the fund amount in the group fund account and the financing fund account is combined to obtain the total fund amount of the resource account, and the equity resources in the group fund account, the financing fund account and the equity account are combined to obtain the total equity resources of the resource account. For the total fund amount and the total equity resources, the perception degree of the user on the total fund amount and the total equity resources can be improved by showing the user to which the resource account belongs.
In this embodiment, in the process of resource transaction by a user based on a resource account, the resource in the resource service may be transacted by binding the transaction channel of the user, for example, a bank card account of the user to the resource account; therefore, the transaction channel in this embodiment includes a bank card payment channel and/or a credit granting payment channel bound to the resource account; in addition, the transaction channels can also comprise other channels for storing the resources of the users bound to the resource account; for example, a channel for storing and transferring resources for purchasing financial products after the users purchase the financial products; or, the user participates in a group service, a payment channel for the group service, etc.
In specific implementation, in order to improve the effectiveness of determining a target transaction object and a transaction channel of the same user of the resource account, a historical transaction object of the logged-in resource account is obtained, and identity authentication information of the resource account and a bound resource channel are inquired; the function of inquiring the identity authentication information of the resource account is to perform the same-user verification on the historical transaction object based on the identity authentication information of the resource account.
(2) The identity authentication information and the identity authentication information of the historical transaction object are verified, and the target transaction object which is the same as the resource account and is the same as the user is determined according to the verification result
The target transaction object which is the same as the resource account and is the same as the user is identified to the resource account, and the target transaction object which has the same identification user as the identification user of the resource account is included; for example, if the authenticated user of the resource account is the user u1, the historical transaction object that authenticates the user as the user u1 among the historical transaction objects is the target transaction object of the same user as the resource account.
In specific implementation, in order to determine that the resource account is the target transaction object of the same user in the historical transaction objects, the target transaction object of the same user is screened from the historical transaction objects on the basis of the identity authentication information of the resource account; in a specific implementation, for different transaction objects, for example: in order to improve the verification efficiency of the historical transaction object of the user, in an optional implementation manner provided in this embodiment, the target transaction object is determined in the following manner:
determining a verification mode for verifying the identity authentication information of the historical transaction object according to the object type of the historical transaction object;
verifying whether the identity authentication information of the historical transaction object is matched with the identity authentication element of the identity authentication information of the resource account or not according to the verification mode;
if yes, determining the matched historical transaction object as a target transaction object which is the same as the resource account and is the same as the user;
if not, the processing is not required.
Specifically, after a historical transaction object of a logged-in resource account and a bound transaction channel are obtained, a target transaction object which is the same as the resource account and is a user is screened from the historical transaction object; in the process of screening a target transaction object which is the same as the resource account in the historical transaction object, verifying the identity authentication information of the historical transaction object according to the object type of the historical transaction object, and verifying whether the identity authentication information of the corresponding historical transaction object is matched with the identity authentication element of the identity authentication information of the resource account according to the determined verification mode;
the identity authentication element comprises an element which is contained in the identity authentication information and used for checking with the user; including user identification and/or identity.
In other words, according to the object type of each historical transaction object, determining a verification mode for verifying the identity authentication information of each historical transaction object; and matching and checking the identity authentication information of each historical transaction object and the identity authentication element of the identity authentication information of the resource account according to the checking mode of each historical transaction object, and determining the historical transaction object of which the identity authentication information is matched with the identity authentication element in the historical transaction object as a target transaction object which is the same as the resource account and is the same as the user.
That is, the identity authentication information and the identity authentication information of the historical transaction object are verified, and the target transaction object which is the same as the resource account and is the same as the user is determined according to the verification result, instead of verifying the identity authentication information and the identity authentication information of the historical transaction object according to the object type of the historical transaction object, and determining the target transaction object which is the same as the user and is the same as the resource account according to the verification result; and forms a new implementation with other processing steps provided by the embodiment.
Specifically, in the process of determining a target transaction object that is the same as the resource account for the same user, the following description will be given of a process of verifying according to the object type by taking the resource account type and the transaction channel type as an example.
The first method comprises the following steps: if the object type of the historical transaction object is the resource account type, verifying the identity authentication information and the identity authentication information of the historical transaction object according to a first verification mode, and determining that the historical transaction object and the resource account are the same user target transaction object according to a verification result; optionally, the first verification method includes identity matching and identity authentication matching; specifically, the first verification method includes: verifying whether the identity of the resource account is matched with the identity of the historical resource account; if not, no processing is carried out; and if so, verifying whether the identity authentication mode of the resource account is the same as that of the historical resource account, if so, determining the historical resource account as a target resource account of the same user as the resource account, and if not, not processing.
For example, for a historical resource account in a historical transaction object, whether a user name in the identity authentication information of the historical resource account is the same as the user name in the identity authentication information of the resource account is checked; if not, the treatment is not needed; if so, further verifying whether the identity authentication mode of the historical resource account is the same as or corresponds to the identity authentication mode of the resource account; if not, no processing is needed; and if so, determining the historical resource account as a target transaction object of the same user as the resource account.
That is, the above-mentioned verification of the identity authentication information and the identity authentication information of the historical transaction object is performed, and the target transaction object which is the same as the user with the resource account is determined according to the verification result, which may be replaced by matching the identity identifier in the identity authentication information in the historical resource account with the identity identifier in the identity authentication information in the resource account if the historical transaction object is the historical resource account, and determining the historical resource account whose identity authentication mode corresponds to the identity authentication mode of the resource account as the target transaction object which is the same as the user with the resource account; and forms a new implementation with other processing steps provided by the embodiment. Or, in the step S104, the identity identifier in the identity information in the historical transaction object may be matched with the identity identifier in the identity authentication information of the resource account, and the historical transaction object whose identity authentication manner is the same as that of the resource account is determined as the target transaction object that is the same as the resource account; and forms a new implementation with other processing steps provided by the present embodiment.
And the second method comprises the following steps: in practical application, the identity authentication mode provided for the resource account is inconsistent with the identity authentication mode provided for the transaction channel; for example, the authentication type for the resource account to perform identity authentication is m1, and the authentication type for the transaction channel to perform identity authentication is m2, so that an error exists if the resource account and the transaction channel are verified by the same user according to the authentication mode;
on the basis, if the object type of the historical transaction object is the transaction channel type, the identity authentication information and the identity authentication information of the historical transaction object are verified according to a second verification mode, and the target transaction object which is the same as the resource account and is the same as the user is determined according to a verification result; optionally, the second verification method includes identity matching; specifically, whether the identity of the resource account is matched with the identity of the historical transaction channel is verified; if yes, the identity of the resource account is determined to be a target transaction channel with the same identity as the resource account; if not, no processing is carried out.
For example, for a bank card channel in a historical transaction object, whether a user name in the identity authentication information of the bank card channel is the same as a user name in the identity authentication information of the resource account is checked; if not, the treatment is not needed; if the transaction objects are the same, the bank card channel is determined as a target transaction object of the same user as the resource account.
That is, the above-mentioned verification of the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result may be replaced by determining, if the historical transaction object is a historical transaction channel, the historical transaction channel in which the identity identifier in the identity authentication information in the historical transaction channel is matched with the identity identifier in the identity authentication information of the resource account is the target transaction object of the same user as the resource account; and forms a new implementation with other processing steps provided by the embodiment. Alternatively, in step S104, a historical transaction object whose identity in the identity authentication information in the historical transaction object matches an identity in the identity authentication information of the resource account may be determined as a target transaction object that is the same as the resource account.
In addition, in the embodiment of determining the target transaction object, an identity authentication element for verifying the identity authentication information of the historical transaction object may be determined according to the object type of the historical transaction object; verifying whether the identity authentication element contained in the identity authentication information of the historical transaction object is matched with the identity authentication element contained in the identity authentication information of the resource account;
specifically, if the object type of the historical transaction object is the resource account type, reading the identity identification and the identity authentication mode of the historical transaction object; verifying whether the identity identification is matched with the identity identification in the identity authentication information and whether the identity authentication mode is matched with the identity authentication mode in the identity authentication information; if yes, determining that the historical transaction object is a target transaction object which is the same as the resource account and is the same as the user; if not, no processing is carried out;
if the object type of the historical trading object is the trading channel type, reading the identity of the historical trading object; verifying whether the identity is matched with the identity in the identity authentication information; if yes, determining that the historical transaction object is a target transaction object which is the same as the resource account and is the same as the user; if not, no processing is carried out.
It should be noted that the two manners of performing verification provided above are only exemplary, and the verification may also be performed in the same manner for different types of historical transaction objects, that is, the verification may be performed only according to any manner described above without distinguishing object types; for historical transaction objects of the resource account type, the identity can be checked only; for the historical transaction object of the transaction channel, the identity identifier and the identity authentication mode may also be verified, and in addition, verification of other information in other identity authentication information may also be performed, the verification of other information is similar to the verification in the two provided above, and the process of performing verification based on other information may refer to the verification process, which is not repeated herein.
In this step, the same-user verification is performed on the historical transaction object based on the identity authentication information, and a target transaction object which is the same user as the resource account in the historical transaction object is determined. After the target transaction object is determined, in order to ensure the validity of the determined target transaction object, in an optional implementation manner provided in this embodiment, a secondary verification is performed on the determined target transaction object, specifically, the secondary verification is performed on the target transaction object by the following method:
verifying whether the identity certificate information of the transaction channel and/or the target transaction object for identity authentication is matched with the identity certificate information associated with the resource account;
if so, constructing a candidate transaction object set which is the same as the resource account and is the same as the resource account on the basis of the transaction channel and the target transaction object, and performing resource transaction of the same user according to the candidate transaction object set;
if not, removing the unmatched transaction channels and/or the target transaction objects.
Specifically, in the process of performing the secondary verification, the queried transaction channel bound to the resource account and the determined identity of the target transaction object are verified with the identity associated with the resource account, if the identities of the transaction channel and the target transaction object are matched with (same as) the identity of the resource account, the verification is determined to be passed, and the following step S106 is executed; if not, removing the unmatched transaction channel and the unmatched target transaction object.
In addition to the process of the secondary verification provided above, the secondary verification may be performed by sending the queried transaction channel and target transaction object to the user to which the resource account belongs, and determining that the secondary verification passes in case that the user submits a confirmation instruction.
(3) Based on the transaction channel and the target transaction object, constructing a candidate transaction object set which is the same as the resource account and is used as the same user, and performing resource transaction of the same user according to the candidate transaction object set
The same user comprises the same user identity or the associated identity authentication information. For example, if the authenticated user of the resource account is user u1 and the authenticated user of the transaction channel is user u1, the transaction channel and the resource account are the same user.
After the identity authentication information and the identity authentication information of the historical transaction object are verified, a target transaction object which is the same as the resource account is determined according to a verification result, namely the historical transaction object is verified with the resource account on the basis of the identity authentication information, the target transaction object is determined, and the target transaction object is obtained, a candidate transaction object set which is the same as the resource account is constructed on the basis of the queried transaction channel bound to the resource account and the target transaction object which is the same as the resource account; optionally, performing resource transaction with the user according to the candidate transaction object set;
that is, the set of candidate transaction objects which are the same as the resource account is constructed based on the transaction channel and the target transaction object, so that the resource transaction of the same user according to the set of candidate transaction objects can be replaced by constructing the set of candidate transaction objects which are the same as the resource account based on the transaction channel and the target transaction object; and forms a new implementation mode with other processing steps provided by the embodiment; or, alternatively, a candidate transaction object set that is the same user as the resource account is constructed based on the transaction channel and the target transaction object, resource transaction of the same user is performed based on the candidate transaction object set, and a new implementation manner is formed with other processing steps provided in this embodiment.
In the specific implementation process, in order to improve the perception degree of the user to which the resource account belongs to on the transaction channels and the target transaction objects in the candidate transaction object set and the perception degree of the historical transaction condition in the process of constructing the candidate transaction object set, the display priorities of the transaction channels and the target transaction objects are determined according to the transaction time spans of the transaction channels, the target transaction objects and the resource account, and the candidate transaction object set is constructed on the basis of the transaction channels, the target transaction objects and the display priorities. Based on this, in an optional implementation manner provided by this embodiment, the set of candidate transaction objects is constructed in the following manner:
determining a transaction time span according to the transaction channel and the transaction records of the target transaction object and the resource account;
constructing the candidate transaction object set by taking the transaction channel and the target transaction object as candidate transaction objects, and determining the display priority of the candidate transaction objects contained in the candidate transaction object set based on the transaction time span;
wherein the transaction time span is negatively correlated with the presentation priority.
Specifically, determining the transaction time span between the transaction time of the transaction channel and the resource account and the current time, and determining the transaction time span between the transaction time of the target transaction object and the current time; taking the transaction channel and the target transaction object as candidate transaction objects to construct the candidate transaction object set; and determining the display priority of the candidate transaction objects according to the respective transaction time span.
For example, the transaction channels comprise a first bank card channel and a second bank card channel, the target transaction object comprises another resource account A and a third bank card channel of the user to which the resource account belongs, the display priorities of the resource account A, the first bank card, the second bank card and the third bank card are respectively determined according to the transaction span time of the transaction channels and the target transaction object, and a candidate transaction object set comprising the transaction channels and the target transaction object is constructed; the transaction time span between the resource account A and the resource account and the current time is the minimum, and the transaction time span between the third bank card and the resource account and the current time is the maximum.
Further, after a candidate transaction object set which is the same as the resource account is constructed, resource transaction of the same user can be carried out according to the candidate transaction object set. And the resource transaction with the user comprises resource circulation between the resource account and the candidate transaction object. In this embodiment, the process of resource transaction with a user is specifically described with the fund flow and the interest flow of a resource account and a candidate transaction object.
In a first optional implementation manner provided by this embodiment, performing resource transaction with the user according to the candidate transaction object set is implemented by:
transferring funds in the resource account to any selected one of the candidate transaction objects in the set of candidate transaction objects;
or,
transferring funds from any one of the selected candidate transaction objects from the set of candidate transaction objects to the resource account.
Specifically, funds in the resource account are transferred to the selected candidate transaction objects in the set of candidate transaction objects, or the funds of the selected candidate transaction objects in the set of candidate transaction objects are transferred to the resource account.
The candidate transaction objects comprise transaction channels and other types of resource accounts; optionally, the set of candidate transaction objects includes a group account created by the user participating in the group service based on the resource account; the group account is a resource account included in the candidate transaction object; for example, a family account in the family group charges the family account based on the resource account, i.e., funds in the resource account are transferred to the family account. Or the candidate transaction object comprises a financial account obtained by opening a financial service based on the resource account by the user; the financial account may be opened based on the resource account.
In addition, in addition to performing resource flow processing on the resource account and the candidate transaction objects in the candidate transaction object set, resource flow may also be performed based on the candidate transaction objects in the candidate transaction object set.
For example, the candidate transaction object set which is the same user as the resource account includes four candidate transaction objects of the resource account a, the first bank card, the second bank card and the third bank card. The fund of the first bank card can be transferred to the second bank card, and the fund of the third bank card can also be transferred to the resource account A; other fund flows are similar to the above-mentioned flow process, and the description of this embodiment is omitted here.
In a second optional implementation manner provided by this embodiment, performing resource transaction with the user according to the candidate transaction object set is implemented by:
transferring the rights and interests in the resource account to any selected candidate transaction object in the candidate transaction object set;
or,
transferring the right to the resource account from any one selected candidate transaction object in the candidate transaction object set.
Specifically, in order to increase the utilization rate of the rights issued to the resource account, the rights and interests can be circulated between the resource account and the candidate transaction object set; that is, the rights and interests in the resource account are transferred to the selected candidate transaction objects in the candidate transaction object set, or the rights and interests of the selected candidate transaction objects in the candidate transaction object set are transferred to the resource account.
In addition, fund and/or equity flow can be conducted in the candidate transaction object set; for example, funds and/or benefits of a first candidate transaction object in the set of candidate transaction objects are transferred to a second candidate transaction object in the set of candidate transaction objects.
In specific implementation, in order to improve the perception degree of a user during execution, after a candidate transaction object set which is the same as a user of a resource account is constructed, the candidate transaction object set is issued to a login terminal of the resource account, so that the candidate transaction object set is displayed at the login terminal.
Step S1204, receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set.
Specifically, after a candidate transaction object set is constructed by the server side, the candidate transaction object set is issued to a login terminal of the resource account, and the login terminal acquires the candidate transaction object set which is the same as the logged-in resource account and carries out display processing; optionally, the display processing includes: displaying the identity information corresponding to the candidate transaction object set in a historical transaction list of the resource account; optionally, after an access entry of a resource transaction service of an application installed in the login terminal is triggered, displaying the identity information corresponding to the candidate transaction object set in a historical transaction list of the resource account; wherein the historical transaction list is generated based on the set of candidate transaction objects and the historical transaction objects.
Further, in order to improve the perception degree of the user on the candidate transaction object of the same user, optionally, the identity information is located at the head of the list in the historical transaction list; and if the identity identification information in the historical transaction list is triggered, displaying the candidate transaction objects contained in the candidate transaction object set.
For example, a user u1 accesses a resource transaction (transfer) service through a login terminal for logging in a resource account, wherein after detecting an access instruction for the resource transfer service, the login terminal equivalently acquires a resource transaction request submitted by the user u1, and submits the resource transaction request to a server to construct a candidate transaction object set of the same user as the resource account; the login terminal receives a historical transaction object identifier which is issued by the server and contains a candidate transaction object set; presenting a transaction list presentation page as shown in fig. 2 to the user u 1; the user u1 is a user to which the resource account belongs and is located at the head of the list, and the arrangement sequence of the historical transaction object identifiers is determined based on the transaction time span of each historical transaction object. And if the fact that the identity identification information aiming at the user u1 is triggered is detected, jumping to a candidate transaction object display page shown in fig. 3, and displaying the candidate transaction objects contained in the candidate transaction object set.
It should be noted that, in order to ensure the privacy of the historical transaction object, in the process of displaying the historical transaction object identifier, the account name of the historical transaction object is displayed, and the desensitization result of the real user identifier (actual user name) of the historical transaction object is displayed; as shown in fig. 2.
In practical application, if a user u to which a resource account belongs has two resource accounts, one is a logged-in resource account and the other is a resource account a, the user has multiple bank cards, for example, a first bank card and a second bank card bound to the logged-in resource account and a third bank card bound to the resource account a, because the users bound to the first bank card, the second bank card and the third bank card are the same, optionally, in the process of constructing the candidate transaction object set, a transaction channel bound to the resource account which is the same as the logged-in resource account is determined as the transaction channel of the logged-in resource account.
As shown in fig. 3, the first bank is shown as a transaction channel bound to a logged-in resource account; the second bank is the transaction channel bound to resource account a.
In order to further improve the perception degree of the user on the transaction records of the candidate transaction object of the same user, optionally, the user can operate the candidate transaction object through the candidate transaction object displayed by the sliding login terminal; optionally, if a first touch action for the candidate transaction object is detected, the transaction record of the candidate transaction object and the resource account for which the first touch action is directed is obtained and displayed. If a second touch action for the candidate transaction object is detected, deleting the candidate transaction object for the second touch action from the historical transaction list, and/or deleting the candidate transaction object for the second touch action from the candidate transaction object set.
Specifically, the user may manage the historical transaction list through a page as shown in fig. 2 or fig. 3, where the management includes viewing transaction records of target historical transaction objects in the historical transaction list and deleting the target historical transaction objects.
Along the above example, the user u1 slides the resource account a shown in fig. 3, and the login terminal displays the management control for the resource account a shown in fig. 4; the method comprises a transaction record control and a deletion control for checking transaction records, wherein if a touch action on the transaction record control is detected, historical transaction records of a resource account and a resource account A are obtained and displayed; and if the touch action on the deleting control is detected, deleting the resource account A from the list.
In addition, the aaa1 shown in fig. 2 may also be slid to manage aaa1, which is similar to the management of the resource account a described above, and this embodiment is not described herein again.
For a user applying for a resource account but not performing identity authentication (real-name authentication) on the resource account, in order to ensure the security of the user participating in resource service and protect the privacy of the user, a transaction channel can be bound after the user performs identity authentication and identity authorization, and the bound transaction channel and a historical transaction object are read; in the case that the user does not perform identity authentication, since the identity authentication information of the user cannot be obtained, and the historical transaction object and the user identity of the user cannot be obtained, in order to improve the user's experience of participating in resource services or resource transaction services and improve the user's mind, in an optional implementation manner provided by this embodiment, if the resource account does not perform identity authentication, identity authentication prompting information is displayed in the historical transaction list of the resource account; after the identity authentication reminding information is triggered, identity authentication processing of the resource account is carried out; and/or if the resource account is not bound with a transaction channel, displaying the identity information corresponding to the resource account in a historical transaction list of the resource account; and performing transaction channel binding processing of the resource account after the identity identification information is triggered.
Specifically, under the condition that the resource account is not subjected to identity authentication, and under the condition that a user accesses the resource transaction service, identity authentication reminding information is displayed in a historical transaction list; further, after the user performs identity authentication, only the identity identification information of the user to which the resource account belongs is displayed in a historical transaction list under the condition that the resource account is not bound to a transaction channel, namely, an unbound bank card; and if the fact that the identity identification information is triggered is detected, displaying a channel binding reminder to the user. In addition, the user can also perform transaction channel binding processing by triggering a channel binding reminder.
For example, the user u1 accesses the resource transaction service through the login terminal of the resource account, if the login terminal detects that the resource account is not authenticated, the real-name reminding page shown in fig. 5 is displayed, and the user u1 can perform identity authentication processing by triggering "deauthentication"; after the identity authentication processing is performed, a transaction list display page shown in fig. 2 is displayed through interaction data with a server, a channel binding reminder shown in fig. 6 is displayed when it is detected that a user u1 triggers the user u1 and the resource account is not bound to a transaction channel, and the transaction channel binding processing is performed if it is detected that the reminder content of the channel binding reminder is triggered.
In addition, since the historical transaction records are the privacy of the data user to a certain extent, and the resource of the user can be transferred through the resource account after the identity authentication is performed, in order to ensure the data security of the user, the user accesses the resource transaction service, and if the login terminal detects that the resource account is not authenticated, the real-name reminding page only containing the real-name reminding content is displayed.
That is, in the above example, the user u1 accesses the resource transaction service through the login terminal of the resource account, and if the login terminal detects that the resource account is not authenticated, the real-name reminding page shown in fig. 7 is displayed; similar to the above examples, the present embodiment is not described herein again.
Step S1206, performing resource transaction between the resource account and the same user as the candidate transaction object based on the transaction instruction.
In specific implementation, if a transaction instruction of a user for any one of the candidate transaction objects in the candidate transaction object set is received, the equity and/or fund in the resource account is transferred to and/or from the candidate transaction object based on the transaction instruction.
The third embodiment of the resource transaction processing method provided by the present specification:
the resource transaction processing method provided by the embodiment is applied to a server, and the resource transaction processing method provided by the following embodiment is applied to a login terminal of a logged-in resource account.
Referring to fig. 13, the resource transaction processing method provided in this embodiment is applied to a server, and specifically includes steps S1302 to S1308.
Step S1302, receiving a resource transaction request submitted by a login terminal that has logged in a resource account.
Step S1304, according to the resource transaction request, obtaining a historical transaction object of the resource account, and inquiring the identity authentication information of the resource account and the bound transaction channel.
Step S1306, the identity authentication information and the identity authentication information of the historical transaction object are verified, and the target transaction object of the same user as the resource account is determined according to the verification result.
Step S1308, based on the transaction channel and the target transaction object, constructing a candidate transaction object set that is the same as the resource account and issuing the candidate transaction object set to the login terminal for display processing.
Optionally, the following operations are also performed:
receiving a transaction request which is submitted by the login terminal and carries the resource account, any one candidate transaction object selected by the user in the candidate transaction object set, the resource amount and the transaction type;
if the transaction type is a transfer-out type, transferring the resource corresponding to the resource amount in the resource account to any one candidate transaction object;
and if the transaction type is a transfer-in type, transferring the resource corresponding to the resource amount in any one candidate transaction object to the resource account.
Optionally, the method further includes issuing a transaction result to the login terminal after the resource is transferred.
Similar to the execution process of the resource transaction processing method for the first transaction bill, please refer to the relevant content of the first embodiment for reading the present embodiment, and refer to the specific implementation process of the resource transaction processing method provided in the first embodiment for reading the relevant content of the present embodiment, which is not described herein again; in addition, the related contents of this embodiment can also be referred to in reading the above first embodiment.
A fourth embodiment of a resource transaction processing method provided in this specification:
referring to fig. 14, the resource transaction processing method provided in this embodiment is applied to a login terminal of a logged-in resource account, and specifically includes steps S1402 to S1406.
Step S1402, in case that an access instruction of the user to the resource transaction service is detected, submits a resource transaction request to the server.
Step S1404, receiving a candidate transaction object set issued by the server and being the same as the resource account for the same user, and performing display processing.
Step S1406, obtaining a transaction instruction of the user for any one candidate transaction object in the candidate transaction object set, and submitting a transaction request to the server.
Optionally, the method further includes receiving and displaying a transaction result sent by the server.
Similar to the execution process of the resource transaction processing method for the first transaction bill, please refer to the relevant contents of the first embodiment in this embodiment, and refer to the specific implementation process of the resource transaction processing method provided in the first embodiment in this embodiment, which is not described herein again; in addition, the related contents of this embodiment can also be referred to in reading the above first embodiment.
An embodiment of a resource transaction processing apparatus provided in this specification is as follows:
in the above embodiment, a first resource transaction processing method is provided, and correspondingly, a resource transaction processing apparatus is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 15, a schematic diagram of a resource transaction processing apparatus provided in this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The embodiment provides a resource transaction processing device, which comprises:
an obtaining module 1502 configured to obtain a historical transaction object of a logged resource account, and query the identity authentication information of the resource account and a bound transaction channel;
the verification module 1504 is configured to verify the identity authentication information and the identity authentication information of the historical transaction object, and determine that the resource account is a target transaction object of the same user according to the verification result;
the construction module 1506 is configured to construct a candidate transaction object set which is the same user as the resource account based on the transaction channel and the target transaction object, so as to perform resource transaction of the same user according to the candidate transaction object set.
Another embodiment of a resource transaction processing apparatus provided in this specification is as follows:
in the above embodiment, a second resource transaction processing method is provided, and correspondingly, a resource transaction processing apparatus is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 16, a schematic diagram of a resource transaction processing apparatus provided in this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The embodiment provides a resource transaction processing device, which comprises:
an obtaining module 1602, configured to obtain a candidate transaction object set that is the same as the logged-in resource account as the user according to the resource transaction request submitted by the user, and perform display processing;
a receiving module 1604 configured to receive a transaction instruction for any one of the set of candidate transaction objects by the user;
a resource trading module 1606 configured to conduct resource trading between the resource account and the co-user of the candidate trading object based on the trading instruction.
An embodiment of a resource transaction processing apparatus provided in this specification is as follows:
corresponding to the first resource transaction processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide a resource transaction processing device, where the resource transaction processing device is configured to execute the resource transaction processing method provided above, and fig. 17 is a schematic structural diagram of the resource transaction processing device provided in one or more embodiments of the present specification.
The embodiment provides a resource transaction processing device, which comprises:
as shown in fig. 17, the resource transaction processing apparatus may have a large difference due to different configurations or performances, and may include one or more processors 1701 and a memory 1702, and one or more stored applications or data may be stored in the memory 1702. Memory 1702 may be transient or persistent storage, among other things. The application program stored in the memory 1702 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a resource transaction processing device. Further, the processor 1701 may be configured to communicate with the memory 1702 to execute a series of computer-executable instructions in the memory 1702 on the resource transaction processing device. The resource transaction processing apparatus may also include one or more power supplies 1703, one or more wired or wireless network interfaces 1704, one or more input/output interfaces 1705, one or more keyboards 1706, and the like.
In one particular embodiment, a resource transaction processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the resource transaction processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:
acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel;
verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result;
and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
Another embodiment of a resource transaction processing apparatus provided in this specification is as follows:
corresponding to the second resource transaction processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide a resource transaction processing device, where the resource transaction processing device is configured to execute the resource transaction processing method provided above, and fig. 18 is a schematic structural diagram of a resource transaction processing device provided in one or more embodiments of the present specification.
The embodiment provides a resource transaction processing device, which comprises:
as shown in fig. 18, the resource transaction processing device may have a large difference due to different configurations or performances, and may include one or more processors 1801 and a memory 1802, and one or more stored applications or data may be stored in the memory 1802. Memory 1802 may be, among other things, transient storage or persistent storage. The application program stored in memory 1802 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a resource transaction processing device. Still further, the processor 1801 may be configured to communicate with the memory 1802 and execute a series of computer-executable instructions in the memory 1802 on the resource transaction processing device. The resource transaction processing apparatus may also include one or more power supplies 1803, one or more wired or wireless network interfaces 1804, one or more input/output interfaces 1805, one or more keyboards 1806, etc.
In one particular embodiment, a resource transaction processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the resource transaction processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:
according to a resource transaction request submitted by a user, acquiring a candidate transaction object set which is the same as the user with a logged-in resource account and displaying the candidate transaction object set;
receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
An embodiment of a storage medium provided in this specification is as follows:
corresponding to the resource transaction processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide a storage medium.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the following processes are implemented:
acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel;
verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result;
and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the resource transaction processing method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described here.
Another storage medium embodiment provided in this specification is as follows:
on the basis of the same technical concept, corresponding to the second resource transaction processing method described above, one or more embodiments of the present specification further provide a storage medium.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the following processes are implemented:
according to a resource transaction request submitted by a user, acquiring a candidate transaction object set which is the same as the user with a logged-in resource account and displaying the candidate transaction object set;
receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the resource transaction processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the foregoing corresponding method, and repeated parts are not described again.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical blocks. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development, but the original code before compiling is also written in a specific Programming Language, which is called Hardware Description Language (HDL), and the HDL is not only one kind but many kinds, such as abll (Advanced boot Expression Language), AHDL (alternate hard Description Language), traffic, CUPL (computer universal Programming Language), HDCal (Java hard Description Language), lava, lola, HDL, PALASM, software, rhydl (Hardware Description Language), and vhul-Language (vhyg-Language), which is currently used in the field. It will also be apparent to those skilled in the art that hardware circuitry for implementing the logical method flows can be readily obtained by a mere need to program the method flows with some of the hardware description languages described above and into an integrated circuit.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that 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 a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims (25)

1. A resource transaction processing method, comprising:
acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel;
verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining a target transaction object which is the same as the resource account and is the same as the user according to a verification result;
and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
2. The resource transaction processing method according to claim 1, wherein the verifying the identity authentication information with the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result comprises:
determining a verification mode for verifying the identity authentication information of the historical transaction object according to the object type of the historical transaction object;
verifying whether the identity authentication information of the historical transaction object is matched with the identity authentication element of the identity authentication information of the resource account or not according to the verification mode;
and if so, determining the matched historical transaction object as a target transaction object which is the same as the resource account and is the same as the user.
3. The resource transaction processing method of claim 1, the historical transaction object, comprising: historical resource accounts and/or historical transaction channels for resource transaction exist between the resource accounts and the resource accounts within a preset time range;
wherein the historical resource accounts include at least one of: fund accounts, equity accounts, service accounts.
4. The resource transaction processing method according to claim 3, wherein the verifying the identity authentication information with the identity authentication information of the historical transaction object and determining that the resource account is the target transaction object of the same user according to the verification result comprises:
verifying whether the identity of the resource account is matched with the identity of the historical resource account;
if so, verifying whether the identity authentication mode of the resource account is the same as that of the historical resource account, and if so, determining the historical resource account as a target resource account which is the same as the resource account;
and/or the presence of a gas in the gas,
verifying whether the identity of the resource account is matched with the identity of the historical transaction channel;
if so, determining the identity of the resource account as a target transaction channel with the same identity as the resource account.
5. The resource transaction processing method of claim 1, further comprising:
issuing the candidate transaction object set to a login terminal of the resource account so as to display the candidate transaction object set at the login terminal;
receiving a trading instruction aiming at any one candidate trading object contained in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
6. The resource transaction processing method according to claim 5, wherein after an access entry of a resource transaction service of an application installed in the login terminal is triggered, identity information corresponding to the candidate transaction object set is displayed in a historical transaction list of the resource account;
wherein the historical transaction list is generated based on the set of candidate transaction objects and the historical transaction object.
7. The resource transaction processing method according to claim 6, wherein the identification information is located at the head of the list in the historical transaction list;
and if the identity identification information in the historical transaction list is triggered, displaying the candidate transaction objects contained in the candidate transaction object set.
8. The resource transaction processing method according to claim 7, wherein if a first touch action for the candidate transaction object is detected, a transaction record of the candidate transaction object and the resource account for which the first touch action is specific is obtained and displayed.
9. The resource transaction processing method according to claim 7, wherein if a second touch action for the candidate transaction object is detected, the candidate transaction object targeted by the second touch action is deleted from the historical transaction list, and/or the candidate transaction object targeted by the second touch action is deleted from the candidate transaction object set.
10. The resource transaction processing method of claim 1, said conducting resource transactions with users according to the set of candidate transaction objects, comprising:
transferring funds in the resource account to any selected one of the candidate transaction objects in the set of candidate transaction objects;
or,
transferring funds from any one of the selected candidate transaction objects from the set of candidate transaction objects to the resource account.
11. The resource transaction processing method of claim 1, said conducting resource transactions with users according to the set of candidate transaction objects, comprising:
transferring the rights and interests in the resource account to any selected candidate transaction object in the candidate transaction object set;
or,
transferring the right to the resource account from any one selected candidate transaction object in the candidate transaction object set.
12. The resource transaction processing method according to claim 1, further comprising, after the step of verifying the identity authentication information and the identity authentication information of the historical transaction object, and after the step of determining that the resource account is the same user as the target transaction object according to the verification result is executed, and before the step of constructing a candidate transaction object set that is the same user as the resource account based on the transaction channel and the target transaction object, so as to execute the resource transaction step of the same user according to the candidate transaction object set:
verifying whether the identity certificate information of the transaction channel and/or the target transaction object for identity authentication is matched with the identity authentication information associated with the resource account;
if yes, executing the candidate transaction object set which is the same as the resource account and is the same as the resource account based on the transaction channel and the target transaction object, and performing the resource transaction step of the same user according to the candidate transaction object set;
if not, removing the unmatched transaction channels and/or the target transaction objects.
13. The resource transaction processing method of claim 1, wherein constructing a set of candidate transaction objects that are co-user with the resource account based on the transaction channel and the target transaction object comprises:
determining a transaction time span according to the transaction channel and the transaction records of the target transaction object and the resource account;
constructing the candidate transaction object set by taking the transaction channel and the target transaction object as candidate transaction objects, and determining the display priority of the candidate transaction objects contained in the candidate transaction object set based on the transaction time span;
wherein the transaction time span is negatively correlated with the presentation priority.
14. The resource transaction processing method of claim 1, further comprising:
if the resource account is not subjected to identity authentication, displaying identity authentication reminding information in a historical transaction list of the resource account;
after the identity authentication reminding information is triggered, identity authentication processing of the resource account is carried out;
and/or the presence of a gas in the gas,
if the resource account is not bound with a transaction channel, displaying the identity identification information corresponding to the resource account in a historical transaction list of the resource account;
and performing transaction channel binding processing of the resource account after the identity identification information is triggered.
15. The resource transaction processing method of claim 3, further comprising:
inquiring the identity authentication information of the historical resource account and the historical transaction channel;
and determining the historical resource account and the historical transaction channel of the same user based on the identity authentication information of the historical resource account and the historical transaction channel, and constructing a second candidate transaction object set based on the historical resource account and the historical transaction channel of the same user.
16. A resource transaction processing method, comprising:
according to a resource transaction request submitted by a user, acquiring a candidate transaction object set which is the same as a logged-in resource account and is displayed;
receiving a transaction instruction of the user for any one candidate transaction object in the candidate transaction object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
17. The resource transaction processing method of claim 16, wherein the set of candidate transaction objects is constructed and obtained based on a transaction channel bound to the resource account and a target transaction object for the same user as the resource account;
and determining the verification result of verifying the identity authentication information of the resource account and the identity authentication information of the historical transaction object.
18. The resource transaction processing method of claim 16, the presentation processing comprising: displaying the identity identification information corresponding to the candidate transaction object set in a historical transaction list of the resource account;
correspondingly, if the identity information in the historical transaction list is triggered, the candidate transaction objects contained in the candidate transaction object set are displayed.
19. The resource transaction processing method of claim 16, the conducting a resource transaction of the resource account with the same user as the candidate transaction object based on the transaction instruction, comprising:
transferring funds and/or equity in the resource account to the candidate transaction object;
or,
transferring funds and/or equity from the candidate transaction object to the resource account.
20. A resource transaction processing apparatus comprising:
the acquisition module is configured to acquire a historical transaction object of a logged resource account, and inquire identity authentication information of the resource account and a bound transaction channel;
the verification module is configured to verify the identity authentication information and the identity authentication information of the historical transaction object, and determine that the resource account is the target transaction object of the same user according to the verification result;
and the construction module is configured to construct a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object so as to conduct resource transaction of the same user according to the candidate transaction object set.
21. A resource transaction processing apparatus comprising:
the acquisition module is configured to acquire a candidate transaction object set which is the same as the logged-in resource account as a user according to a resource transaction request submitted by the user and perform display processing;
a receiving module configured to receive a trading instruction of the user for any one of the candidate trading objects in the candidate trading object set;
a resource transaction module configured to conduct a resource transaction of the resource account with the same user as the candidate transaction object based on the transaction instruction.
22. A resource transaction processing device comprising:
a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:
acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel;
verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result;
and constructing a candidate transaction object set which is the same as the resource account and is the same as the user on the basis of the transaction channel and the target transaction object, so as to carry out resource transaction of the same user according to the candidate transaction object set.
23. A resource transaction processing device comprising:
a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:
according to a resource transaction request submitted by a user, acquiring a candidate transaction object set which is the same as the user with a logged-in resource account and displaying the candidate transaction object set;
receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
24. A storage medium storing computer-executable instructions that when executed by a processor implement the following:
acquiring a historical transaction object of a logged resource account, and inquiring identity authentication information of the resource account and a bound transaction channel;
verifying the identity authentication information and the identity authentication information of the historical transaction object, and determining that the resource account is the target transaction object of the same user according to the verification result;
and constructing a candidate transaction object set which is the same as the resource account and is the same as the user based on the transaction channel and the target transaction object, so as to perform resource transaction of the same user according to the candidate transaction object set.
25. A storage medium storing computer-executable instructions that when executed by a processor implement the following:
according to a resource transaction request submitted by a user, acquiring a candidate transaction object set which is the same as the user with a logged-in resource account and displaying the candidate transaction object set;
receiving a trading instruction of the user for any one candidate trading object in the candidate trading object set;
and performing resource transaction between the resource account and the same user of the candidate transaction object based on the transaction instruction.
CN202211019288.8A 2022-08-24 2022-08-24 Resource transaction processing method and device Pending CN115330373A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211019288.8A CN115330373A (en) 2022-08-24 2022-08-24 Resource transaction processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211019288.8A CN115330373A (en) 2022-08-24 2022-08-24 Resource transaction processing method and device

Publications (1)

Publication Number Publication Date
CN115330373A true CN115330373A (en) 2022-11-11

Family

ID=83925073

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211019288.8A Pending CN115330373A (en) 2022-08-24 2022-08-24 Resource transaction processing method and device

Country Status (1)

Country Link
CN (1) CN115330373A (en)

Similar Documents

Publication Publication Date Title
US11379818B2 (en) Systems and methods for payment management for supporting mobile payments
CN110889693B (en) Payment method, device and system
CN111784345B (en) Payment processing method, device, equipment and system
Alqahtani et al. Exploratory Study of M‐Transaction: User's Perspectives
CN112016136A (en) Data processing method and device based on alliance chain
CN114548963B (en) Payment interaction processing method and device
US20170364944A1 (en) Systems and methods for efficient processing of large scale propagation of resources among accounts
CN114463110A (en) Credit granting system and method based on block chain
CN107528822B (en) Service execution method and device
Kazan The innovative capabilities of digital payment platforms: A comparative study of Apple pay & Google wallet
CN113095507A (en) Method, device, equipment and medium for training and predicting machine learning model
US10922392B2 (en) Systems and methods for generating and managing composite digital identities
US20200234288A1 (en) Systems and methods of securing sensitive data
Heath et al. Digital Enlightenment, Mydex, and restoring control over personal data to the individual
CN115330373A (en) Resource transaction processing method and device
CN115330372A (en) Payment processing method and device based on prepaid voucher
CN113497805B (en) Registration processing method, device, equipment and system
Pust The future of money: How Bitcoin and its underlying Blockchain technology could affect the financial sector
CN113419794A (en) Payment processing method and device
Nyström A Qualitative study of Possible Drivers and Barriers to Consumer Adoption of Open Banking Services
EP3541039A1 (en) Method and apparatus for accessing controlled data
US20220058621A1 (en) Methods and systems for facilitating managing of payments made using digital wallets
WO2019143816A1 (en) Systems and methods of securing sensitive data
WO2019143586A1 (en) Provisioning of payment acceptance to payment account holders
KR102439779B1 (en) Method, system and non-transitory computer-readable recording medium for providing entitlement-based service using a blockchain network

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