Cross-transaction-channel transaction data processing method and device, equipment and storage medium
By reusing the signing information of other trading channels in multiple trading channels, the problem that users need to sign multiple contracts for the same transaction type under multiple channels is solved, and the transaction experience and efficiency are improved.
Patent Information
- Application Number
- CN202411101958.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-12
- Publication Date
- 2024-11-29
AI Technical Summary
In the multi-trading channel scenario, users need to sign multiple contracts for the same transaction type, resulting in poor transaction experience.
By receiving the user's transaction request, confirm whether there is any signing information for the target transaction type. If it does not exist, confirm the signing information of other trading channels and reuse it as the signing information of the current trading channel for consistency verification and subsequent inspection Transaction logic execution.
This greatly reduces the repeated signing problem of users for the same transaction type in multiple transaction channels scenarios, and improves transaction experience and processing efficiency.
Smart Images

Figure CN119048236A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of financial technology, and in particular to a method, device, equipment and storage medium for processing transaction data across transaction channels. Background Art
[0002] The transaction channel is a channel through which the core transaction system supports user transactions. For example, different mobile terminals (such as mobile banking, etc.), bank counters, ATM machines, POS machines, etc. are all different transaction channels. In order to improve the security and standardization of transactions, in traditional transaction data processing, for each transaction channel, users must first sign a contract for the transaction channel (i.e., business contract) before initiating a transaction in the transaction channel. For example, a user has signed a contract for a Class A transaction on the mobile banking client, but has not signed a contract for a Class A transaction on the XX Life client. If the user wants to initiate a Class A transaction through the XX Life client, he or she must also sign a contract for a Class A transaction on the XX Life client. In other words, in the prior art, for the same transaction type, there are N supported transaction channels, and the user needs to sign at least N times before using these transaction channels to initiate a Class A transaction. In this multi-transaction channel scenario, the user's repeated signing of contracts for the same transaction type makes the user's transaction experience poor. Summary of the invention
[0003] The purpose of the embodiments of this specification is to provide a transaction data processing method, device, equipment and storage medium across transaction channels to reduce or avoid repeated signing of contracts for the same transaction type by users in multi-transaction channel scenarios, thereby improving the user's transaction experience.
[0004] To achieve the above objectives, on the one hand, an embodiment of this specification provides a method for processing transaction data across transaction channels, including:
[0005] Receiving a transaction request for a target transaction type initiated by a user based on a first transaction channel;
[0006] confirming whether there is first signing information of the user for the first transaction channel and the target transaction type;
[0007] When the first contract information does not exist, confirming whether there is second contract information of the user for other transaction channels and the target transaction type;
[0008] When the second contract information exists, the second contract information is multiplexed as the first contract information of the user for the first transaction channel and the target transaction type;
[0009] Performing consistency verification on the first signing information and the user identity information of the user;
[0010] When the first signing information and the user identity information pass the consistency verification, the subsequent transaction logic of the transaction request is executed.
[0011] In the transaction data processing method across transaction channels of the embodiment of this specification, after confirming whether there is second contract information of the user for other transaction channels and the target transaction type, it also includes:
[0012] When the second contract information does not exist, triggering a processing logic for guiding the user to sign a contract for the first transaction channel and the target transaction type;
[0013] The signing information when the user successfully signs the contract for the first transaction channel and the target transaction type is saved as the first signing information of the user for the first transaction channel and the target transaction type.
[0014] In the cross-transaction channel transaction data processing method of the embodiment of this specification, the second contract information is multiplexed as the first contract information of the user for the first transaction channel and the target transaction type, including:
[0015] backing up the second signing information;
[0016] A mapping relationship between the backup second contract information and the first transaction channel and the target transaction type is constructed to serve as the first contract information of the user for the first transaction channel and the target transaction type.
[0017] In the transaction data processing method across transaction channels of the embodiment of this specification, after verifying the consistency of the first contract information and the user identity information of the user, it also includes:
[0018] When the first contract information and the user identity information fail to pass the consistency verification, the subsequent transaction logic of the transaction request is rejected and a rejection reason prompt is returned.
[0019] In the transaction data processing method across transaction channels of the embodiment of this specification, the user identity information includes the user's certificate information and / or biometric information.
[0020] In the transaction data processing method across transaction channels of the embodiment of this specification, the first transaction channel includes a transaction channel based on a mobile terminal; the other transaction channels include transaction channels based on mobile terminals and / or other terminals that are different from the first transaction channel.
[0021] On the other hand, the embodiment of this specification also provides a cross-transaction channel transaction data processing device, including:
[0022] A receiving module, configured to receive a transaction request for a target transaction type initiated by a user based on a first transaction channel;
[0023] A first confirmation module, used to confirm whether there is first signing information of the user for the first transaction channel and the target transaction type;
[0024] A second confirmation module, used for confirming whether there is second contract information of the user for other transaction channels and the target transaction type when the first contract information does not exist;
[0025] a multiplexing module, configured to multiplex the second contract information as the first contract information of the user for the first transaction channel and the target transaction type when the second contract information exists;
[0026] A verification module, used to verify the consistency between the first signing information and the user identity information of the user;
[0027] An execution module is used to execute the subsequent transaction logic of the transaction request when the first signing information and the user identity information pass consistency verification.
[0028] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein when the computer program is executed by the processor, the instructions of the above method are executed.
[0029] On the other hand, an embodiment of the present specification further provides a computer storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer device, the instructions of the above method are executed.
[0030] On the other hand, an embodiment of the present specification further provides a computer program product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor of a computer device, the computer program executes instructions of the above method.
[0031] It can be seen from the technical solutions provided in the above embodiments of this specification that, in the embodiments of this specification, after receiving a transaction request for a target transaction type initiated by a user based on a certain transaction channel, it is possible to first confirm whether there is contract information of the user for the transaction channel and the target transaction type; if there is no contract information of the user for the transaction channel and the target transaction type, it is further confirmed whether there is contract information of the user for other transaction channels and the target transaction type; if there is contract information of the user for other transaction channels and the target transaction type, the contract information of the user for other transaction channels and the target transaction type can be reused as the contract information of the user for the transaction channel and the target transaction type. In this way, in a multi-transaction channel scenario, for the same transaction type, the user only needs to sign for any one of them, and can realize transactions for the transaction type based on other transaction channels by reusing the contract information, without having to sign for the transaction type one by one for other transaction channels, thereby greatly reducing or avoiding the problem of users repeatedly signing for the same transaction type in a multi-transaction channel scenario, and improving the user's transaction experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor. In the drawings:
[0033] Figure 1 A schematic diagram of an application environment for cross-transaction channel transaction data processing in some embodiments of this specification is shown;
[0034] Figure 2 A flowchart showing a method for processing transaction data across transaction channels in some embodiments of this specification;
[0035] Figure 3 A flowchart of multiplexing the second contract information into the first contract information in an exemplary embodiment of this specification is shown;
[0036] Figure 4 A schematic diagram showing how the second contract information is multiplexed as the first contract information in an exemplary embodiment of this specification;
[0037] Figure 5 A flowchart showing a method for processing transaction data across transaction channels in other embodiments of this specification;
[0038] Figure 6A structural block diagram of a transaction data processing device across transaction channels in some embodiments of this specification is shown;
[0039] Figure 7 The structure block diagram of the computer device in some embodiments of the present specification is shown.
[0040] [Description of Reference Numerals]
[0041] 10. Client;
[0042] 20. Server;
[0043] 61. Receiving module;
[0044] 62. First confirmation module;
[0045] 63. Second confirmation module;
[0046] 64. Multiplexing module;
[0047] 65. Verification module;
[0048] 66. Execution module;
[0049] 702. Computer equipment;
[0050] 704, processor;
[0051] 706. Memory;
[0052] 708, driving mechanism;
[0053] 710, input / output interface;
[0054] 712. Input devices;
[0055] 714. Output devices;
[0056] 716. Presentation equipment;
[0057] 718. Graphical user interface;
[0058] 720, network interface;
[0059] 722. Communication link;
[0060] 724. Communication bus. DETAILED DESCRIPTION
[0061] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.
[0062] Figure 1 A schematic diagram of the application environment for cross-transaction channel transaction data processing in some embodiments of this specification is shown in the figure; the application environment includes a client 10 and a server 20. The server 20 can receive a transaction request for a target transaction type initiated by a user based on a first transaction channel; confirm whether there is a first contract information of the user for the first transaction channel and the target transaction type; when the first contract information does not exist, confirm whether there is a second contract information of the user for other transaction channels and the target transaction type; when the second contract information exists, reuse the second contract information as the first contract information of the user for the first transaction channel and the target transaction type; perform consistency verification on the first contract information and the user identity information of the user; when the first contract information and the user identity information pass the consistency verification, execute the subsequent transaction logic of the transaction request. The embodiments of this specification can reduce or avoid the problem of repeated contract signing for the same transaction type by users in multi-transaction channel scenarios, thereby improving the user's transaction experience.
[0063] In some embodiments of the present specification, different clients 10 form different transaction channels. The client 10 may be a self-service terminal device, a mobile terminal (i.e., a smart phone), a display, a desktop computer, a tablet computer, a laptop computer, a digital assistant, or a smart wearable device, etc. The smart wearable device may include a smart bracelet, a smart watch, smart glasses, or a smart helmet, etc. Of course, the client 10 is not limited to the above-mentioned electronic devices with a certain entity, and it may also be software running in the above-mentioned electronic devices.
[0064] In some embodiments of the present specification, the server 20 may be an electronic device with computing and network interaction functions; or it may be software running in the electronic device and providing business logic for transaction data processing and network interaction.
[0065] The embodiment of this specification provides a transaction data processing method across transaction channels, which can be applied to the above-mentioned service side, refer to Figure 2 As shown, in some embodiments of this specification, a method for processing transaction data across transaction channels may include the following steps:
[0066] Step 201: Receive a transaction request for a target transaction type initiated by a user based on a first transaction channel.
[0067] Step 202: confirm whether there is first signing information of the user for the first transaction channel and the target transaction type.
[0068] Step 203: When the first contract information does not exist, confirm whether there is second contract information of the user for other transaction channels and the target transaction type.
[0069] Step 204: When the second contract information exists, the second contract information is multiplexed as the first contract information of the user for the first transaction channel and the target transaction type.
[0070] Step 205: verify the consistency between the first signing information and the user identity information of the user.
[0071] Step 206: When the first signing information and the user identity information pass the consistency verification, execute the subsequent transaction logic of the transaction request.
[0072] In the embodiments of this specification, after receiving a transaction request for a target transaction type initiated by a user based on a certain transaction channel, it is possible to first confirm whether there is contract information of the user for the transaction channel and the target transaction type; if there is no contract information of the user for the transaction channel and the target transaction type, it is further confirmed whether there is contract information of the user for other transaction channels and the target transaction type; if there is contract information of the user for other transaction channels and the target transaction type, the contract information of the user for other transaction channels and the target transaction type can be reused as the contract information of the user for the transaction channel and the target transaction type. In this way, in a multi-transaction channel scenario, for the same transaction type, the user only needs to sign for any one of them, and can realize transactions for the transaction type based on other transaction channels by reusing the contract information, without having to sign for the transaction type one by one for other transaction channels, thereby greatly reducing or avoiding the problem of users repeatedly signing for the same transaction type in a multi-transaction channel scenario, and improving the user's transaction experience.
[0073] In addition, in the embodiments of the present specification, for the same transaction type, since multiple transaction channels can share a copy of the contract information (that is, after a user has signed a contract for a certain transaction type in one of the transaction channels, the user does not need to sign a contract for the transaction type in other transaction channels, and can initiate transactions for the transaction type based on other transaction channels), the transaction data processing of the embodiments of the present specification can be referred to as cross-transaction channel transaction data processing.
[0074] In some embodiments of the present specification, for the same transaction type, the server may support multiple different transaction channels to initiate transactions, and the user may initiate transactions of this transaction type through any transaction channel based on their own usage preferences, operational convenience, etc.; for example, taking the gold accumulation business as an example, the user may initiate transactions for the gold accumulation business through the mobile banking APP; the user may also initiate transactions for the gold accumulation business through other APPs.
[0075] In some embodiments of the present specification, the contract information may include but is not limited to a contract account number, a transaction password, reserved information, a login password, a contract mobile phone number, etc.
[0076] In order to improve the security and standardization of transactions, in some embodiments of this specification, after receiving a transaction request for a target transaction type initiated by a user based on a first transaction channel, it is possible to first confirm whether there is a first contract information of the user for the first transaction channel and the target transaction type. For example, after receiving a transaction request for a target transaction type initiated by a user based on a first transaction channel, the user's contract information can be queried from the user contract information database based on the user's user identity information (such as identity card ID, mobile phone number login) to determine whether there is a first contract information of the user for the first transaction channel and the target transaction type. Among them, the above-mentioned user contract information database may refer to a user contract information database of the same transaction service provider. Among them, the same transaction service provider can be, for example, a user contract information database of the same banking institution (such as XX Bank).
[0077] If the first contract information of the user for the first transaction channel and the target transaction type is queried, it can be confirmed that the user has signed a contract for the first transaction channel, and the subsequent transaction logic can be executed based on the first contract information. If the first contract information of the user for the first transaction channel and the target transaction type is not queried, it can be confirmed that the user has not signed a contract for the first transaction channel.
[0078] In order to reduce or avoid repeated signing of contracts for the same transaction type by users in a multi-transaction channel scenario and improve transaction processing efficiency, when the first signing information does not exist (that is, the first signing information of the user for the first transaction channel and the target transaction type is not queried), it can be further determined whether there is second signing information of the user for other transaction channels and the target transaction type; when the second signing information exists, the second signing information can be reused as the first signing information of the user for the first transaction channel and the target transaction type, so that the user can use the first transaction channel to conduct transactions when signing a contract for the first transaction channel and the target transaction type.
[0079] In some embodiments of the present specification, the first transaction channel includes a transaction channel based on a mobile terminal (for example, an APP client with transaction functions installed on a smart phone); the other transaction channels include transaction channels based on mobile terminals and / or other terminals that are different from the first transaction channel (for example, other APP clients with transaction functions installed on smart phones, desktop computers, tablet computers, laptops and / or smart wearable devices).
[0080] Other transaction channels refer to: transaction channels other than the first transaction channel among all transaction channels supported by the server for the same transaction type. For example, in an exemplary embodiment, for domestic transfer transactions, the full transaction channels supported by the server include: transaction channel C1, transaction channel C2, transaction channel C3, transaction channel C4 and transaction channel C5. If the user initiates a transaction request for a domestic transfer for the target transaction type through transaction channel C5, then transaction channel C1, transaction channel C2, transaction channel C3 and transaction channel C4 are all other transaction channels relative to transaction channel C5.
[0081] refer to Figure 3 As shown, in some embodiments of this specification, multiplexing the second contract information as the first contract information of the user for the first transaction channel and the target transaction type may include the following steps:
[0082] Step 301: Back up the second signing information.
[0083] Step 302: Construct a mapping relationship between the backup second contract information and the first transaction channel and the target transaction type, so as to serve as the first contract information of the user for the first transaction channel and the target transaction type.
[0084] In this way, when the user initiates a transaction request for the target transaction type through the first transaction channel next time, the server can more conveniently obtain the first signing information for the first transaction channel and the target transaction type, thereby eliminating the need to perform steps such as confirming whether there is second signing information of the user for other transaction channels and the target transaction type when the first signing information does not exist; and reusing the second signing information as the user's first signing information for the first transaction channel and the target transaction type when the second signing information exists, thereby helping to further improve the processing efficiency of transaction data processing.
[0085] For example, in Figure 4 In the illustrated embodiment, before a user initiates a transaction request for transaction type X through transaction channel A, the user has signed a contract for transaction channel B and transaction type X, and the server has saved the user's contract information for transaction channel B and transaction type X. When a transaction request for transaction type X is initiated through transaction channel A, since the user has not signed a contract for transaction channel A and transaction type X, the user's contract information for transaction channel B and transaction type X can be reused as the user's contract information for transaction channel A and transaction type X. Figure 4 In the figure, <transaction channel A, transaction type X: contract information> means that the contract information is the contract information for transaction channel A and transaction type X; <transaction channel B, transaction type X: contract information> means that the contract information is the contract information for transaction channel B and transaction type X.
[0086] In some embodiments of the present specification, performing consistency verification on the first contract information and the user identity information of the user may include: collecting the user identity information of the user, comparing the collected user identity information with the user identity information in the first contract information to determine whether the collected user identity information is consistent with the user identity information in the first contract information; if they are consistent, confirming that the first contract information and the user identity information have passed the consistency verification; otherwise, confirming that the first contract information and the user identity information have not passed the consistency verification. The user identity information may include, for example, the user's certificate information and / or biometric information. Performing consistency verification on the first contract information and the user's user identity information is conducive to further improving transaction security.
[0087] In some embodiments of the present specification, executing the subsequent transaction logic of the transaction request may include executing the remaining transaction processing logic and returning the transaction result.
[0088] refer to Figure 5As shown, in some other embodiments of this specification, the transaction data processing method across transaction channels may include the following steps:
[0089] Step 501: Receive a transaction request for a target transaction type initiated by a user based on a first transaction channel.
[0090] Step 502: confirm whether there is first contract information of the user for the first transaction channel and the target transaction type. If there is no first contract information of the user for the first transaction channel and the target transaction type, execute step 503; otherwise, execute step 507.
[0091] Step 503: confirm whether there is second contract information of the user for other transaction channels and the target transaction type. If there is no second contract information of the user for other transaction channels and the target transaction type, execute step 504; otherwise, execute step 506.
[0092] Step 504: trigger processing logic for guiding the user to sign a contract for the first transaction channel and the target transaction type.
[0093] Step 505: Save the contract signing information when the user successfully signs the contract for the first transaction channel and the target transaction type as the first contract signing information of the user for the first transaction channel and the target transaction type.
[0094] In this way, through steps 504 to 505, the user can complete the signing of the first transaction channel and the target transaction type.
[0095] Step 506: reuse the second contract information as the first contract information of the user for the first transaction channel and the target transaction type. Then execute step 507.
[0096] Step 507: verify the consistency between the first signing information and the user identity information of the user.
[0097] Step 508: Determine whether the first contract information is consistent with the user identity information. If the first contract information is consistent with the user identity information, execute step 509; otherwise, execute step 510.
[0098] Step 509: Execute the subsequent transaction logic of the transaction request.
[0099] Step 510: Refuse to execute the subsequent transaction logic of the transaction request, and return a prompt indicating the reason for the rejection.
[0100] pass Figure 5The cross-transaction channel transaction data processing method shown can not only significantly reduce or avoid the problem of users repeatedly signing contracts for the same transaction type in multi-transaction channel scenarios, but also improve transaction processing efficiency and transaction security.
[0101] Although the process flows described above include multiple operations that occur in a particular order, it should be clearly understood that the processes may include more or fewer operations, which may be performed sequentially or in parallel (eg, using parallel processors or a multi-threaded environment).
[0102] Corresponding to the above-mentioned cross-transaction channel transaction data processing method, the embodiment of this specification also provides a cross-transaction channel transaction data processing device, which can be configured on the above-mentioned server, refer to Figure 6 As shown, in some embodiments of the present specification, a transaction data processing device across transaction channels may include:
[0103] A receiving module 61 is used to receive a transaction request for a target transaction type initiated by a user based on a first transaction channel;
[0104] A first confirmation module 62, used to confirm whether there is first signing information of the user for the first transaction channel and the target transaction type;
[0105] A second confirmation module 63 is used to confirm whether there is second contract information of the user for other transaction channels and the target transaction type when the first contract information does not exist;
[0106] A multiplexing module 64 is configured to multiplex the second contract information as the first contract information of the user for the first transaction channel and the target transaction type when the second contract information exists;
[0107] A verification module 65, configured to verify the consistency between the first contract information and the user identity information of the user;
[0108] The execution module 66 is used to execute the subsequent transaction logic of the transaction request when the first signing information and the user identity information pass the consistency verification.
[0109] In some embodiments of the present specification, the transaction data processing device across transaction channels also includes a signing module; the signing module can be used to: trigger the processing logic for guiding the user to sign a contract for the first transaction channel and the target transaction type when the second confirmation module 63 confirms that the second signing information does not exist; save the signing information when the user successfully signs the contract for the first transaction channel and the target transaction type as the first signing information of the user for the first transaction channel and the target transaction type.
[0110] In the transaction data processing device across transaction channels of some embodiments of the present specification, the second contract information is multiplexed as the first contract information of the user for the first transaction channel and the target transaction type, including: backing up the second contract information; constructing a mapping relationship between the backed-up second contract information and the first transaction channel and the target transaction type, respectively, to serve as the first contract information of the user for the first transaction channel and the target transaction type.
[0111] In the transaction data processing device across transaction channels of some embodiments of the present specification, the execution module 66 is also used to: when the first contract information and the user identity information fail to pass the consistency verification, refuse to execute the subsequent transaction logic of the transaction request and return a prompt of the rejection reason.
[0112] In the transaction data processing device across transaction channels of some embodiments of the present specification, the user identity information includes the user's certificate information and / or biometric information.
[0113] In the cross-transaction-channel transaction data processing device of some embodiments of the present specification, the first transaction channel includes a transaction channel based on a mobile terminal; the other transaction channels include transaction channels based on a mobile terminal and / or other terminals that are different from the first transaction channel.
[0114] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0115] It should be noted that in the embodiments of this specification, the user identity information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user and fully authorized by all parties, that is, the acquisition, transmission, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.
[0116] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0117] The embodiments of this specification also provide a computer device. Figure 7As shown, in some embodiments of the present specification, the computer device 702 may include one or more processors 704, such as one or more central processing units (CPUs) or graphics processing units (GPUs), and each processing unit may implement one or more hardware threads. The computer device 702 may also include any memory 706, which is used to store any kind of information such as code, settings, data, etc. In a specific embodiment, the computer program on the memory 706 and can be run on the processor 704, when the computer program is run by the processor 704, can execute the instructions of the transaction data processing method across transaction channels described in any of the above embodiments. Non-limiting, for example, the memory 706 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 702. In one case, when the processor 704 executes the associated instructions stored in any memory or combination of memories, the computer device 702 can perform any operation of the associated instructions. The computer device 702 also includes one or more drive mechanisms 708 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.
[0118] The computer device 702 may also include an input / output interface 710 (I / O) for receiving various inputs (via input device 712) and for providing various outputs (via output device 714). A specific output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, the input / output interface 710 (I / O), input device 712, and output device 714 may not be included, and the computer device 702 may be used as a computer device in a network. The computer device 702 may also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the components described above together.
[0119] The communication link 722 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.
[0120] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), computer-readable storage media, and computer program products of some embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processor to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processor generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0121] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processor to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0122] These computer program instructions can also be loaded onto a computer or other programmable data processor so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0123] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0124] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0125] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computer device. As defined in this specification, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0126] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
[0127] The present specification embodiments may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present specification embodiments may also be practiced in distributed computing environments where tasks are performed by remote processors connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.
[0128] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0129] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0130] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiments of this specification. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0131] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims
1. A method for processing transaction data across transaction channels, characterized in that: include: Receiving a transaction request for a target transaction type initiated by a user based on a first transaction channel; confirming whether there is first signing information of the user for the first transaction channel and the target transaction type; When the first contract information does not exist, confirming whether there is second contract information of the user for other transaction channels and the target transaction type; When the second contract information exists, the second contract information is multiplexed as the first contract information of the user for the first transaction channel and the target transaction type; Performing consistency verification on the first signing information and the user identity information of the user; When the first signing information and the user identity information pass the consistency verification, the subsequent transaction logic of the transaction request is executed.
2. The cross-transaction channel transaction data processing method according to claim 1, characterized in that: After confirming whether there is second signing information of the user for other transaction channels and the target transaction type, the method further includes: When the second contract information does not exist, triggering a processing logic for guiding the user to sign a contract for the first transaction channel and the target transaction type; The signing information when the user successfully signs the contract for the first transaction channel and the target transaction type is saved as the first signing information of the user for the first transaction channel and the target transaction type.
3. The cross-transaction channel transaction data processing method according to claim 1, characterized in that: Reusing the second signing information as the first signing information of the user for the first transaction channel and the target transaction type includes: backing up the second signing information; A mapping relationship between the backup second contract information and the first transaction channel and the target transaction type is constructed to serve as the first contract information of the user for the first transaction channel and the target transaction type.
4. The cross-transaction channel transaction data processing method according to claim 1, characterized in that: After verifying the consistency between the first signing information and the user identity information of the user, the method further includes: When the first contract information and the user identity information fail to pass the consistency verification, the subsequent transaction logic of the transaction request is rejected and a rejection reason prompt is returned.
5. The cross-transaction channel transaction data processing method according to claim 1, characterized in that: The user identity information includes the user's certificate information and / or biometric information.
6. The cross-transaction channel transaction data processing method according to claim 1, characterized in that: The first transaction channel includes a transaction channel based on a mobile terminal; the other transaction channels include transaction channels based on a mobile terminal and / or other terminals that are different from the first transaction channel.
7. A cross-transaction channel transaction data processing device, characterized in that: include: A receiving module, configured to receive a transaction request for a target transaction type initiated by a user based on a first transaction channel; A first confirmation module, used to confirm whether there is first signing information of the user for the first transaction channel and the target transaction type; A second confirmation module, used for confirming whether there is second contract information of the user for other transaction channels and the target transaction type when the first contract information does not exist; a multiplexing module, configured to multiplex the second contract information as the first contract information of the user for the first transaction channel and the target transaction type when the second contract information exists; A verification module, used to verify the consistency between the first signing information and the user identity information of the user; An execution module is used to execute the subsequent transaction logic of the transaction request when the first signing information and the user identity information pass consistency verification.
8. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 6.
9. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes instructions of the method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor of a computer device, the computer program executes instructions of the method according to any one of claims 1 to 6.
